FreeTrade (OP)
Legendary
Offline
Activity: 1470
Merit: 1030
|
|
July 17, 2014, 04:33:51 PM |
|
Two blocks were generated for 1737. One was checkpointed, but the other had a longer chain . . . . the client should have picked the checkpointed chain, but there was a bug and some clients continued to mine on the longer invalid chain. The updated client should fix this problem and ensure it doesn't re-occur. A re-index should fix your current chain.
|
RepNet is a reputational social network blockchain for uncensored Twitter/Reddit style discussion. 10% Interest On All Balances. 100% Distributed to Users and Developers.
|
|
|
Hippie Tech
aka Amenstop
Legendary
Offline
Activity: 1624
Merit: 1001
All cryptos are FIAT digital currency. Do not use.
|
|
July 17, 2014, 04:40:31 PM |
|
How do you re-index ?
And whats the deal with my unconfirmed 4.72595184 LTS ?
|
|
|
|
|
saymissme
|
|
July 17, 2014, 04:57:03 PM |
|
I'm not fork ./lottosharesd getblockhash 1736 afaf6d86486d0d8be2f3a87601f943a239a2ab22d83488147ae8d2bc3588e5f2
|
|
|
|
JulioCesar
Member
Offline
Activity: 64
Merit: 10
|
|
July 17, 2014, 04:59:33 PM |
|
similiar to lottocoin??
|
1b7150efc4abdc96f11a0b678d974541318a4a7973e0588d4849651551963a7d
|
|
|
ShXnot
|
|
July 17, 2014, 05:00:37 PM |
|
Two blocks were generated for 1737. One was checkpointed, but the other had a longer chain . . . . the client should have picked the checkpointed chain, but there was a bug and some clients continued to mine on the longer invalid chain. The updated client should fix this problem and ensure it doesn't re-occur. A re-index should fix your current chain. brilliant with -reindex now im on 1795 blocks" : 1795, "currentblocksize" : 0, "currentblocktx" : 0, "difficulty" : 2.40023486, "errors" : "", "generate" : false, "genproclimit" : -1, "hashespersec" : 0, "networkhashps" : 13019164, "pooledtx" : 0, "testnet" : false
|
|
|
|
kokojie
Legendary
Offline
Activity: 1806
Merit: 1003
|
|
July 17, 2014, 05:02:23 PM |
|
I have played a ticket on the forked chain, how do I get the lts back? looks like that transaction isn't confirming now that I'm on the right chain.
|
btc: 15sFnThw58hiGHYXyUAasgfauifTEB1ZF6
|
|
|
ShXnot
|
|
July 17, 2014, 05:12:15 PM |
|
someone on right fork please share some node
|
|
|
|
pharesim
|
|
July 17, 2014, 05:15:21 PM Last edit: July 17, 2014, 06:11:06 PM by pharesim |
|
78.46.32.25:4132
|
|
|
|
ShXnot
|
|
July 17, 2014, 05:21:48 PM |
|
78.46.32.25:4132
thanks mate
|
|
|
|
jalmari
|
|
July 17, 2014, 05:37:25 PM |
|
With latest wallet version and after reindex now im on 1750. Is this the correct one?
|
|
|
|
FreeTrade (OP)
Legendary
Offline
Activity: 1470
Merit: 1030
|
|
July 17, 2014, 05:40:14 PM |
|
Try running this command in the debug panel -
getblockhash 1737
it should read
8db3fe16e36ac6dbd0b013a45f7819b9623f7f1f2579bac05e750b43db2ee986
|
RepNet is a reputational social network blockchain for uncensored Twitter/Reddit style discussion. 10% Interest On All Balances. 100% Distributed to Users and Developers.
|
|
|
ShXnot
|
|
July 17, 2014, 05:44:19 PM |
|
With latest wallet version and after reindex now im on 1750. Is this the correct one?
No, it's not make a conf file with above node, remove the old chain and sync again it will stuck on 1736 with out of sync message i think we must wait for 1737 to be solved
|
|
|
|
jalmari
|
|
July 17, 2014, 06:00:31 PM |
|
With latest wallet version and after reindex now im on 1750. Is this the correct one?
No, it's not make a conf file with above node, remove the old chain and sync again it will stuck on 1736 with out of sync message i think we must wait for 1737 to be solved I removed the chain again before reading this and there for I did not add the above node. Anyways, I think that I am now in the right chain. Last block is 1737 with hash 8db3fe16e36ac6dbd0b013a45f7819b9623f7f1f2579bac05e750b43db2ee986
|
|
|
|
pharesim
|
|
July 17, 2014, 06:07:53 PM |
|
ShXnot: sorry, but I also was on a wrong fork again, synced to the correct one now!
|
|
|
|
ShXnot
|
|
July 17, 2014, 06:08:06 PM |
|
With latest wallet version and after reindex now im on 1750. Is this the correct one?
No, it's not make a conf file with above node, remove the old chain and sync again it will stuck on 1736 with out of sync message i think we must wait for 1737 to be solved I removed the chain again before reading this and there for I did not add the above node. Anyways, I think that I am now in the right chain. Last block is 1737 with hash 8db3fe16e36ac6dbd0b013a45f7819b9623f7f1f2579bac05e750b43db2ee986 ok, now i think im on the right fork too but the wallet shows me out of sync message with 12 hours behind also i have the hash same as you for 1737 not sure what to do now btw, i ran it on 2 machines and the result was the same
|
|
|
|
ShXnot
|
|
July 17, 2014, 06:10:30 PM |
|
ShXnot: sorry, but I also was on a wrong fork again, synced to the correct one now!
really? ))) no problem mate im still trying to figure out how to fix it
|
|
|
|
tonyk
|
|
July 17, 2014, 06:25:51 PM |
|
OK, I finally got the correct block hash for block 1737, even though pharesim went offline or maxed out his connections.
Now what? Just wait?
|
|
|
|
FreeTrade (OP)
Legendary
Offline
Activity: 1470
Merit: 1030
|
|
July 17, 2014, 06:27:15 PM |
|
we're still waiting for block 1738 as far as i can see.
I'll offer a 20LTS bounty to whoever mines it (I'll send to the subsidy address in the mined block)
|
RepNet is a reputational social network blockchain for uncensored Twitter/Reddit style discussion. 10% Interest On All Balances. 100% Distributed to Users and Developers.
|
|
|
Hippie Tech
aka Amenstop
Legendary
Offline
Activity: 1624
Merit: 1001
All cryptos are FIAT digital currency. Do not use.
|
|
July 17, 2014, 07:00:45 PM |
|
I'm now showing block 1739 but the 4.7xx LTS remains unconfirmed.
Why am I not seeing 20 LTS ?
|
|
|
|
|