Topic: [ANN][SEED] SeedCoin | New Road Map - page 124. (Read 184103 times)
What a forkfest right now :/
Dev, can you confirm that we are on correct fork ?
Code:
seedcoind getinfo
{
"version" : "v0.9.1.0-49-g49f746b",
"protocolversion" : 60013,
"walletversion" : 60000,
"stake" : 0.00000000,
"blocks" : 3463,
"timeoffset" : 0,
"moneysupply" : 399.56336962,
"connections" : 1,
"proxy" : "",
"difficulty" : {
"proof-of-work" : 9.67364279,
"proof-of-stake" : 0.00000097
},
"testnet" : false,
"keypoololdest" : 1412456088,
"keypoolsize" : 101,
"paytxfee" : 0.00001000,
"mininput" : 0.00000000,
"errors" : ""
}
Funny, I cannot get the wallet synched to the correct fork, got some nodes ?
That's where the initial updated wallet gets stuck. There was a network security hole in the updated staking algo that allowed people to fork the network if they set their clocks forward and began staking.ep ge
The wallet needs to be compiled again or you'll keep getting hung up on the attack.
lol i'm no newbie, you don't have to tell me that, wallet is compiled from scratch with latest github of course
My wallet is on the same block as such pool but they arent getting any coins in their blocks it looks like and there is a message that says
" The network does not seem to accept new blocks and orphaned the last bunch "
" The network does not seem to accept new blocks and orphaned the last bunch "
Funny, I cannot get the wallet synched to the correct fork, got some nodes ?
That's where the initial updated wallet gets stuck. There was a network security hole in the updated staking algo that allowed people to fork the network if they set their clocks forward and began staking.
The wallet needs to be compiled again or you'll keep getting hung up on the attack.
Nope.. Tried like 5 times now from scratch, always syncs to 3140 or something different...
yeah something is going wrong... of course I rented 350MH/s about an hour before all this shit started :/
Hmm it looks like there are again multiple different forks, which is the correct one ?!
I'm ending up on 31xx everytime i try to resync
I'm ending up on 31xx everytime i try to resync
the official ones are
addnode=185.45.192.191
addnode=198.144.184.175
addnode=199.127.226.221
I'm in the process of unbanning things. Do make sure you have built the latest copy of seedcoind off the github repo - the original update had a timewarp bug in the staking algo that allowed an attack on the network, which is how we ended up forked in the first place.
addnode=185.45.192.191
addnode=198.144.184.175
addnode=199.127.226.221
I'm in the process of unbanning things. Do make sure you have built the latest copy of seedcoind off the github repo - the original update had a timewarp bug in the staking algo that allowed an attack on the network, which is how we ended up forked in the first place.
after one hour of trying to make it sync with the latest wallet, I managed to make it start syncing.
it 's stuck at 48 blocks remaining
it 's stuck at 48 blocks remaining
Funny, I cannot get the wallet synched to the correct fork, got some nodes ?
Mine so far...
addnode=99.236.215.227:15330
addnode=184.155.137.189:15330
addnode=185.45.192.191
addnode=198.144.184.175
addnode=199.127.226.221
addnode=32.213.107.52:63555
addnode=107.150.39.42:46411
addnode=178.33.126.221:56234
addnode=75.118.157.32:60286
addnode=192.99.36.115:48706
addnode=198.27.69.59:33755
just got new linux daemon, this is what im showing:
"version" : "v0.9.1.0-49-g49f746b",
"protocolversion" : 60013,
"walletversion" : 60000,
"blocks" : 3414,
EDIT: YES WE ARE GOOD TO GO! sent tweet out. man, two updates in one night! time for sleepy time.
"version" : "v0.9.1.0-49-g49f746b",
"protocolversion" : 60013,
"walletversion" : 60000,
"blocks" : 3414,
EDIT: YES WE ARE GOOD TO GO! sent tweet out. man, two updates in one night! time for sleepy time.
lifeforce pools concur - some pools are not updated
we are:
{
"version" : "v0.9.1.0-49-g49f746b",
"protocolversion" : 60013,
"walletversion" : 60000,
"blocks" : 3451,
Funny, I cannot get the wallet synched to the correct fork, got some nodes ?
what pool except goldmine is on the correct block? (goldmine doesnt have a port for high hash asics)
edit: suchpool will do
Hashlink look fine, so far everything seems OK - blocks are confirming.edit: suchpool will do
what pool except goldmine is on the correct block? (goldmine doesnt have a port for high hash asics)
edit: suchpool will do
edit: suchpool will do
3403 does not move the right fork?
Source updated with checkpoint for correct fork.
For people with windows wallets, go to help > debug window
Paste the following:
getblock 000000000055b9d4876d376097e81ce34506cf148d28b94af13dda0c73944341
if you get an error you will need to resync your block chain.
The current wallet on dropbox has the correct checkpoint on it. If you are on the right fork, the update is optional.
I am very, very sorry for the inconvenience. We'll get this sorted.
For people with windows wallets, go to help > debug window
Paste the following:
getblock 000000000055b9d4876d376097e81ce34506cf148d28b94af13dda0c73944341
if you get an error you will need to resync your block chain.
The current wallet on dropbox has the correct checkpoint on it. If you are on the right fork, the update is optional.
I am very, very sorry for the inconvenience. We'll get this sorted.
None of the fork in the correct pools!???
seedcoind getblock 000000000055b9d4876d376097e81ce34506cf148d28b94af13dda0c73944341
{
"hash" : "000000000055b9d4876d376097e81ce34506cf148d28b94af13dda0c73944341",
"confirmations" : 22,
"size" : 256,
"height" : 3403,
"version" : 1,
We are on correct fork
{
"hash" : "000000000055b9d4876d376097e81ce34506cf148d28b94af13dda0c73944341",
"confirmations" : 22,
"size" : 256,
"height" : 3403,
"version" : 1,
We are on correct fork
Thumbs up! Thanks!
Jump to: