Navigation:
Bitcoin Portable 30.1 freeware
Bitcoin Core, developed by Satoshi Nakamoto, is the original software for the Bitcoin network, serving as a full node wallet that ensures the integrity and security of transactions. It empowers users to participate in the decentralized Bitcoin ecosystem by validating blocks and transactions, while also providing a user-friendly interface for managing funds. With robust privacy features and regular updates, Bitcoin Core remains a cornerstone for enthusiasts and developers alike, fostering trust a ...
| Author | Satoshi Nakamoto |
| Released | 2026-01-02 |
| Filesize | 29.90 MB |
| Downloads | 2876 |
| OS | Windows 11, Windows 10 32/64 bit |
| Installation | Instal And Uninstall |
| Keywords | Bitcoin Core, cash system, online payment, cash, finance, P2P, transaction |
| Users' rating (37 rating) |
Bitcoin Portable Free Download - we do not host any Bitcoin Portable torrent files or links of Bitcoin Portable on rapidshare.com, depositfiles.com, megaupload.com etc. All Bitcoin Portable download links are direct Bitcoin Portable download from publisher site or their selected mirrors.
| 30.1 | Jan 2, 2026 | New Release | Wallet: #33528 wallet: don't consider unconfirmed TRUC coins with ancestors Build: #33580 depends: Use $(package)_file_name when downloading from the fallback #33906 depends: Add patch for Windows11Style plugin #32009 contrib: turn off compression of macOS SDK to fix determinism IPC: #33229 multiprocess: Don't require bitcoin -m argument when IPC options are used #33517 multiprocess: Fix high overhead from message logging #33519 Update libmultiprocess subtree in 30.x branch #33566 miner: fix empty mempool case for waitNext() #33676 interfaces: enable cancelling running waitNext calls P2P: #33723 chainparams: remove dnsseed.bitcoin.dashjr-list-of-p2p-nodes.us GUI: gui#899 qt: Modernize custom filtering gui#901 Add createwallet, createwalletdescriptor, and migratewallet to history filter Test: #33612 test: change log rate limit version gate Doc: #33630 doc: correct topology requirements in submitpackage helptext #33826 scripted-diff: Remove obsolete comment #33827 doc: Correct pkgin command usage on NetBSD Misc: #33508 ci: fix buildx gha cache authentication on forks #33558 ci: Use native platform for win-cross task #33581 ci: Properly include $FILE_ENV in DEPENDS_HASH #33744 ci: Fix lint runner selection (and docker cache) #33996 contrib: fix manpage generation |
| 30.0 | Oct 13, 2025 | New Release | Policy: The maximum number of potentially executed legacy signature operations in a single standard transaction is now limited to 2500. Signature operations in all previous output scripts, in all input scripts, as well as all P2SH redeem scripts (if there are any) are counted toward the limit. The new limit is assumed to not affect any known typically formed standard transactions. The change was done to prepare for a possible BIP54 deployment in the future. (#32521) -datacarriersize is increased to 100,000 by default, which effectively uncaps the limit (as the maximum transaction size limit will be hit first). It can be overridden with -datacarriersize=83 to revert to the limit enforced in previous versions. (#32406) Multiple data carrier (OP_RETURN) outputs in a transaction are now permitted for relay and mining. The -datacarriersize limit applies to the aggregate size of the scriptPubKeys across all such outputs in a transaction, not including the scriptPubKey size itself. (#32406) The minimum block feerate (-blockmintxfee) has been changed to 0.001 satoshi per vB. It can still be changed using the configuration option. This option can be used by miners to set a minimum feerate on packages added to block templates. (#33106) The default minimum relay feerate (-minrelaytxfee) and incremental relay feerate (-incrementalrelayfee) have been changed to 0.1 satoshis per vB. They can still be changed using their respective configuration options, but it is recommended to change both together if you decide to do so. (#33106) Other minimum feerates (e.g. the dust feerate, the minimum returned by the fee estimator, and all feerates used by the wallet) remain unchanged. The mempool minimum feerate still changes in response to high volume. Note that unless these lower defaults are widely adopted across the network, transactions created with lower fee rates are not guaranteed to propagate or confirm. The wallet feerates remain unchanged; -mintxfee must be changed before attempti |
| 29.0 | Apr 15, 2025 | New Release | P2P and network changes: Transactions of non-witness size 65 bytes and above are now allowed by mempool and relay policy. This is to better reflect the actual afforded protections against CVE-2017-12842 and open up additional use-cases of smaller transaction sizes. (#26265) New RPCs: The scanblocks RPC returns the relevant blockhashes from a set of descriptors by scanning all blockfilters in the given range. It can be used in combination with the getblockheader and rescanblockchain RPCs to achieve fast wallet rescans. Note that this functionality can only be used if a compact block filter index (-blockfilterindex=1) has been constructed by the node. (#23549) Updated RPCs: All JSON-RPC methods accept a new named parameter called args that can contain positional parameter values. This is a convenience to allow some parameter values to be passed by name without having to name every value. The python test framework and bitcoin-cli tool both take advantage of this, so for example: bitcoin-cli -named createwallet wallet_name=mywallet load_on_startup=1 Can now be shortened to: bitcoin-cli -named createwallet mywallet load_on_startup=1 The verifychain RPC will now return false if the checks didn’t fail, but couldn’t be completed at the desired depth and level. This could be due to missing data while pruning, due to an insufficient dbcache or due to the node being shutdown before the call could finish. (#25574) sendrawtransaction has a new, optional argument, maxburnamount with a default value of 0. Any transaction containing an unspendable output with a value greater than maxburnamount will not be submitted. At present, the outputs deemed unspendable are those with scripts that begin with an OP_RETURN code (known as ‘datacarriers’), scripts that exceed the maximum script size, and scripts that contain invalid opcodes. The testmempoolaccept RPC now returns 2 additional results within the “fees” result: “effective-feerate” is the feerate including fees and siz |
