Topic: [ANN] ¤ DMD Diamond 3.0 | Scarce ¤ Valuable ¤ Secure | PoS 3.0 | Masternodes 65% - page 788. (Read 1260636 times)
June 27, 2014, 09:55:43 AM
Is there problem with Cryptsy again? I have transfered coins 9 hours ago still no sign of them. They really must love DMDs.
June 27, 2014, 09:49:18 AM
I'm uploading the Foundation Wallet's BC at the moment so should be ready in 1,5h , will cut the time of re-sync significantly.
EDIT: Slight delay as I have encountered some problem while porting the blockchain to the other host, uploading again and once tested will release it.
EDIT: Slight delay as I have encountered some problem while porting the blockchain to the other host, uploading again and once tested will release it.
June 27, 2014, 09:24:00 AM
my wallet dont work
assertion failed!
file:src\kernel.cpp,line 412
Expression: pindex->getblockHash() == (!fTestNet ? hashGenesisBlock : hashGenesisBlockTestNet)
assertion failed!
file:src\kernel.cpp,line 412
Expression: pindex->getblockHash() == (!fTestNet ? hashGenesisBlock : hashGenesisBlockTestNet)
When this happens, the safest way out is to re-index the block chain. Either do a full download again or, (faster) delete blkindex.dat and run diamondd -loadblock=blk0001.dat
That will take some long time, while rebuilding the index.
We will address this problem ASAP.
What's the proper command for MAC? I've tried and doesn't seem to be working for me.
June 27, 2014, 08:52:09 AM
Thanks for clarifying danbi!
I know minting takes time and is a somewhat random process, but is there any way to tell if the wallet is setup correctly for minting? My getinfo shows
"newmint" : 0.00000000,
"stake" : 0.00000000,
I know minting takes time and is a somewhat random process, but is there any way to tell if the wallet is setup correctly for minting? My getinfo shows
"newmint" : 0.00000000,
"stake" : 0.00000000,
June 27, 2014, 08:13:48 AM
As for danbis pool, not sure about the stats there, seems as if it was down. Anyone mining there with success?
Shitload of orphaned in there.
Stats are paused on the pool website, the orphans are from about 20 hours ago. My miner is showing accepted shares and the correct network diff, so I hope its just display problems and mining is actually working fine...
Correct. The pool has always been on the 'right' chain, but because of some other issues, it was often subject of 'overtaking attack' by the wrong chains. A side effect of a fix we made to the wallet code earlier has made this possible. With more and more people minting, the 'wrong' chain had become weaker and weaker. As popshot explained, the network (protocol) is designed to heal itself.
I am currently running the pool's maintenance scripts to have it properly display earnings etc during this period. Will be away from computers for a couple more days most of the time so coding few fixes to speed things up will wait for the weekend.
June 27, 2014, 07:57:56 AM
It is a pity that it all was so seriously and at the crucial moment (start Pos) occurred fork .. Need more carefully checked before a new release wallet.
guidosuller
I replaced not only the base with blocks but and backup wallet.dat only then earned my wallet
guidosuller
I replaced not only the base with blocks but and backup wallet.dat only then earned my wallet
You must delete blkindex.dat for this to work.
This all happened for several reasons. Most of reasons being people are way too lazy and did not upgrade their wallets, yet continue to solo mine with heavy hash power. There is apparently malicious code out there, let's hope these drop out for good.
In a way, the combination of heavy miners that did not upgrade and PoS kicking in created the "problem". It was more or less expected -- just we did not expect it to be so pronounced. In a while, old wallets will stop accepting new blocks and it will "sort it out by itself".
June 27, 2014, 07:51:45 AM
my wallet dont work
assertion failed!
file:src\kernel.cpp,line 412
Expression: pindex->getblockHash() == (!fTestNet ? hashGenesisBlock : hashGenesisBlockTestNet)
assertion failed!
file:src\kernel.cpp,line 412
Expression: pindex->getblockHash() == (!fTestNet ? hashGenesisBlock : hashGenesisBlockTestNet)
When this happens, the safest way out is to re-index the block chain. Either do a full download again or, (faster) delete blkindex.dat and run diamondd -loadblock=blk0001.dat
That will take some long time, while rebuilding the index.
We will address this problem ASAP.
June 27, 2014, 07:47:31 AM
Hi, my pc did a restart during the night and my wallet crashed when it reopened. i resynced the blockchain but now its only saying i have 200dmd with 70 staking so ive lost over 650 dmd. whats happened as the transactions are still there...
June 27, 2014, 07:28:25 AM
As for danbis pool, not sure about the stats there, seems as if it was down. Anyone mining there with success?
Shitload of orphaned in there.
Stats are paused on the pool website, the orphans are from about 20 hours ago. My miner is showing accepted shares and the correct network diff, so I hope its just display problems and mining is actually working fine...
June 27, 2014, 07:19:13 AM
As for danbis pool, not sure about the stats there, seems as if it was down. Anyone mining there with success?
Shitload of orphaned in there.
June 27, 2014, 07:10:57 AM
Not sure. Cryptohunger pool is on the right fork though.
They've confirmed they had the updated version of the client.
If the pool shows the correct network diff (around 42 atm), it should be on the correct chain, because a wrong chain should likely have a much lower diff, right?
Yes, also the wrong number of blocks. Usually the chain with the highest network hash is the main one, that's how the Bitcoin protocol works. That said , the main does not always mean correct, however in this case (with the correct wallet) it shouldn't be the case.
As for danbis pool, not sure about the stats there, seems as if it was down. Anyone mining there with success?
June 27, 2014, 07:02:40 AM
Not sure. Cryptohunger pool is on the right fork though.
They've confirmed they had the updated version of the client.
If the pool shows the correct network diff (around 42 atm), it should be on the correct chain, because a wrong chain should likely have a much lower diff, right?
June 27, 2014, 06:51:24 AM
Something the next version of the wallet definitely needs is auto-notification if a new version is detected and an indicator showing staking weight, network weight and ETA to stake. Don't know if this is possible or not but some way to detect forked chains and notify of possible problem 
If I remember correctly (getting old) DOGE coin switched to a different wallet database that allowed much faster opening, re-indexing and syncing ...
If I remember correctly (getting old) DOGE coin switched to a different wallet database that allowed much faster opening, re-indexing and syncing ...
June 27, 2014, 06:42:15 AM
Not sure. Cryptohunger pool is on the right fork though.
They've confirmed they had the updated version of the client.
June 27, 2014, 06:40:49 AM
If that is the case, you should then be active and keep posting regularly an updated blockchain so that we don't need to be sinking the wallet from too far away. We don't all leave our wallets open all day/night long.
I'd love to do that, however the foundation wallet is still 'turning on' (sync seems to be done already).. and has been turning on for hours , there are over 77 thousands of transactions to go through. Once it's operational and I confirm we are on the same chain then I will share the database.
The error message, I can't fix it as it's a deeply rooted problem.
June 27, 2014, 06:35:51 AM
So are you saying that danbis pool IS on the wrong chain? Just want to know if it makes sense to direct miners elsewhere for the weekend...
Not sure. Cryptohunger pool is on the right fork though.
June 27, 2014, 06:26:16 AM
So wallet must be kept open after re-index or another oh-shit have to re-index if power fails or needing to reboot after winblowz updates ... Closing wallet NOT advisable till new wallet bugfixes LOL
@popshot how about publishing checkpoints regularly on OP so users can verify they are on correct blockchain
@popshot how about publishing checkpoints regularly on OP so users can verify they are on correct blockchain
June 27, 2014, 06:14:12 AM
It seems that forking was inevitable as not everyone had updated their clients , and some powerful miners kept mining after the switch. The network is designed in such a way that it will 'heal' itself without any intervention .. the strongest chain will prevail.
The situation with that error is indeed annoying and it might not be a quick fix, especially, because danbi had to go to a few day conference and his time and resources are extremely limited to deal with it at this very moment. I was hit with it as well and the foundation wallet is dysfunctional and has been syncing since yesterday.
All we can do at the moment is wait and don't despair as these things are fixable - the network can fix itself but the wallet need some more work. Danbi will be back this weekend and will follow up on this issue.
I haven't got access to his pool so cannot share the correct chain.
To some saying about having coins 7 days old and not minting.. Minting does not happen just like that , it's a lottery, you need to wait for your turn (either difficulty falls or the coins will be grouped next time round automatically and that will increase the chance of you successfully staking).
The situation with that error is indeed annoying and it might not be a quick fix, especially, because danbi had to go to a few day conference and his time and resources are extremely limited to deal with it at this very moment. I was hit with it as well and the foundation wallet is dysfunctional and has been syncing since yesterday.
All we can do at the moment is wait and don't despair as these things are fixable - the network can fix itself but the wallet need some more work. Danbi will be back this weekend and will follow up on this issue.
I haven't got access to his pool so cannot share the correct chain.
To some saying about having coins 7 days old and not minting.. Minting does not happen just like that , it's a lottery, you need to wait for your turn (either difficulty falls or the coins will be grouped next time round automatically and that will increase the chance of you successfully staking).
So are you saying that danbis pool IS on the wrong chain? Just want to know if it makes sense to direct miners elsewhere for the weekend...
June 27, 2014, 06:08:59 AM
It seems that forking was inevitable as not everyone had updated their clients , and some powerful miners kept mining after the switch. The network is designed in such a way that it will 'heal' itself without any intervention .. the strongest chain will prevail.
The situation with that error is indeed annoying and it might not be a quick fix, especially, because danbi had to go to a few day conference and his time and resources are extremely limited to deal with it at this very moment. I was hit with it as well and the foundation wallet is dysfunctional and has been syncing since yesterday.
All we can do at the moment is wait and don't despair as these things are fixable - the network can fix itself but the wallet need some more work. Danbi will be back this weekend and will follow up on this issue.
I haven't got access to his pool so cannot share the correct chain.
To some saying about having coins 7 days old and not minting.. Minting does not happen just like that , it's a lottery, you need to wait for your turn (either difficulty falls or the coins will be grouped next time round automatically and that will increase the chance of you successfully staking).
The situation with that error is indeed annoying and it might not be a quick fix, especially, because danbi had to go to a few day conference and his time and resources are extremely limited to deal with it at this very moment. I was hit with it as well and the foundation wallet is dysfunctional and has been syncing since yesterday.
All we can do at the moment is wait and don't despair as these things are fixable - the network can fix itself but the wallet need some more work. Danbi will be back this weekend and will follow up on this issue.
I haven't got access to his pool so cannot share the correct chain.
To some saying about having coins 7 days old and not minting.. Minting does not happen just like that , it's a lottery, you need to wait for your turn (either difficulty falls or the coins will be grouped next time round automatically and that will increase the chance of you successfully staking).
If that is the case, you should then be active and keep posting regularly an updated blockchain so that we don't need to be sinking the wallet from too far away. We don't all leave our wallets open all day/night long.
June 27, 2014, 06:00:41 AM
It seems that forking was inevitable as not everyone had updated their clients , and some powerful miners kept mining after the switch. The network is designed in such a way that it will 'heal' itself without any intervention .. the strongest chain will prevail.
The situation with that error is indeed annoying and it might not be a quick fix, especially, because danbi had to go to a few day conference and his time and resources are extremely limited to deal with it at this very moment. I was hit with it as well and the foundation wallet is dysfunctional and has been syncing since yesterday.
All we can do at the moment is wait and don't despair as these things are fixable - the network can fix itself but the wallet need some more work. Danbi will be back this weekend and will follow up on this issue.
I haven't got access to his pool so cannot share the correct chain.
To some saying about having coins 7 days old and not minting.. Minting does not happen just like that , it's a lottery, you need to wait for your turn (either difficulty falls or the coins will be grouped next time round automatically and that will increase the chance of you successfully staking).
The situation with that error is indeed annoying and it might not be a quick fix, especially, because danbi had to go to a few day conference and his time and resources are extremely limited to deal with it at this very moment. I was hit with it as well and the foundation wallet is dysfunctional and has been syncing since yesterday.
All we can do at the moment is wait and don't despair as these things are fixable - the network can fix itself but the wallet need some more work. Danbi will be back this weekend and will follow up on this issue.
I haven't got access to his pool so cannot share the correct chain.
To some saying about having coins 7 days old and not minting.. Minting does not happen just like that , it's a lottery, you need to wait for your turn (either difficulty falls or the coins will be grouped next time round automatically and that will increase the chance of you successfully staking).
Jump to: