[AMBER] X13 POW/POS| 10k AMBER=0,01% SHARES | BUY, HOLD & GET DIVIDENDS in BTC/$ - page 137.

mhanbostanci

legendary

Activity: 3206

Merit: 1525

Hello,

my AmberCoin.conf :

Code:

server=1
daemon=1
listen=1
upnp=0
rpcuser=****************
rpcpassword=***********
rpcport=31981
maxconnections=5
connect=ambercoin01.mooo.com
connect=ambercoin03.mooo.com

I cant stake.
Because my wallet not sync.

my debug log:

Code:

received block 00000000b32642a4258e
ProcessBlock: ORPHAN BLOCK, prev=8dee448695e48e3296e0
received block 8dee448695e48e3296e0
ProcessBlock: ORPHAN BLOCK, prev=00000000afdbbb4f572a
received block 00000000afdbbb4f572a
ProcessBlock: ORPHAN BLOCK, prev=00000000506ad7db5f07
received block 00000000506ad7db5f07
ProcessBlock: ORPHAN BLOCK, prev=000000013579c6acceb5
received block 000000013579c6acceb5
ProcessBlock: ORPHAN BLOCK, prev=00000000e3a42d790777
received block 000000001a77e9cc401f
ProcessBlock: ORPHAN BLOCK, prev=00000000700e921c4fa0
received block 000000007ff4cde27e0a
ProcessBlock: ORPHAN BLOCK, prev=000000001a77e9cc401f
ProcessSyncCheckpoint: pending for sync-checkpoint 00000000576d25c84ad1194cf6e605c9c54530b787d2e6142a934c584916cb2e
ProcessSyncCheckpoint: pending for sync-checkpoint 00000000576d25c84ad1194cf6e605c9c54530b787d2e6142a934c584916cb2e
received block 00000000576d25c84ad1
ProcessBlock: ORPHAN BLOCK, prev=000000001be41dbdcf2d
received block 000000001be41dbdcf2d
ProcessBlock: ORPHAN BLOCK, prev=00000001029da1f987b7
received block 0cc957b2bb2dcf160125
Misbehaving: 45.32.69.218:31982 (0 -> 100) DISCONNECTING
disconnecting node ambercoin03.mooo.com
ERROR: ProcessBlock() : block with too little proof-of-stake
trying connection ambercoin03.mooo.com lastseen=0,0hrs
connected ambercoin03.mooo.com
send version message: version 90001, blocks=599469, us=176.9.165.51:31982, them=45.32.69.218:31982, peer=45.32.69.218:31982
receive version message: version 90001, blocks=601618, us=176.9.165.51:55739, them=45.32.69.218:31982, peer=45.32.69.218:31982
ProcessSyncCheckpoint: pending for sync-checkpoint 00000000576d25c84ad1194cf6e605c9c54530b787d2e6142a934c584916cb2e

help me please!

Jayfek

full member

Activity: 139

Merit: 100

Quote from: crzybilly on November 30, 2015, 12:30:55 PM

Quote from: bathrobehero on November 30, 2015, 12:27:13 PM

I have 3 connections with maxconnections=1 so the connect command is overriding it.

Just checking:

getblockbynumber 601532 "proofhash" : "000000001be41dbdcf2d082ead1d0b5a358c55258ea307f88604c089c19c310c"

"height" : 601532,
"proofhash" : "000000001be41dbdcf2d082ead1d0b5a358c55258ea307f88604c089c19c310c"

2 wallets both using 02.mooo and 03.mooo (banned from 01.mooo), not staking:
getblockbynumber 601532 "proofhash" : "000000001be41dbdcf2d082ead1d0b5a358c55258ea307f88604c089c19c310c"

crzybilly

sr. member

Activity: 703

Merit: 250

Quote from: bathrobehero on November 30, 2015, 12:27:13 PM

I have 3 connections with maxconnections=1 so the connect command is overriding it.

Just checking:

getblockbynumber 601532 "proofhash" : "000000001be41dbdcf2d082ead1d0b5a358c55258ea307f88604c089c19c310c"

"height" : 601532,
"proofhash" : "000000001be41dbdcf2d082ead1d0b5a358c55258ea307f88604c089c19c310c"

bathrobehero

legendary

Activity: 2002

Merit: 1051

ICO? Not even once.

I have 3 connections with maxconnections=1 so the connect command is overriding it.

Just checking:

getblockbynumber 601532 "proofhash" : "000000001be41dbdcf2d082ead1d0b5a358c55258ea307f88604c089c19c310c"

crackfoo

legendary

Activity: 3486

Merit: 1126

Have any of the exchanges got this sorted back out yet?

Slydrule

full member

Activity: 185

Merit: 100

I am also connected to 2 nodes now (ambercoin02 and ambercoin03) and I match block 601182 proof hash.

I guess I am still banned by ambercoin01.

exemplaar

hero member

Activity: 978

Merit: 506

Quote from: crackfoo on November 30, 2015, 09:56:28 AM

Quote from: verycoinsuchlist on November 30, 2015, 09:40:45 AM

Quote from: crzybilly on November 30, 2015, 09:39:45 AM

Quote from: verycoinsuchlist on November 30, 2015, 09:38:34 AM

so, I just wonder how come he seems to be on the wrong chain while still being able to maintain the connections?

cannot confirm or deny he's on the right nodes, until getpeerinfo is run

that indeed would be good to know...

He may have forked and then added those nodes? It's possible he needs to del the chain and resync?

No way. Wallet was closed several days. Reason must be that i was obviously to quick with that getblockbynumber command while wallet was still initializing. Grin

My blk.dat is clean and i'm on the right chain
proofhash" : "000076b401342b25950ed4eab565bc720043bb35b80713efcc4f46ccedb52c35"

verycoinsuchlist

member

Activity: 89

Merit: 10

Quote from: crackfoo on November 30, 2015, 09:56:28 AM

He may have forked and then added those nodes? It's possible he needs to del the chain and resync?

in case of block mismatch I'd say this is a clear YES... seems to be the only way atm.
usually such blocks should went orphan with the downvoted client, however there seems to be a problem in such scenarios the clients prefer to fork instead and decides to maintain his copy of the blockchain over dropping it and joining back to network...

however, letting the clients just look into one direction to one or more central nodes, thus having them do the negotiation individually seems at least to calm the waves... as mentioned, my wallets seem to move along as one would expect for some time now... but the network also seems to be not that large right now

crackfoo

legendary

Activity: 3486

Merit: 1126

Quote from: verycoinsuchlist on November 30, 2015, 09:40:45 AM

Quote from: crzybilly on November 30, 2015, 09:39:45 AM

Quote from: verycoinsuchlist on November 30, 2015, 09:38:34 AM

so, I just wonder how come he seems to be on the wrong chain while still being able to maintain the connections?

cannot confirm or deny he's on the right nodes, until getpeerinfo is run

that indeed would be good to know...

He may have forked and then added those nodes? It's possible he needs to del the chain and resync?

verycoinsuchlist

member

Activity: 89

Merit: 10

Quote from: crzybilly on November 30, 2015, 09:39:45 AM

Quote from: verycoinsuchlist on November 30, 2015, 09:38:34 AM

so, I just wonder how come he seems to be on the wrong chain while still being able to maintain the connections?

cannot confirm or deny he's on the right nodes, until getpeerinfo is run

that indeed would be good to know...

crzybilly

sr. member

Activity: 703

Merit: 250

Quote from: verycoinsuchlist on November 30, 2015, 09:38:34 AM

so, I just wonder how come he seems to be on the wrong chain while still being able to maintain the connections?

cannot confirm or deny he's on the right nodes, until getpeerinfo is run

verycoinsuchlist

member

Activity: 89

Merit: 10

so, I just wonder how come he seems to be on the wrong chain while still being able to maintain the connections?

shouldn't the negotiation between the clients detect the mismatch and downvote the client?

crzybilly

sr. member

Activity: 703

Merit: 250

Quote from: bathrobehero on November 30, 2015, 09:31:54 AM

Quote from: exemplaar on November 30, 2015, 09:01:46 AM

Current status: 2 active connections to Ambercoin network

.conf:
listen=0
addnode=ambercoin01.mooo.com
addnode=ambercoin02.mooo.com

getblockbynumber 601182 "proofhash" : "0000709ddf69c904205bf4e922f49d32775c9ec6d1313d72b34f9f9f4e402b5d"

it looks ok for now...

I'm only connected to the original node (ambercoin01.mooo.com), but:

getblockbynumber 601182 "proofhash" : "000076b401342b25950ed4eab565bc720043bb35b80713efcc4f46ccedb52c35"

Matches bold above

AmberCoinDev

hero member

Activity: 630

Merit: 500

Quote

getblockbynumber 601182 "proofhash" : "000076b401342b25950ed4eab565bc720043bb35b80713efcc4f46ccedb52c35"

Correct hash.

crackfoo

legendary

Activity: 3486

Merit: 1126

Quote from: bathrobehero on November 30, 2015, 09:31:54 AM

Quote from: exemplaar on November 30, 2015, 09:01:46 AM

Current status: 2 active connections to Ambercoin network

.conf:
listen=0
addnode=ambercoin01.mooo.com
addnode=ambercoin02.mooo.com

getblockbynumber 601182 "proofhash" : "0000709ddf69c904205bf4e922f49d32775c9ec6d1313d72b34f9f9f4e402b5d"

it looks ok for now...

I'm only connected to the original node (ambercoin01.mooo.com), but:

getblockbynumber 601182 "proofhash" : "000076b401342b25950ed4eab565bc720043bb35b80713efcc4f46ccedb52c35"

I get this one as well...

bathrobehero

legendary

Activity: 2002

Merit: 1051

ICO? Not even once.

Quote from: exemplaar on November 30, 2015, 09:01:46 AM

Current status: 2 active connections to Ambercoin network

.conf:
listen=0
addnode=ambercoin01.mooo.com
addnode=ambercoin02.mooo.com

getblockbynumber 601182 "proofhash" : "0000709ddf69c904205bf4e922f49d32775c9ec6d1313d72b34f9f9f4e402b5d"

it looks ok for now...

I'm only connected to the original node (ambercoin01.mooo.com), but:

getblockbynumber 601182 "proofhash" : "000076b401342b25950ed4eab565bc720043bb35b80713efcc4f46ccedb52c35"

AmberCoinDev

hero member

Activity: 630

Merit: 500

ambercoin03.mooo.com now allow connections as well.

verycoinsuchlist

member

Activity: 89

Merit: 10

Quote from: AmberCoinDev on November 30, 2015, 08:41:15 AM

Quote from: crzybilly on November 30, 2015, 08:02:09 AM

Quote from: AmberCoinDev on November 30, 2015, 07:49:12 AM

Quote

It's best they stay connected to the main node, so they don't cause forks... but others should connect to those nodes if they are having issues connecting to the first node.

How to make it in that way?

check and make sure they aren't getting banned

ambercoin02.mooo.com now allow connections.
You can try it.

oh, cool... just added a second connect line to include ambercon02 node and it joins in smoothly... is assume that might be rather beneficial helping to avoid or at least lower the risk of the fork-by-stake problem many users seem to experience...

however, last time I checked my wallets, everything seems to be fine. running a couple hours in line now without an issue while staking/mining...

edit: 3rd node joined in just fine... now obviously on 3 connections, looks quite good

14:27:32

[
{
"addr" : "ambercoin01.mooo.com:31982",
"services" : "00000001",
"lastsend" : 1448890039,
"lastrecv" : 1448890039,
"conntime" : 1448890038,
"version" : 90001,
"subver" : "/AmberCoin:3.0.0.3/",
"inbound" : false,
"startingheight" : 601240,
"banscore" : 0
},
{
"addr" : "ambercoin02.mooo.com:31982",
"services" : "00000001",
"lastsend" : 1448890041,
"lastrecv" : 1448890041,
"conntime" : 1448890038,
"version" : 90001,
"subver" : "/AmberCoin:3.0.0.3/",
"inbound" : false,
"startingheight" : 601240,
"banscore" : 0
},
{
"addr" : "ambercoin03.mooo.com:31982",
"services" : "00000001",
"lastsend" : 1448890041,
"lastrecv" : 1448890050,
"conntime" : 1448890039,
"version" : 90001,
"subver" : "/AmberCoin:3.0.0.3/",
"inbound" : false,
"startingheight" : 601240,
"banscore" : 0
}
]

crzybilly

sr. member

Activity: 703

Merit: 250

Quote from: AmberCoinDev on November 30, 2015, 08:41:15 AM

Quote from: crzybilly on November 30, 2015, 08:02:09 AM

Quote from: AmberCoinDev on November 30, 2015, 07:49:12 AM

Quote

It's best they stay connected to the main node, so they don't cause forks... but others should connect to those nodes if they are having issues connecting to the first node.

How to make it in that way?

check and make sure they aren't getting banned

ambercoin02.mooo.com now allow connections.
You can try it.

getpeerinfo
[
{
"addr" : "ambercoin01.mooo.com",
"services" : "00000001",
"lastsend" : 1448888729,
"lastrecv" : 1448888730,
"conntime" : 1448888728,
"version" : 90001,
"subver" : "/AmberCoin:3.0.0.3/",
"inbound" : false,
"startingheight" : 601194,
"banscore" : 0
},
{
"addr" : "104.238.177.80:31982", <---- ambercoin02.mooo.com
"services" : "00000001",
"lastsend" : 1448888730,
"lastrecv" : 1448888730,
"conntime" : 1448888729,
"version" : 90001,
"subver" : "/AmberCoin:3.0.0.3/",
"inbound" : false,
"startingheight" : 601194,
"banscore" : 0
}
]

exemplaar

hero member

Activity: 978

Merit: 506

Current status: 2 active connections to Ambercoin network

.conf:
listen=0
addnode=ambercoin01.mooo.com
addnode=ambercoin02.mooo.com

getblockbynumber 601182 "proofhash" : "0000709ddf69c904205bf4e922f49d32775c9ec6d1313d72b34f9f9f4e402b5d"

it looks ok for now...

Topic: [AMBER] X13 POW/POS| 10k AMBER=0,01% SHARES | BUY, HOLD & GET DIVIDENDS in BTC/$ - page 137. (Read 407556 times)