1. We will share a fresh correct DB shortly so everyone can download it.
Edit: https://www.dropbox.com/s/m058ukshakusj4h/1.rar?dl=0
2. Meanwhile - start your wallets like that (in command line): AmberCoin-Qt.exe -connect=ambercoin01.mooo.com
When it syncs - start staking.
This should bring more stability.
Edit: In Linux ./AmberCoind -connect=ambercoin01.mooo.com
Topic: [AMBER] X13 POW/POS| 10k AMBER=0,01% SHARES | BUY, HOLD & GET DIVIDENDS in BTC/$ - page 149. (Read 407572 times)
November 26, 2015, 03:10:48 PM
November 26, 2015, 03:03:31 PM
sync from start, delete peer file too... if you'd like I can make a copy of my DB to help you out... I still have 12 connections, so I know i'm on the right chain
Reloading of a blockchain didn't solve a problem!
Restored again with 1 wrong node!
Please execute "getpeerinfo" and write the list of the correct nodes on a forum!
what ambercoindev really needs to do is ban the forked people from chain for a certain period of time... that way everyone can unfork with a DB rebuild.
November 26, 2015, 02:46:21 PM
sync from start, delete peer file too... if you'd like I can make a copy of my DB to help you out... I still have 12 connections, so I know i'm on the right chain
Reloading of a blockchain didn't solve a problem!
Restored again with 1 wrong node!
Please execute "getpeerinfo" and write the list of the correct nodes on a forum!
u have all nodes in the op.
November 26, 2015, 02:42:41 PM
sync from start, delete peer file too... if you'd like I can make a copy of my DB to help you out... I still have 12 connections, so I know i'm on the right chain
Reloading of a blockchain didn't solve a problem!
Restored again with 1 wrong node!
Please execute "getpeerinfo" and write the list of the correct nodes on a forum!
November 26, 2015, 02:37:03 PM
592177, time is 21:24
Mostly to see how time is handled by bitcointalk.org
bitcointalk.org = UTC timezoneMostly to see how time is handled by bitcointalk.org
1 connections, staking like hell, every minute 0.x AMBER
I have 2 wallets , second @ 592159 (first wallet is the same time 592187), switching between 0/1 connections and "last block generated 3 seconds ago"
November 26, 2015, 02:25:23 PM
592177, time is 21:24
Mostly to see how time is handled by bitcointalk.org
Mostly to see how time is handled by bitcointalk.org
November 26, 2015, 12:21:35 PM
592022 im on that block. My connectıon lost now 0 connection. İ have 3 stakes on the confirmations probably all of them orphan now.
Main node is on 591,996.
We are investigating the issue.
November 26, 2015, 12:20:16 PM
atm just 1-2 active connections but staking fine.
November 26, 2015, 12:03:52 PM
592022 im on that block. My connectıon lost now 0 connection. İ have 3 stakes on the confirmations probably all of them orphan now.
Main node is on 591,996.
We are investigating the issue.
November 26, 2015, 12:00:30 PM
592022 im on that block. My connectıon lost now 0 connection. İ have 3 stakes on the confirmations probably all of them orphan now.
November 26, 2015, 11:53:44 AM
Sync from the beginning. It takes time but helped my wallet now its staking ok. Deleted all but wallet.dat 
What block height are you now at?
connected 24.18.171.156:31982
send version message: version 90001, blocks=592014, us=37.33.81.77:31982, them=24.18.171.156:31982, peer=24.18.171.156:31982
socket closed
November 26, 2015, 11:25:19 AM
Sync from the beginning. It takes time but helped my wallet now its staking ok. Deleted all but wallet.dat
What block height are you now at?
November 26, 2015, 11:00:11 AM
Sync from the beginning. It takes time but helped my wallet now its staking ok. Deleted all but wallet.dat
November 26, 2015, 10:33:07 AM
I shut my wallet down until a fix is made. I am only staking and am apparently on a wrong fork. Every stake orphans.
November 26, 2015, 10:24:59 AM
Ccex looks like still on maintanance.
I need some bitcoin but looks like i should continue to wait.
I need some bitcoin but looks like i should continue to wait.
November 26, 2015, 09:50:53 AM
Only 1 active node!
FORK again?
Two wallets, different IP and computer, 3 connections both.FORK again?
Code:
addnode=176.9.165.51:31982 v3.0.0.3
Code:
socket recv error 104
disconnecting node 104.238.177.80:31982
received block 000000079379d2273a66
Misbehaving: 176.9.165.51:31982 (0 -> 100) DISCONNECTING
disconnecting node 176.9.165.51:31982
ERROR: ProcessBlock() : block with too little proof-of-work
disconnecting node 104.238.177.80:31982
received block 000000079379d2273a66
Misbehaving: 176.9.165.51:31982 (0 -> 100) DISCONNECTING
disconnecting node 176.9.165.51:31982
ERROR: ProcessBlock() : block with too little proof-of-work
3 hours ago was period about 1...1.5 hours when all staking was orphaned:
"Status: conflicted, broadcast through 2 node(s)"
"Status: conflicted, broadcast through 1 node(s)"
before this orphaned/conflicting period everything was like:
"Status: 694 confirmations, broadcast through 16 node(s)"
November 26, 2015, 09:50:35 AM
Only 1 active node!
FORK again?
sync from start, delete peer file too... if you'd like I can make a copy of my DB to help you out... I still have 12 connections, so I know i'm on the right chain FORK again?
Code:
addnode=176.9.165.51:31982 v3.0.0.3
Code:
socket recv error 104
disconnecting node 104.238.177.80:31982
received block 000000079379d2273a66
Misbehaving: 176.9.165.51:31982 (0 -> 100) DISCONNECTING
disconnecting node 176.9.165.51:31982
ERROR: ProcessBlock() : block with too little proof-of-work
disconnecting node 104.238.177.80:31982
received block 000000079379d2273a66
Misbehaving: 176.9.165.51:31982 (0 -> 100) DISCONNECTING
disconnecting node 176.9.165.51:31982
ERROR: ProcessBlock() : block with too little proof-of-work
November 26, 2015, 09:37:26 AM
Only 1 active node!
FORK again?
FORK again?
Code:
addnode=176.9.165.51:31982 v3.0.0.3
Code:
socket recv error 104
disconnecting node 104.238.177.80:31982
received block 000000079379d2273a66
Misbehaving: 176.9.165.51:31982 (0 -> 100) DISCONNECTING
disconnecting node 176.9.165.51:31982
ERROR: ProcessBlock() : block with too little proof-of-work
disconnecting node 104.238.177.80:31982
received block 000000079379d2273a66
Misbehaving: 176.9.165.51:31982 (0 -> 100) DISCONNECTING
disconnecting node 176.9.165.51:31982
ERROR: ProcessBlock() : block with too little proof-of-work
November 25, 2015, 06:30:44 PM
Still no response to my open ticket on C-Cex, but I see that they have Amber back in maintenance mode again.
I'm not sure how they handle cases like this? Anyone know if they replace lost coins when they mess up?
they could have done what I did, which caused me to be on a forked chain... amber dev released a wallet 3.0.0.2 right before 3.0.0.3... if you upgraded to .2 and ran it, it forked your chain even if you upgraded to .3... they are likely going to have to resync completely to be back on the right chain.I'm not sure how they handle cases like this? Anyone know if they replace lost coins when they mess up?
Yeah that's what I'm concerned about. I believe that means the amber I sent from their site last night is now on the wrong chain. Not sure how they'll handle that, but I'll be sure to let everyone here know.
it'll show back up in your wallet once they resync
November 25, 2015, 05:36:29 PM
Dang it... I missed the update to the update. I stake 40 miles from my home so I'll be waiting until Friday to correct my situation.
Jump to: