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

[antho281]

Just checking in.  With staking off and no block explorers, there's no way for me to know if I've gone off the chain.
(With staking on, it's easy because you suddenly start getting rewards piling in.)

I guess the fact that 02.mooo and 03.mooo haven't disconnected me is a good sign.

getblockcount: 602455

getblockbynumber 602455
"proofhash" : "0000000034dd7f9e70b21e2405aa1dafc52d279a6d4f6766b9322c5b0584fd83"

Where at the same point!
Still matching

[binmon]

Just checking in.  With staking off and no block explorers, there's no way for me to know if I've gone off the chain.
(With staking on, it's easy because you suddenly start getting rewards piling in.)

I guess the fact that 02.mooo and 03.mooo haven't disconnected me is a good sign.

getblockcount: 602455

getblockbynumber 602455
"proofhash" : "0000000034dd7f9e70b21e2405aa1dafc52d279a6d4f6766b9322c5b0584fd83"

I get the same proofhash as you did, if that's any consolation..........  it is to me, glad to see it!  
(cuz I'm staking... and not seeming to have any problem.)

[antho281]

Down to 1 peer on one of my wallet now.... looks like a fork who's coming -.-

[antho281]

Main wallet got the same hash!!
Pool wallet forked

EDIT: in fact... I don't know, can you send me the 602470?
"000000004e80dd621bcdec7eec5615558b07585468702b931f39f031c95d"

[antho281]

Just a lack of peer then...

[lethax]

Anyone know any active mining pools? The two on the thread are dead.

[antho281]

I'm trying to build one at the moment !
If I ever can connect to a few peer, I could make it online!

[lethax]

Let me know when you get it setup and I"ll join you.

[richwang]

AmberCoin is so popular this week.

[Jayfek]

one thing i noticed while browsing the git repo late last night is that the acceptable time drift is ± 24 hours....thats rather HUGE!

What do you mean?
Where is it in the code and what could it affect?

https://github.com/AmberCoinDev/Amber/blob/master/src/main.h#L75-L76

Code:

inline int64_t PastDrift(int64_t nTime)   { return nTime - 24 * 60 * 60; } // up to 1 day from the past
inline int64_t FutureDrift(int64_t nTime) { return nTime + 24 * 60 * 60; } // up to 1 day from the future

having such a large variance in acceptable drift time leaves the network open to a timestamp manipulation attack...which, ironically enough, can be used for (among other things) forcing a client to reject otherwise valid hashes/blocks resulting in forced forking.

Here is an old article about timejacking. Even though it is quite old, the basic principles still apply: http://culubas.blogspot.com/2011/05/timejacking-bitcoin_802.html.

In this old (and still good) article mentioned allowed drift time 30 minutes/0.5 hours is 48 times less than 24 hours in AmberCoin code... There must be reason for so big time drift window, like attempt to handle incorrectly handled timezone by node?
For me seems that staking, last changed part of code, is responsible for forking. 2 times 2 my wallets forked very soon after enabling staking. Now staking is disabled (by wallet encryption), connected strictly only to "mooo-s" and minting locally, every found block accepted (which is little bit strange...).

getblockcount
602856
getblockbynumber 602856
"proofhash" : "0000000029d1b1a876606ff107d91d05d0a76b74224eacf2823634e3141f7a3a"

[AmberCoinDev]

one thing i noticed while browsing the git repo late last night is that the acceptable time drift is ± 24 hours....thats rather HUGE!

What do you mean?
Where is it in the code and what could it affect?

https://github.com/AmberCoinDev/Amber/blob/master/src/main.h#L75-L76

Code:

inline int64_t PastDrift(int64_t nTime)   { return nTime - 24 * 60 * 60; } // up to 1 day from the past
inline int64_t FutureDrift(int64_t nTime) { return nTime + 24 * 60 * 60; } // up to 1 day from the future

having such a large variance in acceptable drift time leaves the network open to a timestamp manipulation attack...which, ironically enough, can be used for (among other things) forcing a client to reject otherwise valid hashes/blocks resulting in forced forking.

Here is an old article about timejacking. Even though it is quite old, the basic principles still apply: http://culubas.blogspot.com/2011/05/timejacking-bitcoin_802.html.

In this old (and still good) article mentioned allowed drift time 30 minutes/0.5 hours is 48 times less than 24 hours in AmberCoin code... There must be reason for so big time drift window, like attempt to handle incorrectly handled timezone by node?
For me seems that staking, last changed part of code, is responsible for forking. 2 times 2 my wallets forked very soon after enabling staking. Now staking is disabled (by wallet encryption), connected strictly only to "mooo-s" and minting locally, every found block accepted (which is little bit strange...).

getblockcount
602856
getblockbynumber 602856
"proofhash" : "0000000029d1b1a876606ff107d91d05d0a76b74224eacf2823634e3141f7a3a"

"proofhash" : "0000000029d1b1a876606ff107d91d05d0a76b74224eacf2823634e3141f7a3a" is correct.

We will look into this issue with drift time.
But it was the same before an update and all worked perfectly.

[twn]

Dev, friday u told company will be buy some coins tru market. Do you know when it will be happen?
Any news about dividends?

[AmberCoinDev]

Dev, friday u told company will be buy some coins tru market. Do you know when it will be happen?

Yes.
I wrote that we consider such a possibility.
It will not take too much time.
Once the decision is made I will let all know about it.

Any news about dividends?

Not yet.

[exemplaar]

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


height : 602856
proofhash : 0000000029d1b1a876606ff107d91d05d0a76b74224eacf2823634e3141f7a3a


"addr" : "108.61.173.201:31982",
"services" : "00000001",
"lastsend" : 1448972519,
"lastrecv" : 1448972519,
"conntime" : 1448972229,
"version" : 90001,
"subver" : "/AmberCoin:3.0.0.3/",
"inbound" : false,
"startingheight" : 603217,
"banscore" : 0
},
{
"addr" : "45.32.69.218:31982",
"services" : "00000001",
"lastsend" : 1448972449,
"lastrecv" : 1448972519,
"conntime" : 1448972230,
"version" : 90001,
"subver" : "/AmberCoin:3.0.0.3/",
"inbound" : false,
"startingheight" : 603217,
"banscore" : 0
},
{
"addr" : "104.238.177.80:31982",
"services" : "00000001",
"lastsend" : 1448972421,
"lastrecv" : 1448972518,
"conntime" : 1448972230,
"version" : 90001,
"subver" : "/AmberCoin:3.0.0.3/",
"inbound" : false,
"startingheight" : 603217,
"banscore" : 0



EDIT:

height : 603234
proofhash : 00002c725912c30bdf624ecbae00208af6982d268e55456ee0b75e34a9a8994e

[butcherboss]

10k amber price too high to receive dividend

[exemplaar]

10k amber price too high to receive dividend

Buying little by little and mining little by little and you will get in no time to 10K.

Today is a good time to start.  

[AmberCoinDev]

height : 603234
proofhash : 00002c725912c30bdf624ecbae00208af6982d268e55456ee0b75e34a9a8994e

CONFIRM

[AmberCoinDev]

http://amber.explorer.ssdpool.com:9146/ seems to be up to date. 

[richwang]

10k amber price too high to receive dividend

1 btc can buy 10k AmberCoin in c-cex or cryptsy, is it too high?

[OVRGRO]

http://amber.explorer.ssdpool.com:9146/ seems to be up to date. 

I went to check it last night, said I had barely 10k coins... I almost cried, but noticed it was early may on the date stamp lol.