Search results
Jump to navigation
Jump to search
- {{Historical software}} [[Category:Historical versions]] ...3 KB (420 words) - 09:24, 23 September 2025
- ===Emergency versions=== Emergency versions of Bitcoin should preferably be based on the latest stable versions instead of the very latest code in order to avoid introducing new bugs. ...12 KB (1,945 words) - 07:44, 26 September 2022
- message. The versions field within "sendpackages" is interpreted as a bitfield; peers may relay multiple versions of packages. Package relay requires both peers to support wtxid-based relay ...28 KB (4,234 words) - 18:44, 24 April 2024
- * Historical Prime example fronted is tested on the latest versions of: ...8 KB (1,182 words) - 22:35, 20 April 2013
- Consensus code must have bug-for-bug compatibility across versions and implementations (meaning, 0.12 must have the same consensus behaviour a ...ripting engine, signature verification component, and a signing component. Historical database applications do not need signature verification/signing functional ...15 KB (2,318 words) - 17:57, 25 May 2025
- ...K (it is a full node and does everything) or not (it is SPV).<br>In future versions, these bits will convey more precise information about what the node can an ...at found us.<br>So, for example, when the code looks for a peer to request historical blocks from, it prefers an outbound node, if possible. ...17 KB (2,685 words) - 17:55, 25 May 2025
- ...ned as text files in a versioned repository, their revision history is the historical record of the feature proposal. ...igned a number, while Post-History is used to record the dates of when new versions of the BIP are posted to bitcoin mailing lists. Both headers should be in y ...16 KB (2,623 words) - 10:02, 1 January 2021
- ...lid plans to ever re-enable all of these opcodes. They are listed here for historical interest only. This was used by early versions of Bitcoin where people paid directly to IP addresses, before Bitcoin addre ...27 KB (4,435 words) - 15:19, 6 February 2025
- ...ned as text files in a versioned repository, their revision history is the historical record of the feature proposal. ...e BIP was assigned a number, while Post-History is used to record when new versions of the BIP are posted to bitcoin mailing lists. ...34 KB (5,496 words) - 20:07, 24 April 2024
- Note that some download links are no longer valid as highly insecure versions may have been deleted, or links may have changed. ...hasn't been updated for a while. Changelogs for newer versions as well as historical release notes can be found at bitcoin.org: https://bitcoin.org/en/version-h ...47 KB (7,111 words) - 07:58, 26 September 2022
- ...s of the bitcoin system. During synchronization the software is processing historical bitcoin transactions and making sure for itself that all of the rules of th ...it falls back to a build-in list which is updated from time to time in new versions of the software. There is also an IRC based mechanism but it is disabled by ...44 KB (7,257 words) - 01:56, 10 June 2019
- ...s power than used by a GPU. The information in this table is preserved for historical interest, but does not include many GPUs which were released after the adve Stream SDK 2.5 seems to have resolved many of the problems with earlier versions. Everyone's setups will be unique so this should only be a guide or starti ...131 KB (14,245 words) - 23:09, 13 February 2023