We stand with Ukraine to help keep people safe. Join us
All Apps
Best AppsReviewsComparisonsHow-To
When you purchase through links on our site, we may earn an affiliate commission

Bitcoin Core for Mac

Experimental digital currency.

Free
In English
Version 23.0.0
3.8
Based on 5 user rates

Bitcoin Core overview

Bitcoin Core is programmed to decide which block chain contains valid transactions. The users of Bitcoin Core only accept transactions for that block chain, making it the Bitcoin block chain that everyone else wants to use. For the latest developments related to Bitcoin Core, be sure to visit the project’s official website.

The software is a community-driven Open Source project, released under the MIT license.

What’s new in version 23.0.0

P2P and network changes:
  • A bitcoind node will no longer rumour addresses to inbound peers by default. They will become eligible for address gossip after sending an ADDR, ADDRV2, or GETADDR message.
  • Before this release, Bitcoin Core had a strong preference to try to connect only to peers that listen on port 8333. As a result of that, Bitcoin nodes listening on non-standard ports would likely not get any Bitcoin Core peers connecting to them. This preference has been removed.
  • Full support has been added for the CJDNS network. See the new option -cjdnsreachable and doc/cjdns.md
Fee estimation changes:
  • Fee estimation now takes the feerate of replacement (RBF) transactions into account.
Rescan startup parameter removed:
  • The -rescan startup parameter has been removed. Wallets which require rescanning due to corruption will still be rescanned on startup. Otherwise, please use the rescanblockchain RPC to trigger a rescan.
Tracepoints and Userspace, Statically Defined Tracing support:
  • Bitcoin Core release binaries for Linux now include experimental tracepoints which act as an interface for process-internal events. These can be used for review, debugging, monitoring, and more. The tracepoint API is semi-stable. While the API is tested, process internals might change between releases requiring changes to the tracepoints. Information about the existing tracepoints can be found under doc/tracing.md and usage examples are provided in contrib/tracing/.
Updated RPCs:
  • The validateaddress RPC now returns an error_locations array for invalid addresses, with the indices of invalid character locations in the address (if known). For example, this will attempt to locate up to two Bech32 errors, and return their locations if successful. Success and correctness are only guaranteed if fewer than two substitution errors have been made. The error message returned in the error field now also returns more specific errors when decoding fails.
  • The -deprecatedrpc=addresses configuration option has been removed. RPCs gettxout, getrawtransaction, decoderawtransaction, decodescript, gettransaction verbose=true and REST endpoints /rest/tx, /rest/getutxos, /rest/block no longer return the addresses and reqSigs fields, which were previously deprecated in 22.0.
  • The getblock RPC command now supports verbosity level 3 containing transaction inputs’ prevout information. The existing /rest/block/ REST endpoint is modified to contain this information too. Every vin field will contain an additional prevout subfield describing the spent output. prevout contains the following keys:
    • generated - true if the spent coins was a coinbase.
    • height
    • value
    • scriptPubKey
  • The top-level fee fields fee, modifiedfee, ancestorfees and descendantfees returned by RPCs getmempoolentry,getrawmempool(verbose=true), getmempoolancestors(verbose=true) and getmempooldescendants(verbose=true) are deprecated and will be removed in the next major version (use -deprecated=fees if needed in this version). The same fee fields can be accessed through the fees object in the result. WARNING: deprecated fields ancestorfees and descendantfees are denominated in sats, whereas all fields in the fees object are denominated in BTC.
  • Both createmultisig and addmultisigaddress now include a warnings field, which will show a warning if a non-legacy address type is requested when using uncompressed public keys.
  • Changes to wallet related RPCs can be found in the Wallet section below.
New RPCs:
  • Information on soft fork status has been moved from getblockchaininfo to the new getdeploymentinfo RPC which allows querying soft fork status at any block, rather than just at the chain tip. Inclusion of soft fork status in getblockchaininfo can currently be restored using the configuration -deprecatedrpc=softforks, but this will be removed in a future release. Note that in either case, the status field now reflects the status of the current block rather than the next block.
Files:
  • On startup, the list of banned hosts and networks (via setban RPC) in banlist.dat is ignored and only banlist.json is considered. Bitcoin Core version 22.x is the only version that can read banlist.dat and also write it to banlist.json. If banlist.json already exists, version 22.x will not try to translate the banlist.dat into json. After an upgrade, listbanned can be used to double check the parsed entries.
Updated settings:
  • In previous releases, the meaning of the command line option -persistmempool (without a value provided) incorrectly disabled mempool persistence. -persistmempool is now treated like other boolean options to mean -persistmempool=1. Passing -persistmempool=0, -persistmempool=1 and -nopersistmempool is unaffected.
  • -maxuploadtarget now allows human readable byte units [k|K|m|M|g|G|t|T]. E.g. -maxuploadtarget=500g. No whitespace, +- or fractions allowed. Default is M if no suffix provided.
  • If -proxy= is given together with -noonion then the provided proxy will not be set as a proxy for reaching the Tor network. So it will not be possible to open manual connections to the Tor network for example with the addnode RPC. To mimic the old behavior use -proxy= together with -onlynet= listing all relevant networks except onion.
Tools and Utilities:
  • Update -getinfo to return data in a user-friendly format that also reduces vertical space.
  • CLI -addrinfo now returns a single field for the number of onion addresses known to the node instead of separate torv2 and torv3 fields, as support for Tor V2 addresses was removed from Bitcoin Core in 22.0.
Wallet:
  • Descriptor wallets are now the default wallet type. Newly created wallets will use descriptors unless descriptors=false is set during createwallet, or the Descriptor wallet checkbox is unchecked in the GUI.
  • Note that wallet RPC commands like importmulti and dumpprivkey cannot be used with descriptor wallets, so if your client code relies on these commands without specifying descriptors=false during wallet creation, you will need to update your code.
  • Newly created descriptor wallets will contain an automatically generated tr() descriptor which allows for creating single key Taproot receiving addresses.
  • upgradewallet will now automatically flush the keypool if upgrading from a non-HD wallet to an HD wallet, to immediately start using the newly-generated HD keys.
  • a new RPC newkeypool has been added, which will flush (entirely clear and refill) the keypool.
  • listunspent now includes ancestorcount, ancestorsize, and ancestorfees for each transaction output that is still in the mempool.
  • lockunspent now optionally takes a third parameter, persistent, which causes the lock to be written persistently to the wallet database. This allows UTXOs to remain locked even after node restarts or crashes.
  • receivedby RPCs now include coinbase transactions. Previously, the following wallet RPCs excluded coinbase transactions: getreceivedbyaddress, getreceivedbylabel, listreceivedbyaddress, listreceivedbylabel. This release changes this behaviour and returns results accounting for received coins from coinbase outputs. The previous behaviour can be restored using the configuration -deprecatedrpc=exclude_coinbase, but may be removed in a future release.
  • A new option in the same receivedby RPCs, include_immature_coinbase (default=false), determines whether to account for immature coinbase transactions. Immature coinbase transactions are coinbase transactions that have 100 or fewer confirmations, and are not spendable.
GUI changes:
  • UTXOs which are locked via the GUI are now stored persistently in the wallet database, so are not lost on node shutdown or crash.
  • The Bech32 checkbox has been replaced with a dropdown for all address types, including the new Bech32m (BIP-350) standard for Taproot enabled wallets.
Low-level changes:
  • RPC: getblockchaininfo now returns a new time field, that provides the chain tip time.
  • Tests: For the regtest network the activation heights of several softforks were set to block height 1. They can be changed by the runtime setting -testactivationheight=name@height.

Bitcoin Core for Mac

Free
In English
Version 23.0.0
Write a detailed review about Bitcoin Core

Write your thoughts in our old-fashioned comment

MacUpdate Comment Policy. We strongly recommend leaving comments, however comments with abusive words, bullying, personal attacks of any type will be moderated.
3.8

(7 Reviews of Bitcoin Core)

  • Comments

  • User Ratings

Dana-Sutton
Dana-Sutton
Dec 17 2017
0.15.1
0.0
Dec 17 2017
0.0
Version: 0.15.1
Back in the seventeenth century there used to be a Dutch app. called Tulips that was aimed at pretty much the same audience.
Mac007
Mac007
Jun 19 2013
0.8.2
0.0
Jun 19 2013
0.0
Version: 0.8.2
Be sure to consider the risks involved with this app. http://bitcoin.org/en/you-need-to-know
Monkeyjunkey
Monkeyjunkey
Feb 22 2013
0.7.1
5.0
Feb 22 2013
5.0
Version: 0.7.1
And we're at 0.8.0.
Monkeyjunkey
Monkeyjunkey
Sep 23 2012
0.6.3
5.0
Sep 23 2012
5.0
Version: 0.6.3
0.7.0 is out: http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.7.0/
Monkeyjunkey
Monkeyjunkey
Jun 18 2012
0.6.2
5.0
Jun 18 2012
5.0
Version: 0.6.2
Awesome concept. I'd love to see broader acceptance for this. Minors: * URI support on the mac is currently still missing. Wonder why, since it would be great to improve adaptation. * Client eats up some CPU while catching up. Hope they can tweak that in the future.
JunT7292
JunT7292
Mar 23 2014
1.0
Mar 23 2014
1.0
Version: null
Monkeyjunkey
Monkeyjunkey
Sep 14 2013
5.0
Sep 14 2013
5.0
Version: null
Zpk
Zpk
Jun 17 2013
5.0
Jun 17 2013
5.0
Version: null
barzus
barzus
Jun 17 2013
5.0
Jun 17 2013
5.0
Version: null
H3L0
H3L0
May 11 2013
3.5
May 11 2013
3.5
Version: null