Bitcoin Forum

Bitcoin Core version *0.15.1* is now available from:

  https://bitcoincore.org/bin/bitcoin-core-0.15.1

or

  https://bitcoin.org/bin/bitcoin-core-0.15.1

This is a new minor version release, including various bugfixes and
performance improvements, as well as updated translations.

Please report bugs using the issue tracker at GitHub:

  https://github.com/bitcoin/bitcoin/issues

To receive security and update notifications, please subscribe to:

  https://bitcoincore.org/en/list/announcements/join/

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).

The first time you run version 0.15.0 or higher, your chainstate database will
be converted to a new format, which will take anywhere from a few minutes to
half an hour, depending on the speed of your machine.

The file format of `fee_estimates.dat` changed in version 0.15.0. Hence, a
downgrade from version 0.15 or upgrade to version 0.15 will cause all fee
estimates to be discarded.

Note that the block database format also changed in version 0.8.0 and there is no
automatic upgrade code from before version 0.8 to version 0.15.0. Upgrading
directly from 0.7.x and earlier without redownloading the blockchain is not supported.
However, as usual, old wallet versions are still supported.

Downgrading warning
-------------------

The chainstate database for this release is not compatible with previous
releases, so if you run 0.15 and then decide to switch back to any
older version, you will need to run the old release with the `-reindex-chainstate`
option to rebuild the chainstate data structures in the old format.

If your node has pruning enabled, this will entail re-downloading and
processing the entire blockchain.

Compatibility
==============

Bitcoin Core is extensively tested on multiple operating systems using
the Linux kernel, macOS 10.8+, and Windows Vista and later. Windows XP is not supported.

Bitcoin Core should also work on most other Unix-like systems but is not
frequently tested on them.


Notable changes
===============

Network fork safety enhancements
--------------------------------

A number of changes to the way Bitcoin Core deals with peer connections and invalid blocks
have been made, as a safety precaution against blockchain forks and misbehaving peers.

- Unrequested blocks with less work than the minimum-chain-work are now no longer processed even
if they have more work than the tip (a potential issue during IBD where the tip may have low-work).
This prevents peers wasting the resources of a node.

- Peers which provide a chain with less work than the minimum-chain-work during IBD will now be disconnected.

- For a given outbound peer, we now check whether their best known block has at least as much work as our tip. If it
doesn't, and if we still haven't heard about a block with sufficient work after a 20 minute timeout, then we send
a single getheaders message, and wait 2 more minutes. If after two minutes their best known block has insufficient
work, we disconnect that peer. We protect 4 of our outbound peers from being disconnected by this logic to prevent
excessive network topology changes as a result of this algorithm, while still ensuring that we have a reasonable
number of nodes not known to be on bogus chains.

- Outbound (non-manual) peers that serve us block headers that are already known to be invalid (other than compact
block announcements, because BIP 152 explicitly permits nodes to relay compact blocks before fully validating them)
will now be disconnected.

- If the chain tip has not been advanced for over 30 minutes, we now assume the tip may be stale and will try to connect
to an additional outbound peer. A periodic check ensures that if this extra peer connection is in use, we will disconnect
the peer that least recently announced a new block.

- The set of all known invalid-themselves blocks (i.e. blocks which we attempted to connect but which were found to be
invalid) are now tracked and used to check if new headers build on an invalid chain. This ensures that everything that
descends from an invalid block is marked as such.


Miner block size limiting deprecated
------------------------------------

Though blockmaxweight has been preferred for limiting the size of blocks returned by
getblocktemplate since 0.13.0, blockmaxsize remained as an option for those who wished
to limit their block size directly. Using this option resulted in a few UI issues as
well as non-optimal fee selection and ever-so-slightly worse performance, and has thus
now been deprecated. Further, the blockmaxsize option is now used only to calculate an
implied blockmaxweight, instead of limiting block size directly. Any miners who wish
to limit their blocks by size, instead of by weight, will have to do so manually by
removing transactions from their block template directly.


GUI settings backed up on reset
-------------------------------

The GUI settings will now be written to `guisettings.ini.bak` in the data directory before wiping them when
the `-resetguisettings` argument is used. This can be used to retroactively troubleshoot issues due to the
GUI settings.


Duplicate wallets disallowed
----------------------------

Previously, it was possible to open the same wallet twice by manually copying the wallet file, causing
issues when both were opened simultaneously. It is no longer possible to open copies of the same wallet.


Debug `-minimumchainwork` argument added
----------------------------------------

A hidden debug argument `-minimumchainwork` has been added to allow a custom minimum work value to be used
when validating a chain.


Low-level RPC changes
----------------------

- The "currentblocksize" value in getmininginfo has been removed.

- `dumpwallet` no longer allows overwriting files. This is a security measure
  as well as prevents dangerous user mistakes.

- `backupwallet` will now fail when attempting to backup to source file, rather than
  destroying the wallet.

- `listsinceblock` will now throw an error if an unknown `blockhash` argument
  value is passed, instead of returning a list of all wallet transactions since
  the genesis block. The behaviour is unchanged when an empty string is provided.

0.15.1 Change log
=================

### Mining
- #11100 `7871a7d` Fix confusing blockmax{size,weight} options, dont default to throwing away money (TheBlueMatt)

### RPC and other APIs
- #10859 `2a5d099` gettxout: Slightly improve doc and tests (jtimon)
- #11267 `b1a6c94` update cli for estimate\*fee argument rename (laanwj)
- #11483 `20cdc2b` Fix importmulti bug when importing an already imported key (pedrobranco)
- #9937 `a43be5b` Prevent `dumpwallet` from overwriting files (laanwj)
- #11465 `405e069` Update named args documentation for importprivkey (dusty-wil)
- #11131 `b278a43` Write authcookie atomically (laanwj)
- #11565 `7d4546f` Make listsinceblock refuse unknown block hash (ryanofsky)
- #11593 `8195cb0` Work-around an upstream libevent bug (theuni)

### P2P protocol and network code
- #11397 `27e861a` Improve and document SOCKS code (laanwj)
- #11252 `0fe2a9a` When clearing addrman clear mapInfo and mapAddr (instagibbs)
- #11527 `a2bd86a` Remove my testnet DNS seed (schildbach)
- #10756 `0a5477c` net processing: swap out signals for an interface class (theuni)
- #11531 `55b7abf` Check that new headers are not a descendant of an invalid block (more effeciently) (TheBlueMatt)
- #11560 `49bf090` Connect to a new outbound peer if our tip is stale (sdaftuar)
- #11568 `fc966bb` Disconnect outbound peers on invalid chains (sdaftuar)
- #11578 `ec8dedf` Add missing lock in ProcessHeadersMessage(...) (practicalswift)
- #11456 `6f27965` Replace relevant services logic with a function suite (TheBlueMatt)
- #11490 `bf191a7` Disconnect from outbound peers with bad headers chains (sdaftuar)

### Validation
- #10357 `da4908c` Allow setting nMinimumChainWork on command line (sdaftuar)
- #11458 `2df65ee` Don't process unrequested, low-work blocks (sdaftuar)

### Build system
- #11440 `b6c0209` Fix validationinterface build on super old boost/clang (TheBlueMatt)
- #11530 `265bb21` Add share/rpcuser to dist. source code archive (MarcoFalke)

### GUI
- #11334 `19d63e8` Remove custom fee radio group and remove nCustomFeeRadio setting (achow101)
- #11198 `7310f1f` Fix display of package name on 'open config file' tooltip (esotericnonsense)
- #11015 `6642558` Add delay before filtering transactions (lclc)
- #11338 `6a62c74` Backup former GUI settings on `-resetguisettings` (laanwj)
- #11335 `8d13b42` Replace save|restoreWindowGeometry with Qt functions (MeshCollider)
- #11237 `2e31b1d` Fixing division by zero in time remaining (MeshCollider)
- #11247 `47c02a8` Use IsMine to validate custom change address (MarcoFalke)

### Wallet
- #11017 `9e8aae3` Close DB on error (kallewoof)
- #11225 `6b4d9f2` Update stored witness in AddToWallet (sdaftuar)
- #11126 `2cb720a` Acquire cs_main lock before cs_wallet during wallet initialization (ryanofsky)
- #11476 `9c8006d` Avoid opening copied wallet databases simultaneously (ryanofsky)
- #11492 `de7053f` Fix leak in CDB constructor (promag)
- #11376 `fd79ed6` Ensure backupwallet fails when attempting to backup to source file (tomasvdw)
- #11326 `d570aa4` Fix crash on shutdown with invalid wallet (MeshCollider)

### Tests and QA
- #11399 `a825d4a` Fix bip68-sequence rpc test (jl2012)
- #11150 `847c75e` Add getmininginfo test (mess110)
- #11407 `806c78f` add functional test for mempoolreplacement command line arg (instagibbs)
- #11433 `e169349` Restore bitcoin-util-test py2 compatibility (MarcoFalke)
- #11308 `2e1ac70` zapwallettxes: Wait up to 3s for mempool reload (MarcoFalke)
- #10798 `716066d` test bitcoin-cli (jnewbery)
- #11443 `019c492` Allow "make cov" out-of-tree; Fix rpc mapping check (MarcoFalke)
- #11445 `51bad91` 0.15.1 Backports (MarcoFalke)
- #11319 `2f0b30a` Fix error introduced into p2p-segwit.py, and prevent future similar errors (sdaftuar)
- #10552 `e4605d9` Tests for zmqpubrawtx and zmqpubrawblock (achow101)
- #11067 `eeb24a3` TestNode: Add wait_until_stopped helper method (MarcoFalke)
- #11068 `5398f20` Move wait_until to util (MarcoFalke)
- #11125 `812c870` Add bitcoin-cli -stdin and -stdinrpcpass functional tests (promag)
- #11077 `1d80d1e` fix timeout issues from TestNode (jnewbery)
- #11078 `f1ced0d` Make p2p-leaktests.py more robust (jnewbery)
- #11210 `f3f7891` Stop test_bitcoin-qt touching ~/.bitcoin (MeshCollider)
- #11234 `f0b6795` Remove redundant testutil.cpp|h files (MeshCollider)
- #11215 `cef0319` fixups from set_test_params() (jnewbery)
- #11345 `f9cf7b5` Check connectivity before sending in assumevalid.py (jnewbery)
- #11091 `c276c1e` Increase initial RPC timeout to 60 seconds (laanwj)
- #10711 `fc2aa09` Introduce TestNode (jnewbery)
- #11230 `d8dd8e7` Fixup dbcrash interaction with add_nodes() (jnewbery)
- #11241 `4424176` Improve signmessages functional test (mess110)
- #11116 `2c4ff35` Unit tests for script/standard and IsMine functions (jimpo)
- #11422 `a36f332` Verify DBWrapper iterators are taking snapshots (TheBlueMatt)
- #11121 `bb5e7cb` TestNode tidyups (jnewbery)
- #11521 `ca0f3f7` travis: move back to the minimal image (theuni)
- #11538 `adbc9d1` Fix race condition failures in replace-by-fee.py, sendheaders.py (sdaftuar)
- #11472 `4108879` Make tmpdir option an absolute path, misc cleanup (MarcoFalke)
- #10853 `5b728c8` Fix RPC failure testing (again) (jnewbery)
- #11310 `b6468d3` Test listwallets RPC (mess110)

### Miscellaneous
- #11377 `75997c3` Disallow uncompressed pubkeys in bitcoin-tx [multisig] output adds (TheBlueMatt)
- #11437 `dea3b87` [Docs] Update Windows build instructions for using WSL and Ubuntu 17.04 (fanquake)
- #11318 `8b61aee` Put back inadvertently removed copyright notices (gmaxwell)
- #11442 `cf18f42` [Docs] Update OpenBSD Build Instructions for OpenBSD 6.2 (fanquake)
- #10957 `50bd3f6` Avoid returning a BIP9Stats object with uninitialized values (practicalswift)
- #11539 `01223a0` [verify-commits] Allow revoked keys to expire (TheBlueMatt)


Credits
=======

Thanks to everyone who directly contributed to this release:

- Andreas Schildbach
- Andrew Chow
- Chris Moore
- Cory Fields
- Cristian Mircea Messel
- Daniel Edgecumbe
- Donal OConnor
- Dusty Williams
- fanquake
- Gregory Sanders
- Jim Posen
- John Newbery
- Johnson Lau
- João Barbosa
- Jorge Timón
- Karl-Johan Alm
- Lucas Betschart
- MarcoFalke
- Matt Corallo
- Paul Berg
- Pedro Branco
- Pieter Wuille
- practicalswift
- Russell Yanofsky
- Samuel Dobson
- Suhas Daftuar
- Tomas van der Wansem
- Wladimir J. van der Laan

As well as everyone that helped translating on Transifex (https://www.transifex.com/projects/p/bitcoin/).

Thanks for another stunning release. Such a shame from the S2X fraction to force you for that build. The good thing is it makes the software more secure against future attacks, on the other hand SegWit support has been postponed for the next release.

I'm not so comfortable with how the github process exactly works. But for me the 15.2 milestone seems to be almost done, only one pr is open right now. So can we expect 15.2 very soon also or will other pull requests be added to 15.2 first?
Thanks :)

Other things will probably be added to the 0.15.2 milestone closer to when it is released. Generally releases of bitcoin are based on time rather than features :)

thanks for the update info new release with bug fixed this is what i expected

Hoping transactions will be more faster

Thank you very much :)

P.S. I really like your work in the bitcoin github :)

Thank you for the updated news. I see several bugs is fixed. Means faster and secure transactions ever. Hope upcoming releases will bring us more security features..
Congratulations..

Really hope transactions will be more faster

Kudos to the contributors! Expecting improvement in the following weeks.

Very fast and smooth sync on x86_64 linux. Looks really good. What might be the time frame on 0.15.2 and might that fully support running lnd on top of that build?

I agree! Love the new update.

not mandatory from 15.0 right?

No, the upgrade brings a number of improvements but there is nothing stopping you from continuing to use 15.0 instead :)

Absoulately very good project .
Hope quietly transactions will be more faster and also will bring us more security features.
Really I agree!!

Wow a very astonishing new release. With this new model I can mine more efficiently with a greater profit.

how long take to synch all the blockchain? (connection 20Mo/bits

What I found irritating is that the latest version 0.15.1 was already available for download on bitcoin.org, but on bitcoincore.org the latest version was still 0.15.0.1 for a couple of days.

So, I downloaded the latest version from bitcoin.org, installed it and then discovered the discrepancy and rolled back to the old version and three days later (when it was listed on bitcoincore.org) upgraded to 0.15.1 again  :D

will this security more tight than old. since my money not wanna steal~

How is it working for people, anybody notice a marked improvement before I try it for myself?

don't spam guys. when i think old one good. but this one better. and remove estimate thing. nice team  ;D

geez i become double post


remove up. and stable block chain download nice guys[added]

Thanks for another stunning release. Such a shame from the S2X fraction to force you for that build. The good thing is it makes the software more secure against future attacks, on the other hand SegWit support has been postponed for the next release.

I'm not so comfortable with how the github process exactly works. But for me the 15.2 milestone seems to be almost done, only one pr is open right now. So can we expect 15.2 very soon also or will other pull requests be added to 15.2 first?
Thanks Smiley

token/ico will died soon. they give free and leave it. that why bitcoin core team reject work with them. and Etherium one of fist did it. Mining and better with stake.

For wallet not found bug running already half day. thank for release team~

I am hoping this update will have positive effect on transaction fees. Is this the case here?

Transaction fees already they implement. On segwit.

guys don't spam please...lol Dev need our test this out. if there bug or not

2 days test fine. prune is good too as for full nodes on my server...later update next day on server. since today holiday~

hello,I used it for the first time slowly working full day, almost 5% as if it does not respond to the server and does not show any numbers of currencies is this normal or not must be a long time, I mean, a few days ago? Please explain to me more..

Bitcoin Core 0.15.1
Compared to the previous version
I noticed this version has more flexibility
They are more stable and safer
Easy to use interface

Can anyone tell me how much time it will take to download all blocks for a new purse (100mbps) and what size will be of the wallet? The last number I remember was around 120Gb

we all have to be patient. if you let the work do it, it will be all right. all confidence in it ;)

It's 152GB at the moment. It's not easy to estimate how long it will take as it depends on the speed the peers you connect to upload it as well as your download speed. I'd take a wild guess that it would be at least a week. If you can find a copy to download from torrent then it would be a lot quicker.

Thanks a lot. And if I have blocks till the size of 125 Gb can I use them and download the remaining data? I have being using BTC Core several years ago and have more than 100Gb in my previous purse.

You certainly can. Depending on what version you are upgrading from IIRC there is some automatic conversion process that it will do so you'll have to wait for it do that first. Then it will just pick up from where it left off and synchronise the rest.

I see several bugs is fixed. Hope upcoming releases will really bring us such more security features and transactions will be more faster !)

I have update my system with the latest version Bitcoin Core 0.15.1 and many issues are now resolved. Thankyou

Is it a fast conversion from 14.01 to 15.01 if I have an up to date block list?

If your blockchain is up to date then it's just a quick install.

Nice, just 152 gigabytes per second is a very high conductivity but will it be more security? I hope it will. As for me, I think this news could be more than just a release. Thank you devs for your work, let's see where this leads to.

I mentioned this above: https://bitcointalk.org/index.php?topic=2388679.msg24554227#msg24554227
Other PRs will be added to the 15.2 milestone over time, as it becomes clearer which features will make it into that release and which won't.

What error did you get? Perhaps we can help if you give some more information

Yep, changes to bitcoincore.org undergo review too, not just changes to bitcoin core code. You can see the PR here: https://github.com/bitcoin-core/bitcoincore.org/pull/464
Can sometimes take a few days before the announcement is posted unfortunately :)

Bitcoin Core is programmed to decide which block chain contains valid transactions and Bitcoin Core is the reference client of bitcoin. The latest stable version of Bitcoin Core is now available.Bitcoin Core 0.15.0.1 has been released with a fix for a minor bug causing crashes when upgrading . A link is https://bitcoincore.org/bin/bitcoin-core-0.15.1/[/font] ........... :D

how to get your private key in bitcoin core, what does it need, and do I have to wait until the whole blockcjain is downloaded?

yes, I also think we need to be patient and yet we need faith and everything will turn out

To survive today funding is mandatory.
The same holds true for tomorrow and days ahead.
Hence, the necessity is to create a recurring source of funds that would secure the minimum material necessities of our daily lives.
This needs a process. A tested and secure one.
Once this is established, we can move into expansion or diversification without disturbing the already established process.
Hence, we slowly need to move into a recurring process of magnification of fund inflow.

And, Bitcointalk is the safest and a secure way to start.

That is my goal.

I am noticing that this update has remedied some very large issues, but the transition is sort of tricky- thank you achow for your recommends and tips.

Please post your queries while working on the above, will help resolve.

May I ask what is "during IBD will now be disconnected"

I also tried downloading to a computer, but when the download was running 50%, it was reported error, and Bitcoin Core Qt.exe stopped abruptly ...

I do not understand what it is

Of course, with the new version, the security and transaction speed is increased. But we can not say anything about the transaction charges. They still might be applicable on every transaction you make. But we hope that these transactions charges remain at low and wothout any taxation.

wow you have a successfull project of bitcoin core good job everyone God bless

So about the latest release of bitcoin core, the version 0.15.1 has better features, updated GUI, and it is more efficient and more reliable on transactions. I can say that bitcoin has evolved and I loved it.

You don't have to wait for the blockchain to download, you could export them using:


Ignore the first line If you're wallet is not encrypted.

IBD stands for Initial Block Download, it is the process through which a Bitcoin full node downloads and validates the whole blockchain from the genesis block up to current time the first time it is run (to get up to sync).

Anyone interested in the seeing the data on how many nodes are upgrading in real-time, please PM me, I'm testing a new unique service and I'm interested in user opinion.

its good to have a safer code behind the platform.

Where is the better place to save private key?

what is the checksum to verify?

my result with the qt inside is edf150cf1fd013e2b2a26f126c7ae058f3d0f5dd1614b967e2340ce6bf67e784

d64d2e27cad78bbd2a0268bdaa9efa3f1eca670a4fab462b5e851699c780e3a0  bitcoin-0.15.1-aarch64-linux-gnu.tar.gz
ceba092c9a390082ff184c8d82a24bc34d7f9b421dc5c1e6847fcf769541f305  bitcoin-0.15.1-arm-linux-gnueabihf.tar.gz
231e4c9f5cf4ba977dbaf118bf38b0fde4d50ab7b9efd65bee6647fb14035a2c  bitcoin-0.15.1-i686-pc-linux-gnu.tar.gz
b6771c5d67fb6b9c4882cc351e579470a008211d76407155e544b28b00fcd711  bitcoin-0.15.1-osx64.tar.gz
0ce5ca1ba424603526d8a40d9321f1f735797a7205a7fbbe39561c078f2a0858  bitcoin-0.15.1-osx.dmg
34de2dbe058c1f8b6464494468ebe2ff0422614203d292da1c6458d6f87342b4  bitcoin-0.15.1.tar.gz
cc7a31d8fece1462955bddef87945420721e42cfe6af589a36547b0940851765  bitcoin-0.15.1-win32-setup.exe
4d2ad1371df1904367955d3f250212d0edd9f338c26d5cd60d7d8ce3f1733f5a  bitcoin-0.15.1-win32.zip
905a5999fb52b083d7e3bedb2dc6704ca641823f81865db58a55a6a20b454d8c  bitcoin-0.15.1-win64-setup.exe
b858521496c0d7699a6916c20767cdb123eb39be70ffc544d6876b08af3b696a  bitcoin-0.15.1-win64.zip
387c2e12c67250892b0814f26a5a38f837ca8ab68c86af517f975a2a2710225b  bitcoin-0.15.1-x86_64-linux-gnu.tar.gz

Bitcoin i really fine curenncy people invest in with positive mind and get too much ..

No it's unrelated, the price going up is speculation, ignore it unless you have bitcoins now and htink the price is near it's highest already then cash out at least most of them. You can always get back in later after the price finishes dropping. Now if you think the price is going to go up more you can always hold on and hope it does.

How are people finding the migration from 14 to 15 does it take long to complete?

is this the final version?

It's the latest stable version there is no final one. Developers will continue to find ways to improve bitcoin/fix bugs.

Shutting down the software first before upgrading to the new update is very important. It helps the process to be smooth and free from errors

Guys, should I add wallet.dat before downloading the whole blockchain or after? Does it matter actually?

wooo so what are the issues people are having with the wallet so far?

Bitcoin core should read the wallet file on startup, anything else doesn't matter. You won't be able to send anything before the blockchain is downloaded though.

So this is the new and updated version right? What happened to the old version? Does it have a much better and useful features than the old one? I just wanted to before I upgrade on this latest version.

Ok thanks. One more question: how can I get BCH and BTG from BCC? I have read some instructions but they are too complicated for me at the time.

And by BCC you mean Bitcoin Core? You can simply export the private keys by following this: https://bitcoin.stackexchange.com/questions/4203/how-can-i-export-the-private-key-for-an-address-from-the-satoshi-client (second post) and then import them into Coinomi (It support both BTG and BCH).

Thanks for this amazing release. It's just too bad that SegWit support was postponsed on its next release, but I hope it can get fixed.

It's likely that 0.16 will be released very soon, maybe even within a week or two :)

I am thinking about downloading and installing the upgrade but the thought of waiting for the whole chaing to re-sync fills me with dread. Surely one of you must have already tried this if I am up to date with blocks, will the change take 1 hour, 1 day, 1 week?

If you up to date with blocks then there is no need to resynch so the whole upgrade process should take less than half an hour.



That's great news, what is the source of this information?

than you very much for update infomation. I would like to know more about bugs or issues which is still remaining.Where can I find it? ???

i have a question, how far a replay attack can go back in time? i mean if i have a TX with 10k confirmations can still be attacked with a replay attack?

Thanks for the update, i think transactions will be more easier.

Of course! There's a mac build and Bitcoin Core is routinely tested on Macs (some of the developers use Macs).

enlish:
Transaction costs are too high now! Trading time is too long, can improve this shortcoming? This is fatal for everyday small transaction payments!
 
中文：

现在的交易费用太高了！交易时间也太长了，能不能改进，对日常的小的交易支付来说，这是致命的！

no one know?

Probably because you are asking in the wrong thread. AKAIK replay attacks are not limited by time, but if you start a thread asking then someone more knowledgeable than I might answer.

The transaction time is the turn off for me. It's extremely high.

does anyone have a proper link for running bitcoin core on raspberry pi?

I've seen on reddit gmaxwell (nullc) and I think Luke JR also pointed to a release of 0.16 rather soon. As far as I know, this version will be the one that has native segwit support for bech32 addresses (finally). Hopefully this will make Coinbase support segwit and we can see cheaper transactions because it's getting out of hand with the fees sometimes.

Thanks for that, I'm trying to resist joining Reddit as there are not enough hours in the day for me as it is. It's not just Coinbase but the nearly all major services are using Core so that must account for a very large proportion of transactions. When they are all finally able to start using Segwit then that should increase capacity. Hopefully giving slightly reduced Tx fees until Lightning Network is available which is the major scaling event we desperately need.

You don't need to join reddit, I've never had an account, you just can lurk it, or bookmark whoever is worth listening to, I got a couple of posters I like that I follow.

On Coinbase; i like to think that they are just being conservative, and they are not deliberately delaying segwit adoption to push whatever hardfork agenda they must be planning next. I've learned to never trust Coinbase.

I am noticing that this update has remedied some very large issues

The source of the information is me telling you ;) The segwit wallet PR is becoming almost ready to merge and then there will be a couple of other things to do before it is released, but it shouldn't be too much longer to wait

A replay attack only happens if there are two chains, and you want to create a transaction on one chain but not the other. Generally this is only possible after a new forkcoin is released, and so an old transaction with 10k confirmations is likely to already be in both blockchains (because it was part of the chain before the split) and thus a replay attack doesn't make sense on it.

Well, thanks. What I was really meaning to ask is what is the best way to follow the progress myself?

BTW. I had no idea from your nickname at first who you were.  :-[ Thanks, Samuel.

Thank you for the informative answer TheQuin, the thought of waiting for a whole chain resync was filling me with dread. Might put it off now though as seeing that 16 is about to drop  :)

It feels like it's been forever since the last IRC meeting summary, too (here's the last one, from the beginning of November): https://bitcoincore.org/en/meetings/2017/11/02/

I guess they decided to go a different route than the following with the numbering?
https://github.com/bitcoin/bitcoin/issues/11449

let's say the bitcoin core is now upgraded to bitcoin XT
what would be the changes that would happen in bitcoin? price? fee? wallet? diff?

Bitcoin XT died long time ago and It's not coming back. Bitcoin price is no longer affected by hard forks negatively (BTG, BCH, SBTC, BTCX etc.) because people consider them as free money so It they would dump them for BTC which result in an increase.

need help. i m searching for the orginal BTC wallet. but whenever i download it, it starts downloading bitcoin core. now i believe bitcoin core is a different currency ? m i right ? is BTC same as BTX ?

Best way is probably to sit on on the weekly developer meetings on IRC, https://bitcoincore.org/en/meetings/
Upcoming things like releases are generally discussed there :)

The S2X stuff forced us to push out a different 0.15.1 with a lot more fork protection additions to keep users safe. Because of that it was decided that 0.16 should be the release with the segwit wallet support, so it's being brought forward by quite a lot yes :)

is bitcoin core better than blockchain and the others?

With the last version I had to downgrade in order to use it. Hope this one works for me

If it doesn't please let us know on GitHub! We can't fix bugs we don't know about :)

Yes, BCC is Bitcoin Core wallet. I am just wondering if it is safe to follow that instruction. What if I transfer my BTC to another wallet before getting BCH and BTG? Will I still be able to gain those two?

Yes, the BCH and BTG will remain in your addresses regardless If you move your bitcoins or not and doing that will be safer as even If we assume that Coinomi is not a trustworthy wallet (e.g they save your private keys in their servers), they won't be able to get your bitcoins because you will be moving them.

The new version of bitcoin core is really very fast and amazing.Is it going to get its new update soon?

Great, thanx, that's what I needed to know.


Man, Bitcoin Core (BCC) is not a currency it is an original wallet for BitCoin (BTC). There many new abbreviations so you can easily get confused. Anyway, I think BCC is the original wallet because when I had used it most of those present today did not even exist. BTX is a BITCORE, (not BITCOIN CORE) and it is really a separate crypto not connected to original bitcoin. Hope that'll help you a bit

Hello, is my first message and i dont know if is ok tihis message: i've a big problem: i lost my passprhase Wallet Bitcoin Core and i need help: is possible recover or change passprhase ? thank you. Paolo Rivetta

I guess that's the wrong post to open up that question. And no it's not possible. But maybe you find some ideas in this topic here:
https://bitcointalk.org/index.php?topic=85495.0

I have been waiting to see this release. Now I am here to enjoy whats gonna happen now.. Hope it will perform better now ;D

Hi,

Thanks for the new release. The better side of this is that it makes the software more secure against attacks and easy to use when we compare to previous version. This new update will fixed most of the bugs which we can expected from it. Again thanks for it.
Congrats........

If you lost your password, there is no way to access your wallet, your funds are lost. If you know at least a little bit about the password and not a lot of special characters were used then you can contact WalletRecoveryServices.com but make sure to read the message shown in the top first and see If it applies to you.

https://blockchain.info/tx/618f35f4fb933a802853f5140163f13b4d0cc7696d5972b517aef06c4101c0ff


seriously?

from 3 days to 2 weeks now infinity?

no wonder the mempool is backed up..

is this when the bitcoin cash crap started? was the 0.15.1 release the catalyst?

I have a problem with Bitcoin cash Bitcash (BCC) corrupting the Bitcoin (BTC) database.  I have to reindex both and still they get stuck at the fork of BCC off of BTC chain on August 1, 2017.

Anyone else been having this problem???  any solution?  perhaps running BTC and BCC on different computers????  any other solution to the corrupting DB problem?    - Thanks

I suppose this question is meant for the devs, but just in case: I suggest to just show (display) it. Because right below there's Open Configuration File and the instructions (how to override) are above that button which makes it easy to both see the current setting and know how to change it without reading documentation. The only thing that's missing (see other parts of the GUI) would be advice that a restart is required for the new setting to to take effect. (In case dbcache isn't set in bitcoin.conf, I assume the default value would be displayed).

No, it was not.

Use a custom datadir for one of the nodes. Both will attempt to use the same datadir and that will be very problematic because they are two distinct blockchains.

I just purchased a new external HDD to run a Bitcoin Core node on my MacBook Air. It's syncing right now and I have never felt so much part of the revolution/evolution  :D

I still haven't found a good example, or guide on how to use importmulti to import several privkeys, with say the console for the QT wallet.

it is a pain in the ass that you need to download a total of 3gb to have the bitcoin core though you have a turtle internet what a shame maybe developers out there could manage to have a bit internal of the memory to support many person to download such a thing! we can minimize the GB but not affecting the system and performance and others!

3GB? I hope you're not talking about the 145GB blockchain.  :o

It'd probably take longer as a zip file than to sync using 0
15.1 because the signature validation is more of a bottleneck than network speed usually.

i think 3GB is not that big. I think you need to uninstall unimportant files to accomodate the storage of upgrade bitcoin core. Anyway, the upgrade bitcoin core is such a help for everyones performance.

The problem lies to your turtle net, why not just change your provider so you can experience the usefulness of bitcoin core? This is what I think before I'm trying to download the whole network but it's all worth it when it's done. And if you are also looking at the size, be like this man.

Please see this, it maybe will help you:
This tutorial This is how to import multiple private keys with the importwallet "destination" command

Very fast and smooth sync on x86_64 linux.

Bitcoin is the name of the coin. Bitcoin Core is a full node software for Bitcoin. They are not two separate coins, but they are different things. You do not create an account for either Bitcoin or Bitcoin Core. You need a wallet, which Bitcoin Core is.

Hello. May I ask what is Bitcoin Core for? I am just new in cryptocurrency and ai really am interested in learning blockchain technology as well as the related programs and apps for it.

Thank for sharing, bro
i'm a newbie and i'm confused between choosing Core or Classic
now, i'll choose Core.
have a nice day, all guys.

I'm trying to install a node as outlines on https://bitnodes.earn.com

curl https://bitnodes.earn.com/install-full-node.sh | sh

keep getting a checksum error..

Checksum failed: bitcoin-0.15.1.tar.gz (e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855). Please rerun this script to download and validate the binaries again.

Wow a very astonishing new release. It's the latest stable version there is no final one.

this bitcoin wallet. you can use it. the most reliable wallet for bitcoin!

Does this update increase the transaction speed.. Can someone shed light on this?

I have about 7 wallets and each one is increasing the space they take on my HDD.
Would be nice to have lite versions with functionality of qt wallets.

hopefully this will be very good news which at the moment I hope will have some better features such as stronger security features as well as faster transaction ways. hopefully this project will run successfully because this is what is expected to be a new breakthrough.

Ow that's good thank you for explanation..
I just get stuck and was little bit confused with these bitcoins things
there are a lot of frod also between good products very sad :(

Hi All,

Thank you for this release ! It seems to be a well done update.

Now I have a few questions and fears concerning segwit, segwit2x, btc cash and btcg.

Which is closer to the vision https://www.bitcoincash.org/bitcoin.pdf  ???

Those 2 articles guide my reflection:

https://medium.com/blockchain-law/the-segwit-forks-an-exit-voice-account-b5cf01cbee97

https://medium.com/@jgarzik/bitcoin-is-being-hot-wired-for-settlement-a5beb1df223a

First of all I see that none of the 3 solutions addresses mining gear concentrations and or utility. For example I saw bitmain raises its prices for the S9 brutally. I don't see much competition to bitmain. The A9 aren't bad it is just that the S9 are still better.

However it is the way of mining pow.

Here what I like, and don't about each solutions.

1. Segwit

+ compatibility with old wallet. I think that satoshi must be able at all time to use his wallet. I understand that his coins are still on all chains.

- breach the on chain system, the fees and all ways to estimates income from miners.

- I fear that segwit txs will take over the blocks and or that txs can be blocked from segwit. I know those 2 comments are uninformed but I think that the more segwit scale, the more it will have a larger imbedded fee, which will raise the fee for the on chain users. Is it wrong? Then I fear that segwit may be able to ban certain txs. is it true?

2. Segwit 2x.

basically segwit + a fork. So why even do segwit and not move to bcash? furthermore how could I agree with an agreement from NY were I wasn't even informed or part of it. Nothing. It was totally centralized as a decision.

3. btcash I like the idea of on chain scaling. I think it is the cleanest way forward. However it doesn't change the hardware mining cartel. best fabs, best layout, best everything is very capital intensive. Hardware isn't really open sourceable, yet. Then more practically looking at the wallet options, it is way less clear than with core. At least with core I know one main wallet that works, is continually improved and safe. Here I have no idea which one to download, not even a torrent...

4. Again just moving from bitmain to nvidia isn't a solution. Nvidia anti mining actual attitude and eventually will be tempted by the same moves as bitmain.

Thank you all for reading my little reflection, and I hope that you will be able to help me see clearer between all the options. I love the fact that I can chose what ever I want in the end.

These are completely untrue. You are conflating segwit with the lightning network. They are two completely and absolutely different things. Segwit does not do anything to how fees are calculated nor does it have a "larger imbedded fee" nor does it do anything to raise fees for on chain users. Segwit cannot ban anything. It is a technology, not a system. i suggest that you actually read up on how segwit works (as in read the BIPs) and not just people's blog posts.

One of the biggest issues with on chain scaling is that it becomes more difficult for people who want to run nodes to actually be able to run nodes. The cost required to run a node (which includes more than just bandwidth and disk space) increases dramatically by increasing block sizes, so much so that the idea of decentralized nodes just completely goes out the window.

1.I disagree as soon as the blockspace is increased it changes the pricing structure. it's a simple mathematical statement. I don't understand how you can deny it logically. What ever the modification to the max txs per block will have an impact on the fee. So if txs more to segwit it means less for blockspace or what ever the system off chain (and true I didn't read the bip). I mean it isn't on chain, on the block chain as intented by satoshi and us when we joined. I mean it was clearly all txs in a block every 10 min, the block 1mb, no one can change that blah blah... then saturation.

2. Wrong a 500GB SSD cost 150$ !!! It is such a lie about difficulty for people. What the fuck all interconnected system are super complex to setup and the DIY about banking is quite risky and can WAY more expansive than decades of banking fees...  At one point the market will bash all narratives that you try to construct here. even more brutal will be your fall if you believe them. Safety cost don't increase with the size of the blockchain. your all argument is so flawed, it's brutal... never written a line of code in your life I guess? mostly pr and cr?

I never said that it wouldn't effect fees. I said it does not effect fee calculation.

Segwit transactions are still on chain and fees are still basically calculated in the same way (some constants change). It does not suddenly become impossible to estimate fees are to estimate income for miners. All segwit transactions are in blocks; all data in segwit transactions are in block. Nothing about that has changed.

I do highly suggest that you read up on how segwit actually works before jumping to conclusions and trying to have a discussion about it.

I said there's more to it than just disk space. Can you read?

You also need a computer, one with a CPU and RAM that can handle the load of processing the blocks that are being received. You also need to have enough network bandwidth in order to be able to receive and relay blocks and transactions. Furthermore, blocks could be constructed to be malicious and cause DoS attacks, and larger blocks make those worse. So there's way more to larger blocks than just disk space, or even network bandwidth requirements.

Yes, I totally have never written a single line of code in my life. That's why I have a Github account (https://github.com/achow101) with several repositories (many of which are my own) where I have made several commits. It's also why I have 52 commits in Bitcoin Core (https://github.com/bitcoin/bitcoin/commits?author=achow101) and several Pull Requests (https://github.com/bitcoin/bitcoin/pulls/achow101). It's also why my name is in the release notes at the beginning of this thread.

---

I think I'm being trolled. I'll probably ignore you now.

Okay, In all events thank you very much for your reply. I strongly agree that I have to read this bip and understand at least segwit before speaking. that is why I asked btw. So seg wit is like a block extension not mined by the presegwit node while being only mined by the segwit nodes. so it increase the block space with another code extension which adds more potential vulnerabilities... one instant is enough.

I am sorry but you don't understand the cost of security... again one instant. segwit can be spammed too... it's the cyberspace...

I should venerate you? you know there is distinction between what an engineer does and an user...  a stupid iphone is more power full than the entire nasa apollo space program computer resources... please... there are always those light wallet for anyone who wants... it's core here... or was.

getting this with an url payment

http://i65.tinypic.com/35c36dx.png

The short answer is that BitPay can't manage their server properly (https://bitcointalk.org/index.php?topic=2642207.0). See that thread for more information and workarounds.

Also, in future, please post questions relating to technical problems in the Technical Support board (https://bitcointalk.org/index.php?board=4.0), where they are more likely to be seen by people who can help you.

security is a relative word, some things are seems secured to me when I look at or it may seem not when u look at it. Its more like will it be beneficial to all users. One question hangs in my mind is that, Will this be the future of sending/receiving money or not. heheh

Havings the same issues, hope it will fixed.

Are there any dependents programs like C++ run time software i need to run a full node in windows?  Running 64 bit 15.1 version and allowing connections and about 5 hours later it gets a popup saying ignore,abort and try again run time error.

That only happens when i allow incoming connections..

Not sure what to do, fresh install and fully patched windows 10 pro and Firefox  on a i5 with 8 gb ram and 1 meg dbase cash.

Icon

A job well done or salute to the organizers in this bitcoin.You did your very good idea regarding thisnew core.Congratulations and more tokens to be converted.

Thank you for the updated news.
Really hope transactions will be more faster

Bitcoin Core 0.16.0 has been released: https://bitcointalk.org/index.php?topic=3024763.0