ZeroQT ⭐

Like the dark look on the site, like the concept and am interested in the staking and potential of an instant crypto coin.
Casinos are a popular phenomenon as they give free or faucet rewards which can get revenue from customers filling captchas and advertising revenues or even pay to click, so a staking system then just depends on the price of the ZeroQT token on exchanges, hopeful, still learning about the coin...thx

638e6e3d226eb

 

Ok reindex fails with `fatal error occurred`, this is the log but I think LoyceV  may well be correct...
Thanks for the feedback, I have dat files safe

best=00000000000000000e7f7840597bd01793617a08281f95128b0591fc358c5b99 height=316097 version=0x00000002 log2_work=80.231896 tx=44754159 date='2014-08-17T15:16:57Z' progress=0.125087 cache=575.9MiB(4206868txo)
2018-12-04T12:34:09Z Fatal LevelDB error: IO error: F:\Bitcoin\Bitcoin1\chainstate\001736.ldb: Data error (cyclic redundancy check).


2018-12-04T12:34:09Z You can use -debug=leveldb to get more complete diagnostic messages
2018-12-04T12:34:09Z *** System error while flushing: Fatal LevelDB error: IO error: F:\Bitcoin\Bitcoin1\chainstate\001736.ldb: Data error (cyclic redundancy check).


2018-12-04T15:35:47Z UPnP Port Mapping successful.
2018-12-04T15:36:35Z Failed to connect best block (System error while flushing: Fatal LevelDB error: IO error: F:\Bitcoin\Bitcoin1\chainstate\001736.ldb: Data error (cyclic redundancy check).

 (code 0))
2018-12-04T15:36:35Z socket sending timeout: 10963s
2018-12-04T15:36:35Z Potential stale tip detected, will try using extra outbound peer (last tip update: 10947 seconds ago)
2018-12-04T15:36:35Z socket sending timeout: 10947s
2018-12-04T15:36:35Z socket receive timeout: 10854s
2018-12-04T15:36:35Z tor: Thread interrupt
2018-12-04T15:36:35Z addcon thread exit
2018-12-04T15:36:35Z msghand thread exit
2018-12-04T15:36:35Z net thread exit
2018-12-04T15:36:35Z Shutdown: In progress...
2018-12-04T15:36:35Z torcontrol thread exit
2018-12-04T15:36:35Z opencon thread exit
2018-12-04T15:36:36Z UPNP_DeletePortMapping() returned: 0
2018-12-04T15:36:36Z upnp thread exit
2018-12-04T15:36:37Z [default wallet] AddToWallet 2d62f39b1cce947763657af22559f07f348b53d853fe4706ec1240b1567124f2 
2018-12-04T15:36:38Z scheduler thread interrupt
2018-12-04T15:36:38Z Fatal LevelDB error: IO error: F:\Bitcoin\Bitcoin1\chainstate\001736.ldb: Data error (cyclic redundancy check).

2018-12-04T15:36:38Z You can use -debug=leveldb to get more complete diagnostic messages
2018-12-04T15:36:38Z *** System error while flushing: Fatal LevelDB error: IO error: F:\Bitcoin\Bitcoin1\chainstate\001736.ldb: Data error (cyclic redundancy check).

2018-12-04T15:36:42Z FlushStateToDisk: failed to flush state (System error while flushing: Fatal LevelDB error: IO error: F:\Bitcoin\Bitcoin1\chainstate\001736.ldb: Data error (cyclic redundancy check).

 (code 0))
2018-12-04T15:36:42Z Fatal LevelDB error: IO error: F:\Bitcoin\Bitcoin1\chainstate\001736.ldb: Data error (cyclic redundancy check).

2018-12-04T15:36:42Z You can use -debug=leveldb to get more complete diagnostic messages
2018-12-04T15:36:42Z *** System error while flushing: Fatal LevelDB error: IO error: F:\Bitcoin\Bitcoin1\chainstate\001736.ldb: Data error (cyclic redundancy check).

2018-12-04T15:36:43Z FlushStateToDisk: failed to flush state (System error while flushing: Fatal LevelDB error: IO error: F:\Bitcoin\Bitcoin1\chainstate\001736.ldb: Data error (cyclic redundancy check).

 (code 0))
2018-12-04T15:36:46Z [default wallet] Releasing wallet
2018-12-04T15:36:46Z Shutdown: done

Hello, since 17.0.1 pc cant seem to get to sync bitcoin core as the program confirms for a while then says cannot read from database, then closes. Its on a western digital 1Tb drive(less than 3 years old) but I read somewhere they now recommend an SSD to run bitcoin : is this the case?

I ran chkdsk /f /r, which replaced bad clusters across several folders but then pc crashed after a day...need I restart/finish this process and will it even sync when/if it does : are spinning disks now obsolete for bitcoin on a 15mbit connection, considering format and rescan may alternatively be the solution.

Having many blockchains on my drive, even format and resync is a formidable task, considering other blockchains on this drive work fine, may format be the solution or is the above the overriding factor since the wallet got rewritten incorrectly at version 16...

Thanks

 

http://yannik.biz/?ref=372

Thx great trusted faucet, long time claim here, positive!!!

@ Victor Bitcoin

Install the compound wallet, open it then close it whenever...

Find the compound blockchain location on your hd  (local disk C: / users /yourname /apps / compound, unless you put it elsewhere)

Replace the wallet dat in the compound blockchain folder with your real wallet .dat

Open compound wallet again

That should be ok it should then sync your wallet on your new machine

Yes am wondering the same at 8 days waiting to stake...I guess it may also depend how fast your internet is if your wallet is competing against a network.

The top article says `Min/Max Stake Age: 1/30 Days` does this mean a wallet may have to wait upto 30 days to begin seeing returns from staking?

Ok yes, thanks Cellard and jackg, I think I understand it...what you described is helpfull as I only need 2 versions of the blockchain to achieve it.....and is otherwise what I was thinking.

The fact I cannot use my original address afterwards I find slightly worrying as I use it in so many sites....but hopefully they can update address and all then use my new btc address.... hopefully

So if I wait until after the Btcx2 fork, do I `dig` each new forks currency from the same original bitcoin address? Or does the new currency value follow where the original bitcoin balance is .... for example:

... if I use btc address 1, send it to btc address 2, then `dig` btc address 1 for BCC from BCC blockchain(as described)....when I then do the same to BTG would I `dig` from Btc address 1? As I`m thinking that the fork will hold value that was present at the time of the fork...in your explanation we move my balance of Btc to my fresh address, which shows that the balance is held on the blockchain at the time of the fork and doesn`t necessarily follow the actual balance...unless as you warned someone were to `dig` btc address 2 before I had `dug` Btc address 1.

Thanks for understanding my caution.

Bob and Jack...thanks for the advices....ie do it all on my own HD with new wallets....

So... by `new wallet` do you mean `create new wallet address` in Qt wallet, or make a totally seperate instance of Qt syncing to a totally seperate version of the blockchain on my HD?(I can copy and rescan the one`s I have for instance....so then there would be four of them on my HD, is that what you mean?)

My BCC wallet has currently a different address to my Btc address and is syncing to a seperate version of the blockchain on my HD...so when I import keys or dat...it will momentarily have the same address as my btc wallet right? Then I send to my unique BCC address....on its own seperate copy of the blockchain....and then the BCC is safely seperated.

Then once seperated....is it safe to continue using my original Btc address? Or will I need to use the one I send to that will hold the btc during this process? I`ve heard it said NOT to use from then on...why would that be necessary?

This process will be needed for each fork....BCC, BTG...and BTC2x?? But can be done after they fork and prove stable ?

Thanks again....

Hello, as bitcoin has been forking BCH and BTG, I wondered if you could give general advice as to best cope with these forks. I have bitcoin qt wallets holding my bitcoin and also a bitcoin cash qt wallet each with separate blockchains on my HD. So now the BCH and BTG forks have established is it safe to do the following:-
1)Send coinbase the btc in my wallet.
2)Move my BTC wallet/dat file to my also synced BCH wallet, then rescan it, to reveal my BCH.
3)Send the BCH to the original wallet address that I first synced as my independant BCH wallet address, and thus separate the BCH from my btc by rescanning with its returned original BCH wallet/dat file.
4) Rescan my BTC wallet with my original wallet address (that I will then have removed from my BCH wallet as I rescan to its original address) and continue to use my original BTC wallet address(as I work online with this address and will need to rescan for BTG and segitBTC2x ie)

Will this process safely separate the two currencies ?

Would this same process be applicable to the BTG fork should it prove to be valid and stable ?
I would send my bitcoin to coinbase before the segwit fork date and thus the emerging BTC or BTC2 whichever coinbase identifies would theoretically duplicate and be separated by coinbase and give me two different balances of bitcoin after that November day(?)
As I would have moved my bitcoin after the BCH and BTG forks then presumably the process (1-4 above) would work for both currencies even if performed after the Segwit fork as I hold the keys to my original blockchain address.

Also, I appreciate that BTG has yet to prove itself. However I am anticipating that to have become clear by the time of the segwit fork in early November, which will need another copy of the blockchain and another rescan with my original private keys(wallet/dat file)

Hoping you can advise me on this process outlined above for how to best handle these forks.

Thanks

Got payment...thx Bitcoinflame!!!

https://blockchain.info/tx/9d526805b3491d1b5171fdcc30012b908384fd68e282afd6d08d8bfc99620c51

0.00046 BTC

http://www.bitcoinflame.com?ref=9d850d57