|
NextGenCrypto
|
 |
October 15, 2015, 07:55:23 PM |
|
somebody want to fill my buy @2xxx?
They have to fill my few buy @3xxx first! Ain't gonna happen guys.  |
|
|
|
qwep
Legendary
 Offline
Activity: 1008
Merit: 1000
|
|
October 15, 2015, 07:59:18 PM |
|
somebody want to fill my buy @2xxx?
They have to fill my few buy @3xxx first! Ain't gonna happen guys. well i hope it does, the good thing about not having an over hype coin is you get a good price from the miners that dump, soon we will be able to generate coin with the new masternode. |
|
|
|
|
|
ShiftTeam (OP)
|
|
October 15, 2015, 09:50:36 PM |
|
You are right. We do not need hype. We will get this done. Cant give any estimate on time yet. Once we know, we will sure let everyone know  |
|
|
|
|
|
Rexxxem
|
|
October 15, 2015, 09:59:01 PM
Last edit: October 16, 2015, 02:44:14 AM by Rexxxem |
|
Edit:
Soloing to the wallet and ended up forking onto my own chain..
Any idea how that could have happened? Loss of peers or quick disruption in internet connectivity? Wasnt home to witness what caused it but definitely curious as to why..
|
|
|
|
|
|
GoldenEye
|
|
October 15, 2015, 11:19:42 PM |
|
What's wrong? (current github version) > I1016 01:16:34.182592 20827 downloader.go:278] Block synchronisation started
I1016 01:16:35.213820 20827 chain_manager.go:671] imported 0 block(s) (0 queued 1 ignored) including 0 txs in 765.873451ms. #161589 [f260e1cc / f260e1cc]
I1016 01:16:35.224563 20827 chain_manager.go:863] Bad block #161590 (29566ebd81b232a3ffd3f6a66155557a57df4bcfa2b028070653bc39913015e8)
I1016 01:16:35.224617 20827 chain_manager.go:864] invalid merkle root. received=2caf2adcee0429405dba24c5cbbb3a08a9eb8af4a241861e46458ca1334ebce7 got=a4a4809562fce34993db7189e2a935167ed8c3661b168f65694030d4fb81a01a
I1016 01:16:35.225581 20827 downloader.go:254] Synchronisation failed: hash fetching canceled (requested)
|
|
|
|
|
nhutphan
Member
Offline
Activity: 108
Merit: 10
|
|
October 15, 2015, 11:40:17 PM |
|
A lot of buying order now. So, it is very hard to fill up my order  |
Sell GTX750ti - GTX960 - GTX970 - HD7950 iceq...
Please pm here.
|
|
|
fartbags
Legendary
Offline
Activity: 1190
Merit: 1004
|
|
October 16, 2015, 12:35:40 AM |
|
somebody want to fill my buy @2xxx?
They have to fill my few buy @3xxx first! Ain't gonna happen guys. Anyone want to fill my @1xxx after? |
|
|
|
|
Lovethecoins
|
|
October 16, 2015, 01:48:02 AM |
|
somebody want to fill my buy @2xxx?
They have to fill my few buy @3xxx first! Ain't gonna happen guys. Anyone want to fill my @1xxx after? Sure let me just buy at 4000 first  |
|
|
|
qwep
Legendary
Offline
Activity: 1008
Merit: 1000
|
|
October 16, 2015, 03:01:41 AM |
|
somebody want to fill my buy @2xxx?
They have to fill my few buy @3xxx first! Ain't gonna happen guys. Anyone want to fill my @1xxx after? Sure let me just buy at 4000 first come on people dump at lease 10k make us feel happy! |
|
|
|
|
nhutphan
Member
Offline
Activity: 108
Merit: 10
|
|
October 16, 2015, 03:42:41 AM |
|
somebody want to fill my buy @2xxx?
They have to fill my few buy @3xxx first! Ain't gonna happen guys. Anyone want to fill my @1xxx after? Sure let me just buy at 4000 first come on people dump at lease 10k make us feel happy! Lucky me, I got enough yesterday. Only me buying at that time |
Sell GTX750ti - GTX960 - GTX970 - HD7950 iceq...
Please pm here.
|
|
|
|
ShiftTeam (OP)
|
|
October 16, 2015, 05:10:04 AM
Last edit: October 16, 2015, 06:03:51 AM by ShiftTeam |
|
What's wrong? (current github version) > I1016 01:16:34.182592 20827 downloader.go:278] Block synchronisation started
I1016 01:16:35.213820 20827 chain_manager.go:671] imported 0 block(s) (0 queued 1 ignored) including 0 txs in 765.873451ms. #161589 [f260e1cc / f260e1cc]
I1016 01:16:35.224563 20827 chain_manager.go:863] Bad block #161590 (29566ebd81b232a3ffd3f6a66155557a57df4bcfa2b028070653bc39913015e8)
I1016 01:16:35.224617 20827 chain_manager.go:864] invalid merkle root. received=2caf2adcee0429405dba24c5cbbb3a08a9eb8af4a241861e46458ca1334ebce7 got=a4a4809562fce34993db7189e2a935167ed8c3661b168f65694030d4fb81a01a
I1016 01:16:35.225581 20827 downloader.go:254] Synchronisation failed: hash fetching canceled (requested)
We will definitely have a look on this. This might be related to the above issue with the fork. The received one is correct, "root": "2caf2adcee0429405dba24c5cbbb3a08a9eb8af4a241861e46458ca1334ebce7"The basic idea is that someone who is out of sync with the rest of the network is giving you a bad block. Now, it could be someone solo mining for instance or the boot strapping nodes. My intuition says that this is network related, e.g. latency/slow propagation of blocks. Let me check and get back to you. EDIT. The London boot strapping node was totally f:ed and was on the wrong block. Peer node had panicked. I have made some small adjustments all the core nodes and lets see if that helps everyone to stay in sync. If you get any problem like the above one, do the following. ./shift removedb ./shift upgradedb This will resync the blockchain. That might be a good idea if this happens and you can not sync after "Synchronisation failed: hash fetching canceled" Regards |
|
|
|
|
wildduck
Legendary
Offline
Activity: 966
Merit: 1001
|
|
October 16, 2015, 06:10:52 AM |
|
Come on people dump some more in my buy orders |
|
|
|
|
|
GoldenEye
|
|
October 16, 2015, 08:21:08 AM
Last edit: October 16, 2015, 08:48:23 AM by GoldenEye |
|
What's wrong? (current github version) > I1016 01:16:34.182592 20827 downloader.go:278] Block synchronisation started
I1016 01:16:35.213820 20827 chain_manager.go:671] imported 0 block(s) (0 queued 1 ignored) including 0 txs in 765.873451ms. #161589 [f260e1cc / f260e1cc]
I1016 01:16:35.224563 20827 chain_manager.go:863] Bad block #161590 (29566ebd81b232a3ffd3f6a66155557a57df4bcfa2b028070653bc39913015e8)
I1016 01:16:35.224617 20827 chain_manager.go:864] invalid merkle root. received=2caf2adcee0429405dba24c5cbbb3a08a9eb8af4a241861e46458ca1334ebce7 got=a4a4809562fce34993db7189e2a935167ed8c3661b168f65694030d4fb81a01a
I1016 01:16:35.225581 20827 downloader.go:254] Synchronisation failed: hash fetching canceled (requested)
We will definitely have a look on this. This might be related to the above issue with the fork. The received one is correct, "root": "2caf2adcee0429405dba24c5cbbb3a08a9eb8af4a241861e46458ca1334ebce7"The basic idea is that someone who is out of sync with the rest of the network is giving you a bad block. Now, it could be someone solo mining for instance or the boot strapping nodes. My intuition says that this is network related, e.g. latency/slow propagation of blocks. Let me check and get back to you. EDIT. The London boot strapping node was totally f:ed and was on the wrong block. Peer node had panicked. I have made some small adjustments all the core nodes and lets see if that helps everyone to stay in sync. If you get any problem like the above one, do the following. ./shift removedb ./shift upgradedb This will resync the blockchain. That might be a good idea if this happens and you can not sync after "Synchronisation failed: hash fetching canceled" Regards After removedb and upgradedb stuck on block 30: > I1016 10:46:19.437411 3719 downloader.go:278] Block synchronisation started
I1016 10:46:20.663721 3719 chain_manager.go:671] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 948.418011ms. #1 [3dce3d75 / 3dce3d75]
I1016 10:46:29.336791 3719 chain_manager.go:863] Bad block #31 (a4e7785f19f984044087ed2b32523f8e86b2b487646c516cc690cc4e883bb9f3)
I1016 10:46:29.336853 3719 chain_manager.go:864] invalid merkle root. received=8a549bff93cf2aff5b5493f005515120e54fea0085061c91d0a103679052daa9 got=f5d060911dd5c66b2ca20d97f264149b3877cf615f67006c7e0cce409c250cc7
I1016 10:46:29.336991 3719 downloader.go:254] Synchronisation failed: hash fetching canceled (requested)
edit: console output updated |
|
|
|
|
|
ShiftTeam (OP)
|
|
October 16, 2015, 09:45:33 AM |
|
What's wrong? (current github version) > I1016 01:16:34.182592 20827 downloader.go:278] Block synchronisation started
I1016 01:16:35.213820 20827 chain_manager.go:671] imported 0 block(s) (0 queued 1 ignored) including 0 txs in 765.873451ms. #161589 [f260e1cc / f260e1cc]
I1016 01:16:35.224563 20827 chain_manager.go:863] Bad block #161590 (29566ebd81b232a3ffd3f6a66155557a57df4bcfa2b028070653bc39913015e8)
I1016 01:16:35.224617 20827 chain_manager.go:864] invalid merkle root. received=2caf2adcee0429405dba24c5cbbb3a08a9eb8af4a241861e46458ca1334ebce7 got=a4a4809562fce34993db7189e2a935167ed8c3661b168f65694030d4fb81a01a
I1016 01:16:35.225581 20827 downloader.go:254] Synchronisation failed: hash fetching canceled (requested)
We will definitely have a look on this. This might be related to the above issue with the fork. The received one is correct, "root": "2caf2adcee0429405dba24c5cbbb3a08a9eb8af4a241861e46458ca1334ebce7"The basic idea is that someone who is out of sync with the rest of the network is giving you a bad block. Now, it could be someone solo mining for instance or the boot strapping nodes. My intuition says that this is network related, e.g. latency/slow propagation of blocks. Let me check and get back to you. EDIT. The London boot strapping node was totally f:ed and was on the wrong block. Peer node had panicked. I have made some small adjustments all the core nodes and lets see if that helps everyone to stay in sync. If you get any problem like the above one, do the following. ./shift removedb ./shift upgradedb This will resync the blockchain. That might be a good idea if this happens and you can not sync after "Synchronisation failed: hash fetching canceled" Regards After removedb and upgradedb stuck on block 30: > I1016 10:46:19.437411 3719 downloader.go:278] Block synchronisation started
I1016 10:46:20.663721 3719 chain_manager.go:671] imported 1 block(s) (0 queued 0 ignored) including 0 txs in 948.418011ms. #1 [3dce3d75 / 3dce3d75]
I1016 10:46:29.336791 3719 chain_manager.go:863] Bad block #31 (a4e7785f19f984044087ed2b32523f8e86b2b487646c516cc690cc4e883bb9f3)
I1016 10:46:29.336853 3719 chain_manager.go:864] invalid merkle root. received=8a549bff93cf2aff5b5493f005515120e54fea0085061c91d0a103679052daa9 got=f5d060911dd5c66b2ca20d97f264149b3877cf615f67006c7e0cce409c250cc7
I1016 10:46:29.336991 3719 downloader.go:254] Synchronisation failed: hash fetching canceled (requested)
edit: console output updated Can you please try with version 0.3.0. Do a removedb and then start v0.3.0. Binaries are on github. And if that does not help.. remove everthing in chaindata directory.. be careful just to del files in that dir. Do NOT touch keystore |
|
|
|
|
|
GoldenEye
|
|
October 16, 2015, 11:59:47 AM |
|
Can you please try with version 0.3.0. Do a removedb and then start v0.3.0. Binaries are on github. And if that does not help.. remove everthing in chaindata directory.. be careful just to del files in that dir. Do NOT touch keystore
How to check out clone the old v3? |
|
|
|
|
qwep
Legendary
Offline
Activity: 1008
Merit: 1000
|
|
October 16, 2015, 01:04:23 PM |
|
Is the current reward block 1 Shift ?
|
|
|
|
|
|
ShiftTeam (OP)
|
|
October 16, 2015, 01:28:00 PM |
|
Can you please try with version 0.3.0. Do a removedb and then start v0.3.0. Binaries are on github. And if that does not help.. remove everthing in chaindata directory.. be careful just to del files in that dir. Do NOT touch keystore
How to check out clone the old v3? Read the OP. https://github.com/shiftcurrency/shift-executables/tree/master/Shift-v0.3.0Make sure you go to RAW before you download.. thats a valid url. |
|
|
|
|
|
ShiftTeam (OP)
|
|
October 16, 2015, 01:28:39 PM |
|
Is the current reward block 1 Shift ?
No 3 + uncles Regards |
|
|
|
|
|
GoldenEye
|
|
October 16, 2015, 01:50:37 PM
Last edit: October 16, 2015, 02:03:28 PM by GoldenEye |
|
Can you please try with version 0.3.0. Do a removedb and then start v0.3.0. Binaries are on github. And if that does not help.. remove everthing in chaindata directory.. be careful just to del files in that dir. Do NOT touch keystore
With the old v0.3 all seems fine. Block 31 was passed without problems and the client is syncing now. edit: Syncing successful, on block #216359 now. |
|
|
|
|
|
chalkboard17
|
|
October 16, 2015, 02:10:28 PM |
|
Is the current reward block 1 Shift ?
No 3 + uncles Regards Is the current block time 25s? Always when I verify block explorer it says block time <17.5s (right now 16.5) |
|
|
|
|
