Code:
{
"blocks" : 3003,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : {
"proof-of-work" : 7.50529447,
"proof-of-stake" : 1696.39477649,
"search-interval" : 16
},
"blockvalue" : 1973167540,
"netmhashps" : 805.87485770,
"netstakeweight" : 2504185177500.73095703,
"errors" : "",
"pooledtx" : 0,
"stakeweight" : {
"minimum" : 0,
"maximum" : 0,
"combined" : 0
},
"testnet" : false
}
"blocks" : 3003,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : {
"proof-of-work" : 7.50529447,
"proof-of-stake" : 1696.39477649,
"search-interval" : 16
},
"blockvalue" : 1973167540,
"netmhashps" : 805.87485770,
"netstakeweight" : 2504185177500.73095703,
"errors" : "",
"pooledtx" : 0,
"stakeweight" : {
"minimum" : 0,
"maximum" : 0,
"combined" : 0
},
"testnet" : false
}
heh, lets see where this finish
i am gonna stake on this chain
the dev should sync the seednodes to this chain too
it is the longest one, so it is the correct chain.
also i am not the only one on this chain.
longest does not automatically imply the correct one
diff is much higher on the the other chain, and we're also not alone here
if you want suprnova to be the right chain:
you need to give the dev the blockhash for block 2800 and he puts that in the source as a checkpoint.
and then he updates and resync the checkpointing server and then he updates and resyncs the other nodes. and then tells everyone to update and resync.
and when he resyncs he puts your addnode in his conf
he can also change the protocol version