cryptofarmer
|
|
December 14, 2016, 11:17:24 PM |
|
Where's the last message you posted @redking? It's just being deleted?
|
|
|
|
cryptofarmer
|
|
December 14, 2016, 11:19:28 PM |
|
chain c-cex.
We found our wallet sync does not match official block explorer sync. That's why we disabled wallet for now and do not register deposits. Now block explorer is down. We will wait until it will be up again and check if we on the same chain. Well, can you please put the wallet back online for 24 hours so everyone that has deposits sent to your exchange can receive them?? You really should have tweet about this before just shutting the wallet down, this messed alot of people up. I agree, A lot of coins are now send to basicaly a black hole.... Because miners have autopayout, they won't notice until its to late.
|
|
|
|
felixbrucker
|
|
December 14, 2016, 11:43:04 PM |
|
Where's the last message you posted @redking? It's just being deleted? wondering the same, would be a shame
|
|
|
|
synthgauge
|
|
December 14, 2016, 11:50:31 PM Last edit: December 15, 2016, 09:48:27 PM by synthgauge |
|
I dont hate the guy, he makes living from 0.01 BTC contributions and thats the way he has been living since he was born. I bet hes vietnamese struggling heroine addiction, that explains why there are 100 new ICOs every day.
|
|
|
|
|
c-cex
Legendary
Offline
Activity: 1498
Merit: 1001
CryptoCurrency EXchange: https://c-cex.com
|
|
December 15, 2016, 09:52:04 AM |
|
We just update our wallet to latest from github but it does not sync. It was able to get 3 blocks and then stop. We tried to sync from scratch with fresh wallet.dat - same issue.
Here is what happening in debug.log for freshy launched wallet with empty data dir:
SetBestChain: new best=00000f8923e2585d5cbd height=1 trust=2097154 blocktrust=1048577 date=11/08/16 17:38:49 ProcessBlock: ACCEPTED received block 00000047b8d42ab011bc SetBestChain: new best=00000047b8d42ab011bc height=2 trust=3145731 blocktrust=1048577 date=11/21/16 05:06:15 ProcessBlock: ACCEPTED received block 0000004b8b45189977df SetBestChain: new best=0000004b8b45189977df height=3 trust=4194308 blocktrust=1048577 date=11/21/16 05:08:17 ProcessBlock: ACCEPTED received block 000000299fe41f7a5aa0 ERROR: AcceptBlock() : incorrect proof-of-work ERROR: ProcessBlock() : AcceptBlock FAILED
After that it disconnects from node and does not get any new block. Anybody can suggest a solution?
About all deposits sent to C-CEX wallet. They are all valid and will be registered once we will be able to sync.
|
|
|
|
redkinggg
|
|
December 15, 2016, 11:35:14 AM |
|
We just update our wallet to latest from github but it does not sync. It was able to get 3 blocks and then stop. We tried to sync from scratch with fresh wallet.dat - same issue.
Here is what happening in debug.log for freshy launched wallet with empty data dir:
SetBestChain: new best=00000f8923e2585d5cbd height=1 trust=2097154 blocktrust=1048577 date=11/08/16 17:38:49 ProcessBlock: ACCEPTED received block 00000047b8d42ab011bc SetBestChain: new best=00000047b8d42ab011bc height=2 trust=3145731 blocktrust=1048577 date=11/21/16 05:06:15 ProcessBlock: ACCEPTED received block 0000004b8b45189977df SetBestChain: new best=0000004b8b45189977df height=3 trust=4194308 blocktrust=1048577 date=11/21/16 05:08:17 ProcessBlock: ACCEPTED received block 000000299fe41f7a5aa0 ERROR: AcceptBlock() : incorrect proof-of-work ERROR: ProcessBlock() : AcceptBlock FAILED
After that it disconnects from node and does not get any new block. Anybody can suggest a solution?
About all deposits sent to C-CEX wallet. They are all valid and will be registered once we will be able to sync.
You need to use the same wallet you had before, or all pending deposits will not go through. Simply upload the exisitng wallet you originally had.
|
|
|
|
CS86
Newbie
Offline
Activity: 36
Merit: 0
|
|
December 15, 2016, 12:00:31 PM |
|
From Nova:
addnode=116.62.9.41:5556 addnode=121.42.154.119:5556 addnode=139.162.90.238:5556 addnode=139.59.177.141:5556 addnode=158.69.238.192:5556 addnode=185.45.192.150:5556 addnode=189.10.64.117:5556 addnode=200.181.80.3:5556 addnode=222.187.224.93:5556 addnode=222.187.224.97:5556 addnode=46.0.205.147:5556 addnode=5.189.155.182:5556 addnode=85.236.188.28:23883 addnode=85.24.143.58:5556 addnode=85.25.195.161:5556 addnode=86.5.90.211:5556 addnode=92.63.57.235:5556 addnode=92.63.57.241:5556 addnode=92.63.57.24:5556 addnode=95.85.33.201:5556
|
|
|
|
barrysty1e
|
|
December 15, 2016, 12:15:16 PM |
|
We just update our wallet to latest from github but it does not sync. It was able to get 3 blocks and then stop. We tried to sync from scratch with fresh wallet.dat - same issue.
Here is what happening in debug.log for freshy launched wallet with empty data dir:
SetBestChain: new best=00000f8923e2585d5cbd height=1 trust=2097154 blocktrust=1048577 date=11/08/16 17:38:49 ProcessBlock: ACCEPTED received block 00000047b8d42ab011bc SetBestChain: new best=00000047b8d42ab011bc height=2 trust=3145731 blocktrust=1048577 date=11/21/16 05:06:15 ProcessBlock: ACCEPTED received block 0000004b8b45189977df SetBestChain: new best=0000004b8b45189977df height=3 trust=4194308 blocktrust=1048577 date=11/21/16 05:08:17 ProcessBlock: ACCEPTED received block 000000299fe41f7a5aa0 ERROR: AcceptBlock() : incorrect proof-of-work ERROR: ProcessBlock() : AcceptBlock FAILED
After that it disconnects from node and does not get any new block. Anybody can suggest a solution?
About all deposits sent to C-CEX wallet. They are all valid and will be registered once we will be able to sync.
git clone https://github.com/xenixcoin/xenixcoin.git cd xenixcoin git checkout 4f64992f5d cd src/leveldb chmod +x build_detect_platform make clean make libleveldb.a libmemenv.a cd .. make -f makefile.unix -j4 strip xenixd
root@harry:/usr/xenixcoin/src# ./xenixd -server -daemon -rpcuser=barrystyle -rpcpassword= -rpcbind=127.0.0.1 -rpcallowip=127.0.0.1 -datadir=datadir getmininginfo { "blocks" : 956, "currentblocksize" : 0, "currentblocktx" : 0, "difficulty" : { "proof-of-work" : 703.28903794, "proof-of-stake" : 0.00068651, "search-interval" : 0 }, "blockvalue" : 8400000, "netmhashps" : 3843.00689259, "netstakeweight" : 534.45401973, "errors" : "", "pooledtx" : 0, "stakeweight" : { "minimum" : 0, "maximum" : 0, "combined" : 0 }, "stakeinterest" : 1000000, "testnet" : false }
there you go c-cex; currently at block 956 with no extra prodding. dev's own nodes are giving out incorrect proof of work at block 3, but this gets ignored quickly as other legitimate hosts step in with the correct block data. ready... go! FYI 'git checkout 4f64992f5d' takes you to the source tree before bad checkpoints added by dev.
|
my father wears sneakers in the pool
|
|
|
cryptofarmer
|
|
December 15, 2016, 12:43:13 PM |
|
We just update our wallet to latest from github but it does not sync. It was able to get 3 blocks and then stop. We tried to sync from scratch with fresh wallet.dat - same issue.
Here is what happening in debug.log for freshy launched wallet with empty data dir:
SetBestChain: new best=00000f8923e2585d5cbd height=1 trust=2097154 blocktrust=1048577 date=11/08/16 17:38:49 ProcessBlock: ACCEPTED received block 00000047b8d42ab011bc SetBestChain: new best=00000047b8d42ab011bc height=2 trust=3145731 blocktrust=1048577 date=11/21/16 05:06:15 ProcessBlock: ACCEPTED received block 0000004b8b45189977df SetBestChain: new best=0000004b8b45189977df height=3 trust=4194308 blocktrust=1048577 date=11/21/16 05:08:17 ProcessBlock: ACCEPTED received block 000000299fe41f7a5aa0 ERROR: AcceptBlock() : incorrect proof-of-work ERROR: ProcessBlock() : AcceptBlock FAILED
After that it disconnects from node and does not get any new block. Anybody can suggest a solution?
About all deposits sent to C-CEX wallet. They are all valid and will be registered once we will be able to sync.
git clone https://github.com/xenixcoin/xenixcoin.git cd xenixcoin git checkout 4f64992f5d cd src/leveldb chmod +x build_detect_platform make clean make libleveldb.a libmemenv.a cd .. make -f makefile.unix -j4 strip xenixd
root@harry:/usr/xenixcoin/src# ./xenixd -server -daemon -rpcuser=barrystyle -rpcpassword= -rpcbind=127.0.0.1 -rpcallowip=127.0.0.1 -datadir=datadir getmininginfo { "blocks" : 956, "currentblocksize" : 0, "currentblocktx" : 0, "difficulty" : { "proof-of-work" : 703.28903794, "proof-of-stake" : 0.00068651, "search-interval" : 0 }, "blockvalue" : 8400000, "netmhashps" : 3843.00689259, "netstakeweight" : 534.45401973, "errors" : "", "pooledtx" : 0, "stakeweight" : { "minimum" : 0, "maximum" : 0, "combined" : 0 }, "stakeinterest" : 1000000, "testnet" : false }
there you go c-cex; currently at block 956 with no extra prodding. dev's own nodes are giving out incorrect proof of work at block 3, but this gets ignored quickly as other legitimate hosts step in with the correct block data. ready... go! FYI 'git checkout 4f64992f5d' takes you to the source tree before bad checkpoints added by dev. So what do the miners want? Wich chain to follow? Because of the problems syncing to the "official" chain. I suggest we follow chain with blockheight now ~956. If not please provide proper source and nodes.
|
|
|
|
redkinggg
|
|
December 15, 2016, 01:23:41 PM |
|
We just update our wallet to latest from github but it does not sync. It was able to get 3 blocks and then stop. We tried to sync from scratch with fresh wallet.dat - same issue.
Here is what happening in debug.log for freshy launched wallet with empty data dir:
SetBestChain: new best=00000f8923e2585d5cbd height=1 trust=2097154 blocktrust=1048577 date=11/08/16 17:38:49 ProcessBlock: ACCEPTED received block 00000047b8d42ab011bc SetBestChain: new best=00000047b8d42ab011bc height=2 trust=3145731 blocktrust=1048577 date=11/21/16 05:06:15 ProcessBlock: ACCEPTED received block 0000004b8b45189977df SetBestChain: new best=0000004b8b45189977df height=3 trust=4194308 blocktrust=1048577 date=11/21/16 05:08:17 ProcessBlock: ACCEPTED received block 000000299fe41f7a5aa0 ERROR: AcceptBlock() : incorrect proof-of-work ERROR: ProcessBlock() : AcceptBlock FAILED
After that it disconnects from node and does not get any new block. Anybody can suggest a solution?
About all deposits sent to C-CEX wallet. They are all valid and will be registered once we will be able to sync.
git clone https://github.com/xenixcoin/xenixcoin.git cd xenixcoin git checkout 4f64992f5d cd src/leveldb chmod +x build_detect_platform make clean make libleveldb.a libmemenv.a cd .. make -f makefile.unix -j4 strip xenixd
root@harry:/usr/xenixcoin/src# ./xenixd -server -daemon -rpcuser=barrystyle -rpcpassword= -rpcbind=127.0.0.1 -rpcallowip=127.0.0.1 -datadir=datadir getmininginfo { "blocks" : 956, "currentblocksize" : 0, "currentblocktx" : 0, "difficulty" : { "proof-of-work" : 703.28903794, "proof-of-stake" : 0.00068651, "search-interval" : 0 }, "blockvalue" : 8400000, "netmhashps" : 3843.00689259, "netstakeweight" : 534.45401973, "errors" : "", "pooledtx" : 0, "stakeweight" : { "minimum" : 0, "maximum" : 0, "combined" : 0 }, "stakeinterest" : 1000000, "testnet" : false }
there you go c-cex; currently at block 956 with no extra prodding. dev's own nodes are giving out incorrect proof of work at block 3, but this gets ignored quickly as other legitimate hosts step in with the correct block data. ready... go! FYI 'git checkout 4f64992f5d' takes you to the source tree before bad checkpoints added by dev. So what do the miners want? Wich chain to follow? Because of the problems syncing to the "official" chain. I suggest we follow chain with blockheight now ~956. If not please provide proper source and nodes. I agree. Stay with chain with blockheight now ~956....which ccex had up already. Why the fuss and taking down the wallet...I dont know.
|
|
|
|
stiger25
Newbie
Offline
Activity: 47
Merit: 0
|
|
December 15, 2016, 01:25:21 PM |
|
I sent you a message to give you the solution We just update our wallet to latest from github but it does not sync. It was able to get 3 blocks and then stop. We tried to sync from scratch with fresh wallet.dat - same issue.
Here is what happening in debug.log for freshy launched wallet with empty data dir:
SetBestChain: new best=00000f8923e2585d5cbd height=1 trust=2097154 blocktrust=1048577 date=11/08/16 17:38:49 ProcessBlock: ACCEPTED received block 00000047b8d42ab011bc SetBestChain: new best=00000047b8d42ab011bc height=2 trust=3145731 blocktrust=1048577 date=11/21/16 05:06:15 ProcessBlock: ACCEPTED received block 0000004b8b45189977df SetBestChain: new best=0000004b8b45189977df height=3 trust=4194308 blocktrust=1048577 date=11/21/16 05:08:17 ProcessBlock: ACCEPTED received block 000000299fe41f7a5aa0 ERROR: AcceptBlock() : incorrect proof-of-work ERROR: ProcessBlock() : AcceptBlock FAILED
After that it disconnects from node and does not get any new block. Anybody can suggest a solution?
About all deposits sent to C-CEX wallet. They are all valid and will be registered once we will be able to sync.
|
|
|
|
barrysty1e
|
|
December 15, 2016, 01:25:34 PM |
|
So what do the miners want? Wich chain to follow? Because of the problems syncing to the "official" chain. I suggest we follow chain with blockheight now ~956. If not please provide proper source and nodes.
https://github.com/barrystyle/xenixcoinmodified pre-checkpoint with two 'honest' nodes set as seeds. have fun all.
|
my father wears sneakers in the pool
|
|
|
cryptofarmer
|
|
December 15, 2016, 01:29:59 PM |
|
So what do the miners want? Wich chain to follow? Because of the problems syncing to the "official" chain. I suggest we follow chain with blockheight now ~956. If not please provide proper source and nodes.
https://github.com/barrystyle/xenixcoinmodified pre-checkpoint with two 'honest' nodes set as seeds. have fun all. Synced to what chain / height?
|
|
|
|
redkinggg
|
|
December 15, 2016, 01:34:18 PM |
|
So what do the miners want? Wich chain to follow? Because of the problems syncing to the "official" chain. I suggest we follow chain with blockheight now ~956. If not please provide proper source and nodes.
https://github.com/barrystyle/xenixcoinmodified pre-checkpoint with two 'honest' nodes set as seeds. have fun all. Thanks barry. How you been my aussie brother?!?!
|
|
|
|
barrysty1e
|
|
December 15, 2016, 01:43:59 PM |
|
Synced to what chain / height?
the correct chain (block 961), at this second. i say the correct chain, as the other chain is invalid (block 3 PoW incorrect). Thanks barry. How you been my aussie brother?!?!
good man, still using those antminers to save heating cost over winter good to see you around bud
|
my father wears sneakers in the pool
|
|
|
stiger25
Newbie
Offline
Activity: 47
Merit: 0
|
|
December 15, 2016, 01:50:19 PM |
|
We modify the block reward
The first block generates 10000000 currency (premine) From 2 to 100 block 0 currency From 101 to 575 block 19 currency From 576 to 3000000 block 0.084 currency
|
|
|
|
felixbrucker
|
|
December 15, 2016, 01:50:45 PM |
|
actually those checkpoints secure the blockchain (see https://bitcointalk.org/index.php?topic=194078.0) to prevent additional chains with really fast asics now the chain used by ccex and dutch-mining is off of the "official" one, but thats another matter if one wants to sync to the official chain i suggest using the addnodes provided by nova the other way round use those by ccex
|
|
|
|
EpyxZ
|
|
December 15, 2016, 01:56:05 PM |
|
actually those checkpoints secure the blockchain (see https://bitcointalk.org/index.php?topic=194078.0) to prevent additional chains with really fast asics now the chain used by ccex and dutch-mining is off of the "official" one, but thats another matter if one wants to sync to the official chain i suggest using the addnodes provided by nova the other way round use those by ccex It's too close to xmas to be using that language man :p just gave me a OMG we got AA batteries but needed AAA. lol. XENIX the official xmas coin :p
|
|
|
|
barrysty1e
|
|
December 15, 2016, 02:43:56 PM |
|
actually those checkpoints secure the blockchain (see https://bitcointalk.org/index.php?topic=194078.0) to prevent additional chains with really fast asics now the chain used by ccex and dutch-mining is off of the "official" one, but thats another matter if one wants to sync to the official chain i suggest using the addnodes provided by nova the other way round use those by ccex well aware of the reasons for having checkpoint blocks, just as well as their potential for abuse. trying connection 208.163.158.201 lastseen=0.0hrs received block 00000f8923e2585d5cbd SetBestChain: new best=00000f8923e2585d5cbd height=1 trust=2097154 blocktrust=1048577 date=11/08/16 17:38:49 ProcessBlock: ACCEPTED received block 00000047b8d42ab011bc SetBestChain: new best=00000047b8d42ab011bc height=2 trust=3145731 blocktrust=1048577 date=11/21/16 05:06:15 ProcessBlock: ACCEPTED received block 0000004b8b45189977df * hyuck, we're gonna need minimum PoW 1e0fffff SetBestChain: new best=0000004b8b45189977df height=3 trust=4194308 blocktrust=1048577 date=11/21/16 05:08:17 ProcessBlock: ACCEPTED received block 000000299fe41f7a5aa0 * hyuck, we're gonna need minimum PoW 1e09a06c ERROR: AcceptBlock() : incorrect proof-of-work ERROR: ProcessBlock() : AcceptBlock FAILED Misbehaving: 92.63.57.24:5556 (0 -> 100) DISCONNECTING disconnecting node 92.63.57.24 getblocks -1 to 00000000000000000000 limit 500 getblocks -1 to 00000000000000000000 limit 500
for the sake of being a team player, rather than a dick; check the 'hyucks' above. some debug code i've thrown in whilst attempting to sync against the 'official' nodes. block 4 needs to be 1e09a06c, but in xenixblockchain.com; it is listed as 1e0340dac-cex has been on the correct chain from the start; not sure what happened with nova.
|
my father wears sneakers in the pool
|
|
|
|