@mnb7089 coins are not real now, what it is now being tested to verify that the TestNet not have bugs and it runs smoothly. Next Wednesday will activate the MainNet.
We will get an exact date and time today. This is precisely my concern too and I would feel terrible if people took work off for a day that may change. There is discussion about it now and we're tallying it up. Let me report back with an announcement with an exact day and time for mainnet launch.
I kind of agree with you but i hope GUI will be available in a few days of mainnet launch. People are struggling even to check balance. Even i am not able to see how much stake reward i got for voting on a block.
how delete the wallet , i'm forget not enter the publickey , i want restart process but cmd said the wallet already exist
the wallet is created but i'm not insert the public key , i answer "no" , is a bug ?? on the step number 3 , said "invalid public key " , actually i'm not insert or not use both private & public key
Deleting the "Dcrwallet" folder in your local application data folder will delete the wallet. Then when you create the new wallet, re-entering the seed that you received at first creation will let you retain all of your addresses and any DCR you received.
You will need to create a new wallet using the seed that you got, if you were selected successfully for the Airdrop. The coins will be send to this address
Thank you for your continued consideration, _ingsoc. Maybe a mild pressure relief: I think I can speak for the community in saying even if I went ahead and took a day off and the date were pushed, I'd know it were for good reason and would rather that than rushing it.
post localhost:19110 malformed after step dcrctl --testnet --notls -u user -P pass --wallet getnewaddress , why so many error here ??
I'll cross-post this here, as it seems appropriate; I originally posted it in the "Public Testnet Evaluation" thread in Technical Development. I found out that the simnet option does NOT put it on the "official" testnet! I thought it did at first, but I still see no need to retract my earlier post because it's actually still correct - it does put you on testnet - A testnet, just not THE testnet. Taking a moment for a side note: I LOVE THIS SHIT! I've often wanted to use the capability of Bitcoin & clones that's referred to as "testnet-in-a-box" - but I always found it so tedious to get working that I never actually did. One reason I wanted to was to test miners for coins with few/no pools, or before launch - in the former case, the mainnet diff may be too high, causing the time required (on average) to pop a block to become too long for testing, and in the latter case, there's no mainnet at all. But this shit is awesome! You can set up your own testnet-in-a-box effortlessly - for any purpose you may need it for! Anyways, tangent over - let me clarify how I've gotten up and running on the current official testnet and mined some tDCR for myself! This is to be done on the system with which you wish to run your main (real) instance of dcrd, as well as dcrwallet and where you plan to access it using dcrctl. All Decred-related binaries are assumed to be in PATH (I like to stuff 'em in /usr/local/bin, chown them to root, and chmod them to 711.) Screen is used in my examples so that you don't need to keep open a shitton of terminals/tabs (I love screen; I use it myself for this and other purposes, too.) Code: screen -dmS decred dcrd --notls --testnet --rpcuser=Slut --rpcpas=x This won't put you in the screen - it will run the command in a detached one for you, which you may access at any time using: Code: screen -dr decred To detach yourself from the screen you're in, hold down Ctrl, press and release a, then d, and then you may let go of Ctrl. To create a wallet - first open a screen for it and attach, then run dcrwallet. I don't have a detailed walkthrough on getting you through the prompts, as I created mine a while ago, but you should be fine. Code: screen -S dcrwallet dcrwallet --noservertls --noclienttls -u Slut -P x --create I'm not totally sure on that dcrwallet command, but it's something on that order - the help output is your friend. Note that I DIDN'T use "--testnet" - testnet is apparently the default, at least for the binary I have. Finally, you should be ready to use your wallet/daemon using dcrctl - this will get you a new address; for other commands, as I said, see the help outputs. Code: dcrctl -u Slut -P x --notls --testnet --wallet getnewaddress If you opted for hiding the wallet details behind another password during wallet creation, you'll need to provide this to dcrwallet on the command line. Nitpick: You know what I don't get? Security is *so* important that we can't bind the RPC server to anything except localhost without TLS - and this is ENFORCED, currently, by the code - yet the password for the wallet information (which is admittedly less sensitive than the main wallet pass) can be passed to dcrwallet on the COMMAND LINE. If you don't get why it's funny - try running it on a linux-based machine under your account, then sudo su to an unprivileged account (I used the git account, because it had a shell that wasn't /sbin/nologin or /bin/false), and then run ps ax and pipe it to grep dcrwallet. Oops, any unprivileged user now knows the password for the (less sensitive) wallet information just by listing the active processes. Note that this CAN be fixed simply by using a config file (I THINK - I still haven't really gotten into using those with Decred yet), but I just find it kind of funny that TLS is enforced in the damned binary because apparently we can't make that security decision for ourselves... yet the accidental leak I just mentioned I haven't even seen a warning about, let alone a straight up action from the devs that disallows it.