mbk
|
|
July 20, 2014, 11: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
|
|
|
|
primer-
Legendary
Offline
Activity: 1092
Merit: 1000
|
|
July 20, 2014, 11: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!
|
|
|
|
slimcoin (OP)
|
|
July 20, 2014, 12:02:04 PM |
|
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.
|
-Much Donate BTC-1D5pnma7E1CP6cquHujycVy79EyXJ3eY
|
|
|
primer-
Legendary
Offline
Activity: 1092
Merit: 1000
|
|
July 20, 2014, 12:04:59 PM |
|
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!
|
|
|
|
mbk
|
|
July 20, 2014, 12:27:37 PM |
|
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.
|
|
|
|
slimcoin (OP)
|
|
July 20, 2014, 01:12:35 PM |
|
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.
|
-Much Donate BTC-1D5pnma7E1CP6cquHujycVy79EyXJ3eY
|
|
|
chiguireitor
Legendary
Offline
Activity: 872
Merit: 1010
Coins, Games & Miners
|
|
July 20, 2014, 01:49:29 PM |
|
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?
Happened to me too... seems it is blockchain cleanup time
|
|
|
|
yang5034
|
|
July 20, 2014, 02:35:44 PM |
|
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.
|
|
|
|
mbk
|
|
July 20, 2014, 02:38:11 PM |
|
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? 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.
|
|
|
|
jadefalke
Legendary
Offline
Activity: 1456
Merit: 1014
|
|
July 20, 2014, 03:10:48 PM |
|
can't sync even with the connect=1 etc.
|
|
|
|
slimcoin (OP)
|
|
July 20, 2014, 03:32:50 PM |
|
If you cannot sync, try using -connect=212.75.31.155:41684 instead. Also make sure you deleted you blkindex.dat, blk0001.dat, and addr.dat files.
|
-Much Donate BTC-1D5pnma7E1CP6cquHujycVy79EyXJ3eY
|
|
|
idad01
|
|
July 20, 2014, 03:35:15 PM |
|
 getblockhash 43745  0000001f76a5fdd273fbb83562c3430c465214eb6fd1697345de453190731240
Correct?
|
|
|
|
a123
Member
Offline
Activity: 98
Merit: 10
|
|
July 20, 2014, 03:39:09 PM |
|
 getblockhash 43745  0000001f76a5fdd273fbb83562c3430c465214eb6fd1697345de453190731240
Correct?
im on the same fork as you, and this is the same as the one on http://www.blockexperts.com/slm but the difficulty (0.0235) and network hash (64420h/s) is completely off. any idea which is the main fork? I'm using the settings "maxconnections=1 -connect=76.127.202.17"
|
|
|
|
primer-
Legendary
Offline
Activity: 1092
Merit: 1000
|
|
July 20, 2014, 04:28:35 PM |
|
getblockhash 43745  0000001f76a5fdd273fbb83562c3430c465214eb6fd1697345de453190731240 This is not the correct fork ?? ) Such fail. Dev go jump of a bridge. EDIT: Dev, is this your IP ? 212.75.31.155 ? This IP belongs to a cable provider, a Bulgarian (third world country populated by gypsies and thiefs) cable provider. No VPN/VPS/Dedi servers use this IP range, only home cable subscribers. tl;dr Slimcoin dev. is Bulgarian.
|
|
|
|
asdlolciterquit
|
|
July 20, 2014, 04:42:52 PM |
|
How many coins i mine in 24 hours?
|
|
|
|
slimcoin (OP)
|
|
July 20, 2014, 04:53:33 PM |
|
 getblockhash 43745  0000001f76a5fdd273fbb83562c3430c465214eb6fd1697345de453190731240
Correct?
Yes, that is correct.
|
-Much Donate BTC-1D5pnma7E1CP6cquHujycVy79EyXJ3eY
|
|
|
rfcdejong
|
|
July 20, 2014, 08:12:28 PM |
|
getblockhash 43745  0000001f76a5fdd273fbb83562c3430c465214eb6fd1697345de453190731240 This is not the correct fork ?? ) Such fail. Dev go jump of a bridge. EDIT: Dev, is this your IP ? 212.75.31.155 ? This IP belongs to a cable provider, a Bulgarian (third world country populated by gypsies and thiefs) cable provider. No VPN/VPS/Dedi servers use this IP range, only home cable subscribers. tl;dr Slimcoin dev. is Bulgarian. Primer, could you stop attackking slimcoin dev that much You are in this coin, don't attack the dev or the coin you mine, unless you want the value to go down and buy up more.. but when do you turn?
|
|
|
|
primer-
Legendary
Offline
Activity: 1092
Merit: 1000
|
|
July 20, 2014, 08:19:16 PM |
|
Primer, could you stop attackking slimcoin dev that much You are in this coin, don't attack the dev or the coin you mine, unless you want the value to go down and buy up more.. but when do you turn? I have not posted for a month and look where it got us. Everything is broken. PoB ROI is unachieveable. PoS/PoW is broken. Block propagation broken. GUI icons and transactions broken. Coin is centralized. A hacker could destroy the blockchain if he gains access to devs checkpoint node. On top of all that, retarded dev wants to write a FAQ for beginners. Fucking retard.
|
|
|
|
freet0pian
|
|
July 20, 2014, 10:58:33 PM |
|
Primer, could you stop attackking slimcoin dev that much You are in this coin, don't attack the dev or the coin you mine, unless you want the value to go down and buy up more.. but when do you turn? I have not posted for a month and look where it got us. Everything is broken. PoB ROI is unachieveable. PoS/PoW is broken. Block propagation broken. GUI icons and transactions broken. Coin is centralized. A hacker could destroy the blockchain if he gains access to devs checkpoint node. On top of all that, retarded dev wants to write a FAQ for beginners. Fucking retard. Sorry, but how old are you? You haven't matured enough yet to stop that childish howling of yours? Hmmm, maybe you have tourette's. If so, you're excused .
|
░▒▓█ welcome to freet0pia █▓▒░
|
|
|
d5000
Legendary
Offline
Activity: 4046
Merit: 7322
Decentralization Maximalist
|
|
July 20, 2014, 10:59:05 PM |
|
It's hard to take you serious, primer-, but this coin is an experimental technology, not a clone. Remember Peercoin? Is now a stable Top-10-crypto, but had similar problems at the start. It took about half a year until a really usable version came out. And a FAQ is not a bad idea, because so dev must not answer the same questions in the thread again and again and can concentrate on bug fixing. I'm new with this coin and still looking around, but I see high potential. Although I'm also a peercoin, Nxt and BTC fanboy
|
|
|
|
|