|
crzybilly
|
 |
November 29, 2015, 06:45:14 PM |
|
13:27:59

getpeerinfo
13:27:59

[
{
"addr" : "ambercoin01.mooo.com",
"services" : "00000001",
"lastsend" : 1448821612,
"lastrecv" : 1448821612,
"conntime" : 1448821559,
"version" : 90001,
"subver" : "/AmberCoin:3.0.0.3/",
"inbound" : false,
"startingheight" : 599461,
"banscore" : 0
}
]
Thx, I'll try using your DB.
http://www.mediafire.com/download/26ibd56699yedhq/amber.zip |
|
|
|
|
|
johnnysof
|
|
November 29, 2015, 06:49:29 PM |
|
"height" : 599444,
"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? |
|
|
|
|
|
AmberCoinDev (OP)
|
|
November 29, 2015, 06:51:24 PM |
|
"height" : 599444,
"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? They get banned by adding a "checkpoint=*******" line into AmberCoin.conf on ambercoin01.mooo.com |
|
|
|
|
crzybilly
|
|
November 29, 2015, 06:51:39 PM |
|
"height" : 599444,
"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. |
|
|
|
|
crackfoo
Legendary
 Offline
Activity: 3500
Merit: 1126
|
|
November 29, 2015, 06:52:39 PM |
|
What do you mean?
They get banned by adding a "checkpoint=*******" line into AmberCoin.conf
Can you tell us what ***** should be? |
ZPOOL - the miners multipool! Support We pay 10 FLUX Parallel Assets (PA) directly to block rewards! Get paid more and faster. No PA fee's or waiting around for them, paid instantly on every block found!
|
|
|
|
AmberCoinDev (OP)
|
|
November 29, 2015, 06:55:39 PM |
|
What do you mean?
They get banned by adding a "checkpoint=*******" line into AmberCoin.conf
Can you tell us what ***** should be? No. You shouldn'd add anything! It is long line with a key. It should be only on ambercoin01.mooo.com It works as a checkpointing server. |
|
|
|
|
crzybilly
|
|
November 29, 2015, 06:58:13 PM |
|
What do you mean?
They get banned by adding a "checkpoint=*******" line into AmberCoin.conf
Can you tell us what ***** should be? No. You shouldn'd add anything! It is long line with a key. It should be only on ambercoin01.mooo.com It works as a checkpointing server. so you are banning people, because some people are still coming a crossed as a banscore of 0 |
|
|
|
|
|
Slydrule
|
|
November 29, 2015, 06:58:28 PM |
|
"height" : 599444,
"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. |
|
|
|
|
|
AmberCoinDev (OP)
|
|
November 29, 2015, 07:01:12 PM |
|
"height" : 599444,
"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%. |
|
|
|
|
AmberCoinDev (OP)
|
|
November 29, 2015, 07:02:00 PM |
|
so you are banning people, because some people are still coming a crossed as a banscore of 0
Is that any other way to ban them? |
|
|
|
|
crzybilly
|
|
November 29, 2015, 07:02:26 PM |
|
"height" : 599444,
"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. NO NO NO don't set that to 0... set it to 1 so that it can connect to ambercoin01 rpcallowip=127.0.0.1 rpcallow=localhost rpcport=31981 listen=1 daemon=1 server=1 gen=0 addnode=ambercoin01.mooo.com is my conf |
|
|
|
|
|
crzybilly
|
|
November 29, 2015, 07:09:21 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.
How's the download coming? "height" : 599496, "proofhash" : "0000000cbc180e9c62c3fce6ab6d3858f8272ca203ce2152aa611f1099b9506d", |
|
|
|
|
|
AmberCoinDev (OP)
|
|
November 29, 2015, 07:11:28 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.
How's the download coming? "height" : 599496, "proofhash" : "0000000cbc180e9c62c3fce6ab6d3858f8272ca203ce2152aa611f1099b9506d", |
|
|
|
|
crzybilly
|
|
November 29, 2015, 07:13:44 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.
How's the download coming? "height" : 599496, "proofhash" : "0000000cbc180e9c62c3fce6ab6d3858f8272ca203ce2152aa611f1099b9506d", it can't be wrong... ambercoin01 is the only node I accept  Trying to help everyone else out get on the correct chain |
|
|
|
|
|
johnnysof
|
|
November 29, 2015, 07:18:02 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.
How's the download coming? "height" : 599496, "proofhash" : "0000000cbc180e9c62c3fce6ab6d3858f8272ca203ce2152aa611f1099b9506d", it can't be wrong... ambercoin01 is the only node I accept Trying to help everyone else out get on the correct chain Where should be ambercoin01 added? in the conf file with "addnode"? |
|
|
|
|
|
crzybilly
|
|
November 29, 2015, 07:20:12 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.
How's the download coming? "height" : 599496, "proofhash" : "0000000cbc180e9c62c3fce6ab6d3858f8272ca203ce2152aa611f1099b9506d", it can't be wrong... ambercoin01 is the only node I accept Trying to help everyone else out get on the correct chain Where should be ambercoin01 added? in the conf file with "addnode"? This is a good config setting you can use rpcallowip=127.0.0.1 rpcallow=localhost rpcport=31981 listen=1 daemon=1 (remove this line if you don't solo mine) server=1 (remove this line if you don't solo mine) gen=0 addnode=ambercoin01.mooo.com |
|
|
|
|
|
johnnysof
|
|
November 29, 2015, 07:22:03 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.
How's the download coming? "height" : 599496, "proofhash" : "0000000cbc180e9c62c3fce6ab6d3858f8272ca203ce2152aa611f1099b9506d", it can't be wrong... ambercoin01 is the only node I accept Trying to help everyone else out get on the correct chain Where should be ambercoin01 added? in the conf file with "addnode"? This is a good config setting you can use rpcallowip=127.0.0.1 rpcallow=localhost rpcport=31981 listen=1 daemon=1 (remove this line if you don't solo mine) server=1 (remove this line if you don't solo mine) gen=0 addnode=ambercoin01.mooo.com Thanks, I'll give it a try and hope it works. |
|
|
|
|
|
Framauro
|
|
November 29, 2015, 07:22:54 PM |
|
"height" : 599444,
"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. NO NO NO don't set that to 0... set it to 1 so that it can connect to ambercoin01 rpcallowip=127.0.0.1 rpcallow=localhost rpcport=31981 listen=1 daemon=1 server=1 gen=0 addnode=ambercoin01.mooo.com is my conf Guys, LISTEN=1 or 0 means at what port it must connect, if you have listen=1 and rpcpport=31981 then it will connect to port 31981. If you got Listen=0 it will not connect to rpcport 31981. It has nothing to do with your addnodes. If you make a config file with only the addnodes (so without deamon=1 and server=1 etc...) your wallet will still connect to the addnodes in you config file. This is my config: server=1 daemon=1 listen=1 rpcuser=user rpcpassword=pass rpcport=31981 addnode=108.61.173.201 addnode=188.163.90.183 addnode=88.198.100.148 everything is working fine here. 20:21:59  getblockbynumber 594177 20:21:59  { "hash" : "00000000215b5309e034ccf4a4b4091a0d874d52980b5cc867c554f7e7c4e1a9", "confirmations" : 5341, "size" : 186, "height" : 594177, "version" : 6, "merkleroot" : "0cf807f825350135af1b5d22d590e4873ac225092bbb991a37de06778e0e7450", "mint" : 0.50000000, "time" : 1448630660, "nonce" : 4263179624, "bits" : "1d010426", "difficulty" : 0.98403856, "blocktrust" : "fbeaef62", "chaintrust" : "53a684f73fa2e6", "previousblockhash" : "00000000b7142d1d2c327f14f0def30b56eefb94548395c3732b9e8aa8997256", "nextblockhash" : "e3dd4eacf4582fa922c6c1d4e910e1ec067b91adbe4b5f79790f977bacae1145", "flags" : "proof-of-work", "proofhash" : "00000000215b5309e034ccf4a4b4091a0d874d52980b5cc867c554f7e7c4e1a9", "entropybit" : 1, "modifier" : "9c5bc1cbb554c637", "modifierchecksum" : "3a6d5ef8", "tx" : [ "0cf807f825350135af1b5d22d590e4873ac225092bbb991a37de06778e0e7450" ] } |
|
|
|
|
twn
Legendary
Offline
Activity: 1204
Merit: 1011
|
|
November 29, 2015, 07:24:20 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.
How's the download coming? "height" : 599496, "proofhash" : "0000000cbc180e9c62c3fce6ab6d3858f8272ca203ce2152aa611f1099b9506d", I have this correct but 599444 different than what dev writes. So am i on right chain or not? |
|
|
|
|
|
crzybilly
|
|
November 29, 2015, 07: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.
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 |
|
|
|
|
|
