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

[binmon]

For me, the dividend money is gone.

Everything else is surprise, i expect nothing.

"Believe it when you see it" 

[verycoinsuchlist]

...funny thing is, my solomining wallet stayed on track 'till now... the staking one went off, no connections (banned) as of now.

next thing that I just noticed... I simply left that one staking wallet (which went offline some hours ago) untouched and running... and now it has reconnected to the very same node as if nothing has happened in the first place. no changes made the time in between... it just seem to have decided that, whatever seemed to be not ok that time it went off, now again is ok so it's accepted again. no clues about that behaviour...

[binmon]

Sure is getting old though... 

[AmberCoinDev]

...funny thing is, my solomining wallet stayed on track 'till now... the staking one went off, no connections (banned) as of now.

next thing that I just noticed... I simply left that one staking wallet (which went offline some hours ago) untouched and running... and now it has reconnected to the very same node as if nothing has happened in the first place. no changes made the time in between... it just seem to have decided that, whatever seemed to be not ok that time it went off, now again is ok so it's accepted again. no clues about that behaviour...

It can be due to reduced to 30 min bantime.
Currently bantime 30 min is on node02 and node03.

Node01 still has 24h.

[antho281]

I can read checkpoint here...
But.. what is it?

Code:

2015-12-04 13:49:31 [Pool]	[ambercoin] (Thread 2) Malformed message from (unauthorized) [//IP_ADDRESS_HERE]: p5"versionp�,��_

a�aV��
��FS� ��������Ѵ_�/AmberCoin:3.0.0.3/WS	p5"checkpointmz�n<$
8Ƽ��ܵ|��š��
�'�VLgԶuLG0E!��̳g;���X��I/�ݓ�o���P���� ��n���>�CMr���ӏ������c��H�p5"checkpointl�� $
�����Ad p��\�~���
                            :w�|��"�GPKF0D ho�V�I��>u�N�Ӝ``�`��8�ْO�=? )9��+?�g�=�o2�t.�����'�&4&�o�p5"checkpointm��$
~]�&�@�iC����U���V�9F�

[verycoinsuchlist]

...funny thing is, my solomining wallet stayed on track 'till now... the staking one went off, no connections (banned) as of now.

next thing that I just noticed... I simply left that one staking wallet (which went offline some hours ago) untouched and running... and now it has reconnected to the very same node as if nothing has happened in the first place. no changes made the time in between... it just seem to have decided that, whatever seemed to be not ok that time it went off, now again is ok so it's accepted again. no clues about that behaviour...

It can be due to reduced to 30 min bantime.
Currently bantime 30 min is on node02 and node03.

Node01 still has 24h.

that would ony explain the relatively short interval after it was able to reconnect... yet, that's not the question I'd try to point toward: why did it went and stay offline in the first place while being able to reconnect as if nothing had happened. no fork, no nothing... just reconnected to the current chain.

[bathrobehero]

I've got forked once again. All 3 mooo nodes disconnected me and the only node I was still connected to was thecryptopool's node which seem to be on the wrong fork. I'm done with this coin for now.

[antho281]

I've got forked once again. All 3 mooo nodes disconnected me and the only node I was still connected to was thecryptopool's node which seem to be on the wrong fork. I'm done with this coin for now.

I can confirm I'm still on the good fork! 😊
Got 4 peers at the moment, still sync with block explorer and my 2 others wallets

EDIT: I double checked, I still have my peers, but looks like it doesn't sync.... again

[AmberCoinDev]

Wallet Amberstuck again,
the discussions on BTT only about networks,node,connections,conf.file,wallet ,..etc more than twenty pages without solutions
Dividends until now not happening,no news,no announcements
hi Dev : we are waiting your respons here about the dividends
please give you respect for those who waiting for

thanks

While we are fixing the wallet's stability problems company follows its plans.
All plans on the ground are being implemented even a little bit quicker than they should.

We have migrated to new hosting recently.
It is a lot of news indeed but issues with wallets have eclipted them.
We will share it soon through our official sites.

[OVRGRO]

While we are fixing the wallet's stability problems company follows its plans.
All plans on the ground are being implemented even a little bit quicker than they should.

We have migrated to new hosting recently.
It is a lot of news indeed but issues with wallets have eclipted them.
We will share it soon through our official sites.

i like how this sounds...

[Steak Cloud]

Hi Ambercoin,

We are on block 611746 at the time of this post in line with Blockexperts. Can someone please confirm that we are good to start payouts?
Also, what exchanges are up to date?

Regards

Steak Cloud support

[crzybilly]

Hi Ambercoin,

We are on block 611746 at the time of this post in line with Blockexperts. Can someone please confirm that we are good to start payouts?
Also, what exchanges are up to date?

Regards

Steak Cloud support

getblockbynumber and post hash and height

[Bootsize17]

While we are fixing the wallet's stability problems company follows its plans.
All plans on the ground are being implemented even a little bit quicker than they should.

We have migrated to new hosting recently.
It is a lot of news indeed but issues with wallets have eclipted them.
We will share it soon through our official sites.

[/quote]


Thanks Dev,

I've been apart of this endeavor since July. All signs point to a promising future for this coin. The Dev and company behind the coin, communicate......... A rare thing at the age of this coin. They are consistent, and open. Definately sticking with this coin.

[binmon]

For what it's worth, I just got the following for block # 611937:

"proofhash" : "000000002d6c3335806a101dcc32663cbdee73afa34ceec0758904e10a1fcce9",


Hope it's still on track... it seems to be!

[crzybilly]

For what it's worth, I just got the following for block # 611937:

"proofhash" : "000000002d6c3335806a101dcc32663cbdee73afa34ceec0758904e10a1fcce9",


Hope it's still on track... it seems to be!

000000002d6c3335806a101dcc32663cbdee73afa34ceec0758904e10a1fcce9

match

[Steak Cloud]

    "synccheckpoint" : "00000000360bcf9f4599992b6c37e94b7f6c77feb51f522a79b1250afa680de0",
    "height" : 611789,
    "timestamp" : "2015-12-05 00:50:02 UTC",
    "policy" : "strict"


Currently on "blocks" : 612014,

[Steak Cloud]

   "synccheckpoint" : "00000000360bcf9f4599992b6c37e94b7f6c77feb51f522a79b1250afa680de0",
    "height" : 611789,
    "timestamp" : "2015-12-05 00:50:02 UTC",
    "policy" : "strict"

Matches what I have.

getblockbynumber 611789
"proofhash" : "00000000360bcf9f4599992b6c37e94b7f6c77feb51f522a79b1250afa680de0"

Although, I seem to have lost my connection with 01.mooo.

Code:

22:03:05 getpeerinfo
22:03:05
[
{
"addr" : "ambercoin03.mooo.com",
"services" : "00000001",
"lastsend" : 1449284518,
"lastrecv" : 1449284518,
"conntime" : 1449220527,
"version" : 90001,
"subver" : "/AmberCoin:3.0.0.3/",
"inbound" : false,
"startingheight" : 610092,
"banscore" : 0
}
]

Ambercoin.CONF

Code:

upnp=0
listen=0
connect=ambercoin01.mooo.com
#connect=ambercoin02.mooo.com
connect=ambercoin03.mooo.com

Debug.LOG

Code:

trying connection ambercoin01.mooo.com lastseen=0.0hrs
connected ambercoin01.mooo.com
send version message: version 90001, blocks=612019, us=0.0.0.0:0, them=108.61.173.201:31982, peer=108.61.173.201:31982
socket closed
disconnecting node ambercoin01.mooo.com

Same here, running on one connection but seems to be running well. I will send out half of the payments, and then send the other half made up of larger payouts once the first has been picked up by a few of the miners and they report back here.

[verycoinsuchlist]

my staking wallet went out of connections again (yet again without any forking) at about an hour+ ago... but went back online after a restart
...the mining wallet stayed online for something close to a day now, though...

both wallets are listening and using the mooo nodes via addnode, so also accepting nodes other than the .mooo's (running with 4-7 peer-connections since)

however, in my view any evidence pointing at POW to be the problem still has to emerge...

apart from that, I'm still pretty cautious on how to rate the network stability at the moment, yet I've got a slight notion that it at least might have become less brittle... I'll watch every now and then ...as much as weekend allows

[richwang]

12:16:27

getblockbynumber 611937


12:16:27

{
"hash" : "000000002d6c3335806a101dcc32663cbdee73afa34ceec0758904e10a1fcce9",
"confirmations" : 198,
"size" : 187,
"height" : 611937,
"version" : 6,
"merkleroot" : "d0d8a5ded52c39a380814372278104b638e3da2b25a7dfa9298badcaf677018d",
"mint" : 0.50000000,
"time" : 1449281783,
"nonce" : 6184193,
"bits" : "1d00cb2d",
"difficulty" : 1.25997347,
"blocktrust" : "1428ee196",
"chaintrust" : "5412c94fae2205",
"previousblockhash" : "00000000802cf5517a2bfdf20903b8c2a1c5e24f6dd0d346660409c13a927151",
"nextblockhash" : "03c58cefc98ba7275c2e79d49aa12c7cd708e829937583c9d82adf2d0997aa14",
"flags" : "proof-of-work",
"proofhash" : "000000002d6c3335806a101dcc32663cbdee73afa34ceec0758904e10a1fcce9",
"entropybit" : 1,
"modifier" : "710bec974d94fea0",
"modifierchecksum" : "843d6220",
"tx" : [
"d0d8a5ded52c39a380814372278104b638e3da2b25a7dfa9298badcaf677018d"
]
}

[richwang]

12:17:35

getblockbynumber 612135


12:17:35

{
"hash" : "0000000009f6d73e06ff83823ceee8f4182deedf6971339c92229e77b420a052",
"confirmations" : 1,
"size" : 247,
"height" : 612135,
"version" : 6,
"merkleroot" : "09bc8d8d9cdad4f4b5cc75805a4373fc602f3188fd5260dd26ba171935f76845",
"mint" : 0.50000000,
"time" : 1449288973,
"nonce" : 4828812,
"bits" : "1c147820",
"difficulty" : 12.50638105,
"blocktrust" : "c81aeb1f0",
"chaintrust" : "54149646a0895e",
"previousblockhash" : "0000000019fc6da6a383e5ac3799fad75a21b57c9968e350bf8eb728c5ffb1eb",
"flags" : "proof-of-work",
"proofhash" : "0000000009f6d73e06ff83823ceee8f4182deedf6971339c92229e77b420a052",
"entropybit" : 0,
"modifier" : "ec87fc0c3b7f2311",
"modifierchecksum" : "0718507c",
"tx" : [
"09bc8d8d9cdad4f4b5cc75805a4373fc602f3188fd5260dd26ba171935f76845"
]
}