No, I had another computer that was not fully synced yet when the reorganization happened and cut it off. And all block upto block 43685 was left was there.
Topic: [ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 43. (Read 284959 times)
July 20, 2014, 09:38:11 AM
I have a running wallet on a long fork but all recent transactions are marked with a question mark. Does it mean all these blocks were deleted from the database and we cannot get them back?
July 20, 2014, 09:35:44 AM
If you are back at block 35587 or so, there was a fork in the blockchain. The upcoming update will have the hard checkpoints for that fork.
You can get back on the correct blockchain by: deleting blkindex.dat, blk0001.dat, and the addr.dat and starting the slimcoin client with the following flags: "-maxconnections=1 -connect=76.127.202.17"
To see if you are on the correct fork, the rpc command "getblockhash 35587" should return 0x07450307a456afcbc62d8414913a8b4497f4dc13629337b7db5658aa52877155
can't sync now.You can get back on the correct blockchain by: deleting blkindex.dat, blk0001.dat, and the addr.dat and starting the slimcoin client with the following flags: "-maxconnections=1 -connect=76.127.202.17"
To see if you are on the correct fork, the rpc command "getblockhash 35587" should return 0x07450307a456afcbc62d8414913a8b4497f4dc13629337b7db5658aa52877155
July 20, 2014, 08:49:29 AM
hi,
when i went to bed Yesterday everything with my Client was ok, now he rolled back a lot of Transactions and they are unconfirmed. Unconfirmed Transaction start 11.07.2014 around 2:51 GMT+1. Does anybody else had such a Problem? How can i Fix that?
Could it be possible that we have a Fork issue again, or is it only my Client out of sync?
when i went to bed Yesterday everything with my Client was ok, now he rolled back a lot of Transactions and they are unconfirmed. Unconfirmed Transaction start 11.07.2014 around 2:51 GMT+1. Does anybody else had such a Problem? How can i Fix that?
Could it be possible that we have a Fork issue again, or is it only my Client out of sync?
Happened to me too... seems it is blockchain cleanup time
July 20, 2014, 08:12:35 AM
No, I had another computer that was not fully synced yet when the reorganization happened and cut it off. And all block upto block 43685 was left was there.
July 20, 2014, 07:27:37 AM
How the data was lost? Had the wallet deleted recent blocks immediately as the fork occurred?
The issue was not the block propagation at all (if that even is an issue). The issue was with the checkpoint node being off-line and hitching onto an incorrect fork, where then it forced all other nodes to go to that fork since it is the checkpoint node. That incorrect fork was not caused by block propagation delays either, it was caused by the creation of PoS blocks. Since it has been off-line, the staked coins on it accumulated coinage. When the node came back on-line, it created a few PoS blocks immediately, before it synced up, causing a fork. Since it was the checkpoint node, the network was forced to that chain.
Up to block 43685 was all I could salvage.
Up to block 43685 was all I could salvage.
July 20, 2014, 07:04:59 AM
The issue was not the block propagation at all (if that even is an issue). The issue was with the checkpoint node being off-line and hitching onto an incorrect fork, where then it forced all other nodes to go to that fork since it is the checkpoint node. Up to block 43685 was all I could salvage.
The fact that you are not even aware of the block propagation issue (wallet getting stuck every hour or so) shows how incompetent you are.
Let this coins rest in peace and die now. Lets hope someone with more experience forks it soon.
EDIT : You cant even make it work with multiple centralized checkpoints, remove them and it will crumble into a million forks. Is this a high school project for you ? Get lost incompetent dev!
July 20, 2014, 07:02:04 AM
The issue was not the block propagation at all (if that even is an issue). The issue was with the checkpoint node being off-line and hitching onto an incorrect fork, where then it forced all other nodes to go to that fork since it is the checkpoint node. That incorrect fork was not caused by block propagation delays either, it was caused by the creation of PoS blocks. Since it has been off-line, the staked coins on it accumulated coinage. When the node came back on-line, it created a few PoS blocks immediately, before it synced up, causing a fork. Since it was the checkpoint node, the network was forced to that chain.
Up to block 43685 was all I could salvage.
Up to block 43685 was all I could salvage.
July 20, 2014, 06:57:10 AM
If anyone still believes current PoB is genious - its not. You will never reach ROI if you burn more than 3-4k.
I have burnt 15k and i only get 4-10 PoB blocks /day. I'd need 150 days for ROI if the number of burnt coins in the network stayed the same (not possible).
On top of being incompetent developer is also very bad at math. Just look at his total coin supply estimate on the first page. 250 mil. HA!
I have burnt 15k and i only get 4-10 PoB blocks /day. I'd need 150 days for ROI if the number of burnt coins in the network stayed the same (not possible).
On top of being incompetent developer is also very bad at math. Just look at his total coin supply estimate on the first page. 250 mil. HA!
July 20, 2014, 06:51:46 AM
I synced from the 76.127.202.17 and now on 43710 block, getblockhash 35587 is correct. We was on 44449 block before the fork! You can see it on http://www.blockexperts.com/slm right now. Everything was fine till that height. Now last 15-20 hours are lost. I think it's not right. Don't you have data to restore?
If you are back at block 35587 or so, there was a fork in the blockchain. The upcoming update will have the hard checkpoints for that fork.
You can get back on the correct blockchain by: deleting blkindex.dat, blk0001.dat, and the addr.dat and starting the slimcoin client with the following flags: "-maxconnections=1 -connect=76.127.202.17"
To see if you are on the correct fork, the rpc command "getblockhash 35587" should return 0x07450307a456afcbc62d8414913a8b4497f4dc13629337b7db5658aa52877155
You can get back on the correct blockchain by: deleting blkindex.dat, blk0001.dat, and the addr.dat and starting the slimcoin client with the following flags: "-maxconnections=1 -connect=76.127.202.17"
To see if you are on the correct fork, the rpc command "getblockhash 35587" should return 0x07450307a456afcbc62d8414913a8b4497f4dc13629337b7db5658aa52877155
July 20, 2014, 06:25:45 AM
The fork happened because of the BLOCK PROPAGATION ISSUE i pointed at many many times.
Fucking developer is a retard. I will not be wasting my time with this shitcoin any more.
Fucking developer is a retard. I will not be wasting my time with this shitcoin any more.
How many shitcoins did you kill btw, primer- ? You with your CPU farm instamined almost every new coin and dumped it on the market, then you insult everyone who makes you bank ?
I tried to point the dev in the right direction but he is just too stupid. He posted yesterday he was workiing on a FAQ instead of addressing serious issues with the coin. What an idiot.
If you have a block propagation issue it will most definitely lead to a fork. crypto 1-0-1.
July 20, 2014, 06:24:57 AM
Thanks for pointing this out. I will add the folowing change when I next update the client. Try editing main.h. Search for the lines where CHAINCHECKS_SWITCH_TIME and POB_POS_TARGET_SWITCH_TIME are defined. The number they correspond to, add a ULL to the end, no space, ex: 2403654400ULL
Save and recompile.
Tell me if that works.
Had no luck. The warnings are gone when I add ULL to the numbers, but compiler stucks and crashes when compiling main.cpp.
PS: The crash seems to be a RAM issue, so slimcoin has nothing to do with it. Sorry.
PS2: Got it to work now.
July 20, 2014, 06:23:07 AM
The fork happened because of the BLOCK PROPAGATION ISSUE i pointed at many many times.
Fucking developer is a retard. I will not be wasting my time with this shitcoin any more.
Fucking developer is a retard. I will not be wasting my time with this shitcoin any more.
How many shitcoins did you kill btw, primer- ? You with your CPU farm instamined almost every new coin and dumped it on the market, then you insult everyone who makes you bank ?
July 20, 2014, 06:14:57 AM
The fork happened because of the BLOCK PROPAGATION ISSUE i pointed at many many times.
Fucking developer is a retard. I will not be wasting my time with this shitcoin any more.
Fucking developer is a retard. I will not be wasting my time with this shitcoin any more.
July 20, 2014, 05:55:09 AM
If you are back at block 35587 or so, there was a fork in the blockchain. The upcoming update will have the hard checkpoints for that fork.
You can get back on the correct blockchain by: deleting blkindex.dat, blk0001.dat, and the addr.dat and starting the slimcoin client with the following flags: "-maxconnections=1 -connect=76.127.202.17"
To see if you are on the correct fork, the rpc command "getblockhash 35587" should return 0x07450307a456afcbc62d8414913a8b4497f4dc13629337b7db5658aa52877155
You can get back on the correct blockchain by: deleting blkindex.dat, blk0001.dat, and the addr.dat and starting the slimcoin client with the following flags: "-maxconnections=1 -connect=76.127.202.17"
To see if you are on the correct fork, the rpc command "getblockhash 35587" should return 0x07450307a456afcbc62d8414913a8b4497f4dc13629337b7db5658aa52877155
wow, all my 3 wallets on the wrong fork..
July 20, 2014, 05:05:25 AM
If you are back at block 35587 or so, there was a fork in the blockchain. The upcoming update will have the hard checkpoints for that fork.
You can get back on the correct blockchain by: deleting blkindex.dat, blk0001.dat, and the addr.dat and starting the slimcoin client with the following flags: "-maxconnections=1 -connect=76.127.202.17"
To see if you are on the correct fork, the rpc command "getblockhash 35587" should return 0x07450307a456afcbc62d8414913a8b4497f4dc13629337b7db5658aa52877155
You can get back on the correct blockchain by: deleting blkindex.dat, blk0001.dat, and the addr.dat and starting the slimcoin client with the following flags: "-maxconnections=1 -connect=76.127.202.17"
To see if you are on the correct fork, the rpc command "getblockhash 35587" should return 0x07450307a456afcbc62d8414913a8b4497f4dc13629337b7db5658aa52877155
July 20, 2014, 03:57:34 AM
appreciate that, looks totaly wired atm.
July 20, 2014, 03:39:54 AM
I am currently working on getting the blockchain where it was before.
July 20, 2014, 03:39:08 AM
current number of block 35825?
?
?It's short blockchain.
July 20, 2014, 03:29:06 AM
current number of block 35825??
? July 20, 2014, 02:37:11 AM
The linux binaries are not perfect yet. I am working on getting statically linked 32 and 64 bit binaries. Currently, they are dynamically linked for 64 bit. It is best for you to just download all of the libraries and compile it yourself. Compiling on linux is not hard at all, look at build-unix.txt in the doc/ directory.
Thanks. I tried to compile slimcoind now (using the latest code on git), but compiler (g++ 4.8.2) gets stuck (simply stops to compile) after the following lines:
Code:
main.cpp:994:3: warning: this decimal constant is unsigned only in ISO C90 [enabled by default]
int64 nRewardCoinYear = nTime > POB_POS_TARGET_SWITCH_TIME ? (10 * CENT) : CENT; // creation amount per coin-year
^
main.cpp:1030:3: warning: this decimal constant is unsigned only in ISO C90 [enabled by default]
if(fTestNet || nTime > POB_POS_TARGET_SWITCH_TIME)
^
main.cpp:1125:3: warning: this decimal constant is unsigned only in ISO C90 [enabled by default]
if(fTestNet || pindexLast->nTime > POB_POS_TARGET_SWITCH_TIME)
^
main.cpp:2380:3: warning: this decimal constant is unsigned only in ISO C90 [enabled by default]
if(fTestNet || GetBlockTime() > CHAINCHECKS_SWITCH_TIME)
Unfortunately there is no version marked as "stable" which I could try.
Thanks for pointing this out. I will add the folowing change when I next update the client. Try editing main.h. Search for the lines where CHAINCHECKS_SWITCH_TIME and POB_POS_TARGET_SWITCH_TIME are defined. The number they correspond to, add a ULL to the end, no space, ex: 2403654400ULL
Save and recompile.
Tell me if that works.
Jump to: