10k amber price too high to receive dividend
1 btc can buy 10k AmberCoin in c-cex or cryptsy, is it too high? 
Topic: [AMBER] X13 POW/POS| 10k AMBER=0,01% SHARES | BUY, HOLD & GET DIVIDENDS in BTC/$ - page 133. (Read 407572 times)
December 01, 2015, 08:13:53 AM
December 01, 2015, 07:42:17 AM
http://amber.explorer.ssdpool.com:9146/ seems to be up to date. 
December 01, 2015, 07:40:11 AM
Quote
height : 603234
proofhash : 00002c725912c30bdf624ecbae00208af6982d268e55456ee0b75e34a9a8994e
CONFIRM proofhash : 00002c725912c30bdf624ecbae00208af6982d268e55456ee0b75e34a9a8994e
December 01, 2015, 07:33:23 AM
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.
December 01, 2015, 07:30:45 AM
10k amber price too high to receive dividend
December 01, 2015, 07:28:08 AM
.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
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
December 01, 2015, 07:25:22 AM
Quote
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.
Quote
Any news about dividends?
Not yet.
December 01, 2015, 05:58:37 AM
Dev, friday u told company will be buy some coins tru market. Do you know when it will be happen?
Any news about dividends?
Any news about dividends?
December 01, 2015, 04:54:34 AM
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
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.
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.
December 01, 2015, 03:55:34 AM
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
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.
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"
December 01, 2015, 02:04:13 AM
AmberCoin is so popular this week.
December 01, 2015, 12:19:13 AM
Let me know when you get it setup and I"ll join you.
November 30, 2015, 11:59:25 PM
I'm trying to build one at the moment !
If I ever can connect to a few peer, I could make it online!
If I ever can connect to a few peer, I could make it online!
November 30, 2015, 11:52:32 PM
Anyone know any active mining pools? The two on the thread are dead.
November 30, 2015, 11:18:26 PM
Just a lack of peer then... 
November 30, 2015, 11:11:00 PM
Main wallet got the same hash!!
Pool wallet forked
EDIT: in fact... I don't know, can you send me the 602470?
"000000004e80dd621bcdec7eec5615558b07585468702b931f39f031c95d"
Pool wallet forked
EDIT: in fact... I don't know, can you send me the 602470?
"000000004e80dd621bcdec7eec5615558b07585468702b931f39f031c95d"
November 30, 2015, 11:03:25 PM
Down to 1 peer on one of my wallet now.... looks like a fork who's coming -.-
November 30, 2015, 10:44:44 PM
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"
(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.)
November 30, 2015, 10:41:18 PM
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"
(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
November 30, 2015, 10:31:21 PM
my wallet stuck at block 599417 from yesterday
with 16 connections active
with 16 connections active
Do you have staking on?
getblockbynumber 599417
"proofhash" : "000d2a2834052a57757c1dc98b47ee165a0368446962ed0ea450d73ac067daca"
yes i have
do i need to replace all files and remove peers dat again,..
Only if the proofhash I posted doesn't match what you have. I gather you've tried restarting your wallet?
If he has 16 connections then he could be connected to some bad nodes too. IMO, he should restore the DB and fix his .conf file to set listen to 0 and connect only to the 3 main nodes (ambercoin01.mooo.com, ambercoin02.mooo.com and ambercoin03.mooo.com)
And btw, I had the same problem with resyncing. It kept stalling. I just kept closing and restarting my wallet until it resynced completely. I had to restart 2 or 3 times.
Jump to: