polanskiman
|
|
July 31, 2014, 09:52:58 AM |
|
Current checkpoint:  { "synccheckpoint" : "00000000011c6943555847f7a7c701cb21d6c1e33a56e4a3be2593424dc7f80d", "height" : 511430, "timestamp" : "2014-07-31 09:51:11 UTC" }
|
|
|
|
polanskiman
|
|
July 31, 2014, 09:56:46 AM Last edit: July 31, 2014, 12:01:12 PM by polanskiman |
|
Here's are some stubborn people:
{ "addr" : "72.200.68.98:61887", "services" : "00000001", "lastsend" : 1406800492, "lastrecv" : 1406800419, "conntime" : 1406800418, "version" : 60006, "subver" : "/Diamond:2.0.2.1/", "inbound" : true, "releasetime" : 0, "startingheight" : 511431, "banscore" : 0 },
{ "addr" : "131.191.88.111:17771", "services" : "00000001", "lastsend" : 1406800608, "lastrecv" : 1406800577, "conntime" : 1406800564, "version" : 60006, "subver" : "/Diamond:2.0.2.1/", "inbound" : false, "releasetime" : 0, "startingheight" : 386226, "banscore" : 0 }
|
|
|
|
|
Timelord2067
Legendary
Offline
Activity: 3724
Merit: 2222
💲🏎️💨🚓
|
|
July 31, 2014, 03:26:54 PM |
|
No zip file then?
|
|
|
|
utahjohn
|
|
July 31, 2014, 05:40:03 PM |
|
Still having blockchain problems ... re-indexed from beginning and diff was 35-45 for several hours and then dropped to 9. This is frustrating
|
|
|
|
NineEleven
|
|
July 31, 2014, 06:11:29 PM |
|
I would suggest those suffering from this issue follow this checklist:
1. Upgrade to the latest wallet version (2.0.3) -- as a bonus you are getting the fast index feature, which besides being.. fast, helps great deal with the block index corruption (does not resolve it 100% yet). 2. Delete your peers.dat file! 3. Then make sure you have noirc=1 in the Diamond.conf file. 4. Make sure you have connect=193.68.21.19 in your configuration file. (or, later switch it to addnode=193.68.21.19) 5. If you do not run your wallet all the time (thus acting as a node for others), it might be helpful to have listen=0 in the configuration file as well. 6. Download the posted recent block chain (or sync from scratch).
So in summary, you need this in the config file:
listen=0 noirc=1 connect=193.68.21.19
The later might be addnode= instead so you get more peers from that node and be connected when it is down or unreachable. Unfortunately, that node might be banning you... because of your past behavior. We are working to make the ban duration shorter.
PS: We want to get rid of wallets version 2.0.2.1. Unfortunately, this also means we need to get rid of 2.0.2.2 as due to some error that shows itself as 2.0.2.1 too... So if you have one of these versions, *please* upgrade.
PPS: Re-arranged the steps appropriately.
Hello all from Portugal this is my first post here I have never write here but i read it every day, and i'm am a DMD miner / investor But today this is getting very hard I have two servers one for solo mining where my miners connect at 150 mhs and another machine just for staking And my Diamond.conf is this on both machines listen=0 server=1 daemon=1 rpcuser=username rpcpassword=passowrd rpcport=1444 rpcallowip=* rpcthreads=8182 connect=193.68.21.19 noirc=1 and today this is the second time that the mining server get's on the wrong fork this is very bad for the reputation A situation like this kill atheistcoin, almost kill fluttercoin Of course my wallets are always updated I think the most important feature for any type of currency ( crypto or flat ) is stability and the last months every week some coin got forked, it happen to me in flut , DMD , ATH , STR and so on As an investor i already dumped 5M flut , and I'm start thinking in dump my 3000 DMD, and begin to miner and dump . I really like DMD , the small reward , make it difficult and interesting , and the sloow adition of coin's to the network is a huge advantage . By the way , and this is just my opinion , POS was a huge mistake it bring more problems to the blockchain than advantages , POW and high hash rate is what makes a coin secure , look a dogecoin, since the hashrate drops, people star concerning about network security price drops and i think that doge will eventualy die . And the reason i love DMD was the groestl algo and a fixed reward of 1 DMD , POS sucks . Since de POS switch , this coin have had many problems, and as an investor i dont like new wallets every week , it makes me nervous . Another problem, my wallet evrey time it shut-down , i have to resync from scratch whit loadblok=blk0001.dat, that issue must be fixed asap ( again this is POS fault) Please , focus on stability, we don’t need a fancy wallet , or fancy features , as an investor i want reliable block chain, HIGH HASHRATE nothing more. sory for my bad inglish Regards Porfirio from sunny portugal
|
|
|
|
NineEleven
|
|
July 31, 2014, 06:28:44 PM |
|
Still having blockchain problems ... re-indexed from beginning and diff was 35-45 for several hours and then dropped to 9. This is frustrating yep that what’s happened to me again
|
|
|
|
shveicar
Legendary
Offline
Activity: 1414
Merit: 1013
DMD info: https://diamond-info.github.io/
|
|
July 31, 2014, 06:54:02 PM |
|
There is still a lot of work to strengthen the security of the network of Diamond and prevent such attacks in the future. Such methods are available and should be used .. The Diamond should be one of the most stable coins to such attacks. Only then will success.
|
|
|
|
pallas
Legendary
Offline
Activity: 2716
Merit: 1094
Black Belt Developer
|
|
July 31, 2014, 07:04:49 PM |
|
I've experienced this error:
diamondd: /usr/include/boost/thread/pthread/recursive_mutex.hpp:101: void boost::recursive_mutex::lock(): Assertion `!pthread_mutex_lock(&m)' failed.
A couple times when stopping the daemon.
|
|
|
|
cryptonit
Legendary
Offline
Activity: 3038
Merit: 1053
bit.diamonds | uNiq.diamonds
|
|
July 31, 2014, 08:09:44 PM |
|
as an investor i dont like new wallets every week , it makes me nervous . Another problem, my wallet evrey time it shut-down , i have to resync from scratch whit loadblok=blk0001.dat, that issue must be fixed asap ( again this is POS fault) Please , focus on stability, we don’t need a fancy wallet , or fancy features , as an investor i want reliable block chain, HIGH HASHRATE nothing more. sory for my bad inglish Regards Porfirio from sunny portugal hi porfirio we take ur feedback very serious thx for posting still one or two new wallets will come in this stabilisation phase but not for fancy features we want exact same as u a stable network and stable wallet but later on most wallet releases will be optional so fancy stuff for people who want but noone forced to update regarding ur resync after each shut down please tell us what wallet version u run i strong suggest upgrade to 2.0.3 to everyone it will be soon mandatory to have at least this version
|
|
|
|
danbi
|
|
July 31, 2014, 08:10:32 PM |
|
And my Diamond.conf is this on both machines
listen=0 server=1 daemon=1 rpcuser=username rpcpassword=passowrd rpcport=1444 rpcallowip=* rpcthreads=8182 connect=193.68.21.19 noirc=1
and today this is the second time that the mining server get's on the wrong fork
This is pretty much not possible. You cannot get on the wrong fork when connected to only 193.68.21.19. There is no way you can get a wrong block. What does 'getpeerinfo' return? If your setup is correct, you should have only one peer, 193.68.21.19. Also, rpcallow=* is a very bad idea. rpcthreads=8182 possibly too...
|
BTC: 15cJkRupKAkGr6sTxj1Uzb6uHbvuRyK1GL DMD: dJZEqNcjiUiMMd8DKBFS9oMWtArAD2GCHr
|
|
|
cryptonit
Legendary
Offline
Activity: 3038
Merit: 1053
bit.diamonds | uNiq.diamonds
|
|
July 31, 2014, 09:05:03 PM |
|
diff raise again sign situation solved miners found their way home time for me move my miners again to http://multipool.bit.diamonds/we made over 1100 DMD there already in a few days join us and earn not only DMD but also a chance to win 100DMD in multipool lotto with ur average daily hashrate u earn there lotto tickets (numbers) more hashrate more tickets (up to 6 max each day) next drawing of winner is sunday 3rd august the winner will be choosen by austrian officicial lotto jackpotnumber from 3.august (will be visible there after around 21:00 europe time on 3rd august http://www.win2day.at/gaming/RundenPlakat_wai.jsp) our lotto number which is closest to it wins close in mathematical sence not how many numbers are the same so example 123456 joker number 923456 not closest number 187654 closest number
|
|
|
|
danbi
|
|
July 31, 2014, 09:05:21 PM |
|
As announced previously, the http://dmdpool.digsys.bg pool has now introduced 1% fee from 1st of August 2014. Let's hope this change, by eliminating "unfair competition" will encourage more Diamond mining pols to be created.
|
BTC: 15cJkRupKAkGr6sTxj1Uzb6uHbvuRyK1GL DMD: dJZEqNcjiUiMMd8DKBFS9oMWtArAD2GCHr
|
|
|
jhed
Newbie
Offline
Activity: 26
Merit: 0
|
|
July 31, 2014, 09:14:25 PM |
|
Still having blockchain problems ... re-indexed from beginning and diff was 35-45 for several hours and then dropped to 9. This is frustrating yep that what’s happened to me again If anybody is consistently getting on the wrong block chain, you might consider that 193.68.21.19 actually has the wrong block chain. Check your debug.log to see if you have what I found in mine: received block 000000000310f60b9126 ProcessBlock: ORPHAN BLOCK, prev=000000000302b0af011c received block 000000000302b0af011c ProcessBlock: ORPHAN BLOCK, prev=0000000004e6b27a0790 received block 0000000000d652bceaa2 connection timeout ProcessBlock: ACCEPTED received block 00000000078b6cf20c99 Misbehaving: 193.68.21.19:17771 (0 -> 100) DISCONNECTING disconnecting node 193.68.21.19:17771 ERROR: ProcessBlock() : block with too little proof-of-work
I am successfully solo mining right now. Here is getinfo from my diamondd: > date Thu Jul 31 20:20:45 GMT 2014 > diamondd getinfo { "version" : "v2.0.3.0", "protocolversion" : 60006, "walletversion" : 60000, "blocks" : 512014, "moneysupply" : 517671.38180200, "connections" : 8, "proxy" : "", "difficulty" : 13.98245459, "paytxfee" : 0.00100000, } > date Thu Jul 31 21:00:31 GMT 2014 > diamondd getinfo { "version" : "v2.0.3.0", "protocolversion" : 60006, "walletversion" : 60000, "blocks" : 512050, "moneysupply" : 517709.18180200, "connections" : 11, "difficulty" : 10.46732144, "paytxfee" : 0.00100000, } Try nuking 193.68.21.19 from your configs and deleting your peers.dat to reset it.
|
|
|
|
danbi
|
|
July 31, 2014, 09:22:52 PM |
|
Still having blockchain problems ... re-indexed from beginning and diff was 35-45 for several hours and then dropped to 9. This is frustrating yep that what’s happened to me again If anybody is consistently getting on the wrong block chain, you might consider that 193.68.21.19 actually has the wrong block chain. Check your debug.log to see if you have what I found in mine: received block 000000000310f60b9126 ProcessBlock: ORPHAN BLOCK, prev=000000000302b0af011c received block 000000000302b0af011c ProcessBlock: ORPHAN BLOCK, prev=0000000004e6b27a0790 received block 0000000000d652bceaa2 connection timeout ProcessBlock: ACCEPTED received block 00000000078b6cf20c99 Misbehaving: 193.68.21.19:17771 (0 -> 100) DISCONNECTING disconnecting node 193.68.21.19:17771 ERROR: ProcessBlock() : block with too little proof-of-work
I am successfully solo mining right now. Here is getinfo from my diamondd: > date Thu Jul 31 20:20:45 GMT 2014 > diamondd getinfo { "version" : "v2.0.3.0", "protocolversion" : 60006, "walletversion" : 60000, "blocks" : 512014, "moneysupply" : 517671.38180200, "connections" : 8, "proxy" : "", "difficulty" : 13.98245459, "paytxfee" : 0.00100000, } > date Thu Jul 31 21:00:31 GMT 2014 > diamondd getinfo { "version" : "v2.0.3.0", "protocolversion" : 60006, "walletversion" : 60000, "blocks" : 512050, "moneysupply" : 517709.18180200, "connections" : 11, "difficulty" : 10.46732144, "paytxfee" : 0.00100000, } Try nuking 193.68.21.19 from your configs and deleting your peers.dat to reset it. This will guarantee whatever you mine, will never, ever be accepted on the Diamond block chain. But, if you enjoy mining at low difficulty, alone, it's a good method. :-)
|
BTC: 15cJkRupKAkGr6sTxj1Uzb6uHbvuRyK1GL DMD: dJZEqNcjiUiMMd8DKBFS9oMWtArAD2GCHr
|
|
|
utahjohn
|
|
July 31, 2014, 09:40:50 PM |
|
This will guarantee whatever you mine, will never, ever be accepted on the Diamond block chain.
Exactly why I have quit mining until this repeated forking is resolved. LOL good luck with your ORPHANS if you are on wrong blockchain ... I have closed wallet until this situation if suitably corrected. Using only connect=193.68.21.19 defeats the whole purpose of de-centralized blockchain and if I use addnode=193.68.21.19 I end up on wrong fork again after a couple hours mining Thus my frustration
|
|
|
|
jhed
Newbie
Offline
Activity: 26
Merit: 0
|
|
July 31, 2014, 09:47:14 PM |
|
This will guarantee whatever you mine, will never, ever be accepted on the Diamond block chain.
Exactly why I have quit mining until this repeated forking is resolved. LOL good luck with your ORPHANS if you are on wrong blockchain ... I have closed wallet until this situation if suitably corrected. Using only connect=193.68.21.19 defeats the whole purpose of de-centralized blockchain and if I use addnode=193.68.21.19 I end up on wrong fork again after a couple hours mining Thus my frustration utahjohn, I agree. So why are you adding it into your config? The network decides who has the right chain and who has the wrong one. Since cryptsy just accepted a transaction from me, I'd say I'm on the right chain. You all should really check your debug.log for "Misbehaving: 193.68.21.19:17771 (0 -> 100) DISCONNECTING"
|
|
|
|
utahjohn
|
|
July 31, 2014, 09:53:24 PM |
|
This will guarantee whatever you mine, will never, ever be accepted on the Diamond block chain.
Exactly why I have quit mining until this repeated forking is resolved. LOL good luck with your ORPHANS if you are on wrong blockchain ... I have closed wallet until this situation if suitably corrected. Using only connect=193.68.21.19 defeats the whole purpose of de-centralized blockchain and if I use addnode=193.68.21.19 I end up on wrong fork again after a couple hours mining Thus my frustration utahjohn, I agree. So why are you adding it into your config? The network decides who has the right chain and who has the wrong one. Since cryptsy just accepted a transaction from me, I'd say I'm on the right chain. You all should really check your debug.log for "Misbehaving: 193.68.21.19:17771 (0 -> 100) DISCONNECTING" I'd advise against deposit/withdraw from Cryptsy until forking issue is resolved. I would guess Cryptsy also on wrong fork as the difficulty before these problems started showing up was in the 60-110 range and thus had highest hashrate versus the 7-15 I see when I think I'm on wrong fork.
|
|
|
|
jhed
Newbie
Offline
Activity: 26
Merit: 0
|
|
July 31, 2014, 10:04:46 PM |
|
This will guarantee whatever you mine, will never, ever be accepted on the Diamond block chain.
Exactly why I have quit mining until this repeated forking is resolved. LOL good luck with your ORPHANS if you are on wrong blockchain ... I have closed wallet until this situation if suitably corrected. Using only connect=193.68.21.19 defeats the whole purpose of de-centralized blockchain and if I use addnode=193.68.21.19 I end up on wrong fork again after a couple hours mining Thus my frustration utahjohn, I agree. So why are you adding it into your config? The network decides who has the right chain and who has the wrong one. Since cryptsy just accepted a transaction from me, I'd say I'm on the right chain. You all should really check your debug.log for "Misbehaving: 193.68.21.19:17771 (0 -> 100) DISCONNECTING" I'd advise against deposit/withdraw from Cryptsy until forking issue is resolved. I would guess Cryptsy also on wrong fork as the difficulty before these problems started showing up was in the 60-110 range and thus had highest hashrate versus the 7-15 I see when I think I'm on wrong fork. Difficulty and connection count is going up over here on the network-accepted chain: > date Thu Jul 31 22:03:35 GMT 2014 jhed@omnom-tower:~> diamondd getinfo { "version" : "v2.0.3.0", "protocolversion" : 60006, "walletversion" : 60000, "blocks" : 512114, "moneysupply" : 517784.82106200, "connections" : 16, "proxy" : "", "difficulty" : 18.93459497, "testnet" : false, "paytxfee" : 0.00100000, "errors" : "" }
|
|
|
|
cryptonit
Legendary
Offline
Activity: 3038
Merit: 1053
bit.diamonds | uNiq.diamonds
|
|
July 31, 2014, 10:35:16 PM |
|
jhed Newbie * Online Online
Activity: 3 Posts: 3 nice try appear out of nowhere after a attack with 3 post account all at DMD and try motivate people dont to use the stable point of our network i would say thats part2 of an attack plan multiple attacks failed now try the social one..... people trust in danbi's suggested solution we are on same chain as cryptsy dmd multipool is one same chain
|
|
|
|
|