Bitcoin blockchain pruning - How to reduce Bitcoin core ...

XCP Counterparty Protocol

Counterparty is a protocol for the creation and use of decentralised financial instruments using Bitcoin as a transport layer. It has an open-source and Public Domain reference implementation, counterpartyd, which is available for download/perusal at https://github.com/PhantomPhreak/counterpartyd/.
[link]

Japanese Version of Ethereum

Japan's clone of Ethereum
[link]

I0coin (I0C), news for I0coin cryptocurrency

I0coin (I0C) is a peer-to-peer cryptocurrency based on Bitcoin with a faster block time and shorter maturity. I0coin is merge mined with Bitcoin to allow for super efficient, low energy mining, and a massive network hash rate. I0coin is the most secure cryptocurrency with a block time faster than Bitcoin's.
[link]

Error starting up new Bitcoin Unlimited BCH node.

EDIT: Fixed, I just needed to run "./bch-unlimited-1.8.0.0/bin/bitcoind --daemon -reindex" It's fully synced now.
It was syncing for awhile at first but now it keeps crashing whenever I run the following command."./bch-unlimited-1.8.0.0/bin/bitcoind --daemon"
It throws the error "Error: Failed to connect best block"Below is the log. Any help is appreciated.
2020-07-29 18:53:36 CDBEnv::Open: LogDir=/root/.bitcoin/database ErrorFile=/root/.bitcoin/db.log 2020-07-29 18:53:36 Cache configuration: 2020-07-29 18:53:36 * Using 0.0MiB for block database 2020-07-29 18:53:36 * Using 0.0MiB for block undo database 2020-07-29 18:53:36 * Using 2.0MiB for block index database 2020-07-29 18:53:36 * Using 0.0MiB for txindex database 2020-07-29 18:53:36 * Using 317.1MiB for chain state database 2020-07-29 18:53:36 * Using 2155.9MiB for in-memory UTXO set 2020-07-29 18:53:36 init message: Opening Block database... 2020-07-29 18:53:36 LevelDB using max_open_files=1000 (default=1000) 2020-07-29 18:53:36 Opening LevelDB in /root/.bitcoin/blocks/index 2020-07-29 18:53:37 Opened LevelDB successfully 2020-07-29 18:53:37 Using obfuscation key for /root/.bitcoin/blocks/index: 0000000000000000 2020-07-29 18:53:37 init message: Opening UTXO database... 2020-07-29 18:53:37 LevelDB using max_open_files=1000 (default=1000) 2020-07-29 18:53:37 Opening LevelDB in /root/.bitcoin/chainstate 2020-07-29 18:53:38 Opened LevelDB successfully 2020-07-29 18:53:38 Using obfuscation key for /root/.bitcoin/chainstate: 8e46379444ba7f52 2020-07-29 18:53:38 init message: Opening Coins Cache database... 2020-07-29 18:53:38 init message: Loading block index... 2020-07-29 18:53:44 Checking all blk files are present... 2020-07-29 18:53:44 LoadBlockIndexDB: last block file = 695 2020-07-29 18:53:44 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=119, size=103373591, heights=441306...441426, time=2016-11-30...2016-12-01) 2020-07-29 18:53:44 LoadBlockIndexDB: hashBestChain=000000000000000000c687014d1c6b88d26a2af658fea4598bbf9d36ae5a987c height=439622 date=2016-11-19 07:15:45 progress=0.268064 2020-07-29 18:53:44 init message: Verifying blocks... 2020-07-29 18:53:44 Verifying last 6 blocks at level 3 2020-07-29 18:53:45 No coin database inconsistencies in last 7 blocks (16216 transactions) 2020-07-29 18:53:45 block index 8915ms 2020-07-29 18:53:45 init message: Loading wallet... 2020-07-29 18:53:45 nFileVersion = 1080000 2020-07-29 18:53:45 Keys: 103 plaintext, 0 encrypted, 103 w/ metadata, 103 total 2020-07-29 18:53:45 wallet 5ms 2020-07-29 18:53:45 init message: Activating best chain... 2020-07-29 18:53:45 ERROR: ConnectBlockDependencyOrdering: block 0000000000000000012ecb0a0b8f28ee434841410d0c04ae14faa20cb5102635 inputs missing/spent in tx 335 0a01201f6cff4d38207d118c9f6100182d40033ffbcfe6daefbf9669e0f98ace 2020-07-29 18:53:45 InvalidChainFound: invalid block=0000000000000000012ecb0a0b8f28ee434841410d0c04ae14faa20cb5102635 height=439623 log2_work=85.562686 date=2016-11-19 07:25:44 2020-07-29 18:53:45 InvalidChainFound: current best=000000000000000000c687014d1c6b88d26a2af658fea4598bbf9d36ae5a987c height=439622 log2_work=85.562655 date=2016-11-19 07:15:45 2020-07-29 18:53:46 ERROR: ConnectTip(): ConnectBlock 0000000000000000012ecb0a0b8f28ee434841410d0c04ae14faa20cb5102635 failed 2020-07-29 18:53:46 Invalid block due to bad-txns-inputs-missingorspent 2020-07-29 18:53:46 InvalidChainFound: invalid block=0000000000000000012ecb0a0b8f28ee434841410d0c04ae14faa20cb5102635 height=439623 log2_work=85.562686 date=2016-11-19 07:25:44 2020-07-29 18:53:46 InvalidChainFound: current best=000000000000000000c687014d1c6b88d26a2af658fea4598bbf9d36ae5a987c height=439622 log2_work=85.562655 date=2016-11-19 07:15:45 2020-07-29 18:53:46 Chain activation failed, returning to next best choice 2020-07-29 18:53:48 Waiting for genesis block to be imported... 2020-07-29 18:53:48 Imported mempool transactions from disk: 0 successes, 0 expired 2020-07-29 18:53:48 Bound to [::]:8333 2020-07-29 18:53:48 Bound to 0.0.0.0:8333 2020-07-29 18:53:48 Error: Failed to connect best block 2020-07-29 18:53:48 Shutdown: In progress... 2020-07-29 18:53:48 StopNode() 2020-07-29 18:53:49 Dumped mempool: 2e-06s to copy, 0.001151s to dump 
submitted by BowlofFrostedFlakes to btc [link] [comments]

Will the SEC block the Fidelity Bitcoin index fund?

I know that the current SEC chairman is quite hostile to cryptocurrency funds. Which lead me into question if Fidelity will actually be able to get SEC approval for their index fund. Anyone who is more knowledge in this matter want to share their opinion of how this might play out?
Does the Fidelity fund have a shot because it is an index fund and not a ETF? Or will it be dead on arrival like the recent Bitcoin ETF applications?
submitted by Panda_Procrastinator to investing [link] [comments]

Can/will the SEC block the Fidelity index fund? (x-post from /r/Bitcoin)

submitted by ASICmachine to CryptoCurrencyClassic [link] [comments]

08-10 22:26 - 'Don't look for the needle in the haystack, buy the haystack. These are wise words from john. C bogle. Inventor of the index fund. Block chain technology has grown exponentially since 2009. The total crypto currency cap is r...' by /u/Melodic_Award removed from /r/Bitcoin within 0-8min

'''
Don't look for the needle in the haystack, buy the haystack. These are wise words from john. C bogle. Inventor of the index fund. Block chain technology has grown exponentially since 2009. The total crypto currency cap is roughly $115 billion. Should you invest? (High returns comes with high risks and extreme volatility) bit coin’s market share has dropped but getting ready to kick off soon, now altcoins are the majority. There are literally thousands of coins to choose from. So the question is how can one invest in crypto currency effectively with great turnouts? I myself started out on some little coins while investing in them little by little, well I can say I really made a smart decision by doing so with these coins which are now generating great turnouts for me. Interested persons should reach me for more information on these coins which are really promising. [[email protected]]1
'''
Context Link
Go1dfish undelete link
unreddit undelete link
Author: Melodic_Award
1: mailto:[email protected]
submitted by removalbot to removalbot [link] [comments]

Is it normal for a new Full Node server to repeatedly show Potential Sale Tip detected messages? What does this even mean. I surprisingly can't find anything with a solution on the internet. Please look at my log dump and give me an idea what to do. Im trying to run a full node in service to the net

Here is my log messages:

2019-11-14T03:05:38Z Bitcoin Core version v0.18.1 (release build)
2019-11-14T03:05:38Z Assuming ancestors of block 0000000000000000000f1c54590ee18d15ec70e68c8cd4cfbadb1b4f11697eee have valid signatures.
2019-11-14T03:05:38Z Setting nMinimumChainWork=0000000000000000000000000000000000000000051dc8b82f450202ecb3d471
2019-11-14T03:05:38Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation
2019-11-14T03:05:38Z Default data directory /home/norman/.bitcoin
2019-11-14T03:05:38Z Using data directory /media/norman/Seagate Expansion Drive/.bitcoin/
2019-11-14T03:05:38Z Config file: /media/norman/Seagate Expansion Drive/.bitcoin/bitcoin.conf (not found, skipping)
2019-11-14T03:05:38Z Using at most 125 automatic connections (1024 file descriptors available)
2019-11-14T03:05:38Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2019-11-14T03:05:38Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2019-11-14T03:05:38Z Using 8 threads for script verification
2019-11-14T03:05:38Z scheduler thread start
2019-11-14T03:05:38Z HTTP: creating work queue of depth 16
2019-11-14T03:05:38Z No rpcpassword set - using random cookie authentication.
2019-11-14T03:05:38Z Generated RPC authentication cookie /media/norman/Seagate Expansion Drive/.bitcoin/.cookie
2019-11-14T03:05:38Z HTTP: starting 4 worker threads
2019-11-14T03:05:38Z Using wallet directory /media/norman/Seagate Expansion Drive/.bitcoin/
2019-11-14T03:05:38Z init message: Verifying wallet(s)...
2019-11-14T03:05:38Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2019-11-14T03:05:38Z Using wallet /media/norman/Seagate Expansion Drive/.bitcoin/
2019-11-14T03:05:38Z BerkeleyEnvironment::Open: LogDir=/media/norman/Seagate Expansion Drive/.bitcoin/database ErrorFile=/media/norman/Seagate Expansion Drive/.bitcoin/db.log
2019-11-14T03:05:39Z init message: Loading banlist...
2019-11-14T03:05:39Z Cache configuration:
2019-11-14T03:05:39Z * Using 2.0 MiB for block index database
2019-11-14T03:05:39Z * Using 8.0 MiB for chain state database
2019-11-14T03:05:39Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2019-11-14T03:05:39Z init message: Loading block index...
2019-11-14T03:05:39Z Opening LevelDB in /media/norman/Seagate Expansion Drive/.bitcoin/blocks/index
2019-11-14T03:05:39Z Opened LevelDB successfully
2019-11-14T03:05:39Z Using obfuscation key for /media/norman/Seagate Expansion Drive/.bitcoin/blocks/index: 0000000000000000
2019-11-14T03:05:39Z LoadBlockIndexDB: last block file = 0
2019-11-14T03:05:39Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=293, heights=0...0, time=2009-01-03...2009-01-03)
2019-11-14T03:05:39Z Checking all blk files are present...
2019-11-14T03:05:39Z Opening LevelDB in /media/norman/Seagate Expansion Drive/.bitcoin/chainstate
2019-11-14T03:05:40Z Opened LevelDB successfully
2019-11-14T03:05:40Z Using obfuscation key for /media/norman/Seagate Expansion Drive/.bitcoin/chainstate: fb03fb54abfe4745
2019-11-14T03:05:40Z Loaded best chain: hashBestChain=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 date=2009-01-03T18:15:05Z progress=0.000000
2019-11-14T03:05:40Z init message: Rewinding blocks...
2019-11-14T03:05:40Z init message: Verifying blocks...
2019-11-14T03:05:40Z block index 1516ms
2019-11-14T03:05:40Z init message: Loading wallet...
2019-11-14T03:05:40Z BerkeleyEnvironment::Open: LogDir=/media/norman/Seagate Expansion Drive/.bitcoin/database ErrorFile=/media/norman/Seagate Expansion Drive/.bitcoin/db.log
2019-11-14T03:05:40Z [default wallet] nFileVersion = 180100
2019-11-14T03:05:40Z [default wallet] Keys: 2001 plaintext, 0 encrypted, 2001 w/ metadata, 2001 total. Unknown wallet records: 0
2019-11-14T03:05:41Z [default wallet] Wallet completed loading in 449ms
2019-11-14T03:05:41Z [default wallet] setKeyPool.size() = 2000
2019-11-14T03:05:41Z [default wallet] mapWallet.size() = 0
2019-11-14T03:05:41Z [default wallet] mapAddressBook.size() = 0
2019-11-14T03:05:41Z mapBlockIndex.size() = 1
2019-11-14T03:05:41Z nBestHeight = 0
2019-11-14T03:05:41Z torcontrol thread start
2019-11-14T03:05:41Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there
2019-11-14T03:05:41Z Bound to [::]:8333
2019-11-14T03:05:41Z Bound to 0.0.0.0:8333
2019-11-14T03:05:41Z init message: Loading P2P addresses...
2019-11-14T03:05:41Z Loaded 253 addresses from peers.dat 16ms
2019-11-14T03:05:41Z init message: Starting network threads...
2019-11-14T03:05:41Z net thread start
2019-11-14T03:05:41Z dnsseed thread start
2019-11-14T03:05:41Z opencon thread start
2019-11-14T03:05:41Z init message: Done loading
2019-11-14T03:05:41Z addcon thread start
2019-11-14T03:05:41Z msghand thread start
2019-11-14T03:05:52Z Loading addresses from DNS seeds (could take a while)
2019-11-14T03:05:54Z 187 addresses found from DNS seeds
2019-11-14T03:05:54Z dnsseed thread exit
2019-11-14T03:37:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 1890 seconds ago)
2019-11-14T03:48:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 2520 seconds ago)
2019-11-14T03:58:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 3150 seconds ago)
2019-11-14T04:09:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 3780 seconds ago)
2019-11-14T04:19:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 4410 seconds ago)
2019-11-14T04:30:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 5040 seconds ago)
2019-11-14T04:40:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 5670 seconds ago)
2019-11-14T04:51:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 6300 seconds ago)
2019-11-14T05:01:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 6930 seconds ago)
2019-11-14T05:12:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 7560 seconds ago)
2019-11-14T05:22:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 8190 seconds ago)
2019-11-14T05:33:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 8820 seconds ago)
2019-11-14T05:43:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 9450 seconds ago)
2019-11-14T05:54:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 10080 seconds ago)
2019-11-14T06:04:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 10710 seconds ago)
2019-11-14T06:15:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 11340 seconds ago)
2019-11-14T06:25:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 11970 seconds ago)
2019-11-14T06:36:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 12600 seconds ago)
2019-11-14T06:46:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 13230 seconds ago)
2019-11-14T06:57:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 13860 seconds ago)
2019-11-14T07:07:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 14490 seconds ago)
2019-11-14T07:18:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 15120 seconds ago)
2019-11-14T07:28:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 15750 seconds ago)
2019-11-14T07:39:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 16380 seconds ago)
2019-11-14T07:49:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 17010 seconds ago)
2019-11-14T08:00:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 17640 seconds ago)
2019-11-14T08:10:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 18270 seconds ago)
2019-11-14T08:21:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 18900 seconds ago)
2019-11-14T08:31:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 19530 seconds ago)
2019-11-14T08:42:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 20160 seconds ago)
2019-11-14T08:52:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 20790 seconds ago)
2019-11-14T09:03:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 21420 seconds ago)
2019-11-14T09:13:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 22050 seconds ago)
2019-11-14T09:24:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 22680 seconds ago)
2019-11-14T09:34:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 23310 seconds ago)
2019-11-14T09:45:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 23940 seconds ago)
2019-11-14T09:55:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 24570 seconds ago)
2019-11-14T10:06:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 25200 seconds ago)
2019-11-14T10:16:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 25830 seconds ago)
2019-11-14T10:27:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 26460 seconds ago)
2019-11-14T10:37:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 27090 seconds ago)
2019-11-14T10:48:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 27720 seconds ago)
2019-11-14T10:58:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 28350 seconds ago)
2019-11-14T11:09:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 28980 seconds ago)
2019-11-14T11:19:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 29610 seconds ago)
2019-11-14T11:30:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 30240 seconds ago)
2019-11-14T11:40:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 30870 seconds ago)
2019-11-14T11:51:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 31500 seconds ago)
2019-11-14T12:01:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 32130 seconds ago)
2019-11-14T12:12:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 32760 seconds ago)
2019-11-14T12:22:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 33390 seconds ago)
2019-11-14T12:33:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 34020 seconds ago)
2019-11-14T12:43:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 34650 seconds ago)
2019-11-14T12:54:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 35280 seconds ago)
2019-11-14T13:04:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 35910 seconds ago)
2019-11-14T13:15:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 36540 seconds ago)
2019-11-14T13:25:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 37170 seconds ago)
2019-11-14T13:36:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 37800 seconds ago)
2019-11-14T13:46:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 38430 seconds ago)
2019-11-14T13:57:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 39060 seconds ago)
2019-11-14T14:07:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 39690 seconds ago)
2019-11-14T14:18:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 40320 seconds ago)
2019-11-14T14:28:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 40950 seconds ago)
2019-11-14T14:39:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 41580 seconds ago)
2019-11-14T14:49:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 42210 seconds ago)
2019-11-14T15:00:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 42840 seconds ago)
2019-11-14T15:10:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 43470 seconds ago)
2019-11-14T15:21:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 44100 seconds ago)
2019-11-14T15:31:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 44730 seconds ago)
2019-11-14T15:42:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 45360 seconds ago)
2019-11-14T15:52:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 45990 seconds ago)
2019-11-14T16:03:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 46620 seconds ago)
2019-11-14T16:13:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 47250 seconds ago)
2019-11-14T16:24:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 47880 seconds ago)
2019-11-14T16:34:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 48510 seconds ago)
2019-11-14T16:45:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 49140 seconds ago)
2019-11-14T16:55:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 49770 seconds ago)
2019-11-14T17:06:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 50400 seconds ago)
2019-11-14T17:16:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 51030 seconds ago)
2019-11-14T17:27:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 51660 seconds ago)
2019-11-14T17:37:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 52290 seconds ago)
2019-11-14T17:48:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 52920 seconds ago)
2019-11-14T17:58:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 53550 seconds ago)
2019-11-14T18:09:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 54180 seconds ago)
2019-11-14T18:19:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 54810 seconds ago)
2019-11-14T18:30:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 55440 seconds ago)
2019-11-14T18:40:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 56070 seconds ago)
2019-11-14T18:51:24Z Potential stale tip detected, will try using extra outbound peer (last tip update: 56700 seconds ago)
2019-11-14T19:01:54Z Potential stale tip detected, will try using extra outbound peer (last tip update: 57330 seconds ago)


this goes on until I decided just to shut down server after 24 hours and the .dat blockchain file was stuck at 16MB in size. Seemed like going nowhere.
submitted by Alchemy333 to Bitcoin [link] [comments]

Bitcoind stuck in startup loading block index

Hi,
I have had bitcoin core running on a raspberry pi for about 4 month now (followed the raspibolt instructions from stadicus) and it worked fine until 3 days ago it suddenly stopped working. With bitcoin-cli blockchaininfo i got
error code: -28 Loading block index... 
or something similar. When a looked in the debug log file i saw this:
2019-08-29T16:48:08Z BerkeleyEnvironment::Open: LogDir=/home/bitcoin/.bitcoin/database ErrorFile=/home/bitcoin/.bitcoin/db.log 2019-08-29T16:48:11Z init message: Loading banlist... 2019-08-29T16:48:11Z Cache configuration: 2019-08-29T16:48:11Z * Using 2.0 MiB for block index database 2019-08-29T16:48:11Z * Using 8.0 MiB for chain state database 2019-08-29T16:48:11Z * Using 90.0 MiB for in-memory UTXO set (plus up to 47.7 MiB of unused mempool space) 2019-08-29T16:48:11Z init message: Loading block index... 2019-08-29T16:48:11Z Opening LevelDB in /home/bitcoin/.bitcoin/blocks/index 2019-08-29T16:48:11Z Opened LevelDB successfully 2019-08-29T16:48:11Z Using obfuscation key for /home/bitcoin/.bitcoin/blocks/index: 0000000000000000 2019-08-29T16:54:14Z 2019-08-29T16:54:14Z Bitcoin Core version v0.18.1 (release build) 2019-08-29T16:54:14Z Assuming ancestors of block 0000000000000000000f1c54590ee18d15ec70e68c8cd4cfbadb1b4f11697eee have valid signatures. 2019-08-29T16:54:14Z Setting nMinimumChainWork=0000000000000000000000000000000000000000051dc8b82f450202ecb3d471 2019-08-29T16:54:14Z Using the 'standard' SHA256 implementation 2019-08-29T16:54:15Z Default data directory /home/bitcoin/.bitcoin 2019-08-29T16:54:15Z Using data directory /home/bitcoin/.bitcoin 2019-08-29T16:54:15Z Config file: /home/bitcoin/.bitcoin/bitcoin.conf 2019-08-29T16:54:15Z Using at most 20 automatic connections (1024 file descriptors available) 2019-08-29T16:54:15Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2019-08-29T16:54:15Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2019-08-29T16:54:15Z Using 4 threads for script verification 2019-08-29T16:54:15Z scheduler thread start 2019-08-29T16:54:15Z HTTP: creating work queue of depth 16 2019-08-29T16:54:15Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation. 2019-08-29T16:54:15Z HTTP: starting 4 worker threads 2019-08-29T16:54:15Z Using wallet directory /home/bitcoin/.bitcoin 2019-08-29T16:54:15Z init message: Verifying wallet(s)... 2019-08-29T16:54:15Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2019-08-29T16:54:15Z Using wallet /home/bitcoin/.bitcoin 2019-08-29T16:54:15Z BerkeleyEnvironment::Open: LogDir=/home/bitcoin/.bitcoin/database ErrorFile=/home/bitcoin/.bitcoin/db.log 2019-08-29T16:54:16Z init message: Loading banlist... 2019-08-29T16:54:16Z Cache configuration: 2019-08-29T16:54:16Z * Using 2.0 MiB for block index database 2019-08-29T16:54:16Z * Using 8.0 MiB for chain state database 2019-08-29T16:54:16Z * Using 90.0 MiB for in-memory UTXO set (plus up to 47.7 MiB of unused mempool space) 2019-08-29T16:54:16Z init message: Loading block index... 2019-08-29T16:54:16Z Opening LevelDB in /home/bitcoin/.bitcoin/blocks/index 2019-08-29T16:54:16Z Opened LevelDB successfully 2019-08-29T16:54:16Z Using obfuscation key for /home/bitcoin/.bitcoin/blocks/index: 0000000000000000 
After that there should follow a line about Loading the block index but it never appears.
It seems to be restarting without shutting down correctly, maybe it cannot find the block index? I tried reinstalling core, recreating the symlink to the hdd and resetting the service but nothing happened. Everytime it starts it gets stuck at the same point. It also takes an awful long time to stop bitcoind but i don't know if that is normal.
I found several people with similar problems online but noting helped so far. Has anyone had a similar problem in the past and found a solution to this?
submitted by BologneseWithCheese to Bitcoin [link] [comments]

Why am I getting exit code 1 after stopping bitcoin RPC server?

This is how I'm starting and stopping bitcoin from a service unit
[Service] ExecStart=/usbin/bitcoind -daemon=0 -datadir=/home/jsonrpc/bitcoin -conf=/home/jsonrpc/bitcoin/settings.conf ExecStop=/usbin/bitcoin-cli -datadir=/home/jsonrpc/bitcoin -conf=/home/jsonrpc/bitcoin/settings.conf stop 
And this is what I get when I stop the service:
Shutdown requested. Exiting. Interrupting HTTP RPC server Interrupting RPC Shutdown: In progress... Stopping HTTP RPC server Stopping RPC RPC stopped. scheduler thread interrupt Shutdown: done bitcoin.service: Main process exited, code=exited, status=1/FAILURE 
debug.log
2018-11-21T18:02:16Z Bitcoin Core version v0.17.0.0-ge1ed37edaedc85b8c3468bd9a726046344036243 (release build) 2018-11-21T18:02:16Z InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2018-11-21T18:02:16Z Assuming ancestors of block 0000000000000000002e63058c023a9a1de233554f28c7b21380b6c9003f36a8 have valid signatures. 2018-11-21T18:02:16Z Setting nMinimumChainWork=0000000000000000000000000000000000000000028822fef1c230963535a90d 2018-11-21T18:02:16Z Using the 'standard' SHA256 implementation 2018-11-21T18:02:16Z Default data directory /home/jsonrpc/.bitcoin 2018-11-21T18:02:16Z Using data directory /home/jsonrpc/bitcoin 2018-11-21T18:02:16Z Using config file /home/jsonrpc/bitcoin/settings.conf 2018-11-21T18:02:16Z Using at most 4 automatic connections (1024 file descriptors available) 2018-11-21T18:02:16Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements 2018-11-21T18:02:16Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements 2018-11-21T18:02:16Z Using 0 threads for script verification 2018-11-21T18:02:16Z HTTP: creating work queue of depth 16 2018-11-21T18:02:16Z Starting RPC 2018-11-21T18:02:16Z Starting HTTP RPC server 2018-11-21T18:02:16Z Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcauth for rpcauth auth generation. 2018-11-21T18:02:16Z HTTP: starting 2 worker threads 2018-11-21T18:02:16Z Using wallet directory /home/jsonrpc/bitcoin 2018-11-21T18:02:16Z init message: Verifying wallet(s)... 2018-11-21T18:02:16Z Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2018-11-21T18:02:16Z Using wallet wallet.dat 2018-11-21T18:02:16Z BerkeleyEnvironment::Open: LogDir=/home/jsonrpc/bitcoin/database ErrorFile=/home/jsonrpc/bitcoin/db.log 2018-11-21T18:02:16Z scheduler thread start 2018-11-21T18:02:24Z Cache configuration: 2018-11-21T18:02:24Z * Using 2.0MiB for block index database 2018-11-21T18:02:24Z * Using 8.0MiB for chain state database 2018-11-21T18:02:24Z * Using 40.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space) 2018-11-21T18:02:24Z init message: Loading block index... 2018-11-21T18:02:24Z Opening LevelDB in /home/jsonrpc/bitcoin/blocks/index 2018-11-21T18:02:25Z Opened LevelDB successfully 2018-11-21T18:02:25Z Using obfuscation key for /home/jsonrpc/bitcoin/blocks/index: 0000000000000000 2018-11-21T18:03:38Z LoadBlockIndexDB: last block file = 1425 2018-11-21T18:03:38Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=71, size=79377521, heights=549167...549288, time=2018-11-07...2018-11-08) 2018-11-21T18:03:38Z Checking all blk files are present... 2018-11-21T18:03:47Z Opening LevelDB in /home/jsonrpc/bitcoin/chainstate 2018-11-21T18:03:47Z Opened LevelDB successfully 2018-11-21T18:03:48Z Using obfuscation key for /home/jsonrpc/bitcoin/chainstate: XXXXXXXXXXXXXXXX 2018-11-21T18:03:50Z Loaded best chain: hashBestChain=0000000000000000001d43d5aeb32c7d5158e48da84b896413e6439d09e53081 height=548521 date=2018-11-03T01:39:02Z progress=0.989162 2018-11-21T18:03:50Z init message: Rewinding blocks... 2018-11-21T18:04:22Z init message: Verifying blocks... 2018-11-21T18:04:22Z Verifying last 6 blocks at level 3 2018-11-21T18:04:22Z [0%]...[16%]...ThreadRPCServer method=stop user=deploy 2018-11-21T18:17:13Z block index 889465ms 2018-11-21T18:17:13Z Shutdown requested. Exiting. 2018-11-21T18:17:14Z Interrupting HTTP RPC server 2018-11-21T18:17:14Z Interrupting RPC 2018-11-21T18:17:14Z Shutdown: In progress... 2018-11-21T18:17:15Z Stopping HTTP RPC server 2018-11-21T18:17:15Z Stopping RPC 2018-11-21T18:17:15Z RPC stopped. 2018-11-21T18:17:16Z scheduler thread interrupt 2018-11-21T18:17:19Z Shutdown: done 
submitted by rraallvv to Bitcoin [link] [comments]

My installation of Bitcoin 0.13.1 keeps corrupting.

I have had bitcoin 0.12.1 installed on this computer for like a year. Well, I opened it yesterday after not using it for a few weeks, and it said corrupted. So, I ran reindex, and same thing happen. So, I then I tried 0.13.1 same thing. So, I then renamed the original bitcoin directory to something else, and let 0.13.1 completely from scratch redownload and verify the blockchain, essentially a fresh install with an empty wallet. And it's amazingly doing the same crash like a 1 and 1/2 year back from present. Crashes every single time.
This is very bizarre, I'm running 0.13.1 on a different computer as well with no problem.
It can't be hard drive corruption, as I completely installed from scratch(I kept the whole old directory renamed).
Running: Windows 7 Home x64 Processor AMD A10 7850k Ram: 8 GB DDR3 Motherboard: FM2A88X Extreme6+
Here is what the error log says. 2016-11-21 08:56:21 Bitcoin version v0.13.1 2016-11-21 08:56:21 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2016-11-21 08:56:21 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..." 2016-11-21 08:56:23 Default data directory C:\Users\7850fr\AppData\Roaming\Bitcoin 2016-11-21 08:56:23 Using data directory C:\Users\7850fr\AppData\Roaming\Bitcoin 2016-11-21 08:56:23 Using config file C:\Users\7850fr\AppData\Roaming\Bitcoin\bitcoin.conf 2016-11-21 08:56:23 Using at most 125 connections (2048 file descriptors available) 2016-11-21 08:56:23 Using 4 threads for script verification 2016-11-21 08:56:23 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2016-11-21 08:56:23 scheduler thread start 2016-11-21 08:56:23 Using wallet wallet.dat 2016-11-21 08:56:23 init message: Verifying wallet... 2016-11-21 08:56:23 CDBEnv::Open: LogDir=C:\Users\7850fr\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\7850fr\AppData\Roaming\Bitcoin\db.log 2016-11-21 08:56:23 Bound to [::]:8333 2016-11-21 08:56:23 Bound to 0.0.0.0:8333 2016-11-21 08:56:23 Cache configuration: 2016-11-21 08:56:23 * Using 2.0MiB for block index database 2016-11-21 08:56:23 * Using 8.0MiB for chain state database 2016-11-21 08:56:23 * Using 2990.0MiB for in-memory UTXO set 2016-11-21 08:56:23 init message: Loading block index... 2016-11-21 08:56:23 Opening LevelDB in C:\Users\7850fr\AppData\Roaming\Bitcoin\blocks\index 2016-11-21 08:56:23 Opened LevelDB successfully 2016-11-21 08:56:23 Using obfuscation key for C:\Users\7850fr\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000 2016-11-21 08:56:23 Opening LevelDB in C:\Users\7850fr\AppData\Roaming\Bitcoin\chainstate 2016-11-21 08:56:23 Opened LevelDB successfully 2016-11-21 08:56:23 Using obfuscation key for C:\Users\7850fr\AppData\Roaming\Bitcoin\chainstate: e6cf4fb809239da2 2016-11-21 08:56:29 LoadBlockIndexDB: last block file = 309 2016-11-21 08:56:29 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=5, size=3913220, heights=367145...367495, time=2015-07-27...2015-07-29) 2016-11-21 08:56:29 Checking all blk files are present... 2016-11-21 08:56:29 LoadBlockIndexDB: transaction index disabled 2016-11-21 08:56:29 LoadBlockIndexDB: hashBestChain=0000000000000000118998d9ef2128c646ae70544947f5c05c8b72faf6c7ff9b height=366170 date=2015-07-20 14:34:15 progress=0.618733 2016-11-21 08:56:29 init message: Rewinding blocks... 2016-11-21 08:56:31 Corruption: block checksum mismatch 2016-11-21 08:56:31 *** System error while flushing: Database corrupted 2016-11-21 08:56:33 Aborted block database rebuild. Exiting. 2016-11-21 08:56:33 scheduler thread interrupt 2016-11-21 08:56:33 Shutdown: In progress... 2016-11-21 08:56:33 StopNode() 2016-11-21 08:56:33 Corruption: block checksum mismatch 2016-11-21 08:56:33 *** System error while flushing: Database corrupted
submitted by DakotaChiliBeans to Bitcoin [link] [comments]

Bitcoin outperformed Vision Hill Crypto Fund Composite index returns by more than 100% in 1H19 - The Block Crypto

Bitcoin outperformed Vision Hill Crypto Fund Composite index returns by more than 100% in 1H19 - The Block Crypto submitted by prnewswireadmin to cryptonewswire [link] [comments]

Bitcoin Cash SV block explorer now indexing!

submitted by MattAbrams to btc [link] [comments]

moved the bitcoin blockchain folder and made a symlink....

perms are fine, tested etc for that user.
selinux is set to permissive.
WTF is wrong with the client?
bitcoin-qt:
Error loading block database.
Do you want to rebuild block database now?
debug.log:
2016-12-04 04:17:07 init message: Loading block index... 2016-12-04 04:17:07 Wiping LevelDB in /home/scrubbed/.bitcoin/blocks/index 2016-12-04 04:17:07 Opening LevelDB in /home/scrubbed/.bitcoin/blocks/index 2016-12-04 04:17:07 IO error: /home/scrubbed/.bitcoin/blocks/index: Invalid argument 2016-12-04 04:17:09 scheduler thread interrupt 2016-12-04 04:17:09 Shutdown: In progress... 2016-12-04 04:17:09 StopNode() 2016-12-04 04:17:09 Shutdown: done 
submitted by javi404 to Bitcoin [link] [comments]

Ability to invest in Bitcoin Trust, Block chain Opportunities ETF and CryptoCurrency Index Fund under registered plan (TFSA/RRSP) coming soon to Canada

submitted by cdnbbboy59 to BitcoinCA [link] [comments]

Help! Assertion failed bitcoin core debug.log

2017-03-31 20:49:31 Bitcoin version v0.14.0 2017-03-31 20:49:31 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2017-03-31 20:49:31 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..." 2017-03-31 20:49:31 Assuming ancestors of block 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90 have valid signatures. 2017-03-31 20:49:32 Default data directory C:\Users\topher\AppData\Roaming\Bitcoin 2017-03-31 20:49:32 Using data directory C:\Users\topher\AppData\Roaming\Bitcoin 2017-03-31 20:49:32 Using config file C:\Users\topher\AppData\Roaming\Bitcoin\bitcoin.conf 2017-03-31 20:49:32 Using at most 125 automatic connections (2048 file descriptors available) 2017-03-31 20:49:32 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements 2017-03-31 20:49:32 Using 2 threads for script verification 2017-03-31 20:49:32 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2017-03-31 20:49:32 Using wallet wallet.dat 2017-03-31 20:49:32 scheduler thread start 2017-03-31 20:49:32 init message: Verifying wallet... 2017-03-31 20:49:32 CDBEnv::Open: LogDir=C:\Users\topher\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\topher\AppData\Roaming\Bitcoin\db.log 2017-03-31 20:49:32 Bound to [::]:8333 2017-03-31 20:49:33 Bound to 0.0.0.0:8333 2017-03-31 20:49:33 Cache configuration: 2017-03-31 20:49:33 * Using 2.0MiB for block index database 2017-03-31 20:49:33 * Using 8.0MiB for chain state database 2017-03-31 20:49:33 * Using 290.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space) 2017-03-31 20:49:33 init message: Loading block index... 2017-03-31 20:49:33 Opening LevelDB in C:\Users\topher\AppData\Roaming\Bitcoin\blocks\index 2017-03-31 20:49:33 Opened LevelDB successfully 2017-03-31 20:49:33 Using obfuscation key for C:\Users\topher\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000 2017-03-31 20:49:33 Opening LevelDB in C:\Users\topher\AppData\Roaming\Bitcoin\chainstate 2017-03-31 20:49:33 Opened LevelDB successfully 2017-03-31 20:49:33 Using obfuscation key for C:\Users\topher\AppData\Roaming\Bitcoin\chainstate: 8ef1b2c988c63095
submitted by T0pher90 to Bitcoin [link] [comments]

Size of blockchain vs size on disk [bitcoind node question]

Quick check.
At the time of this posting, the blockchain size appears to be 24.32GB.
The current block appears to be: 332,061.
Yet, on the node I'm running, the blocks are taking up substantially more space:
$du -h /root
4.0K /root/.cache
8.0K /root/.ssh
16K /root/.aptitude
244K /root/.bitcoin/database
610M /root/.bitcoin/chainstate
46M /root/.bitcoin/blocks/index
29G /root/.bitcoin/blocks
29G /root/.bitcoin
29G /root
At this rate, it appears my 40GB VPS will run out of space soon, which is disconcerting because I thought I would be good to go for at least another 6 months on a 40GB machine.
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/vda1 40G 33G 5.0G 87% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
udev 991M 4.0K 991M 1% /dev
tmpfs 201M 316K 200M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 1001M 0 1001M 0% /run/shm
none 100M 0 100M 0% /run/user
More debug info:
bitcoind getinfo
{
"version" : 90300, "protocolversion" : 70002, "walletversion" : 60000, "balance" : 0.00000000, "blocks" : 331737, "timeoffset" : 0, "connections" : 29, "proxy" : "", "difficulty" : 40300030327.89140320, "testnet" : false, "keypoololdest" : 1417064498, "keypoolsize" : 101, "paytxfee" : 0.00000000, "relayfee" : 0.00001000, "errors" : "" 
}
Does anyone know:
  1. If there is a way to decrease this size (are there deletable files that can be purged without purging parts of the blockchain itself?).
  2. What the real math is for VPS hosting of a bitcoind node? For example, if the current blockchain size is 24.32GB, but the bitcoind application actually consumes at least 29GB...it would seem there is substantial file size overhead here...what is this overhead in relation to the size of the blockchain?
I'm trying to figure out exactly what my VPS needs truly are for hosting a node in the cheapest way (not mining or storing coins, just helping the network and learning)...and it seems like Digital Ocean (while I LOVE THEM) may not be the best choice since they do not offer ala carte SSD sizing (you have to go up to a much faster machine to get more space).
Thoughts?
I really like Digital Ocean, but it seems like I will have to wait for them to release ala carte SSD sizing (I was told it would happen in 2015) for them to be a truly efficient hosting solution for running a node.
Can anyone else recommend another VPS host solution that does offer ala carte storage/SSD/HDD sizing?
submitted by gunslinger_006 to Bitcoin [link] [comments]

bitcoind crashing and corrupting chain, can't get the node synced -- known issue? Possible fix?

I'm running Bitcoin Classic from the official PPA on an Atom CPU using 2 GB of RAM and
bitcoind -disablewallet -daemon -dbcache=1000 
to launch bitcoind. Every time I checked, RAM usage was below 1.5 GB. Today, I came back to see the following in the log:
2016-03-12 17:32:29 Pre-allocating up to position 0x1000000 in rev00363.dat 2016-03-12 17:32:29 UpdateTip: new best=000000000000000005efb0fa564aebed1543e91fb7cbb3666f76518d04beeab4 height=381436 log2_work=83.542258 tx=90266769 date=2015-10-31 19:48:01 progress=0.884439 cache=716.5MiB(399486tx) 2016-03-12 17:32:29 UpdateTip: new best=0000000000000000047b1c27126c0a92cc353deed82a8308ec3f14b21f56bae0 height=381437 log2_work=83.542286 tx=90266771 date=2015-10-31 19:42:28 progress=0.884436 cache=716.5MiB(399488tx) 2016-03-12 17:32:31 UpdateTip: new best=000000000000000009b442d95f5c8944916990d3bd73564cfdf06c80ec51f630 height=381438 log2_work=83.542313 tx=90269011 date=2015-10-31 19:48:59 progress=0.884443 cache=718.0MiB(401474tx) 2016-03-12 17:32:33 UpdateTip: new best=00000000000000000e8e6eb74e60af14a855276d2cdb9fc0a4502720e39f9d61 height=381439 log2_work=83.54234 tx=90271316 date=2015-10-31 19:55:44 progress=0.884450 cache=718.8MiB(403323tx) 2016-03-12 17:32:39 ************************ EXCEPTION: St9bad_alloc std::bad_alloc bitcoin in ProcessMessages() 2016-03-12 17:32:39 ProcessMessages(block, 270899 bytes) FAILED peer=12 2016-03-12 17:32:41 ERROR: ConnectBlock(): inputs missing/spent 2016-03-12 17:32:41 Misbehaving: 5.9.101.143:8333 (0 -> 100) BAN THRESHOLD EXCEEDED 2016-03-12 17:32:41 InvalidChainFound: invalid block=00000000000000000be349d51a1fc4cc9a70f9ca067517aeedffbbf83304e5eb height=381440 log2_work=83.542368 date=2015-10-31 20:09:22 2016-03-12 17:32:41 InvalidChainFound: current best=00000000000000000e8e6eb74e60af14a855276d2cdb9fc0a4502720e39f9d61 height=381439 log2_work=83.54234 date=2015-10-31 19:55:44 2016-03-12 17:32:41 ERROR: ConnectTip(): ConnectBlock 00000000000000000be349d51a1fc4cc9a70f9ca067517aeedffbbf83304e5eb failed 2016-03-12 17:32:41 InvalidChainFound: invalid block=00000000000000000be349d51a1fc4cc9a70f9ca067517aeedffbbf83304e5eb height=381440 log2_work=83.542368 date=2015-10-31 20:09:22 2016-03-12 17:32:41 InvalidChainFound: current best=00000000000000000e8e6eb74e60af14a855276d2cdb9fc0a4502720e39f9d61 height=381439 log2_work=83.54234 date=2015-10-31 19:55:44 2016-03-12 17:32:41 connect() to [2001:41d0:1:a5b8::1]:8333 failed: Network is unreachable (101) 2016-03-12 17:32:41 connect() to [2001:470:507d:0:6ab5:99ff:fe73:ac18]:8333 failed: Network is unreachable (101) 2016-03-12 17:32:42 receive version message: /Classic:0.12.0/: version 70012, blocks=402365, us=163.172.136.98:49308, peer=22 2016-03-12 17:32:45 Pre-allocating up to position 0x2000000 in blk00366.dat 2016-03-12 17:32:49 Pre-allocating up to position 0x3000000 in blk00366.dat 2016-03-12 17:32:52 Pre-allocating up to position 0x4000000 in blk00366.dat 2016-03-12 17:32:54 Pre-allocating up to position 0x5000000 in blk00366.dat 2016-03-12 17:32:59 Pre-allocating up to position 0x6000000 in blk00366.dat 2016-03-12 19:01:05 tor: Thread interrupt 
The last line is me rebooting the box. When the node came back up, it started vomiting all over the log, which I assume means the block database is FUBAR (again) and I'll have to delete and re-download everything:
2016-03-12 19:01:30 Bitcoin version v0.12.0.0-unk (Mar 9 2016, 01:41:30) 2016-03-12 19:01:30 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1 2016-03-12 19:01:30 Using OpenSSL version OpenSSL 1.0.1f 6 Jan 2014 2016-03-12 19:01:30 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2016-03-12 19:01:30 Default data directory /home/bitcoin/.bitcoin 2016-03-12 19:01:30 Using data directory /home/bitcoin/.bitcoin 2016-03-12 19:01:30 Using config file /home/bitcoin/.bitcoin/bitcoin.conf 2016-03-12 19:01:30 Using at most 125 connections (1024 file descriptors available) 2016-03-12 19:01:30 Using 2 threads for script verification 2016-03-12 19:01:30 scheduler thread start 2016-03-12 19:01:30 HTTP: creating work queue of depth 16 2016-03-12 19:01:30 No rpcpassword set - using random cookie authentication 2016-03-12 19:01:30 Generated RPC authentication cookie /home/bitcoin/.bitcoin/.cookie 2016-03-12 19:01:30 HTTP: starting 4 worker threads 2016-03-12 19:01:30 Bound to [::]:8333 2016-03-12 19:01:30 Bound to 0.0.0.0:8333 2016-03-12 19:01:30 Cache configuration: 2016-03-12 19:01:30 * Using 2.0MiB for block index database 2016-03-12 19:01:30 * Using 257.5MiB for chain state database 2016-03-12 19:01:30 * Using 740.5MiB for in-memory UTXO set 2016-03-12 19:01:30 init message: Loading block index... 2016-03-12 19:01:30 Opening LevelDB in /home/bitcoin/.bitcoin/blocks/index 2016-03-12 19:01:31 Opened LevelDB successfully 2016-03-12 19:01:31 Using obfuscation key for /home/bitcoin/.bitcoin/blocks/index: 0000000000000000 2016-03-12 19:01:31 Opening LevelDB in /home/bitcoin/.bitcoin/chainstate 2016-03-12 19:01:32 Opened LevelDB successfully 2016-03-12 19:01:32 Using obfuscation key for /home/bitcoin/.bitcoin/chainstate: 0000000000000000 2016-03-12 19:01:41 LoadBlockIndexDB: last block file = 366 2016-03-12 19:01:41 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=120, size=88408331, heights=381171...381988, time=2015-10-30...2015-11-04) 2016-03-12 19:01:41 Checking all blk files are present... 2016-03-12 19:01:41 LoadBlockIndexDB: transaction index disabled 2016-03-12 19:01:42 LoadBlockIndexDB: hashBestChain=00000000000000000e8e6eb74e60af14a855276d2cdb9fc0a4502720e39f9d61 height=381439 date=2015-10-31 19:55:44 progress=0.884403 2016-03-12 19:01:42 init message: Verifying blocks... 2016-03-12 19:01:42 Verifying last 288 blocks at level 3 2016-03-12 19:01:42 ERROR: DisconnectBlock(): added transaction mismatch? database corrupted 2016-03-12 19:01:42 ERROR: ApplyTxInUndo: undo data adding output to missing transaction 2016-03-12 19:01:42 ERROR: ApplyTxInUndo: undo data overwriting existing transaction 2016-03-12 19:01:42 ERROR: ApplyTxInUndo: undo data overwriting existing output 2016-03-12 19:01:42 ERROR: ApplyTxInUndo: undo data adding output to missing transaction 
I thought this may have been a "speciality" of the ARM version I compiled myself when I saw it previously, but now it's happening with official binaries on a completely different platform (still hosted at Scaleway, but their x86_64 based offering, not their ARM offering). Of course, I can't rule out Scaleway somehow being unable to deal with the traffic pattern of bitcoind and corrupting the DB - is there a way to debug that?
Does anyone know what may cause this or what to do against it? I don't believe in the "out of RAM" theory since I also had similar crashes happen on nodes with ridiculous amounts of swap enabled (this box didn't though). I really can't run a node if it's going to keep blowing up.
If any somewhat-well-known developer wants to debug this/have a look at the corrupted database, send me your SSH public key and I'll give you access to the node. There's nothing of value on the box, the cost is limited, and traffic doesn't cost me anything, so I'm happy to let you play with it for a month or so.
submitted by aaaaaaaarrrrrgh to btc [link] [comments]

LedgerX rolls out LXVX, a volatility index for bitcoin - The Block Crypto

LedgerX rolls out LXVX, a volatility index for bitcoin - The Block Crypto submitted by ulros to fbitcoin [link] [comments]

Parallel Bitcoin block validation by abandoning the UTXO-index

submitted by tomtomtom7 to programming [link] [comments]

Bitcoin Cash SV block explorer now indexing!

Bitcoin Cash SV block explorer now indexing! submitted by cryptoallbot to cryptoall [link] [comments]

Bitcoin Cash SV block explorer now indexing!

submitted by ABitcoinAllBot to BitcoinAll [link] [comments]

Can I copy bitcoin core files from one platform to another to avoid rebuilding the entire block index?

So I've been running core on a couple different machines (one Ubuntu, the other Windows) and the Windows box keeps crashing after a day or two. This is really frustrating because each time it crashes it tells me I have to rebuild the block index database, which takes days to finish. Can I simply copy my current files from my Ubuntu machine onto my Windows machine and reopen without having to do all of this, or are the two versions' files incompatible?
submitted by TwinTurboMike to btc [link] [comments]

Need help. "Error Opening Block Database"

Hello I started my computer up today and opened bitcoin to find the message: "Error opening block database. Do you want to rebuild the block database now?" I went through the log file and found this:
Bitcoin version v0.8.5-beta (2013-09-12 13:35:18 +1000)
Using OpenSSL version OpenSSL 1.0.1c 10 May 2012
Startup time: 2013-12-07 22:03:05
Default data directory C:\Users\Warren Flick\AppData\Roaming\Bitcoin
Using data directory C:\Users\Warren Flick\AppData\Roaming\Bitcoin
Using at most 125 connections (2048 file descriptors available)
Using 8 threads for script verification
init message: Verifying wallet...
dbenv.open LogDir=C:\Users\Warren Flick\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\Warren Flick\AppData\Roaming\Bitcoin\db.log
Bound to [::]:8333
Bound to 0.0.0.0:8333
init message: Loading block index...
Opening LevelDB in C:\Users\Warren Flick\AppData\Roaming\Bitcoin\blocks\index
Opened LevelDB successfully
Opening LevelDB in C:\Users\Warren Flick\AppData\Roaming\Bitcoin\chainstate
Opened LevelDB successfully
LoadBlockIndexDB(): last block file = 91
LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=299, size=65504445, heights=268263...268561, time=2013-11-06...2013-11-08)
LoadBlockIndexDB(): transaction index disabled
LoadBlockIndexDB(): hashBestChain=000000000000000239e967c1e1f03a75b94ccc34724bc8258fb6d7dcd8aa355b height=268524 date=2013-11-08 11:07:10
init message: Verifying blocks...
Verifying last 288 blocks at level 3
LevelDB read failure: Invalid argument: not an sstable (bad magic number)
Flush(false)
DBFlush(false) ended 0ms
StopNode()
Flushed 0 addresses to peers.dat 31ms
Committing 144 changed transactions to coin database...
Flush(true)
DBFlush(true) ended 0ms
Anybody know a solution?
submitted by MoAmmoFoJamo to BitcoinBeginners [link] [comments]

Bitcoin Cash Is Volatility Leader in Block Tribune Index

Bitcoin Cash Is Volatility Leader in Block Tribune Index submitted by Cryptoknowledge to Bitcoincash [link] [comments]

But how does bitcoin actually work? - YouTube Why Blockchain Matters More Than You Think! - YouTube BITCOIN में INVESTMENT करें या नहीं I Complete Analysis I ... How to Mine Bitcoin with Nicehash 2019 - YouTube How Does Blockchain Work? - YouTube

My bad, the link is for a block that was back in 28 Jul 2013 14:57:27 GMT. Basically my take is that block height is the block id in the main block chain, but block index is the index number in blockchain.info database, as amaclin mentioned they might be two different transaction ids (or also double spends) that one of them would end up in the main blockchain, so the block-index is always ... XBX Bitcoin Index. A robust bitcoin index, uniquely designed to prevent manipulation, serving as the reference rate for tens of millions of dollars of registered derivative products. Data Services. Consolidated API's, historical trade and order book data, advanced indexes, and customizable algorithms. Bitcoin block file pruning – What is it and how it works? The Bitcoin blockchain data contains all transaction history from the day Bitcoin was created to till date. With 1MB block size and 10 minutes block time the size of the chain grows larger and larger. Digital money that’s instant, private, and free from bank fees. Download our official wallet app and start using Bitcoin today. Read news, start mining, and buy BTC or BCH. The number of Bitcoins generated per block starts at 50 and is halved every 210,000 blocks (about four years). Bitcoin transactions are broadcast to the network by the sender, and all peers trying to solve blocks collect the transaction records and add them to the block they are working to solve. Miners get incentive to include transactions in ...

[index] [28396] [23742] [1476] [19850] [6342] [9107] [30104] [6740] [33832] [32826]

But how does bitcoin actually work? - YouTube

Subscribe here: https://goo.gl/9FS8uF Become a Patreon!: https://www.patreon.com/ColdFusion_TV The Blockchain and it's potential simply explained. Hi, welcom... For more information: https://www.bitcoinmining.com and https://www.weusecoins.com What is Bitcoin Mining? Have you ever wondered how Bitcoin is generated? T... Learn basics about blockchain. By watching this video you'll get to know about blockchain by its definition, understand what, who and how secures the chain o... How to Mine Bitcoin with Nicehash 2019 www.nicehash.com Support with crypto: https://streamlabs.com/brandoncoin1#/crypto Easy way to get started mining crypt... Start trading Bitcoin and cryptocurrency here: http://bit.ly/2Vptr2X Bitcoin is the first decentralized digital currency. All Bitcoin transactions are docume...

#