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

[Slydrule]

And changing your AmberCoin.CONF file to this will lock you onto the main servers only:
(Modified from what Fuzzbawls posted to include all 3 servers.)

Code:

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

I can confirm this has gotten me back on the right track.  However I did disable staking for the meantime.
[/quote]

Me too - as long as I do not unlock my wallet and begin staking my wallet seems to be okay. 

How do we confirm everyone has done likewise?

[mhanbostanci]

how to fix?
What to do?

large amounts of posts the last days, so it's getting quite hard to find something within the mess... for you and anyone else stopping by now

I've posted a solution here: https://bitcointalk.org/index.php?topic=944408.msg13105815#msg13105815

but I suggest making your way through the posts of the last 4-5 pages as I do not have a complete overview myself

edit: or just have a look at the post one above mine

I am very happy

Code:

received block f9b766240abd9fb8ddcc
SetBestChain: new best=f9b766240abd9fb8ddcc  height=602058  trust=23586872002454935  blocktrust=3055183  date=11/30/15 22:23:53
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 3ms
CTxMemPool::accept() : accepted 1da9416671 (poolsz 1)
received block 7bee8d0570a74b50f131
SetBestChain: new best=7bee8d0570a74b50f131  height=602059  trust=23586872006469055  blocktrust=4014120  date=11/30/15 22:24:21
ProcessBlock: ACCEPTED
Flushing wallet.dat
Flushed wallet.dat 3ms
received block 609ca650053c1b7173f7
SetBestChain: new best=609ca650053c1b7173f7  height=602060  trust=23586872011351108  blocktrust=4882053  date=11/30/15 22:24:33
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 3ms
received block 85a33d58ff7077b21fd9
SetBestChain: new best=85a33d58ff7077b21fd9  height=602061  trust=23586872018008480  blocktrust=6657372  date=11/30/15 22:25:15
ProcessBlock: ACCEPTED
Flushing wallet.dat
Flushed wallet.dat 3ms
Flushed 301 addresses to peers.dat  2ms

Thank you so much.
I am grateful

[OVRGRO]

Just gonna say it... It has been a tumultuous 5 weeks with dividends delayed, wallet issues, etc... But y'all have all banded together and really made this a community

[crzybilly]

how to fix?
What to do?

large amounts of posts the last days, so it's getting quite hard to find something within the mess... for you and anyone else stopping by now

I've posted a solution here: https://bitcointalk.org/index.php?topic=944408.msg13105815#msg13105815

but I suggest making your way through the posts of the last 4-5 pages as I do not have a complete overview myself

edit: or just have a look at the post one above mine

I am very happy

Code:

received block f9b766240abd9fb8ddcc
SetBestChain: new best=f9b766240abd9fb8ddcc  height=602058  trust=23586872002454935  blocktrust=3055183  date=11/30/15 22:23:53
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 3ms
CTxMemPool::accept() : accepted 1da9416671 (poolsz 1)
received block 7bee8d0570a74b50f131
SetBestChain: new best=7bee8d0570a74b50f131  height=602059  trust=23586872006469055  blocktrust=4014120  date=11/30/15 22:24:21
ProcessBlock: ACCEPTED
Flushing wallet.dat
Flushed wallet.dat 3ms
received block 609ca650053c1b7173f7
SetBestChain: new best=609ca650053c1b7173f7  height=602060  trust=23586872011351108  blocktrust=4882053  date=11/30/15 22:24:33
ProcessBlock: ACCEPTED
getblocks -1 to 00000000000000000000 limit 500
getblocks -1 to 00000000000000000000 limit 500
Flushing wallet.dat
Flushed wallet.dat 3ms
received block 85a33d58ff7077b21fd9
SetBestChain: new best=85a33d58ff7077b21fd9  height=602061  trust=23586872018008480  blocktrust=6657372  date=11/30/15 22:25:15
ProcessBlock: ACCEPTED
Flushing wallet.dat
Flushed wallet.dat 3ms
Flushed 301 addresses to peers.dat  2ms

Thank you so much.
I am grateful

you are not out of the woods yet sir/ma'am

getblockcount and getblockbynumber the block count

[crzybilly]

Just gonna say it... It has been a tumultuous 5 weeks with dividends delayed, wallet issues, etc... But y'all have all banded together and really made this a community

it helps when some very smart people are here to help people through the wallet issues... Thank you Fuzzbawls for jumping in, to help field some of the issues

[lethax]

Awesome, i'm getting the same proof as you guys. what sucks is i lost all 600 amber i mined last night ><

[antho281]

Just caught up with all the new messages and my wallet survived.  All the hashes match.  Still only connected to ambercoin02.mooo.com & ambercoin03.mooo.com.

Congrats Slydrule on your parole.  I'm still in the ambercoin01.mooo.com slammer.

Code:

trying connection ambercoin01.mooo.com lastseen=0.0hrs
connected ambercoin01.mooo.com
send version message: version 90001, blocks=601881, 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

Currently on: 601883

getblockbynumber 601883
"proofhash" : "001bba7508d344825644012d88cc8bdfe34becaf959ee568dddac24ca5f26a30"

getblockbynumber 601883
"proofhash" : "001bba7508d344825644012d88cc8bdfe34becaf959ee568dddac24ca5f26a30"

Still following here!

[mhanbostanci]

you are not out of the woods yet sir/ma'am

getblockcount and getblockbynumber the block count

602207

getblockbynumber 602207

Code:

{
"hash" : "000000000d6a7838ed524829132f361b69c928c60312a8479fd92787388c761d",
"confirmations" : 1,
"size" : 187,
"height" : 602207,
"version" : 6,
"merkleroot" : "f2cd59b83d9e7b3a3a0925e96943840ec6f1db264836b49dde8377b82d8dc15a",
"mint" : 0.50000000,
"time" : 1448928588,
"nonce" : 1052483,
"bits" : "1c6b3652",
"difficulty" : 2.38775177,
"blocktrust" : "263461687",
"chaintrust" : "53ccfb661c0143",
"previousblockhash" : "0000000070972a575d0d1c65535ef473a1b80844536e1039fdbf1f4b4bc898d2",
"flags" : "proof-of-work",
"proofhash" : "000000000d6a7838ed524829132f361b69c928c60312a8479fd92787388c761d",
"entropybit" : 1,
"modifier" : "85a674bfa6639167",
"modifierchecksum" : "1078be7b",
"tx" : [
"f2cd59b83d9e7b3a3a0925e96943840ec6f1db264836b49dde8377b82d8dc15a"
]
}

[crzybilly]

you are not out of the woods yet sir/ma'am

getblockcount and getblockbynumber the block count

602203

getblockbynumber 602203

Code:

"height" : 602203,
"proofhash" : "000000004dcc8bb4742db98529cb39a48309653b81c7781e29596157ab017ee7",

000000004dcc8bb4742db98529cb39a48309653b81c7781e29596157ab017ee7 Matches

[mhanbostanci]

you are not out of the woods yet sir/ma'am

getblockcount and getblockbynumber the block count

602203

getblockbynumber 602203

Code:

"height" : 602203,
"proofhash" : "000000004dcc8bb4742db98529cb39a48309653b81c7781e29596157ab017ee7",

000000004dcc8bb4742db98529cb39a48309653b81c7781e29596157ab017ee7 Matches

this number is constantly growing

"height" : 602209

"previousblockhash" : "000000003bb50d255f7db4f839456c124636de570ae13c35fb901374c5ce0453",

[Mig-23]

my wallet stuck at block 599417 from yesterday

with 16 connections active

[Fuzzbawls]

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.

[crzybilly]

my wallet stuck at block 599417 from yesterday

with 16 connections active

Do you have staking on?

getblockbynumber 599417
"proofhash" : "000d2a2834052a57757c1dc98b47ee165a0368446962ed0ea450d73ac067daca"

okay... I'm sorry I have to clarify this...

IT HAS NOTHING TO DO WITH STAKING... I'm staking and mining this entire time

Status: 61 confirmations, broadcast through 2 nodes
Date: 11/30/2015 19:23
Source: Generated
Credit: 0.25180821 AMBER
Net amount: +0.25180821 AMBER

Status: 1097 confirmations
Date: 11/30/2015 07:55
Source: Generated
Credit: 0.08706849 AMBER
Net amount: +0.08706849 AMBER

Status: 1596 confirmations
Date: 11/30/2015 00:56
Source: Generated
Credit: 0.2249589 AMBER
Net amount: +0.2249589 AMBER

[pokeytex]

Awesome, i'm getting the same proof as you guys. what sucks is i lost all 600 amber i mined last night ><

@lethax - another way to look at it is - you never really had them - it sucks but remember - if it is too good to be true - it probably isn't.

[crzybilly]

Don't get me wrong, I had some legit POS rewards too.  I'm just saying how else could I have forked unless a POS created a block that got rejected, but my wallet carried on anyhow.

Fuzzbawls posted a perfectly good explanation end of last page.

[crzybilly]

Don't get me wrong, I had some legit POS rewards too.  I'm just saying how else could I have forked unless a POS created a block that got rejected, but my wallet carried on anyhow.

Fuzzbawls posted a perfectly good explanation end of last page.

So how did it fork me?  Fooled the main server and the server sent me a bad block?

correct

[lethax]

Awesome, i'm getting the same proof as you guys. what sucks is i lost all 600 amber i mined last night ><

@lethax - another way to look at it is - you never really had them - it sucks but remember - if it is too good to be true - it probably isn't.

So true. I'll get over it and just purchase a bunch. It's my goal now to get to 10k min.

[Mig-23]

my wallet stuck at block 599417 from yesterday

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,..


edit : i saw ccex still on maintenance too

[Slydrule]

my wallet stuck at block 599417 from yesterday

with 16 connections active

Do you have staking on?

getblockbynumber 599417
"proofhash" : "000d2a2834052a57757c1dc98b47ee165a0368446962ed0ea450d73ac067daca"

okay... I'm sorry I have to clarify this...

IT HAS NOTHING TO DO WITH STAKING... I'm staking and mining this entire time

Status: 61 confirmations, broadcast through 2 nodes
Date: 11/30/2015 19:23
Source: Generated
Credit: 0.25180821 AMBER
Net amount: +0.25180821 AMBER

Status: 1097 confirmations
Date: 11/30/2015 07:55
Source: Generated
Credit: 0.08706849 AMBER
Net amount: +0.08706849 AMBER

Status: 1596 confirmations
Date: 11/30/2015 00:56
Source: Generated
Credit: 0.2249589 AMBER
Net amount: +0.2249589 AMBER

Don't get me wrong, I had some legit POS rewards too.  I'm just saying how else could I have forked unless a POS created a block that got rejected, but my wallet carried on anyhow.

I had the same problem this morning.  I was connected to 02.mooo and 03.mooo and staking was on.  I forked in a very short time.  Then I restored the DB and resynced with my wallet locked and staking off and I have been running on the correct chain all day.  I am not turning on staking until someone determines its not a problem or determines it is and fixed it.

[Slydrule]

my wallet stuck at block 599417 from yesterday

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.