[HYP] HyperStake | Generous Reward Staking | Advanced Staking Controls & Wallet

[presstab]

This coins daemon is 100% impossible to sync...

ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 31a471982f272fefaae842dbaa0ab1507b014162c40310c4dde0087714a66675
received block df1f9b6cb2da78fa9fbf
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block df1f9b6cb2da78fa9fbf7a651f5936e29d02b2fc0949d824524019e78521c45d
received block 2d9d163b348d29d5d66f
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 2d9d163b348d29d5d66f8c65497ce481a26c776c7dcc0a565bcabd75ba34af5b
received block f1385230f46c3040bce6
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block f1385230f46c3040bce674e0b6787729e311429ebf60226081dc2ceba9a48d24
received block 30f335481d6b4831eddb
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 30f335481d6b4831eddbd0151abe01db5efc63e5c2ae92b2a1ac7da9b8c70aeb
received block db95163b1389a1fed6ae
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block db95163b1389a1fe

I've synced around 170k blocks in 24 hours, at this rate it will take me over 10 days to sync the whole 1.9m blocks.

Is it just me or is this normal?

It can definitely get tricky. I would follow the bootstrap instructions from the op if I were you.

[1714773807]

1714773807

[1714773807]

1714773807

[1714773807]

1714773807

[Kushedout]

Presstab, the hourly bootstrap might not have been updated for a while.  Syncing my self on a new box at the moment, I'll post an updated bootsrap when done.

[iantunc]

Presstab, the hourly bootstrap might not have been updated for a while.  Syncing my self on a new box at the moment, I'll post an updated bootsrap when done.

The hourly bootstrap is updated regularly by a task manager, the wallet daemon is supervised by a process manager.

Takes about 3-4 hours to sync.

[altcoiner-]

This coins daemon is 100% impossible to sync...

ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 31a471982f272fefaae842dbaa0ab1507b014162c40310c4dde0087714a66675
received block df1f9b6cb2da78fa9fbf
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block df1f9b6cb2da78fa9fbf7a651f5936e29d02b2fc0949d824524019e78521c45d
received block 2d9d163b348d29d5d66f
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 2d9d163b348d29d5d66f8c65497ce481a26c776c7dcc0a565bcabd75ba34af5b
received block f1385230f46c3040bce6
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block f1385230f46c3040bce674e0b6787729e311429ebf60226081dc2ceba9a48d24
received block 30f335481d6b4831eddb
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 30f335481d6b4831eddbd0151abe01db5efc63e5c2ae92b2a1ac7da9b8c70aeb
received block db95163b1389a1fed6ae
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block db95163b1389a1fe

I've synced around 170k blocks in 24 hours, at this rate it will take me over 10 days to sync the whole 1.9m blocks.

Is it just me or is this normal?

It can definitely get tricky. I would follow the bootstrap instructions from the op if I were you.

OP doesn't provide any info for me
linux VPS, and I can't even find the data folder.
Can anyone elaborate for me? The syncing is becoming painful

[Lightsplasher]

This coins daemon is 100% impossible to sync...

ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 31a471982f272fefaae842dbaa0ab1507b014162c40310c4dde0087714a66675
received block df1f9b6cb2da78fa9fbf
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block df1f9b6cb2da78fa9fbf7a651f5936e29d02b2fc0949d824524019e78521c45d
received block 2d9d163b348d29d5d66f
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 2d9d163b348d29d5d66f8c65497ce481a26c776c7dcc0a565bcabd75ba34af5b
received block f1385230f46c3040bce6
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block f1385230f46c3040bce674e0b6787729e311429ebf60226081dc2ceba9a48d24
received block 30f335481d6b4831eddb
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 30f335481d6b4831eddbd0151abe01db5efc63e5c2ae92b2a1ac7da9b8c70aeb
received block db95163b1389a1fed6ae
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block db95163b1389a1fe

I've synced around 170k blocks in 24 hours, at this rate it will take me over 10 days to sync the whole 1.9m blocks.

Is it just me or is this normal?

It can definitely get tricky. I would follow the bootstrap instructions from the op if I were you.

OP doesn't provide any info for me
linux VPS, and I can't even find the data folder.
Can anyone elaborate for me? The syncing is becoming painful

Specifically the data directory should be named .HyperStake and located under the home directory.  "ls -ah" should show it there.  I hope you get it syncing.

To quote OP:

Syncing Notice: When syncing the chain, the client can get stuck occasionally and need to be restarted in order to continue syncing. Please consider using the bootstrap for the quickest sync.

Block Chain Bootstrap
Bootstrap file updated every hour - http://hyperstrap.ml/
     Usage: extract bootstrap.dat into data directory (for Windows go to "run" and type in %appdata% and find HyperStake folder), remove blkindex.dat and blk0001.dat. When you fire up your QT wallet, it will automatically detect the bootstrap and begin to work. Bootstrapping may take an hour or two depending on the machine, please be patient, the bootstrap happens from the splashscreen, and clicking on it while bootstrapping may cause it to quit. Please note that it is common for the bootstrap to load 90k or so blocks at a time and jump out of bootstrap mode. If you client does this, simply turn it off. Go back to your datadir and rename bootstrap.dat.old to bootstrap.dat and restart your client, it will pick up where it left off.
If you are using the daemon you will need to enter the following startup switch: ./hyperstaked -loadblock=bootstrap.dat

[presstab]

I know that bootstrapping is painful at the moment. There are two reasons for this:

1) The bootstrap will jump out at random blocks because the ProcessBlock() function for some reason fails. I am investigating this still and hope to find a solution.

2) After the first bootstrap takes you so far, and you restart the bootstrap it will start from block 0 again and then say something like "ERROR: ProcessBlock() : already have block 0 000005fe04e512585c36" over and over until you get to your current block you have synced to. I have come up with a solution for this problem, which tells the bootstrap to skip to a few blocks before your last synced block. This saves valuable rescanning time.

I am hoping to have a new "FastStrap" code out in the near future that will help newcomers sync the HYP chain without as much pain.

[altcoiner-]

well bootstrap did not work for me at all, using the daemon that is.
Nothing is working for me atm, i don't think i'll be using hyper

[upgradeadvice]

Same issue here, no matter how I try to load the bootstrap:

ProcessBlock: ORPHAN BLOCK, prev=ace679d1bfc18e6f58b8
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 8c464eedafbb8588484d91329aeba76d35474758be2b90fe90fe3c02884d1392
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 17ba747a5abc3b60c48db56dc8219f54940d5466ee9eeedcc58d8dc59d09b46d
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 048c83a1bbfd38eb48ddfe3f7f5da986c75c58aebdb9164f3296399577229cd1
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block dfa955d6b17f37df452ad6f5c385b15b99a7bbbedff9336e19349eb0e2866e8a
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 8c1037bf7722dc35b670c37ee3dfcabeef1313f928b33d43599235bc58327b23
ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake 62e7ea85be03e6840c1b7602c1b009943f7a5ce2e92f5f23538b71d38cfed469, hashProof=0000000000000000000000000000000000000000000000000000000000000000
WARNING: ProcessBlock(): check proof-of-stake failed for block 6893f5789af11d6301d62261c54ecc145fb824c346e2410c31976d4488c14bc1
ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake 07c2a5fdac5d87841df98ed77d8c8af7e59dfe5f792f2a1dbc404a34794c05fb, hashProof=0000000000000000000000000000000000000000000000000000000000000000
WARNING: ProcessBlock(): check proof-of-stake failed for block 1c46ec1143164c50243d866688b952542bb9f3c7778671e175fbb6116cad36f6

Eventually, everyone just disconnects. Someone with an updated chain and client could do a reindex, create a new bootstrap, and check to see that it works with a new v1.1.2 install.

[altcoiner-]

Same issue here, no matter how I try to load the bootstrap:

ProcessBlock: ORPHAN BLOCK, prev=ace679d1bfc18e6f58b8
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 8c464eedafbb8588484d91329aeba76d35474758be2b90fe90fe3c02884d1392
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 17ba747a5abc3b60c48db56dc8219f54940d5466ee9eeedcc58d8dc59d09b46d
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 048c83a1bbfd38eb48ddfe3f7f5da986c75c58aebdb9164f3296399577229cd1
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block dfa955d6b17f37df452ad6f5c385b15b99a7bbbedff9336e19349eb0e2866e8a
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block 8c1037bf7722dc35b670c37ee3dfcabeef1313f928b33d43599235bc58327b23
ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake 62e7ea85be03e6840c1b7602c1b009943f7a5ce2e92f5f23538b71d38cfed469, hashProof=0000000000000000000000000000000000000000000000000000000000000000
WARNING: ProcessBlock(): check proof-of-stake failed for block 6893f5789af11d6301d62261c54ecc145fb824c346e2410c31976d4488c14bc1
ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake 07c2a5fdac5d87841df98ed77d8c8af7e59dfe5f792f2a1dbc404a34794c05fb, hashProof=0000000000000000000000000000000000000000000000000000000000000000
WARNING: ProcessBlock(): check proof-of-stake failed for block 1c46ec1143164c50243d866688b952542bb9f3c7778671e175fbb6116cad36f6

Eventually, everyone just disconnects. Someone with an updated chain and client could do a reindex, create a new bootstrap, and check to see that it works with a new v1.1.2 install.

agreed, bootstrap does nothing for me on the daemon

[presstab]

If the bootstrap "does nothing" then you are doing it wrong. What should happen is it begins to bootstrap and will maybe go anywhere from 5,000 blocks to 100,000 blocks before hitting an orphan that throws of the bootstrap. I am working on adding some proper orphan handling to the bootstrap processing, but it will not be ready tonight, or maybe even this week.

If your bootstrap "is not doing anything", make sure to carefully read the instructions again. For daemon you should have something like "./hyperstaked -loadblock=bootstrap.dat"

[billotronic]

If the bootstrap "does nothing" then you are doing it wrong. What should happen is it begins to bootstrap and will maybe go anywhere from 5,000 blocks to 100,000 blocks before hitting an orphan that throws of the bootstrap. I am working on adding some proper orphan handling to the bootstrap processing, but it will not be ready tonight, or maybe even this week.

If your bootstrap "is not doing anything", make sure to carefully read the instructions again. For daemon you should have something like "./hyperstaked -loadblock=bootstrap.dat"

really? I was always under the impressions having it named in the data dir was enough for it to work. if this is the case it should be added to the docs somewhere

{edit} also, how long are we talking? I would guess its at least an hour or so to bootstrap a virgin wallet. at least. might be worth looking into to avoid folks jumping the gun about a frozen client if we could say 'bootstrapping takes and average of x'

[upgradeadvice]

So this method got me to 300k+ and going:

Code:

./hyperstaked -loadblock=bootstrap.dat

Run until block 160,000 then kill it

Code:

./hyperstaked

Run until 161k or so then kill it done?

./hyperstaked -loadblock=bootstrap.dat.old

Run until synced? I'm not there yet...

I did notices a few reorgs while tailing the log file... is that normal for HYP?


Edit
These appear then a lot of orphans follow. I gave up here and started the slow p2p sync.

ERROR: FetchInputs() : 51b948beee mempool Tx prev not found 240463d12e
ERROR: CheckProofOfStake() : INFO: read txPrev failed

Edit 2
I believe the client thinks the last 200k or so blocks in the bootstrap are invalid. Eventually, it will just reprocess these as orphan and start syncing via p2p at around 340k

[presstab]

What I am seeing is that these bootstraps will have orphans embedded in them. These orphans are processed but never set as orphans and so the rest of the chain trails off because it doesn't connect to the previous blocks properly because the orphan is in the way. I am working on handling these orphans.

[Kushedout]

What I am seeing is that these bootstraps will have orphans embedded in them. These orphans are processed but never set as orphans and so the rest of the chain trails off because it doesn't connect to the previous blocks properly because the orphan is in the way. I am working on handling these orphans.

This makes sense, no wonder why my own bootstraps were failing.

Almost done syncing from scratch. Lets say after it syncs and i run walletrepair and create a bootstrap right after. Would that be a "cleaner"/  less problematic bootstrap?

[Mark Zuckerberg]

Never heard of this coin.  Stopped by, did some reading and still don't care.

[alterdicecom]

Hello,

Hyperstake has been added to https://alterdice.com for betting and recently to our new exchange. Bringing us to 12 supported currencies.

Our latest project in the coming weeks will also support hyperstake as well as a few other strong proof of stake blockchains. Please feel free to check us out, any feedback is welcomed.

https://bitcointalk.org/index.php?topic=1280448.msg13181620#msg13181620

John,
support@alterdice.com

[altcoiner-]

What I am seeing is that these bootstraps will have orphans embedded in them. These orphans are processed but never set as orphans and so the rest of the chain trails off because it doesn't connect to the previous blocks properly because the orphan is in the way. I am working on handling these orphans.

Waiting for a solution...
Current bootstrap, nothing fixed.

[iantunc]

What I am seeing is that these bootstraps will have orphans embedded in them. These orphans are processed but never set as orphans and so the rest of the chain trails off because it doesn't connect to the previous blocks properly because the orphan is in the way. I am working on handling these orphans.

Waiting for a solution...
Current bootstrap, nothing fixed.

hope you will wait a little bit more (you weren't going to use this coin either way). this problem comes from the native bitcoin code. what can be done to eliminate orphans in the bootstrap file is a fresh sync of the bootstrap server wallet daemon. it will be faster for you to sync your daemon by yourself, like all of us do.    

[HunterS]

Hey guys.I tried to send some coins and it failed so I ran checkwallet than repair wallet for mismatchcoins now I keep getting a double spend error when i try to send coins again.

[Sinergetikus]

Hi everyone.
I was using HyperStake-qt on my ubuntu vps, but yesterday I compiled hyperstaked and run it with "start-stop-daemon -SbCv -x /usr/local/bin/hyperstaked".
How can i understand that everything work fine?
Is it possible to send any command to wallet daemon?