I'm now showing block 1739 but the 4.7xx LTS remains unconfirmed.
Why am I not seeing 20 LTS ?
Topic: LottoShares - Dice 0% Edge - 80LTS Airdrop to all DOGE owners - page 29. (Read 62741 times)
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)
I'll offer a 20LTS bounty to whoever mines it (I'll send to the subsidy address in the mined block)
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?
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
With latest wallet version and after reindex now im on 1750. Is this the correct one?
No, it's notmake 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
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: sorry, but I also was on a wrong fork again, synced to the correct one now!
With latest wallet version and after reindex now im on 1750. Is this the correct one?
No, it's notmake 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
With latest wallet version and after reindex now im on 1750. Is this the correct one?
No, it's notmake 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
Try running this command in the debug panel -
getblockhash 1737
it should read
8db3fe16e36ac6dbd0b013a45f7819b9623f7f1f2579bac05e750b43db2ee986
getblockhash 1737
it should read
8db3fe16e36ac6dbd0b013a45f7819b9623f7f1f2579bac05e750b43db2ee986
With latest wallet version and after reindex now im on 1750. Is this the correct one?
78.46.32.25:4132
thanks mate
78.46.32.25:4132
someone on right fork please share some node
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.
something is not right here
i've updated my wallet from this link
https://github.com/LottoShares/lottoshares/releases/tag/1.0.0
removed the old blockchain and synced again
now synced but it's on block 1749
lottoshares.42tx.com shows me 1736 as current block
mind to tell me what is going on?
i've updated my wallet from this link
https://github.com/LottoShares/lottoshares/releases/tag/1.0.0
removed the old blockchain and synced again
now synced but it's on block 1749
lottoshares.42tx.com shows me 1736 as current block
mind to tell me what is going on?
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
similiar to lottocoin??
I was update the new wallte
and mining it
now my black at 1791
but in the http://lottoshares.42tx.com/ not update
maybe you need check http://lottoshares.42tx.com/
my node ip is:
addnode=211.155.92.230
please sync
thanks very much!
and mining it
now my black at 1791
but in the http://lottoshares.42tx.com/ not update
maybe you need check http://lottoshares.42tx.com/
my node ip is:
addnode=211.155.92.230
please sync
thanks very much!
I'm not fork
Quote
./lottosharesd getblockhash 1736
afaf6d86486d0d8be2f3a87601f943a239a2ab22d83488147ae8d2bc3588e5f2
afaf6d86486d0d8be2f3a87601f943a239a2ab22d83488147ae8d2bc3588e5f2
I was update the new wallte
and mining it
now my black at 1791
but in the http://lottoshares.42tx.com/ not update
maybe you need check http://lottoshares.42tx.com/
my node ip is:
addnode=211.155.92.230
please sync
thanks very much!
and mining it
now my black at 1791
but in the http://lottoshares.42tx.com/ not update
maybe you need check http://lottoshares.42tx.com/
my node ip is:
addnode=211.155.92.230
please sync
thanks very much!
How do you re-index ?
And whats the deal with my unconfirmed 4.72595184 LTS ?
And whats the deal with my unconfirmed 4.72595184 LTS ?
something is not right here
i've updated my wallet from this link
https://github.com/LottoShares/lottoshares/releases/tag/1.0.0
removed the old blockchain and synced again
now synced but it's on block 1749
lottoshares.42tx.com shows me 1736 as current block
mind to tell me what is going on?
i've updated my wallet from this link
https://github.com/LottoShares/lottoshares/releases/tag/1.0.0
removed the old blockchain and synced again
now synced but it's on block 1749
lottoshares.42tx.com shows me 1736 as current block
mind to tell me what is going on?
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.
Jump to: