okay.. thats good for now. synched and staked already
any command to rollback last block?

All not work. Can´t connect anymore even goin that route :/

"height" : 601672
"proofhash" : "000000000744d766e9667524224f64e2c0c75f483410f696f16da4a29b26e882"

That means you are still on wrong chain.

This explorer works fine now and shows correct information https://www.blockexperts.com/amber

To help those who are not on a main chain - here is fresh (some hours ago) correct blockchain:

    https://www.dropbox.com/s/94hqeihkupmqjkn/BlockChain2711.rar?dl=0

P.S. Use "repairwallet" command after you synced.

AmberCoin-qt.exe -server -connect=ambercoin01.mooo.com

that's my shortcut to ambercoin. remove -server if you don't plan on solo mining

there  s 4 active node connected but no synch how may i fix it?

type the following in debug window:

getblockcount
take results from this and put after
getblockbynumber <results from previous command>

paste height & proofhash here

there is no activity on blockexplorer whats going on guys?
https://www.blockexperts.com/amber
when this situation will solve?

help me please!

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

Just checking:

getblockbynumber 601532 "proofhash" : "000000001be41dbdcf2d082ead1d0b5a358c55258ea307f88604c089c19c310c"

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

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

getblockbynumber 601182 "proofhash" : "000076b401342b25950ed4eab565bc720043bb35b80713efcc4f46ccedb52c35"

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

How to make it in that way?

Old wallets are cut by "protocolversion".

Will "maxconnections=" work with "connect=" option and "listen=1"?

Last DEBUG info from ambercoin01.mooo.com.
Maybe would be helpful.

getblocks stopping at limit 319039 000000001e9e81e56405
accepted connection 81.88.143.194:58254
getblocks 13920 to 000000002177ca4f7aa4 limit 500
  getblocks stopping at limit 14419 0000000000e17c6c14e5
partner 81.88.143.194:58254 using obsolete version 90000; disconnecting
ProcessMessage(version, 112 bytes) FAILED
disconnecting node 81.88.143.194:58254
connection from 113.161.128.181:64841 dropped (banned)
getblocks 318540 to c184b39662b4c2b46b3b limit 500
  getblocks stopping at 318975 c184b39662b4c2b46b3b
connection from 71.187.62.42:56790 dropped (banned)
connection timeout
accepted connection 176.107.192.2:61021
partner 176.107.192.2:61021 using obsolete version 90000; disconnecting
ProcessMessage(version, 112 bytes) FAILED
disconnecting node 176.107.192.2:61021
trying connection 108.61.174.143:31982 lastseen=1.2hrs
connection from 85.214.23.49:38378 dropped (banned)
connection from 213.180.26.45:53289 dropped (banned)
connection from 212.83.176.222:50699 dropped (banned)
connection from 213.180.26.34:54001 dropped (banned)
getblocks 598600 to 00000000ec75c4beed3d limit 500
  getblocks stopping at limit 599099 53c6a89261562977f215
getblocks 598600 to 00000000059cd7afbae2 limit 500
  getblocks stopping at limit 599099 53c6a89261562977f215
received getdata (12 invsz)
connection from 113.161.128.181:64842 dropped (banned)

Here is the relevant section of the debug log file:

ThreadSocketHandler started
ThreadStakeMiner started
trying connection ambercoin01.mooo.com lastseen=0.0hrs
Flushed 0 addresses to peers.dat  18ms
refreshWallet
connected ambercoin01.mooo.com
send version message: version 90001, blocks=594334, us=0.0.0.0:0, them=108.61.173.201:31982, peer=108.61.173.201:31982
trying connection 108.61.173.201 lastseen=0.0hrs
socket closed
disconnecting node ambercoin01.mooo.com
connected 108.61.173.201
send version message: version 90001, blocks=594334, us=0.0.0.0:0, them=108.61.173.201:31982, peer=108.61.173.201:31982
trying connection 188.163.90.183 lastseen=0.0hrs
socket closed
disconnecting node 108.61.173.201

I took this section right after the point where the wallet synchronizes.  This is repeated throughout the log file.

wow...been following along with this recent update and all the problems that have sprung up these past couple days. I'd like to clear up a bit of misinformation that has been tossed around regarding the conf/startup flags:

-daemon : "Run in the background as a daemon and accept commands". This actually has little effect when using the Qt GUI wallet.
-server : "Accept command line and JSON-RPC commands". This is what allows solo-mining when using an external mining program (cpuminer/ccminer/cgminer/etc).
-addnode : "Add a node to connect to and attempt to keep the connection open". Further nodes will be retrieved from these nodes and attempt to connect.
-connect : "Connect only to the specified node(s)". Says it all, ONLY nodes specified will be allowed to maintain a connection.
-listen : "Accept connections from outside (default: 1 if no -proxy or -connect)". This has EVERYTHING to do with the P2P network, and nothing to do with solo-mining or the RPC.

If your goal is to only connect to one node (whichever node that may be), set the following in your conf file:


listen is (or should) automatically be set to 0 whenever connect is used, but better to explicitly define it anyways. Another setting that is (or should) be set to 0 automatically when connect or listen are used, is upnp.

After doing a bit of code review, users should explicitly disable upnp in their wallets irregardless of your connection preferences as the current Amber source has not yet been updated to work with the recently patched miniupnpc versions (https://bitcoin.org/en/release/v0.11.1#fix-buffer-overflow-in-bundled-upnp).

As for why some people cannot connect to ambercoin01.mooo.com: the two very likely reasons this could be happening is that
1) the node has banned you for submitting invalid hashes. This ban will eventually be lifted, but you pretty much just have to wait it out.
2) the maximum number of stable connections for said node has been reached and further connections are being dropped.

Has anyone looked into he problem why some people cannot connect to ambercoin01.mooo.com?