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

[NaXxow]

If the slimcoin dev is around it would be advisable to urgently release a new wallet with checkpoints to solve this forking problem. The 2 chains are still alive and with similar hashing power on both of them. One party will be very upset soon. I have also 2 new blocks on just one of the chains.

+1
That's important for the future of SLIM.

[1714531483]

1714531483

[1714531483]

1714531483

[1714531483]

1714531483

[1714531483]

1714531483

[NaXxow]

We sure to add "addnode=63.141.232.170" to your slimcoin.conf, this is the pool node!

One guy with 1mh/s in pool? That's crazy.

[jadefalke]

not again ;(

[mbk]

Second fork is now at 9497 vs 9485 block but BTER is on 9485 fork! I've got withdraw confirmed on that fork. We should stay with this fork otherwise BTER trades could be reversed. It shouldn't happen! Guys, check it yourself and make the decision.

[mumus]

Second fork is now at 9497 vs 9485 block but BTER is on 9485 fork! I've got withdraw confirmed on that fork. We should stay with this fork otherwise BTER trades could be reversed. It shouldn't happen! Guys, check it yourself and make the decision.

I've also made a test with BTER. I sent some small amount of coins from 2 different wallet daemons that were connected to the 2 different chain. The wallet.dat was the same on both wallet daemons. Interestingly both deposits arrived to BTER and after a while on both wallet I could see all the transactions. Based on my current knowledge I can't explain this behavior.
So based on this deposit test I couldn't determine on which chain BTER is right now.

[rfcdejong]

getblockhash 9504

00000002cc86d041ea9546f49d5fa627afc4a1361f22f45237dfb962d54d24f0


14:07:36

{
"hash" : "00000002cc86d041ea9546f49d5fa627afc4a1361f22f45237dfb962d54d24f0",
"size" : 414,
"height" : 9504,
"version" : 1,
"merkleroot" : "ff58251dbdd0aac4806453831e04a887e7c1ca2c238a9eb5f0551b58d60d4077",
"time" : "2014-06-08 12:05:28 UTC",
"nonce" : 178968645,
"bits" : "1d16eede",
"difficulty" : 0.04360448,
"mint" : 13.67000000,
"previousblockhash" : "0000000ae239d00e796de03bc4b036475a531c15d7244e625aac9fc49e06d995",
"nextblockhash" : "0000000730cf2135b4dadf63564f4989a1c95b9d4e1125075ab9a283590a9fe1",
"flags" : "proof-of-work",
"proofhash" : "00000002cc86d041ea9546f49d5fa627afc4a1361f22f45237dfb962d54d24f0",
"entropybit" : 0,
"modifier" : "1ece7e32df6efbd1",
"modifierchecksum" : "bd9ffab3",
"tx" : [
"ff58251dbdd0aac4806453831e04a887e7c1ca2c238a9eb5f0551b58d60d4077"
]
}

[sandor111]

Guys, please move to the fork with the longest chain, or you will cry!

[rfcdejong]

hmz seems my other wallet is on the other fork, only 9500 blocks

wallet shortest chain

getblockhash 9500
0000000e19c90533fa581bba7864a0a5d7ef7cc5e183ebe0cdb0cd0975968f1a


wallet longest chain

getblockhash 9500
000000044021e8af4fdb1cb8c5a27a2cd8339c3e1749bfb888e65ce5f9eca4c8

[mumus]

hmz seems my other wallet is on the other fork, only 9500 blocks

wallet shortest chain

getblockhash 9500
0000000e19c90533fa581bba7864a0a5d7ef7cc5e183ebe0cdb0cd0975968f1a


wallet longest chain

getblockhash 9500
000000044021e8af4fdb1cb8c5a27a2cd8339c3e1749bfb888e65ce5f9eca4c8

These are the nodes that I'm connected with that represents the so called longest chain  (9500 - 000000044021e8af4fdb1cb8c5a27a2cd8339c3e1749bfb888e65ce5f9eca4c8)

114.34.15.168:41682
63.141.232.170:41682 - Sandor's pool
50.116.56.210:41682
108.7.224.149:41682
85.25.195.74:41682 
72.252.176.12:41682
213.82.213.152:41682
144.76.142.47:41682

[primer-]

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

[rfcdejong]

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

[sandor111]

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

[sandor111]

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

[rfcdejong]

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]

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.

[primer-]

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.

[rfcdejong]

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

[rfcdejong]

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

[primer-]

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.

[primer-]

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