Bitcoin (BTC) | Ternio BlockCard™ Bitcoin Virtual Debit Card

Testnet is currently on non-BIP101 (legacy) chains. More fork tests will follow.

We turned off the hashpower on the BIP101 fork at the end of our testing today. After I went to sleep, it seems someone started hashing on the legacy fork, and the work on that chain overtook the BIP101 fork. These are from an XT node that I know was following the big-block fork, and has several 9 MB blocks in its database:
./bitcoin-cli getblock 000000003199e2651d08bb2282d0896128d04ac3bf82f344d3ab92bf0061c80b | grep height "height" : 585471 ./bitcoin-cli getblockhash 585471 0000000000324544abe2531548faec6525a856999f3b46ecf9128a3f5b273d24 
Those are not the same hash. Not the same block. The first block was orphaned at height 585471, but the second block is currently confirmed. Here's another interesting block for the records:
./bitcoin-cli getblock 0000000015cbe557995bf95861d66231d01513ba99f06d23854522272c9049c3 | less "hash" : "0000000015cbe557995bf95861d66231d01513ba99f06d23854522272c9049c3", "confirmations" : -1, "size" : 9115445, "height" : 586921, "version" : 536870919, "merkleroot" : "6fcc61f29be259c74bc95e8f57c249678572b82b343b6b2bb62897ce1cfd7283", tx: [ .... (9.1 MB of tx go here) ... ] "time" : 1447195582, "nonce" : 3149336320, "bits" : "1c276440", "difficulty" : 6.49874805, "chainwork" : "0000000000000000000000000000000000000000000000067d572257e0d8ef4b", "previousblockhash" : "0000000020e32b6f8f80950b3bb888294a8ece8e61b6ee4b0fed6800d0a44209" } 
That's from a sequence of (IIRC) about five 9.1 MB blocks that we mined over the course of 7 minutes. It's since been reorged out by an empty Legacy block:
./bitcoin-cli getblock `./bitcoin-cli getblockhash 586921` { "hash" : "00000000004572422af0fd54ac158ff430bf60003c54db27eb2e953d4ae2aa4c", "confirmations" : 14985, "size" : 262, "height" : 586921, "version" : 4, "merkleroot" : "857b0723d7999341cd0b9ff9fa0e112dbbb19535dc32c7f06d3721a528c0021a", "tx" : [ "857b0723d7999341cd0b9ff9fa0e112dbbb19535dc32c7f06d3721a528c0021a" ], "time" : 1447140611, "nonce" : 2663112535, "bits" : "1c24a880", "difficulty" : 6.98332357, "chainwork" : "00000000000000000000000000000000000000000000000677759d3b1ee4737d", "previousblockhash" : "00000000007947bac4fb9dbc759704958bc38c2050f7cd236c2a7e0b8c859958", "nextblockhash" : "000000000048c36f0ed2bb68145ea4376ed4facfbbc020726204162f95692387" } 
The second block was mined 54971 seconds or 15.27 hours later.
So far, the testnet chain has forked twice when it should have, and it has reorged twice when it should have. The first reorg was caused by us switching to Core to overtake the BIP101 branch. The second reorg was caused by us switching off our hashpower, and someone else overtaking the BIP101 branch. So far I have not found any behavior that is incorrect.
Edit Nov 12th: We're currently focusing on developing tools to collect data from subsequent tests right now. We should be able to fork pretty much whenever we want as long as we leave the hashrate off when we're not using it. If we leave the hashrate on, it's (a) expensive, and (b) harder to test the forking behavior since we'd have to hash on Core to get it to catch up first.
submitted by jtoomim to bitcoinxt [link] [comments]

How to trustlessly verify current status of Segwit

Bitcoin is a trustless system. The motto is "Don't trust, verify!". In this spirit I wanted to be able to tell how many blocks among last 2016 are signalling Segwit support. So I wrote a simple bash script:
#!/bin/bash YES=0; NO=0 for i in $(seq $[$(bitcoin-cli getblockcount)-2015] $(bitcoin-cli getblockcount)); do bitcoin-cli getblock $(bitcoin-cli getblockhash $i)| grep '"version"' | sed -e 's/^.*: /obase=2;/' -e 's/,$//' | bc | grep -q '1.$' && YES=$[$YES+1] || NO=$[$NO+1] done echo "Supporting: $YES, opposing: $NO" 
You can run it on your full node to calculate current status. It takes some time, so be patient. Example output from my node:
Supporting: 11, opposing: 2005 
(As somebody already mentioned, Slushpool started to signal prematurely.)
The script just asks bitcoind how many blocks there are, then asks hash of each block with number from (inclusive range) and for each hash it asks for block, to get version. Version is converted to binary and then appropriate bit is grepped and counted.
If you ever see Supporting: 1916 (or more) at the end of retarget period, you know Segwit locked-in. It should even work on older clients, so you can activate manually. :)
Enjoy!
Update: as Totont01 pointed out, you have to count within retarget period.
submitted by kixunil to Bitcoin [link] [comments]

GetBlock.io is Going Live! Fee-free Access to Full Blockchain Nodes

Hello!
At GetBlock we provide connection for the most popular cryptocurrencies nodes via an open API (JSON-RPC). There is no need to deploy a node yourself, our service allows you to connect to the blockchain via a full node without having to pay a fee.
We are constantly developing and adding new nodes, on the contrary, the connection always stays put — fast and secure 24/7. At the moment, GetBlock offers nodes of more than 20 cryptos, including Bitcoin (BTC), Ethereum (ETH), Monero (XMR), and Litecoin (LTC).
The platform is quite suitable for young entrepreneurs and beginners, as well as for crypto developers and blockchain users, for all those who have neither time nor resources to run their own full node.
To start using the node, please get your personal and free API key. Tell us about your project or why you need access to blockchain data, and we will grant you a free API key.
If you do have any further questions or partnership offers, feel free to contact us via email: [[email protected]](mailto:[email protected])
submitted by getblockio to u/getblockio [link] [comments]

Bitcoin Genesis Block?

Is there a way to view the message Satoshi Nakamoto stored in the genesis block?
Can that be done via a block explorer or something similar?
Just curious.
submitted by bullett007 to Bitcoin [link] [comments]

Getblock Nodes. Free access to blockchain nodes

Hello!
We are a multi-block explorer, and we have several blockchain nodes:
In the near future we are expecting the addition :)
If you are interested in getting a free access to blockchains API (JSON-RPC), simply follow the link (Feedback form at the bottom of the page).
Tell us about your project or why you need access to blockchain data, and we will grant you a free API key.
Since as a result we become partners, and all serious partnerships are public, we will have to exchange active links in the «Partners» section on our websites.
submitted by getblockio to u/getblockio [link] [comments]

How to retrieve latest block header data in the bitcoin network?

Hi, I'm trying to find out how to get information in a C program by connecting to the bitcoin network? I don't really know much about HTTP and internet retrieving, I need information such as merkleroot, target, version etc. of a blockheader so I can find the nonce value (solution) to them.
Can someone point m in the right direction?
submitted by gradschl to Bitcoin [link] [comments]

Configuring bitcoin full node for faster RPC calls

I have been working with a bitcoin full node and attempting to parse the blockchain data, whilst storing it in an external database.
The script I am using iterates through each block using getblock[hash;2] which populates multiple tables. However in order to get the current blocks input values we have to perform an expensive getRawTransaction each previous txid.
We have singled this out as the bottleneck in the code for most time taken, rendering the script very slow. We have also tried using RPC batching but this also takes considerable amount of time, potentially more with a memory overhead.
I am wondering if there is a best configuration of the daemon to improve RPC call speed? i.e. using rpcthread/queue, increasing dbcache etc.
Another option would be to implement blocks only mode, by reducing the bandwidth could this improve RPC commands?
Bitcoin Core Daemon version v0.16.0.0-g4b4d7eb255
Server Details OS-Ubuntu 16.04 32 GB ram
submitted by dandan4561 to Bitcoin [link] [comments]

Observe for yourself: Segwit allows 2 MB blocks in the typical scenario

Basic English explanation of the process

To demonstrate this, I take each block, figure out the average transaction size and weight, calculate how many of these segwit would allow in a block, and then measure the total sizes of them.
Because the generation transaction is inherently unusual, and few transactions make too small a sample size to be meaningful, I exclude blocks with fewer than 16 transactions (ie, empty blocks).
Finally, I take the average of these segwit block sizes.

The result

25th pct: 1807737 Average: 1890429.153079902 90th pct: 2062659 Largest: 2816041 
Yes, 1.890429 MB is close enough that I'm going to round it up to 1.9 MB or even 2 MB considering the Notes below.

How to reproduce this

Note I do all this stuff on Linux. If you don't know how to use Linux yet, get a Raspberry Pi and learn. ;)
1. Build custom bitcoind to calculate max segwit block sizes.
Apply this patch to your bitcoin code and recompile:
curl https://gist.githubusercontent.com/luke-j62435b3fb80fcf9c12a4629be02c5861/raw/e7baefecff05322277773410ec5e841164a54bcb/segwit_equiv_hack.diff | patch -p1 make 
2. Generate table of max segwit block sizes.
[Re]start your custom bitcoind, and for each block, print its height, block hash, max segwit block size, and transaction count.
first_block=412404 last_block=465000 while [ $first_block -le $last_block ]; do blkhash=$(bitcoin-cli getblockhash $first_block); echo "$first_block $blkhash $(bitcoin-cli getblock $blkhash | python -c 'import json, sys; j = json.load(sys.stdin); print("%d %d" % (j["segwit_equiv_hack"], len(j["tx"])))')"; let first_block=first_block+1; done > data 
This is looking at the last 1 year of blocks.
3. Calculate average (and other stats) of statistically-useful max segwit block sizes.
Save this Python script to a file, then run it: python size_statistics.py < data

Notes

  1. These statistics are assuming every single block is full, and with the same ratio of spam/non-spam as presently. In a less extreme scenario, if a block maxed out at 1.8 MB, the 200k of transactions left would simply get mined in a 2.2+ MB block instead since the average block size wouldn't be the average filled block size.
  2. The network currently does not have any Lightning or sidechain usage yet. It is likely these will weigh heavier on witness data, and thereby expand the block sizes further, possibly even hitting 3 MB.
submitted by luke-jr to Bitcoin [link] [comments]

...was I just shadow banned from /r/Bitcoin ?

I replied to theymos , regarding the bitcoin core client's RPC command: invalidateblock. I asked if this would have really allowed a node to manually fork if a block was discovered to be infected from the <0.16.3 vulnerability.
My question/reply revolved around whether or not that would do anything other than stall the node, since the getblocks message only returns a list of block hashes for the "best" chain, so the node wouldn't receive any blocks until a fork beat out the corrupted one.
It appears my comment does not show up in incognito. Curious if anyone else can see my comment or if I was shadow banned long ago...
If I was actually shadowbanned, then I'm a bit more than miffed. I'm genuinely asking about the behavior of the protocol to make sure my logic in Bitcoin Verde's implementation is correct. Cool.
EDIT: The comment chain I'm referring to: https://www.reddit.com/Bitcoin/comments/9hkoo6/new_info_escalates_importance_upgrading_to_0163/e6d4u9q/
EDIT 2: theymos : Thanks for the reply, and if I was shadow-banned, thanks for the unban. I wish you guys would reconsider your willy-nilly banning.
EDIT 3: ...okay. What is happening here? My first reply to theymos is showing up (presumably because he himself has replied), but now my 2nd reply isn't showing up? I'm either still shadowbanned and theymos is individually approving my posts, or any reply to a moderator must be approved first before being shown, or there's a massive delay between posting and being visible to others. I'd like to believe it's the lattermost scenario, but that feels naive given the subreddit's reputation.
EDIT 4: My most recent reply is now showing up. Great. I have no idea what is going on or if I'm actually shadowbanned. Regardless, I don't care anymore; I have more important things to do than investigate.
submitted by FerriestaPatronum to btc [link] [comments]

sPRUNED Bitcoin Client - A new release is out [0.0.5]

sPRUNED Bitcoin Client - A new release is out [0.0.5]
Hello everyone.

I'd like to announce a new release of sPRUNED Bitcoin client.


spruned is a bitcoin client for lightweight systems.it doesn't need to store the blockchain on the disk, just the headers.128mb ram & 500mb hdd should be fairly enough to keep it up & running.
Supports both Bitcoin Mainnet and Testnet.
It doesn't rely on any central authority, use both the Electrum and the P2P Bitcoin Network in real-time to gather the data you need.
The new release (latest is v0.0.5.1) have:

  • lot of bugfixing all around
  • a robusts P2P connectionpool with a 100% getblock hitrate
  • an electrum servers quorum-based fee estimation
  • proxies and tor support
  • less memory usage for low end devices
  • RPC API improvements

The new release is cool enough to back BTC-RPC-Explorer with Tor Support:


https://preview.redd.it/zdgvz55lxbl21.jpg?width=1606&format=pjpg&auto=webp&s=44ac3b67cc49369b04f71dab691dabf772d959aa

And is able to keep Clightning in Sync on a low-end VPS (High bandwidth consumption, don't use metered connections).

https://preview.redd.it/hjs3blryybl21.png?width=1913&format=png&auto=webp&s=5ffa4bf8c7054bf6291b29d53dc71e715c7cf1ae
Give it a try!
$ pip install spruned*
$ spruned --daemon
$ bitcoin-cli getblockchaininfo

*dependencies required, check the README :)

https://github.com/gdassori/spruned/releases
https://pypi.org/project/spruned/
https://twitter.com/KHS9NE


submitted by case666 to Bitcoin [link] [comments]

Bitcoin Unlimited - Bitcoin Cash edition 1.1.2.0 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.1.2.0, November 12, 2017) from:
 
https://www.bitcoinunlimited.info/download
 
This release is compatible with the Bitcoin Cash with the upcoming planned hard fork that will take place on Nov 13th
 
The main change of this release is the introduction of a new difficulty adjustment algorithm (DAA) that replaced the old EDA (Emergency Difficulty Adjustment). If you are interested in more detail about the new DAA you could find more details in the technical specification.
Another major change is the introduction of a new format to store the UTXO (chainstate) database. The UTXO storage has been indexed per output rather than per transaction. The code has been ported from the Bitcoin Core project. This feature brings advantages both in terms of a faster reindex and IBD operation, lower memory consumption, on the other hand the on-disk space requirement increased of about 15%.
Other notable changes:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/BitcoinCash/doc/release-notes/release-notes-bucash1.1.2.0.md
 
Ubuntu PPA is in the process of being updated.
submitted by s1ckpig to btc [link] [comments]

BlockParser - A way to get the balance of all bitcoin addresses

For same time, I was searching for a way to get the balance of all bitcoin addresses in order to do statistical analysis of the wealthy distribution. If finally found a way to do it without using an external API such as blockchain.info. This method will allow you to create a list of all bitcoin addresses ordered by balance, excluding empty ones. This does not work properly for addresses involved in multisignature transactions.
Prerequisites:
Step 1 – Parse all blocks using this small program
#!/usbin/perl # File: blockParser.pl # Author: Saulo Fonseca # Licence: GNU GPLv3 use warnings; use strict; use JSON; # Get argument as block number my $blockNumber = $ARGV[0] + 0; # Convert to int # Get all transactions my $blockHash = `bitcoin-cli getblockhash $blockNumber`; chomp($blockHash); my $out = `bitcoin-cli getblock $blockHash`; my $json = decode_json($out); if (defined $json->{'tx'}) { my $txs = $json->{'tx'}; foreach my $txHash (@$txs) { $out = `bitcoin-cli getrawtransaction $txHash 1`; $json = decode_json($out); if (defined $json->{'vin'}) { # Get all input transactions my $vins = $json->{'vin'}; foreach my $vin (@$vins) { if (defined $vin->{'txid'}) { my $tx = $vin->{'txid'}; my $index = $vin->{'vout'}; printf("%s\t%d\tdel\n",$tx,$index); } } } if (defined $json->{'vout'}) { # Get all output addresses my $vouts = $json->{'vout'}; foreach my $vout (@$vouts) { if (defined $vout->{'scriptPubKey'}->{'addresses'}) { my $keys = $vout->{'scriptPubKey'}->{'addresses'}; my $value = $vout->{'value'}; my $index = $vout->{'n'}; foreach my $key (@$keys) { printf("%s\t%d\t%s\t%.8f\n",$txHash,$index,$key,$value); } } } } } } 
This program will get the height of the block as an argument and return a tab separated output with the following columns:
Here is an example of the output for the block 100000 (with cropped TXIDs in order to fit the reddit width):
8c14f0...d06d87 0 1HWqMzw1jfpXb3xyuUZ4uWXY4tqL2cW47J 50.00000000 87a157...382e03 0 del fff252...9702c4 0 1JqDybm2nWTENrHvMyafbSXXtTk5Uv5QAn 5.56000000 fff252...9702c4 1 1EYTGtG4LnFfiMvjJdsU7GMGCQvsRSjYhx 44.44000000 cf4e29...bf3ec3 1 del 6359f0...236ec4 0 1H8ANdafjpqYntniT3Ddxh4xPBMCSz33pj 0.01000000 6359f0...236ec4 1 1Am9UTGfdnxabvcywYG2hvzr6qK8T3oUZT 2.99000000 f4515f...72600b 0 del e9a668...b80c1d 0 16FuTPaeRSPVxxCnwQmdyx2PQWxX6HWzhQ 0.01000000 
You should process all blocks using this program and send the output to a text file. The command in bash that does it is:
seq -w 1 555000 | while read i; do (./blockParser.pl $i >> blocks.txt); done 
This will take a while depending on the performance of your system. However, it must be done only one time.
Step 2 – Export the list of all spent transactions
Use the following command to export all spent transactions on all processed blocks on step 1:
grep -h del blocks.txt | cut -f1,2 > spent.txt 
The lower cap letter L in “del” will not match any entry on a hex string nor on an address, as it is not allowed in base58.
Step 3 – Get the list of all UTXO
By removing all spent transactions, you have the list of all UTXO (unspent transactions output). Do it by running:
grep -v -f spent.txt blocks.txt > utxo.txt 
Step 4 – List all addresses balances
Using the UTXO list, you can get the balances of all addresses by running:
cat utxo.txt | cut -f3,4 | awk '{ seen[$1] += $2 } END { for (i in seen) printf "%.8f\t%s\n", seen[i], i }' | sort -n -r > anyBTC.txt 
Conclusion
You can import this last file on your favorite analysis program in order to have a better idea how the distribution of bitcoins over the addresses is.
PS: After the arrival of new blocks by the network, you only need to process the step 1 for the new blocks and repeat all the other steps in order to have an updated version of the files.
submitted by sauloqf to Bitcoin [link] [comments]

PIVX Core Wallet 3.0.5 final release (November 13th, 2017) - Mandatory Upgrade

Github release link
Forum Post

Important Notes

Upgrade instructions

1- Download the appropriate release for your platform from the Github release link. For command line installs/updates this link may help.
2- Start up your client and see if you are on the wrong chain by using this link (Am I forked?) or manually comparing your latest block hash against the [block explorer](www.presstab.pw/phpexplorePIVX/index.php#)
3- If you are on the correct chain, let it fully sync (or as far as it will go) and then repeat step 2. If you are still on the right chain move on to step 4. If you're on the wrong chain, download the chainstate from this link (mirror) and follow the instructions to install it. Do NOT delete wallet.dat or your backups folder. Once this is done, restart your client and let it finish syncing
  1. stop your wallet and/or daemon
  2. locate the folder with the blockchain folders (usually ~/.pivx/)
  3. do a complete(!) backup of this folder in case something goes wrong
  4. completely remove the folders "blocks", "chainstate", "sporks" and "zerocoin"
  5. download one of the snapshot-files (preferably the newest one) above into this folder
  6. unpack the snapshot file: 'unzip '
  7. the folders deleted above are now replaced by the ones from the snapshot
  8. restart your wallet and/or daemon
4- On this step you should be fully synced and on the right chain. Using the debug screen or pivx-cli, use the command
spork show 
to output your spork status. Have a look at spork 16 and make sure the value is 1510179528 (now 1609459199). If it is, go ahead and start staking.
If you are having trouble getting the correct value for spork 16, try adding nodes to your pivx.conf file that are protocol 70912. A list of 70912 nodes can be found at http://www.presstab.pw/phpexplorePIVX/nodes.php . This can be done from the debug menu or with pivx-cli by saying
addnode 123.45.67.89 add 

Notable Changes

libzerocoin Exploit Fix

zPIV relies on a 3rd party library called libzerocoin. All currencies that utilize the zerocoin protocol use libzerocoin, and many of those currencies have been exposed to an exploit which allowed for the creation of multiple zero-knowledge spending proofs for one single zerocoin mint. The PIVX developers were able properly identify the exploit, track down any fraudulent spending proofs, link the fraudulent spending proofs with their one valid proof that they were mutated from, and remove any mints from the accumulators that were derived from the invalid spends.

zPIV Maintenance Mode Spork

Handling the above noted libzerocoin exploit required the PIVX team to immediately release a patched wallet to as many users as possible which rejected bad spends and also disabled all zPIV transactions in general. The process of releasing a patched wallet in such a small time frame is frustrating and difficult for all members of the PIVX team and especially users of PIVX. The PIVX developers have added a new spork which allows for zPIV transacting to be turned on/off without having to release a patched wallet. This will allow much smoother operation if any problems occur in the future, and should also allow exchanges and 3rd party services to continue to operate even if zPIV is in maintenance mode.

Accumulator Code Refactor

The zPIV accumulator code has undergone a major refactor. Accumulators are one of the most essential components of the zerocoin protocol, and also one of the most computationally expensive parts of the protocol. This refactoring speeds up syncing and spending of zPIV by over 5x. The new code also allows for spending of zPIV with only 2 required mints occurring on the network after your mint has been added, whereas before 3 were required. This refactor allows for lighter resource load and a smoother user experience.

Money Supply Indexing

The exploit in libzerocoin threw off some of the wallet's internal money supply calculations for both the zPIV supply and the PIV supply. User's wallet's will automatically recalculate the supply on block 908001. User's also have the ability to recalculate supply using the startup flag reindexmoneysupply.

More Extensive Tracking of zPIV Supply Through RPC

More information has been added to the getinfo and getblock RPC calls, which now display the total zPIV supply as well as the balance for each zPIV accumulator.

Multisig GUI

Provides functionality which is currently only available through raw transactions. Multisignature addresses require signatures from multiple parties before coins belonging to the address are spent. Accessed through the File dropdown menu.

Credits

FAQ

  • Will I lose piv or zpiv?
    • No. Backup your wallet.dat again for good measure and never delete a wallet.dat file.
  • My wallet is stuck on block ?
    • Check if you're forked (Am I forked?) and then check if you're really on v3.0.5. If you're on the right version and chain, just hang tight and your wallet will find a good node to sync with eventually. Contact support if it's more than a few hours and the problem persists
  • My zPIV balance is incorrect
    • Contact support in discord or via the Support Portal. Please note that during the upgrade period and zerocoin maintenance mode there may be delays.
submitted by turtleflax to pivx [link] [comments]

Relic for my offspring

Relic for my offspring submitted by PixelPhobiac to Bitcoin [link] [comments]

Bitcoin ABC 0.18.8 released!

Bitcoin ABC version 0.18.8 is now available from:
https://download.bitcoinabc.org/0.18.8/
This release includes the following features and fixes: - dumpwallet now includes hex-encoded scripts from the wallet in the dumpfile - importwallet now imports these scripts, but corresponding addresses may not be added correctly or a manual rescan may be required to find relevant· transactions - getblock 2 (verbosity = 2) now returns hex values in transaction JSON blobs - Remove miner policy estimator in favor of minimum fees, also remove fee_estimates.dat. Old copies will be left in place. - The log timestamp format is now ISO 8601 (e.g. "2019-01-28T15:41:17Z") - Behavior change: in case of multiple values for an argument, the following rules apply: - From the command line, the last value takes precedence - From the config file, the first value takes precedence - From the config file, if an argument is negated it takes precedent over all the previous occurences of this argument (e.g. "foo=2 \n nofoo=1" will set foo=0) - The configuration files now support assigning options to a specific network. To do so, sections or prefix can be used: main.uacomment=bch-mainnet test.uacomment=bch-testnet regtest.uacomment=bch-regtest [main] mempoolsize=300 [test] mempoolsize=200 [regtest] mempoolsize=50 The addnode=, connect=, port=, bind=, rpcport=, rpcbind= and wallet= options will only apply to mainnet when specified in the configuration file, unless a network is specified.
submitted by jasonbcox to BitcoinABC [link] [comments]

Trying to salvage some coins from 2013. Core (bitcoin-qt.exe v0.8.1-beta on Windows 8.1) is taking weeks to DL the blockchain as expected but keeps crashing now. Can I upgrade to a newer version without losing what I've gotten already (about 75% complete)?

Currently there are 134305 blocks remaining. When I start it up it works pretty smoothly for a while but then slows down. I leave it running while I'm gone but the last several days when I've come back it has crashed and gives me an I/O error, and I have to hit OK then start it back up. It does appear to be further along when I start it back up but not by a whole lot. So this has really slowed my progress. It's reindexed about 75% though, and so I don't want to start over from the beginning.
The drive it is on has ~400gb of free space so that's not the issue. I have 8gb of memory, and the task manager says bitcoin is taking up about 500mb, but it's using 60-85% of my cpu at a time.
If I download a newer version of core, I can just copy/paste the old wallet.dat file, right? But wouldn't it have to start downloading the entire blockchain again from the beginning? If so, is there any quicker method?
While typing this, it crashed twice. It only runs for about 10 minutes.
The version I have doesn't have any settings I can change. I read that there's a db size limit you can change in later versions that could help. This one does have a "debug window" with a command line console but I don't really know what to do with it. Here is a list of available commands: 
addmultisigaddress <'["key","key"]'> [account]
addnode
backupwallet
createmultisig <'["key","key"]'>
createrawtransaction [{"txid":txid,"vout":n},...] {address:amount,...}
decoderawtransaction
dumpprivkey
encryptwallet
getaccount
getaccountaddress
getaddednodeinfo [node]
getaddressesbyaccount
getbalance [account] [minconf=1]
getblock
getblockcount
getblockhash
getblocktemplate [params]
getconnectioncount
getdifficulty
getgenerate
gethashespersec
getinfo
getmininginfo
getnewaddress [account]
getpeerinfo
getrawmempool
getrawtransaction [verbose=0]
getreceivedbyaccount [minconf=1]
getreceivedbyaddress [minconf=1]
gettransaction
gettxout [includemempool=true]
gettxoutsetinfo
getwork [data]
help [command]
importprivkey [label] [rescan=true]
keypoolrefill
listaccounts [minconf=1]
listaddressgroupings
listlockunspent
listreceivedbyaccount [minconf=1] [includeempty=false]
listreceivedbyaddress [minconf=1] [includeempty=false]
listsinceblock [blockhash] [target-confirmations]
listtransactions [account] [count=10] [from=0]
listunspent [minconf=1] [maxconf=9999999] ["address",...]
lockunspent unlock? [array-of-Objects]
move [minconf=1] [comment]
sendfrom [minconf=1] [comment] [comment-to]
sendmany {address:amount,...} [minconf=1] [comment]
sendrawtransaction
sendtoaddress [comment] [comment-to]
setaccount
setgenerate [genproclimit]
settxfee
signmessage
signrawtransaction [{"txid":txid,"vout":n,"scriptPubKey":hex,"redeemScript":hex},...] [,...] [sighashtype="ALL"]
stop
submitblock [optional-params-obj]
validateaddress
verifymessage

submitted by closer_to_the_flame to Bitcoin [link] [comments]

PSA: SegWit changes the format of data returned by JSON-RPC API, thus making it backward-incompatible

As far as I know, all soft-forks so far were backwards-compatible, i.e. a piece of software working with JSON-RPC API doesn't need to be upgraded when a soft-fork is activated. For example, OP_CHECKLOCKTIMEVERIFY will interpreted by old software as OP_NOP2, which is harmless.
But SegWit is different in this respect because it changes data formats.
For example, suppose you use getblock API to get raw block contents and parse it using bitcore-lib to extract some useful information of new blocks. If you happen to use Bitcoin Core 0.13.1, then after SegWit activation, getblock will return data in new format which bitcore-lib cannot understand, so your application will no longer work.
So if your application happens to use affected APIs (getblock is one of them, but I don't have a complete list), you choice is either to:
(I think Bitcoin Core could easily make all APIs backward compatible by transforming data into the old format for old calls and introducing new calls which return data in new format, e.g. getblocksw for segwit-comptable software. But it's too late for this...)
submitted by killerstorm to Bitcoin [link] [comments]

Bitcoin Plus 2.7.0 Release Candidate 2

Bitcoin 2.7.0 Release Candidate 2 is now available to download from the following location.
https://github.com/bitcoinplusorg/xbcwalletsource/releases/tag/v2.7.0rc2
This release updates chainstate and the RPC getblock call to include PoS specific information. The update to chainstate will require a reindex for all users including those who have already updated to 2.7.0rc1. The reindex for users who have already updated is much quicker than the reindex required from 2.6.0 or before to 2.7.0. No changes after RC2 are expected to require another reindex.
submitted by Bushstar to BitcoinPlus_XBC [link] [comments]

REQUEST: Please help me fellas

So i've been playing around, in java (to build some crypto stuff, mainly something for myr) with the bitcoind/qt RPC making calls such as getinfo, getmininginfo, getblock (all of the btc RPC calls) and also have gotten the blocknotify/walletnotify working. However when i try the same methods with the myriadcoind/qt, with the same .conf file as the btc one, i don't get any response from the wallet or it's returning null Json objects? Is there something wrong with my .conf settings?

Enable RPC

server=1 rpcport=8333 rpcallowip=127.0.0.1 rpcuser=v rpcpassword=p 
edit: just to add im using http POST requests which bitcoins rpc responds to, maybe the myriad client doesn't respond to POST, only json rpc calls which would mean i would have to attempt a different kind of implementation?
edit2: i fixed it by chaning my .conf file to look like this
listen=1 rpcuser=v rpcpassword=p rpcport=8332 server=1 rpcallowip=192.168.0.0/24 
seems like the port might of been of since when i tried port 8333 with bitcoins qt it gave me an error.
submitted by illuminatiman to myriadcoin [link] [comments]

Bitcoin Unlimited - Bitcoin Cash edition 1.1.2.0 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.1.2.0, November 12, 2017) from:
 
https://www.bitcoinunlimited.info/download
 
This release is compatible with the Bitcoin Cash with the upcoming planned hard fork that will take place on Nov 13th
 
The main change of this release is the introduction of a new difficulty adjustment algorithm (DAA) that replaced the old EDA (Emergency Difficulty Adjustment). If you are interested in more detail about the new DAA you could find more details in the technical specification.
Another major change is the introduction of a new format to store the UTXO (chainstate) database. The UTXO storage has been indexed per output rather than per transaction. The code has been ported from the Bitcoin Core project. This feature brings advantages both in terms of a faster reindex and IBD operation, lower memory consumption, on the other hand the on-disk space requirement increased of about 15%.
Other notable changes:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/BitcoinCash/doc/release-notes/release-notes-bucash1.1.2.0.md
Ubuntu PPA is in the process of being updated.
submitted by s1ckpig to bitcoin_unlimited [link] [comments]

No SegWit2x Mining, But New "Clashic" Block #504039 Mined

It's unknown if there is no SegWit2x mining because no one has father to fix the purportedly borked code, but this morning I discovered this new "Clashic" block on my Bitcoin ABC 15.0.0 node (output shown is from a "getblock" command):
{ "hash": "0000000000000000000fdfc1041e943e6adfa28a12d97a6720aaa69f19c76435", "confirmations": 1, "size": 32862, "height": 504039, "version": 536870912, "versionHex": "20000000", "merkleroot": "df60ad7d2a7a86bbae97d01a57fd9779550674b1275a212503ceed62c30e1851", "tx": [ "d04e0a84ad71f9daa58539b68e29145bdfcbed1f3dad9cf2ee75f32e7e7b7a07", "8b8d717d41dc6a47b055fa4cf2edadc8afd0813ffc2fc9fe32b13dbfa507b92d", "76b9c4c2d360dd0fb17ed81a5e23560b0259e4695a3c93ec9d612600174cc69e", "76dc1ab2d578c7bd4cc0a5bd7e94a4d1a39bc53404828479506c39a895a2c55e", "772a00ea7346057845d606aa6646c4a54e6bfdbfbe5ebcf6a056726db2a6090f", "be3eb59982b81cdf20f8f554ed059930dd5aead215e8d76997e176ed91fa5e8d", "68963e656719281077e47cdc8597fd72e2e0eafb7b3bd42cf5a6f8c15b077ea7", "35d5b2d1995ce51b9c0ee0566d41ef1a5ee345ff56710a08db18cbc845dab1ad", "832ffcf1fd759eea5e8be4cd6d4e9ff110d6e41b14b537116ee1622a8037524f", "ac6a244c928f5373183fe09de5f6176c3f1bebb0601a5ab0bc93a902ac181d9c", "5159225217c036bbdf940f84eeb68e7159d4b96181557ae84b9693a8bd31fd14", "c8716c483cdd9e97039bb10f3270145fcce0628c21d0b0c9011fd61b64afbd62", "9f1cab7ecbd08d5e68509cef791f5590765c5d25b29570b3d2fd63655550eacb", "8e7c390208ca29eca9d1e852c049ae0649577aadce6a035cb4227ee8d2bc79b7", "67a7814cfa551d5f671417957daa43a85ababe179aafd01a472db5e81cfee0a9", "af2a944cfb428467002029ddb71348a6d4f676d4c883afd9833b96b2e0163778", "54c9bf80f3178860e8561eed8735f81366fa7aa1167418ae864c5eaffe1e3171", "7d71b929f5942fc5f6456f6312b40bd797a53ab90ec09b75a5470ebe4f908730", "e0861a01dc01933d895950588abe1325207b3ed147359c9e6f642ccd24569079", "adc35f6692b05e55a133a11668f1bdb504983e957384537cd14c43e53d02e79a", "cc8583daa110b4ff8af7c0e474e374d669862b0c8280ed837b687062b7009807", "1ce59a31682c33f7725e92909d21c5203200e5274f73a66a185ca10346cf3e60", "92ad14671662523ed09222ea1e7a065c981d4ae547e5897da9f016a3abfd45c7", "bf618000115f09ebef29c3d67f2fcbf7da983aa57c72fb9cca60c8d426132eba", "0de408c0f8620be7ea787b2221a189c95becca7465372f5598660367795d8c57", "05845896a02f96e25ac7535a0d9660d3d15e552670b0d38b451c83f5b3590395", "d55f4d32114d94f00aa5540c4c91a9173774807f664de3fdb58c31f5288292fe", "83df5aaebb4f2718cc3466a00db2ff9975613e8bfba21f000ad381a9dc53d4ef", "e3e9cfe8fee9bb2f6c4bd104da5c33b5dd05e382add2abd8ca706379539124fd", "2a5cd1c9b0590ea310dcd363cc80b7b71f4c94135f52ce05a1a245c2df2b6f3c", "d58d23c4bee43b3816d66def6b783d8525bedbe5a53e849857c2bffe5e35872a", "11f5eb1134d53c468d4aeac02aac2629693641af1a9a85a80c64f7c774808c0e", "e2dd305837478d4cd8129c9eb018e85d2776adab7c41c478c4a1f36a33a3406f", "a505ea0a6723c074747e9202f872aa8ba64aa4d5fd692ebfd6592f581eee9391", "149a42c19244fbbb6004a67672b671dee430521a37776feb2f22aef38e5af6bc", "62bc476c2e254eb1a6b293cfae567b157e51267b34f34ee352984392e3ef0f3f", "8cfe5c06a1880b348ee7758cfaa78da6654c6c62a2556c780bff34783bebf5c2", "f8e50ef95d0a096c43459fccf3ad44f27238420333f02d86e0337d1ba58361a6", "400fc7be490b11ebe2baf34961d435a52d3e14e27d69a76ceae716ed0c97b73a", "cd41a77de8149b7feb019b0e9bcf6113a8ad1f98b1cd1b1e24774247c546de7e", "73eec7d88cd2910c80d7747031ca3ec66dabed9ca372097b31079ac2cbecd65e", "d4513f5e80b1d1e8357dd9d956e0fb77720d53d771cf05a725e787fbed9a4765", "a4eafc3ea854cf39aa69da95a47d7d34e8d6eb4c936bc747cfab1f9b7ffceda4", "e5e24a2f3377d27dff287d08f689145f1de2222526ecc1e3b976d90678dcce55", "a24a9f739e696ff22bf3ac975dd37b9524d16136d024218ca73e2785c1b8ebb2", "ba6bc6d3c3fda070e5eaaa9256b43de390cd22691056b87abcf294383c4b2c48", "d342caa553133eb6e5d92ca8307200202b4e93feea4c41b66c6313604f63dce9", "9ce3a864d94ad274a7030d56bf471e9729d4ca60528ca51c1afb45c50f05b1cd", "8420c8d16bf8fdb9c0072d600770800fbce0ca5edf9dcbb60392c7696b374ea9", "07b514f47a805ca76d461ced9f1ed303af757a326b28c2ab66c3429b1ddb118b", "caa97ac4d21d439d9c464621ff267d5ae96cff88797d67492a641a4535a61618", "4b205add554d62b33cf99206e9d22d30838c455ae699b9d15f57bbbae8d45341", "40264894b3cf0475f961863bc8243598e3df787f70744afe3ef51d0cf78bce13", "1310a1b4592afa101cd0a250c8f6eb57f847442f3ace6ebad923c9d0ca8e2082", "b75c07b0bc9846c89e8181dd02539ff936615bf332d2f3b17851f7bb1009cb3b", "db9565c25b5a4f0819b20b9d75fc18de0aa3b6098d696e08dd24dc86f4916a70", "4f4cac78ee917047426dade6c585bf3a90e435ddca657b2cc5c4f7d7e000bf46", "989a94491bc22e34e89d10159653fcb298e578a00fe8a4f40f7b886d5c3e56f1", "13540550d8c382d177c5c26a278028a7105b238c581d9eabe26dceabe3f6de9a", "345d0c8c2a4139b0dbdcb36bd20d067dbb37ebb1b164a4cc36decf4038d7a0e6", "eaca78839daf5a51b03b341de72c45aad036b17313007a25cabb0466e938cac0", "ece6d98b3c9f0599fd0035df8a333fe73b58c8b8dce1b00d94bd74431aecd6cb", "4515c64c6b43b0e62076d0b6da3ecd3ab8ef0d37baca5f9fcc292ae666d9938f", "db9ac3391fc83cb77bc8aacba72c973e242a544fe8f3589b787008998653174b", "ce1fc9ccf4ec230c212d8b264c3ae0f3714fd74088cc8229a4ec2c61d7c01d09", "ceaf13ee16380f76b39c9668a8b917832befd84513fca6e23c10171c2be5fa8b", "f62d11631a1b1aa4f0f7ad05194fe1235754e4ddb7ac3328894cee02de586fe4", "344de7e964d3d3fc8050e38bb340e57866717b4667126b95b56e99e9a5121caa", "a2efc748eceebdc849cab697bcd0f29c8d291f6fdd6cedbd38ad7506c94fff62", "752bd6e4a45f2976fd741bab0ac69c5a30913697190b504342562176ffc0b3f8", "0ecf83573b6cccbb23e5f6cbfa2024d2078305eb87ad81068effb2ec4a94f089", "f8f543272f8c64ce42b3ec58a1417cd28a1086e08af4f5065508e0a956b67c9d", "f95d3809b1da007551d229c92897b7f42eeba4e2a20bdaf73ef2960ea54d615d", "15b4892e4ba194fd0d0eb8bfb5d297e150340f211e448e958a4df6d9f2496b98", "b790263bbde819192a94cc7c353ce9aa6c61b4a2984c6ed3fdea06a5dfe7007b", "c14c3023ddc3f33df7a328c6eab969753bbb3eae8281d8444b2f02bb691716e3", "8735ab937a1549b22327958a729934ef8b93fb96e71774d745eef7e3fefef4c1", "0fc8e59c96e166a4c42a339665496f594a9a3cf72a7ddc77e4a599ee13a85393", "27c0c14c2f92c0576bcf2c0479743b9339859690a003fa38f78f39bef2c89d46", "3cd7e5d27cd9b476ab8bbae9eeed68412de11f88e69a408a7a73bfb025ebc07d", "8ab042f5440ce60e0f89208e88d7b78d86d2a89ece869c1786771f08c7b4ccc2", "dff05a03b814e3de43863c164a05497ffc0d1713ad13ea581055fe1557ba477d", "efbf9a53dd45823d8e1f36e31ca275bc996a911c968aa149d149a202cb14164d", "8f27f5ba3350b8f5efaba28c5694eea31bca0f7296bb9c0797a2275f18b90269", "a81cd0bc50c18e5ba157ac682f774aa960bd11b7ea1389000996f25c45b86752", "8dfaeebd9a7b8c46bcd7e059f98fd1b98977b2a95ccb7ad3f0387459733971e8", "f0ee1b12b1f9a4e6178c44827ce6059420c486b67d7ca3366140bafc22c80598", "470f43cff2e3aad5603513b625eac0063cf420e1bc6cdf0aa3c1c4fb71736f58", "9be0f2c74de525c3b7d38d030e5b843bb77c79e1a9f924dd79c73da0215f56a3", "2f2a0288d1efe709835f5da8ab0b1303f49a69abdf1222694e13d7d5912e7c6f", "9a5d2ce78d908010ccc9955be7aea9947899eeafc71733102022759e8609e435", "70b51d5c1ae6280451005568313f31b330924aac0d94c562874b7dc53a47abf1", "2ab69bed37f821680bd7d73be104188d6fc207a58496c3431d4124bab595476c", "74b9afc8a3552fda94edf6b99aa7b82da0cca731414048058b6885ab872bbab1", "7f71c6d315aaa1ea7f30c8986d2d8bdb49d540de173dd958775d8c80131d8df2", "4db37453796cd3acf5489e80f491b9191c3a8abbddb5c7450f25be50d6e47af3" ], "time": 1511007107, "mediantime": 1510806460, "nonce": 1427084338, "bits": "180349c7", "difficulty": 334376642271.5151, "chainwork": "0000000000000000000000000000000000000000007cb2b96442a3194e68d5ab", "previousblockhash": "000000000000000000e56c9596b72a1afdecd29762ca0e75ea567696a79aebe9" } 
submitted by AcerbLogic to btc [link] [comments]

Bitcoin Unlimited - Bitcoin Cash edition 1.1.2.0 has just been released

Download the latest Bitcoin Cash compatible release of Bitcoin Unlimited (1.1.2.0, November 12, 2017) from:
 
https://www.bitcoinunlimited.info/download
 
This release is compatible with the Bitcoin Cash with the upcoming planned hard fork that will take place on Nov 13th
 
The main change of this release is the introduction of a new difficulty adjustment algorithm (DAA) that replaced the old EDA (Emergency Difficulty Adjustment). If you are interested in more detail about the new DAA you could find more details in the technical specification.
Another major change is the introduction of a new format to store the UTXO (chainstate) database. The UTXO storage has been indexed per output rather than per transaction. The code has been ported from the Bitcoin Core project. This feature brings advantages both in terms of a faster reindex and IBD operation, lower memory consumption, on the other hand the on-disk space requirement increased of about 15%.
Other notable changes:
 
Release notes: https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/BitcoinCash/doc/release-notes/release-notes-bucash1.1.2.0.md
 
Ubuntu PPA is in the process of being updated.
submitted by s1ckpig to Bitcoincash [link] [comments]

Get Block Card Review I Crypto Debit Card Free Bitcoin - Get BTC - works with BlockChain + Coinbase! Free Bitcoin - Get BTC works with BlockChain + Coinbase! How To Mine 1 Bitcoin in 10 Minutes - Blockchain BTC Miner Pro Bitcoin Q&A: Block height, syncing, and validation

Coin: Bitcoin: Host: c0237261554a: Synchronized: true: Last Block: 639791: Last Block Update: Sat, 18 Jul 2020 20:14:08 UTC: Mempool in Sync: true: Last Mempool Update Blockchain.com is the most popular place to securely buy, store, and trade Bitcoin, Ethereum, and other top cryptocurrencies. Get rid of Bitcoin scam popups and harmful extensions with AdwCleaner If MalwareBytes anti malware or Zemana Anti Malware cannot get rid of this adware, then we recommends to run the AdwCleaner. AdwCleaner is a free removal tool for browser hijacker infections, potentially unwanted applications, toolbars and adware responsible for redirecting To assemble the block data, simply concatenate your block header, number of transactions encoded in Bitcoin varint format, followed by each of the transactions in your block (beginning with the coinbase). If the server has listed "submit/coinbase" in its "mutable" key, you may opt to omit the transactions after the coinbase. getblock¶. getblock "blockhash" (verbosity). If verbosity is 0, returns a string that is serialized, hex-encoded data for block ‘hash’. If verbosity is 1, returns an Object with information about block ‘hash’.

[index] [1869] [3752] [14170] [1874] [24236] [10805] [3951] [11286] [22288] [3655]

Get Block Card Review I Crypto Debit Card

Get The Block Card: https://getblockcard.com/i/aVaxIgEq Play On Moolah: https://rcl.ink/6iV Get The Brave Browser: https://rcl.ink/uWz =====... How to mine Bitcoin is a hot topic, especially with the Bitcoin BTC block reward halving coming up which will reduce the Bitcoins mined each day from 1,800 coins to 900 BTC coins. What it really takes to mine a Bitcoin in 10 Minutes. Firstly I'll show you a special free method to mine Bitcoin and send funds directly to your wallet in 10 minutes! Of course it doesn't ... Best bitcoin script, bitcoin generator or bitcoin adder! this bitcoin 2020 - it bitcoin mining tutorial, new easy earn bitcoin! Use litecoin, Ethereum, Ripple, Monero - earn money free on 2020! Best bitcoin script, bitcoin generator or bitcoin adder! this bitcoin 2020 - it bitcoin mining tutorial, new easy earn bitcoin! Use litecoin, Ethereum, Ripple, Monero - earn money free on 2020!

Flag Counter