Title: Bitcoin Core version 0.12.0 is now available Post by: grue on February 23, 2016, 04:36:27 PM Bitcoin Core version 0.12.0 is now available from:
https://bitcoin.org/bin/bitcoin-core-0.12.0/ (https://bitcoin.org/bin/bitcoin-core-0.12.0/) This is a new major version release, bringing new features and other improvements. Please report bugs using the issue tracker at github: https://github.com/bitcoin/bitcoin/issues (https://github.com/bitcoin/bitcoin/issues) Upgrading and downgrading How to Upgrade If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux). Downgrade warning Downgrade to a version < 0.10.0 Because release 0.10.0 and later makes use of headers-first synchronization and parallel block download (see further), the block files and databases are not backwards-compatible with pre-0.10 versions of Bitcoin Core or other software:
If you want to be able to downgrade smoothly, make a backup of your entire data directory. Without this your node will need start syncing (or importing from bootstrap.dat) anew afterwards. It is possible that the data from a completely synchronised 0.10 node may be usable in older versions as-is, but this is not supported and may break as soon as the older version attempts to reindex. This does not affect wallet forward or backward compatibility. Downgrade to a version < 0.12.0 Because release 0.12.0 and later will obfuscate the chainstate on every fresh sync or reindex, the chainstate is not backwards-compatible with pre-0.12 versions of Bitcoin Core or other software. If you want to downgrade after you have done a reindex with 0.12.0 or later, you will need to reindex when you first start Bitcoin Core version 0.11 or earlier. Notable changes Signature validation using libsecp256k1 ECDSA signatures inside Bitcoin transactions now use validation using https://github.com/bitcoin/secp256k1 (https://github.com/bitcoin/secp256k1) instead of OpenSSL. Depending on the platform, this means a significant speedup for raw signature validation speed. The advantage is largest on x86_64, where validation is over five times faster. In practice, this translates to a raw reindexing and new block validation times that are less than half of what it was before. Libsecp256k1 has undergone very extensive testing and validation. A side effect of this change is that libconsensus no longer depends on OpenSSL. Reduce upload traffic A major part of the outbound traffic is caused by serving historic blocks to other nodes in initial block download state. It is now possible to reduce the total upload traffic via the -maxuploadtarget parameter. This is not a hard limit but a threshold to minimize the outbound traffic. When the limit is about to be reached, the uploaded data is cut by not serving historic blocks (blocks older than one week). Moreover, any SPV peer is disconnected when they request a filtered block. This option can be specified in MiB per day and is turned off by default (-maxuploadtarget=0). The recommended minimum is 144 * MAX_BLOCK_SIZE (currently 144MB) per day. Whitelisted peers will never be disconnected, although their traffic counts for calculating the target. A more detailed documentation about keeping traffic low can be found in /doc/reduce-traffic.md (https://raw.githubusercontent.com/bitcoin/bitcoin/v0.12.0/doc/reduce-traffic.md). Direct headers announcement (BIP 130) Between compatible peers, BIP 130 (http://"https://github.com/bitcoin/bips/blob/master/bip-0130.mediawiki) direct headers announcement is used. This means that blocks are advertized by announcing their headers directly, instead of just announcing the hash. In a reorganization, all new headers are sent, instead of just the new tip. This can often prevent an extra roundtrip before the actual block is downloaded. With this change, pruning nodes are now able to relay new blocks to compatible peers. Memory pool limiting Previous versions of Bitcoin Core had their mempool limited by checking a transaction's fees against the node's minimum relay fee. There was no upper bound on the size of the mempool and attackers could send a large number of transactions paying just slighly more than the default minimum relay fee to crash nodes with relatively low RAM. A temporary workaround for previous versions of Bitcoin Core was to raise the default minimum relay fee. Bitcoin Core 0.12 will have a strict maximum size on the mempool. The default value is 300 MB and can be configured with the -maxmempool parameter. Whenever a transaction would cause the mempool to exceed its maximum size, the transaction that (along with in-mempool descendants) has the lowest total feerate (as a package) will be evicted and the node's effective minimum relay feerate will be increased to match this feerate plus the initial minimum relay feerate. The initial minimum relay feerate is set to 1000 satoshis per kB. Bitcoin Core 0.12 also introduces new default policy limits on the length and size of unconfirmed transaction chains that are allowed in the mempool (generally limiting the length of unconfirmed chains to 25 transactions, with a total size of 101 KB). These limits can be overriden using command line arguments; see the extended help (--help -help-debug) for more information. Opt-in Replace-by-fee transactions It is now possible to replace transactions in the transaction memory pool of Bitcoin Core 0.12 nodes. Bitcoin Core will only allow replacement of transactions which have any of their inputs' nSequence number set to less than 0xffffffff - 1. Moreover, a replacement transaction may only be accepted when it pays sufficient fee, as described in BIP 125 (https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki). Transaction replacement can be disabled with a new command line option, -mempoolreplacement=0. Transactions signaling replacement under BIP125 will still be allowed into the mempool in this configuration, but replacements will be rejected. This option is intended for miners who want to continue the transaction selection behavior of previous releases. The -mempoolreplacement option is not recommended for wallet users seeking to avoid receipt of unconfirmed opt-in transactions, because this option does not prevent transactions which are replaceable under BIP 125 from being accepted (only subsequent replacements, which other nodes on the network that implement BIP 125 are likely to relay and mine). Wallet users wishing to detect whether a transaction is subject to replacement under BIP 125 should instead use the updated RPC calls gettransaction and listtransactions, which now have an additional field in the output indicating if a transaction is replaceable under BIP125 ("bip125-replaceable"). Note that the wallet in Bitcoin Core 0.12 does not yet have support for creating transactions that would be replaceable under BIP 125. RPC: Random-cookie RPC authentication When no -rpcpassword is specified, the daemon now uses a special 'cookie' file for authentication. This file is generated with random content when the daemon starts, and deleted when it exits. Its contents are used as authentication token. Read access to this file controls who can access through RPC. By default it is stored in the data directory but its location can be overridden with the option -rpccookiefile. This is similar to Tor's CookieAuthentication: see https://www.torproject.org/docs/tor-manual.html.en (https://www.torproject.org/docs/tor-manual.html.en) This allows running bitcoind without having to do any manual configuration. Relay: Any sequence of pushdatas in OP_RETURN outputs now allowed Previously OP_RETURN outputs with a payload were only relayed and mined if they had a single pushdata. This restriction has been lifted to allow any combination of data pushes and numeric constant opcodes (OP_1 to OP_16) after the OP_RETURN. The limit on OP_RETURN output size is now applied to the entire serialized scriptPubKey, 83 bytes by default. (the previous 80 byte default plus three bytes overhead) Relay and Mining: Priority transactions Bitcoin Core has a heuristic 'priority' based on coin value and age. This calculation is used for relaying of transactions which do not pay the minimum relay fee, and can be used as an alternative way of sorting transactions for mined blocks. Bitcoin Core will relay transactions with insufficient fees depending on the setting of -limitfreerelay=<r> (default: r=15 kB per minute) and -blockprioritysize=<s>. In Bitcoin Core 0.12, when mempool limit has been reached a higher minimum relay fee takes effect to limit memory usage. Transactions which do not meet this higher effective minimum relay fee will not be relayed or mined even if they rank highly according to the priority heuristic. The mining of transactions based on their priority is also now disabled by default. To re-enable it, simply set -blockprioritysize=<n> where is the size in bytes of your blocks to reserve for these transactions. The old default was 50k, so to retain approximately the same policy, you would set -blockprioritysize=50000. Additionally, as a result of computational simplifications, the priority value used for transactions received with unconfirmed inputs is lower than in prior versions due to avoiding recomputing the amounts as input transactions confirm. External miner policy set via the prioritisetransaction RPC to rank transactions already in the mempool continues to work as it has previously. Note, however, that if mining priority transactions is left disabled, the priority delta will be ignored and only the fee metric will be effective. This internal automatic prioritization handling is being considered for removal entirely in Bitcoin Core 0.13, and it is at this time undecided whether the more accurate priority calculation for chained unconfirmed transactions will be restored. Community direction on this topic is particularly requested to help set project priorities. Automatically use Tor hidden services Starting with Tor version 0.2.7.1 it is possible, through Tor's control socket API, to create and destroy 'ephemeral' hidden services programmatically. Bitcoin Core has been updated to make use of this. This means that if Tor is running (and proper authorization is available), Bitcoin Core automatically creates a hidden service to listen on, without manual configuration. Bitcoin Core will also use Tor automatically to connect to other .onion nodes if the control socket can be successfully opened. This will positively affect the number of available .onion nodes and their usage. This new feature is enabled by default if Bitcoin Core is listening, and a connection to Tor can be made. It can be configured with the -listenonion, -torcontrol and -torpassword settings. To show verbose debugging information, pass -debug=tor. Notifications through ZMQ Bitcoind can now (optionally) asynchronously notify clients through a ZMQ-based PUB socket of the arrival of new transactions and blocks. This feature requires installation of the ZMQ C API library 4.x and configuring its use through the command line or configuration file. Please see docs/zmq.md (https://raw.githubusercontent.com/bitcoin/bitcoin/v0.12.0/doc/zmq.md) for details of operation. Wallet: Transaction fees Various improvements have been made to how the wallet calculates transaction fees. Users can decide to pay a predefined fee rate by setting -paytxfee=<n> (or settxfee <n> rpc during runtime). A value of n=0 signals Bitcoin Core to use floating fees. By default, Bitcoin Core will use floating fees. Based on past transaction data, floating fees approximate the fees required to get into the mth block from now. This is configurable with -txconfirmtarget=<m> (default: 2). Sometimes, it is not possible to give good estimates, or an estimate at all. Therefore, a fallback value can be set with -fallbackfee=<f> (default: 0.0002 BTC/kB). At all times, Bitcoin Core will cap fees at -maxtxfee=<x> (default: 0.10) BTC. Furthermore, Bitcoin Core will never create transactions smaller than the current minimum relay fee. Finally, a user can set the minimum fee rate for all transactions with -mintxfee=<i>, which defaults to 1000 satoshis per kB. Wallet: Negative confirmations and conflict detection The wallet will now report a negative number for confirmations that indicates how deep in the block chain the conflict is found. For example, if a transaction A has 5 confirmations and spends the same input as a wallet transaction B, B will be reported as having -5 confirmations. If another wallet transaction C spends an output from B, it will also be reported as having -5 confirmations. To detect conflicts with historical transactions in the chain a one-time -rescan may be needed. Unlike earlier versions, unconfirmed but non-conflicting transactions will never get a negative confirmation count. They are not treated as spendable unless they're coming from ourself (change) and accepted into our local mempool, however. The new "trusted" field in the listtransactions RPC output indicates whether outputs of an unconfirmed transaction are considered spendable. Wallet: Merkle branches removed Previously, every wallet transaction stored a Merkle branch to prove its presence in blocks. This wasn't being used for more than an expensive sanity check. Since 0.12, these are no longer stored. When loading a 0.12 wallet into an older version, it will automatically rescan to avoid failed checks. Wallet: Pruning With 0.12 it is possible to use wallet functionality in pruned mode. This can reduce the disk usage from currently around 60 GB to around 2 GB. However, rescans as well as the RPCs importwallet, importaddress, importprivkey are disabled. To enable block pruning set prune=<N> on the command line or in bitcoin.conf, where N is the number of MiB to allot for raw block & undo data. A value of 0 disables pruning. The minimal value above 0 is 550. Your wallet is as secure with high values as it is with low ones. Higher values merely ensure that your node will not shut down upon blockchain reorganizations of more than 2 days - which are unlikely to happen in practice. In future releases, a higher value may also help the network as a whole: stored blocks could be served to other nodes. For further information about pruning, you may also consult the release notes of v0.11.0 (https://github.com/bitcoin/bitcoin/blob/v0.11.0/doc/release-notes.md#block-file-pruning). NODE_BLOOM service bit Support for the NODE_BLOOM service bit, as described in BIP 111 (https://github.com/bitcoin/bips/blob/master/bip-0111.mediawiki), has been added to the P2P protocol code. BIP 111 defines a service bit to allow peers to advertise that they support bloom filters (such as used by SPV clients) explicitly. It also bumps the protocol version to allow peers to identify old nodes which allow bloom filtering of the connection despite lacking the new service bit. In this version, it is only enforced for peers that send protocol versions >=70011. For the next major version it is planned that this restriction will be removed. It is recommended to update SPV clients to check for the NODE_BLOOM service bit for nodes that report versions newer than 70011. Option parsing behavior Command line options are now parsed strictly in the order in which they are specified. It used to be the case that -X -noX ends up, unintuitively, with X set, as -X had precedence over -noX. This is no longer the case. Like for other software, the last specified value for an option will hold. RPC: Low-level API changes
The following items contain assembly representations of scriptSig signatures and are affected by this change:
For example, the scriptSig.asm property of a transaction input that previously showed an assembly representation of: Code: 304502207fa7a6d1e0ee81132a269ad84e68d695483745cde8b541e3bf630749894e342a022100c1f7ab20e13e22fb95281a870f3dcf38d782e53023ee313d741ad0cfbc0c509001 400000 OP_NOP2 now shows as: Code: 304502207fa7a6d1e0ee81132a269ad84e68d695483745cde8b541e3bf630749894e342a022100c1f7ab20e13e22fb95281a870f3dcf38d782e53023ee313d741ad0cfbc0c5090[ALL] 400000 OP_CHECKLOCKTIMEVERIFY Note that the output of the RPC decodescript did not change because it is configured specifically to process scriptPubKey and not scriptSig scripts. RPC: SSL support dropped SSL support for RPC, previously enabled by the option rpcssl has been dropped from both the client and the server. This was done in preparation for removing the dependency on OpenSSL for the daemon completely. Trying to use rpcssl will result in an error: Code: Error: SSL mode for RPC (-rpcssl) is no longer supported. If you are one of the few people that relies on this feature, a flexible migration path is to use stunnel. This is an utility that can tunnel arbitrary TCP connections inside SSL. On e.g. Ubuntu it can be installed with: Code: sudo apt-get install stunnel4 Then, to tunnel a SSL connection on 28332 to a RPC server bound on localhost on port 18332 do: Code: stunnel -d 28332 -r 127.0.0.1:18332 -p stunnel.pem -P '' It can also be set up system-wide in inetd style. Another way to re-attain SSL would be to setup a httpd reverse proxy. This solution would allow the use of different authentication, loadbalancing, on-the-fly compression and caching. A sample config for apache2 could look like: Code: Listen 443 Mining Code Changes The mining code in 0.12 has been optimized to be significantly faster and use less memory. As part of these changes, consensus critical calculations are cached on a transaction's acceptance into the mempool and the mining code now relies on the consistency of the mempool to assemble blocks. However all blocks are still tested for validity after assembly. Other P2P Changes The list of banned peers is now stored on disk rather than in memory. Restarting bitcoind will no longer clear out the list of banned peers; instead a new RPC call (clearbanned) can be used to manually clear the list. The new setban RPC call can also be used to manually ban or unban a peer. 0.12.0 Change log Detailed release notes follow. This overview includes changes that affect behavior, not code moves, refactors and string updates. For convenience in locating the code changes and accompanying discussion, both the pull request and git merge commit are mentioned. RPC and REST
Configuration and command-line options
Block and transaction handling
P2P protocol and network code
Validation
Build system
Wallet
GUI
Tests and QA
Miscellaneous
Credits Thanks to everyone who directly contributed to this release:
As well as everyone that helped translating on Transifex (https://www.transifex.com/projects/p/bitcoin/). Title: Re: Bitcoin Core version 0.12.0 is now available Post by: -ck on February 23, 2016, 08:18:07 PM Funny, advertiZed isn't correct spelling for any variant of English.
Regardless, congrats on a fine release, especially for the changes that positively affect mining. Title: Re: Bitcoin Core version 0.12.0 is now available Post by: Stringer Bell on February 24, 2016, 11:56:51 AM Well done everyone :) Thank you devs!
Title: Re: Bitcoin Core version 0.12.0 is now available Post by: Amph on February 24, 2016, 01:46:11 PM i accidentally set per kb on the fee menu, how do you undo it? i want to customize it per satoshi and not per kb
Title: Re: Bitcoin Core version 0.12.0 is now available Post by: knight22 on February 24, 2016, 01:55:39 PM Sorry but RBF is a big no no. Opt in or not.
Title: Re: Bitcoin Core version 0.12.0 is now available Post by: ekoice on February 27, 2016, 06:41:28 AM Very informative, thanks 4 sharing ;) I really liked this new version, contains new salient features and has been improved in a nice way for the users and it encourages every bitcoin user to think that bitcoin is going to help them a lot with upgrading and improving its system so far.Title: Re: Bitcoin Core version 0.12.0 is now available Post by: Watercooler on February 27, 2016, 09:53:34 AM Thanks to all the developers for this new release, good job and keep up the good work for the future releases and new features
Title: Re: Bitcoin Core version 0.12.0 is now available Post by: chek2fire on February 27, 2016, 05:27:38 PM And the ppa package for ubuntu are ready :)
https://launchpad.net/~bitcoin/+archive/ubuntu/bitcoin Title: Re: Bitcoin Core version 0.12.0 is now available Post by: rally on February 27, 2016, 05:31:03 PM Do you have to upgrade or can you continue with the old version?
I have version v0.11.1 Title: Re: Bitcoin Core version 0.12.0 is now available Post by: achow101 on February 27, 2016, 05:53:08 PM Do you have to upgrade or can you continue with the old version? It is not required to upgrade but it is recommended that you do. There have been several bug fixes and new features added as well as optimization to improve the speed of stuff so you probably should upgrade.I have version v0.11.1 Title: Re: Bitcoin Core version 0.12.0 is now available Post by: rally on February 27, 2016, 06:08:25 PM Do you have to upgrade or can you continue with the old version? It is not required to upgrade but it is recommended that you do. There have been several bug fixes and new features added as well as optimization to improve the speed of stuff so you probably should upgrade.I have version v0.11.1 It is because it has taken several days a few weeks ago to download the whole blockchain and i am a bit scared to have problems again. If i do the upgrade, i can be certain that it won't cause problems? DOes the download go faster with the new version? Title: Re: Bitcoin Core version 0.12.0 is now available Post by: achow101 on February 27, 2016, 06:27:31 PM Do you have to upgrade or can you continue with the old version? It is not required to upgrade but it is recommended that you do. There have been several bug fixes and new features added as well as optimization to improve the speed of stuff so you probably should upgrade.I have version v0.11.1 It is because it has taken several days a few weeks ago to download the whole blockchain and i am a bit scared to have problems again. If i do the upgrade, i can be certain that it won't cause problems? DOes the download go faster with the new version? Title: Re: Bitcoin Core version 0.12.0 is now available Post by: rally on February 27, 2016, 06:30:17 PM Do you have to upgrade or can you continue with the old version? It is not required to upgrade but it is recommended that you do. There have been several bug fixes and new features added as well as optimization to improve the speed of stuff so you probably should upgrade.I have version v0.11.1 It is because it has taken several days a few weeks ago to download the whole blockchain and i am a bit scared to have problems again. If i do the upgrade, i can be certain that it won't cause problems? DOes the download go faster with the new version? OK. I am going to try it. I have just finished downloading the blockchain with my old wallet. I have to close it now, download the new one and it should be working ? Is that right? Title: Re: Bitcoin Core version 0.12.0 is now available Post by: achow101 on February 27, 2016, 06:31:51 PM Do you have to upgrade or can you continue with the old version? It is not required to upgrade but it is recommended that you do. There have been several bug fixes and new features added as well as optimization to improve the speed of stuff so you probably should upgrade.I have version v0.11.1 It is because it has taken several days a few weeks ago to download the whole blockchain and i am a bit scared to have problems again. If i do the upgrade, i can be certain that it won't cause problems? DOes the download go faster with the new version? OK. I am going to try it. I have just finished downloading the blockchain with my old wallet. I have to close it now, download the new one and it should be working ? Is that right? Title: Re: Bitcoin Core version 0.12.0 is now available Post by: cesmak on February 27, 2016, 06:32:07 PM Used for two days, during the night crashed and corrupted the database.... back to 0.11.2, months without any problem with the 11.2 release, the new version problems in 2 days. i will wait a 0.12.x to retry to use.....
Title: Re: Bitcoin Core version 0.12.0 is now available Post by: rally on February 27, 2016, 06:34:22 PM Used for two days, during the night crashed and corrupted the database.... back to 0.11.2, months without any problem with the 11.2 release, the new version problems in 2 days. i will wait a 0.12.x to retry to use..... Oops; I just did download the new version..... Title: Re: Bitcoin Core version 0.12.0 is now available Post by: achow101 on February 27, 2016, 06:36:02 PM Used for two days, during the night crashed and corrupted the database.... back to 0.11.2, months without any problem with the 11.2 release, the new version problems in 2 days. i will wait a 0.12.x to retry to use..... Did the program crash or the computer? The program shouldn't crash, or if it did, there is probably another underlying problem. I have been running 0.12 for weeks now and I have had no problems whatsoever.Title: Re: Bitcoin Core version 0.12.0 is now available Post by: cesmak on February 27, 2016, 06:38:13 PM Used for two days, during the night crashed and corrupted the database.... back to 0.11.2, months without any problem with the 11.2 release, the new version problems in 2 days. i will wait a 0.12.x to retry to use..... Did the program crash or the computer? The program shouldn't crash, or if it did, there is probably another underlying problem. I have been running 0.12 for weeks now and I have had no problems whatsoever.The program core stopped working (with a windows message that the program halted in a wrong way), the pc remained healty, but the db was corrupted. turn back to 11.2 and another 24 hours to reindex all the DB. 11.2 are months that work ok 24/7.... This is the log error (is in italian as i'm italian and use the italian version....) 2016-02-26 04:01:39 LevelDB read failure: IO error: d:\Programmi\Bitcoin\DataBase\chainstate\4932597.ldb: Impossibile trovare il file specificato. 2016-02-26 04:01:39 IO error: d:\Programmi\Bitcoin\DataBase\chainstate\4932597.ldb: Impossibile trovare il file specificato. 2016-02-26 04:21:37 socket sending timeout: 1201s 2016-02-26 04:21:39 socket sending timeout: 1201s 2016-02-26 04:21:40 socket sending timeout: 1201s 2016-02-26 06:37:00 Error reading from database: Database I/O error 2016-02-26 06:48:04 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..." Title: Re: Bitcoin Core version 0.12.0 is now available Post by: rally on February 27, 2016, 06:39:26 PM Used for two days, during the night crashed and corrupted the database.... back to 0.11.2, months without any problem with the 11.2 release, the new version problems in 2 days. i will wait a 0.12.x to retry to use..... Did the program crash or the computer? The program shouldn't crash, or if it did, there is probably another underlying problem. I have been running 0.12 for weeks now and I have had no problems whatsoever.I have just opened my wallet and works perfect. I hope it will stay so. Thanks for the help and i keep in touch. Thanks. Title: Re: Bitcoin Core version 0.12.0 is now available Post by: rally on February 28, 2016, 01:16:11 PM I have just tried my wallet again with the update i did yesterday.
Still working perfect. Title: Re: Bitcoin Core version 0.12.0 is now available Post by: cesmak on February 29, 2016, 07:34:27 AM Used for two days, during the night crashed and corrupted the database.... back to 0.11.2, months without any problem with the 11.2 release, the new version problems in 2 days. i will wait a 0.12.x to retry to use..... Did the program crash or the computer? The program shouldn't crash, or if it did, there is probably another underlying problem. I have been running 0.12 for weeks now and I have had no problems whatsoever.The program core stopped working (with a windows message that the program halted in a wrong way), the pc remained healty, but the db was corrupted. turn back to 11.2 and another 24 hours to reindex all the DB. 11.2 are months that work ok 24/7.... This is the log error (is in italian as i'm italian and use the italian version....) 2016-02-26 04:01:39 LevelDB read failure: IO error: d:\Programmi\Bitcoin\DataBase\chainstate\4932597.ldb: Impossibile trovare il file specificato. 2016-02-26 04:01:39 IO error: d:\Programmi\Bitcoin\DataBase\chainstate\4932597.ldb: Impossibile trovare il file specificato. 2016-02-26 04:21:37 socket sending timeout: 1201s 2016-02-26 04:21:39 socket sending timeout: 1201s 2016-02-26 04:21:40 socket sending timeout: 1201s 2016-02-26 06:37:00 Error reading from database: Database I/O error 2016-02-26 06:48:04 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..." Probably i found where is the problem, not a bitcoin core wallet fault, but my avira free antivirus, i found today, that in the night when the problem happened, the scanner marked and quarantined that file... i will re-upgrade my wallet to the latest version.... case closed. Cheers Title: Re: Bitcoin Core version 0.12.0 is now available Post by: rally on February 29, 2016, 06:22:06 PM Used for two days, during the night crashed and corrupted the database.... back to 0.11.2, months without any problem with the 11.2 release, the new version problems in 2 days. i will wait a 0.12.x to retry to use..... Did the program crash or the computer? The program shouldn't crash, or if it did, there is probably another underlying problem. I have been running 0.12 for weeks now and I have had no problems whatsoever.The program core stopped working (with a windows message that the program halted in a wrong way), the pc remained healty, but the db was corrupted. turn back to 11.2 and another 24 hours to reindex all the DB. 11.2 are months that work ok 24/7.... This is the log error (is in italian as i'm italian and use the italian version....) 2016-02-26 04:01:39 LevelDB read failure: IO error: d:\Programmi\Bitcoin\DataBase\chainstate\4932597.ldb: Impossibile trovare il file specificato. 2016-02-26 04:01:39 IO error: d:\Programmi\Bitcoin\DataBase\chainstate\4932597.ldb: Impossibile trovare il file specificato. 2016-02-26 04:21:37 socket sending timeout: 1201s 2016-02-26 04:21:39 socket sending timeout: 1201s 2016-02-26 04:21:40 socket sending timeout: 1201s 2016-02-26 06:37:00 Error reading from database: Database I/O error 2016-02-26 06:48:04 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..." Probably i found where is the problem, not a bitcoin core wallet fault, but my avira free antivirus, i found today, that in the night when the problem happened, the scanner marked and quarantined that file... i will re-upgrade my wallet to the latest version.... case closed. Cheers I am glad for you. I did just do the update when i saw your post with your problems and was a bit scared that i should have the same problem. Mine is working fine at this moment. Title: Re: Bitcoin Core version 0.12.0 is now available Post by: Lauda on March 01, 2016, 12:15:53 AM I did just do the update when i saw your post with your problems and was a bit scared that i should have the same problem. You don't need to be 'scared' of anything. You should be making regular backups of your wallet.dat file so that even in the case of a full-scale disaster you are prepared. It has been working for me without any issues from the day of release.but my avira free antivirus Good time to change your AV. It seems fine with Bitdefender. Sorry but RBF is a big no no. Opt in or not. It is fine; it has its uses. Nobody is forcing you to use it. Title: Re: Bitcoin Core version 0.12.0 is now available Post by: densuj on March 01, 2016, 04:04:25 PM I will try to upgrade thank you for the info
Title: Re: Bitcoin Core version 0.12.0 is now available Post by: CarrollFilms on March 02, 2016, 04:14:03 AM You lost me at "Memory Pool Limiting"
Title: Re: Bitcoin Core version 0.12.0 is now available Post by: crazyearner on March 02, 2016, 11:30:32 PM Would be nice if blockchain and content could be compressed up and not needed getting way too big and storing too much data on my system. Hate to see what the average size of core is going to be by next year or 2 to 3 years. Think the average joe is not going to download due to size. Still getting crashing when loading so guessing not fixed my problem in last 3 or 4 version updates when using on SSD.
Title: Re: Bitcoin Core version 0.12.0 is now available Post by: Lauda on March 02, 2016, 11:35:37 PM Would be nice if blockchain and content could be compressed up and not needed getting way too big and storing too much data on my system. Not really no. Somebody suggested compressing the data within the blocks but that doesn't work either (random data compression).Hate to see what the average size of core is going to be by next year or 2 to 3 years. Think the average joe is not going to download due to size. The data will be rising constantly. The average Joe does not need to have everything downloaded if they don't want to. They can use SPV clients (e.g. electrum).Still getting crashing when loading so guessing not fixed my problem in last 3 or 4 version updates when using on SSD. Have you reported it with more information to the developers? I've been using it on 2 SSDs and 1 external HDD and have not had problems in any versions so far.Title: Re: Bitcoin Core version 0.12.0 is now available Post by: Amph on March 03, 2016, 03:01:56 PM i've already asked this but none responded
how to remove the fee per kb? i want to set them per satoshi, but i can not undo anymore the "per kilobyte" mark Title: Re: Bitcoin Core version 0.12.0 is now available Post by: wazzap on March 04, 2016, 08:16:24 PM The new version is smooth and working perpectly :)
Title: Re: Bitcoin Core version 0.12.0 is now available Post by: rte369x on March 06, 2016, 07:55:27 AM Thanks for posting this information. It really helps me since I am new in this business. Great!
Title: Re: Bitcoin Core version 0.12.0 is now available Post by: Shawshank on March 06, 2016, 09:51:25 AM how tor emove the fee per kb? i want to set them per satoshi, but i can not undo anymore the "per kilobyte" mark It works for me when I do the following: Go to Settings/Options . Select the Wallet tab. Tick the check box: "Enable coin control features". It will appear a button with the label "Inputs...". Press on that button and select the inputs you want, or if you prefer, select all inputs. At that moment, the radio button "total at least" gets enabled and it is ready to use. Title: Re: Bitcoin Core version 0.12.0 is now available Post by: BTCisfuture on March 09, 2016, 12:23:27 AM I have just tried my wallet again with the update i did yesterday. same story/.Still working perfect. Title: Re: Bitcoin Core version 0.12.0 is now available Post by: Amph on March 09, 2016, 03:07:37 PM how tor emove the fee per kb? i want to set them per satoshi, but i can not undo anymore the "per kilobyte" mark It works for me when I do the following: Go to Settings/Options . Select the Wallet tab. Tick the check box: "Enable coin control features". It will appear a button with the label "Inputs...". Press on that button and select the inputs you want, or if you prefer, select all inputs. At that moment, the radio button "total at least" gets enabled and it is ready to use. i was referring to the custom menu where you set "per kb" or not" after you set per kb, you can not uncheck it anymore Title: Re: Bitcoin Core version 0.12.0 is now available Post by: Shawshank on March 09, 2016, 11:17:23 PM how tor emove the fee per kb? i want to set them per satoshi, but i can not undo anymore the "per kilobyte" mark It works for me when I do the following: Go to Settings/Options . Select the Wallet tab. Tick the check box: "Enable coin control features". It will appear a button with the label "Inputs...". Press on that button and select the inputs you want, or if you prefer, select all inputs. At that moment, the radio button "total at least" gets enabled and it is ready to use. i was referring to the custom menu where you set "per kb" or not" after you set per kb, you can not uncheck it anymore I have tried again and I can uncheck the "per kilobyte" radio button only if I select at least one input as I specified in my previous post. If I select at least one input, I can switch from the "per kilobyte" radio button to the "total at least" radio button and viceversa without problem. I agree that it is not working 100% OK because the UI lets you have the "total at least" radio button selected and active and the "Send as zero-fee transaction if possible" checkbox ticked and active simultaneously, which doesn't make sense, but that is a different issue. Title: Re: Bitcoin Core version 0.12.0 is now available Post by: Amph on March 11, 2016, 08:58:54 AM how tor emove the fee per kb? i want to set them per satoshi, but i can not undo anymore the "per kilobyte" mark It works for me when I do the following: Go to Settings/Options . Select the Wallet tab. Tick the check box: "Enable coin control features". It will appear a button with the label "Inputs...". Press on that button and select the inputs you want, or if you prefer, select all inputs. At that moment, the radio button "total at least" gets enabled and it is ready to use. i was referring to the custom menu where you set "per kb" or not" after you set per kb, you can not uncheck it anymore I have tried again and I can uncheck the "per kilobyte" radio button only if I select at least one input as I specified in my previous post. If I select at least one input, I can switch from the "per kilobyte" radio button to the "total at least" radio button and viceversa without problem. I agree that it is not working 100% OK because the UI lets you have the "total at least" radio button selected and active and the "Send as zero-fee transaction if possible" checkbox ticked and active simultaneously, which doesn't make sense, but that is a different issue. ah yes, it work now, i've tried again, why i need to do this trick to unlock the "total at least" option? all this mess for something that should be available by default it looks like a bug to me Title: Re: Bitcoin Core version 0.12.0 is now available Post by: sky0910 on March 13, 2016, 06:28:30 AM I have just tried my wallet again with the update i did yesterday. same story/.Still working perfect. i didn't find any change.. is it usual ? Title: Re: Bitcoin Core version 0.12.0 is now available Post by: SirArthurVlade on March 23, 2016, 06:15:18 PM Those are some good updates. Many of them were expectant from much of the community aswell.
Title: Re: Bitcoin Core version 0.12.0 is now available Post by: jtipt on March 24, 2016, 01:41:33 PM Hey guys, I was think about switching from blockchain.info to bitcoin core. Should I do that? I mean can some one give me advantages and disadvantages of using a downloaded wallet then a online one.
Title: Re: Bitcoin Core version 0.12.0 is now available Post by: achow101 on March 24, 2016, 01:55:17 PM Hey guys, I was think about switching from blockchain.info to bitcoin core. Should I do that? I mean can some one give me advantages and disadvantages of using a downloaded wallet then a online one. You should switch to use at least a desktop wallet. Desktop wallets put you in full control of your wallet and Bitcoin. It doesn't put you at the whim of the shitty service that blockchain.info provides. With Bitcoin Core, you will have to download the full blockchain, and if you don't have enough bandwidth to download 60+ Gb of blockchain, then you probably shouldn't use Bitcoin Core. It can be used in pruned mode so you don't need to store all of that data, but it still must be downloaded and processed so your computer will need a decent processor and at least 4 Gb of RAM. If you don't want to have the full blockchain, I recommend that you use Electrum.Title: Re: Bitcoin Core version 0.12.0 is now available Post by: jtipt on March 24, 2016, 03:58:30 PM ~ I don't really have a issue with bandwidth and since it's a torrent it would take hardly 3-4hrs to download it but the problem is I don't have 60 gb of storage lol, yeah got a lame ass pc. I will check out electrum, I also have heard about armory is that a good wallet? Title: Re: Bitcoin Core version 0.12.0 is now available Post by: achow101 on March 24, 2016, 04:09:09 PM ~ I don't really have a issue with bandwidth and since it's a torrent it would take hardly 3-4hrs to download it but the problem is I don't have 60 gb of storage lol, yeah got a lame ass pc. I will check out electrum, I also have heard about armory is that a good wallet? You don't need 60 Gb of storage. You can have the prune option enabled which can reduce the space used to around 2 Gb. Armory is a good wallet but it requires Bitcoin Core and Bitcoin Core must not be pruned. You would have to download all 60+ Gb of the blockchain in order to use Armory. Title: Re: Bitcoin Core version 0.12.0 is now available Post by: jtipt on March 24, 2016, 04:55:32 PM ~ I don't really have a issue with bandwidth and since it's a torrent it would take hardly 3-4hrs to download it but the problem is I don't have 60 gb of storage lol, yeah got a lame ass pc. I will check out electrum, I also have heard about armory is that a good wallet? You don't need 60 Gb of storage. You can have the prune option enabled which can reduce the space used to around 2 Gb. Armory is a good wallet but it requires Bitcoin Core and Bitcoin Core must not be pruned. You would have to download all 60+ Gb of the blockchain in order to use Armory. Title: Re: Bitcoin Core version 0.12.0 is now available Post by: shorena on March 25, 2016, 01:44:54 PM ~ I don't really have a issue with bandwidth and since it's a torrent it would take hardly 3-4hrs to download it but the problem is I don't have 60 gb of storage lol, yeah got a lame ass pc. I will check out electrum, I also have heard about armory is that a good wallet? You don't need 60 Gb of storage. You can have the prune option enabled which can reduce the space used to around 2 Gb. Armory is a good wallet but it requires Bitcoin Core and Bitcoin Core must not be pruned. You would have to download all 60+ Gb of the blockchain in order to use Armory. Both have their advantages and their problems. Core needs constant backups, electrum only a single one (the seed, write. it. down!). Core makes you part of the network, electurm needs others to run servers. Core wallets files are hardened against brute force attacks, electrum wallet files not (or only barely). If you are happy with electrum, stick with it. Title: Re: Bitcoin Core version 0.12.0 is now available Post by: BTCxPRO on March 28, 2016, 06:29:47 PM I have just opened my wallet and works perfect. I hope it will stay so. Thanks. Title: Re: Bitcoin Core version 0.12.0 is now available Post by: 0day on March 31, 2016, 07:54:43 PM A lot has changed since my last login!! 3 years ago.
Glad to be BTCack Title: Re: Bitcoin Core version 0.12.0 is now available Post by: reddog6714 on April 03, 2016, 12:37:12 AM if it is so good why has it taken me all day Saturday and half the night to download what is essentially still not working
i am running the fastest NBN and have a huge download capacity running a quadcore computer with windows 7 and i am still waiting for it to synch WTF Title: Re: Bitcoin Core version 0.12.0 is now available Post by: Hi7 on April 03, 2016, 10:57:24 AM Didn't have the upgrade yet, upgrading now. Thank you :)
Title: Re: Bitcoin Core version 0.12.0 is now available Post by: cloh76 on April 04, 2016, 01:07:21 AM Taking forever to Sync
Title: Re: Bitcoin Core version 0.12.0 is now available Post by: Lauda on April 05, 2016, 10:18:33 PM Taking forever to Sync Should be much faster than any previous version. I'll assume either: 1) Default settings with average hardware; 2) Old hardware; 3) Other problems. Which is it?if it is so good why has it taken me all day Saturday and half the night to download what is essentially still not working That's a problem on your end. It took my full node 17 hours to download and sync from scratch with default settings. I've recently done this test. We can't really help you without any information.i am running the fastest NBN and have a huge download capacity running a quadcore computer with windows 7 and i am still waiting for it to synch WTF Both have their advantages and their problems. Core needs constant backups, electrum only a single one (the seed, write. it. down!). I concur. Many do not realize this and end up losing their coins. Title: Re: Bitcoin Core version 0.12.0 is now available Post by: AzibLala007 on April 06, 2016, 10:06:44 AM i don't think there is need to shift on new version.
the old one is working perfectly. Title: Re: Bitcoin Core version 0.12.0 is now available Post by: shorena on April 06, 2016, 11:54:48 AM i don't think there is need to shift on new version. the old one is working perfectly. Some see it as a vote for bitcoins future. Do you prefer 2 MB blocks ASAP and support classic or do you prefer WegWit first and support bitcoin core. Other than that I have to say 0.12 is significantly faster in terms of sync times (be that full sync or catching up longer periods). Title: Re: Bitcoin Core version 0.12.0 is now available Post by: sauc1er on April 06, 2016, 02:42:03 PM A lot has changed since my last login!! 3 years ago. Glad to be BTCack WORD! Title: Re: Bitcoin Core version 0.12.0 is now available Post by: fepayday on April 14, 2016, 10:43:39 AM what it this bitcoin core guys?
Title: Re: Bitcoin Core version 0.12.0 is now available Post by: Lauda on April 14, 2016, 11:27:08 AM what it this bitcoin core guys? It is the main Bitcoin implementation right now. It is just one client out of many (e.g. Electrum, Armory). |