Is it effective to get address 0 and send the 1000drk to that within the same wallet? Or should I always create a new wallet to send to?
Mine worked when I had over 1000 coins in my wallet, got address 0 (from that wallet), and sent 1000 DRK to the address (within that wallet). Nice, thanks. Saves a bit of time. |
|
|
|
|
Is it effective to get address 0 and send the 1000drk to that within the same wallet? Or should I always create a new wallet to send to?
|
|
|
|
People selling because they think 0.020 is the resistance and price will fall again?  |
|
|
|
|
Man id be pissed if i sold to trade something else then woke up to this
|
|
|
|
I want to note that this newest development on the testnet side and on how future changes will be rolled out could be a massive new development as well.
There was some pain in the two attempts previously to roll out RC3, but it looks like everything is in place now to have a robust and safe coin moving forward even if forks are needed for continued development.
If that is the case, you could indeed see that fork in BTC that you never thought would happen... but I would be happy if they just sit tight and don't make that change either.
DRK could really make a move if that is the case. Continued development will be the key.
Even if bitcoin can fork I doubt they will implement anon technologies because there are too many big businesses and governments to please. Too many eyes on them I think? |
|
|
|
|
lol I hate how impatient I am.
|
|
|
|
Maybe DRK should abandon masternodes entirely? Masternodes have ruined the price.
I bought in at $1, price is looking pretty good |
|
|
|
For people who missed it <@evan82> Two blocks are solved at nearly the same moment on the network, both are propogated and accepted by the network. In the current implementation both blocks have the same hash, but in these blocks there's some discrepency about who to vote for.
<@evan82> In one block the miner votes for 88802 and 88803, in the other the miner abstains from voting. When the next block is solved it's based on of one of the older blocks, so half of the network beleives the miner cheated and rejects the block causing a fork.
<@evan82> The solution to this is rather simple. Any changes to the votes need to also change the hash of the block. The network must not think these two blocks are the same.
<@evan82> http://pastebin.com/QmbM8dPH |
|
|
|
|
If it takes more than hours or days to implement this hard fork then I'd say it'll be months before the coin see's 0.02 again.
Hopefully we don't have another few weeks wait on our hands, although I know what has to be done, has to be done.
|
|
|
|
|
<@evan82> Two blocks are solved at nearly the same moment on the network, both are propogated and accepted by the network. In the current implementation both blocks have the same hash, but in these blocks there's some discrepency about who to vote for.
<@evan82> In one block the miner votes for 88802 and 88803, in the other the miner abstains from voting. When the next block is solved it's based on of one of the older blocks, so half of the network beleives the miner cheated and rejects the block causing a fork.
<@evan82> The solution to this is rather simple. Any changes to the votes need to also change the hash of the block. The network must not think these two blocks are the same.
|
|
|
|
[08:51] <@evan82> I found the problem :-)
[08:51] <@evan82> It's actually rather simple to fix
[08:52] <@evan82> anyone care to guess from the paste? I'm curious
<@evan82> http://pastebin.com/QmbM8dPH |
|
|
|
|
A lot of people sold during the crash and need it to go to -0.013 again or lower
|
|
|
|
And just a quick reminder:
the-way-to-make-money-is-to-buy-when-blood-is-running-in-the-streets-john-d-rockefeller
There is a possibility that we are not at this point yet... And I don't mean to FUD. Logically thinking, the price was @0.016 while people were expecting the migration. Now that the migration has failed because of the same fucking mistakes, I cannot explain 0.0156. We'll see... It looks like dev might have been being a little over-cautious, in which case we are in a flash crash that will quickly resume the trend. this not to mention people (like me) take advantage of such situations |
|
|
|
Problem is this happens all the time now. Every fork. Tired of this BS. Time to move on to something new. This old lady has sung her last song.
How is it affecting you? Darkcoin isn't working for you? No one should be worried unless they are wanting masternode payments right away |
|
|
|
|
hours, days or weeks. any guesses?
|
|
|
|
Just a reminder for people who need to update masternodes from lord chaeplin's guide chmod 755 darkcoind.1 check its the right version ./darkcoind.1 --help ./darkcoind stop replace mv darkcoind darkcoind.old
mv darkcoind.1 darkcoind ./darkcoind
./darkcoind getinfo |
|
|
|
|
Updated masternode, on block 88843, all good
|
|
|
|
|
Show Posts
