599640
"proofhash" : "0000709ddf69c904205bf4e922f49d32775c9ec6d1313d72b34f9f9f4e402b5d"
Topic: [AMBER] X13 POW/POS| 10k AMBER=0,01% SHARES | BUY, HOLD & GET DIVIDENDS in BTC/$ - page 141. (Read 407572 times)
November 29, 2015, 03:17:12 PM
November 29, 2015, 03:16:35 PM
November 29, 2015, 03:15:28 PM
599444
proofhash" : "0011a3c300bfd4721765333d1a79bc21b6ef7f66aff4f60a89d7c17a74cc18e4"
proofhash" : "0011a3c300bfd4721765333d1a79bc21b6ef7f66aff4f60a89d7c17a74cc18e4"
November 29, 2015, 03:11:10 PM
delete database folder too
No more error, but with only using your blk0001.dat, it started syncing right from the beginning. 596,xxx blocks remaining...
What's really weird is that, like TWN said, my 599444 block doesn't match, but 599496 does? How is that possible?
Doesn't match what you guys have:
getblockbynumber 599444
"proofhash" : "0011a3c300bfd4721765333d1a79bc21b6ef7f66aff4f60a89d7c17a74cc18e4"
Later block matches???
getblockbynumber 599496
"proofhash" : "0000000cbc180e9c62c3fce6ab6d3858f8272ca203ce2152aa611f1099b9506d"
matches
You and Dev had a different proofhash for 599444.
"height" : 599444,
"proofhash" : "0000003f72634279704cdfd11620d1f3df4c08f2d9cd617fabe3a7d62f730469"
"proofhash" : "0000003f72634279704cdfd11620d1f3df4c08f2d9cd617fabe3a7d62f730469"
599496 matches though
Agreed, but I don't understand how a previous block can be different?
My wallet as same as yours. My 444 wrong 496 right
November 29, 2015, 02:57:02 PM
delete database folder too
No more error, but with only using your blk0001.dat, it started syncing right from the beginning. 596,xxx blocks remaining...
What's really weird is that, like TWN said, my 599444 block doesn't match, but 599496 does? How is that possible?
Doesn't match what you guys have:
getblockbynumber 599444
"proofhash" : "0011a3c300bfd4721765333d1a79bc21b6ef7f66aff4f60a89d7c17a74cc18e4"
Later block matches???
getblockbynumber 599496
"proofhash" : "0000000cbc180e9c62c3fce6ab6d3858f8272ca203ce2152aa611f1099b9506d"
matches
You and Dev had a different proofhash for 599444.
"height" : 599444,
"proofhash" : "0000003f72634279704cdfd11620d1f3df4c08f2d9cd617fabe3a7d62f730469"
"proofhash" : "0000003f72634279704cdfd11620d1f3df4c08f2d9cd617fabe3a7d62f730469"
599496 matches though
November 29, 2015, 02:55:43 PM
Anyone can give me a node list? Even with the ones mentioned I can't sync.
November 29, 2015, 02:53:18 PM
moved to here: https://bitcointalksearch.org/topic/m.13104425
November 29, 2015, 02:52:27 PM
delete database folder too
No more error, but with only using your blk0001.dat, it started syncing right from the beginning. 596,xxx blocks remaining...
What's really weird is that, like TWN said, my 599444 block doesn't match, but 599496 does? How is that possible?
Doesn't match what you guys have:
getblockbynumber 599444
"proofhash" : "0011a3c300bfd4721765333d1a79bc21b6ef7f66aff4f60a89d7c17a74cc18e4"
Later block matches???
getblockbynumber 599496
"proofhash" : "0000000cbc180e9c62c3fce6ab6d3858f8272ca203ce2152aa611f1099b9506d"
matches
November 29, 2015, 02:51:43 PM
Does anyone know who or what 176.9.165.51 is?
November 29, 2015, 02:48:51 PM
I'm on a wrong chain, had my dad shut down my wallet so I'm not adding to the mayhem. I can talk an old man through the checkblockbynumber process, but I can't send him deleting stuff in my appdata folders. I'll be a few days until I can resync
Yeah, better to shut down than to run wallet on wrong chain.
And later re-sync when all is ok.
November 29, 2015, 02:48:46 PM
Same error, but without the txleveldb directory, the DB.LOG file shortened to:
Unacceptable log file C:\Users\User\AppData\Roaming\AmberCoin\database\log.0000000003: unsupported log version 19
Invalid log file: log.0000000003: Invalid argument
PANIC: Invalid argument
process-private: unable to find environment
delete database folder yet?
November 29, 2015, 02:43:40 PM
I'm on a wrong chain, had my dad shut down my wallet so I'm not adding to the mayhem. I can talk an old man through the checkblockbynumber process, but I can't send him deleting stuff in my appdata folders. I'll be a few days until I can resync
November 29, 2015, 02:42:47 PM
Maybe Dev can find a way to ban all of the old wallet versions? I know other coins that have done this with a new wallet release.
It is regulated by protocolversion check.
protocolversion" : 90001
All wallets with lower protocolversion get banned.
"height" : 599568,
"proofhash" : "000044d81d77ceb6dd34c4d8bd21b8cc41b17570d49ee3f1ee9e8bd6d22204cf",
November 29, 2015, 02:40:37 PM
"height" : 599444,
"proofhash" : "0000003f72634279704cdfd11620d1f3df4c08f2d9cd617fabe3a7d62f730469"
"proofhash" : "0000003f72634279704cdfd11620d1f3df4c08f2d9cd617fabe3a7d62f730469"
This really gets a mess.
Previous post from dev for block 598473 seems to be ok.
getblockbynumber 598473
"proofhash" : "000008d1c209665b7427e9f412a3e991b9d97224c228d4afbdbd4ad4d794b1ef"
the last one for block 599444 is completely wrong again:
getblockbynumber 599444
"proofhash" : "000bfe9a9c34a3649c9f8a93618c18861835c2e7db7ba355bd06fc16afd98961"
What is wrong and why I lose the right chain all the time?
I just resync the wallet from scratch yesterday.
the honest answer... because dev hasn't banned the people on the wrong chain
What do you mean?!?
Any advise how to fix that?
The only real way to fix this, is to have ambercoin01.mooo.com start banning connections.
I agree. But as I have posted I cannot connected to ambercoin01.moo0.com. I get 0 connections and my wallet never syncs. Maybe this node is overloaded and cannot support any more connections or there is some limit on the connections it will accept but whatever it is, if people cannot connect it is not a solution.
Also, you must set listen to 0 (listen=0) in your wallet .conf file or it will listen for other connections and accept them. So you could wind up connecting to a bad node again and then off to a fork. At least I believe that's how it works.
Not "moo0.com" but "mooo.com"!!!
Connections count far from MAX.
Load 20-30%.
That was a typo. I am using mooo. In fact I started my wallet about 30 minutes ago with connect=ambercoin01.mooo.com and listen=0. No connections so far and my wallet is still not syncing.
November 29, 2015, 02:36:21 PM
Maybe Dev can find a way to ban all of the old wallet versions? I know other coins that have done this with a new wallet release.
November 29, 2015, 02:35:15 PM
My current block is 599568? Is that the correct chain?
November 29, 2015, 02:34:45 PM
Thanks. Downloading now. While I was waiting, I tried resyncing again with the correct DB from Nov 27th.
Again, when I caught up to block 599444, I got the same wrong hash again.
"proofhash" : "0011a3c300bfd4721765333d1a79bc21b6ef7f66aff4f60a89d7c17a74cc18e4"
Your DB is about 15% downloaded so far. Once that's finished, I'll try again. I'll get a hash the most current block too.
Again, when I caught up to block 599444, I got the same wrong hash again.
"proofhash" : "0011a3c300bfd4721765333d1a79bc21b6ef7f66aff4f60a89d7c17a74cc18e4"
Your DB is about 15% downloaded so far. Once that's finished, I'll try again. I'll get a hash the most current block too.
How's the download coming?
"height" : 599496,
"proofhash" : "0000000cbc180e9c62c3fce6ab6d3858f8272ca203ce2152aa611f1099b9506d",
221 KB/s - 276 MB of 324 MB, 4 mins left
I'm going to use your CONF file too. (I had renamed mine, so it didn't have one.)
Hmmm...not sure if I can remove something to fix this?
that would be, because I recompiled it with the latest db and ssl... delete the txleveldb
Same error, but without the txleveldb directory, the DB.LOG file shortened to:
Unacceptable log file C:\Users\User\AppData\Roaming\AmberCoin\database\log.0000000003: unsupported log version 19
Invalid log file: log.0000000003: Invalid argument
PANIC: Invalid argument
process-private: unable to find environment
delete database folder too
November 29, 2015, 02:28:13 PM
What is the correct block we should be on?
"height" : 599541,
"proofhash" : "00000000060d1b4b5bd89dc0325b41f953338049e531d3754cb2fa939e19508a"
November 29, 2015, 02:27:11 PM
What is the correct block we should be on?
November 29, 2015, 02:25:31 PM
Thanks. Downloading now. While I was waiting, I tried resyncing again with the correct DB from Nov 27th.
Again, when I caught up to block 599444, I got the same wrong hash again.
"proofhash" : "0011a3c300bfd4721765333d1a79bc21b6ef7f66aff4f60a89d7c17a74cc18e4"
Your DB is about 15% downloaded so far. Once that's finished, I'll try again. I'll get a hash the most current block too.
Again, when I caught up to block 599444, I got the same wrong hash again.
"proofhash" : "0011a3c300bfd4721765333d1a79bc21b6ef7f66aff4f60a89d7c17a74cc18e4"
Your DB is about 15% downloaded so far. Once that's finished, I'll try again. I'll get a hash the most current block too.
How's the download coming?
"height" : 599496,
"proofhash" : "0000000cbc180e9c62c3fce6ab6d3858f8272ca203ce2152aa611f1099b9506d",
221 KB/s - 276 MB of 324 MB, 4 mins left
I'm going to use your CONF file too. (I had renamed mine, so it didn't have one.)
Hmmm...not sure if I can remove something to fix this?
that would be, because I recompiled it with the latest db and ssl... delete the txleveldb
Jump to: