[ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 130.

maxpower

sr. member

Activity: 456

Merit: 250

Quote from: slimcoin on June 08, 2014, 08:56:51 AM

Mandatory Client Upgrade

The block chain fork has been fixed along with some other Proof of Burn block discrepancies.
Update the wallet now to get on the correct block chain fork.
You must update the wallet before block 10500 for Proof of Burn block discrepancy fixes.

Source Code: https://github.com/slimcoin/slimcoin
Binaries: https://github.com/slimcoin/slicmoin-executable

After you update the wallet, add the addnodes found on the OP page. Delete both blkindex.dat and blk0001.dat. Start the wallet up the first time with the -rescan option.

Updated my Mac build with latest code: https://www.dropbox.com/s/b5irhas4xqvh2pb/Slimcoin-Qt-0.3.0.0-Mac.zip

sandor111

hero member

Activity: 616

Merit: 500

Quote from: slimcoin on June 08, 2014, 08:56:51 AM

Mandatory Client Upgrade

The block chain fork has been fixed along with some other Proof of Burn block discrepancies.
Update the wallet now to get on the correct block chain fork.
You must update the wallet before block 10500 for Proof of Burn block discrepancy fixes.

Source Code: https://github.com/slimcoin/slimcoin
Binaries: https://github.com/slimcoin/slicmoin-executable

After you update the wallet, add the addnodes found on the OP page. Delete both blkindex.dat and blk0001.dat. Start the wallet up the first time with the -rescan option.

Quoting for reference

Compiling the wallet now, the pool will have some downtime while I update it.

BTW, I'm adding .1BTC to the rpcthreads bounty.
So total .25BTC if someone implements that.

rfcdejong

hero member

Activity: 798

Merit: 500

i noticed it Wink

gjhiggins

legendary

Activity: 2254

Merit: 1290

Quote from: rfcdejong on June 08, 2014, 07:32:36 AM

I have done a pull request with the checkpoint for the longest chain
https://github.com/rfcdejong/slimcoin

Good call, Raymond.

The compiler warns that uint's aint big enough, I made mine uint256s.

Code:

static MapCheckpoints mapCheckpoints =
  boost::assign::map_list_of
  ( 0,      hashGenesisBlockOfficial )
  ( 9012,   uint256("0x00000006b2c364c71c279977abc8adf528d25263fb3b4fa623a309745d9f6246"))
  ( 9013,   uint256("0x000000064ce948cdba2c2223dd75c3677847a00daded6be78a097db82d616eee"))
;

wfm. I successfully managed to restrain myself from submitting a PR to your PR.

Cheers,

Graham

slimcoin

full member

Activity: 182

Merit: 100

Mandatory Client Upgrade

The block chain fork has been fixed along with some other Proof of Burn block discrepancies.
Update the wallet now to get on the correct block chain fork.
You must update the wallet before block 10500 for Proof of Burn block discrepancy fixes.

Source Code: https://github.com/slimcoin/slimcoin
Binaries: https://github.com/slimcoin/slicmoin-executable

After you update the wallet, add the addnodes found on the OP page. Delete both blkindex.dat and blk0001.dat. Start the wallet up the first time with the -rescan option.

rfcdejong

hero member

Activity: 798

Merit: 500

mine syncs good, but my 18 burnt coins are gone in that wallet past block ~4000...

primer-

legendary

Activity: 1092

Merit: 1000

Quote from: sandor111 on June 08, 2014, 08:32:10 AM

Quote from: mumus on June 08, 2014, 08:25:31 AM

Quote from: primer- on June 08, 2014, 08:23:14 AM

I cant get it to sync with the other fork, i keep getting :
getblockhash 9013
7d9282cd681c9d93b7791aa0c1072002c55066acb9431d939a33e091114d2625

Try slimcoind -connect=114.34.15.168 with a clean data folder

Go to data folder and do "rm -rf !(slimcoin.conf|wallet.dat)", then restart the wallet with that node.

I have, the node list above still connects to the other fork. Let me try to force the node via connect= ...

sandor111

hero member

Activity: 616

Merit: 500

Quote from: mumus on June 08, 2014, 08:25:31 AM

Quote from: primer- on June 08, 2014, 08:23:14 AM

I cant get it to sync with the other fork, i keep getting :
getblockhash 9013
7d9282cd681c9d93b7791aa0c1072002c55066acb9431d939a33e091114d2625

Try slimcoind -connect=114.34.15.168 with a clean data folder

Go to data folder and do "rm -rf !(slimcoin.conf|wallet.dat)", then restart the wallet with that node.

mumus

sr. member

Activity: 291

Merit: 250

Quote from: primer- on June 08, 2014, 08:23:14 AM

I cant get it to sync with the other fork, i keep getting :
getblockhash 9013
7d9282cd681c9d93b7791aa0c1072002c55066acb9431d939a33e091114d2625

Try slimcoind -connect=114.34.15.168 with a clean data folder

primer-

legendary

Activity: 1092

Merit: 1000

I cant get it to sync with the other fork, i keep getting :
getblockhash 9013
7d9282cd681c9d93b7791aa0c1072002c55066acb9431d939a33e091114d2625

primer-

legendary

Activity: 1092

Merit: 1000

Quote from: rfcdejong on June 08, 2014, 07:59:31 AM

Quote from: rfcdejong on June 08, 2014, 07:53:34 AM

then perhaps clone from my fork.. or use the addnodes

but still, i did put my wrong wallet on the other fork, and my burned coins are 'gone', or at least not visible... ohoh

seems to be working by just setting the correct nodes and deleting the blockchain blk0001.dat and blkindex.dat, syncing quickly

Delete addr.dat as well as old nodes are stored there.

rfcdejong

hero member

Activity: 798

Merit: 500

Quote from: rfcdejong on June 08, 2014, 07:53:34 AM

then perhaps clone from my fork.. or use the addnodes

but still, i did put my wrong wallet on the other fork, and my burned coins are 'gone', or at least not visible... ohoh

seems to be working by just setting the correct nodes and deleting the blockchain blk0001.dat and blkindex.dat, syncing quickly

rfcdejong

hero member

Activity: 798

Merit: 500

then perhaps clone from my fork.. or use the addnodes

but still, i did put my wrong wallet on the other fork, and my burned coins are 'gone', or at least not visible... ohoh

primer-

legendary

Activity: 1092

Merit: 1000

Quote from: sandor111 on June 08, 2014, 07:48:44 AM

Quote from: rfcdejong on June 08, 2014, 07:32:36 AM

I have done a pull request with the checkpoint for the longest chain, it is up to slimcoin dev to accept it or not

https://github.com/rfcdejong/slimcoin

ps: best would be not to withdraw or send coins until a fork is choosen

Thank you, let's wait on the dev's answer.

"Dev" wont be around anytime soon, he logs in at midnight CET time, so 8-9 hours from now.

sandor111

hero member

Activity: 616

Merit: 500

Quote from: rfcdejong on June 08, 2014, 07:32:36 AM

I have done a pull request with the checkpoint for the longest chain, it is up to slimcoin dev to accept it or not

https://github.com/rfcdejong/slimcoin

ps: best would be not to withdraw or send coins until a fork is choosen

Thank you, let's wait on the dev's answer.

rfcdejong

hero member

Activity: 798

Merit: 500

I have done a pull request with the checkpoint for the longest chain, it is up to slimcoin dev to accept it or not

https://github.com/rfcdejong/slimcoin

ps: best would be not to withdraw or send coins until a fork is choosen

sandor111

hero member

Activity: 616

Merit: 500

Use only these nodes to get on the right fork:

addnode=114.34.15.168
addnode=63.141.232.170
addnode=77.237.251.163
addnode=84.198.182.60

sandor111

hero member

Activity: 616

Merit: 500

Quote from: rfcdejong on June 08, 2014, 07:17:49 AM

The forked happened on block 9013
a fix would be by setting a checkpoint for block 9013 at 000000064ce948cdba2c2223dd75c3677847a00daded6be78a097db82d616eee

shortest chain
getblockhash 9013
7d9282cd681c9d93b7791aa0c1072002c55066acb9431d939a33e091114d2625

getblockhash 9012
00000006b2c364c71c279977abc8adf528d25263fb3b4fa623a309745d9f6246

longest chain
getblockhash 9013
000000064ce948cdba2c2223dd75c3677847a00daded6be78a097db82d616eee

getblockhash 9012
00000006b2c364c71c279977abc8adf528d25263fb3b4fa623a309745d9f6246

I have notified the developer

rfcdejong

hero member

Activity: 798

Merit: 500

The forked happened on block 9013
a fix would be by setting a checkpoint for block 9013 at 000000064ce948cdba2c2223dd75c3677847a00daded6be78a097db82d616eee

shortest chain
getblockhash 9013
7d9282cd681c9d93b7791aa0c1072002c55066acb9431d939a33e091114d2625

getblockhash 9012
00000006b2c364c71c279977abc8adf528d25263fb3b4fa623a309745d9f6246

longest chain
getblockhash 9013
000000064ce948cdba2c2223dd75c3677847a00daded6be78a097db82d616eee

getblockhash 9012
00000006b2c364c71c279977abc8adf528d25263fb3b4fa623a309745d9f6246

primer-

legendary

Activity: 1092

Merit: 1000

I am waiting to see which chain gets chosen by bter...

Topic: [ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 130. (Read 284956 times)