Author

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

sr. member
Activity: 291
Merit: 250
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
hero member
Activity: 798
Merit: 500
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
hero member
Activity: 616
Merit: 500
Guys, please move to the fork with the longest chain, or you will cry!
hero member
Activity: 798
Merit: 500
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"
]
}
sr. member
Activity: 291
Merit: 250
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.
mbk
member
Activity: 106
Merit: 10
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.
legendary
Activity: 1456
Merit: 1014
legendary
Activity: 1085
Merit: 1000
ALT Add: APfc4bykKHxYSVkvzsLdQvmiTXvTgMiCRM
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.
legendary
Activity: 1085
Merit: 1000
ALT Add: APfc4bykKHxYSVkvzsLdQvmiTXvTgMiCRM
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.
hero member
Activity: 616
Merit: 500
We are on the right fork! Come join our pool...
sr. member
Activity: 291
Merit: 250
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.
sr. member
Activity: 511
Merit: 250
Open and Transparent Science Powered By Blockchain
The OP has instructions how to compile Slimminer with Windows but no instructions how to compile with Linux. Any help?

sudo apt-get update
sudo apt-get install libcurl4-openssl-dev libjansson4 autoconf git
git clone https://github.com/slimcoin/slimminer.git
cd slimminer
./autogen.sh
./configure CFLAGS="-O3"
make
make install

Many thanks!
hero member
Activity: 658
Merit: 500
The OP has instructions how to compile Slimminer with Windows but no instructions how to compile with Linux. Any help?

sudo apt-get update
sudo apt-get install libcurl4-openssl-dev libjansson4 autoconf git
git clone https://github.com/slimcoin/slimminer.git
cd slimminer
./autogen.sh
./configure CFLAGS="-O3"
make
make install
sr. member
Activity: 511
Merit: 250
Open and Transparent Science Powered By Blockchain
The OP has instructions how to compile Slimminer with Windows but no instructions how to compile with Linux. Any help?
hero member
Activity: 658
Merit: 500
Still nobody wants to share how to setup a private pool??
Great community...
full member
Activity: 153
Merit: 102
Right now 2 forks are at 9283 and 9250. I've stopped the wallet on 9250 chain, deleted blk* files and addr.dat, added nodes below, restarted and it synced to the 9283 chain. I think everybody on this chain should do it. The difference between chains is more then 30 blocks and 9283 chain has 30% more hashpower.

Nodes:
addnode=63.141.232.170
addnode=144.76.142.47
addnode=144.76.142.49
addnode=94.229.76.122
addnode=185.21.191.189
addnode=85.110.8.131
addnode=96.237.174.192
addnode=60.250.174.75
addnode=198.199.101.230
addnode=192.82.119.85
addnode=107.170.123.185
addnode=95.85.25.57
addnode=222.134.95.70
addnode=54.187.155.212
addnode=54.201.166.212
addnode=192.241.173.228
addnode=119.63.94.173
addnode=181.193.75.66
addnode=144.76.142.47
addnode=144.76.142.49
addnode=76.127.202.17
addnode=96.237.174.192
addnode=125.115.54.166
addnode=76.127.202.17
addnode=96.237.174.192
addnode=107.181.250.216
addnode=107.181.250.217


I did exactly the same 30 min ago on 2 daemons with these nodes from the list and got on the other chain.
I will try now again.
Good
I want to do it
sr. member
Activity: 291
Merit: 250
Right now 2 forks are at 9283 and 9250. I've stopped the wallet on 9250 chain, deleted blk* files and addr.dat, added nodes below, restarted and it synced to the 9283 chain. I think everybody on this chain should do it. The difference between chains is more then 30 blocks and 9283 chain has 30% more hashpower.

Nodes:
addnode=63.141.232.170
addnode=144.76.142.47
addnode=144.76.142.49
addnode=94.229.76.122
addnode=185.21.191.189
addnode=85.110.8.131
addnode=96.237.174.192
addnode=60.250.174.75
addnode=198.199.101.230
addnode=192.82.119.85
addnode=107.170.123.185
addnode=95.85.25.57
addnode=222.134.95.70
addnode=54.187.155.212
addnode=54.201.166.212
addnode=192.241.173.228
addnode=119.63.94.173
addnode=181.193.75.66
addnode=144.76.142.47
addnode=144.76.142.49
addnode=76.127.202.17
addnode=96.237.174.192
addnode=125.115.54.166
addnode=76.127.202.17
addnode=96.237.174.192
addnode=107.181.250.216
addnode=107.181.250.217


I did exactly the same 30 min ago on 2 daemons with these nodes from the list and got on the other chain.
I will try now again.
mbk
member
Activity: 106
Merit: 10
Right now 2 forks are at 9283 and 9250. I've stopped the wallet on 9250 chain, deleted blk* files and addr.dat, added nodes below, restarted and it synced to the 9283 chain. I think everybody on this chain should do it. The difference between chains is more then 30 blocks and 9283 chain has 30% more hashpower.

Nodes:
addnode=63.141.232.170
addnode=144.76.142.47
addnode=144.76.142.49
addnode=94.229.76.122
addnode=185.21.191.189
addnode=85.110.8.131
addnode=96.237.174.192
addnode=60.250.174.75
addnode=198.199.101.230
addnode=192.82.119.85
addnode=107.170.123.185
addnode=95.85.25.57
addnode=222.134.95.70
addnode=54.187.155.212
addnode=54.201.166.212
addnode=192.241.173.228
addnode=119.63.94.173
addnode=181.193.75.66
addnode=144.76.142.47
addnode=144.76.142.49
addnode=76.127.202.17
addnode=96.237.174.192
addnode=125.115.54.166
addnode=76.127.202.17
addnode=96.237.174.192
addnode=107.181.250.216
addnode=107.181.250.217
sr. member
Activity: 291
Merit: 250
Looks like we have a new problem - 2 parallel forks. There are block 9246 at diff 0.04594785 and block 9218 at diff 0.03496026 at the same time in different wallets.

I was in the middle of writing exactly about this. I have all my nodes (4) on 9232 ( 5:49AM GMT) but the pool http://new.hashharder.com/dcrypt/slimcoin is on 9255

sandor111's pool on http://63.141.232.170/ seems to be also on the fork with the lower block height ( 9241 @ 7:13AM GMT) so I suggest that the this is the "dominant" fork. The question is about bter.com.
Can the owner of http://new.hashharder.com/dcrypt/slimcoin check also this issue?
sr. member
Activity: 379
Merit: 250
Looks like we have a new problem - 2 parallel forks. There are block 9246 at diff 0.04594785 and block 9218 at diff 0.03496026 at the same time in different wallets.

I was in the middle of writing exactly about this. I have all my nodes (4) on 9232 ( 5:49AM GMT) but the pool http://new.hashharder.com/dcrypt/slimcoin is on 9255

I just checked and indeed I am also having the same problem being at block 9241 and 9268 at the same time in 2 different wallets. I am still solomining.
Jump to: