[ANN][SHIFT] The New Web | IPFS/Phantom | ShiftNrg.org Hosted Decentralized! - page 220.

nhutphan

member

Activity: 108

Merit: 10

Quote from: fartbags on October 19, 2015, 02:12:16 PM

Quote from: reb0rn21 on October 19, 2015, 11:15:17 AM

Quote from: Maverick69 on October 19, 2015, 10:54:11 AM

Someone has more than 80k SHIFT on Bittrex! Shocked

This is a really good time to buy!

And if that 80K person decide to go in short..... :d

Then there won't be enough buy support for him to dump! LOL. Maybe I can get some more for 500 satoshi.

500 satoshi? Very interesting. Good luck!

fartbags

legendary

Activity: 1190

Merit: 1004

Quote from: reb0rn21 on October 19, 2015, 11:15:17 AM

Quote from: Maverick69 on October 19, 2015, 10:54:11 AM

Someone has more than 80k SHIFT on Bittrex! Shocked

This is a really good time to buy!

And if that 80K person decide to go in short..... :d

Then there won't be enough buy support for him to dump! LOL. Maybe I can get some more for 500 satoshi.

reb0rn21

legendary

Activity: 1899

Merit: 1024

Quote from: Maverick69 on October 19, 2015, 10:54:11 AM

Someone has more than 80k SHIFT on Bittrex! Shocked

This is a really good time to buy!

And if that 80K person decide to go in short..... :d

Maverick69

sr. member

Activity: 458

Merit: 250

Someone has more than 80k SHIFT on Bittrex! Shocked

This is a really good time to buy!

Colonel Crouton

sr. member

Activity: 354

Merit: 252

Quote from: Argwai96 on October 18, 2015, 11:59:59 AM

it looks like a good time to setup some buy support for the upcoming dump.

It should be a big one. Hopefully it won't sink the price too much.

nhutphan

member

Activity: 108

Merit: 10

Quote from: Argwai96 on October 18, 2015, 11:59:59 AM

it looks like a good time to setup some buy support for the upcoming dump.

I came back after a day played around with Soil. That is a great time to mine and buy SHIFT. I hope dev will update next 2 - 3 weeks. Then, we will speed up 2-3 steps ahead compare to EXP or SOIL.

Cheers!

Argwai96

legendary

Activity: 1036

Merit: 1000

Thug for life!

it looks like a good time to setup some buy support for the upcoming dump.

ShiftTeam

hero member

Activity: 483

Merit: 510

The Shift Team

Quote from: GoldenEye on October 16, 2015, 09:50:37 AM

Quote from: ShiftTeam on October 16, 2015, 05:45:33 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

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.

Ok we will look into that. We have some theories

ShiftTeam

hero member

Activity: 483

Merit: 510

The Shift Team

Quote from: qwep on October 16, 2015, 10:26:33 AM

Quote from: chalkboard17 on October 16, 2015, 10:10:28 AM

Quote from: ShiftTeam on October 16, 2015, 09:28:39 AM

Quote from: qwep on October 16, 2015, 09:04:23 AM

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)

oh ok, yea i wanted to figure out pretty much how many coins are mined daily so i could setup my buy support base on those numbers.

The static blocktime is 25s, that solved the number of orphan blocks we had for a while. Alot of blocks did not had the time to propagate the network in time.. simple speaking. The target from the beginning was 17 seconds. It is pretty close.. the static blocktime is not the final blocktime in any way. All stats are on blockexplorer.

Exp had 60s blocktime but was several minuted before their patch. In this case.. use block explorer.. it does not lie.

qwep

legendary

Activity: 1008

Merit: 1000

Quote from: chalkboard17 on October 16, 2015, 10:10:28 AM

Quote from: ShiftTeam on October 16, 2015, 09:28:39 AM

Quote from: qwep on October 16, 2015, 09:04:23 AM

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)

oh ok, yea i wanted to figure out pretty much how many coins are mined daily so i could setup my buy support base on those numbers.

chalkboard17

sr. member

Activity: 484

Merit: 251

Quote from: ShiftTeam on October 16, 2015, 09:28:39 AM

Quote from: qwep on October 16, 2015, 09:04:23 AM

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)

GoldenEye

hero member

Activity: 601

Merit: 500

Quote from: ShiftTeam on October 16, 2015, 05:45:33 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

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.

ShiftTeam

hero member

Activity: 483

Merit: 510

The Shift Team

Quote from: qwep on October 16, 2015, 09:04:23 AM

Is the current reward block 1 Shift ?

No 3 + uncles

Regards

ShiftTeam

hero member

Activity: 483

Merit: 510

The Shift Team

Quote from: GoldenEye on October 16, 2015, 07:59:47 AM

Quote from: ShiftTeam on October 16, 2015, 05:45:33 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?

Read the OP. https://github.com/shiftcurrency/shift-executables/tree/master/Shift-v0.3.0

Make sure you go to RAW before you download.. thats a valid url.

qwep

legendary

Activity: 1008

Merit: 1000

Is the current reward block 1 Shift ?

GoldenEye

hero member

Activity: 601

Merit: 500

Quote from: ShiftTeam on October 16, 2015, 05:45:33 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?

ShiftTeam

hero member

Activity: 483

Merit: 510

The Shift Team

Quote from: GoldenEye on October 16, 2015, 04:21:08 AM

Quote from: ShiftTeam on October 16, 2015, 01:10:04 AM

Quote from: GoldenEye on October 15, 2015, 07:19:42 PM

What's wrong? (current github version)

Code:

> 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:

Code:

> 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

hero member

Activity: 601

Merit: 500

Quote from: ShiftTeam on October 16, 2015, 01:10:04 AM

Quote from: GoldenEye on October 15, 2015, 07:19:42 PM

What's wrong? (current github version)

Code:

> 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:

Code:

> 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

wildduck

legendary

Activity: 966

Merit: 1001

Come on people dump some more in my buy orders

ShiftTeam

hero member

Activity: 483

Merit: 510

The Shift Team

Quote from: GoldenEye on October 15, 2015, 07:19:42 PM

What's wrong? (current github version)

Code:

> 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

Topic: [ANN][SHIFT] The New Web | IPFS/Phantom | ShiftNrg.org Hosted Decentralized! - page 220. (Read 547569 times)