{"built": "2026-11-13", "passages": [{"id": "abc-bchn-split#infobox", "slug": "abc-bchn-split", "title": "ABC vs BCHN split", "section": "Summary and infobox", "text": "The November 2020 split in which Bitcoin ABC, insisting on an 8% coinbase funding rule, left Bitcoin Cash; its chain became BCHA, later eCash. Date: 15 November 2020 [btk-xec]; Last common block: 661,647 [btk-xec]; First ABC-only block: 661,648 [btk-xec]; Cause: Bitcoin ABC's 8% coinbase rule (Infrastructure Funding Plan) [btk-xec]; Outcome: ABC chain traded as BCHA, renamed eCash (XEC) on 1 July 2021 [btk-xec]; BCH side: Bitcoin Cash Node and other clients kept BCH [ep-s17e26-bchn]", "aliases": "bcha ifp coinbase rule 2020 split", "refs": ["btk-xec", "ep-s17e26-bchn"], "url": "/wiki/abc-bchn-split/"}, {"id": "abc-bchn-split#takeover", "slug": "abc-bchn-split", "title": "ABC vs BCHN split", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: the only Bitcoin Cash split fought over money for developers rather than block size, and the episode in which the original client lost the ticker it created. [btk-xec] [ep-s17e19-ifp]", "aliases": "bcha ifp coinbase rule 2020 split", "refs": ["btk-xec", "ep-s17e19-ifp"], "url": "/wiki/abc-bchn-split/"}, {"id": "abc-bchn-split#2", "slug": "abc-bchn-split", "title": "ABC vs BCHN split", "section": "The rule", "text": "Bitcoin Cash's November 2020 upgrade split the chain at block 661,648 over the 8% coinbase rule, and the ABC chain traded as BCHA [btk-xec]. Wikipedia describes it as a second contested hard fork in which the leading node implementation, Bitcoin ABC, created BCHA [wp-bch]. The rule is documented in eCash's Infrastructure Funding Plan [xec-ifp].", "aliases": "bcha ifp coinbase rule 2020 split", "refs": ["btk-xec", "wp-bch", "xec-ifp"], "url": "/wiki/abc-bchn-split/"}, {"id": "abc-bchn-split#3", "slug": "abc-bchn-split", "title": "ABC vs BCHN split", "section": "ABC's side", "text": "On S17 E19, Amaury Séchet said “the core of the split was really around the funding”: other implementations had more funding than ABC, which was “constantly running out of money”, so it needed a self-funding mechanism [ep-s17e19-ifp].", "aliases": "bcha ifp coinbase rule 2020 split", "refs": ["ep-s17e19-ifp"], "url": "/wiki/abc-bchn-split/"}, {"id": "abc-bchn-split#4", "slug": "abc-bchn-split", "title": "ABC vs BCHN split", "section": "BCHN's side", "text": "On S17 E26, Calin Culianu summarised it as “Bitcoin ABC until Amaury decided to charge tax, and then we kicked them out”, with the remaining code renamed Bitcoin Cash Node [ep-s17e26-bchn].", "aliases": "bcha ifp coinbase rule 2020 split", "refs": ["ep-s17e26-bchn"], "url": "/wiki/abc-bchn-split/"}, {"id": "abc-bchn-split#5", "slug": "abc-bchn-split", "title": "ABC vs BCHN split", "section": "Afterwards", "text": "BCHA was renamed eCash (XEC) on 1 July 2021, at 1 BCHA to 1,000,000 XEC [btk-xec].", "aliases": "bcha ifp coinbase rule 2020 split", "refs": ["btk-xec"], "url": "/wiki/abc-bchn-split/"}, {"id": "abc-bchn-split#6", "slug": "abc-bchn-split", "title": "ABC vs BCHN split", "section": "Heard on Bitcoin Takeover", "text": "Marc De Mesel described his side of the 2020 split on S17 E44 (September 2026): “I really did not agree with what Amaury was planning for Bitcoin Cash. He planned to introduce a, they call it dev tax.” [ep-s17e44-q496]", "aliases": "bcha ifp coinbase rule 2020 split", "refs": ["ep-s17e44-q496"], "url": "/wiki/abc-bchn-split/"}, {"id": "abitchain#infobox", "slug": "abitchain", "title": "ABitchain (ABTC)", "section": "Summary and infobox", "text": "A registration airdrop listing at block 498,888 with a 100:1 ratio and 3 billion supply; no chain, code or announcement was found. Snapshot (forkdrop): Block 498,888 [fd-data]; Block 498,888 time: 2017-12-12 10:29:53 UTC [btc-498888]; Ratio (forkdrop): 100:1 [fd-data]; Max supply (forkdrop): 3 Billion [fd-data]; forkdrop reason: “Airdrop Over” [fd-data]", "aliases": "abtc abitchain", "refs": ["btc-498888", "fd-data"], "url": "/wiki/abitchain/"}, {"id": "abitchain#takeover", "slug": "abitchain", "title": "ABitchain (ABTC)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: ABitchain is a single-source entry; the 2017 project page was not archived. [fd-data]", "aliases": "abtc abitchain", "refs": ["fd-data"], "url": "/wiki/abitchain/"}, {"id": "abitchain#9", "slug": "abitchain", "title": "ABitchain (ABTC)", "section": "Record", "text": "forkdrop's data file lists ABitchain with ticker ABTC, a registration airdrop at block 498888 on 2017-12-12, a 100:1 ratio and a maximum supply of 3 Billion [fd-data]. Block 498,888 was mined on 12 December 2017 [btc-498888]. forkdrop gives the source chain as “???” and files the coin among historic entries with the reason “Airdrop Over” [fd-data]. No 2017-2018 capture of the project site was found, and no code or announcement was found either [fd-data].", "aliases": "abtc abitchain", "refs": ["btc-498888", "fd-data"], "url": "/wiki/abitchain/"}, {"id": "adam-back#infobox", "slug": "adam-back", "title": "Adam Back", "section": "Summary and infobox", "text": "British cryptographer who invented Hashcash, co-founded Blockstream, and opposed Bitcoin XT's hard fork. Born: July 1970, London [wp-back]; Invention: Hashcash (1997), the basis of Bitcoin-style proof of work [wp-back]; Company: Co-founded Blockstream in 2014; CEO from 3 Oct 2016 [wp-back]; Hong Kong Roundtable: Signed as President, Blockstream [hk-letter]; 2015 roadmap: Signatory of “Capacity increases for the Bitcoin system” [roadmap-2015]; Satoshi question: Named as a candidate by journalists; denies it [wp-back]", "aliases": "adam3us hashcash", "refs": ["hk-letter", "roadmap-2015", "wp-back"], "url": "/wiki/adam-back/"}, {"id": "adam-back#takeover", "slug": "adam-back", "title": "Adam Back", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Back is the small-block side's most visible executive. Fork Wars records his August 2015 “2-4-8” suggestion, which complicates the idea that his side never offered larger blocks. [btk-forkwars]", "aliases": "adam3us hashcash", "refs": ["btk-forkwars"], "url": "/wiki/adam-back/"}, {"id": "adam-back#12", "slug": "adam-back", "title": "Adam Back", "section": "Cryptographer", "text": "Back was born in London in July 1970 and has a computer science PhD from the University of Exeter [wp-back]. In 1997 he invented Hashcash; a similar system is used in Bitcoin [wp-back]. He was one of the first two people to receive an email from Satoshi Nakamoto [wp-back].", "aliases": "adam3us hashcash", "refs": ["wp-back"], "url": "/wiki/adam-back/"}, {"id": "adam-back#13", "slug": "adam-back", "title": "Adam Back", "section": "Block size war", "text": "Back criticised Bitcoin XT's 75% activation threshold as too low [xt-bw]. Fork Wars records an August 2015 tweet in which he suggested 2 MB, then 4 MB in two years and 8 MB in four [btk-forkwars]. He signed the December 2015 capacity roadmap and the February 2016 Hong Kong Roundtable statement, the latter as President of Blockstream [roadmap-2015] [hk-letter].", "aliases": "adam3us hashcash", "refs": ["btk-forkwars", "hk-letter", "roadmap-2015", "xt-bw"], "url": "/wiki/adam-back/"}, {"id": "adam-back#14", "slug": "adam-back", "title": "Adam Back", "section": "Satoshi speculation", "text": "Several outlets have named Back as a possible Satoshi Nakamoto, and in 2026 an investigation by John Carreyrou in The New York Times asserted that he is; Back denied the allegation [wp-back].", "aliases": "adam3us hashcash", "refs": ["wp-back"], "url": "/wiki/adam-back/"}, {"id": "amaury-sechet#infobox", "slug": "amaury-sechet", "title": "Amaury Séchet (deadalnix)", "section": "Summary and infobox", "text": "Bitcoin ABC lead developer; launched Bitcoin Cash in 2017 and eCash (XEC) in 2020. Handle: deadalnix [ep-s17e19-ecash]; Known for: Bitcoin ABC; Bitcoin Cash (2017); eCash XEC (2020) [btk-xec]; Takeover episodes: S15 E28 (2024), S17 E19 (2026) [ep-s17e19-ecash]", "aliases": "deadalnix", "refs": ["btk-xec", "ep-s17e19-ecash"], "url": "/wiki/amaury-sechet/"}, {"id": "amaury-sechet#takeover", "slug": "amaury-sechet", "title": "Amaury Séchet (deadalnix)", "section": "Takeover view (editorial opinion)", "text": "Vlad introduced him on S17 E19 as “the Greg Maxwell of big blockers”. Every big-block article in the Forks! magazine runs into him eventually. [ep-s17e19-sponsors] [btk-xec]", "aliases": "deadalnix", "refs": ["btk-xec", "ep-s17e19-sponsors"], "url": "/wiki/amaury-sechet/"}, {"id": "amaury-sechet#17", "slug": "amaury-sechet", "title": "Amaury Séchet (deadalnix)", "section": "Career", "text": "Amaury Séchet, known as deadalnix, led Bitcoin ABC, the software that launched Bitcoin Cash in 2017 [btk-bch]. He told Bitcoin Takeover that the original plan was an extension block, and that Bitcoin ABC was started when that did not work [btk-xec]. He said ABC was its own fork of Bitcoin Core rather than a reuse of XT, Classic or Unlimited [ep-s17e19-abc].", "aliases": "deadalnix", "refs": ["btk-bch", "btk-xec", "ep-s17e19-abc"], "url": "/wiki/amaury-sechet/"}, {"id": "amaury-sechet#18", "slug": "amaury-sechet", "title": "Amaury Séchet (deadalnix)", "section": "Two more splits", "text": "In 2018, Bitcoin SV split away after the nChain camp rejected ABC-led changes; in 2020 his own chain left Bitcoin Cash over an 8% developer fund and became eCash (XEC) [btk-xec]. Kurt Wuckert Jr. gave the opposing view of that period on S17 E39 [ep-s17e39-avalanche].", "aliases": "deadalnix", "refs": ["btk-xec", "ep-s17e39-avalanche"], "url": "/wiki/amaury-sechet/"}, {"id": "anon#infobox", "slug": "anon", "title": "ANON (Anonymous Bitcoin)", "section": "Summary and infobox", "text": "A 2018 Zerocash-protocol coin bootstrapped from a merge of the Bitcoin and Zclassic UTXO sets, 1:1 for BTC and 2:1 for ZCL, with masternodes. Source chains: Bitcoin (1:1) and Zclassic (2:1) [anon-site]; Snapshot (forkdrop): Block 540,870 [fd-data]; Block 540,870 time: 2018-09-11 00:59:09 UTC [btc-540870]; Protocol: Zerocash, Equihash PoW, masternodes [anon-readme]; forkdrop reason: “Reneged” [fd-data]", "aliases": "anon anonymous bitcoin zerocash zclassic masternodes", "refs": ["anon-readme", "anon-site", "btc-540870", "fd-data"], "url": "/wiki/anon/"}, {"id": "anon#takeover", "slug": "anon", "title": "ANON (Anonymous Bitcoin)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: ANON used the same recipe as Bitcoin Private, a Zclassic-code chain seeded with a snapshot of Bitcoin balances. [anon-readme] [btcp-readme]", "aliases": "anon anonymous bitcoin zerocash zclassic masternodes", "refs": ["anon-readme", "btcp-readme"], "url": "/wiki/anon/"}, {"id": "anon#21", "slug": "anon", "title": "ANON (Anonymous Bitcoin)", "section": "Design", "text": "The README says ANON “is an implementation of the zerocash protocol, bootstrapped with a merge of the Official Bitcoin and Zclassic UTXO sets via a snapshot and airdrop, and with the additional implementation of masternodes” [anon-readme]. The archived site, captured on 25 August 2018, says the fork gives “a 2:1 ratio of ANON to all holders of ZClassic” and 1:1 to Bitcoin holders [anon-site]. It says ANON uses Equihash proof of work [anon-site].", "aliases": "anon anonymous bitcoin zerocash zclassic masternodes", "refs": ["anon-readme", "anon-site"], "url": "/wiki/anon/"}, {"id": "anon#22", "slug": "anon", "title": "ANON (Anonymous Bitcoin)", "section": "Record", "text": "forkdrop's data file gives block 540870 and a date of 2018-09-10, links a BTCManager announcement, and files it among historic entries with the reason “Reneged” [fd-data]. Block 540,870 was mined in the first hour of 11 September 2018 UTC [btc-540870]. Bitcoin Private describes itself the same way, as “a fork of Zclassic, merging in a snapshotted UTXO set of Bitcoin” [btcp-readme].", "aliases": "anon anonymous bitcoin zerocash zclassic masternodes", "refs": ["btc-540870", "btcp-readme", "fd-data"], "url": "/wiki/anon/"}, {"id": "antoine-poinsot#infobox", "slug": "antoine-poinsot", "title": "Antoine Poinsot", "section": "Summary and infobox", "text": "Bitcoin Core contributor (GitHub darosior) and lead author of BIP-54, the Consensus Cleanup soft fork that fixes the timewarp bug. GitHub: darosior [gh-darosior]; Organization (GitHub): @chaincodelabs [gh-darosior]; BIP-54: Author, with Matt Corallo [bip54]; BIP-54 assigned: 2025-04-11 [bip54]; BIP-54 status: Complete [bip54]", "aliases": "antoine poinsot darosior bip54", "refs": ["bip54", "gh-darosior"], "url": "/wiki/antoine-poinsot/"}, {"id": "antoine-poinsot#takeover", "slug": "antoine-poinsot", "title": "Antoine Poinsot", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Poinsot's BIP-54 is the Consensus Cleanup that Robin Linus discussed on S17 E48 against Peter Todd's guess of a 2029 activation. [bip54] [ep-s17e48-gcc]", "aliases": "antoine poinsot darosior bip54", "refs": ["bip54", "ep-s17e48-gcc"], "url": "/wiki/antoine-poinsot/"}, {"id": "antoine-poinsot#25", "slug": "antoine-poinsot", "title": "Antoine Poinsot", "section": "BIP-54", "text": "BIP-54, “Consensus Cleanup”, lists Antoine Poinsot and Matt Corallo as authors and was assigned on 2025-04-11 [bip54]. It “proposes new consensus rules in order to fix the timewarp attack, reduce the worst case block validation time, prevent Merkle tree weaknesses” and avoid duplicate transactions [bip54]. Optech's topic page on the consensus cleanup soft fork also covers BIP-54 [optech-gcc]. See Great Consensus Cleanup and the timewarp bug [bip54].", "aliases": "antoine poinsot darosior bip54", "refs": ["bip54", "optech-gcc"], "url": "/wiki/antoine-poinsot/"}, {"id": "antoine-poinsot#26", "slug": "antoine-poinsot", "title": "Antoine Poinsot", "section": "Profile", "text": "His GitHub account is darosior, and the profile lists the organization @chaincodelabs [gh-darosior]. Other roles and dates are not sourced here [gh-darosior].", "aliases": "antoine poinsot darosior bip54", "refs": ["gh-darosior"], "url": "/wiki/antoine-poinsot/"}, {"id": "antpool#infobox", "slug": "antpool", "title": "Antpool", "section": "Summary and infobox", "text": "Bitmain's Bitcoin mining pool: a Hong Kong Roundtable signer in 2016, a Bitcoin Cash backer that burned part of its BCH, and a 2022 funder of Ethereum Classic grants. Operator: Bitmain [wp-bitmain]; Hong Kong, Feb 2016: Kevin Pan, Manager, signed [hk-letter]; BCH burn: 12% of mined BCH sent to irrecoverable addresses [wp-bitmain]; ETC grants (Jul 2022): With Bitmain, $10M grants programme [etc-history]", "aliases": "antpool ant pool kevin pan", "refs": ["etc-history", "hk-letter", "wp-bitmain"], "url": "/wiki/antpool/"}, {"id": "antpool#takeover", "slug": "antpool", "title": "Antpool", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Antpool's hashrate made it a signer whose name carried weight at Hong Kong, and its BCH burn is an unusual case of a pool destroying its own revenue to push a fork. [btk-forkwars] [wp-bitmain]", "aliases": "antpool ant pool kevin pan", "refs": ["btk-forkwars", "wp-bitmain"], "url": "/wiki/antpool/"}, {"id": "antpool#29", "slug": "antpool", "title": "Antpool", "section": "Pool", "text": "Wikipedia says Bitmain operates BTC.com and Antpool, “historically two of the largest mining pools for bitcoin” [wp-bitmain]. Its homepage title reads “ANTPOOL - 先进的比特币矿池” (Chinese for advanced Bitcoin mining pool) [antpool-site]. When the pool started is not sourced here [wp-bitmain].", "aliases": "antpool ant pool kevin pan", "refs": ["antpool-site", "wp-bitmain"], "url": "/wiki/antpool/"}, {"id": "antpool#30", "slug": "antpool", "title": "Antpool", "section": "Forks", "text": "Kevin Pan signed the February 2016 Hong Kong Roundtable statement as “Manager AntPool” [hk-letter]; Bitcoin Takeover lists AntPool among the pools that, the authors said, had more than 80 percent of recent hash power [btk-forkwars]. Wikipedia says that to boost Bitcoin Cash prices, Antpool “burned” 12% of the BCH it mined [wp-bitmain]. In July 2022 the Ethereum Classic site recorded that “AntPool and Bitmain signal support for Ethereum Classic ecosystem with $10M Investment in a Grants program” [etc-history].", "aliases": "antpool ant pool kevin pan", "refs": ["btk-forkwars", "etc-history", "hk-letter", "wp-bitmain"], "url": "/wiki/antpool/"}, {"id": "avalanche#infobox", "slug": "avalanche", "title": "Avalanche (consensus)", "section": "Summary and infobox", "text": "A family of leaderless, metastable voting protocols that eCash layers on top of Nakamoto consensus to finalise blocks and, since 2025, transactions. Origin: “Scalable and Probabilistic Leaderless BFT Consensus through Metastability”, arXiv, 2019 [avalanche-paper]; Authors: Team Rocket, Maofan Yin, Kevin Sekniqi, Robbert van Renesse, Emin Gün Sirer [avalanche-paper]; On eCash: blocks: Post-consensus since 14 September 2022 [btk-xec]; On eCash: transactions: Finalised since 15 November 2025 (block 923,347) [btk-xec]; Stake requirement: At least 100 million XEC, unmoved for 2,016 blocks [btk-xec]; Not to be confused with: AVAX, Ava Labs' chain: both build on the same consensus paper but share no validators, token or network [btk-xec]", "aliases": "avalanche avax pre-consensus staking finality", "refs": ["avalanche-paper", "btk-xec"], "url": "/wiki/avalanche/"}, {"id": "avalanche#takeover", "slug": "avalanche", "title": "Avalanche (consensus)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Avalanche is Amaury Séchet's answer to the hash war that split Bitcoin Cash. Instead of trusting hashpower alone, eCash nodes with stake vote on the tip, which Séchet says makes many 51% attacks “just not possible”. [ep-s17e19-aval] [btk-xec]", "aliases": "avalanche avax pre-consensus staking finality", "refs": ["btk-xec", "ep-s17e19-aval"], "url": "/wiki/avalanche/"}, {"id": "avalanche#33", "slug": "avalanche", "title": "Avalanche (consensus)", "section": "The protocol", "text": "The 2019 arXiv paper by “Team Rocket”, Maofan Yin, Kevin Sekniqi, Robbert van Renesse and Emin Gün Sirer introduces “a family of leaderless Byzantine fault tolerance protocols” built on metastability [avalanche-paper]. Asked why eCash chose it, Séchet said: “Because it's fast and it's simple. And it's actually correct, because many of the alternatives that are out there are unsound” [ep-s17e19-avalwhy].", "aliases": "avalanche avax pre-consensus staking finality", "refs": ["avalanche-paper", "ep-s17e19-avalwhy"], "url": "/wiki/avalanche/"}, {"id": "avalanche#34", "slug": "avalanche", "title": "Avalanche (consensus)", "section": "On eCash", "text": "On S17 E19 Amaury Séchet described Avalanche as a consensus layer added on top of the BCH-derived protocol that “can make decisions in seconds, typically less than two seconds” [ep-s17e19-aval]. He said it produces no auditable record, “which is why we don't want to remove the Nakamoto consensus” [ep-s17e19-aval]. Bitcoin Takeover's eCash article dates block post-consensus to 14 September 2022 and transaction finality to 15 November 2025, block 923,347 [btk-xec].", "aliases": "avalanche avax pre-consensus staking finality", "refs": ["btk-xec", "ep-s17e19-aval"], "url": "/wiki/avalanche/"}, {"id": "avalanche#35", "slug": "avalanche", "title": "Avalanche (consensus)", "section": "Staking", "text": "The eCash article says staking requires each staked coin to hold at least 100 million XEC and stay unmoved for 2,016 blocks, on an always-on Avalanche node, and that since November 2023 10% of each block goes to one staker chosen by lottery [btk-xec]. Kurt Wuckert Jr. discussed Avalanche pre-consensus and his disagreement with Séchet on S17 E39 [ep-s17e39-avalanche]. See eCash (XEC).", "aliases": "avalanche avax pre-consensus staking finality", "refs": ["btk-xec", "ep-s17e39-avalanche"], "url": "/wiki/avalanche/"}, {"id": "bch-bsv-hash-war#infobox", "slug": "bch-bsv-hash-war", "title": "BCH–BSV hash war", "section": "Summary and infobox", "text": "The November 2018 contest between Bitcoin ABC and Bitcoin SV over Bitcoin Cash's upgrade, which split BCH into two chains. Date: 15 November 2018 [btk-bsv]; Last common block: 556,766, mined by SVPool [btk-bsv]; First BSV-only block: 556,767 [btk-bsv]; ABC side: Roger Ver, Jihan Wu (Bitmain); 32 MB [wp-bsv]; SV side: Craig Wright, Calvin Ayre; 128 MB [wp-bsv]; Disputed changes: CTOR and OP_CHECKDATASIG, activated by BCH and rejected by BSV [btk-bsv]; Prices on split day: BCH about $289, BSV about $96.50 [wp-bsv]", "aliases": "hash war 2018 bsv bch split", "refs": ["btk-bsv", "wp-bsv"], "url": "/wiki/bch-bsv-hash-war/"}, {"id": "bch-bsv-hash-war#takeover", "slug": "bch-bsv-hash-war", "title": "BCH–BSV hash war", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Takeover has heard both sides on air: Kurt Wuckert Jr. called the ABC side dishonest in how it fought, while Amaury Séchet argued BSV's whole premise was that whatever Craig says is gospel. [ep-s17e39-hashwar] [ep-s17e19-bsv]", "aliases": "hash war 2018 bsv bch split", "refs": ["ep-s17e19-bsv", "ep-s17e39-hashwar"], "url": "/wiki/bch-bsv-hash-war/"}, {"id": "bch-bsv-hash-war#38", "slug": "bch-bsv-hash-war", "title": "BCH–BSV hash war", "section": "The split", "text": "Bitcoin Cash split on 15 November 2018, its scheduled upgrade day [btk-bsv]. The last common block, 556,766, was mined by SVPool; the first BSV-only block, 556,767, followed 25 minutes later [btk-bsv]. Bitcoin Cash activated Canonical Transaction Ordering (CTOR) and OP_CHECKDATASIG that hour, while BSV rejected CTOR, restored four opcodes and set a 128 MB default [btk-bsv].", "aliases": "hash war 2018 bsv bch split", "refs": ["btk-bsv"], "url": "/wiki/bch-bsv-hash-war/"}, {"id": "bch-bsv-hash-war#39", "slug": "bch-bsv-hash-war", "title": "BCH–BSV hash war", "section": "Two camps", "text": "One camp, supported by Roger Ver and Jihan Wu of Bitmain, promoted Bitcoin ABC with 32 MB blocks; the other, led by Craig Wright and Calvin Ayre, put forward Bitcoin SV with 128 MB [wp-bsv]. On split day BCH traded at about $289 and BSV at about $96.50 [wp-bsv]. Exchanges kept the BCH ticker on the ABC chain and listed the other chain as BSV [btk-bsv].", "aliases": "hash war 2018 bsv bch split", "refs": ["btk-bsv", "wp-bsv"], "url": "/wiki/bch-bsv-hash-war/"}, {"id": "bch-bsv-hash-war#40", "slug": "bch-bsv-hash-war", "title": "BCH–BSV hash war", "section": "Accounts on the podcast", "text": "On S17 E39, Kurt Wuckert Jr. said the SV node had no replay protection, leaving the SV side scrambling when the chain split [ep-s17e39-replay]. He described the ABC side as “very dishonest in the way that they came at this hash war” [ep-s17e39-hashwar]. He also recalled ABC pushing a patch mid-war that added a rolling checkpoint, which he remembered as every 10 blocks; this detail is his recollection and is not verified here [ep-s17e39-checkpoint].", "aliases": "hash war 2018 bsv bch split", "refs": ["ep-s17e39-checkpoint", "ep-s17e39-hashwar", "ep-s17e39-replay"], "url": "/wiki/bch-bsv-hash-war/"}, {"id": "bch-bsv-hash-war#41", "slug": "bch-bsv-hash-war", "title": "BCH–BSV hash war", "section": "Aftermath", "text": "Binance delisted BSV in April 2019, with Kraken, ShapeShift and Blockchain.com following within days [btk-bsv].", "aliases": "hash war 2018 bsv bch split", "refs": ["btk-bsv"], "url": "/wiki/bch-bsv-hash-war/"}, {"id": "big-bitcoin#infobox", "slug": "big-bitcoin", "title": "Big Bitcoin (BBC)", "section": "Summary and infobox", "text": "A February 2018 fork listed at block 508,888 and 1 BTC = 10 BBC, for which no source code was found. Fork height: 508,888 [bth-review]; Block 508,888 time: 2018-02-12 22:26:22 UTC [btc-508888]; Ratio: 1 BTC = 10 BBC [bth-review]; Website: bigbitcoins.org [bth-review]; Source code: “no source code available” [bth-review]", "aliases": "bbc big", "refs": ["btc-508888", "bth-review"], "url": "/wiki/big-bitcoin/"}, {"id": "big-bitcoin#takeover", "slug": "big-bitcoin", "title": "Big Bitcoin (BBC)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Big Bitcoin is a line in a list and little else, which is itself the record: by 2018 a fork could exist as a name, a ratio and a block number. [bth-review]", "aliases": "bbc big", "refs": ["bth-review"], "url": "/wiki/big-bitcoin/"}, {"id": "big-bitcoin#44", "slug": "big-bitcoin", "title": "Big Bitcoin (BBC)", "section": "Record", "text": "The only source this wiki has is the Bitcointalk list of reviewed forks, which gives “Big Bitcoin (BBC) (1 BTC = 10 BBC)”, “fork at 508888”, the site bigbitcoins.org and “no source code available” [bth-review]. Block 508,888 was mined on 12 February 2018 [btc-508888]. The Wayback Machine has no capture of that site for early 2018, so its claims are unknown here [bth-review].", "aliases": "bbc big", "refs": ["btc-508888", "bth-review"], "url": "/wiki/big-bitcoin/"}, {"id": "bip-110#infobox", "slug": "bip-110", "title": "BIP-110 (Reduced Data Temporary Softfork)", "section": "Summary and infobox", "text": "The 2025 proposal for a one-year soft fork limiting data fields, with a 55% threshold and mandatory signalling, whose 2026 enforcement split Knots nodes from Bitcoin. Title: Reduced Data Temporary Softfork [bip110]; Author: Dathon Ohm [bip110]; Assigned: 2025-12-03 [bip110]; Status: Closed [bip110]; Threshold: 1109/2016 (55%), bit 4 [bip110]; Mandatory signalling: Blocks 961632–963647 [bip110]; Duration: 52416 blocks (~1 year) [bip110]; Split: Block 961,632, 8 Aug 2026 [btk-blake]", "aliases": "bip110 reduced data dathon ohm", "refs": ["bip110", "btk-blake"], "url": "/wiki/bip-110/"}, {"id": "bip-110#takeover", "slug": "bip-110", "title": "BIP-110 (Reduced Data Temporary Softfork)", "section": "Takeover view (editorial opinion)", "text": "Vlad predicted on S17 E17 that a Knots fork would let the market price BIP-110's ideas; on S17 E42 Bob Summerwill described the result grinding to a halt. [ep-s17e17-bip110] [ep-s17e42-stall]", "aliases": "bip110 reduced data dathon ohm", "refs": ["ep-s17e17-bip110", "ep-s17e42-stall"], "url": "/wiki/bip-110/"}, {"id": "bip-110#47", "slug": "bip-110", "title": "BIP-110 (Reduced Data Temporary Softfork)", "section": "Proposal", "text": "BIP-110, “Reduced Data Temporary Softfork”, lists Dathon Ohm as author and was assigned on 2025-12-03; its status in the BIPs repository is Closed [bip110]. Its abstract proposes to “Temporarily limit the size of data fields at the consensus level” [bip110]. The rules include invalidating new output scripts over 34 bytes (83 for OP_RETURN), pushes and witness items over 256 bytes, the Taproot annex, and Tapscripts with OP_SUCCESS or executed OP_IF [bip110].", "aliases": "bip110 reduced data dathon ohm", "refs": ["bip110"], "url": "/wiki/bip-110/"}, {"id": "bip-110#48", "slug": "bip-110", "title": "BIP-110 (Reduced Data Temporary Softfork)", "section": "Deployment", "text": "UTXOs created before activation are exempt, and the rules expire after an active_duration of 52416 blocks, “~1 year after activation” [bip110]. The deployment uses a modified BIP9 with a threshold of 1109/2016 (55%), a max_activation_height of 965664 and mandatory signalling of bit 4 in blocks 961632 to 963647, during which non-signalling blocks are rejected [bip110].", "aliases": "bip110 reduced data dathon ohm", "refs": ["bip110"], "url": "/wiki/bip-110/"}, {"id": "bip-110#49", "slug": "bip-110", "title": "BIP-110 (Reduced Data Temporary Softfork)", "section": "The split", "text": "Knots nodes enforcing BIP-110 began rejecting non-signalling blocks at height 961,632 on 8 August 2026, which split them from Bitcoin [btk-blake]. The minority SHA-256d chain then produced eight blocks in 22 days and became Bitcoin BLAKE2b [btk-blake]. Bob Summerwill described that chain grinding to a halt on S17 E42 [ep-s17e42-stall].", "aliases": "bip110 reduced data dathon ohm", "refs": ["btk-blake", "ep-s17e42-stall"], "url": "/wiki/bip-110/"}, {"id": "bip9-version-bits#infobox", "slug": "bip9-version-bits", "title": "BIP9 (version bits)", "section": "Summary and infobox", "text": "The 2015 mechanism that lets miners signal for several soft forks in parallel using bits of the block version, with a 95% threshold and a timeout. Authors: Pieter Wuille, Peter Todd, Greg Maxwell, Rusty Russell [bip9]; Assigned: 4 October 2015 [bip9]; Threshold: 1,916 of 2,016 blocks (95%) [bip9]; States: DEFINED, STARTED, LOCKED_IN, ACTIVE, FAILED [bip9]; Version prefix: Top three bits 001 [bip9]; Used for: CSV, SegWit; a variant (Speedy Trial) for Taproot [btk-allforks]", "aliases": "bip9 version bits signalling signaling threshold 95%", "refs": ["bip9", "btk-allforks"], "url": "/wiki/bip9-version-bits/"}, {"id": "bip9-version-bits#takeover", "slug": "bip9-version-bits", "title": "BIP9 (version bits)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: BIP9 assumed miners would signal for upgrades that users wanted. SegWit broke that assumption, and the BIP91 and BIP148 workarounds that rescued it are why later activation debates were so bitter. [btk-allforks] [bip148]", "aliases": "bip9 version bits signalling signaling threshold 95%", "refs": ["bip148", "btk-allforks"], "url": "/wiki/bip9-version-bits/"}, {"id": "bip9-version-bits#52", "slug": "bip9-version-bits", "title": "BIP9 (version bits)", "section": "Mechanism", "text": "BIP-9 treats the block version field “as a bit vector, where each bit can be used to track an independent change”, tallied every retarget period, so several soft forks can be deployed at once [bip9]. Each deployment has a bit, a start time and a timeout, and moves through the states DEFINED, STARTED, LOCKED_IN, ACTIVE and FAILED [bip9]. Lock-in requires at least 1,916 of 2,016 blocks (95%) to set the bit, and signalling blocks must have 001 as their top three version bits [bip9].", "aliases": "bip9 version bits signalling signaling threshold 95%", "refs": ["bip9"], "url": "/wiki/bip9-version-bits/"}, {"id": "bip9-version-bits#53", "slug": "bip9-version-bits", "title": "BIP9 (version bits)", "section": "Why it replaced version numbers", "text": "BIP-9 explains that earlier upgrades such as BIP-34, BIP-66 and BIP-65 raised the version number, which “permanently restricts the set of allowed nVersion field values” [bip9]. Pieter Wuille, Peter Todd, Greg Maxwell and Rusty Russell are its authors [bip9].", "aliases": "bip9 version bits signalling signaling threshold 95%", "refs": ["bip9"], "url": "/wiki/bip9-version-bits/"}, {"id": "bip9-version-bits#54", "slug": "bip9-version-bits", "title": "BIP9 (version bits)", "section": "SegWit and Taproot", "text": "Bitcoin Takeover's soft-fork table lists SegWit on BIP9 bit 1, “pushed over the line by BIP91 and BIP148” [btk-allforks]. BIP-91 had miners reject blocks that did not signal, with an 80% threshold over 336 blocks [bip91]. Taproot used Speedy Trial, a BIP9 variant with a 90% threshold and a minimum activation height [core-0211]. BIP-8 proposed heights instead of times and an optional forced lock-in [bip8]. See UASF / BIP148 and Taproot activation.", "aliases": "bip9 version bits signalling signaling threshold 95%", "refs": ["bip8", "bip91", "btk-allforks", "core-0211"], "url": "/wiki/bip9-version-bits/"}, {"id": "bip91#infobox", "slug": "bip91", "title": "BIP-91 (reduced-threshold SegWit signalling)", "section": "Summary and infobox", "text": "James Hilliard's 2017 miner-enforced bridge: an 80% vote over 336 blocks that made miners reject blocks not signalling SegWit, letting the original 95% deployment lock in. Author: James Hilliard [bip91]; Created: 2017-05-22 [bw-bip91]; Threshold: 269 of 336 blocks (80%), bit 4 “segsignal” [bip91]; Window: 1 Jun – 15 Nov 2017 [bip91]; Locked in / active: 21 July / 26 July 2017 [btk-forkwars]", "aliases": "bip91 bip-91 segsignal hilliard masf", "refs": ["bip91", "btk-forkwars", "bw-bip91"], "url": "/wiki/bip91/"}, {"id": "bip91#takeover", "slug": "bip91", "title": "BIP-91 (reduced-threshold SegWit signalling)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: BIP-91 was the face-saving mechanism of 2017 — miners could say they had activated SegWit on their own terms while the UASF deadline did the pushing. [btk-forkwars] [bip148]", "aliases": "bip91 bip-91 segsignal hilliard masf", "refs": ["bip148", "btk-forkwars"], "url": "/wiki/bip91/"}, {"id": "bip91#57", "slug": "bip91", "title": "BIP-91 (reduced-threshold SegWit signalling)", "section": "Mechanism", "text": "BIP-91, “Reduced threshold Segwit MASF”, is authored by James Hilliard [bip91]. While active, it requires all blocks to signal the existing SegWit deployment (bit 1); “Blocks that do not signal as required will be rejected” [bip91]. It is deployed with version bits under the name “segsignal” on bit 4, with an 80% threshold of 269 blocks in a 336-block window, starting on 1 June 2017 and timing out on 15 November 2017 [bip91]. The Bitcoin Wiki copy gives its creation date as 2017-05-22 [bw-bip91].", "aliases": "bip91 bip-91 segsignal hilliard masf", "refs": ["bip91", "bw-bip91"], "url": "/wiki/bip91/"}, {"id": "bip91#58", "slug": "bip91", "title": "BIP-91 (reduced-threshold SegWit signalling)", "section": "2017", "text": "Bitcoin Takeover's Fork Wars timeline says “BIP 91 locked in on 21 July 2017 and activated on 26 July”, after which the original BIP-9 SegWit threshold could be met; SegWit locked in on 9 August and activated on 24 August at block 481,824 [btk-forkwars]. The forks overview calls BIP-91 a “Miner-enforced bridge” [btk-allforks]. It ran alongside BIP-148, which had nodes reject non-signalling blocks from 1 August 2017 [bip148].", "aliases": "bip91 bip-91 segsignal hilliard masf", "refs": ["bip148", "btk-allforks", "btk-forkwars"], "url": "/wiki/bip91/"}, {"id": "bip91#59", "slug": "bip91", "title": "BIP-91 (reduced-threshold SegWit signalling)", "section": "Hilliard", "text": "The February 2016 Hong Kong Roundtable statement lists “James Hilliard Pool/Farm Admin BitmainWarranty” among its signers [hk-letter].", "aliases": "bip91 bip-91 segsignal hilliard masf", "refs": ["hk-letter"], "url": "/wiki/bip91/"}, {"id": "bitclassic-coin#infobox", "slug": "bitclassic-coin", "title": "Bitclassic Coin (BICC)", "section": "Summary and infobox", "text": "A Chinese-team fork (比特币金典) moving to 8MB blocks at a height its own site gives as 499,888; forkdrop gives 498,888. Fork height: 499,888 (site, 2019 list); 498,888 (forkdrop) [bicc-site]; Block 499,888 time: 2017-12-18 02:55:58 UTC [btc-499888]; Block size: 8MB [bicc-site]; Max supply (forkdrop): 21,200,000 [fd-data]; Status (Feb 2019 list): “doesn't seem to exist (anymore)” [bth-review]", "aliases": "bicc bitclassic 比特币金典 8mb", "refs": ["bicc-site", "btc-499888", "bth-review", "fd-data"], "url": "/wiki/bitclassic-coin/"}, {"id": "bitclassic-coin#takeover", "slug": "bitclassic-coin", "title": "Bitclassic Coin (BICC)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: the sources disagree on Bitclassic's fork height by a thousand blocks, and the site's own roadmap date does not match either block. [bicc-site] [fd-data]", "aliases": "bicc bitclassic 比特币金典 8mb", "refs": ["bicc-site", "fd-data"], "url": "/wiki/bitclassic-coin/"}, {"id": "bitclassic-coin#62", "slug": "bitclassic-coin", "title": "Bitclassic Coin (BICC)", "section": "Pitch", "text": "The archived site says the block size “changed from 1M to 8M”, promising faster and cheaper transfers [bicc-site]. Its roadmap lists “2018-01-08 Hard fork At a height of 499888, extend 8M block” and a later zero-knowledge-proof upgrade [bicc-site]. The README is the stock Bitcoin Core text with the name changed to BitClassic coin [bicc-readme].", "aliases": "bicc bitclassic 比特币金典 8mb", "refs": ["bicc-readme", "bicc-site"], "url": "/wiki/bitclassic-coin/"}, {"id": "bitclassic-coin#63", "slug": "bitclassic-coin", "title": "Bitclassic Coin (BICC)", "section": "Record", "text": "The 2019 fork list also gives a fork at 499888 and says it “doesn't seem to exist (anymore)” [bth-review]. Block 499,888 was mined on 18 December 2017, not 8 January 2018 [btc-499888]. forkdrop's data file instead gives block 498888 and a date of 2017-12-12, with a maximum supply of 21,200,000 [fd-data]. Which height the chain used is unverified [fd-data].", "aliases": "bicc bitclassic 比特币金典 8mb", "refs": ["btc-499888", "bth-review", "fd-data"], "url": "/wiki/bitclassic-coin/"}, {"id": "bitcoin-2#infobox", "slug": "bitcoin-2", "title": "Bitcoin 2 (BTC2)", "section": "Summary and infobox", "text": "A proof-of-stake snapshot fork of Bitcoin balances at block 507,850, with masternodes and Zerocoin-based zBTC2 privacy; a 2019 review found it running. Snapshot height: 507,850 [btc2-readme]; Block 507,850 time: 2018-02-05 21:16:26 UTC [btc-507850]; Ratio: 1:1 [btc2-ann]; Consensus: Proof of stake [btc2-readme]; Privacy: zBTC2 [btc2-readme]; SegWit: Not supported [btc2-readme]; Status (Feb 2019 list): “seems to be working, 1.2 GB” [bth-review]", "aliases": "btc2 bitcoin2 zbtc2 masternodes", "refs": ["btc-507850", "btc2-ann", "btc2-readme", "bth-review"], "url": "/wiki/bitcoin-2/"}, {"id": "bitcoin-2#takeover", "slug": "bitcoin-2", "title": "Bitcoin 2 (BTC2)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin 2 kept Bitcoin's balances and dropped nearly everything else — mining, SegWit and the history — which is why the snapshot forks sit at the edge of the lineage map. [btc2-readme]", "aliases": "btc2 bitcoin2 zbtc2 masternodes", "refs": ["btc2-readme"], "url": "/wiki/bitcoin-2/"}, {"id": "bitcoin-2#66", "slug": "bitcoin-2", "title": "Bitcoin 2 (BTC2)", "section": "Snapshot", "text": "The README says “the balances of Bitcoin as of block 507850 were recorded to it”, while the chain itself was only about 1.5 GB [btc2-readme]. Block 507,850 was mined on 5 February 2018 [btc-507850]. The 2019 fork list calls it a snapshot fork and quotes the project: “the blockchain data will be pruned from over 150 GB to around 2 GB” [bth-review]. The announcement thread, opened by jackleszz on 3 February 2018, is titled “[BTC2] Bitcoin 2, BTC Fork 1:1, PoS” [btc2-ann].", "aliases": "btc2 bitcoin2 zbtc2 masternodes", "refs": ["btc-507850", "btc2-ann", "btc2-readme", "bth-review"], "url": "/wiki/bitcoin-2/"}, {"id": "bitcoin-2#67", "slug": "bitcoin-2", "title": "Bitcoin 2 (BTC2)", "section": "Design", "text": "Bitcoin 2 “uses a custom, secure Proof of Stake algorithm”, has masternodes for its Swift TX feature, offers zBTC2 coin mixing and makes blocks about once per minute [btc2-readme]. It “does not support Segwit or the Bech32 address format” [btc2-readme]. The fork list's 26 February 2019 status says it “seems to be working, 1.2 GB” [bth-review].", "aliases": "btc2 bitcoin2 zbtc2 masternodes", "refs": ["btc2-readme", "bth-review"], "url": "/wiki/bitcoin-2/"}, {"id": "bitcoin-abc#infobox", "slug": "bitcoin-abc", "title": "Bitcoin ABC", "section": "Summary and infobox", "text": "Amaury Séchet's “Adjustable Blocksize Cap” client, which launched Bitcoin Cash in August 2017 and became eCash's node after the 2020 split. Name: ABC: Adjustable Blocksize Cap [wp-bsv]; Lead developer: Amaury Séchet (deadalnix) [ep-s17e19-abc]; Codebase: Its own fork of Bitcoin Core, not of XT, Classic or Unlimited [ep-s17e19-abc]; Introduced: June 2017, at a conference [wp-bch]; UAHF activation: Median time past 1501590000 (1 August 2017) [uahf-spec]; Initial limit: Fork block size at least 8,000,000 bytes [uahf-spec]; After Nov 2020: Node software of eCash (XEC) [btk-xec]", "aliases": "abc adjustable blocksize cap uahf", "refs": ["btk-xec", "ep-s17e19-abc", "uahf-spec", "wp-bch", "wp-bsv"], "url": "/wiki/bitcoin-abc/"}, {"id": "bitcoin-abc#takeover", "slug": "bitcoin-abc", "title": "Bitcoin ABC", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: ABC is a rare case of a client becoming its own chain. It wrote Bitcoin Cash's first rules, lost the BCH ticker over its funding rule in 2020, and carried on as eCash. [btk-xec] [ep-s17e19-ifp]", "aliases": "abc adjustable blocksize cap uahf", "refs": ["btk-xec", "ep-s17e19-ifp"], "url": "/wiki/bitcoin-abc/"}, {"id": "bitcoin-abc#70", "slug": "bitcoin-abc", "title": "Bitcoin ABC", "section": "Origin", "text": "The first software implementation of the Bitcoin Cash fork was introduced under the name Bitcoin ABC during a conference in June 2017, the same month Bitmain called a bigger-block hard fork a “contingency plan” [wp-bch]. ABC stands for Adjustable Blocksize Cap [wp-bsv]. On S17 E19, Amaury Séchet said ABC was its own fork of Bitcoin Core rather than a descendant of XT, Classic or Unlimited [ep-s17e19-abc].", "aliases": "abc adjustable blocksize cap uahf", "refs": ["ep-s17e19-abc", "wp-bch", "wp-bsv"], "url": "/wiki/bitcoin-abc/"}, {"id": "bitcoin-abc#71", "slug": "bitcoin-abc", "title": "Bitcoin ABC", "section": "UAHF", "text": "ABC's user-activated hard fork specification set a default activation time of 1501590000, the median time past corresponding to 1 August 2017 [uahf-spec]. It required the fork block size limit to be configured to at least 8,000,000 bytes [uahf-spec]. Alongside it, the Bitcoin Cash specification defined a SIGHASH_FORKID signature digest so that transactions could not be replayed across the split [rp-sighash].", "aliases": "abc adjustable blocksize cap uahf", "refs": ["rp-sighash", "uahf-spec"], "url": "/wiki/bitcoin-abc/"}, {"id": "bitcoin-abc#72", "slug": "bitcoin-abc", "title": "Bitcoin ABC", "section": "The 2018 and 2020 splits", "text": "In November 2018 the ABC camp, backed by Roger Ver and Jihan Wu of Bitmain, kept a 32 MB block size while the Bitcoin SV camp pushed 128 MB [wp-bsv]. In November 2020 ABC's 8% coinbase rule split it from the rest of Bitcoin Cash, and its chain traded as BCHA before being renamed eCash [btk-xec].", "aliases": "abc adjustable blocksize cap uahf", "refs": ["btk-xec", "wp-bsv"], "url": "/wiki/bitcoin-abc/"}, {"id": "bitcoin-air#infobox", "slug": "bitcoin-air", "title": "Bitcoin Air (XAP)", "section": "Summary and infobox", "text": "A Bitcoin + Peercoin merge airdrop with a Thanksgiving 2018 snapshot, hybrid PoS/PoW and a carbon-credit-backed stablecoin side-chain plan. Snapshot: 22 November 2018 (Thanksgiving) [xap-site]; Snapshot block (forkdrop): 551,000 [fd-data]; Block 551,000 time: 2018-11-21 23:50:39 UTC [btc-551000]; Source coins: Bitcoin and Peercoin [xap-site]; Supply: 21M in circulation + 42M tail emission [xap-site]; Block: 4 minutes, 16MB, 12.5 XAP [xap-site]", "aliases": "xap air peercoin carbon usdap", "refs": ["btc-551000", "fd-data", "xap-site"], "url": "/wiki/bitcoin-air/"}, {"id": "bitcoin-air#takeover", "slug": "bitcoin-air", "title": "Bitcoin Air (XAP)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Air is a two-parent airdrop, mixing Bitcoin's holder base with Peercoin's consensus, and it says it is not tied to Peercoin's teams. [xap-site]", "aliases": "xap air peercoin carbon usdap", "refs": ["xap-site"], "url": "/wiki/bitcoin-air/"}, {"id": "bitcoin-air#75", "slug": "bitcoin-air", "title": "Bitcoin Air (XAP)", "section": "Design", "text": "The archived site, captured on 27 October 2018, calls Bitcoin Air “a bilateral merge fork between Bitcoin ($BTC) and Peercoin ($PPC)” and says the team was still discussing adding Bitcoin Cash [xap-site]. It says it combines Bitcoin's user base “with the environmental and user-friendly consensus method of Peercoin” and plans a stable side-chain backed by carbon credits [xap-site]. Its listed specifications include 21,000,000 XAP in circulation, a 42,000,000 XAP tail emission, hybrid PoS/PoW, a four-minute block time and 16MB blocks [xap-site]. It adds: “We are in no way associated with the Peercoin Foundation, Peercoin Development Team, or Peercoin Community Team.” [xap-site]", "aliases": "xap air peercoin carbon usdap", "refs": ["xap-site"], "url": "/wiki/bitcoin-air/"}, {"id": "bitcoin-air#76", "slug": "bitcoin-air", "title": "Bitcoin Air (XAP)", "section": "Record", "text": "The site set “Thanksgiving Day, November 22nd, 2018” as the snapshot date [xap-site]. forkdrop's data file gives block 551000 and a maximum supply of 41,000,000 [fd-data]. Block 551,000 was mined late on 21 November 2018 UTC [btc-551000]. The Bitcointalk thread was opened by its bounty manager on 4 October 2018 [xap-ann]. Its state after early 2019 is unknown [fd-data].", "aliases": "xap air peercoin carbon usdap", "refs": ["btc-551000", "fd-data", "xap-ann", "xap-site"], "url": "/wiki/bitcoin-air/"}, {"id": "bitcoin-all#infobox", "slug": "bitcoin-all", "title": "Bitcoin ALL (BTA)", "section": "Summary and infobox", "text": "A Chinese-language December 2017 project (比特币荣耀) planning snapshots at block 498,960 and on 1 January 2018, AuxPoW mining and user voting; no source code was found. First snapshot: Block 498,960 (planned ≈13 Dec 2017) [bta-site]; Block 498,960 time: 2017-12-12 21:39:19 UTC [btc-498960]; Second snapshot: Timestamp 1514736000 (1 Jan 2018), block 501,906 [bta-site]; Mining: AuxPoW (merged mining), planned [bta-site]; Source code: None available (2019 list) [bth-review]", "aliases": "bta btall bitcoin all 比特币荣耀 auxpow potx", "refs": ["bta-site", "btc-498960", "bth-review"], "url": "/wiki/bitcoin-all/"}, {"id": "bitcoin-all#takeover", "slug": "bitcoin-all", "title": "Bitcoin ALL (BTA)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin ALL planned two snapshots and promised to unfreeze each holder's coins by the smaller of the two balances. [bta-site]", "aliases": "bta btall bitcoin all 比特币荣耀 auxpow potx", "refs": ["bta-site"], "url": "/wiki/bitcoin-all/"}, {"id": "bitcoin-all#79", "slug": "bitcoin-all", "title": "Bitcoin ALL (BTA)", "section": "Plan", "text": "The archived Chinese site, captured on 27 March 2018, lays out a roadmap: a first snapshot at block height 498960 around 13 December 2017, and a second at timestamp 1514736000 on 1 January 2018, which it maps to block 501906 [bta-site]. Block 498,960 was mined on 12 December 2017 [btc-498960]. Holders would get BTA 1:1 against their BTC balance, frozen at first and released according to the smaller of the two snapshots [bta-site]. The site promises AuxPoW mining, zero premine and a transaction-voting scheme it calls PoTX [bta-site].", "aliases": "bta btall bitcoin all 比特币荣耀 auxpow potx", "refs": ["bta-site", "btc-498960"], "url": "/wiki/bitcoin-all/"}, {"id": "bitcoin-all#80", "slug": "bitcoin-all", "title": "Bitcoin ALL (BTA)", "section": "Record", "text": "The 2019 fork list gives a fork at 498960, notes the site is “only in Chinese”, and says “no source code available” [bth-review]. forkdrop's data file lists fork block and date as N/A and marks the coin not live [fd-data]. Whether a chain ever ran is unknown [fd-data].", "aliases": "bta btall bitcoin all 比特币荣耀 auxpow potx", "refs": ["bth-review", "fd-data"], "url": "/wiki/bitcoin-all/"}, {"id": "bitcoin-atom#infobox", "slug": "bitcoin-atom", "title": "Bitcoin Atom", "section": "Summary and infobox", "text": "A January 2018 SegWit-enabled fork built around on-chain atomic swaps and hybrid proof of stake. Fork height: Block 505,888, 24 January 2018 [bca-readme]; Fork time: Bitcoin block 505,888, header time 24 January 2018 14:26:41 UTC [btc-505888]; Codebase: Forked from Bitcoin Core and kept in sync with it [bca-readme]; Features: SegWit, hash time-locked contracts and an HTLC API [bca-readme]; Consensus: Hybrid: proof-of-stake block minting enabled by default [bca-readme]", "aliases": "bca atomic swaps", "refs": ["bca-readme", "btc-505888"], "url": "/wiki/bitcoin-atom/"}, {"id": "bitcoin-atom#takeover", "slug": "bitcoin-atom", "title": "Bitcoin Atom", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Atom pitched itself as an exchange-free swap coin, the opposite of the exchange-listing frenzy that most airdrop forks of its month depended on. [bca-readme]", "aliases": "bca atomic swaps", "refs": ["bca-readme"], "url": "/wiki/bitcoin-atom/"}, {"id": "bitcoin-atom#83", "slug": "bitcoin-atom", "title": "Bitcoin Atom", "section": "Launch", "text": "According to its README, the Bitcoin Atom fork took place at block 505,888 on 24 January 2018 [bca-readme]. Bitcoin block 505,888 has a header time of 24 January 2018, 14:26:41 UTC [btc-505888].", "aliases": "bca atomic swaps", "refs": ["bca-readme", "btc-505888"], "url": "/wiki/bitcoin-atom/"}, {"id": "bitcoin-atom#84", "slug": "bitcoin-atom", "title": "Bitcoin Atom", "section": "Design", "text": "The README describes a SegWit-enabled Bitcoin fork with on-chain atomic swaps using hash time-locked contracts and its own HTLC API [bca-readme]. It supports a hybrid consensus in which proof-of-stake block minting is enabled by default, letting holders earn transaction fees [bca-readme]. Its codebase is forked from Bitcoin Core and, per the README, kept in sync with it [bca-readme].", "aliases": "bca atomic swaps", "refs": ["bca-readme"], "url": "/wiki/bitcoin-atom/"}, {"id": "bitcoin-blake2b#infobox", "slug": "bitcoin-blake2b", "title": "Bitcoin BLAKE2b (XBT / BTCB2)", "section": "Summary and infobox", "text": "The 2026 fork that grew out of Luke Dashjr's BIP-110 anti-spam soft fork and replaced SHA-256d with BLAKE2b. Sold as XBT on some venues. Names: Bitcoin BLAKE2b, Bitcoin BIP110, BTCB2, XBT (venue-dependent) [btk-blake]; Type: UTXO hard fork of Bitcoin, new proof of work [blake-dev]; Last common block: 961,631, 8 August 2026 [btk-blake]; SHA-256d stall: Eight blocks (961,632–961,639) in 22 days [btk-blake]; First BLAKE2b block: 961,640, 30 August 2026 [blake-dev]; Proof of work: BLAKE2b, 164-byte version-2 header [btk-blake]; Temporary rules: Reduced-data rules and 800,000 WU cap until 1 Sep 2027 [blake-dev]; Client: Bitcoin Knots 29.4.1.knots20260508 [knots-2941]; Key figure: Luke Dashjr [btk-blake]; Market cap: unknown — not tracked by CoinGecko or CoinMarketCap [btk-blake]", "aliases": "xbt btcb2 bip110 knots blake2b luke", "refs": ["blake-dev", "btk-blake", "knots-2941"], "url": "/wiki/bitcoin-blake2b/"}, {"id": "bitcoin-blake2b#takeover", "slug": "bitcoin-blake2b", "title": "Bitcoin BLAKE2b (XBT / BTCB2)", "section": "Takeover view (editorial opinion)", "text": "Vlad's verdict in the magazine: the youngest and most volatile chain in the issue, and the only one that began as an attempt to make Bitcoin smaller. The XBT ticker is an operational hazard because Kraken has long used XBT for Bitcoin itself. [btk-blake] [bmd-advisory]", "aliases": "xbt btcb2 bip110 knots blake2b luke", "refs": ["bmd-advisory", "btk-blake"], "url": "/wiki/bitcoin-blake2b/"}, {"id": "bitcoin-blake2b#87", "slug": "bitcoin-blake2b", "title": "Bitcoin BLAKE2b (XBT / BTCB2)", "section": "From soft fork to hard fork", "text": "The chain began as BIP-110, a soft fork to restrict arbitrary data on Bitcoin [bip110]. Activation split the chain at block 961,632 on 8 August 2026, the first block of BIP-110's mandatory signalling period; the SHA-256d side then produced only eight blocks in 22 days [btk-blake]. Bob Summerwill described the minority chain grinding to a halt on S17 E42 [ep-s17e42-stall].", "aliases": "xbt btcb2 bip110 knots blake2b luke", "refs": ["bip110", "btk-blake", "ep-s17e42-stall"], "url": "/wiki/bitcoin-blake2b/"}, {"id": "bitcoin-blake2b#88", "slug": "bitcoin-blake2b", "title": "Bitcoin BLAKE2b (XBT / BTCB2)", "section": "New proof of work", "text": "The project then switched proof of work from SHA-256d to BLAKE2b; the first BLAKE2b block was 961,640 on 30 August 2026 [blake-dev]. The project's developer page says it is not BIP-110 itself, which was a soft fork, but a hard fork that changed the proof of work so existing SHA-256d miners cannot produce valid blocks [blake-dev]. The algorithm was chosen by a lottery using the last hex digits of Testnet4 blocks [btk-blake].", "aliases": "xbt btcb2 bip110 knots blake2b luke", "refs": ["blake-dev", "btk-blake"], "url": "/wiki/bitcoin-blake2b/"}, {"id": "bitcoin-blake2b#89", "slug": "bitcoin-blake2b", "title": "Bitcoin BLAKE2b (XBT / BTCB2)", "section": "Temporary data limits", "text": "Reduced-data rules and an 800,000 weight unit cap (about 300 kB) apply until the previous block's median time past reaches 1 September 2027 [blake-dev].", "aliases": "xbt btcb2 bip110 knots blake2b luke", "refs": ["blake-dev"], "url": "/wiki/bitcoin-blake2b/"}, {"id": "bitcoin-blake2b#90", "slug": "bitcoin-blake2b", "title": "Bitcoin BLAKE2b (XBT / BTCB2)", "section": "Names and the XBT problem", "text": "The same asset trades as XBT, BTCB2 and BIP110 on different small venues [btk-blake]. XBT has long been used for Bitcoin itself on platforms such as Kraken, so a media advisory asked outlets to identify the fork by network, not ticker [bmd-advisory].", "aliases": "xbt btcb2 bip110 knots blake2b luke", "refs": ["bmd-advisory", "btk-blake"], "url": "/wiki/bitcoin-blake2b/"}, {"id": "bitcoin-blake2b#91", "slug": "bitcoin-blake2b", "title": "Bitcoin BLAKE2b (XBT / BTCB2)", "section": "People", "text": "Luke Dashjr, maintainer of Bitcoin Knots, is credited on BIP-110 and authored the BLAKE2b header, the activation headline and the coinbase maturity rule [btk-blake]. On S17 E17, months before the split, Vlad predicted a Knots fork would let the market price BIP-110's ideas [ep-s17e17-bip110].", "aliases": "xbt btcb2 bip110 knots blake2b luke", "refs": ["btk-blake", "ep-s17e17-bip110"], "url": "/wiki/bitcoin-blake2b/"}, {"id": "bitcoin-blvck#infobox", "slug": "bitcoin-blvck", "title": "BTC BLVCK (BTCV)", "section": "Summary and infobox", "text": "A CryptoNight fork announced for block 507,777 with 21 million forked coins plus a 2.1 million coin presale. Fork height: 507,777 [btcv-ann]; Block 507,777 time: 2018-02-05 12:58:13 UTC [btc-507777]; Algorithm: CryptoNight [btcv-ann]; Supply: 21M forked + 2.1M additional coin offer [btcv-ann]; forkdrop reason: “Homepage Down” [fd-data]", "aliases": "btcv blvck black cryptonight", "refs": ["btc-507777", "btcv-ann", "fd-data"], "url": "/wiki/bitcoin-blvck/"}, {"id": "bitcoin-blvck#takeover", "slug": "bitcoin-blvck", "title": "BTC BLVCK (BTCV)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: BTC BLVCK sold 10% extra coins in a presale on top of the 1:1 fork. [btcv-ann]", "aliases": "btcv blvck black cryptonight", "refs": ["btcv-ann"], "url": "/wiki/bitcoin-blvck/"}, {"id": "bitcoin-blvck#94", "slug": "bitcoin-blvck", "title": "BTC BLVCK (BTCV)", "section": "Record", "text": "The announcement of 28 December 2017 gives “11 February on BTC Block 507777” as the fork, with the CryptoNight algorithm, six-minute blocks and blocks up to 8MB [btcv-ann]. It lists a fork emission of 21,000,000 and an additional coin offer of 2,100,000, for 23,100,000 in total [btcv-ann]. Block 507,777 was mined on 5 February 2018, not 11 February [btc-507777]. forkdrop's data file uses 2018-02-05 and files the coin among historic entries with the reason “Homepage Down” [fd-data].", "aliases": "btcv blvck black cryptonight", "refs": ["btc-507777", "btcv-ann", "fd-data"], "url": "/wiki/bitcoin-blvck/"}, {"id": "bitcoin-boy#infobox", "slug": "bitcoin-boy", "title": "Bitcoin Boy (BCB)", "section": "Summary and infobox", "text": "A fork at block 502,233 promising huge blocks, Lua smart contracts and voting, at 100 BCB per BTC by forkdrop's data. Fork height: 502,233 [bcb-site]; Block 502,233 time: 2018-01-02 16:30:22 UTC [btc-502233]; Ratio (forkdrop): 100:1 [fd-data]; Max supply (forkdrop): 2.31 Billion [fd-data]", "aliases": "bcb boy", "refs": ["bcb-site", "btc-502233", "fd-data"], "url": "/wiki/bitcoin-boy/"}, {"id": "bitcoin-boy#takeover", "slug": "bitcoin-boy", "title": "Bitcoin Boy (BCB)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Boy's code repository holds only a one-line README pointing at its website. [bcb-readme]", "aliases": "bcb boy", "refs": ["bcb-readme"], "url": "/wiki/bitcoin-boy/"}, {"id": "bitcoin-boy#97", "slug": "bitcoin-boy", "title": "Bitcoin Boy (BCB)", "section": "Record", "text": "The archived site, captured on 8 April 2018, says the snapshot and fork would happen “when the bitcoins reach to the height of 502,233 in the blockchain” [bcb-site]. It promises a bigger block, a Lua smart-contract system and a voting function [bcb-site]. Block 502,233 was mined on 2 January 2018 [btc-502233]. The GitHub README contains only the name and bitcoinboy.org [bcb-readme]. forkdrop's data file gives a 100:1 ratio and a maximum supply of 2.31 Billion [fd-data]. Its state after 2018 is unknown [fd-data].", "aliases": "bcb boy", "refs": ["bcb-readme", "bcb-site", "btc-502233", "fd-data"], "url": "/wiki/bitcoin-boy/"}, {"id": "bitcoin-candy#infobox", "slug": "bitcoin-candy", "title": "Bitcoin Candy (CDY)", "section": "Summary and infobox", "text": "An airdrop fork of Bitcoin Cash: split at BCH block 512,666 in January 2018 with 1,000 CDY per BCH, Equihash mining, 2-minute blocks and a 21 billion supply. Type: Hard fork of Bitcoin Cash with replay protection [cdy-readme]; Fork height: Bitcoin Cash block 512,666 [cdy-chainparams]; Block 512,666 time: 2018-01-12 23:32:52 UTC (13 Jan in Asia) [bch-512666]; Ratio: 1 BCH = 1,000 CDY [cdy-ann]; Proof of work: Equihash [cdy-readme]; Supply: 21 billion at launch; the current website says 22 billion [cdy-site]; Premine: 1% of supply [cdy-ann]", "aliases": "cdy candy", "refs": ["bch-512666", "cdy-ann", "cdy-chainparams", "cdy-readme", "cdy-site"], "url": "/wiki/bitcoin-candy/"}, {"id": "bitcoin-candy#takeover", "slug": "bitcoin-candy", "title": "Bitcoin Candy (CDY)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Candy is the moment the airdrop era turned on Bitcoin Cash itself. Five months after BCH left Bitcoin, someone forked BCH with a quantum-resistance pitch and the slogan “Help Bitcoin (Cash) Great Again”. [cdy-ann] [cdy-readme]", "aliases": "cdy candy", "refs": ["cdy-ann", "cdy-readme"], "url": "/wiki/bitcoin-candy/"}, {"id": "bitcoin-candy#100", "slug": "bitcoin-candy", "title": "Bitcoin Candy (CDY)", "section": "Announcement", "text": "The Bitcointalk announcement of 9 January 2018 said the team would fork Bitcoin Cash at block 512,666 and explore “anti-quantum attacks” on the new chain [cdy-ann]. It listed a two-minute block interval, a 21 billion supply, Equihash GPU mining, no SegWit and a 1% premine, and said BCH holders would receive 1,000 CDY per BCH [cdy-ann].", "aliases": "cdy candy", "refs": ["cdy-ann"], "url": "/wiki/bitcoin-candy/"}, {"id": "bitcoin-candy#101", "slug": "bitcoin-candy", "title": "Bitcoin Candy (CDY)", "section": "The fork", "text": "The Candy client sets cdyHeight to 512,666 and defines a later Equihash-related fork height (CDYEquihashForkHeight) of 656,960 [cdy-chainparams]. Bitcoin Cash block 512,666 has a header time of 23:32:52 UTC on 12 January 2018, which is the morning of 13 January in China [bch-512666]. The README dates the split to 13 January 2018 and says the two chains share their history up to it [cdy-readme].", "aliases": "cdy candy", "refs": ["bch-512666", "cdy-chainparams", "cdy-readme"], "url": "/wiki/bitcoin-candy/"}, {"id": "bitcoin-candy#102", "slug": "bitcoin-candy", "title": "Bitcoin Candy (CDY)", "section": "Later changes", "text": "The current website lists the fork height and date, Equihash(144,5), a 1:1000 distribution, a 1% premine, 32 MB blocks and a supply of 22 billion, a billion more than the launch announcement stated [cdy-site] [cdy-ann]. This wiki has not found a primary source that explains the change in supply, so the reason is unknown [cdy-site].", "aliases": "cdy candy", "refs": ["cdy-ann", "cdy-site"], "url": "/wiki/bitcoin-candy/"}, {"id": "bitcoin-cash-node#infobox", "slug": "bitcoin-cash-node", "title": "Bitcoin Cash Node", "section": "Summary and infobox", "text": "The Bitcoin Cash full-node client that took over from Bitcoin ABC when ABC's funding rule split off in November 2020. Type: Bitcoin Cash full-node client [ep-s17e26-bchn]; Lineage: Renamed from a fork of Bitcoin ABC; a Bitcoin Core lineage codebase [ep-s17e26-bchn]; Role: The node “most people run” on Bitcoin Cash, according to Calin Culianu [ep-s17e26-bchn]; Split: 15 November 2020, when ABC's chain left as BCHA [btk-xec]; Website: bitcoincashnode.org [bchn-site]", "aliases": "bchn", "refs": ["bchn-site", "btk-xec", "ep-s17e26-bchn"], "url": "/wiki/bitcoin-cash-node/"}, {"id": "bitcoin-cash-node#takeover", "slug": "bitcoin-cash-node", "title": "Bitcoin Cash Node", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: BCHN is the answer to “who kept the BCH ticker in 2020”. The magazine and the podcast both frame the split as a fight over a development tax, not over block size. [btk-xec] [ep-s17e26-bchn]", "aliases": "bchn", "refs": ["btk-xec", "ep-s17e26-bchn"], "url": "/wiki/bitcoin-cash-node/"}, {"id": "bitcoin-cash-node#105", "slug": "bitcoin-cash-node", "title": "Bitcoin Cash Node", "section": "From ABC to BCHN", "text": "On S17 E26, Bitcoin Cash developer Calin Culianu described the client's origin: “it was Bitcoin ABC until Amaury decided to charge tax, and then we kicked them out. And then we renamed it to Bitcoin Cash Node, BCHN” [ep-s17e26-bchn]. He said it is the node most people run, alongside others such as BCHD and Knuth, and that its codebase is the one ultimately derived from Bitcoin Core [ep-s17e26-bchn].", "aliases": "bchn", "refs": ["ep-s17e26-bchn"], "url": "/wiki/bitcoin-cash-node/"}, {"id": "bitcoin-cash-node#106", "slug": "bitcoin-cash-node", "title": "Bitcoin Cash Node", "section": "The 2020 split", "text": "On 15 November 2020 Bitcoin ABC's chain split from Bitcoin Cash at block 661,648 over the 8% coinbase rule, and traded as BCHA [btk-xec]. The chain that rejected the rule kept the Bitcoin Cash name and the BCH code [wp-bch]. See ABC vs BCHN split.", "aliases": "bchn", "refs": ["btk-xec", "wp-bch"], "url": "/wiki/bitcoin-cash-node/"}, {"id": "bitcoin-cash-plus#infobox", "slug": "bitcoin-cash-plus", "title": "Bitcoin Cash Plus (BCP)", "section": "Summary and infobox", "text": "A 2018 Equihash fork of Bitcoin, not of Bitcoin Cash despite its name, whose README and a third-party list give different fork heights; it stopped producing blocks in 2018. Fork height (README): 509,696 [bcp-readme]; Block 509,696 time: 2018-02-18 02:33:41 UTC [btc-509696]; Fork height (third-party list): 501,407 [bth-review]; Proof of work: Equihash [bcp-readme]; Block size: 8 MB [bcp-readme]; Replay protection: 2-way, SIGHASH_FORK_ID [bcp-readme]; Status (Feb 2019 list): Not working; last synced block 536,609 on 8 Jun 2018 [bth-review]", "aliases": "bcp cash plus", "refs": ["bcp-readme", "btc-509696", "bth-review"], "url": "/wiki/bitcoin-cash-plus/"}, {"id": "bitcoin-cash-plus#takeover", "slug": "bitcoin-cash-plus", "title": "Bitcoin Cash Plus (BCP)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: the name says Bitcoin Cash, the code says Bitcoin. BCP shows how fork names in late 2017 were marketing, not lineage. [bth-review]", "aliases": "bcp cash plus", "refs": ["bth-review"], "url": "/wiki/bitcoin-cash-plus/"}, {"id": "bitcoin-cash-plus#109", "slug": "bitcoin-cash-plus", "title": "Bitcoin Cash Plus (BCP)", "section": "Fork", "text": "The project README says “Bitcoin Cash Plus (BCP) is a hardfork of bitcoin-core that occurred at block 509696” [bcp-readme]. A Bitcointalk list of reviewed forks gives “fork at 501407” instead; this wiki has not checked which is right [bth-review]. Block 501,407 was mined on 28 December 2017 and block 509,696 on 18 February 2018 [btc-501407] [btc-509696]. A reply in the same thread said “Bitcoin Cash Plus is not a fork of Bitcoin Cash” [bth-review].", "aliases": "bcp cash plus", "refs": ["bcp-readme", "btc-501407", "btc-509696", "bth-review"], "url": "/wiki/bitcoin-cash-plus/"}, {"id": "bitcoin-cash-plus#110", "slug": "bitcoin-cash-plus", "title": "Bitcoin Cash Plus (BCP)", "section": "Design and status", "text": "The README lists Equihash, an 8MB block size, a new difficulty algorithm and “2-way Replay protection (SIGHASH_FORK_ID)” [bcp-readme]. The list's 26 February 2019 status says it “doesn't seem to be working anymore”, with the last synced block 536609 on 8 June 2018 [bth-review].", "aliases": "bcp cash plus", "refs": ["bcp-readme", "bth-review"], "url": "/wiki/bitcoin-cash-plus/"}, {"id": "bitcoin-cash#infobox", "slug": "bitcoin-cash", "title": "Bitcoin Cash", "section": "Summary and infobox", "text": "The big-block fork of 1 August 2017, Bitcoin's first durable chain split. Ticker: BCH [btk-bch]; Type: UTXO hard fork of Bitcoin [btk-bch]; Split: 1 August 2017, by flag day (MTP 1501590000) [btk-bch]; Last common block: 478,558 [btk-bch]; First BCH-only block: 478,559, mined by ViaBTC, about 1.9 MB [btk-bch]; Proof of work: SHA-256d [btk-bch]; Supply: 21 million, Bitcoin's schedule [btk-bch]; Children: Bitcoin SV (2018), eCash XEC (2020) [btk-bch]; Block limit: 32 MB from May 2018; ABLA adaptive limit from May 2024 [btk-bch]", "aliases": "bch big blocks", "refs": ["btk-bch"], "url": "/wiki/bitcoin-cash/"}, {"id": "bitcoin-cash#takeover", "slug": "bitcoin-cash", "title": "Bitcoin Cash", "section": "Takeover view (editorial opinion)", "text": "Vlad landed on BTC in 2017 and disliked the campaign to call BCH “the real Bitcoin”. Nine years later he spent eight hours with the big blockers who stayed. The wiki keeps both: the facts, and that history. [btk-bch] [ep-s17e26-forkday]", "aliases": "bch big blocks", "refs": ["btk-bch", "ep-s17e26-forkday"], "url": "/wiki/bitcoin-cash/"}, {"id": "bitcoin-cash#113", "slug": "bitcoin-cash", "title": "Bitcoin Cash", "section": "Split", "text": "Bitcoin Cash is the main consequence of the block size war. It split from Bitcoin on 1 August 2017 by flag day; the last common block was 478,558, and the first BCH-only block, 478,559, was mined by ViaBTC about six hours later at about 1.9 MB [btk-bch]. Calin Culianu, who worked on Bitcoin ABC, told Bitcoin Takeover he was \"there on Fork Day\" [ep-s17e26-forkday].", "aliases": "bch big blocks", "refs": ["btk-bch", "ep-s17e26-forkday"], "url": "/wiki/bitcoin-cash/"}, {"id": "bitcoin-cash#114", "slug": "bitcoin-cash", "title": "Bitcoin Cash", "section": "Bitcoin ABC", "text": "The software that launched the fork was Bitcoin ABC, led by Amaury Séchet. He told the podcast it was its own fork of Bitcoin Core and did not reuse the work of XT, Classic or Unlimited [ep-s17e19-abc].", "aliases": "bch big blocks", "refs": ["ep-s17e19-abc"], "url": "/wiki/bitcoin-cash/"}, {"id": "bitcoin-cash#115", "slug": "bitcoin-cash", "title": "Bitcoin Cash", "section": "Upgrades", "text": "Bitcoin Cash upgrades on a May/November schedule. It replaced its emergency difficulty adjustment in November 2017, raised the limit to 32 MB and re-enabled opcodes including OP_CAT in May 2018, added CTOR in November 2018, Schnorr signatures in 2019, the ASERT difficulty algorithm in November 2020, CashTokens in May 2023 and the ABLA adaptive block size algorithm in May 2024 [btk-bch]. Séchet has said many big blockers initially resisted changing the difficulty algorithm because it would cement BCH as a minority fork [ep-s17e19-daa].", "aliases": "bch big blocks", "refs": ["btk-bch", "ep-s17e19-daa"], "url": "/wiki/bitcoin-cash/"}, {"id": "bitcoin-cash#116", "slug": "bitcoin-cash", "title": "Bitcoin Cash", "section": "Children", "text": "Bitcoin Cash has split twice: Bitcoin SV left on 15 November 2018 and Bitcoin ABC's chain, later eCash (XEC), left on 15 November 2020 [btk-bch].", "aliases": "bch big blocks", "refs": ["btk-bch"], "url": "/wiki/bitcoin-cash/"}, {"id": "bitcoin-cash#117", "slug": "bitcoin-cash", "title": "Bitcoin Cash", "section": "Heard on Bitcoin Takeover", "text": "Peter Rizun, who said he worked on Bitcoin Cash, still asked on S16 E30 (June 2025): “Why did Bitcoin Cash fork right there? I mean, I was part of it, I was working on Bitcoin Cash, but again, who was really pulling those strings? I don't know.” [ep-s16e30-q5577] Roger Ver framed the fork as a consequence of fees on S15 E26 (March 2024): “If the user experience had continued to be good on Bitcoin, nobody would use Litecoin for anything. Bitcoin Cash never would have even come into existence.” [ep-s15e26-q639] Early investor Marc De Mesel, looking back on S17 E44 (September 2026), said that “up until today, Bitcoin Cash did not prove to be a success”. [ep-s17e44-q1104]", "aliases": "bch big blocks", "refs": ["ep-s15e26-q639", "ep-s16e30-q5577", "ep-s17e44-q1104"], "url": "/wiki/bitcoin-cash/"}, {"id": "bitcoin-cbc#infobox", "slug": "bitcoin-cbc", "title": "Bitcoin@CBC (BCBC)", "section": "Summary and infobox", "text": "A snapshot fork keyed to block 498,754 that filtered early coinbase coins and two famous addresses out of its copy of the Bitcoin ledger. Snapshot height: 498,754 [bth-review]; Block 498,754 time: 2017-12-11 15:07:40 UTC [btc-498754]; Type: Snapshot fork, no shared pre-fork history [bth-review]; Ratio: <1:1 (forkdrop); n BTC = n-1 BCBC (2018 forum post) [fd-data]; Status (Feb 2019 list): Not working; last synced block 18,286 on 17 Jul 2018 [bth-review]", "aliases": "bcbc bitcoin@cbc cbc cleanblockchain clean blockchain", "refs": ["btc-498754", "bth-review", "fd-data"], "url": "/wiki/bitcoin-cbc/"}, {"id": "bitcoin-cbc#takeover", "slug": "bitcoin-cbc", "title": "Bitcoin@CBC (BCBC)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin@CBC is one of the few forks that edited the inherited balances on purpose, removing early coinbase coins and two named addresses. [bth-review]", "aliases": "bcbc bitcoin@cbc cbc cleanblockchain clean blockchain", "refs": ["bth-review"], "url": "/wiki/bitcoin-cbc/"}, {"id": "bitcoin-cbc#120", "slug": "bitcoin-cbc", "title": "Bitcoin@CBC (BCBC)", "section": "Design", "text": "The 2019 fork list calls Bitcoin CBC a “snapshot fork (no shared pre-fork blockchain history)” taken at block 498,754 [bth-review]. Block 498,754 was mined on 11 December 2017 [btc-498754]. The list quotes the project saying “All unspent coinbase generated coins from 50000 first blocks from original Bitcoin blockchain were filtered (1235650 coins)” and that two well-known addresses holding 108,108 coins were deleted [bth-review]. It also quotes a rule that each address with a positive balance was reduced by one coin, with those funds going to an ExtraReward pool [bth-review].", "aliases": "bcbc bitcoin@cbc cbc cleanblockchain clean blockchain", "refs": ["btc-498754", "bth-review"], "url": "/wiki/bitcoin-cbc/"}, {"id": "bitcoin-cbc#121", "slug": "bitcoin-cbc", "title": "Bitcoin@CBC (BCBC)", "section": "Record", "text": "An April 2018 reply in the same fork-list thread summed the payout up as “n BTC = n-1 BCBC” [bth-review]. forkdrop's data file lists the ratio as <1:1 and the maximum supply as 21,000,000 [fd-data]. forkdrop's announcement link, Bitcointalk topic 3109563, now carries the title “[CLOSED]: unnamed coin”, and the surviving posts in it advertise a Bitcoin@CBC mining pool [bcbc-thread]. The 2019 list found the website, Twitter account and GitHub repository gone, and its node “doesn't seem to be working anymore”, last synced at block 18,286 on 17 July 2018 [bth-review].", "aliases": "bcbc bitcoin@cbc cbc cleanblockchain clean blockchain", "refs": ["bcbc-thread", "bth-review", "fd-data"], "url": "/wiki/bitcoin-cbc/"}, {"id": "bitcoin-clashic#infobox", "slug": "bitcoin-clashic", "title": "Bitcoin Clashic", "section": "Summary and infobox", "text": "A minority chain that kept Bitcoin Cash's original rules when BCH changed its difficulty algorithm in November 2017. Type: Minority chain left behind by Bitcoin Cash's November 2017 upgrade [ep-s17e19-clashic]; Trigger: BCH replaced its emergency difficulty adjustment on 13 November 2017 [btk-bch]; Assessment: “More or less of a troll fork” (Amaury Séchet) [ep-s17e19-clashic]", "aliases": "clashic bchc", "refs": ["btk-bch", "ep-s17e19-clashic"], "url": "/wiki/bitcoin-clashic/"}, {"id": "bitcoin-clashic#takeover", "slug": "bitcoin-clashic", "title": "Bitcoin Clashic", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Clashic matters less as a coin than as a pattern. Every contentious upgrade can leave a no-upgrade chain behind, and Bitcoin Cash produced its first one within four months. [btk-bch] [ep-s17e19-clashic]", "aliases": "clashic bchc", "refs": ["btk-bch", "ep-s17e19-clashic"], "url": "/wiki/bitcoin-clashic/"}, {"id": "bitcoin-clashic#124", "slug": "bitcoin-clashic", "title": "Bitcoin Clashic", "section": "Origin", "text": "On 13 November 2017 Bitcoin Cash replaced its emergency difficulty adjustment (EDA) with a new difficulty adjustment algorithm using a rolling 144-block window [btk-bch]. Asked about Clashic on S17 E19, Amaury Séchet said some people did not want that hard fork changing the DAA and created an alternative chain, which he called “more or less of a troll fork” that “never really had any kind of real support” [ep-s17e19-clashic].", "aliases": "clashic bchc", "refs": ["btk-bch", "ep-s17e19-clashic"], "url": "/wiki/bitcoin-clashic/"}, {"id": "bitcoin-clashic#125", "slug": "bitcoin-clashic", "title": "Bitcoin Clashic", "section": "Listing", "text": "The February 2019 Bitcointalk review list names it “Bitcoin Clashic (BCL)”, gives its fork as block 478,558, Bitcoin Cash's own split from Bitcoin, and quotes its site saying the mainnet “launched on August 1st, 2017 and is still alive” [bth-review].", "aliases": "clashic bchc", "refs": ["bth-review"], "url": "/wiki/bitcoin-clashic/"}, {"id": "bitcoin-clashic#126", "slug": "bitcoin-clashic", "title": "Bitcoin Clashic", "section": "What is not known", "text": "No source here gives the height at which Clashic and Bitcoin Cash diverged in November 2017, so it is unknown in this wiki and tracked as pending in the scope list [ep-s17e19-clashic] [btk-bch].", "aliases": "clashic bchc", "refs": ["btk-bch", "ep-s17e19-clashic"], "url": "/wiki/bitcoin-clashic/"}, {"id": "bitcoin-class#infobox", "slug": "bitcoin-class", "title": "Bitcoin Class (BCS)", "section": "Summary and infobox", "text": "An April 2018 fork of Bitcoin Cash at BCH height 528,000 with two-minute Equihash blocks and an anti-quantum research plan. Parent: Bitcoin Cash [bcs-class-ann]; Fork height (BCH): 528,000 [bcs-class-ann]; Algorithm: Equihash [bcs-class-ann]; Block interval: 2 minutes [bcs-class-ann]; Premine: 1% of supply [bcs-class-ann]", "aliases": "bcs class quantum", "refs": ["bcs-class-ann"], "url": "/wiki/bitcoin-class/"}, {"id": "bitcoin-class#takeover", "slug": "bitcoin-class", "title": "Bitcoin Class (BCS)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Class is a fork of a fork, splitting from Bitcoin Cash rather than from Bitcoin. [bcs-class-ann]", "aliases": "bcs class quantum", "refs": ["bcs-class-ann"], "url": "/wiki/bitcoin-class/"}, {"id": "bitcoin-class#129", "slug": "bitcoin-class", "title": "Bitcoin Class (BCS)", "section": "Record", "text": "The announcement of 24 April 2018 says “Bitcoin Class team will fork Bitcoin Cash at block height 528000” and promises to explore a “quantum-resistant solution of bitcoin” [bcs-class-ann]. It lists a two-minute block interval, a 21 million supply, Equihash GPU mining, no SegWit and a 1% premine [bcs-class-ann]. forkdrop's data file gives Bitcoin Cash as the source chain and a date of 2018-04-29 [fd-data]. The BCS ticker is also used by Bitcoin Smart and Bitcoin Star [fd-data]. Its state after 2018 is unknown [fd-data].", "aliases": "bcs class quantum", "refs": ["bcs-class-ann", "fd-data"], "url": "/wiki/bitcoin-class/"}, {"id": "bitcoin-classic#infobox", "slug": "bitcoin-classic", "title": "Bitcoin Classic", "section": "Summary and infobox", "text": "The early-2016 client that proposed a one-time 2 MB hard fork (BIP-109) after Bitcoin XT stalled. Type: Alternative full-node client based on Bitcoin Core 0.11.2 [classic-rel]; First release: Bitcoin Classic 0.11.2, 10 February 2016 [classic-rel]; Proposal: BIP-109: block size limit from 1,000,000 to 2,000,000 bytes [bip109]; Extra limit: 1,300,000,000 bytes hashed for signatures per block [bip109]; Trigger: Bit 0x10000000 in 750 of 1,000 blocks, then a 28-day grace period [bip109]; Expiry: Withdrawn if not triggered by 1 January 2018 [bip109]; Outcome: Never activated; BIP-109 status Closed [bip109]", "aliases": "classic bip109 2mb", "refs": ["bip109", "classic-rel"], "url": "/wiki/bitcoin-classic/"}, {"id": "bitcoin-classic#takeover", "slug": "bitcoin-classic", "title": "Bitcoin Classic", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Classic was the smaller ask after XT, and it was stalled less by code than by an industry letter: the Hong Kong Roundtable statement, signed days after Classic's first release, promised a Core hard fork instead. [hk-letter] [classic-rel]", "aliases": "classic bip109 2mb", "refs": ["classic-rel", "hk-letter"], "url": "/wiki/bitcoin-classic/"}, {"id": "bitcoin-classic#132", "slug": "bitcoin-classic", "title": "Bitcoin Classic", "section": "The proposal", "text": "BIP-109 raised the block size limit from 1,000,000 to 2,000,000 bytes and added a new limit of 1,300,000,000 bytes hashed to compute signatures per block [bip109]. Miners signalled with bit 0x10000000; once 750 of the preceding 1,000 blocks carried it, a 28-day grace period would begin [bip109]. If it was not triggered by 1 January 2018 the BIP was to be considered withdrawn [bip109].", "aliases": "classic bip109 2mb", "refs": ["bip109"], "url": "/wiki/bitcoin-classic/"}, {"id": "bitcoin-classic#133", "slug": "bitcoin-classic", "title": "Bitcoin Classic", "section": "The client", "text": "The first Bitcoin Classic release, version 0.11.2, was announced on 10 February 2016 as “focused on doubling the transaction capacity of Bitcoin” [classic-rel]. It was based on Bitcoin Core 0.11.2 and compatible with its blockchain files and wallet [classic-rel].", "aliases": "classic bip109 2mb", "refs": ["classic-rel"], "url": "/wiki/bitcoin-classic/"}, {"id": "bitcoin-classic#134", "slug": "bitcoin-classic", "title": "Bitcoin Classic", "section": "Outcome", "text": "Ten days after that release, the Hong Kong Roundtable statement committed its signers to run only Bitcoin Core-compatible consensus systems for the foreseeable future [hk-letter]. BIP-109 never activated and its status in the BIPs repository is Closed [bip109]. Bitcoin XT adopted Classic's 2 MB bump in January 2016 [xt-bw].", "aliases": "classic bip109 2mb", "refs": ["bip109", "hk-letter", "xt-bw"], "url": "/wiki/bitcoin-classic/"}, {"id": "bitcoin-clean#infobox", "slug": "bitcoin-clean", "title": "bitcoinClean (BCL)", "section": "Summary and infobox", "text": "An April 2018 fork at block 518,800 that promised mining only with renewable energy through a peer-reviewed “proof-of-greenness”. Fork height: 518,800 [bcl-site]; Block 518,800 time: 2018-04-18 15:26:13 UTC [btc-518800]; Pitch: “the first eco-friendly crypto currency” [bcl-site]; Block size: 8MB [bcl-site]; Status (Feb 2019 list): Stopped; last synced block 588600 on 11/10/2018 [bth-review]", "aliases": "bcl bitcoinclean clean green renewable", "refs": ["bcl-site", "btc-518800", "bth-review"], "url": "/wiki/bitcoin-clean/"}, {"id": "bitcoin-clean#takeover", "slug": "bitcoin-clean", "title": "bitcoinClean (BCL)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: bitcoinClean shares the BCL ticker with Bitcoin Clashic, a Bitcoin Cash fork, in the 2019 list, and with Bitcoin Cloud and Bitcoin Lunar in forkdrop's data. [bth-review] [fd-data]", "aliases": "bcl bitcoinclean clean green renewable", "refs": ["bth-review", "fd-data"], "url": "/wiki/bitcoin-clean/"}, {"id": "bitcoin-clean#137", "slug": "bitcoin-clean", "title": "bitcoinClean (BCL)", "section": "Pitch", "text": "The archived site, captured on 10 May 2018, introduces “the first eco-friendly crypto currency” and announces the hard fork at “Block #518.800” on “Tuesday, April 18th, 2018, 5:26:13 PM (UTC)” [bcl-site]. Bitcoin block 518,800 has a header time of 15:26:13 UTC on 18 April 2018, a Wednesday, two hours earlier than the time the site gave [btc-518800]. The site says bitcoinClean “introduces the proof-of-greenness protocol to verify the use of green energy” and that “Every node must undergo a peer review to participate in the network” [bcl-site]. It also lists 8MB blocks [bcl-site].", "aliases": "bcl bitcoinclean clean green renewable", "refs": ["bcl-site", "btc-518800"], "url": "/wiki/bitcoin-clean/"}, {"id": "bitcoin-clean#138", "slug": "bitcoin-clean", "title": "bitcoinClean (BCL)", "section": "Record", "text": "The 2019 fork list says it “doesn't seem to be working anymore, 0.3 GB, last synced block 588600 on 11/10/2018” [bth-review]. On 1 May 2018 a fork-transaction tool added “Bitcoin Clean \"BCL\"”, in a post that warned one of the newly added forks had no replay protection [ayms-nbtc].", "aliases": "bcl bitcoinclean clean green renewable", "refs": ["ayms-nbtc", "bth-review"], "url": "/wiki/bitcoin-clean/"}, {"id": "bitcoin-cloud#infobox", "slug": "bitcoin-cloud", "title": "Bitcoin Cloud (BCL)", "section": "Summary and infobox", "text": "A February 2018 fork at block 510,048 with a difficulty reset, replay protection and SegWit; forkdrop still had it as live in 2019. Fork height: 510,048 [bclc-site]; Block 510,048 time: 2018-02-20 08:20:59 UTC [btc-510048]; Replay protection: Strong (site) [bclc-site]; Ratio: 1:1 [bclc-site]", "aliases": "bcl cloud", "refs": ["bclc-site", "btc-510048"], "url": "/wiki/bitcoin-cloud/"}, {"id": "bitcoin-cloud#takeover", "slug": "bitcoin-cloud", "title": "Bitcoin Cloud (BCL)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: three coins in forkdrop's data use the BCL ticker, Bitcoin Cloud among them. [fd-data]", "aliases": "bcl cloud", "refs": ["fd-data"], "url": "/wiki/bitcoin-cloud/"}, {"id": "bitcoin-cloud#141", "slug": "bitcoin-cloud", "title": "Bitcoin Cloud (BCL)", "section": "Record", "text": "The archived site, captured on 14 August 2018, lists “Fork Block: 510048”, a difficulty reset, strong replay protection, SegWit and a 1:1 ratio [bclc-site]. Block 510,048 was mined on 20 February 2018 [btc-510048]. The README is the stock Bitcoin Core text renamed to BitcoinCloud [bclc-readme]. forkdrop's data file marked it live in its January 2019 update [fd-data]. The BCL ticker is shared with bitcoinClean and Bitcoin Lunar [fd-data]. Its state after 2019 is unknown [fd-data].", "aliases": "bcl cloud", "refs": ["bclc-readme", "bclc-site", "btc-510048", "fd-data"], "url": "/wiki/bitcoin-cloud/"}, {"id": "bitcoin-com#infobox", "slug": "bitcoin-com", "title": "Bitcoin.com", "section": "Summary and infobox", "text": "Roger Ver's company and domain, founded in 2014, which became the most visible Bitcoin Cash promoter after 2017. Founded: 2014, by Roger Ver [wp-bitcoincom]; Headquarters: Saint Kitts and Nevis [wp-bitcoincom]; Wallet: Bitcoin.com Wallet, launched June 2017 [wp-bitcoincom]; CEO from 2020: Dennis Jarvis [wp-bitcoincom]; New York Agreement: Signatory [nya-letter]; Disclosure: Bitcoin.com News has sponsored Bitcoin Takeover episodes [ep-s16e30-intro]", "aliases": "bitcoin.com bitcoin com wallet", "refs": ["ep-s16e30-intro", "nya-letter", "wp-bitcoincom"], "url": "/wiki/bitcoin-com/"}, {"id": "bitcoin-com#takeover", "slug": "bitcoin-com", "title": "Bitcoin.com", "section": "Takeover view (editorial opinion)", "text": "Vlad's own view in the Forks! magazine: what he disliked about Bitcoin Cash was “the way Bitcoin.com quietly became a BCH website”. Disclosure: Bitcoin.com News has sponsored episodes of the show. [btk-bch] [ep-s16e30-intro]", "aliases": "bitcoin.com bitcoin com wallet", "refs": ["btk-bch", "ep-s16e30-intro"], "url": "/wiki/bitcoin-com/"}, {"id": "bitcoin-com#144", "slug": "bitcoin-com", "title": "Bitcoin.com", "section": "History", "text": "Wikipedia says Roger Ver gained control of the Bitcoin.com domain in April 2014, leased it to Blockchain.info and later to OKCoin, and won a $570,000 judgment against OKCoin's Hong Kong entity in November 2017 [wp-bitcoincom]. The company is headquartered in Saint Kitts and Nevis and launched the Bitcoin.com Wallet in June 2017 [wp-bitcoincom]. In May 2020 Dennis Jarvis became CEO and broadened the vision to “economic freedom” rather than one cryptocurrency [wp-bitcoincom].", "aliases": "bitcoin.com bitcoin com wallet", "refs": ["wp-bitcoincom"], "url": "/wiki/bitcoin-com/"}, {"id": "bitcoin-com#145", "slug": "bitcoin-com", "title": "Bitcoin.com", "section": "Forks", "text": "Bitcoin.com is on the list of New York Agreement signatories of May 2017 [nya-letter]. On S15 E26 Ver said that high fees became “such a big headache that literally Bitcoin.com stopped focusing on Bitcoin” [ep-s15e26-focus].", "aliases": "bitcoin.com bitcoin com wallet", "refs": ["ep-s15e26-focus", "nya-letter"], "url": "/wiki/bitcoin-com/"}, {"id": "bitcoin-com#146", "slug": "bitcoin-com", "title": "Bitcoin.com", "section": "Disclosure", "text": "Bitcoin.com News is a sponsor of Bitcoin Takeover; S16 E30, for example, opened with it in the sponsor list [ep-s16e30-intro].", "aliases": "bitcoin.com bitcoin com wallet", "refs": ["ep-s16e30-intro"], "url": "/wiki/bitcoin-com/"}, {"id": "bitcoin-community#infobox", "slug": "bitcoin-community", "title": "Bitcoin Community (BTSQ)", "section": "Summary and infobox", "text": "A January 2018 fork at block 506,066 from a Chinese blockchain-education group whose README copies Bitcoin World's template. Fork height: 506,066 [btsq-readme]; Block 506,066 time: 2018-01-25 15:20:45 UTC [btc-506066]; README estimate: “roughly 00:00:00 UTC January 26, 2018” [btsq-readme]; Mission: “For one hundred million people to understand block chain” [btsq-site]", "aliases": "btsq community", "refs": ["btc-506066", "btsq-readme", "btsq-site"], "url": "/wiki/bitcoin-community/"}, {"id": "bitcoin-community#takeover", "slug": "bitcoin-community", "title": "Bitcoin Community (BTSQ)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Community is a fork whose stated purpose was education rather than a new technical feature. [btsq-site]", "aliases": "btsq community", "refs": ["btsq-site"], "url": "/wiki/bitcoin-community/"}, {"id": "bitcoin-community#149", "slug": "bitcoin-community", "title": "Bitcoin Community (BTSQ)", "section": "README", "text": "The GitHub README says Bitcoin Community “is a fork of the Bitcoin blockchain that will occur at block height 506066, at roughly 00:00:00 UTC January 26, 2018” [btsq-readme]. Block 506,066 was mined 8 hours 39 minutes earlier, at 15:20:45 UTC on 25 January 2018 [btc-506066]. The rest of the README repeats the Bitcoin World template almost word for word [btsq-readme] [btw-readme].", "aliases": "btsq community", "refs": ["btc-506066", "btsq-readme", "btw-readme"], "url": "/wiki/bitcoin-community/"}, {"id": "bitcoin-community#150", "slug": "bitcoin-community", "title": "Bitcoin Community (BTSQ)", "section": "Site", "text": "The archived English site, captured on 10 March 2018, gives the mission “For one hundred million people to understand block chain” and describes a decentralized community of blockchain enthusiasts [btsq-site]. Its FAQ says “Bifurcation height is 506066” and that BTC holders would receive coins [btsq-site]. Its download section offers “Bitcoin v0.15.0.2” builds [btsq-site]. The 2019 fork list has no entry for it [bth-review].", "aliases": "btsq community", "refs": ["bth-review", "btsq-site"], "url": "/wiki/bitcoin-community/"}, {"id": "bitcoin-coral#infobox", "slug": "bitcoin-coral", "title": "Bitcoin Coral (BTCO)", "section": "Summary and infobox", "text": "A late-2017 project listed by forkdrop at block 491,407 whose archived site sold tokens and reused Bitcoin Cash copy. Fork height (forkdrop): 491,407 [fd-data]; Date (forkdrop): 2017-10-24 [fd-data]; Site (Dec 2017): Token sale page [btco-site]", "aliases": "btco coral finma", "refs": ["btco-site", "fd-data"], "url": "/wiki/bitcoin-coral/"}, {"id": "bitcoin-coral#takeover", "slug": "bitcoin-coral", "title": "Bitcoin Coral (BTCO)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Coral's site in December 2017 was a token sale, not a fork claim page. [btco-site]", "aliases": "btco coral finma", "refs": ["btco-site"], "url": "/wiki/bitcoin-coral/"}, {"id": "bitcoin-coral#153", "slug": "bitcoin-coral", "title": "Bitcoin Coral (BTCO)", "section": "Record", "text": "forkdrop's data file lists Bitcoin Coral at block 491407 on 2017-10-24 with a 1:1 ratio, and links a white paper [fd-data]. The archived site, captured on 17 December 2017, shows a token sale (“Tokens to be distributed 53054.38/ 200,000”) and claims “Regulated by FINMA The Swiss Financial Authority” [btco-site]. The same page includes text describing Bitcoin Cash, such as “Bitcoin Cash is resistant to political and social attacks on protocol development” [btco-site]. No chain data was found, and the FINMA claim is unverified [btco-site]. The BTCO ticker is shared with Bitcoin Oil [fd-data].", "aliases": "btco coral finma", "refs": ["btco-site", "fd-data"], "url": "/wiki/bitcoin-coral/"}, {"id": "bitcoin-core-btcc#infobox", "slug": "bitcoin-core-btcc", "title": "Bitcoin Core (BTCC fork token)", "section": "Summary and infobox", "text": "A May 2018 upgrade of Bitcoin Clashic branded Bitcoin Core (BTCC), later renamed Title Network; unrelated to the Bitcoin Core software project. Parent: Bitcoin Clashic [btcc-ann]; Fork block (forkdrop): 576,698 [fd-data]; Later name: Title Network [btcc-readme]", "aliases": "btcc bitcoin core token clashic title network", "refs": ["btcc-ann", "btcc-readme", "fd-data"], "url": "/wiki/bitcoin-core-btcc/"}, {"id": "bitcoin-core-btcc#takeover", "slug": "bitcoin-core-btcc", "title": "Bitcoin Core (BTCC fork token)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: the name copies Bitcoin's reference client, but the coin was an upgrade of Bitcoin Clashic and later dropped the brand. [btcc-ann] [btcc-readme]", "aliases": "btcc bitcoin core token clashic title network", "refs": ["btcc-ann", "btcc-readme"], "url": "/wiki/bitcoin-core-btcc/"}, {"id": "bitcoin-core-btcc#156", "slug": "bitcoin-core-btcc", "title": "Bitcoin Core (BTCC fork token)", "section": "Record", "text": "The announcement of 29 May 2018 says “Bitcoin Core ($BTCC) is an upgrade of Bitcoin Clashic” [btcc-ann]. forkdrop's data file gives Bitcoin Clashic as the source chain, block 576698 and a date of 2018-05-20 [fd-data]. That height would be on the Clashic chain, not Bitcoin's, and this wiki has not checked it against a Clashic block explorer [fd-data]. The repository README, “Bitcoin Core Squared”, later says “The Bitcoin Core $BTCC brand has been sunset. Going forward this project is called Title Network.” [btcc-readme] It announced a proof-of-work change at height 836750 [btcc-readme]. It is a coin, not the Bitcoin reference software [btcc-ann].", "aliases": "btcc bitcoin core token clashic title network", "refs": ["btcc-ann", "btcc-readme", "fd-data"], "url": "/wiki/bitcoin-core-btcc/"}, {"id": "bitcoin-dao#infobox", "slug": "bitcoin-dao", "title": "Bitcoin DAO (BTD)", "section": "Summary and infobox", "text": "A 2018 masternode coin with an ERC-20 pre-airdrop, converting 1:1 at mainnet launch at Bitcoin block 531,650, with 1 BTD per BTC. Mainnet height: 531,650 [btd-dao-ann]; Block 531,650 time: 2018-07-12 19:03:53 UTC [btc-531650]; Max supply: 25 million [btd-dao-ann]; Ratio: 1 BTC = 1 BTD [btd-dao-ann]", "aliases": "btd dao masternodes", "refs": ["btc-531650", "btd-dao-ann"], "url": "/wiki/bitcoin-dao/"}, {"id": "bitcoin-dao#takeover", "slug": "bitcoin-dao", "title": "Bitcoin DAO (BTD)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin DAO handed out ERC-20 tokens first and promised to swap them for coins on its own chain later. [btd-dao-ann]", "aliases": "btd dao masternodes", "refs": ["btd-dao-ann"], "url": "/wiki/bitcoin-dao/"}, {"id": "bitcoin-dao#159", "slug": "bitcoin-dao", "title": "Bitcoin DAO (BTD)", "section": "Record", "text": "The pre-announcement of 6 May 2018 lists a 25 million maximum: 21 million from the hard fork, 2 million for a treasury, 1 million for the airdrop and first masternodes, and 1 million for bounties [btd-dao-ann]. It says the airdrop tokens were ERC-20 and that “After mainnet launch (Bitcoins block №531650) these tokens will be converted 1:1 to BTD” [btd-dao-ann]. Bitcoin holders would also get “1 BTC = 1 BTD” [btd-dao-ann]. A later edit says “we distributed only 2.11% of the total” in that round [btd-dao-ann]. Block 531,650 was mined on 12 July 2018, while forkdrop's data file gives 2018-06-30 [btc-531650] [fd-data]. The BTD ticker is shared with Bitcoin Dollar [fd-data].", "aliases": "btd dao masternodes", "refs": ["btc-531650", "btd-dao-ann", "fd-data"], "url": "/wiki/bitcoin-dao/"}, {"id": "bitcoin-diamond#infobox", "slug": "bitcoin-diamond", "title": "Bitcoin Diamond", "section": "Summary and infobox", "text": "A November 2017 airdrop fork that paid 10 BCD per BTC, changed proof of work and set aside 40 million coins for a rewards pool. Fork height: Block 495,866 [bcd-readme]; Fork time: Bitcoin block 495,866, header time 24 November 2017 09:20:12 UTC [btc-495866]; Airdrop: 10 BCD per 1 BTC [bcd-readme]; Supply: 210 million BCD: 170 million to holders, 40 million to a “community rewards pool” [bcd-readme]; Proof of work: A new algorithm (the README does not name it) [bcd-readme]; Replay protection: Claimed in the README [bcd-readme]", "aliases": "bcd x13", "refs": ["bcd-readme", "btc-495866"], "url": "/wiki/bitcoin-diamond/"}, {"id": "bitcoin-diamond#takeover", "slug": "bitcoin-diamond", "title": "Bitcoin Diamond", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Diamond is the fork-mania template, a 10-for-1 airdrop with a large pool held back from holders. Vlad named it on S17 E19 when asking why no later Bitcoin fork matched Bitcoin Cash. [bcd-readme] [ep-s17e19-otherforks]", "aliases": "bcd x13", "refs": ["bcd-readme", "ep-s17e19-otherforks"], "url": "/wiki/bitcoin-diamond/"}, {"id": "bitcoin-diamond#162", "slug": "bitcoin-diamond", "title": "Bitcoin Diamond", "section": "Launch", "text": "Bitcoin Diamond forked from Bitcoin at the predetermined height of block 495,866, after which its miners began creating blocks with a new proof-of-work algorithm [bcd-readme]. Bitcoin block 495,866 carries a header time of 24 November 2017, 09:20:12 UTC [btc-495866].", "aliases": "bcd x13", "refs": ["bcd-readme", "btc-495866"], "url": "/wiki/bitcoin-diamond/"}, {"id": "bitcoin-diamond#163", "slug": "bitcoin-diamond", "title": "Bitcoin Diamond", "section": "Supply", "text": "The project states a total of 210 million BCD, of which 170 million were distributed to Bitcoin holders at 1 BTC to 10 BCD and 40 million were assigned to a community rewards pool “as tributes and mining” [bcd-readme]. The README also claims an anti-replay function in both directions [bcd-readme].", "aliases": "bcd x13", "refs": ["bcd-readme"], "url": "/wiki/bitcoin-diamond/"}, {"id": "bitcoin-dollar#infobox", "slug": "bitcoin-dollar", "title": "Bitcoin Dollar (BTD)", "section": "Summary and infobox", "text": "A 1:1 claim project for everyone holding Bitcoin on 28 February 2018, with 45 days to claim; no fork block is known. Snapshot date: 28 February 2018 [btd-dollar-ann]; Claim window: 45 days [btd-dollar-ann]; Fork block: Unknown (forkdrop: ???) [fd-data]", "aliases": "btd dollar", "refs": ["btd-dollar-ann", "fd-data"], "url": "/wiki/bitcoin-dollar/"}, {"id": "bitcoin-dollar#takeover", "slug": "bitcoin-dollar", "title": "Bitcoin Dollar (BTD)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Dollar said unclaimed coins would go to its early backers. [btd-dollar-ann]", "aliases": "btd dollar", "refs": ["btd-dollar-ann"], "url": "/wiki/bitcoin-dollar/"}, {"id": "bitcoin-dollar#166", "slug": "bitcoin-dollar", "title": "Bitcoin Dollar (BTD)", "section": "Record", "text": "The announcement of 22 January 2018 says “All Bitcoin holders as of Feb 28, 2018, will be owners of Bitcoin Dollars” [btd-dollar-ann]. Holders would have 45 days to claim, after which unclaimed coins “will be distributed among the early backers, donors or contributors to the project” [btd-dollar-ann]. forkdrop's data file lists a registration airdrop with fork block “???” and a 21,000,000 maximum supply [fd-data]. Whether a chain launched is unknown [fd-data].", "aliases": "btd dollar", "refs": ["btd-dollar-ann", "fd-data"], "url": "/wiki/bitcoin-dollar/"}, {"id": "bitcoin-eco#infobox", "slug": "bitcoin-eco", "title": "Bitcoin ECO (BEC)", "section": "Summary and infobox", "text": "A fork listed at block 500,000 by a Canadian Blockchain Community and listed on the Allcoin exchange in January 2018; the sources disagree on its supply. Fork height (forkdrop): 500,000 [fd-data]; Block 500,000 time: 2017-12-18 18:35:25 UTC [btc-500000]; Max supply: 210ML (site); 210 Billion (forkdrop) [bec-site]; Exchange listing: Allcoin, 6 Jan 2018 (Beijing time) [bec-allcoin]", "aliases": "bec eco allcoin", "refs": ["bec-allcoin", "bec-site", "btc-500000", "fd-data"], "url": "/wiki/bitcoin-eco/"}, {"id": "bitcoin-eco#takeover", "slug": "bitcoin-eco", "title": "Bitcoin ECO (BEC)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: forkdrop's date for Bitcoin ECO is a year after its own block, one of several conflicts in this entry. [fd-data] [btc-500000]", "aliases": "bec eco allcoin", "refs": ["btc-500000", "fd-data"], "url": "/wiki/bitcoin-eco/"}, {"id": "bitcoin-eco#169", "slug": "bitcoin-eco", "title": "Bitcoin ECO (BEC)", "section": "Record", "text": "An Allcoin notice of 6 January 2018 says “Canadian Blockchain Community introduces a new fork of Bitcoin-Bitcoin ECO (BEC)” and schedules BEC trading [bec-allcoin]. The archived site compares BEC with BTC, BTG and BCD and gives it SHA256 mining, 4MB blocks and a maximum supply of “210ML” [bec-site]. forkdrop's data file gives block 500000, a date of 2018-12-18, a 10k:1 ratio, a maximum supply of 210 Billion and the reason “Homepage Down” [fd-data]. Block 500,000 was mined on 18 December 2017, so forkdrop's year conflicts with its own block [btc-500000].", "aliases": "bec eco allcoin", "refs": ["bec-allcoin", "bec-site", "btc-500000", "fd-data"], "url": "/wiki/bitcoin-eco/"}, {"id": "bitcoin-faith#infobox", "slug": "bitcoin-faith", "title": "Bitcoin Faith (BTF)", "section": "Summary and infobox", "text": "A fork at block 500,000 with 8 MB blocks and a 1% reserve; a 2019 review found it still running even though its GitHub repository had disappeared. Fork height: 500,000 [btf-site]; Block 500,000 time: 2017-12-18 18:35:25 UTC [btc-500000]; Ratio: 1:1 [btf-site]; Block size: 8M [btf-site]; Reserve: 1% of 21 million [btf-site]; GitHub: “(disappeared)” [bth-review]; Status (Feb 2019 list): “still seems to be working, 0.6 GB” [bth-review]", "aliases": "btf faith", "refs": ["btc-500000", "btf-site", "bth-review"], "url": "/wiki/bitcoin-faith/"}, {"id": "bitcoin-faith#takeover", "slug": "bitcoin-faith", "title": "Bitcoin Faith (BTF)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Faith outlived its own code repository — a 2019 reviewer could still sync it after the GitHub page was gone. [bth-review]", "aliases": "btf faith", "refs": ["bth-review"], "url": "/wiki/bitcoin-faith/"}, {"id": "bitcoin-faith#172", "slug": "bitcoin-faith", "title": "Bitcoin Faith (BTF)", "section": "Pitch", "text": "The archived site, captured on 1 January 2018, calls BTF “a new chain of 500000 forked at the height of the bitcoin block” and promises holders the same amount “according to the ratio of 1:1” [btf-site]. Block 500,000 was mined on 18 December 2017 [btc-500000]. It lists 8M blocks, a roadmap starting “2017.12.19 At 500000 height forks began to build”, a total of 21 million and says “The Bitcoin Faith reserves 1%” [btf-site].", "aliases": "btf faith", "refs": ["btc-500000", "btf-site"], "url": "/wiki/bitcoin-faith/"}, {"id": "bitcoin-faith#173", "slug": "bitcoin-faith", "title": "Bitcoin Faith (BTF)", "section": "Record", "text": "The 2019 fork list gives the GitHub repository as “(disappeared)” but its 26 February 2019 status says “still seems to be working, 0.6 GB” [bth-review]. The same list uses the ticker BTF for Bitcoin Flash, another fork at block 508000 [bth-review].", "aliases": "btf faith", "refs": ["bth-review"], "url": "/wiki/bitcoin-faith/"}, {"id": "bitcoin-file#infobox", "slug": "bitcoin-file", "title": "Bitcoin FILE (BIFI)", "section": "Summary and infobox", "text": "A fork at block 501,225 at 1 BTC = 1,000 BIFI; the only source this wiki has is the 2019 fork list. Fork height: 501,225 [bth-review]; Block 501,225 time: 2017-12-27 06:55:44 UTC [btc-501225]; Ratio: 1 BTC = 1000 BIFI [bth-review]; Source code: “no source code available” [bth-review]", "aliases": "bifi file", "refs": ["btc-501225", "bth-review"], "url": "/wiki/bitcoin-file/"}, {"id": "bitcoin-file#takeover", "slug": "bitcoin-file", "title": "Bitcoin FILE (BIFI)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: three forks claimed block 501,225 — Bitcoin God, Bitcoin FILE and FastBitcoin — and New Bitcoin snapshotted the same block. [bth-review] [nbtc-site]", "aliases": "bifi file", "refs": ["bth-review", "nbtc-site"], "url": "/wiki/bitcoin-file/"}, {"id": "bitcoin-file#176", "slug": "bitcoin-file", "title": "Bitcoin FILE (BIFI)", "section": "Record", "text": "The 2019 fork list gives “Bitcoin FILE (BIFI) (1 BTC = 1000 BIFI)”, “fork at 501225”, the site bitcoinfile.org and “no source code available” [bth-review]. Block 501,225 was mined on 27 December 2017 [btc-501225]. The list's timeline puts Bitcoin God and FastBitcoin at the same block [bth-review]. This wiki found no capture of the BIFI site from the fork period, so the project's own claims are unknown [bth-review].", "aliases": "bifi file", "refs": ["btc-501225", "bth-review"], "url": "/wiki/bitcoin-file/"}, {"id": "bitcoin-flash#infobox", "slug": "bitcoin-flash", "title": "Bitcoin Flash (BTF)", "section": "Summary and infobox", "text": "A planned early-2018 fork that promised Dash-style instant transactions and masternodes; its fork height differs between its own site and the 2019 fork list. Fork height (site): Block 502,502, “~January 5, 2018” [btfl-site]; Fork height (2019 list): 508,000 [bth-review]; Block 502,502 time: 2018-01-04 08:00:26 UTC [btc-502502]; Block 508,000 time: 2018-02-06 19:28:06 UTC [btc-508000]; Technology: Dash InstantX, masternodes, “Dark Gravity Well” (site spelling) [btfl-site]; Block size limit: 16 MB [btfl-site]; Status (Feb 2019 list): “doesn't seem to exist (anymore)” [bth-review]", "aliases": "btf flash instantx masternodes", "refs": ["btc-502502", "btc-508000", "btfl-site", "bth-review"], "url": "/wiki/bitcoin-flash/"}, {"id": "bitcoin-flash#takeover", "slug": "bitcoin-flash", "title": "Bitcoin Flash (BTF)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Flash shares the BTF ticker with Bitcoin Faith, one of several ticker collisions in the fork wave, so listings that say only “BTF” need checking. [bth-review] [btfl-site]", "aliases": "btf flash instantx masternodes", "refs": ["btfl-site", "bth-review"], "url": "/wiki/bitcoin-flash/"}, {"id": "bitcoin-flash#179", "slug": "bitcoin-flash", "title": "Bitcoin Flash (BTF)", "section": "Pitch", "text": "The archived site, captured on 1 January 2018, showed a countdown “until block 502502 on Bitcoin Core chain (~January 5, 2018)” [btfl-site]. It promised instantly confirmed transactions and said the team “reused reliable & well-tested Dash InstantX technology”, with node operators earning part of the block reward as in Dash [btfl-site]. Its spec table lists a 16 MB block size limit, a retargeting algorithm it calls “Dark Gravity Well” (Dash's algorithm is named Dark Gravity Wave), masternode collateral of 1,000 BTF and two-way replay protection [btfl-site].", "aliases": "btf flash instantx masternodes", "refs": ["btfl-site"], "url": "/wiki/bitcoin-flash/"}, {"id": "bitcoin-flash#180", "slug": "bitcoin-flash", "title": "Bitcoin Flash (BTF)", "section": "Record", "text": "Bitcoin block 502,502 was mined on 4 January 2018 at 08:00:26 UTC [btc-502502]. The 2019 fork list instead gives “fork at 508000”, links the GitHub repository bitcoinflash/bitcoinflash and says the coin “doesn't seem to exist (anymore)” [bth-review]. Block 508,000 was mined on 6 February 2018 [btc-508000]. Which height was finally used is unknown to this wiki [bth-review] [btfl-site].", "aliases": "btf flash instantx masternodes", "refs": ["btc-502502", "btc-508000", "btfl-site", "bth-review"], "url": "/wiki/bitcoin-flash/"}, {"id": "bitcoin-god#infobox", "slug": "bitcoin-god", "title": "Bitcoin God (GOD)", "section": "Summary and infobox", "text": "Chandler Guo's “Christmas” fork of Bitcoin: announced for 25 December 2017 at block 501,225, it actually split on 27 December and switched to proof of stake after two super blocks. Type: Hard fork with replay protection (SIGHASH_FORK_ID) [god-readme]; Announced by: Chandler Guo, 4 Dec 2017 [god-ct]; Fork height: After block 501,225 [god-readme]; Block 501,225 time: 2017-12-27 06:55:44 UTC [btc-501225]; Consensus: Two proof-of-work super blocks from 501,226, then proof of stake [god-consensus]; Supply: 21 million [god-readme]; Ticker: GOD [god-readme]", "aliases": "god chandler guo", "refs": ["btc-501225", "god-consensus", "god-ct", "god-readme"], "url": "/wiki/bitcoin-god/"}, {"id": "bitcoin-god#takeover", "slug": "bitcoin-god", "title": "Bitcoin God (GOD)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin God is the fork era at its most self-aware. Guo framed it as candy for every holder, the README promised to end “the current Bitcoin forking chaos” by adding another fork, and Bitcoin's own block timing missed Christmas by two days. [god-ct] [god-readme] [btc-501225]", "aliases": "god chandler guo", "refs": ["btc-501225", "god-ct", "god-readme"], "url": "/wiki/bitcoin-god/"}, {"id": "bitcoin-god#183", "slug": "bitcoin-god", "title": "Bitcoin God (GOD)", "section": "Announcement", "text": "On 4 December 2017 Chandler Guo tweeted that Bitcoin God would be “forked off the main bitcoin chain at the block height of 501225, which will happen on December 25th to be symbolic of me giving candy to all Bitcoin Holders”, with 21 million coins and no premine [god-ct]. When followers asked whether it was a joke, he replied that it was real [god-news]. Guo had signed the New York Agreement earlier that year as Bitangel.com / Chandler Guo [nya-letter].", "aliases": "god chandler guo", "refs": ["god-ct", "god-news", "nya-letter"], "url": "/wiki/bitcoin-god/"}, {"id": "bitcoin-god#184", "slug": "bitcoin-god", "title": "Bitcoin God (GOD)", "section": "The fork", "text": "Bitcoin block 501,225 has a header time of 06:55:44 UTC on 27 December 2017, two days after the date Guo had picked [btc-501225]. KuCoin announced that day that the chain had forked “at around the block height of 501225” and that it would credit GOD 1:1 [kucoin-god].", "aliases": "god chandler guo", "refs": ["btc-501225", "kucoin-god"], "url": "/wiki/bitcoin-god/"}, {"id": "bitcoin-god#185", "slug": "bitcoin-god", "title": "Bitcoin God (GOD)", "section": "Design", "text": "The README describes a fork after block 501,225 with a per-block difficulty adjustment, SIGHASH_FORK_ID replay protection, addresses starting with g and a proof-of-stake consensus system [god-readme]. The client's consensus header sets SUPER_BLOCK_HEIGHT to 501,226 with two super blocks, and defines the last proof-of-work block as the second of them [god-consensus]. The README says 17 million coins would be airdropped to Bitcoin holders, 400,000 used as staking rewards and 3.6 million airdropped for charity by community vote [god-readme]. Whether the chain still runs is unknown in this wiki [god-readme].", "aliases": "god chandler guo", "refs": ["god-consensus", "god-readme"], "url": "/wiki/bitcoin-god/"}, {"id": "bitcoin-gold#infobox", "slug": "bitcoin-gold", "title": "Bitcoin Gold", "section": "Summary and infobox", "text": "The October 2017 fork that switched to GPU-mined Equihash, and later suffered repeated 51% attacks. Ticker: BTG [btk-btg]; Type: UTXO fork with new proof of work, 1 BTG per BTC [btk-btg]; Snapshot block: 491,406, 24 October 2017 [btk-btg]; First BTG block: 491,407, 12 November 2017 [btk-btg]; Proof of work: Equihash (200,9), then Equihash-BTG (144,5) from 3 July 2018 [btk-btg]; Replay protection: Two-way SIGHASH_FORKID, fork ID 79 [btk-btg]; SegWit: Kept [btk-btg]; Endowment: 100,000 BTG from the first 8,000 blocks [btk-btg]; Founder: Jack Liao (LightningASIC) [btk-btg]", "aliases": "btg equihash", "refs": ["btk-btg"], "url": "/wiki/bitcoin-gold/"}, {"id": "bitcoin-gold#takeover", "slug": "bitcoin-gold", "title": "Bitcoin Gold", "section": "Takeover view (editorial opinion)", "text": "The magazine's angle: a fork sold as “one GPU, one vote” whose public face ran a mining-hardware shop, and whose low hashrate made it a textbook case of what a minority proof-of-work chain risks. [btk-btg]", "aliases": "btg equihash", "refs": ["btk-btg"], "url": "/wiki/bitcoin-gold/"}, {"id": "bitcoin-gold#188", "slug": "bitcoin-gold", "title": "Bitcoin Gold", "section": "Launch", "text": "Bitcoin Gold took a snapshot of Bitcoin at block 491,406 on 24 October 2017, but its first own block, 491,407, came on 12 November 2017, nineteen days later [btk-btg]. Holders at the snapshot received 1 BTG per BTC [btk-btg].", "aliases": "btg equihash", "refs": ["btk-btg"], "url": "/wiki/bitcoin-gold/"}, {"id": "bitcoin-gold#189", "slug": "bitcoin-gold", "title": "Bitcoin Gold", "section": "GPU mining", "text": "The fork replaced SHA-256d with Equihash (200,9), the algorithm used by Zcash, and moved to an Equihash-BTG variant at block 536,200 on 3 July 2018 [btk-btg]. Unlike Bitcoin Cash, it kept SegWit [btk-btg].", "aliases": "btg equihash", "refs": ["btk-btg"], "url": "/wiki/bitcoin-gold/"}, {"id": "bitcoin-gold#190", "slug": "bitcoin-gold", "title": "Bitcoin Gold", "section": "People and endowment", "text": "Its founder and public face, Jack Liao, was chief executive of LightningASIC, a Hong Kong seller of mining hardware [btk-btg]. The first 8,000 blocks were mined at minimum difficulty to a 4-of-6 multisig, creating a 100,000 BTG endowment [btk-btg].", "aliases": "btg equihash", "refs": ["btk-btg"], "url": "/wiki/bitcoin-gold/"}, {"id": "bitcoin-gold#191", "slug": "bitcoin-gold", "title": "Bitcoin Gold", "section": "Attacks", "text": "In January 2020 two reorganisations of 14 and 15 blocks double-spent about 7,000 BTG combined; in July 2020 an attacker mined a 1,300-block private chain, which developers rejected with a checkpoint at block 640,650 [btk-btg].", "aliases": "btg equihash", "refs": ["btk-btg"], "url": "/wiki/bitcoin-gold/"}, {"id": "bitcoin-holocaust#infobox", "slug": "bitcoin-holocaust", "title": "Bitcoin Holocaust (BTHOL)", "section": "Summary and infobox", "text": "A November 2017 fork announcement that would invalidate every coin from block 120,001 or earlier, forking at block 501,488. Fork height: 501,488 [bthol-ann]; Block 501,488 time: 2017-12-29 00:06:52 UTC [btc-501488]; Rule change: Inputs from block 120,001 or earlier invalidated [bthol-ann]; Block size: 1MB [bthol-ann]", "aliases": "bthol holocaust", "refs": ["btc-501488", "bthol-ann"], "url": "/wiki/bitcoin-holocaust/"}, {"id": "bitcoin-holocaust#takeover", "slug": "bitcoin-holocaust", "title": "Bitcoin Holocaust (BTHOL)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: this fork's only announced design change was to invalidate every input from block 120,001 or earlier, a rule aimed at early holders. [bthol-ann]", "aliases": "bthol holocaust", "refs": ["bthol-ann"], "url": "/wiki/bitcoin-holocaust/"}, {"id": "bitcoin-holocaust#194", "slug": "bitcoin-holocaust", "title": "Bitcoin Holocaust (BTHOL)", "section": "Record", "text": "The announcement of 27 November 2017 says “We fork from the evil mainstream bitcoin chain at block 501488” [bthol-ann]. Its main rule is that “All inputs originating ON or BEFORE block 120001 will be INVALIDATED”, aimed at early holders [bthol-ann]. It says the block size stays at 1MB [bthol-ann]. Block 501,488 was mined on 29 December 2017 [btc-501488]. The linked GitHub repository holds a stock Bitcoin Core README [bthol-readme]. forkdrop's data file lists a 15,000,000 maximum supply [fd-data]. Whether a chain ran is unknown [fd-data].", "aliases": "bthol holocaust", "refs": ["btc-501488", "bthol-ann", "bthol-readme", "fd-data"], "url": "/wiki/bitcoin-holocaust/"}, {"id": "bitcoin-hot#infobox", "slug": "bitcoin-hot", "title": "Bitcoin Hot (BTH)", "section": "Summary and infobox", "text": "A December 2017 chain split at block 498,848 with a new proof of work, later listed with a 1:100 ratio and no published source code, and shelved by a claiming service in 2018. Fork height: 498,848 [bth-readme]; Block 498,848 time: 2017-12-12 04:44:12 UTC [btc-498848]; Ratio (third-party list): 1 BTC = 100 BTH [bth-review]; Source code: “no source code available” (third-party review) [bth-review]; Status: Unknown; claiming service reported the network “seems broken” (June 2018) [bth-ws]", "aliases": "bth bithot", "refs": ["btc-498848", "bth-readme", "bth-review", "bth-ws"], "url": "/wiki/bitcoin-hot/"}, {"id": "bitcoin-hot#takeover", "slug": "bitcoin-hot", "title": "Bitcoin Hot (BTH)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Hot is a clean example of the late-2017 fork wave, where a README and a block height were most of what existed, and claiming services ended up as the only record of whether the chain worked. [bth-readme] [bth-ws]", "aliases": "bth bithot", "refs": ["bth-readme", "bth-ws"], "url": "/wiki/bitcoin-hot/"}, {"id": "bitcoin-hot#197", "slug": "bitcoin-hot", "title": "Bitcoin Hot (BTH)", "section": "Fork", "text": "The Bitcoin Hot README describes a fork of the Bitcoin blockchain at block height 498848, “at roughly 12:00:00 UTC Dec 12, 2017”, after which its miners would create blocks with a new proof-of-work algorithm [bth-readme]. Bitcoin block 498,848 itself carries a header time of 04:44:12 UTC on 12 December 2017, several hours earlier than the README's estimate [btc-498848].", "aliases": "bth bithot", "refs": ["btc-498848", "bth-readme"], "url": "/wiki/bitcoin-hot/"}, {"id": "bitcoin-hot#198", "slug": "bitcoin-hot", "title": "Bitcoin Hot (BTH)", "section": "Record", "text": "A Bitcointalk list of reviewed Bitcoin forks, last updated in February 2019, gives Bitcoin Hot as “1 BTC = 100 BTH” and notes “no source code available” [bth-review]. In June 2018 the Walleting.Services claiming thread said of BTH: “Network seems broken. We are putting it on the shelf for now” [bth-ws]. A user in the same thread wrote that BTH sent to ZB.com never arrived [bth-ws].", "aliases": "bth bithot", "refs": ["bth-review", "bth-ws"], "url": "/wiki/bitcoin-hot/"}, {"id": "bitcoin-hush#infobox", "slug": "bitcoin-hush", "title": "Bitcoin Hush (BTCH)", "section": "Summary and infobox", "text": "A Komodo asset chain launched in 2018 that imported UTXO balances from HUSH, SUPERNET, DEX and BTC and described itself as a merged airdrop, not a fork. Type: Komodo asset chain, “merged airdrop” [btch-ann]; Imported UTXOs: HUSH, SUPERNET, DEX, BTC [btch-ann]; Snapshot: Block closest to, not later than, 12:00 UTC 1 Feb 2018 [btch-ann]; Total supply: 21,000,000 [btch-ann]; Named creators: jl777 (KMD) and Duke Leto (HUSH) [btch-ann]", "aliases": "btch hush komodo merged airdrop", "refs": ["btch-ann"], "url": "/wiki/bitcoin-hush/"}, {"id": "bitcoin-hush#takeover", "slug": "bitcoin-hush", "title": "Bitcoin Hush (BTCH)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Hush took BTC balances without taking Bitcoin's chain, and said so in capitals, which makes it the clearest line in this wiki between a fork and an airdrop. [btch-ann]", "aliases": "btch hush komodo merged airdrop", "refs": ["btch-ann"], "url": "/wiki/bitcoin-hush/"}, {"id": "bitcoin-hush#201", "slug": "bitcoin-hush", "title": "Bitcoin Hush (BTCH)", "section": "Merged airdrop", "text": "The announcement by clamoring on 26 January 2018 describes Bitcoin Hush as “a Komodo (KMD) asset chain with imported Unspent Transaction Output (UTXO) datasets from four different blockchains (HUSH, SUPERNET, DEX, BTC)” [btch-ann]. It adds: “It does not fork from KMD, nor does it fork from BTC or HUSH. It is technically NOT A FORK, but a merged airdrop” [btch-ann].", "aliases": "btch hush komodo merged airdrop", "refs": ["btch-ann"], "url": "/wiki/bitcoin-hush/"}, {"id": "bitcoin-hush#202", "slug": "bitcoin-hush", "title": "Bitcoin Hush (BTCH)", "section": "Details", "text": "The announcement said a block height would be chosen “closest to (but not later than) 12pm NOON UTC on Feb 1st 2018”, and that holders had to control the private keys of their transparent addresses to receive the airdrop [btch-ann]. The project's GitHub site calls BTCH “The Immaculate Merge Drop” [btch-gh]. The announcement gives a total supply of “21,000,000 coins, like Satoshi intended”, names jl777 and Duke Leto among its creators, and says the first exchange would be BarterDEX [btch-ann].", "aliases": "btch hush komodo merged airdrop", "refs": ["btch-ann", "btch-gh"], "url": "/wiki/bitcoin-hush/"}, {"id": "bitcoin-interest#infobox", "slug": "bitcoin-interest", "title": "Bitcoin Interest", "section": "Summary and infobox", "text": "A January 2018 Equihash fork that added one coin per block to an “interest pool” for holders who parked their coins. Fork height: Block 505,083 [bci-readme]; Fork time: Bitcoin block 505,083, header time 20 January 2018 02:04:45 UTC (README estimated 22 Jan) [btc-505083]; Proof of work: Equihash [bci-readme]; Reward: 12.5 BCI to the miner plus 1 BCI to the interest pool per block [bci-readme]; Supply: 22 million BCI [bci-readme]; Other: 10-minute blocks, per-block difficulty, SegWit, replay protection [bci-readme]", "aliases": "bci", "refs": ["bci-readme", "btc-505083"], "url": "/wiki/bitcoin-interest/"}, {"id": "bitcoin-interest#takeover", "slug": "bitcoin-interest", "title": "Bitcoin Interest", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: the fork that sold interest on a proof-of-work chain. Its own timing estimate was two days off, a reminder that height, not a calendar date, defines a fork. [bci-readme] [btc-505083]", "aliases": "bci", "refs": ["bci-readme", "btc-505083"], "url": "/wiki/bitcoin-interest/"}, {"id": "bitcoin-interest#205", "slug": "bitcoin-interest", "title": "Bitcoin Interest", "section": "Launch", "text": "The README announced a fork “at block height 505083, at roughly 23:59:59 UTC Jan 22, 2018” [bci-readme]. Bitcoin block 505,083 actually carries a header time of 20 January 2018, 02:04:45 UTC [btc-505083].", "aliases": "bci", "refs": ["bci-readme", "btc-505083"], "url": "/wiki/bitcoin-interest/"}, {"id": "bitcoin-interest#206", "slug": "bitcoin-interest", "title": "Bitcoin Interest", "section": "Design", "text": "Bitcoin Interest used Equihash with 10-minute blocks and difficulty recalculated every block [bci-readme]. Each block paid 12.5 BCI to the miner and 1 BCI to an interest pool, from which holders who “park” coins collect interest [bci-readme]. The supply was raised to 22 million coins, which the README attributes to listing and development costs [bci-readme].", "aliases": "bci", "refs": ["bci-readme"], "url": "/wiki/bitcoin-interest/"}, {"id": "bitcoin-king#infobox", "slug": "bitcoin-king", "title": "Bitcoin King (BCK)", "section": "Summary and infobox", "text": "A fork at block 499,999 that planned a later switch to a PoW+DPoS hybrid; its 2018 comparison chart claimed 21.21 million coins. Fork height: 499,999 [bth-review]; Block 499,999 time: 2017-12-18 18:34:47 UTC [btc-499999]; Supply (site chart): 21.21 MIL [bck-site]; Algorithm (site chart): SHA256 [bck-site]; Max block size (site chart): 8MB [bck-site]; 2019 list: “seems like a waste of my resources to compile/sync/test (sorry)” [bth-review]", "aliases": "bck king", "refs": ["bck-site", "btc-499999", "bth-review"], "url": "/wiki/bitcoin-king/"}, {"id": "bitcoin-king#takeover", "slug": "bitcoin-king", "title": "Bitcoin King (BCK)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: block 499,999 carried at least three airdrop claims — Bitcoin King, BitcoinStake and Lightning Bitcoin. [bth-review] [lbtc-about]", "aliases": "bck king", "refs": ["bth-review", "lbtc-about"], "url": "/wiki/bitcoin-king/"}, {"id": "bitcoin-king#209", "slug": "bitcoin-king", "title": "Bitcoin King (BCK)", "section": "Site", "text": "The archived site, captured on 31 August 2018 and mostly in Chinese, gives a roadmap starting on 2017.12.19 with the fork at height 499999, then a PoW+DPoS consensus change dated 2018.5.31 and fast micro-payments dated 2018.8.31 [bck-site]. Its comparison chart lists BCK with a max supply of “21.21 MIL”, SHA256 mining, 10-minute blocks and 8MB blocks [bck-site].", "aliases": "bck king", "refs": ["bck-site"], "url": "/wiki/bitcoin-king/"}, {"id": "bitcoin-king#210", "slug": "bitcoin-king", "title": "Bitcoin King (BCK)", "section": "Record", "text": "The 2019 fork list gives “fork at 499999” and the repository btcking/btcking, and says it “seems like a waste of my resources to compile/sync/test (sorry)” [bth-review]. Block 499,999 was mined on 18 December 2017 at 18:34:47 UTC [btc-499999]. The same list puts BitcoinStake at the same block [bth-review].", "aliases": "bck king", "refs": ["btc-499999", "bth-review"], "url": "/wiki/bitcoin-king/"}, {"id": "bitcoin-knots#infobox", "slug": "bitcoin-knots", "title": "Bitcoin Knots", "section": "Summary and infobox", "text": "Luke Dashjr's derivative of Bitcoin Core: the long-running alternative client that became the base of the 2025–26 anti-spam movement and of the BIP-110 split. Type: Full-node and wallet software derived from Bitcoin Core [bw-knots]; Lead maintainer: Luke Dashjr [knots-site]; Former names: Bitcoin LJR, Bitcoin Next-Test [bw-knots]; Repository: bitcoinknots/bitcoin, created 25 Feb 2016 [knots-gh]; Latest version (13 Nov 2026): 29.5.knots20260508 [knots-site]; Chain: Follows Bitcoin; BIP-110 nodes split onto their own chain in Aug 2026 [btk-blake]", "aliases": "knots luke-jr bip110 bip-110", "refs": ["btk-blake", "bw-knots", "knots-gh", "knots-site"], "url": "/wiki/bitcoin-knots/"}, {"id": "bitcoin-knots#takeover", "slug": "bitcoin-knots", "title": "Bitcoin Knots", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Knots spent a decade as a niche client and then became a political party. Bitcoin Takeover's BLAKE2b essay calls it the home of the opposition to Core's 2025 OP_RETURN change. [btk-blake]", "aliases": "knots luke-jr bip110 bip-110", "refs": ["btk-blake"], "url": "/wiki/bitcoin-knots/"}, {"id": "bitcoin-knots#213", "slug": "bitcoin-knots", "title": "Bitcoin Knots", "section": "What it is", "text": "The Bitcoin Wiki describes Knots, formerly Bitcoin LJR and Bitcoin Next-Test, as a derivative of Bitcoin Core primarily maintained by Luke Dashjr, with all of Core's functionality and more [bw-knots]. The project's website says that only Luke Dashjr, as lead maintainer, may post to its announcement mailing list [knots-site]. The current GitHub repository was created on 25 February 2016 [knots-gh].", "aliases": "knots luke-jr bip110 bip-110", "refs": ["bw-knots", "knots-gh", "knots-site"], "url": "/wiki/bitcoin-knots/"}, {"id": "bitcoin-knots#214", "slug": "bitcoin-knots", "title": "Bitcoin Knots", "section": "Policy differences", "text": "The Bitcoin Wiki's 2018 feature list includes full replace-by-fee enabled by default from version 0.16, a blockmaxsize option, coin-age priority and a bytespersigopstrict option “to detect certain kinds of spam” [bw-knots]. On S16 E56 Super Testnet argued that because Knots nodes do not relay filtered transactions, they “use objectively less bandwidth than Bitcoin Core” for that traffic [ep-s16e56-knots].", "aliases": "knots luke-jr bip110 bip-110", "refs": ["bw-knots", "ep-s16e56-knots"], "url": "/wiki/bitcoin-knots/"}, {"id": "bitcoin-knots#215", "slug": "bitcoin-knots", "title": "Bitcoin Knots", "section": "Politics and BIP-110", "text": "Bitcoin Takeover's BLAKE2b essay describes Knots, “the alternative client Luke Dashjr has maintained for over a decade”, as the home of the opposition after Bitcoin Core loosened its OP_RETURN policy in 2025 [btk-blake]. Knots nodes enforcing BIP-110 began rejecting non-signalling blocks at height 961,632 on 8 August 2026, which split them from Bitcoin; see Bitcoin BLAKE2b [btk-blake]. On S17 E17 Vlad discussed the possibility of that Knots/BIP-110 fork before it happened [ep-s17e17-bip110].", "aliases": "knots luke-jr bip110 bip-110", "refs": ["btk-blake", "ep-s17e17-bip110"], "url": "/wiki/bitcoin-knots/"}, {"id": "bitcoin-knots#216", "slug": "bitcoin-knots", "title": "Bitcoin Knots", "section": "Versions", "text": "On 13 November 2026 the website offered version 29.5.knots20260508 for macOS, Windows and Linux [knots-site]. The BLAKE2b chain's infobox lists Bitcoin Knots 29.4.1.knots20260508 as its client [btk-blake].", "aliases": "knots luke-jr bip110 bip-110", "refs": ["btk-blake", "knots-site"], "url": "/wiki/bitcoin-knots/"}, {"id": "bitcoin-knots#217", "slug": "bitcoin-knots", "title": "Bitcoin Knots", "section": "Heard on Bitcoin Takeover", "text": "Citing Murch's count of changed lines, Michael Tidwell said on S16 E42 (September 2025) that “there's more lines of code that are different between Knots and Core than there were total lines in the original implementation of Bitcoin”. [ep-s16e42-q2435]", "aliases": "knots luke-jr bip110 bip-110", "refs": ["ep-s16e42-q2435"], "url": "/wiki/bitcoin-knots/"}, {"id": "bitcoin-lambo#infobox", "slug": "bitcoin-lambo", "title": "Bitcoin LAMBO (BTL)", "section": "Summary and infobox", "text": "A self-described pure-speculation SHA-256 fork listed at block 515,350, with strong replay protection and 21 million coins. Fork height (forkdrop): 515,350 [fd-data]; Block 515,350 time: 2018-03-27 05:46:52 UTC [btc-515350]; Algorithm: SHA256 [btl-ann]; Supply: 21,000,000 [btl-ann]", "aliases": "btl lambo psd", "refs": ["btc-515350", "btl-ann", "fd-data"], "url": "/wiki/bitcoin-lambo/"}, {"id": "bitcoin-lambo#takeover", "slug": "bitcoin-lambo", "title": "Bitcoin LAMBO (BTL)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin LAMBO is the fork wave describing itself: its thread calls it pure speculation driven. [btl-ann]", "aliases": "btl lambo psd", "refs": ["btl-ann"], "url": "/wiki/bitcoin-lambo/"}, {"id": "bitcoin-lambo#220", "slug": "bitcoin-lambo", "title": "Bitcoin LAMBO (BTL)", "section": "Record", "text": "The announcement of 28 May 2018 calls the coin “The first PSD COIN, pure specultation driven” [btl-ann]. It lists strong replay protection, SHA256 and a 21000000 supply [btl-ann]. The README is the stock Bitcoin Core text renamed to BitcoinLambo [btl-readme]. forkdrop's data file gives block 515350 and a date of 2018-03-27 [fd-data]. Block 515,350 was mined on 27 March 2018 [btc-515350]. That is two months before the 28 May 2018 announcement, so either the snapshot was set retroactively or forkdrop's row is wrong; this wiki has not resolved which [fd-data]. Its state after 2018 is unknown [fd-data].", "aliases": "btl lambo psd", "refs": ["btc-515350", "btl-ann", "btl-readme", "fd-data"], "url": "/wiki/bitcoin-lambo/"}, {"id": "bitcoin-lightning-bltg#infobox", "slug": "bitcoin-lightning-bltg", "title": "Bitcoin Lightning (BLTG)", "section": "Summary and infobox", "text": "A January 2018 proof-of-stake masternode coin named Bitcoin Lightning, swapped in late 2018 for the Block-Logic BLTG coin. Launch thread: 5 January 2018 [bltg-ann]; Type: PoS with masternodes [bltg-ann]; Swap: 22 Oct – 4 Dec 2018, to Block-Logic [bltg-ann]; New algorithm: quark [bltg-ann]; Masternode collateral (new): 12,000 coins [bltg-ann]", "aliases": "bltg bitcoin lightning block-logic", "refs": ["bltg-ann"], "url": "/wiki/bitcoin-lightning-bltg/"}, {"id": "bitcoin-lightning-bltg#takeover", "slug": "bitcoin-lightning-bltg", "title": "Bitcoin Lightning (BLTG)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: “Bitcoin Lightning” is a name, not a Bitcoin fork — and not to be confused with Lightning Bitcoin or the Lightning Network. [bltg-ann]", "aliases": "bltg bitcoin lightning block-logic", "refs": ["bltg-ann"], "url": "/wiki/bitcoin-lightning-bltg/"}, {"id": "bitcoin-lightning-bltg#223", "slug": "bitcoin-lightning-bltg", "title": "Bitcoin Lightning (BLTG)", "section": "Launch", "text": "The launch thread was opened by aperture on 5 January 2018 with the title “[LAUNCH] | BLTG | Bitcoin Lightning | Masternodes | PoS” [bltg-ann]. Early replies on that day asked for the source code and questioned whether mining had ended [bltg-ann].", "aliases": "bltg bitcoin lightning block-logic", "refs": ["bltg-ann"], "url": "/wiki/bitcoin-lightning-bltg/"}, {"id": "bitcoin-lightning-bltg#224", "slug": "bitcoin-lightning-bltg", "title": "Bitcoin Lightning (BLTG)", "section": "Swap to Block-Logic", "text": "The current, edited first post says “Bitcoin Lightning old BLTG will be swapped for new BLTG block logic technology group” [bltg-ann]. It states “The Swap will start on October 22, 2018 and last until December 4, 2018” and lists the new coin's quark algorithm, 60-second blocks and a 12,000-coin masternode collateral [bltg-ann]. The unrelated Lightning Bitcoin (LBTC) was a fork of the Bitcoin chain at block 499,999 [lbtc-about].", "aliases": "bltg bitcoin lightning block-logic", "refs": ["bltg-ann", "lbtc-about"], "url": "/wiki/bitcoin-lightning-bltg/"}, {"id": "bitcoin-lite#infobox", "slug": "bitcoin-lite", "title": "Bitcoin LITE (BTCL)", "section": "Summary and infobox", "text": "A fork announced for 30 January 2018 whose archived site showed only a countdown and “Coming soon...”; the 2019 list marked it abandoned. Fork date: “fork on 30th January 2018” [bth-review]; Fork height: Unknown [bth-review]; Source code: “no source code available” [bth-review]; Status (Feb 2019 list): “seems abandoned” [bth-review]", "aliases": "btcl lite", "refs": ["bth-review"], "url": "/wiki/bitcoin-lite/"}, {"id": "bitcoin-lite#takeover", "slug": "bitcoin-lite", "title": "Bitcoin LITE (BTCL)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin LITE is the thinnest record in the fork list — a date, a site and no code. [bth-review]", "aliases": "btcl lite", "refs": ["bth-review"], "url": "/wiki/bitcoin-lite/"}, {"id": "bitcoin-lite#227", "slug": "bitcoin-lite", "title": "Bitcoin LITE (BTCL)", "section": "Record", "text": "The 2019 fork list gives “Bitcoin LITE (BTCL)”, “fork on 30th January 2018”, the site bitcoinlite.us and “no source code available”, and says it “seems abandoned” [bth-review]. It gives no fork height [bth-review].", "aliases": "btcl lite", "refs": ["bth-review"], "url": "/wiki/bitcoin-lite/"}, {"id": "bitcoin-lite#228", "slug": "bitcoin-lite", "title": "Bitcoin LITE (BTCL)", "section": "Site", "text": "The site's archived copy of 17 January 2018 shows only “Bitcoin Lite hard fork”, a countdown marked approximate and “Coming soon...” [btcl-site]. It lists countries that had “contributed to the project”: Belarus, China, India, Italy, Moldova, Russia and the USA [btcl-site].", "aliases": "btcl lite", "refs": ["btcl-site"], "url": "/wiki/bitcoin-lite/"}, {"id": "bitcoin-lunar#infobox", "slug": "bitcoin-lunar", "title": "Bitcoin Lunar (BCL)", "section": "Summary and infobox", "text": "A 2018 fork listing whose archived site only promised a website and white paper for the vernal equinox of 2018. Fork block: Unknown (forkdrop: ???) [fd-data]; Date (forkdrop): 2018-03-20 [fd-data]; forkdrop reason: “Inactivity” [fd-data]", "aliases": "bcl lunar", "refs": ["fd-data"], "url": "/wiki/bitcoin-lunar/"}, {"id": "bitcoin-lunar#takeover", "slug": "bitcoin-lunar", "title": "Bitcoin Lunar (BCL)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Lunar never got past a coming-soon page in the captures found. [lunar-site]", "aliases": "bcl lunar", "refs": ["lunar-site"], "url": "/wiki/bitcoin-lunar/"}, {"id": "bitcoin-lunar#231", "slug": "bitcoin-lunar", "title": "Bitcoin Lunar (BCL)", "section": "Record", "text": "The archived site, captured on 4 April 2018, reads “Bitcoin Lunar (BCL) Website & Whitepaper, Vernal Equinox 2018” and points to Twitter for updates [lunar-site]. forkdrop's data file gives fork block “???”, a date of 2018-03-20 and the reason “Inactivity” [fd-data]. No chain or code was found [fd-data].", "aliases": "bcl lunar", "refs": ["fd-data", "lunar-site"], "url": "/wiki/bitcoin-lunar/"}, {"id": "bitcoin-master#infobox", "slug": "bitcoin-master", "title": "BitcoinMaster (BCM)", "section": "Summary and infobox", "text": "A 1:1 fork announced for block 515,000 by a bounty poster who said he was not its developer. Fork height: 515,000 [bcm-ann]; Block 515,000 time: 2018-03-24 19:52:57 UTC [btc-515000]; Ratio: 1:1 [bcm-ann]; forkdrop reason: “Homepage Down” [fd-data]", "aliases": "bcm master bitcoinmaster", "refs": ["bcm-ann", "btc-515000", "fd-data"], "url": "/wiki/bitcoin-master/"}, {"id": "bitcoin-master#takeover", "slug": "bitcoin-master", "title": "BitcoinMaster (BCM)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: BitcoinMaster's thread was run by a bounty poster, and its text was all images. [bcm-ann]", "aliases": "bcm master bitcoinmaster", "refs": ["bcm-ann"], "url": "/wiki/bitcoin-master/"}, {"id": "bitcoin-master#234", "slug": "bitcoin-master", "title": "BitcoinMaster (BCM)", "section": "Record", "text": "The thread of 21 March 2018 is titled “[ANN][FORK] BitcoinMaster (BCM) - Bitcoin faster - Fork at block 515000 1:1” [bcm-ann]. Its poster writes “I'm not the dev of BitcoinMaster”, and the rest of the first post is images from bcmaster.org [bcm-ann]. Block 515,000 was mined on 24 March 2018 [btc-515000]. forkdrop's data file files it among historic entries with the reason “Homepage Down” [fd-data].", "aliases": "bcm master bitcoinmaster", "refs": ["bcm-ann", "btc-515000", "fd-data"], "url": "/wiki/bitcoin-master/"}, {"id": "bitcoin-metal#infobox", "slug": "bitcoin-metal", "title": "Bitcoin Metal (BTCM)", "section": "Summary and infobox", "text": "An April 2018 announcement of a 1:1 Bitcoin hard fork with an online wallet; forkdrop has no fork block for it. Announced: 2 April 2018 [btcm-ann]; Ratio: 1 BTC = 1 BTCM [btcm-ann]; Fork block: Unknown (forkdrop: ???) [fd-data]; Date (forkdrop): 2018-05-01 [fd-data]", "aliases": "btcm metal", "refs": ["btcm-ann", "fd-data"], "url": "/wiki/bitcoin-metal/"}, {"id": "bitcoin-metal#takeover", "slug": "bitcoin-metal", "title": "Bitcoin Metal (BTCM)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Metal pitched itself against scam fork wallets while asking holders to use its own online wallet. [btcm-ann]", "aliases": "btcm metal", "refs": ["btcm-ann"], "url": "/wiki/bitcoin-metal/"}, {"id": "bitcoin-metal#237", "slug": "bitcoin-metal", "title": "Bitcoin Metal (BTCM)", "section": "Pitch", "text": "The Bitcointalk announcement of 2 April 2018 promises “free airdrops: 1 BTC = 1 BTCM” at the fork [btcm-ann]. It says the team wanted “to avoid all scam sites like previous hardforks” and offers an all-in-one online wallet [btcm-ann].", "aliases": "btcm metal", "refs": ["btcm-ann"], "url": "/wiki/bitcoin-metal/"}, {"id": "bitcoin-metal#238", "slug": "bitcoin-metal", "title": "Bitcoin Metal (BTCM)", "section": "Record", "text": "forkdrop's data file lists a registration airdrop with fork block “???”, a date of 2018-05-01 and a 21,000,000 maximum supply [fd-data]. No fork block or chain data was found, so whether it launched is unknown [fd-data].", "aliases": "btcm metal", "refs": ["fd-data"], "url": "/wiki/bitcoin-metal/"}, {"id": "bitcoin-minor#infobox", "slug": "bitcoin-minor", "title": "Bitcoin Minor (BTM)", "section": "Summary and infobox", "text": "A fork listed by forkdrop at block 498,754 with 28 million coins; no other source was found. Fork height (forkdrop): 498,754 [fd-data]; Block 498,754 time: 2017-12-11 15:07:40 UTC [btc-498754]; Max supply (forkdrop): 28,000,000 [fd-data]; forkdrop reason: “Homepage Down” [fd-data]", "aliases": "btm minor", "refs": ["btc-498754", "fd-data"], "url": "/wiki/bitcoin-minor/"}, {"id": "bitcoin-minor#takeover", "slug": "bitcoin-minor", "title": "Bitcoin Minor (BTM)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Minor is a single-source entry; only forkdrop's row remains. [fd-data]", "aliases": "btm minor", "refs": ["fd-data"], "url": "/wiki/bitcoin-minor/"}, {"id": "bitcoin-minor#241", "slug": "bitcoin-minor", "title": "Bitcoin Minor (BTM)", "section": "Record", "text": "forkdrop's data file lists Bitcoin Minor with ticker BTM, block 498754, a date of 2017-12-11, a 1:1 ratio and a maximum supply of 28,000,000 [fd-data]. Block 498,754 was mined on 11 December 2017, the same height as Bitcoin@CBC [btc-498754]. forkdrop files it among historic entries with the reason “Homepage Down” [fd-data]. No 2017-2018 capture of bitcoinminor.org, code or announcement was found [fd-data].", "aliases": "btm minor", "refs": ["btc-498754", "fd-data"], "url": "/wiki/bitcoin-minor/"}, {"id": "bitcoin-nano#infobox", "slug": "bitcoin-nano", "title": "Bitcoin Nano (BTN)", "section": "Summary and infobox", "text": "A snapshot fork of Bitcoin at block 501,888 at 1 BTC = 1,000 BTN, with Equihash, 8 MB blocks and planned EVM side chains; a 2019 review called it abandoned. Snapshot height: 501,888 [nano-readme]; Ratio: 1 BTC = 1000 BTN [nano-readme]; Type: Snapshot fork, no shared pre-fork history [bth-review]; Proof of work: Equihash [nano-readme]; Block size: 8 MB [nano-readme]; Status (Feb 2019 list): “seems abandoned” [bth-review]", "aliases": "btn nano snapshot", "refs": ["bth-review", "nano-readme"], "url": "/wiki/bitcoin-nano/"}, {"id": "bitcoin-nano#takeover", "slug": "bitcoin-nano", "title": "Bitcoin Nano (BTN)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Nano took the same block as Bitcoin Pizza and shows the snapshot model, where a fork copies balances but not history. [nano-readme] [bth-review]", "aliases": "btn nano snapshot", "refs": ["bth-review", "nano-readme"], "url": "/wiki/bitcoin-nano/"}, {"id": "bitcoin-nano#244", "slug": "bitcoin-nano", "title": "Bitcoin Nano (BTN)", "section": "Snapshot", "text": "The README says “Bitcoin Nano (BTN) is a snapshot fork of Bitcoin” taken at block 501888, with holders receiving “1 BTC = 1000 BTN” [nano-readme]. The 2019 fork list calls it a “snapshot fork (no shared pre-fork blockchain history)” and writes the ticker as Nano [bth-review].", "aliases": "btn nano snapshot", "refs": ["bth-review", "nano-readme"], "url": "/wiki/bitcoin-nano/"}, {"id": "bitcoin-nano#245", "slug": "bitcoin-nano", "title": "Bitcoin Nano (BTN)", "section": "Design", "text": "The README lists Equihash, an 8 MB block size and smart contracts “via the side-chain technology, compatible with the Ethereum Virtual Machine (EVM)” [nano-readme]. Its numbered feature list repeats text under the wrong headings, describing side chains under “Mining Algorithm” [nano-readme]. The fork list's verdict was “seems abandoned” [bth-review].", "aliases": "btn nano snapshot", "refs": ["bth-review", "nano-readme"], "url": "/wiki/bitcoin-nano/"}, {"id": "bitcoin-neuro#infobox", "slug": "bitcoin-neuro", "title": "Bitcoin Neuro (BNR)", "section": "Summary and infobox", "text": "A fork listed by forkdrop at block 501,888 with no ratio, supply or links; no other source was found. Fork height (forkdrop): 501,888 [fd-data]; Block 501,888 time: 2017-12-31 12:32:38 UTC [btc-501888]; forkdrop reason: “Inactivity” [fd-data]", "aliases": "bnr neuro", "refs": ["btc-501888", "fd-data"], "url": "/wiki/bitcoin-neuro/"}, {"id": "bitcoin-neuro#takeover", "slug": "bitcoin-neuro", "title": "Bitcoin Neuro (BNR)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Neuro is the thinnest entry in the wiki, a name, a ticker and a block height. [fd-data]", "aliases": "bnr neuro", "refs": ["fd-data"], "url": "/wiki/bitcoin-neuro/"}, {"id": "bitcoin-neuro#248", "slug": "bitcoin-neuro", "title": "Bitcoin Neuro (BNR)", "section": "Record", "text": "forkdrop's data file lists Bitcoin Neuro with ticker BNR, block 501888 and a date of 2017-12-31, with ratio, supply and source chain all “???” [fd-data]. Block 501,888 was mined on 31 December 2017 [btc-501888]. forkdrop files it among historic entries with the reason “Inactivity”, and gives no project site, code or announcement [fd-data].", "aliases": "bnr neuro", "refs": ["btc-501888", "fd-data"], "url": "/wiki/bitcoin-neuro/"}, {"id": "bitcoin-new#infobox", "slug": "bitcoin-new", "title": "Bitcoin New (BTN)", "section": "Summary and infobox", "text": "A Christmas 2017 fork at block 501,000 with a new proof-of-work and a 2.1 billion supply; different from New Bitcoin (NBTC). Fork height: 501,000 [btn-readme]; Block 501,000 time: 2017-12-25 17:42:45 UTC [btc-501000]; Max supply (forkdrop): 2.1 Billion [fd-data]; forkdrop reason: “Reneged” [fd-data]; Status (Feb 2019 list): “doesn't seem to exist (anymore)” [bth-review]", "aliases": "btn bitcoin new", "refs": ["btc-501000", "bth-review", "btn-readme", "fd-data"], "url": "/wiki/bitcoin-new/"}, {"id": "bitcoin-new#takeover", "slug": "bitcoin-new", "title": "Bitcoin New (BTN)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin New and New Bitcoin are two different December 2017 forks with almost the same name. [btn-readme] [fd-data]", "aliases": "btn bitcoin new", "refs": ["btn-readme", "fd-data"], "url": "/wiki/bitcoin-new/"}, {"id": "bitcoin-new#251", "slug": "bitcoin-new", "title": "Bitcoin New (BTN)", "section": "Design", "text": "The README says Bitcoin New “is a fork of the Bitcoin blockchain that will occur at block height 501000”, around 25 December 2017, after which miners would use a new proof-of-work algorithm [btn-readme]. Block 501,000 was mined on 25 December 2017 at 17:42 UTC [btc-501000]. forkdrop's data file gives a maximum supply of 2.1 Billion [fd-data].", "aliases": "btn bitcoin new", "refs": ["btc-501000", "btn-readme", "fd-data"], "url": "/wiki/bitcoin-new/"}, {"id": "bitcoin-new#252", "slug": "bitcoin-new", "title": "Bitcoin New (BTN)", "section": "Record", "text": "The 2019 fork list says “no source code available” and that it “doesn't seem to exist (anymore)” [bth-review]. The “no source code” note conflicts with the GitHub repository that forkdrop links [fd-data], whose README was still online on 13 November 2026 [btn-readme]. forkdrop's data file files Bitcoin New among historic entries with the reason “Reneged” [fd-data]. Not to be confused with New Bitcoin (NBTC) [fd-data].", "aliases": "btn bitcoin new", "refs": ["bth-review", "btn-readme", "fd-data"], "url": "/wiki/bitcoin-new/"}, {"id": "bitcoin-ocho#infobox", "slug": "bitcoin-ocho", "title": "Bitcoin Ocho (OCHO)", "section": "Summary and infobox", "text": "A December 2016 coin with 8MB blocks on pre-SegWit Bitcoin code, announced by goku1997 after a rejected pull request. Announced: 12 December 2016 [ocho-ann]; Block size: 8MB [ocho-readme]; Fork block: Unknown (forkdrop: ???) [fd-data]; forkdrop reason: “Inactivity” [fd-data]", "aliases": "ocho 8mb goku1997", "refs": ["fd-data", "ocho-ann", "ocho-readme"], "url": "/wiki/bitcoin-ocho/"}, {"id": "bitcoin-ocho#takeover", "slug": "bitcoin-ocho", "title": "Bitcoin Ocho (OCHO)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Ocho came out of a rejected block-size pull request to Bitcoin Core in December 2016. [ocho-ann]", "aliases": "ocho 8mb goku1997", "refs": ["ocho-ann"], "url": "/wiki/bitcoin-ocho/"}, {"id": "bitcoin-ocho#255", "slug": "bitcoin-ocho", "title": "Bitcoin Ocho (OCHO)", "section": "Record", "text": "The announcement of 12 December 2016 says “Ocho is a fork of Bitcoin pre-segwit, and with the blocksize hard set to 8MB” [ocho-ann]. It links Bitcoin pull request 9324 and says the author's ideas were rejected [ocho-ann]. The README calls it a currency “that uses 8MB blocks” [ocho-readme]. The first post says “Modifying the genesis block is the next to come”, so whether it shared Bitcoin's history is unknown [ocho-ann]. forkdrop's data file gives a date of 2018-01-31, fork block “???” and the reason “Inactivity” [fd-data].", "aliases": "ocho 8mb goku1997", "refs": ["fd-data", "ocho-ann", "ocho-readme"], "url": "/wiki/bitcoin-ocho/"}, {"id": "bitcoin-oil#infobox", "slug": "bitcoin-oil", "title": "Bitcoin Oil (OIL)", "section": "Summary and infobox", "text": "A February 2019 Business Wire announcement of a planned proof-of-stake Bitcoin fork; no fork block was ever set in the sources found. Announced: 4 February 2019 (press release) [oil-bw]; Fork block: Unknown (forkdrop: TBT / TBD) [fd-data]; Planned consensus: Proof of stake [oil-bw]; Max supply (forkdrop): 21 Billion [fd-data]; Ticker: OIL in the release; BTCO in forkdrop [fd-data]", "aliases": "oil bitcoin oil btco businesswire hannah paddock", "refs": ["fd-data", "oil-bw"], "url": "/wiki/bitcoin-oil/"}, {"id": "bitcoin-oil#takeover", "slug": "bitcoin-oil", "title": "Bitcoin Oil (OIL)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Oil is an announcement, not a recorded chain. It is listed so the name is not confused with the 2017 Oil Bitcoin fork. [oil-bw] [fd-data]", "aliases": "oil bitcoin oil btco businesswire hannah paddock", "refs": ["fd-data", "oil-bw"], "url": "/wiki/bitcoin-oil/"}, {"id": "bitcoin-oil#258", "slug": "bitcoin-oil", "title": "Bitcoin Oil (OIL)", "section": "Announcement", "text": "A Business Wire release dated 4 February 2019 says “Bitcoin Oil, or the Company, announces its plan to create a highly innovative Bitcoin fork and generate crypto-assets which the Company refers to as Bitcoin Oil, or OIL” [oil-bw]. It says the company would use proof of stake to address Bitcoin's energy use, and it names Hannah Paddock as chief marketing officer [oil-bw]. It describes an “SSPSS” strategy covering stability, sustainability, privacy, smart sidechains and scalability, and promises a “forthcoming white paper” [oil-bw].", "aliases": "oil bitcoin oil btco businesswire hannah paddock", "refs": ["oil-bw"], "url": "/wiki/bitcoin-oil/"}, {"id": "bitcoin-oil#259", "slug": "bitcoin-oil", "title": "Bitcoin Oil (OIL)", "section": "Record", "text": "The release itself warns that “there can be no assurance that any of these transactions will be completed” [oil-bw]. forkdrop's data file lists Bitcoin Oil with ticker BTCO, fork block “TBT”, fork date “TBD” and a maximum supply of 21 Billion [fd-data]. No fork block, chain or software release was found for this project. Whether it ever launched is unknown [fd-data].", "aliases": "oil bitcoin oil btco businesswire hannah paddock", "refs": ["fd-data", "oil-bw"], "url": "/wiki/bitcoin-oil/"}, {"id": "bitcoin-oil#260", "slug": "bitcoin-oil", "title": "Bitcoin Oil (OIL)", "section": "Name clash", "text": "It is unrelated to Oil Bitcoin (OBTC), the 2017 fork at block 498,888 [obtc-readme].", "aliases": "oil bitcoin oil btco businesswire hannah paddock", "refs": ["obtc-readme"], "url": "/wiki/bitcoin-oil/"}, {"id": "bitcoin-ore#infobox", "slug": "bitcoin-ore", "title": "Bitcoin Ore (BCO)", "section": "Summary and infobox", "text": "A proof-of-capacity fork whose first coins were issued at block 501,949 only to users of four exchanges, while its team weighed basing it on United Bitcoin instead. Exchange issuance height: 501,949 [bco-site]; Block 501,949 time: 2017-12-31 22:53:08 UTC [btc-501949]; Mining: Proof of Capacity (planned) [bco-site]; Ratio: 1 BTC : 1 BCO [bco-site]; Block size: 8MB, 5-minute blocks (TBC) [bco-site]; Source code: “no source code available” [bth-review]", "aliases": "bco ore proof of capacity poc", "refs": ["bco-site", "btc-501949", "bth-review"], "url": "/wiki/bitcoin-ore/"}, {"id": "bitcoin-ore#takeover", "slug": "bitcoin-ore", "title": "Bitcoin Ore (BCO)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Ore's first issuance existed only on exchange ledgers, and its team said it might base the coin on United Bitcoin rather than Bitcoin. [bco-site]", "aliases": "bco ore proof of capacity poc", "refs": ["bco-site"], "url": "/wiki/bitcoin-ore/"}, {"id": "bitcoin-ore#263", "slug": "bitcoin-ore", "title": "Bitcoin Ore (BCO)", "section": "Pitch", "text": "The archived site, captured on 20 February 2018, calls BCO “A brand new POC mining ecosystem for everyone”, letting users mine with unused hard disk space [bco-site]. Its fork rules give 1 BTC to 1 BCO, a total supply of 21,000,000 and “Proof of Capacity (POC)” mining, with 8MB blocks every 5 minutes marked as to be confirmed [bco-site].", "aliases": "bco ore proof of capacity poc", "refs": ["bco-site"], "url": "/wiki/bitcoin-ore/"}, {"id": "bitcoin-ore#264", "slug": "bitcoin-ore", "title": "Bitcoin Ore (BCO)", "section": "The exchange issuance", "text": "A notice dated 2017/12/31 says the team had agreements with zb.com, aex.com, exx.com and lbank.info, and that the main chain would “issue Bitcoin Ore to users of these four exchanges at block height of 501949” [bco-site]. Block 501,949 was mined on 31 December 2017 [btc-501949]. The same notice says “In addition to classic Bitcoin we are also looking at United Bitcoin (UBTC), which is a strong alternative” as a base, meaning United Bitcoin [bco-site].", "aliases": "bco ore proof of capacity poc", "refs": ["bco-site", "btc-501949"], "url": "/wiki/bitcoin-ore/"}, {"id": "bitcoin-ore#265", "slug": "bitcoin-ore", "title": "Bitcoin Ore (BCO)", "section": "Record", "text": "The 2019 fork list gives “fork at 501949” and “no source code available” [bth-review].", "aliases": "bco ore proof of capacity poc", "refs": ["bth-review"], "url": "/wiki/bitcoin-ore/"}, {"id": "bitcoin-origin#infobox", "slug": "bitcoin-origin", "title": "Bitcoin Origin (ORI)", "section": "Summary and infobox", "text": "A 2018 plan for a five-way multi-fork of BTC, BCH, ETH, LTC and Dash, paying holders by the USD value of their coins; no fork block was set. Source coins: BTC, BCH, ETH, LTC, Dash [origin-site]; Allocation: By USD value of holdings [origin-site]; Fork block: Unknown (forkdrop: TBD) [fd-data]; Max supply (forkdrop): 35 Billion [fd-data]", "aliases": "ori origin multi-fork", "refs": ["fd-data", "origin-site"], "url": "/wiki/bitcoin-origin/"}, {"id": "bitcoin-origin#takeover", "slug": "bitcoin-origin", "title": "Bitcoin Origin (ORI)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Origin weighted its airdrop by dollar value across five chains rather than by coin count. [origin-site]", "aliases": "ori origin multi-fork", "refs": ["origin-site"], "url": "/wiki/bitcoin-origin/"}, {"id": "bitcoin-origin#268", "slug": "bitcoin-origin", "title": "Bitcoin Origin (ORI)", "section": "Record", "text": "The archived site, captured on 4 May 2018, promises an “Innovative, 5-way multi-fork of Bitcoin, Bitcoin Cash, Ethereum, Litecoin and Dash” [origin-site]. Holders would be “awarded Bitcoin Origin in proportion to the United States Dollar (USD) value of their original holdings” [origin-site]. It describes a Proof-of-Ambassador consensus [origin-site]. forkdrop's data file gives fork block and date as “TBD” and a 35 Billion maximum supply [fd-data]. Whether it launched is unknown [fd-data].", "aliases": "ori origin multi-fork", "refs": ["fd-data", "origin-site"], "url": "/wiki/bitcoin-origin/"}, {"id": "bitcoin-parallel#infobox", "slug": "bitcoin-parallel", "title": "Bitcoin Parallel (BCP)", "section": "Summary and infobox", "text": "A CryptoNight two-token project (BCP and BCPC) claimable by BTC holders at block 507,000, with a claim rate that shrank over time. Snapshot height: 507,000 [bcp-medium]; Block 507,000 time: 2018-01-31 18:58:44 UTC [btc-507000]; Claims opened: 12 Feb 2018, 9:00 GMT [bcp-medium]; Day-one rate: 1 BCP and 1,000 BCPC per BTC [bcp-medium]; Algorithm: Optimized CryptoNight [bcp-site]", "aliases": "bcp bcpc parallel cryptonight", "refs": ["bcp-medium", "bcp-site", "btc-507000"], "url": "/wiki/bitcoin-parallel/"}, {"id": "bitcoin-parallel#takeover", "slug": "bitcoin-parallel", "title": "Bitcoin Parallel (BCP)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Parallel paid less the later a holder claimed, and handed unclaimed coins to its own foundation. [bcp-medium]", "aliases": "bcp bcpc parallel cryptonight", "refs": ["bcp-medium"], "url": "/wiki/bitcoin-parallel/"}, {"id": "bitcoin-parallel#271", "slug": "bitcoin-parallel", "title": "Bitcoin Parallel (BCP)", "section": "Claim", "text": "A Medium post signed by the Bitcoin Parallel Foundation on 12 February 2018 says “BTC holders at block height 507,000 can claim your BCP and BCPC now” [bcp-medium]. Block 507,000 was mined on 31 January 2018 [btc-507000]. The first day paid 1 BCP and 1,000 BCPC per BTC, then the rate fell 2% a day to 50%, then 1% a week for 50 weeks [bcp-medium]. Claimants had 365 days, and “All unclaimed BCP and BCPC will be managed by the Foundation for community building, project development and promotion” [bcp-medium].", "aliases": "bcp bcpc parallel cryptonight", "refs": ["bcp-medium", "btc-507000"], "url": "/wiki/bitcoin-parallel/"}, {"id": "bitcoin-parallel#272", "slug": "bitcoin-parallel", "title": "Bitcoin Parallel (BCP)", "section": "Design", "text": "The archived site describes BCPC as a clearing currency with a three-second block time and says “BCP utilizes an optimized CryptoNight algorithm” [bcp-site]. forkdrop's data file lists it as a registration airdrop with a 21,000,000 maximum supply [fd-data]. Its state after 2018 is unknown [fd-data].", "aliases": "bcp bcpc parallel cryptonight", "refs": ["bcp-site", "fd-data"], "url": "/wiki/bitcoin-parallel/"}, {"id": "bitcoin-pay#infobox", "slug": "bitcoin-pay", "title": "Bitcoin Pay (BTP)", "section": "Summary and infobox", "text": "A December 2017 fork at block 499,345 whose first balances were snapshotted by two exchanges; no source code was found. Fork height: 499,345 [bpay-site]; Block 499,345 time: 2017-12-15 00:15:00 UTC (08:15 UTC+8) [btc-499345]; Ratio: 1 BTC = 10 BTP [bth-review]; Mining: CPU mining [bpay-site]; Supply: 2.1 Billion [bpay-site]; Source code: “no source code available” [bth-review]", "aliases": "btp bitcoin pay easypay", "refs": ["bpay-site", "btc-499345", "bth-review"], "url": "/wiki/bitcoin-pay/"}, {"id": "bitcoin-pay#takeover", "slug": "bitcoin-pay", "title": "Bitcoin Pay (BTP)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Pay's own fork notice gave the time as 8:15 Beijing time, which is exactly the block's header time of 00:15 UTC. [bpay-site] [btc-499345]", "aliases": "btp bitcoin pay easypay", "refs": ["bpay-site", "btc-499345"], "url": "/wiki/bitcoin-pay/"}, {"id": "bitcoin-pay#275", "slug": "bitcoin-pay", "title": "Bitcoin Pay (BTP)", "section": "Fork notice", "text": "The archived site, captured on 1 February 2018, says “BITCOIN PAY has been successfully split at 499345 of the UTC+8 (8:15) block” and that “EXX.COM And OURDAX.COM A snapshot has been given first” [bpay-site]. Block 499,345 has a header time of 00:15:00 UTC on 15 December 2017, which is 08:15 in UTC+8 [btc-499345]. The site's project table lists “Double direction replay protection”, CPU mining and a total of 2.1 Billion [bpay-site].", "aliases": "btp bitcoin pay easypay", "refs": ["bpay-site", "btc-499345"], "url": "/wiki/bitcoin-pay/"}, {"id": "bitcoin-pay#276", "slug": "bitcoin-pay", "title": "Bitcoin Pay (BTP)", "section": "Record", "text": "The 2019 fork list gives “Bitcoin Pay (BTP) (1 BTC = 10 BTP)”, “fork at 499345” and “no source code available” [bth-review]. The ticker BTP was also used by Bitcoin Platinum [btp-site].", "aliases": "btp bitcoin pay easypay", "refs": ["bth-review", "btp-site"], "url": "/wiki/bitcoin-pay/"}, {"id": "bitcoin-pieta#infobox", "slug": "bitcoin-pieta", "title": "Bitcoin Pieta (BTP)", "section": "Summary and infobox", "text": "A January 2018 Bitcoin fork announcement with no block or date in any source; forkdrop lists a 10:1 ratio. Announced: 2 January 2018 [pieta-ann]; Fork block: Unknown (forkdrop: ???) [fd-data]; Ratio (forkdrop): 10:1 [fd-data]; forkdrop reason: “Homepage Down” [fd-data]", "aliases": "btp pieta", "refs": ["fd-data", "pieta-ann"], "url": "/wiki/bitcoin-pieta/"}, {"id": "bitcoin-pieta#takeover", "slug": "bitcoin-pieta", "title": "Bitcoin Pieta (BTP)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: replies to Bitcoin Pieta's thread asked the question most of these stubs leave open: what it does that other forks do not. [pieta-ann]", "aliases": "btp pieta", "refs": ["pieta-ann"], "url": "/wiki/bitcoin-pieta/"}, {"id": "bitcoin-pieta#279", "slug": "bitcoin-pieta", "title": "Bitcoin Pieta (BTP)", "section": "Record", "text": "The thread of 2 January 2018 says “Bitcoin Pieta is a new digital currency from fork Bitcoin” and promises mining on many kinds of devices [pieta-ann]. A reply asks “What is the main difference of PIETA with other forked coin like Bitcoin Gold, and Bitcoin Cash?” [pieta-ann] forkdrop's data file gives block and date as “???”, a 10:1 ratio, a 210,000,000 maximum supply and the reason “Homepage Down” [fd-data]. The BTP ticker is shared with three other coins in that file [fd-data].", "aliases": "btp pieta", "refs": ["fd-data", "pieta-ann"], "url": "/wiki/bitcoin-pieta/"}, {"id": "bitcoin-pizza#infobox", "slug": "bitcoin-pizza", "title": "Bitcoin Pizza (BPA)", "section": "Summary and infobox", "text": "A fork at block 501,888 at the end of 2017, announced with a 1:1 airdrop and a planned later swap to a DAG chain at one to one billion. Fork height: 501,888 [bpa-readme]; Block 501,888 time: 2017-12-31 12:32:38 UTC [btc-501888]; Ratio: BTC:BPA 1:1, later 1:1,000,000,000 to DAG BPA (announced) [bpa-ann]; Proof of work: Equihash (announced) [bpa-ann]; Block time: 120 seconds (announced) [bpa-ann]; Cap: 21,210,000 incl. 210,000 for developers and promotion (announced) [bpa-ann]", "aliases": "bpa pizza dag", "refs": ["bpa-ann", "bpa-readme", "btc-501888"], "url": "/wiki/bitcoin-pizza/"}, {"id": "bitcoin-pizza#takeover", "slug": "bitcoin-pizza", "title": "Bitcoin Pizza (BPA)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Pizza borrowed Bitcoin's most famous meme for its name, promised a DAG future, and set aside 210,000 coins for itself — the pattern of most late-2017 airdrop forks in one thread. [bpa-ann]", "aliases": "bpa pizza dag", "refs": ["bpa-ann"], "url": "/wiki/bitcoin-pizza/"}, {"id": "bitcoin-pizza#282", "slug": "bitcoin-pizza", "title": "Bitcoin Pizza (BPA)", "section": "Fork", "text": "The project's README says Bitcoin Pizza “is a fork of the Bitcoin blockchain that will occur at block height 501888, at roughly 00:00:00 UTC January 1, 2018” [bpa-readme]. Block 501,888 was in fact mined with a header time of 12:32:38 UTC on 31 December 2017 [btc-501888].", "aliases": "bpa pizza dag", "refs": ["bpa-readme", "btc-501888"], "url": "/wiki/bitcoin-pizza/"}, {"id": "bitcoin-pizza#283", "slug": "bitcoin-pizza", "title": "Bitcoin Pizza (BPA)", "section": "Announcement", "text": "The Bitcointalk announcement, opened on 12 December 2017, promised a 1:1 fork and then a swap to a DAG-based BPA at 1:1,000,000,000 [bpa-ann]. It listed Equihash, 120-second blocks and a cap of 21,210,000 coins, of which 210,000 were reserved for developers and promotion [bpa-ann]. Whether the DAG chain was ever launched is unknown to this wiki [bpa-ann].", "aliases": "bpa pizza dag", "refs": ["bpa-ann"], "url": "/wiki/bitcoin-pizza/"}, {"id": "bitcoin-platinum#infobox", "slug": "bitcoin-platinum", "title": "Bitcoin Platinum (BTP)", "section": "Summary and infobox", "text": "A December 2017 Equihash fork; Cointelegraph reported a Korean-language post calling it a scam, which the team later disowned, and the episode caused an uproar in South Korea. Announced fork: Block 498,577 (per Cointelegraph) [btp-ct]; Site countdown: “hard-forked in / 500000 blocks” [btp-site]; Proof of work: Equihash [btp-site]; Block time: 2.5 minutes [btp-site]; Replay protection: 2-way (per its site) [btp-site]; Controversy: Deleted tweets calling it a scam; team blamed one developer [btp-site]", "aliases": "btp platinum korea korean scam teenager", "refs": ["btp-ct", "btp-site"], "url": "/wiki/bitcoin-platinum/"}, {"id": "bitcoin-platinum#takeover", "slug": "bitcoin-platinum", "title": "Bitcoin Platinum (BTP)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Platinum is the fork-wave case where the story was a tweet, not a chain — and the record has two versions of who wrote it. [btp-ct] [btp-site]", "aliases": "btp platinum korea korean scam teenager", "refs": ["btp-ct", "btp-site"], "url": "/wiki/bitcoin-platinum/"}, {"id": "bitcoin-platinum#286", "slug": "bitcoin-platinum", "title": "Bitcoin Platinum (BTP)", "section": "Announcement", "text": "Cointelegraph reported on 10 December 2017 that the @bitcoinplatinum account had said its supporters would “hard fork the Bitcoin protocol at block 498,577”, without naming developers, investors or miners [btp-ct]. The project site, as archived on 11 December 2017, showed a countdown reading “Mainnet will be hard-forked in / 500000 blocks” and listed Equihash, 2.5-minute blocks and two-way replay protection [btp-site].", "aliases": "btp platinum korea korean scam teenager", "refs": ["btp-ct", "btp-site"], "url": "/wiki/bitcoin-platinum/"}, {"id": "bitcoin-platinum#287", "slug": "bitcoin-platinum", "title": "Bitcoin Platinum (BTP)", "section": "The deleted tweets", "text": "Cointelegraph, citing JoongAng, reported a creator's post: “Please forgive me. Bitcoin Platinum is a scam coin. I created the project to earn five mln Korean won ($4,590).” [btp-ct]. An apology on the archived site, in Korean, says two deleted Korean tweets were posted by one developer, “WJ Cloud”, under schedule stress, that this developer was removed, and that a young developer accused online had no involvement [btp-site]. Beyond the handle used in the project's own apology, this wiki does not name anyone involved, and it has not resolved the two accounts [btp-ct].", "aliases": "btp platinum korea korean scam teenager", "refs": ["btp-ct", "btp-site"], "url": "/wiki/bitcoin-platinum/"}, {"id": "bitcoin-point#infobox", "slug": "bitcoin-point", "title": "Bitcoin Point (POINT)", "section": "Summary and infobox", "text": "A 1:1 fork announced for block 501,000 with 21 million coins, the same height as Bitcoin New. Fork height: 501,000 [point-ann]; Block 501,000 time: 2017-12-25 17:42:45 UTC [btc-501000]; Supply: 21,000,000 [point-ann]; forkdrop reason: “Inactivity” [fd-data]", "aliases": "point", "refs": ["btc-501000", "fd-data", "point-ann"], "url": "/wiki/bitcoin-point/"}, {"id": "bitcoin-point#takeover", "slug": "bitcoin-point", "title": "Bitcoin Point (POINT)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Point's announcement was three lines and a promise of coming soon. [point-ann]", "aliases": "point", "refs": ["point-ann"], "url": "/wiki/bitcoin-point/"}, {"id": "bitcoin-point#290", "slug": "bitcoin-point", "title": "Bitcoin Point (POINT)", "section": "Record", "text": "The announcement of 21 December 2017 gives “Bitcoin Point block : 501000 Max Coin : 21,000,000” and says “comming soon” [point-ann]. Block 501,000 was mined on 25 December 2017, the same height Bitcoin New used [btc-501000] [btn-readme]. forkdrop's data file files it among historic entries with the reason “Inactivity” [fd-data].", "aliases": "point", "refs": ["btc-501000", "btn-readme", "fd-data", "point-ann"], "url": "/wiki/bitcoin-point/"}, {"id": "bitcoin-post-quantum#infobox", "slug": "bitcoin-post-quantum", "title": "Bitcoin Post-Quantum (BPQ)", "section": "Summary and infobox", "text": "A December 2018 fork announced at block 555,000 that replaced ECDSA with XMSS hash-based signatures and required holders to move coins with their old keys. Fork height: 555,000 (announced) [bpq-ann]; Block 555,000 time: 2018-12-22 23:41:03 UTC [btc-555000]; Signatures: XMSS W-OTS+, stateful hash-based [bpq-ann]; Proof of work: Equihash (96,3) [bpq-site]; Codebase: Forked from Bitcoin Core 0.16.0 [bpq-ann]; Supply: 21,000,000 BPQ, premine 1,050,000 [bpq-site]; Status: Unknown to this wiki [bpq-ann]", "aliases": "bpq post-quantum quantum xmss", "refs": ["bpq-ann", "bpq-site", "btc-555000"], "url": "/wiki/bitcoin-post-quantum/"}, {"id": "bitcoin-post-quantum#takeover", "slug": "bitcoin-post-quantum", "title": "Bitcoin Post-Quantum (BPQ)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: BPQ is the 2018 answer to a question Bitcoin still debates in 2026 — what to do with coins whose owners never move them to quantum-safe keys. BPQ's answer was to burn them. [bpq-ann]", "aliases": "bpq post-quantum quantum xmss", "refs": ["bpq-ann"], "url": "/wiki/bitcoin-post-quantum/"}, {"id": "bitcoin-post-quantum#293", "slug": "bitcoin-post-quantum", "title": "Bitcoin Post-Quantum (BPQ)", "section": "Announcement", "text": "On 10 December 2018 the Bitcointalk user pq announced “the fork of the Bitcoin blockchain that will occur on block #555000”, calling Bitcoin Post-Quantum the first Bitcoin fork “with a quantum-safe signature scheme” [bpq-ann]. The project site says “All bitcoin owners at block height #555000 own the same balance in the Bitcoin Post-Quantum network” [bpq-site]. Bitcoin block 555,000 was mined on 22 December 2018 [btc-555000].", "aliases": "bpq post-quantum quantum xmss", "refs": ["bpq-ann", "bpq-site", "btc-555000"], "url": "/wiki/bitcoin-post-quantum/"}, {"id": "bitcoin-post-quantum#294", "slug": "bitcoin-post-quantum", "title": "Bitcoin Post-Quantum (BPQ)", "section": "Design", "text": "The announcement says BPQ “implements stateful hash-based signature scheme (XMSS W-OTS+)” and that its codebase “is forked from Bitcoin Core 0.16.0 and includes support for SegWit” [bpq-ann]. The site lists Equihash “with unique parameters (96,3)”, a total supply of 21,000,000 BPQ and a premine of 1,050,000 BPQ [bpq-site].", "aliases": "bpq post-quantum quantum xmss", "refs": ["bpq-ann", "bpq-site"], "url": "/wiki/bitcoin-post-quantum/"}, {"id": "bitcoin-post-quantum#295", "slug": "bitcoin-post-quantum", "title": "Bitcoin Post-Quantum (BPQ)", "section": "Claiming and burning", "text": "To get a balance, holders “must generate a pq-address” and then “enter their old ECDSA keys into the wallet program” to move coins from their old addresses [bpq-ann]. The announcement says ECDSA support would later be “completely disabled” and that coins not moved to quantum-safe addresses by then “will be burned” [bpq-ann]. Whether the chain still runs is unknown to this wiki [bpq-ann].", "aliases": "bpq post-quantum quantum xmss", "refs": ["bpq-ann"], "url": "/wiki/bitcoin-post-quantum/"}, {"id": "bitcoin-prime#infobox", "slug": "bitcoin-prime", "title": "Bitcoin Prime (BPR)", "section": "Summary and infobox", "text": "A 2018 airdrop listing with no known fork block; its GitHub repository is gone and its domain was parked in March 2018. Fork block: Unknown (forkdrop: ???) [fd-data]; Ratio (forkdrop): 1:1 [fd-data]; Website (Mar 2018 copy): Parked domain [prime-site]", "aliases": "bpr prime", "refs": ["fd-data", "prime-site"], "url": "/wiki/bitcoin-prime/"}, {"id": "bitcoin-prime#takeover", "slug": "bitcoin-prime", "title": "Bitcoin Prime (BPR)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Prime survives only as a forkdrop row. Nothing else confirms it existed as a chain. [fd-data]", "aliases": "bpr prime", "refs": ["fd-data"], "url": "/wiki/bitcoin-prime/"}, {"id": "bitcoin-prime#298", "slug": "bitcoin-prime", "title": "Bitcoin Prime (BPR)", "section": "Record", "text": "forkdrop's data file lists Bitcoin Prime with ticker BPR, an airdrop flag, a 1:1 ratio, and fork block and date both “???” [fd-data]. It links the site bitcoinprime.org and the GitHub repository BTCPrime/BitcoinPrime [fd-data]. A March 2018 capture of bitcoinprime.org shows a parked domain offered for sale [prime-site]. The GitHub repository forkdrop links returned “not found” when this wiki checked it on 13 November 2026 [fd-data]. No announcement, block or chain was found, so the fork date and state are unknown [fd-data].", "aliases": "bpr prime", "refs": ["fd-data", "prime-site"], "url": "/wiki/bitcoin-prime/"}, {"id": "bitcoin-private#infobox", "slug": "bitcoin-private", "title": "Bitcoin Private", "section": "Summary and infobox", "text": "A 2018 “fork-merge” that combined a Bitcoin UTXO snapshot with Zclassic's chain, then went offline in October 2020. Type: Fork of Zclassic merging a snapshot of Bitcoin's UTXO set [btcp-readme]; Snapshot: Bitcoin block 511,346 and Zclassic block 272,991 [btcp-bw]; Snapshot time: Bitcoin block 511,346, header time 28 February 2018 17:06:58 UTC [btc-511346]; Airdrop: 1:1 to Bitcoin and Zclassic holders [btcp-bw]; Lead developer: Rhett Creighton, creator of Zclassic [btcp-bw]; Proof of work: Equihash, 2 MB blocks every 2.5 minutes [btcp-bw]; Status: “10/8/2020 - Current chain offline” [btcp-readme]", "aliases": "btcp zclassic zcl", "refs": ["btc-511346", "btcp-bw", "btcp-readme"], "url": "/wiki/bitcoin-private/"}, {"id": "bitcoin-private#takeover", "slug": "bitcoin-private", "title": "Bitcoin Private", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: the only fork in this batch built from two parents at once, and a warning about small Equihash chains: it was 51% attacked on a livestream within eight months. [btcp-bw] [btcp-51]", "aliases": "btcp zclassic zcl", "refs": ["btcp-51", "btcp-bw"], "url": "/wiki/bitcoin-private/"}, {"id": "bitcoin-private#301", "slug": "bitcoin-private", "title": "Bitcoin Private", "section": "Fork-merge", "text": "The project's README describes Bitcoin Private as “a fork of Zclassic, merging in a snapshotted UTXO set of Bitcoin” [btcp-readme]. BitcoinWiki dates the fork to 28 February 2018 at Bitcoin block 511,346 and Zclassic block 272,991, with holders of both coins receiving BTCP 1:1 [btcp-bw]. Bitcoin block 511,346 has a header time of 28 February 2018, 17:06:58 UTC [btc-511346].", "aliases": "btcp zclassic zcl", "refs": ["btc-511346", "btcp-bw", "btcp-readme"], "url": "/wiki/bitcoin-private/"}, {"id": "bitcoin-private#302", "slug": "bitcoin-private", "title": "Bitcoin Private", "section": "Design", "text": "BitcoinWiki describes a 21 million coin supply with 2 MB blocks every 2.5 minutes using Equihash, the Zcash-family algorithm [btcp-bw]. Its developer was Rhett Creighton, creator of Zclassic [btcp-bw].", "aliases": "btcp zclassic zcl", "refs": ["btcp-bw"], "url": "/wiki/bitcoin-private/"}, {"id": "bitcoin-private#303", "slug": "bitcoin-private", "title": "Bitcoin Private", "section": "Attack and shutdown", "text": "news.Bitcoin.com reported that on 13 October 2018 someone using the name Geocold livestreamed what they presented as a 51% attack on Bitcoin Private after gaining majority hashrate [btcp-51]. The project's legacy repository now opens with the notice “10/8/2020 - Current chain offline - New code and chain coming soon” [btcp-readme].", "aliases": "btcp zclassic zcl", "refs": ["btcp-51", "btcp-readme"], "url": "/wiki/bitcoin-private/"}, {"id": "bitcoin-pro#infobox", "slug": "bitcoin-pro", "title": "BitcoinPRO (BTP)", "section": "Summary and infobox", "text": "A SHA-256 PoW + PoS coin that gave Bitcoin holders a free distribution as of block 506,984, at 1:10 by its README. Snapshot height: 506,984 [btpro-readme]; Block 506,984 time: 2018-01-31 15:31:13 UTC [btc-506984]; Ratio: 1:10 (README); 1:1 (forkdrop) [btpro-readme]; Block time: 2 minutes [btpro-readme]; Max supply (forkdrop): 210,000,000 [fd-data]", "aliases": "btp bitcoinpro pro", "refs": ["btc-506984", "btpro-readme", "fd-data"], "url": "/wiki/bitcoin-pro/"}, {"id": "bitcoin-pro#takeover", "slug": "bitcoin-pro", "title": "BitcoinPRO (BTP)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: BitcoinPRO is one of four coins forkdrop or the forks literature calls BTP, so the ticker alone identifies nothing. [fd-data]", "aliases": "btp bitcoinpro pro", "refs": ["fd-data"], "url": "/wiki/bitcoin-pro/"}, {"id": "bitcoin-pro#306", "slug": "bitcoin-pro", "title": "BitcoinPRO (BTP)", "section": "Design", "text": "The README offers a “Free Distribution to bitcoin holders as of block #506984 (1:10)” with a two-minute block time, 25 BTP per block and 1% yearly proof-of-stake interest [btpro-readme]. The announcement thread, opened on 28 January 2018, is titled for SHA256 POW + POS and a free airdrop [btpro-ann]. Block 506,984 was mined on 31 January 2018 [btc-506984].", "aliases": "btp bitcoinpro pro", "refs": ["btc-506984", "btpro-ann", "btpro-readme"], "url": "/wiki/bitcoin-pro/"}, {"id": "bitcoin-pro#307", "slug": "bitcoin-pro", "title": "BitcoinPRO (BTP)", "section": "Record", "text": "forkdrop's data file lists the coin as both a fork and a registration airdrop, with a 1:1 ratio that conflicts with the README's 1:10, and a maximum supply of 210,000,000 [fd-data]. Its state after mid-2018 is unknown [fd-data]. The BTP ticker is shared with Bitcoin Pay, Bitcoin Platinum and Bitcoin Pieta [fd-data].", "aliases": "btp bitcoinpro pro", "refs": ["fd-data"], "url": "/wiki/bitcoin-pro/"}, {"id": "bitcoin-reference-line#infobox", "slug": "bitcoin-reference-line", "title": "Bitcoin Reference Line (BRECO)", "section": "Summary and infobox", "text": "An airdrop listed by forkdrop at block 523,118 with 143 million coins; its site later showed only a coming-soon page. Snapshot (forkdrop): Block 523,118 [fd-data]; Block 523,118 time: 2018-05-17 12:48:14 UTC [btc-523118]; Max supply (forkdrop): 143 Million [fd-data]", "aliases": "breco reference line", "refs": ["btc-523118", "fd-data"], "url": "/wiki/bitcoin-reference-line/"}, {"id": "bitcoin-reference-line#takeover", "slug": "bitcoin-reference-line", "title": "Bitcoin Reference Line (BRECO)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Reference Line is known almost only from forkdrop's row. [fd-data]", "aliases": "breco reference line", "refs": ["fd-data"], "url": "/wiki/bitcoin-reference-line/"}, {"id": "bitcoin-reference-line#310", "slug": "bitcoin-reference-line", "title": "Bitcoin Reference Line (BRECO)", "section": "Record", "text": "forkdrop's data file lists an airdrop at block 523118 on 2018-05-17, a maximum supply of 143 Million and a GitHub repository, cadkas/bitcoinreco [fd-data]. Block 523,118 was mined on 17 May 2018 [btc-523118]. A November 2019 capture of bitcoinreferenceline.com shows only “Get Ready... Something Really Cool Is Coming Soon” [reco-site]. No announcement or chain data was found [fd-data].", "aliases": "breco reference line", "refs": ["btc-523118", "fd-data", "reco-site"], "url": "/wiki/bitcoin-reference-line/"}, {"id": "bitcoin-rhodium#infobox", "slug": "bitcoin-rhodium", "title": "Bitcoin Rhodium / xRhodium (XRC)", "section": "Summary and infobox", "text": "A C# proof-of-work coin with a 2.1 million cap that called itself Bitcoin Rhodium, said plainly it was not a Bitcoin fork, and renamed itself xRhodium in 2019. Bitcoin fork?: “NO” (project FAQ) [xrc-faq]; Mainnet: 20 Oct 2018 (project started 1 Dec 2017) [xrc-faq]; Max supply: 2.1 million [xrc-faq]; Proof of work: x13 [xrc-faq]; Block interval: 10 minutes [xrc-faq]; Later name: xRhodium (FAQ of 23 Oct 2019) [xrc-medium]", "aliases": "xrc rhodium xrhodium", "refs": ["xrc-faq", "xrc-medium"], "url": "/wiki/bitcoin-rhodium/"}, {"id": "bitcoin-rhodium#takeover", "slug": "bitcoin-rhodium", "title": "Bitcoin Rhodium / xRhodium (XRC)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Rhodium is the rare Bitcoin-named coin that answered the fork question with a flat no, which is why it sits off the lineage map and in the wiki only as a naming case. [xrc-faq]", "aliases": "xrc rhodium xrhodium", "refs": ["xrc-faq"], "url": "/wiki/bitcoin-rhodium/"}, {"id": "bitcoin-rhodium#313", "slug": "bitcoin-rhodium", "title": "Bitcoin Rhodium / xRhodium (XRC)", "section": "Not a fork", "text": "The project's own FAQ asks “Is this a Bitcoin fork?” and answers “NO. Bitcoin Rhodium is not a Bitcoin fork and uses its own unique blockchain” [xrc-faq]. The same FAQ says it is programmed in C#, that mainnet launched on 20 October 2018 and that the project started on 1 December 2017 [xrc-faq].", "aliases": "xrc rhodium xrhodium", "refs": ["xrc-faq"], "url": "/wiki/bitcoin-rhodium/"}, {"id": "bitcoin-rhodium#314", "slug": "bitcoin-rhodium", "title": "Bitcoin Rhodium / xRhodium (XRC)", "section": "Design", "text": "The FAQ gives a maximum supply of 2.1 million coins, “one-tenth of Bitcoin's”, x13 proof of work and the same 10-minute block interval as Bitcoin [xrc-faq]. A Medium version of the FAQ published on 23 October 2019 uses the name xRhodium, describes the Strong Hands Program of free coins for holding XRC for three months, and asks “Is this a token?” rather than whether it is a fork [xrc-medium].", "aliases": "xrc rhodium xrhodium", "refs": ["xrc-faq", "xrc-medium"], "url": "/wiki/bitcoin-rhodium/"}, {"id": "bitcoin-rm#infobox", "slug": "bitcoin-rm", "title": "Bitcoin RM (BCRM)", "section": "Summary and infobox", "text": "A 2018 smart fork for retail merchants: a clean chain seeded with a 20 August 2018 UTXO snapshot, with claims open to non-US holders until the end of 2018. Snapshot: UTXOs of 20 August 2018 [bcrm-readme]; Snapshot block (forkdrop): 537,746 [fd-data]; Block 537,746 time: 2018-08-21 03:56:27 UTC [btc-537746]; Block interval: 60 seconds [bcrm-ann]; Max supply: 1 Billion [bcrm-ann]; Claims closed: 31 December 2018 [bcrm-ann]", "aliases": "bcrm rm retail merchants", "refs": ["bcrm-ann", "bcrm-readme", "btc-537746", "fd-data"], "url": "/wiki/bitcoin-rm/"}, {"id": "bitcoin-rm#takeover", "slug": "bitcoin-rm", "title": "Bitcoin RM (BCRM)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin RM excluded US owners and addresses that cannot sign messages, so many BTC holders could never claim. [bcrm-ann]", "aliases": "bcrm rm retail merchants", "refs": ["bcrm-ann"], "url": "/wiki/bitcoin-rm/"}, {"id": "bitcoin-rm#317", "slug": "bitcoin-rm", "title": "Bitcoin RM (BCRM)", "section": "Record", "text": "The README says “We start with a clean blockchain, without copying the blockchain of Bitcoin. We take a snapshot of UTXOs on August 20, 2018.” [bcrm-readme] forkdrop's data file gives block 537746 [fd-data]. Block 537,746 was mined on 21 August 2018 UTC [btc-537746]. The thread says eligible non-USA owners with at least 0.001 BTC could claim, that “Users with Bitcoin addresses starting with 3 or bc cannot sign messages and therefore cannot claim”, and that “The claims deadline was December 31, 2018” [bcrm-ann]. It lists 60-second blocks, 20MB blocks, a 1 Billion supply and a 5% founders' fee [bcrm-ann].", "aliases": "bcrm rm retail merchants", "refs": ["bcrm-ann", "bcrm-readme", "btc-537746", "fd-data"], "url": "/wiki/bitcoin-rm/"}, {"id": "bitcoin-silver#infobox", "slug": "bitcoin-silver", "title": "Bitcoin Silver (BTSI)", "section": "Summary and infobox", "text": "An October 2017 fork announcement for an Equihash chain with 30-second blocks, whose text was copied from Bitcoin Gold's and which a 2019 review found no longer existed. Announced: 24 Oct 2017 by Simonsolo [btsi-ann]; Planned date: “COMING 31TH DECEMBER 2017” [bth-review]; Proof of work: Equihash [btsi-ann]; Block interval: 30 seconds [btsi-ann]; Supply: 21 million [btsi-ann]; Source code: “no source code available” [bth-review]", "aliases": "btsi silver", "refs": ["bth-review", "btsi-ann"], "url": "/wiki/bitcoin-silver/"}, {"id": "bitcoin-silver#takeover", "slug": "bitcoin-silver", "title": "Bitcoin Silver (BTSI)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Silver's own announcement says ASICs are obsolete “for mining BTG” — a copy-paste fingerprint of how many 2017 forks were cloned from Bitcoin Gold's pitch. [btsi-ann]", "aliases": "btsi silver", "refs": ["btsi-ann"], "url": "/wiki/bitcoin-silver/"}, {"id": "bitcoin-silver#320", "slug": "bitcoin-silver", "title": "Bitcoin Silver (BTSI)", "section": "Announcement", "text": "Simonsolo opened “Bitcoin Silver - Make Bitcoin Decentralized Again” on Bitcointalk on 24 October 2017 [btsi-ann]. A follow-up post said “The block interval will be lowered to 30 seconds” and gave a supply of 21 Million, Equihash, GPU mining and replay protection [btsi-ann]. The text also says ASICs are “obsolete for mining BTG”, wording taken from Bitcoin Gold [btsi-ann].", "aliases": "btsi silver", "refs": ["btsi-ann"], "url": "/wiki/bitcoin-silver/"}, {"id": "bitcoin-silver#321", "slug": "bitcoin-silver", "title": "Bitcoin Silver (BTSI)", "section": "Fate", "text": "The 2019 fork list gives its date only as “COMING 31TH DECEMBER 2017”, notes “no source code available” and says it “doesn't seem to exist (anymore)” [bth-review]. One reply in the thread asked whether “100K will be premined for devs” [btsi-ann].", "aliases": "btsi silver", "refs": ["bth-review", "btsi-ann"], "url": "/wiki/bitcoin-silver/"}, {"id": "bitcoin-smart#infobox", "slug": "bitcoin-smart", "title": "Bitcoin Smart (BCS)", "section": "Summary and infobox", "text": "A fork at block 505,050 that promised 100 BCS and 100 test tokens per BTC and a built-in token exchange; no source code was found. Fork height: 505,050 [bcs-site]; Block 505,050 time: 2018-01-19 21:58:53 UTC [btc-505050]; Ratio: 1 BTC = 100 BCS + 100 BCST [bcs-site]; Pitch: Smart contracts, token issuance, built-in DEX [bcs-site]; Premine: None claimed [bcs-site]; Source code: “no source code available” [bth-review]", "aliases": "bcs bcst smart", "refs": ["bcs-site", "btc-505050", "bth-review"], "url": "/wiki/bitcoin-smart/"}, {"id": "bitcoin-smart#takeover", "slug": "bitcoin-smart", "title": "Bitcoin Smart (BCS)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Smart's site ended with a copyright line for bitcoincash.org, a small sign of how fork sites were assembled. [bcs-site]", "aliases": "bcs bcst smart", "refs": ["bcs-site"], "url": "/wiki/bitcoin-smart/"}, {"id": "bitcoin-smart#324", "slug": "bitcoin-smart", "title": "Bitcoin Smart (BCS)", "section": "Pitch", "text": "The archived site says “Bitcoin Smart(BCS) is a hard fork of Bitcoin on block height 505050” with a smart-contract system and token issuance [bcs-site]. Holding 1 Bitcoin at block 505,050 was to give “100 Bitcoin Smart(BCS) and 100 Bitcoin smart test token (BCST)”, and the FAQ answers the premine question with “No” [bcs-site]. The page footer reads “© bitcoincash.org” [bcs-site].", "aliases": "bcs bcst smart", "refs": ["bcs-site"], "url": "/wiki/bitcoin-smart/"}, {"id": "bitcoin-smart#325", "slug": "bitcoin-smart", "title": "Bitcoin Smart (BCS)", "section": "Record", "text": "The 2019 fork list records the same ratio and height and notes “no source code available” [bth-review]. Block 505,050 was mined on 19 January 2018 [btc-505050]. The same list gives Bitvote (BTV) the same fork height [bth-review].", "aliases": "bcs bcst smart", "refs": ["btc-505050", "bth-review"], "url": "/wiki/bitcoin-smart/"}, {"id": "bitcoin-stake#infobox", "slug": "bitcoin-stake", "title": "BitcoinStake (BTCS)", "section": "Summary and infobox", "text": "A Chinese-language proof-of-stake fork at block 499,999 at 1 BTC = 100 BTCS, with 21 million of 2.121 billion coins premined for a foundation. Fork height: 499,999 [btcs-site]; Block 499,999 time: 2017-12-18 18:34:47 UTC [btc-499999]; Ratio: 1 BTC = 100 BTCS [bth-review]; Consensus: Proof of stake [btcs-site]; Supply: 2.121 billion, 21 million premined [btcs-site]; Source code: “no source code available” [bth-review]", "aliases": "btcs bitcoinstake stake pos", "refs": ["btc-499999", "btcs-site", "bth-review"], "url": "/wiki/bitcoin-stake/"}, {"id": "bitcoin-stake#takeover", "slug": "bitcoin-stake", "title": "BitcoinStake (BTCS)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: BitcoinStake and World Bitcoin used the same supply plan — 2.121 billion coins, 21 million of them held by a foundation. [btcs-site] [wbtc-site]", "aliases": "btcs bitcoinstake stake pos", "refs": ["btcs-site", "wbtc-site"], "url": "/wiki/bitcoin-stake/"}, {"id": "bitcoin-stake#328", "slug": "bitcoin-stake", "title": "BitcoinStake (BTCS)", "section": "Site", "text": "The archived site, captured on 28 December 2017, is in Chinese [btcs-site]. It describes BTCS as a proof-of-stake change to Bitcoin and says the team would run a fork trial at height 499999 (“在499999的高度进行分叉试验”), with Bitcoin addresses receiving BTCS at a ratio of 1:100 [btcs-site]. It gives a total of 2.121 billion BTCS, of which 21 million were premined for the foundation [btcs-site].", "aliases": "btcs bitcoinstake stake pos", "refs": ["btcs-site"], "url": "/wiki/bitcoin-stake/"}, {"id": "bitcoin-stake#329", "slug": "bitcoin-stake", "title": "BitcoinStake (BTCS)", "section": "Record", "text": "The 2019 fork list gives “BitcoinStake (BTCS) (1 BTC = 100 BTCS)”, “fork at 499999”, notes the site is “(only in Chinese)” and says “no source code available” [bth-review]. Block 499,999 was mined on 18 December 2017 [btc-499999].", "aliases": "btcs bitcoinstake stake pos", "refs": ["btc-499999", "bth-review"], "url": "/wiki/bitcoin-stake/"}, {"id": "bitcoin-star#infobox", "slug": "bitcoin-star", "title": "Bitcoin Star (BCS)", "section": "Summary and infobox", "text": "A January 2018 listing at block 502,999 with a 1000:1 ratio and a 21 billion supply, known only from forkdrop's data and a Facebook link. Fork height (forkdrop): 502,999 [fd-data]; Block 502,999 time: 2018-01-07 11:17:10 UTC [btc-502999]; Ratio (forkdrop): 1000:1 [fd-data]; Max supply (forkdrop): 21 Billion [fd-data]; forkdrop reason: “Inactivity” [fd-data]", "aliases": "bcs star", "refs": ["btc-502999", "fd-data"], "url": "/wiki/bitcoin-star/"}, {"id": "bitcoin-star#takeover", "slug": "bitcoin-star", "title": "Bitcoin Star (BCS)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Star is a single-source entry. Its only project link was a Facebook page. [fd-data]", "aliases": "bcs star", "refs": ["fd-data"], "url": "/wiki/bitcoin-star/"}, {"id": "bitcoin-star#332", "slug": "bitcoin-star", "title": "Bitcoin Star (BCS)", "section": "Record", "text": "forkdrop's data file lists Bitcoin Star with ticker BCS, fork block 502999, a date of 2018-01-07, a 1000:1 ratio and a maximum supply of 21 Billion [fd-data]. Block 502,999 was mined on 7 January 2018 [btc-502999]. Its only project link is a Facebook page, and forkdrop files it among historic entries with the reason “Inactivity” [fd-data]. No code, announcement or chain data was found [fd-data]. The BCS ticker is also used by Bitcoin Smart and Bitcoin Class [fd-data].", "aliases": "bcs star", "refs": ["btc-502999", "fd-data"], "url": "/wiki/bitcoin-star/"}, {"id": "bitcoin-stash#infobox", "slug": "bitcoin-stash", "title": "Bitcoin Stash (BSH)", "section": "Summary and infobox", "text": "A November 2018 fork of Bitcoin Cash by former BCH developers and community members, built around merge mining; still syncing in February 2019. Parent: Bitcoin Cash [bsh-readme]; Fork height (BCH): 556,766 (forkdrop) / 556,767 (2019 list) [fd-data]; Mining: Merge-mined with SHA-256 coins [bsh-readme]; Status (Feb 2019 list): “seems to be working, 0.4 GB” [bth-review]", "aliases": "bsh stash bstash merge mining", "refs": ["bsh-readme", "bth-review", "fd-data"], "url": "/wiki/bitcoin-stash/"}, {"id": "bitcoin-stash#takeover", "slug": "bitcoin-stash", "title": "Bitcoin Stash (BSH)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Stash forked BCH in November 2018 and pitched merge mining as its defence against 51% attacks. [bsh-readme] [fd-data]", "aliases": "bsh stash bstash merge mining", "refs": ["bsh-readme", "fd-data"], "url": "/wiki/bitcoin-stash/"}, {"id": "bitcoin-stash#335", "slug": "bitcoin-stash", "title": "Bitcoin Stash (BSH)", "section": "Pitch", "text": "The README says Bitcoin Stash “is a cryptocurrency that is hard forked from Bitcoin Cash”, made by “a group of former Bitcoin Cash developers and community members that have become dismayed at the current outlook of BCH” [bsh-readme]. It says the coin “utilizes merge mining” against attempts to hijack the chain, and can be merge-mined with Bitcoin and both Bitcoin Cash variants [bsh-readme].", "aliases": "bsh stash bstash merge mining", "refs": ["bsh-readme"], "url": "/wiki/bitcoin-stash/"}, {"id": "bitcoin-stash#336", "slug": "bitcoin-stash", "title": "Bitcoin Stash (BSH)", "section": "Record", "text": "forkdrop's data file gives Bitcoin Cash as the source chain, fork block 556766 and a date of 2018-11-15 [fd-data]. The 2019 fork list gives 556767 instead and reported the chain “seems to be working, 0.4 GB” on 26 February 2019 [bth-review]. Its state after 2019 is unknown [bth-review].", "aliases": "bsh stash bstash merge mining", "refs": ["bth-review", "fd-data"], "url": "/wiki/bitcoin-stash/"}, {"id": "bitcoin-sudu#infobox", "slug": "bitcoin-sudu", "title": "Bitcoin Sudu (SUDU)", "section": "Summary and infobox", "text": "A fork announced in December 2017 for 21 February 2018, promising anonymity and instant confirmations. Planned fork date: 21 February 2018 [sudu-ann]; Fork block: Unknown (forkdrop: ???) [fd-data]; forkdrop reason: “Homepage Down” [fd-data]", "aliases": "sudu", "refs": ["fd-data", "sudu-ann"], "url": "/wiki/bitcoin-sudu/"}, {"id": "bitcoin-sudu#takeover", "slug": "bitcoin-sudu", "title": "Bitcoin Sudu (SUDU)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Sudu called itself a technological experiment whose success would help Bitcoin upgrade. [sudu-ann]", "aliases": "sudu", "refs": ["sudu-ann"], "url": "/wiki/bitcoin-sudu/"}, {"id": "bitcoin-sudu#339", "slug": "bitcoin-sudu", "title": "Bitcoin Sudu (SUDU)", "section": "Record", "text": "The announcement of 6 December 2017 says the team was “implementing anonymization and instant confirmations technology” and that “The fork is scheduled for 21 February 2018” [sudu-ann]. It adds “Bitcoin Sudu fork is a technological experiment” [sudu-ann]. forkdrop's data file gives a date of 2018-02-20, fork block “???” and the reason “Homepage Down” [fd-data]. No chain data was found [fd-data].", "aliases": "sudu", "refs": ["fd-data", "sudu-ann"], "url": "/wiki/bitcoin-sudu/"}, {"id": "bitcoin-sv#infobox", "slug": "bitcoin-sv", "title": "Bitcoin SV", "section": "Summary and infobox", "text": "The nChain-backed split from Bitcoin Cash in the November 2018 “hash war”. Ticker: BSV [btk-bsv]; Type: UTXO hard fork of Bitcoin Cash [btk-bsv]; Split: 15 November 2018 [btk-bsv]; Last common block: 556,766 (mined by SVPool) [btk-bsv]; First BSV-only block: 556,767, 13.6 MB [btk-bsv]; Proof of work: SHA-256d [btk-bsv]; Node software: SV Node; Teranode (October 2025) [btk-bsv]", "aliases": "bsv nchain satoshi vision craig wright", "refs": ["btk-bsv"], "url": "/wiki/bitcoin-sv/"}, {"id": "bitcoin-sv#takeover", "slug": "bitcoin-sv", "title": "Bitcoin SV", "section": "Takeover view (editorial opinion)", "text": "Kurt Wuckert Jr. gave the BSV side of the story on the show for more than three and a half hours, including his account of why the split happened. [ep-s17e39-split] [ep-s17e39-avalanche]", "aliases": "bsv nchain satoshi vision craig wright", "refs": ["ep-s17e39-avalanche", "ep-s17e39-split"], "url": "/wiki/bitcoin-sv/"}, {"id": "bitcoin-sv#342", "slug": "bitcoin-sv", "title": "Bitcoin SV", "section": "Split", "text": "Bitcoin SV split from Bitcoin Cash on 15 November 2018, the day of a scheduled BCH upgrade. The last common block was 556,766; the first BSV-only block, 556,767, was 13.6 MB [btk-bsv]. Exchanges kept the BCH ticker on the Bitcoin ABC chain and listed the nChain chain as BSV [btk-bsv].", "aliases": "bsv nchain satoshi vision craig wright", "refs": ["btk-bsv"], "url": "/wiki/bitcoin-sv/"}, {"id": "bitcoin-sv#343", "slug": "bitcoin-sv", "title": "Bitcoin SV", "section": "The hash war", "text": "The nChain camp rejected the November 2018 upgrade (CTOR and OP_CHECKDATASIG), and instead proposed raising the default block size from 32 MB to 128 MB and restoring more disabled opcodes. Calvin Ayre's CoinGeek pool backed it, and the threats to mine empty blocks on the other chain gave the episode the name \"hash war\" [btk-bsv]. Kurt Wuckert Jr. discussed the split and his view of Amaury Séchet's role on Bitcoin Takeover S17 E39 [ep-s17e39-split] [ep-s17e39-avalanche].", "aliases": "bsv nchain satoshi vision craig wright", "refs": ["btk-bsv", "ep-s17e39-avalanche", "ep-s17e39-split"], "url": "/wiki/bitcoin-sv/"}, {"id": "bitcoin-sv#344", "slug": "bitcoin-sv", "title": "Bitcoin SV", "section": "Craig Wright", "text": "On 14 March 2024, in COPA v Wright, the UK High Court ruled that Craig Wright is not Satoshi Nakamoto, did not write the white paper and did not write the original code [btk-bsv] [copa-judgment].", "aliases": "bsv nchain satoshi vision craig wright", "refs": ["btk-bsv", "copa-judgment"], "url": "/wiki/bitcoin-sv/"}, {"id": "bitcoin-sv#345", "slug": "bitcoin-sv", "title": "Bitcoin SV", "section": "Heard on Bitcoin Takeover", "text": "Discussing the lost Mt. Gox coins on S17 E10 (March 2026), Mark Karpelès said that “the founder behind BSV is also claiming those Bitcoin as his own.” [ep-s17e10-q6954]", "aliases": "bsv nchain satoshi vision craig wright", "refs": ["ep-s17e10-q6954"], "url": "/wiki/bitcoin-sv/"}, {"id": "bitcoin-top#infobox", "slug": "bitcoin-top", "title": "Bitcoin Top (BTT)", "section": "Summary and infobox", "text": "A December 2017 fork at block 501,118 with 17 million coins for Bitcoin holders and 4 million for a community pool; still syncing in February 2019. Fork height: 501,118 [btt-readme]; Block 501,118 time: 2017-12-26 13:50:32 UTC [btc-501118]; Supply: 21 million: 17 million 1:1 to holders, 4 million to a community pool [btt-readme]; Replay protection: Claimed, both directions [btt-readme]; Status (Feb 2019 list): “still seems to be working, 0.2 GB” [bth-review]", "aliases": "btt top", "refs": ["btc-501118", "bth-review", "btt-readme"], "url": "/wiki/bitcoin-top/"}, {"id": "bitcoin-top#takeover", "slug": "bitcoin-top", "title": "Bitcoin Top (BTT)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Top is one of the small forks the 2019 reviewer could still sync, which makes it a better-documented survivor than most of the December 2017 wave. [bth-review]", "aliases": "btt top", "refs": ["bth-review"], "url": "/wiki/bitcoin-top/"}, {"id": "bitcoin-top#348", "slug": "bitcoin-top", "title": "Bitcoin Top (BTT)", "section": "Pitch", "text": "The README says “Bitcoin Top (BTT) is a fork of Bitcoin that occurs at the predetermined height of block 501118” and promises new proof-of-work rules and better privacy [btt-readme]. It claims an anti-replay function in both directions [btt-readme]. Of 21 million BTT, it says 17 million go to Bitcoin holders at 1 BTC : 1 BTT and “The rest 4 million will be automatically transferred into the community rewards pool” [btt-readme].", "aliases": "btt top", "refs": ["btt-readme"], "url": "/wiki/bitcoin-top/"}, {"id": "bitcoin-top#349", "slug": "bitcoin-top", "title": "Bitcoin Top (BTT)", "section": "Record", "text": "The archived site, captured on 3 February 2018, reads “12/26/2017 Hard Forked in Blocks 501118” [btt-site]. Block 501,118 was mined on 26 December 2017 [btc-501118]. The 2019 fork list says it “still seems to be working, 0.2 GB” [bth-review].", "aliases": "btt top", "refs": ["btc-501118", "bth-review", "btt-site"], "url": "/wiki/bitcoin-top/"}, {"id": "bitcoin-transfer#infobox", "slug": "bitcoin-transfer", "title": "Bitcoin Transfer (BTCT)", "section": "Summary and infobox", "text": "A fork listed by forkdrop for 1 April 2018 with no block or supply; its only announcement link is an image on an events site. Fork block: Unknown (forkdrop: ???) [fd-data]; Date (forkdrop): 2018-04-01 [fd-data]; forkdrop reason: “Homepage Down” [fd-data]", "aliases": "btct transfer", "refs": ["fd-data"], "url": "/wiki/bitcoin-transfer/"}, {"id": "bitcoin-transfer#takeover", "slug": "bitcoin-transfer", "title": "Bitcoin Transfer (BTCT)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Transfer is a single-source entry. [fd-data]", "aliases": "btct transfer", "refs": ["fd-data"], "url": "/wiki/bitcoin-transfer/"}, {"id": "bitcoin-transfer#352", "slug": "bitcoin-transfer", "title": "Bitcoin Transfer (BTCT)", "section": "Record", "text": "forkdrop's data file lists Bitcoin Transfer with ticker BTCT, a date of 2018-04-01, a 1:1 ratio, block and supply “???” and the reason “Homepage Down” [fd-data]. Its announcement link is a proof image on coinmarketcal.com [fd-data]. No code, thread or chain data was found [fd-data].", "aliases": "btct transfer", "refs": ["fd-data"], "url": "/wiki/bitcoin-transfer/"}, {"id": "bitcoin-unlimited#infobox", "slug": "bitcoin-unlimited", "title": "Bitcoin Unlimited", "section": "Summary and infobox", "text": "A full-node client that let users and miners choose their own block size limit, governed by a voting federation; later a Bitcoin Cash implementation. Type: Full-node client forked from Bitcoin Core [wp-bu]; Idea: Users signal their preferred block size limit; nodes follow the most-work chain [wp-bu]; Governance: Articles of Federation; elected President, Secretary and other officers; BUIP proposals [bu-articles]; First officer vote: Scheduled for 15 January 2016 [bu-articles]; Attack: Nodes attacked after a bug was disclosed on 14 March 2017 [wp-bu]; Later: Releases compatible with Bitcoin Cash from version 1.1.0.0 [wp-bu]", "aliases": "bu buip unlimited", "refs": ["bu-articles", "wp-bu"], "url": "/wiki/bitcoin-unlimited/"}, {"id": "bitcoin-unlimited#takeover", "slug": "bitcoin-unlimited", "title": "Bitcoin Unlimited", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Unlimited was the most explicitly political client of the war, with a written constitution that put hashpower votes at the centre. [bu-articles]", "aliases": "bu buip unlimited", "refs": ["bu-articles"], "url": "/wiki/bitcoin-unlimited/"}, {"id": "bitcoin-unlimited#355", "slug": "bitcoin-unlimited", "title": "Bitcoin Unlimited", "section": "Principle", "text": "The Articles of Federation assert that “Bitcoin is and should be whatever its users define by the code they run and the rules they vote for with their hash power” [bu-articles]. They describe a federation with a publicly identified President and Secretary who handle Bitcoin Unlimited Improvement Proposals (BUIPs) [bu-articles].", "aliases": "bu buip unlimited", "refs": ["bu-articles"], "url": "/wiki/bitcoin-unlimited/"}, {"id": "bitcoin-unlimited#356", "slug": "bitcoin-unlimited", "title": "Bitcoin Unlimited", "section": "How it differs", "text": "Bitcoin Core had a hard-coded one-megabyte limit; Bitcoin Unlimited instead let users signal the limit they prefer and automatically track the chain with the most proof of work, regardless of block size [wp-bu]. It followed Bitcoin XT and Bitcoin Classic as an alternative path to larger blocks [wp-bu].", "aliases": "bu buip unlimited", "refs": ["wp-bu"], "url": "/wiki/bitcoin-unlimited/"}, {"id": "bitcoin-unlimited#357", "slug": "bitcoin-unlimited", "title": "Bitcoin Unlimited", "section": "March 2017 attack", "text": "Bitcoin Unlimited nodes were attacked after a bug was disclosed on 14 March 2017, and the number of nodes fell from about 780 to about 370 before recovering within 24 hours, according to coin.dance data cited by Wikipedia [wp-bu].", "aliases": "bu buip unlimited", "refs": ["wp-bu"], "url": "/wiki/bitcoin-unlimited/"}, {"id": "bitcoin-unlimited#358", "slug": "bitcoin-unlimited", "title": "Bitcoin Unlimited", "section": "Bitcoin Cash era", "text": "From version 1.1.0.0, Bitcoin Unlimited releases are compatible with Bitcoin Cash [wp-bu]. On S17 E19, Amaury Séchet credited the CashTokens upgrade to Bitcoin Unlimited's push and said some of its developers later moved to a coin called Nexa [ep-s17e19-buidea].", "aliases": "bu buip unlimited", "refs": ["ep-s17e19-buidea", "wp-bu"], "url": "/wiki/bitcoin-unlimited/"}, {"id": "bitcoin-unlimited#359", "slug": "bitcoin-unlimited", "title": "Bitcoin Unlimited", "section": "Heard on Bitcoin Takeover", "text": "On S16 E30 (June 2025), Peter Rizun contrasted the earlier proposals with BU: “XT and classic were both attempts to reach consensus so we could all move forward together and guarantee there would be no fork.” By contrast, he said, “Bitcoin Unlimited was an attempt to say, OK, well, we're going to give up.” [ep-s16e30-bu]", "aliases": "bu buip unlimited", "refs": ["ep-s16e30-bu"], "url": "/wiki/bitcoin-unlimited/"}, {"id": "bitcoin-uranium#infobox", "slug": "bitcoin-uranium", "title": "Bitcoin Uranium (BUM)", "section": "Summary and infobox", "text": "An October 2017 fork announcement with Equihash, one-minute blocks and a 450-day halving, pitched as having no premine unlike Gold, Silver or Platinum. Announced: 25 Oct 2017 by BitcoinUranium [bum-ann]; Slogan: “Make Bitcoin Great Again” [bum-ann]; Proof of work: Equihash [bum-ann]; Halving: Every 450 days [bum-ann]; Block time: 1 minute [bum-ann]; Status (Feb 2019 list): “doesn't seem to exist (anymore)” [bth-review]", "aliases": "bum bcu uranium", "refs": ["bth-review", "bum-ann"], "url": "/wiki/bitcoin-uranium/"}, {"id": "bitcoin-uranium#takeover", "slug": "bitcoin-uranium", "title": "Bitcoin Uranium (BUM)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Uranium sold itself against its siblings — “No pre-mine unlike Bitcoin Gold, Silver, or Platinum” — which shows how crowded the metal-named fork shelf was by late 2017. [bum-ann]", "aliases": "bum bcu uranium", "refs": ["bum-ann"], "url": "/wiki/bitcoin-uranium/"}, {"id": "bitcoin-uranium#362", "slug": "bitcoin-uranium", "title": "Bitcoin Uranium (BUM)", "section": "Announcement", "text": "BitcoinUranium posted “Bitcoin Uranium- Make Bitcoin Great Again” on 25 October 2017 [bum-ann]. It promised Equihash, a “450 days half-life”, a 21 million maximum, a 1 minute block time, “No pre-mine unlike Bitcoin Gold, Silver, or Platinum” and full replay protection [bum-ann]. The same post calls the coin BCU in one sentence and $BUM in its title line [bum-ann].", "aliases": "bum bcu uranium", "refs": ["bum-ann"], "url": "/wiki/bitcoin-uranium/"}, {"id": "bitcoin-uranium#363", "slug": "bitcoin-uranium", "title": "Bitcoin Uranium (BUM)", "section": "Code and fate", "text": "The README describes “a fork of Bitcoin that serves to re-decentralize the mining process of Bitcoin” [bum-readme]. The 2019 fork list gives the date only as “Coming 31th December 2017” and says it “doesn't seem to exist (anymore)” [bth-review].", "aliases": "bum bcu uranium", "refs": ["bth-review", "bum-readme"], "url": "/wiki/bitcoin-uranium/"}, {"id": "bitcoin-wonder#infobox", "slug": "bitcoin-wonder", "title": "Bitcoin Wonder (BCW)", "section": "Summary and infobox", "text": "A DPoS airdrop of 42 million BCW split between BTC holders (1:1), BDS holders and Ti-value holders, keyed to block 500,000. Snapshot (forkdrop): Block 500,000 [fd-data]; Block 500,000 time: 2017-12-18 18:35:25 UTC [btc-500000]; Supply: 42 million: 17M to BTC holders, 8.5M BDS, 8.5M Ti-value, 8M kept [bcw-site]; Consensus: DPoS [bcw-site]", "aliases": "bcw wonder dpos bds ti-value", "refs": ["bcw-site", "btc-500000", "fd-data"], "url": "/wiki/bitcoin-wonder/"}, {"id": "bitcoin-wonder#takeover", "slug": "bitcoin-wonder", "title": "Bitcoin Wonder (BCW)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Wonder split its airdrop between Bitcoin holders and two other coins' holders, so it is not a plain Bitcoin split. [bcw-site]", "aliases": "bcw wonder dpos bds ti-value", "refs": ["bcw-site"], "url": "/wiki/bitcoin-wonder/"}, {"id": "bitcoin-wonder#366", "slug": "bitcoin-wonder", "title": "Bitcoin Wonder (BCW)", "section": "Pitch", "text": "The archived site, captured on 5 April 2018, says “The total amount of BCW is 42 million, twice than that of BTC” [bcw-site]. It allocates 17 million to BTC holders at 1 BTC : 1 BCW, 8.5 million to BDS holders, 8.5 million to Ti-value holders, and keeps 8 million for promotion [bcw-site]. It describes a DPoS consensus and a mission of giving BCW to small and medium-sized enterprises [bcw-site].", "aliases": "bcw wonder dpos bds ti-value", "refs": ["bcw-site"], "url": "/wiki/bitcoin-wonder/"}, {"id": "bitcoin-wonder#367", "slug": "bitcoin-wonder", "title": "Bitcoin Wonder (BCW)", "section": "Record", "text": "forkdrop's data file lists an airdrop at block 500000 on 2017-12-18 [fd-data]. Block 500,000 was mined on 18 December 2017 [btc-500000]. It links a GitHub organisation, Bitcoinwonder [fd-data]. Its state after 2018 is unknown [fd-data].", "aliases": "bcw wonder dpos bds ti-value", "refs": ["btc-500000", "fd-data"], "url": "/wiki/bitcoin-wonder/"}, {"id": "bitcoin-world#infobox", "slug": "bitcoin-world", "title": "Bitcoin World (BTW)", "section": "Summary and infobox", "text": "A December 2017 fork at block 499,777 at 1 BTC = 10,000 BTW; by February 2019 the reviewer found no nodes. Fork height: 499,777 [btw-readme]; Block 499,777 time: 2017-12-17 12:11:17 UTC [btc-499777]; Ratio: 1 BTC = 10000 BTW [bth-review]; Status (Feb 2019 list): “seems to have no nodes (no DNS seeds)” [bth-review]", "aliases": "btw world", "refs": ["btc-499777", "bth-review", "btw-readme"], "url": "/wiki/bitcoin-world/"}, {"id": "bitcoin-world#takeover", "slug": "bitcoin-world", "title": "Bitcoin World (BTW)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin World's README is a near word-for-word template — the same sentences, with other names and heights, open the Bitcoin Community README. [btw-readme] [btsq-readme]", "aliases": "btw world", "refs": ["btsq-readme", "btw-readme"], "url": "/wiki/bitcoin-world/"}, {"id": "bitcoin-world#370", "slug": "bitcoin-world", "title": "Bitcoin World (BTW)", "section": "README", "text": "The README says Bitcoin World “is a fork of the Bitcoin blockchain that will occur at block height 499777, at roughly 12:00:00 UTC December 17, 2017” [btw-readme]. Block 499,777 was mined at 12:11:17 UTC that day [btc-499777]. It adds that miners would begin creating blocks “with a new proof-of-work algorithm” [btw-readme]. The Bitcoin Community README uses the same wording for block 506066 [btsq-readme].", "aliases": "btw world", "refs": ["btc-499777", "btsq-readme", "btw-readme"], "url": "/wiki/bitcoin-world/"}, {"id": "bitcoin-world#371", "slug": "bitcoin-world", "title": "Bitcoin World (BTW)", "section": "Record", "text": "The 2019 fork list gives “Bitcoin World (BTW) (1 BTC = 10000 BTW)” and, for 26 February 2019, says it “seems to have no nodes (no DNS seeds)” [bth-review].", "aliases": "btw world", "refs": ["bth-review"], "url": "/wiki/bitcoin-world/"}, {"id": "bitcoin-xt#infobox", "slug": "bitcoin-xt", "title": "Bitcoin XT", "section": "Summary and infobox", "text": "Mike Hearn's fork of Bitcoin Core that shipped BIP-101 in August 2015 and opened the public, client-versus-client phase of the block size war. Type: Alternative full-node client, forked from Bitcoin Core [xt-bw]; Created by: Mike Hearn, 2014 [xt-bw]; BIP-101 release: 15 August 2015 [xt-bw]; BIP-101 rule: 8 MB from 11 Jan 2016, doubling every two years to 2036 [bip101]; Activation trigger: 750 of 1,000 blocks with version 0x20000007, plus a two-week grace period [bip101]; Outcome: Never activated; BIP-101 status Closed [bip101]; Later: Release G (25 Aug 2017) was a Bitcoin Cash client by default [xt-bw]", "aliases": "xt bip101 hearn", "refs": ["bip101", "xt-bw"], "url": "/wiki/bitcoin-xt/"}, {"id": "bitcoin-xt#takeover", "slug": "bitcoin-xt", "title": "Bitcoin XT", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: XT is where the war became a contest between competing binaries rather than mailing-list threads. Fork Wars dates that public phase from the XT release in August 2015. [btk-forkwars] [xt-bw]", "aliases": "xt bip101 hearn", "refs": ["btk-forkwars", "xt-bw"], "url": "/wiki/bitcoin-xt/"}, {"id": "bitcoin-xt#374", "slug": "bitcoin-xt", "title": "Bitcoin XT", "section": "Origins", "text": "Bitcoin XT was created by Mike Hearn in 2014, originally to carry alternative P2P rules; its December 2014 0.10 release included his BIP 64 UTXO-lookup extension [xt-bw]. After Gavin Andresen stepped down as Bitcoin Core maintainer, he and Hearn organised XT around changes that lacked consensus in Core [xt-bw].", "aliases": "xt bip101 hearn", "refs": ["xt-bw"], "url": "/wiki/bitcoin-xt/"}, {"id": "bitcoin-xt#375", "slug": "bitcoin-xt", "title": "Bitcoin XT", "section": "BIP-101", "text": "BIP-101 set the maximum block size to 8,000,000 bytes at 11 January 2016, doubling every 63,072,000 seconds until 6 January 2036, after which the limit would be 8,192,000,000 bytes [bip101]. It would activate once 750 of 1,000 consecutive blocks carried version 0x20000007, followed by a two-week grace period [bip101]. The BIP says the 8 MB starting size was chosen after feedback from miners on bandwidth-constrained networks, in particular those behind the Great Firewall of China [bip101].", "aliases": "xt bip101 hearn", "refs": ["bip101"], "url": "/wiki/bitcoin-xt/"}, {"id": "bitcoin-xt#376", "slug": "bitcoin-xt", "title": "Bitcoin XT", "section": "Release and reaction", "text": "BIP-101 was merged into XT on 6 August 2015 and released on 15 August 2015 [xt-bw]. Adam Back criticised the 75% threshold as too low [xt-bw]. Hearn later wrote that by running XT “miners could cast a vote for changing the limit” and that the release “pushed powerful emotional buttons” in a small number of people [hearn-resolution].", "aliases": "xt bip101 hearn", "refs": ["hearn-resolution", "xt-bw"], "url": "/wiki/bitcoin-xt/"}, {"id": "bitcoin-xt#377", "slug": "bitcoin-xt", "title": "Bitcoin XT", "section": "Collapse", "text": "The 75% threshold was never reached [xt-bw]. In January 2016 XT replaced BIP-101 with the one-time 2 MB increase used by Bitcoin Classic, and by January 2017 fewer than 30 XT nodes remained [xt-bw]. Andresen withdrew BIP-101 from the BIPs repository in February 2016 [bip101-withdraw]. From August 2017 XT shipped as a Bitcoin Cash client [xt-bw].", "aliases": "xt bip101 hearn", "refs": ["bip101-withdraw", "xt-bw"], "url": "/wiki/bitcoin-xt/"}, {"id": "bitcoin-xt#378", "slug": "bitcoin-xt", "title": "Bitcoin XT", "section": "Heard on Bitcoin Takeover", "text": "On S17 E39 (August 2026), Kurt Wuckert Jr. recalled: “we saw the DDoS attacks against the Bitcoin XT nodes.” [ep-s17e39-q2900]", "aliases": "xt bip101 hearn", "refs": ["ep-s17e39-q2900"], "url": "/wiki/bitcoin-xt/"}, {"id": "bitcoin#infobox", "slug": "bitcoin", "title": "Bitcoin", "section": "Summary and infobox", "text": "The original chain. Every UTXO fork in this wiki shares its history up to a split block. Ticker: BTC (XBT on some venues) [bmd-advisory]; White paper: 31 October 2008, Cryptography mailing list [wp]; Genesis block: Block 0, 3 January 2009 [genesis]; Proof of work: SHA-256d [btk-allforks]; 1 MB block limit: Added in commit a30b56e, 15 July 2010 [c-1mb]; SegWit active: Block 481,824, 24 August 2017 [btk-allforks]; Taproot active: Block 709,632, 14 November 2021 [btk-allforks]", "aliases": "", "refs": ["bmd-advisory", "btk-allforks", "c-1mb", "genesis", "wp"], "url": "/wiki/bitcoin/"}, {"id": "bitcoin#takeover", "slug": "bitcoin", "title": "Bitcoin", "section": "Takeover view (editorial opinion)", "text": "The baseline every fork measures itself against. The wiki treats Bitcoin as the root of the tree, not as the referee: each fork article states what it changed and lets the sources speak. [btk-forksmag]", "aliases": "", "refs": ["btk-forksmag"], "url": "/wiki/bitcoin/"}, {"id": "bitcoin#381", "slug": "bitcoin", "title": "Bitcoin", "section": "Origins", "text": "Satoshi Nakamoto announced the Bitcoin white paper on the Cryptography mailing list on 31 October 2008 [wp]. The genesis block, block 0, is dated 3 January 2009 [genesis].", "aliases": "", "refs": ["genesis", "wp"], "url": "/wiki/bitcoin/"}, {"id": "bitcoin#382", "slug": "bitcoin", "title": "Bitcoin", "section": "The block size constant", "text": "Bitcoin's 1 MB block size limit was added in commit a30b56e on 15 July 2010 [c-1mb]. When Jeff Garzik proposed a patch to raise it in October 2010, Satoshi replied \"Don't use this patch\" and said a change could be phased in later \"if we get closer to needing it\" [satoshi-15139]. That constant became the centre of the block size war [btk-forkwars].", "aliases": "", "refs": ["btk-forkwars", "c-1mb", "satoshi-15139"], "url": "/wiki/bitcoin/"}, {"id": "bitcoin#383", "slug": "bitcoin", "title": "Bitcoin", "section": "Soft forks, not hard forks", "text": "Bitcoin's own rule changes have been soft forks: P2SH (BIP16) in 2012, CLTV (BIP65) in 2015, CSV in 2016, SegWit at block 481,824 in August 2017 and Taproot at block 709,632 in November 2021 [btk-allforks]. The chains that broke away, from Bitcoin Cash in 2017 to Bitcoin BLAKE2b and eCash (ECX) in 2026, are documented as separate articles [btk-forksmag].", "aliases": "", "refs": ["btk-allforks", "btk-forksmag"], "url": "/wiki/bitcoin/"}, {"id": "bitcoin#384", "slug": "bitcoin", "title": "Bitcoin", "section": "How many forks?", "text": "forkdrop.io counts 105 projects that issued coins based on Bitcoin's ledger, 74 of them listed as active and 31 as historic [forkdrop]. Code forks that started from a new genesis block, such as Litecoin, Dogecoin, Dash and Zcash, are not in that count, but this wiki covers them as members of the wider family [ltc-ann].", "aliases": "", "refs": ["forkdrop", "ltc-ann"], "url": "/wiki/bitcoin/"}, {"id": "bitcoincash-zero#infobox", "slug": "bitcoincash-zero", "title": "BitcoinCash Zero (BCZ)", "section": "Summary and infobox", "text": "A January 2019 Zerocoin privacy coin built from snapshots of Bitcoin Cash, Bitcoin SV, GravityCoin and BitcoinZero, pitched in the wake of the hash war. Snapshot date: 4 January 2019 (announced) [bcz-ann]; Snapshotted coins: BCH, BSV, GXX, BZX [bcz-ann]; Algorithm: Lyra2Z [bcz-ann]; Block time: 150 seconds [bcz-ann]; Block size: 4MB [bcz-ann]; Features: Zerocoin, PoS, masternodes [bcz-ann]", "aliases": "bcz bitcoincash zero knife gxx", "refs": ["bcz-ann"], "url": "/wiki/bitcoincash-zero/"}, {"id": "bitcoincash-zero#takeover", "slug": "bitcoincash-zero", "title": "BitcoinCash Zero (BCZ)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: BCZ pitched itself to both sides of the BCH-BSV hash war by snapshotting both chains. [bcz-ann]", "aliases": "bcz bitcoincash zero knife gxx", "refs": ["bcz-ann"], "url": "/wiki/bitcoincash-zero/"}, {"id": "bitcoincash-zero#387", "slug": "bitcoincash-zero", "title": "BitcoinCash Zero (BCZ)", "section": "Announcement", "text": "The thread opened on 18 December 2018 says BitcoinCash Zero “will be forked from: GravityCoin $GXX, BitcoinZero $BZX, BitcoinCash ABC $BCH and BitcoinCash SV $BCHSV” [bcz-ann]. It frames the coin against the ABC-versus-SV hash war and says the GXX team would make snapshots “with their incredible KNIFE technology” on 4 January 2019 [bcz-ann]. Holders of any of the four coins could claim the new coin [bcz-ann].", "aliases": "bcz bitcoincash zero knife gxx", "refs": ["bcz-ann"], "url": "/wiki/bitcoincash-zero/"}, {"id": "bitcoincash-zero#388", "slug": "bitcoincash-zero", "title": "BitcoinCash Zero (BCZ)", "section": "Design", "text": "The thread calls it “the first ever BitcoinCash privacy fork (Full Zerocoin protocol)”, with PoS, PoW and masternodes [bcz-ann]. Its coin info lists Lyra2Z, a 150-second target spacing and a 4MB block size [bcz-ann]. It said the ratio and supply “will be updated and announced when officially calculated”; this wiki has not verified the final ratios [bcz-ann]. BitcoinZero, one of the snapshotted coins, has its own article [bcz-ann].", "aliases": "bcz bitcoincash zero knife gxx", "refs": ["bcz-ann"], "url": "/wiki/bitcoincash-zero/"}, {"id": "bitcointi#infobox", "slug": "bitcointi", "title": "Bitcoin Ti (BTI)", "section": "Summary and infobox", "text": "A December 2017 fork announced for block 501,300 with 21 million coins and a 0.1 million premine; forkdrop gives block 512,480. Fork height: 501,300 (ANN, README); 512,480 (forkdrop) [bti-readme]; Block 501,300 time: 2017-12-27 18:30:53 UTC [btc-501300]; Supply: 21 million [bti-readme]; forkdrop reason: “Homepage Down” [fd-data]", "aliases": "bti btcti ti", "refs": ["btc-501300", "bti-readme", "fd-data"], "url": "/wiki/bitcointi/"}, {"id": "bitcointi#takeover", "slug": "bitcointi", "title": "Bitcoin Ti (BTI)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Ti's own documents and forkdrop disagree on the fork height by over 11,000 blocks. [bti-readme] [fd-data]", "aliases": "bti btcti ti", "refs": ["bti-readme", "fd-data"], "url": "/wiki/bitcointi/"}, {"id": "bitcointi#391", "slug": "bitcointi", "title": "Bitcoin Ti (BTI)", "section": "Record", "text": "The README and the announcement of 15 December 2017 both say “We decide to fork at block height 501300, which is called – Bitcoin Ti(BTI)” [bti-readme] [bti-ann]. They say “All addresses with balance before block height 501300 will get same amount of BTI automatically”, with a 21 million supply [bti-ann]. The README adds a premine of 0.1 million BTI [bti-readme]. Block 501,300 was mined on 27 December 2017 [btc-501300]. forkdrop's data file instead gives block 512480, ticker BTCTI and the reason “Homepage Down” [fd-data]. Block 512,480 was mined on 7 March 2018 [btc-512480]. Which height was used is unverified [fd-data].", "aliases": "bti btcti ti", "refs": ["btc-501300", "btc-512480", "bti-ann", "bti-readme", "fd-data"], "url": "/wiki/bitcointi/"}, {"id": "bitcoinx#infobox", "slug": "bitcoinx", "title": "BitcoinX (BCX)", "section": "Summary and infobox", "text": "A December 2017 Bitcoin fork that split at the same height as Super Bitcoin, credited 10,000 BCX per BTC, and reserved a premine in a 4-of-6 multisig address. Type: Hard fork with a shared history up to block 498,888 [bcx-chainparams]; First BCX block: 498,889 (BCXHeight in the client) [bcx-chainparams]; Last common block: 498,888, header time 2017-12-12 10:29:53 UTC [btc-498888]; Ratio: 1 BTC = 10,000 BCX (BTC_2_BCX_RATE) [bcx-amount]; Premine: 1.05 million BTC-equivalent (10.5 billion BCX) at the fork block [bcx-chainparams]; Premine custody: 4-of-6 multisig script [bcx-chainparams]; Exchange credit: Gate.io and OKEx credited BCX at 1:10,000 [okex-bcx] [bcx-gate]", "aliases": "bcx", "refs": ["bcx-amount", "bcx-chainparams", "bcx-gate", "btc-498888", "okex-bcx"], "url": "/wiki/bitcoinx/"}, {"id": "bitcoinx#takeover", "slug": "bitcoinx", "title": "BitcoinX (BCX)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: BitcoinX shows how cheaply a fork could be minted in December 2017. The same block, 498,888, served as the snapshot for two different forks, and BCX moved the decimal point so that every holder suddenly owned ten thousand coins per bitcoin. [okex-bcx] [bcx-amount]", "aliases": "bcx", "refs": ["bcx-amount", "okex-bcx"], "url": "/wiki/bitcoinx/"}, {"id": "bitcoinx#394", "slug": "bitcoinx", "title": "BitcoinX (BCX)", "section": "Split", "text": "The BitcoinX client sets BCXHeight to 498,889, the first block with BitcoinX rules [bcx-chainparams]. Block 498,888 on Bitcoin, the last shared block, has a header time of 10:29:53 UTC on 12 December 2017 [btc-498888]. OKEx announced that both SBTC and BCX had completed their forks at that height, 18:29 Beijing time, and opened claims and trading the same evening [okex-bcx]. See Super Bitcoin for the other fork at the same height.", "aliases": "bcx", "refs": ["bcx-chainparams", "btc-498888", "okex-bcx"], "url": "/wiki/bitcoinx/"}, {"id": "bitcoinx#395", "slug": "bitcoinx", "title": "BitcoinX (BCX)", "section": "Units and premine", "text": "BitcoinX redefines the unit so that one BTC corresponds to 10,000 BCX, and caps supply at 21 million times that rate [bcx-amount]. At the fork block the client allows a premine of 1.05 million BTC-equivalent, which at that rate is 10.5 billion BCX, and requires it to be paid to a 4-of-6 multisig script built from six listed public keys [bcx-chainparams]. Gate.io's listing notice described the premine as 5% “for maintenance and management” and warned that premined coins could be sold into the market [bcx-gate].", "aliases": "bcx", "refs": ["bcx-amount", "bcx-chainparams", "bcx-gate"], "url": "/wiki/bitcoinx/"}, {"id": "bitcoinx#396", "slug": "bitcoinx", "title": "BitcoinX (BCX)", "section": "Claims", "text": "Gate.io credited users “on a 1BTC:10000BCX rate around block height 498888” and let users trade BCX before the official wallet existed by locking BTC [bcx-gate]. The project's README is a stock Bitcoin Core template that points to bcx.org [bcx-readme]. Whether the chain is still producing blocks is unknown in this wiki [bcx-readme].", "aliases": "bcx", "refs": ["bcx-gate", "bcx-readme"], "url": "/wiki/bitcoinx/"}, {"id": "bitcoinx2#infobox", "slug": "bitcoinx2", "title": "Bitcoin X2 (BTCX2)", "section": "Summary and infobox", "text": "A 2018 registration-airdrop listing whose archived site still carried placeholder text; forkdrop files it as reneged. Fork block: Unknown (forkdrop: ???) [fd-data]; Date (forkdrop): 2018-07-01 [fd-data]; Max supply (forkdrop): 21,000,000 [fd-data]; forkdrop reason: “Reneged” [fd-data]", "aliases": "btcx2 x2", "refs": ["fd-data"], "url": "/wiki/bitcoinx2/"}, {"id": "bitcoinx2#takeover", "slug": "bitcoinx2", "title": "Bitcoin X2 (BTCX2)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: the April 2018 capture of the BTCX2 site is a shop template with lorem ipsum sections next to the fork pitch. [x2-site]", "aliases": "btcx2 x2", "refs": ["x2-site"], "url": "/wiki/bitcoinx2/"}, {"id": "bitcoinx2#399", "slug": "bitcoinx2", "title": "Bitcoin X2 (BTCX2)", "section": "Record", "text": "The archived site, captured on 26 April 2018, is headed “BTCX2 – Bitcoin Fork 2018. – Bringing speed to Bitcoin” and claims “speeds upto x200” over average Bitcoin transfers [x2-site]. The rest of the page in that capture is placeholder text beginning “Lorem ipsum” [x2-site]. forkdrop's data file lists a registration airdrop with fork block “???”, a date of 2018-07-01 and the reason “Reneged” [fd-data]. No chain data was found [fd-data].", "aliases": "btcx2 x2", "refs": ["fd-data", "x2-site"], "url": "/wiki/bitcoinx2/"}, {"id": "bitcoinzero#infobox", "slug": "bitcoinzero", "title": "BitcoinZero (BZX)", "section": "Summary and infobox", "text": "A 2018 Zerocoin privacy coin airdropped to Bitcoin and Hexx holders from a snapshot; its 2024 client is based on Firo. Announced: 28 Aug 2018 (Bitcointalk) [bzx-ann]; Fork completed: 31 Aug 2018 (developer post) [bzx-ann]; Privacy: Zerocoin (2018), Lelantus (2024 README) [bzx-readme-2018] [bzx-readme]; Total coins: 42,000,000 [bzx-readme-2018]; Algorithm (2024): Lyra2Z [bzx-readme]; Client core (2024): Based on Firo 14.12.X [bzx-readme]", "aliases": "bzx bitcoin zero hexx zerocoin", "refs": ["bzx-ann", "bzx-readme", "bzx-readme-2018"], "url": "/wiki/bitcoinzero/"}, {"id": "bitcoinzero#takeover", "slug": "bitcoinzero", "title": "BitcoinZero (BZX)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: BitcoinZero borrowed the Bitcoin name and a BTC snapshot, but its code line runs through Zerocoin and Firo, which makes it a privacy-coin airdrop rather than a Bitcoin chain split. [bzx-ann] [bzx-readme]", "aliases": "bzx bitcoin zero hexx zerocoin", "refs": ["bzx-ann", "bzx-readme"], "url": "/wiki/bitcoinzero/"}, {"id": "bitcoinzero#402", "slug": "bitcoinzero", "title": "BitcoinZero (BZX)", "section": "Snapshot", "text": "The Bitcointalk announcement thread was opened on 28 August 2018 by BitcoinZeroX [bzx-ann]. A forum member quoted in the thread wrote that “all Hexx holders will receive 10 BZX per HXX they hold at the snapshot” and that Bitcoin holders would receive 1 BZX per BTC [bzx-ann]. On 31 August 2018 the project account posted “The fork has been successfully completed” [bzx-ann].", "aliases": "bzx bitcoin zero hexx zerocoin", "refs": ["bzx-ann"], "url": "/wiki/bitcoinzero/"}, {"id": "bitcoinzero#403", "slug": "bitcoinzero", "title": "BitcoinZero (BZX)", "section": "Code", "text": "The 2018 README describes the “Anonymous Zerocoin Protocol” and a total of 42,000,000 BZX [bzx-readme-2018]. The 2024 README, titled “Bitcoinzero [BZX] (Lelantus) Core 2024”, gives Lyra2Z as the algorithm and says the client core is “based on Firo 14.12.X”, linking it to Firo [bzx-readme].", "aliases": "bzx bitcoin zero hexx zerocoin", "refs": ["bzx-readme", "bzx-readme-2018"], "url": "/wiki/bitcoinzero/"}, {"id": "bitcore#infobox", "slug": "bitcore", "title": "BitCore (BTX)", "section": "Summary and infobox", "text": "A new-genesis coin launched in April 2017 that let Bitcoin holders claim BTX against two Bitcoin snapshots, so it is often listed as a Bitcoin fork although it does not share Bitcoin's history. Type: New chain with its own genesis block; BTC holders claim coins against snapshots [btx-readme]; Genesis block: Timestamp 1492973331 (23 Apr 2017, 18:48 UTC) [btx-chainparams]; Established: 24 April 2017, per its README [btx-readme]; Snapshots: Bitcoin blocks 463,604 (claims ended 30 Oct 2017) and 492,820 (2 Nov 2017) [btx-readme]; Block time: 2.5 minutes on average [btx-ann]; Supply: 21 million maximum [btx-ann]; Masternodes: 2,100 BTX collateral; masternodes receive half of new coins [btx-ann]", "aliases": "btx bitcore timetravel10", "refs": ["btx-ann", "btx-chainparams", "btx-readme"], "url": "/wiki/bitcore/"}, {"id": "bitcore#takeover", "slug": "bitcore", "title": "BitCore (BTX)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: BitCore sits in this wiki's fork list because exchanges and fork trackers list it there, but it is the clearest case of an airdrop dressed as a fork. Its own code starts from a fresh genesis block in April 2017 rather than from Bitcoin's chain. [btx-chainparams] [btx-readme]", "aliases": "btx bitcore timetravel10", "refs": ["btx-chainparams", "btx-readme"], "url": "/wiki/bitcore/"}, {"id": "bitcore#406", "slug": "bitcore", "title": "BitCore (BTX)", "section": "Not a chain split", "text": "BitCore's chain parameters define a fresh genesis block with the timestamp 1492973331 and the message “Powerde by Bitsend-Europecoin-Diamond-MAC-B3 23/Apr/2017”, so its history does not include Bitcoin's blocks [btx-chainparams]. Its README describes the link to Bitcoin as a claim: about five million Bitcoin addresses from a snapshot at block 492,820 on 2 November 2017 “are able to claim BitCore BTX for free”, after an earlier snapshot at block 463,604 whose claim window ended on 30 October 2017 [btx-readme].", "aliases": "btx bitcore timetravel10", "refs": ["btx-chainparams", "btx-readme"], "url": "/wiki/bitcore/"}, {"id": "bitcore#407", "slug": "bitcore", "title": "BitCore (BTX)", "section": "Design", "text": "The README lists SegWit, unique address prefixes, a Dash-style masternode system with 2,100 BTX per masternode, a 220-byte data carrier limit and its own proof-of-work algorithm as the main differences at launch [btx-readme]. The current announcement thread gives a 21 million supply, a 2.5-minute average block time, 10 MB blocks (20 MB with SegWit) and halvings like Bitcoin's [btx-ann]. It says a new GPU-oriented algorithm, Mega-BTX, was launched on 1 September 2020 and that masternodes receive half of all newly generated coins [btx-ann].", "aliases": "btx bitcore timetravel10", "refs": ["btx-ann", "btx-readme"], "url": "/wiki/bitcore/"}, {"id": "bitcore#408", "slug": "bitcore", "title": "BitCore (BTX)", "section": "Thread history", "text": "The Bitcointalk thread was started by the user Limx Dev, with the first replies dated 23 April 2017 under a “[PRE ANN]” subject, and its opening posts have been edited as recently as September 2026 [btx-ann]. Exchange listings, prices and the current number of masternodes are not tracked in this wiki and are unknown here [btx-ann].", "aliases": "btx bitcore timetravel10", "refs": ["btx-ann"], "url": "/wiki/bitcore/"}, {"id": "bitethereum#infobox", "slug": "bitethereum", "title": "BitEthereum (BITE)", "section": "Summary and infobox", "text": "A claim-based token for BTC and ETH holders, snapshotted at Bitcoin block 500,283 and Ethereum block 4,766,319, at 3.93946357 BITE per BTC. BTC snapshot: Block 500,283 [bite-site]; Block 500,283 time: 2017-12-20 15:57:32 UTC [btc-500283]; ETH snapshot: Block 4,766,319 [bite-site]; Ratio: 3.93946357 BITE per BTC; 0.34210519 per ETH [bite-site]; Supply: 100 million; 99% to BTC and ETH holders [bite-site]; Claim deadline: 2 April 2018 [bite-site]", "aliases": "bite bitethereum eth airdrop", "refs": ["bite-site", "btc-500283"], "url": "/wiki/bitethereum/"}, {"id": "bitethereum#takeover", "slug": "bitethereum", "title": "BitEthereum (BITE)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: BitEthereum split one airdrop across two chains' holders, two-thirds to Bitcoin and one-third to Ethereum. [bite-site]", "aliases": "bite bitethereum eth airdrop", "refs": ["bite-site"], "url": "/wiki/bitethereum/"}, {"id": "bitethereum#411", "slug": "bitethereum", "title": "BitEthereum (BITE)", "section": "Airdrop", "text": "The archived Chinese site says the total supply is 100 million, with 99% airdropped: 66 million claimable by BTC holders and 33 million by ETH holders [bite-site]. It set the snapshot for 00:00 on 21 December 2017 and required at least 0.1 BTC or 1 ETH per address [bite-site]. The snapshot heights it gives are Ethereum block 4766319 and Bitcoin block 500283, with 3.93946357 BITE per BTC [bite-site]. Block 500,283 was mined on 20 December 2017 UTC [btc-500283].", "aliases": "bite bitethereum eth airdrop", "refs": ["bite-site", "btc-500283"], "url": "/wiki/bitethereum/"}, {"id": "bitethereum#412", "slug": "bitethereum", "title": "BitEthereum (BITE)", "section": "Record", "text": "Holders were to claim by signing with their BTC or ETH address in a client due in March 2018, before a deadline of 2 April 2018 [bite-site]. The 2019 fork list gives the same ratio and deadline, and notes “no source code available” [bth-review]. forkdrop's data file files it among historic entries with the reason “Airdrop Over” [fd-data].", "aliases": "bite bitethereum eth airdrop", "refs": ["bite-site", "bth-review", "fd-data"], "url": "/wiki/bitethereum/"}, {"id": "bitfury#infobox", "slug": "bitfury", "title": "Bitfury", "section": "Summary and infobox", "text": "Bitcoin miner and ASIC maker whose executives signed the 2016 Hong Kong statement and which appeared on the 2017 New York Agreement. Hong Kong statement: Valery Vavilov (CEO) and Alex Petrov (CIO) [hk-letter]; New York Agreement: Listed as Bitfury (United States) [nya-letter]; Described as: One of the biggest miners and an ASIC producer [ep-s16e54-bitfury]", "aliases": "bitfury vavilov", "refs": ["ep-s16e54-bitfury", "hk-letter", "nya-letter"], "url": "/wiki/bitfury/"}, {"id": "bitfury#takeover", "slug": "bitfury", "title": "Bitfury", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitfury signed both of the war's big compromise documents, Hong Kong in 2016 and New York in 2017, neither of which delivered the hard fork it promised. [hk-letter] [nya-letter]", "aliases": "bitfury vavilov", "refs": ["hk-letter", "nya-letter"], "url": "/wiki/bitfury/"}, {"id": "bitfury#415", "slug": "bitfury", "title": "Bitfury", "section": "Block size war", "text": "The February 2016 Hong Kong Roundtable statement lists “Valery Vavilov CEO BitFury” and “Alex Petrov CIO BitFury” among its signers [hk-letter]. The May 2017 New York Agreement lists “Bitfury (United States)” among supporting companies and BitFury among those offering technical help with the upgrades [nya-letter]. Bitcoin Takeover's timeline names BitFury on the mining panel of Scaling Bitcoin Hong Kong in December 2015 [btk-forkwars].", "aliases": "bitfury vavilov", "refs": ["btk-forkwars", "hk-letter", "nya-letter"], "url": "/wiki/bitfury/"}, {"id": "bitfury#416", "slug": "bitfury", "title": "Bitfury", "section": "On the show", "text": "On S16 E54 Ros said “Bitfury was one of the biggest Bitcoin miners” and an ASIC producer, and that a Stroom co-founder had worked there as a Lightning researcher [ep-s16e54-bitfury].", "aliases": "bitfury vavilov", "refs": ["ep-s16e54-bitfury"], "url": "/wiki/bitfury/"}, {"id": "bitgo#infobox", "slug": "bitgo", "title": "BitGo", "section": "Summary and infobox", "text": "Multisignature custody company led by Mike Belshe; a 2x supporter whose name was wrongly put on the New York Agreement, and since January 2026 a NYSE-listed firm. Founded: 2011, as Whensoon, Inc.; renamed BitGo, Inc. in 2014 [wp-bitgo]; Founders: Mike Belshe, Ben Davenport, Will O'Brien, Bill Lee [wp-bitgo]; Wallets: Generally three keys: one BitGo, two owner [wp-bitgo]; Wrapped Bitcoin: Sole custodian [wp-bitgo]; IPO: NYSE, January 2026, $212 million raised [wp-bitgo]; On the show: S16 E1 and S17 E43 with Mike Belshe [btk-feed]", "aliases": "bitgo belshe custody multisig", "refs": ["btk-feed", "wp-bitgo"], "url": "/wiki/bitgo/"}, {"id": "bitgo#takeover", "slug": "bitgo", "title": "BitGo", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: on S17 E43 Belshe said BitGo's name went on the New York Agreement “without my permission once, after I explicitly told them not”, while confirming he supported SegWit2x. [ep-s17e43-nya] [ep-s17e43-2x]", "aliases": "bitgo belshe custody multisig", "refs": ["ep-s17e43-2x", "ep-s17e43-nya"], "url": "/wiki/bitgo/"}, {"id": "bitgo#419", "slug": "bitgo", "title": "BitGo", "section": "Company", "text": "Wikipedia says BitGo was founded by Mike Belshe, Ben Davenport, Will O'Brien and Bill Lee, incorporated in 2011 as “Whensoon, Inc.” and renamed BitGo, Inc. in 2014 [wp-bitgo]. “Generally, BitGo wallets have three keys: one held by BitGo, and two held by the wallet's owner” [wp-bitgo]. Wikipedia lists it as the sole custodian for Wrapped Bitcoin (WBTC) and listed on the NYSE through an IPO in January 2026 [wp-bitgo]. On S17 E43 Belshe said “We've been in the space since 2013” [ep-s17e43-2013], and described wallets that “are multisig or MPC with a two out of three model for security” [ep-s17e43-2of3].", "aliases": "bitgo belshe custody multisig", "refs": ["ep-s17e43-2013", "ep-s17e43-2of3", "wp-bitgo"], "url": "/wiki/bitgo/"}, {"id": "bitgo#420", "slug": "bitgo", "title": "BitGo", "section": "Block size war", "text": "Belshe co-signed the 8 November 2017 “Segwit2x Final Steps” message that suspended the 2 MB hard fork [s2x-suspend]. On S17 E43 he said of the scaling agreements, “These agreements were silly in my view” [ep-s17e43-silly]. He added: “I guess they put BitGo's name on the New York agreement without my permission once, after I explicitly told them not” [ep-s17e43-nya]. He also said “I supported the SegWit2x” and “in the end, the community said no” [ep-s17e43-2x]. Bitcoin Takeover's Fork Wars timeline flags BitGo as an erroneous NYA listing [btk-forkwars].", "aliases": "bitgo belshe custody multisig", "refs": ["btk-forkwars", "ep-s17e43-2x", "ep-s17e43-nya", "ep-s17e43-silly", "s2x-suspend"], "url": "/wiki/bitgo/"}, {"id": "bitgo#421", "slug": "bitgo", "title": "BitGo", "section": "Heard on Bitcoin Takeover", "text": "BitGo CEO Mike Belshe has been a guest twice: S16 E1, ‘Mike Belshe on BitGo, Self Custody & The Future of Bitcoin’ (January 2025) [btk-ep-s16e1]; S17 E43, ‘Mike Belshe on BitGo, Quantum & Clarity’ (September 2026) [btk-ep-s17e43].", "aliases": "bitgo belshe custody multisig", "refs": ["btk-ep-s16e1", "btk-ep-s17e43"], "url": "/wiki/bitgo/"}, {"id": "bithereum#infobox", "slug": "bithereum", "title": "Bithereum (BTH)", "section": "Summary and infobox", "text": "A fork that copied Bitcoin up to block 491,406 (24 Oct 2017) but only started its own chain on 12 November 2017, with Equihash and replay protection. Last copied block: 491,406 (24 Oct 2017) [bth2-readme]; First own block: 491,407 (12 Nov 2017) [bth2-readme]; Proof of work: Equihash [bth2-readme]; Replay protection: SIGHASH_FORK_ID [bth2-readme]; Address prefixes: B and H [bth2-readme]", "aliases": "bth bithereum", "refs": ["bth2-readme"], "url": "/wiki/bithereum/"}, {"id": "bithereum#takeover", "slug": "bithereum", "title": "Bithereum (BTH)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bithereum's README gives the same two blocks and dates as Bitcoin Gold — last copied 491,406 on 24 October, own chain from 491,407 on 12 November 2017. It also shares the BTH ticker with Bitcoin Hot. [bth2-readme] [btk-btg]", "aliases": "bth bithereum", "refs": ["bth2-readme", "btk-btg"], "url": "/wiki/bithereum/"}, {"id": "bithereum#424", "slug": "bithereum", "title": "Bithereum (BTH)", "section": "Fork", "text": "The README says Bithereum “began as a fork of Bitcoin after block height 491406 on Tue, 24 Oct 2017 01:17:35 GMT and began being mined as a separate chain at block height 491407 on Sun, 12 Nov 2017 13:34:01 GMT” [bth2-readme]. Any address holding Bitcoin at block 491406 “held an equal number of Bithereum” after the fork [bth2-readme].", "aliases": "bth bithereum", "refs": ["bth2-readme"], "url": "/wiki/bithereum/"}, {"id": "bithereum#425", "slug": "bithereum", "title": "Bithereum (BTH)", "section": "Design", "text": "The README lists an Equihash proof of work, per-block difficulty adjustment, “Replay protection (SIGHASH_FORK_ID)” and addresses with prefixes of B and H [bth2-readme]. Its ticker, BTH, is also used by Bitcoin Hot [bth2-readme]. The block numbers and dates match those Bitcoin Takeover gives for Bitcoin Gold [btk-btg].", "aliases": "bth bithereum", "refs": ["bth2-readme", "btk-btg"], "url": "/wiki/bithereum/"}, {"id": "bitmain#infobox", "slug": "bitmain", "title": "Bitmain", "section": "Summary and infobox", "text": "The Beijing ASIC maker co-founded by Jihan Wu and Micree Zhan, operator of Antpool and BTC.com, and a major Bitcoin Cash backer. Founded: 2013 by Micree Zhan and Jihan Wu [wp-bitmain]; Headquarters: Beijing [wp-bitmain]; Business: ASIC chips and Antminer mining hardware [wp-bitmain]; Pools: BTC.com and Antpool [wp-bitmain]; Agreements: Hong Kong Roundtable (both co-CEOs); New York Agreement [hk-letter] [nya-letter]; 2018 split: Sided with Bitcoin ABC alongside Roger Ver [wp-bitmain]", "aliases": "antpool btc.com antminer", "refs": ["hk-letter", "nya-letter", "wp-bitmain"], "url": "/wiki/bitmain/"}, {"id": "bitmain#takeover", "slug": "bitmain", "title": "Bitmain", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: no company shows up in more fork-history documents. Bitmain's co-CEOs signed in Hong Kong, it was on the New York list, its pool mined the last common block before Bitcoin Cash, and it backed ABC in 2018. [hk-letter] [nya-letter] [btk-bch]", "aliases": "antpool btc.com antminer", "refs": ["btk-bch", "hk-letter", "nya-letter"], "url": "/wiki/bitmain/"}, {"id": "bitmain#428", "slug": "bitmain", "title": "Bitmain", "section": "Company", "text": "Bitmain was founded in 2013 by Micree Zhan and Jihan Wu and is headquartered in Beijing [wp-bitmain]. Its first product, the Antminer S1, produced 180 gigahashes per second [wp-bitmain]. It also operates BTC.com and Antpool, historically two of the largest Bitcoin mining pools [wp-bitmain].", "aliases": "antpool btc.com antminer", "refs": ["wp-bitmain"], "url": "/wiki/bitmain/"}, {"id": "bitmain#429", "slug": "bitmain", "title": "Bitmain", "section": "In the block size war", "text": "Both co-CEOs, Jihan Wu and Micree Zhan, signed the 2016 Hong Kong Roundtable statement [hk-letter]. Bitmain was a supporter of the 2017 New York Agreement and offered engineering support for its upgrades [nya-letter]. The last block shared by Bitcoin and Bitcoin Cash, 478,558, was mined by BTC.com [btk-bch].", "aliases": "antpool btc.com antminer", "refs": ["btk-bch", "hk-letter", "nya-letter"], "url": "/wiki/bitmain/"}, {"id": "bitmain#430", "slug": "bitmain", "title": "Bitmain", "section": "Bitcoin Cash", "text": "Antpool sent 12% of the Bitcoin Cash it mined to irrecoverable addresses in an effort to support the price [wp-bitmain]. Bitmain sided with Bitcoin ABC, alongside Roger Ver, in the 2018 split [wp-bitmain]. In December 2018 it laid off about half of its 3,000 staff [wp-bitmain].", "aliases": "antpool btc.com antminer", "refs": ["wp-bitmain"], "url": "/wiki/bitmain/"}, {"id": "bitmain#431", "slug": "bitmain", "title": "Bitmain", "section": "Heard on Bitcoin Takeover", "text": "Braiins' Kristian Csepcsar said on S17 E14 (March 2026): “It's very difficult to challenge the position of Bitmain.” [ep-s17e14-q4233]", "aliases": "antpool btc.com antminer", "refs": ["ep-s17e14-q4233"], "url": "/wiki/bitmain/"}, {"id": "bitvote#infobox", "slug": "bitvote", "title": "Bitvote (BTV)", "section": "Summary and infobox", "text": "A January 2018 fork at block 505,050 that switched to the CryptoNight proof of work, pitched as Satoshi's one-CPU-one-vote. Fork height: 505,050 [bth-review]; Block 505,050 time: 2018-01-19 21:58:53 UTC [btc-505050]; Ratio: 1:1 [btv-site]; Proof of work: CryptoNight [btv-readme]; Supply: 21 million; 2-minute blocks [btv-site]; 2019 list: “seems like a waste of my resources to compile/sync/test (sorry)” [bth-review]", "aliases": "btv bitvote cryptonight vote", "refs": ["btc-505050", "bth-review", "btv-readme", "btv-site"], "url": "/wiki/bitvote/"}, {"id": "bitvote#takeover", "slug": "bitvote", "title": "Bitvote (BTV)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitvote forked at the same block as Bitcoin Smart, so one Bitcoin block produced at least two airdrop claims. [bth-review]", "aliases": "btv bitvote cryptonight vote", "refs": ["bth-review"], "url": "/wiki/bitvote/"}, {"id": "bitvote#434", "slug": "bitvote", "title": "Bitvote (BTV)", "section": "Pitch", "text": "The project's README says “Bitvote is a fork of Bitcoin, and its abbreviation is BTV” and that “Bitvote uses the CryptoNight algorithm, which responds to Satoshi Nakamoto's vision of one-CPU-one-vote” [btv-readme]. It promises no premining and says smart contracts and the lightning network would be added later [btv-readme].", "aliases": "btv bitvote cryptonight vote", "refs": ["btv-readme"], "url": "/wiki/bitvote/"}, {"id": "bitvote#435", "slug": "bitvote", "title": "Bitvote (BTV)", "section": "Launch", "text": "The archived site, captured on 1 February 2018, opens with “Bitvote forked successfully” and dates the main-chain release to 2018/1/20 [btv-site]. Its FAQ says BTV would go to BTC holders “as the ratio of 1:1” and that “Its total amount is 21 million, and the block time is 2 minutes” [btv-site].", "aliases": "btv bitvote cryptonight vote", "refs": ["btv-site"], "url": "/wiki/bitvote/"}, {"id": "bitvote#436", "slug": "bitvote", "title": "Bitvote (BTV)", "section": "Record", "text": "The 2019 fork list gives “fork at 505050”, the same height it lists for Bitcoin Smart, and links the repository bitcoinvote/bitcoin [bth-review]. Block 505,050 was mined on 19 January 2018 [btc-505050]. The reviewer did not test it, marking it “seems like a waste of my resources to compile/sync/test (sorry)” [bth-review].", "aliases": "btv bitvote cryptonight vote", "refs": ["btc-505050", "bth-review"], "url": "/wiki/bitvote/"}, {"id": "block-size-war#infobox", "slug": "block-size-war", "title": "Block size war", "section": "Summary and infobox", "text": "The 2015–2017 fight over Bitcoin's 1 MB limit that produced the first durable chain split. Period: 2015 to 2017 [btk-bch]; Trigger: The 1 MB MAX_BLOCK_SIZE constant (July 2010) [c-1mb]; Big-block clients: Bitcoin XT (BIP101), Classic, Unlimited [btk-bch]; Outcome on Bitcoin: SegWit locked in 9 Aug 2017, active 24 Aug 2017 [btk-allforks]; Split: Bitcoin Cash, 1 August 2017 (last common block 478,558) [btk-bch]; Full timeline: /fork-wars/ [btk-forkwars]", "aliases": "", "refs": ["btk-allforks", "btk-bch", "btk-forkwars", "c-1mb"], "url": "/wiki/block-size-war/"}, {"id": "block-size-war#takeover", "slug": "block-size-war", "title": "Block size war", "section": "Takeover view (editorial opinion)", "text": "Fork Wars is the long-form version of this article, with a dated timeline, a stance board for every major actor and the two books side by side. The wiki entry is the short version that the terminal can quote. [btk-forkwars] [ep-s16e60]", "aliases": "", "refs": ["btk-forkwars", "ep-s16e60"], "url": "/wiki/block-size-war/"}, {"id": "block-size-war#439", "slug": "block-size-war", "title": "Block size war", "section": "Summary", "text": "For roughly two years, from 2015 to the summer of 2017, Bitcoin users argued over the 1 MB block size limit. One side wanted it raised so that on-chain payments stayed cheap; the other wanted it kept and capacity added through Segregated Witness and second layers such as Lightning [btk-bch]. The full dated history, with podcast quotes and listen links, is on Fork Wars [btk-forkwars].", "aliases": "", "refs": ["btk-bch", "btk-forkwars"], "url": "/wiki/block-size-war/"}, {"id": "block-size-war#440", "slug": "block-size-war", "title": "Block size war", "section": "Big-block proposals", "text": "Bitcoin XT (BIP101, Gavin Andresen and Mike Hearn) proposed 8 MB blocks doubling every two years until 2036; Bitcoin Classic settled on 2 MB; Bitcoin Unlimited dropped fixed numbers for \"emergent consensus\". None reached activation [btk-bch].", "aliases": "", "refs": ["btk-bch"], "url": "/wiki/block-size-war/"}, {"id": "block-size-war#441", "slug": "block-size-war", "title": "Block size war", "section": "Resolution", "text": "In June 2017 Bitcoin ABC, led by Amaury Séchet, published a user-activated hard fork specification as a counter to BIP148 [btk-bch]. Bitcoin Cash split on 1 August 2017; SegWit locked in on Bitcoin on 9 August and activated at block 481,824 on 24 August 2017 [btk-allforks]. Jonathan Bier, author of The Blocksize War, discussed the period on Bitcoin Takeover S16 E60 [ep-s16e60].", "aliases": "", "refs": ["btk-allforks", "btk-bch", "ep-s16e60"], "url": "/wiki/block-size-war/"}, {"id": "block-size-war#442", "slug": "block-size-war", "title": "Block size war", "section": "Heard on Bitcoin Takeover", "text": "On S17 E35 (August 2026), Vinny Lingham argued: “We have the crypto ecosystem because the block sizes on Bitcoin was constrained.” [ep-s17e35-q545]", "aliases": "", "refs": ["ep-s17e35-q545"], "url": "/wiki/block-size-war/"}, {"id": "blockstream#infobox", "slug": "blockstream", "title": "Blockstream", "section": "Summary and infobox", "text": "The Bitcoin infrastructure company co-founded by Adam Back, Pieter Wuille and Gregory Maxwell in 2014. Founded: 2014 [wp-blockstream]; Founders: Adam Back, with Pieter Wuille, Gregory Maxwell and others [wp-blockstream]; Headquarters: Menlo Park, California [wp-blockstream]; Funding: $21 million seed (2014); $210 million Series B (Aug 2021) [wp-blockstream]; Hong Kong Roundtable: Adam Back signed as President [hk-letter]; 2026: SPAC merger with Cantor Fitzgerald cancelled in July [wp-blockstream]", "aliases": "liquid", "refs": ["hk-letter", "wp-blockstream"], "url": "/wiki/blockstream/"}, {"id": "blockstream#takeover", "slug": "blockstream", "title": "Blockstream", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Blockstream is the big-block side's favourite villain in fork history. This wiki sticks to what is documented: its founders' signatures on the 2015 roadmap and the Hong Kong statement. [roadmap-2015] [hk-letter]", "aliases": "liquid", "refs": ["hk-letter", "roadmap-2015"], "url": "/wiki/blockstream/"}, {"id": "blockstream#445", "slug": "blockstream", "title": "Blockstream", "section": "Company", "text": "Blockstream was founded in 2014 by cryptographer Adam Back with Bitcoin developers and cryptographers including Pieter Wuille and Gregory Maxwell [wp-blockstream]. It is headquartered in Menlo Park, California, and raised $21 million in seed funding in 2014 [wp-blockstream]. In August 2021 it raised $210 million at a $3.2 billion valuation [wp-blockstream].", "aliases": "liquid", "refs": ["wp-blockstream"], "url": "/wiki/blockstream/"}, {"id": "blockstream#446", "slug": "blockstream", "title": "Blockstream", "section": "In the block size war", "text": "Back, Maxwell and Wuille are among the signatories of the December 2015 roadmap “Capacity increases for the Bitcoin system” [roadmap-2015]. Back signed the February 2016 Hong Kong Roundtable statement as Blockstream's President [hk-letter].", "aliases": "liquid", "refs": ["hk-letter", "roadmap-2015"], "url": "/wiki/blockstream/"}, {"id": "blockstream#447", "slug": "blockstream", "title": "Blockstream", "section": "Recent", "text": "In July 2026 Blockstream and Cantor Fitzgerald cancelled a planned SPAC merger that would have listed Blockstream on Nasdaq, citing “current market conditions” [wp-blockstream].", "aliases": "liquid", "refs": ["wp-blockstream"], "url": "/wiki/blockstream/"}, {"id": "bloq#infobox", "slug": "bloq", "title": "Bloq", "section": "Summary and infobox", "text": "Blockchain company co-founded by Matthew Roszak and Jeff Garzik, a New York Agreement supporter, and the team behind United Bitcoin's launch. Co-founder and chairman: Matthew Roszak [wp-roszak]; CEO: Jeff Garzik (per his Bitcointalk signature) [garzik-patch]; New York Agreement: Listed as Bloq (United States) [nya-letter]; Products (2026 site): Vesper, Metronome, Titan, Lumerin, BloqCloud [bloq-site]", "aliases": "bloq roszak vesper", "refs": ["bloq-site", "garzik-patch", "nya-letter", "wp-roszak"], "url": "/wiki/bloq/"}, {"id": "bloq#takeover", "slug": "bloq", "title": "Bloq", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bloq links the SegWit2x compromise to a later fork — it backed the New York Agreement and, when 2x failed, its founders announced United Bitcoin. [ubtc-news] [nya-letter]", "aliases": "bloq roszak vesper", "refs": ["nya-letter", "ubtc-news"], "url": "/wiki/bloq/"}, {"id": "bloq#450", "slug": "bloq", "title": "Bloq", "section": "Company", "text": "Wikipedia describes Matthew Roszak as “the co-founder and chairman of Bloq, a blockchain startup company” [wp-roszak]. Jeff Garzik's Bitcointalk signature reads “Jeff Garzik, Bloq CEO, former bitcoin core dev team” [garzik-patch]. In November 2026 Bloq's homepage lists products including Vesper, Metronome, Titan, Lumerin and BloqCloud [bloq-site].", "aliases": "bloq roszak vesper", "refs": ["bloq-site", "garzik-patch", "wp-roszak"], "url": "/wiki/bloq/"}, {"id": "bloq#451", "slug": "bloq", "title": "Bloq", "section": "Forks", "text": "The New York Agreement lists “Bloq (United States)” among supporters and Bloq among companies offering technical help [nya-letter]. After SegWit2x failed, Bitcoin.com News reported that “Bloq founder Jeff Garzik” and “the chairman of Bloq, Matthew Roszak” would launch United Bitcoin [ubtc-news].", "aliases": "bloq roszak vesper", "refs": ["nya-letter", "ubtc-news"], "url": "/wiki/bloq/"}, {"id": "bob-summerwill#infobox", "slug": "bob-summerwill", "title": "Bob Summerwill", "section": "Summary and infobox", "text": "Former Ethereum Foundation C++ developer and Executive Director of the ETC Cooperative (2019–2024); a 2026 Bitcoin Takeover guest on Ethereum Classic and Bitcoin forks. ETC Cooperative: Executive Director, 2019–2024 [bob-about]; Ethereum Foundation: Core developer on the C++ client [bob-about]; Earlier career: Fifteen years at Electronic Arts [bob-about]; Events: Proof of Work Summit 2023 and 2024 [bob-about]; Based in: Vancouver, BC [gh-bob]", "aliases": "bob summerwill etc cooperative", "refs": ["bob-about", "gh-bob"], "url": "/wiki/bob-summerwill/"}, {"id": "bob-summerwill#takeover", "slug": "bob-summerwill", "title": "Bob Summerwill", "section": "Takeover view (editorial opinion)", "text": "Guest on S17 E42 in September 2026, where he retold the DAO fork from inside the Ethereum Foundation and described the BIP-110 chain grinding to a halt. [ep-s17e42-cpp] [ep-s17e42-stall]", "aliases": "bob summerwill etc cooperative", "refs": ["ep-s17e42-cpp", "ep-s17e42-stall"], "url": "/wiki/bob-summerwill/"}, {"id": "bob-summerwill#454", "slug": "bob-summerwill", "title": "Bob Summerwill", "section": "Career", "text": "Summerwill's site says he spent fifteen years at Electronic Arts, then was a “core developer on the Ethereum Foundation's C++ client”, co-lead architect at the launch of the Enterprise Ethereum Alliance and “Executive Director of the ETC Cooperative from 2019 to 2024” [bob-about]. It says he organised the Proof of Work Summit conferences in 2023 and 2024 and runs The Early Days of Ethereum history project [bob-about]. His GitHub profile gives Vancouver, BC [gh-bob].", "aliases": "bob summerwill etc cooperative", "refs": ["bob-about", "gh-bob"], "url": "/wiki/bob-summerwill/"}, {"id": "bob-summerwill#455", "slug": "bob-summerwill", "title": "Bob Summerwill", "section": "On Bitcoin Takeover", "text": "On S17 E42 he said his ETC Cooperative role “started at the beginning of 2019”, while he had been “a frontline witness” to the 2016 fork [ep-s17e42-coop]. He said he was working for the Ethereum Foundation then, “on the C++ client, which Gavin Wood had started” [ep-s17e42-cpp]. He described Ethereum Classic's ethos as “Bitcoin philosophy, Ethereum technology” [ep-s17e42-ethos], and discussed BIP-110 and the chain that stalled after it [ep-s17e42-stall] [ep-s17e42-stfu].", "aliases": "bob summerwill etc cooperative", "refs": ["ep-s17e42-coop", "ep-s17e42-cpp", "ep-s17e42-ethos", "ep-s17e42-stall", "ep-s17e42-stfu"], "url": "/wiki/bob-summerwill/"}, {"id": "bobby-lee#infobox", "slug": "bobby-lee", "title": "Bobby Lee", "section": "Summary and infobox", "text": "Co-founder and CEO of BTC China, later BTCC, a Hong Kong Roundtable signatory, and Charlie Lee's brother. Co-founded: BTC China (BTCC), 2011 [wp-btcc]; Role: Chief executive officer [wp-btcc]; Hong Kong Roundtable: Signed as CEO, BTCC [hk-letter]; Brother: Charlie Lee [ep-s15e34-bobby]; Later product: Ballet wallets (as described by Charlie Lee) [ep-s15e34-ballet]", "aliases": "bobby btc china ballet", "refs": ["ep-s15e34-ballet", "ep-s15e34-bobby", "hk-letter", "wp-btcc"], "url": "/wiki/bobby-lee/"}, {"id": "bobby-lee#takeover", "slug": "bobby-lee", "title": "Bobby Lee", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: the Lee brothers sit on both sides of the fork story, one running the biggest Chinese exchange at the Hong Kong Roundtable, the other running the oldest surviving Bitcoin code fork. [hk-letter] [ep-s15e34-bobby]", "aliases": "bobby btc china ballet", "refs": ["ep-s15e34-bobby", "hk-letter"], "url": "/wiki/bobby-lee/"}, {"id": "bobby-lee#458", "slug": "bobby-lee", "title": "Bobby Lee", "section": "BTCC", "text": "Wikipedia says BTCC was founded in 2011 by Bobby Lee, Yang Linke and Huang Xiaoyu as BTC China, initially a part-time project for Lee, who became CEO when it incorporated in 2013 [wp-btcc]. Wikipedia says it became the largest cryptocurrency exchange by volume globally in November 2013 [wp-btcc]. See BTCC.", "aliases": "bobby btc china ballet", "refs": ["wp-btcc"], "url": "/wiki/bobby-lee/"}, {"id": "bobby-lee#459", "slug": "bobby-lee", "title": "Bobby Lee", "section": "Hong Kong Roundtable", "text": "The February 2016 Roundtable statement lists Bobby Lee as CEO of BTCC and Samson Mow as its COO [hk-letter]. BTCC also appears among the New York Agreement signatories in May 2017 [nya-letter].", "aliases": "bobby btc china ballet", "refs": ["hk-letter", "nya-letter"], "url": "/wiki/bobby-lee/"}, {"id": "bobby-lee#460", "slug": "bobby-lee", "title": "Bobby Lee", "section": "Brother of Charlie Lee", "text": "On S15 E34 Charlie Lee said he would be on a Consensus panel “with my brother Bobby” [ep-s15e34-bobby]. In the same episode he recommended funded Ballet wallets as gifts and said “Bobby can't steal coins from Ballet wallets” [ep-s15e34-ballet].", "aliases": "bobby btc china ballet", "refs": ["ep-s15e34-ballet", "ep-s15e34-bobby"], "url": "/wiki/bobby-lee/"}, {"id": "btc-com#infobox", "slug": "btc-com", "title": "BTC.com", "section": "Summary and infobox", "text": "Bitmain-operated mining pool and block explorer that mined the last block shared by Bitcoin and Bitcoin Cash; the domain now hosts a “BTC.com Museum”. Operator: Bitmain (with Antpool) [wp-bitmain]; New York Agreement: Listed as btc.com (China) [nya-letter]; Block 478,558: Mined with a /NYA/ tag; last common BTC/BCH block [btk-bch]; Domain (Nov 2026): “BTC.com Museum” [btccom-site]", "aliases": "btc.com btccom museum", "refs": ["btccom-site", "btk-bch", "nya-letter", "wp-bitmain"], "url": "/wiki/btc-com/"}, {"id": "btc-com#takeover", "slug": "btc-com", "title": "BTC.com", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: the last block Bitcoin and Bitcoin Cash share was mined by a Bitmain pool that had signed the agreement it advertised, which is the split in one coinbase. [btk-bch] [nya-letter]", "aliases": "btc.com btccom museum", "refs": ["btk-bch", "nya-letter"], "url": "/wiki/btc-com/"}, {"id": "btc-com#463", "slug": "btc-com", "title": "BTC.com", "section": "Pool", "text": "Wikipedia says Bitmain “operates BTC.com and Antpool, historically two of the largest mining pools for bitcoin” [wp-bitmain]. The New York Agreement lists “btc.com (China)” among its supporters [nya-letter].", "aliases": "btc.com btccom museum", "refs": ["nya-letter", "wp-bitmain"], "url": "/wiki/btc-com/"}, {"id": "btc-com#464", "slug": "btc-com", "title": "BTC.com", "section": "The split", "text": "Bitcoin Takeover's Bitcoin Cash feature records that block 478,558, the last block Bitcoin and Bitcoin Cash share, was “mined by BTC.com with a /NYA/ tag in the coinbase” at 13:16:14 UTC [btk-bch].", "aliases": "btc.com btccom museum", "refs": ["btk-bch"], "url": "/wiki/btc-com/"}, {"id": "btc-com#465", "slug": "btc-com", "title": "BTC.com", "section": "Today", "text": "As of 13 November 2026 the btc.com domain serves a site titled “BTC.com Museum | Bitcoin History & Primary Sources” [btccom-site]. Who runs it now is not sourced in this wiki [btccom-site].", "aliases": "btc.com btccom museum", "refs": ["btccom-site"], "url": "/wiki/btc-com/"}, {"id": "btcc#infobox", "slug": "btcc", "title": "BTCC", "section": "Summary and infobox", "text": "China's leading early bitcoin exchange (BTC China), a signatory of both the 2016 Hong Kong Roundtable and the 2017 New York Agreement. Founded: 2011, as BTC China [wp-btcc]; Founders: Bobby Lee, Yang Linke, Huang Xiaoyu [wp-btcc]; Peak: Largest cryptocurrency exchange by volume, November 2013 [wp-btcc]; China trading: Ceased in 2017 [wp-btcc]; Sold: January 2018, to an unnamed Hong Kong firm [wp-btcc]; Agreements signed: Hong Kong Roundtable (2016); New York Agreement (2017) [hk-letter] [nya-letter]", "aliases": "btcc btc china exchange", "refs": ["hk-letter", "nya-letter", "wp-btcc"], "url": "/wiki/btcc/"}, {"id": "btcc#takeover", "slug": "btcc", "title": "BTCC", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: BTCC is the company that put two future protagonists at the 2016 table, Bobby Lee as CEO and Samson Mow as COO, and then signed the 2017 deal that tried to deliver the 2 MB half. [hk-letter] [nya-letter]", "aliases": "btcc btc china exchange", "refs": ["hk-letter", "nya-letter"], "url": "/wiki/btcc/"}, {"id": "btcc#468", "slug": "btcc", "title": "BTCC", "section": "History", "text": "Wikipedia says BTCC was founded in 2011 by Bobby Lee, Yang Linke and Huang Xiaoyu as BTC China, incorporated in 2013 with a Shanghai headquarters, and became the largest cryptocurrency exchange by volume globally in November 2013 [wp-btcc]. It ceased trading in China in 2017 because of regulatory changes and was bought by an unnamed firm in Hong Kong in January 2018 [wp-btcc].", "aliases": "btcc btc china exchange", "refs": ["wp-btcc"], "url": "/wiki/btcc/"}, {"id": "btcc#469", "slug": "btcc", "title": "BTCC", "section": "Block size war", "text": "The Hong Kong Roundtable statement of February 2016 lists Bobby Lee as BTCC's CEO and Samson Mow as COO [hk-letter]. BTCC is also on the list of New York Agreement signatories of May 2017 [nya-letter].", "aliases": "btcc btc china exchange", "refs": ["hk-letter", "nya-letter"], "url": "/wiki/btcc/"}, {"id": "byteball#infobox", "slug": "byteball", "title": "Byteball / Obyte (GBYTE)", "section": "Summary and infobox", "text": "A DAG ledger announced in September 2016 with no mining, which promised 98% of its coins to Bitcoin holders who linked their addresses; now called Obyte. Announced: 5 Sep 2016 by tonych [obyte-ann]; Former name: Byteball [obyte-ann]; Ledger: DAG; no PoW, no PoS, no mining [obyte-ann]; Distribution (2016 text): 98% to Bitcoin holders who linked addresses; 1% to the founder [byteball-2016]; Snapshot example: “e.g. in block 437000” (2016 text) [byteball-2016]", "aliases": "obyte gbyte bytes blackbytes dag tonych", "refs": ["byteball-2016", "obyte-ann"], "url": "/wiki/byteball/"}, {"id": "byteball#takeover", "slug": "byteball", "title": "Byteball / Obyte (GBYTE)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Byteball shows the airdrop idea without the fork — no shared chain, just a promise to Bitcoin holders who proved what they held. [byteball-2016]", "aliases": "obyte gbyte bytes blackbytes dag tonych", "refs": ["byteball-2016"], "url": "/wiki/byteball/"}, {"id": "byteball#472", "slug": "byteball", "title": "Byteball / Obyte (GBYTE)", "section": "Announcement", "text": "The Bitcointalk thread opened by tonych on 5 September 2016 now carries the name Obyte, with the line “Former name: Byteball” [obyte-ann]. It describes a ledger built as a DAG, without proof of work, proof of stake or mining [obyte-ann].", "aliases": "obyte gbyte bytes blackbytes dag tonych", "refs": ["obyte-ann"], "url": "/wiki/byteball/"}, {"id": "byteball#473", "slug": "byteball", "title": "Byteball / Obyte (GBYTE)", "section": "The Bitcoin distribution", "text": "The 2016 announcement, as quoted in a reply the same day, said “98% of all bytes and blackbytes (the private untraceable currency) will be distributed among bitcoin holders who link their bitcoin and byteball addresses before the launch”, with “1% I reserve for myself” [byteball-2016]. Holders were to link addresses with a small BTC payment, and bytes would be paid in proportion to the BTC on the linked address “in a specific bitcoin block (e.g. in block 437000 which is expected late October - early November)” [byteball-2016]. Which block was finally used is not sourced here [byteball-2016].", "aliases": "obyte gbyte bytes blackbytes dag tonych", "refs": ["byteball-2016"], "url": "/wiki/byteball/"}, {"id": "calvin-ayre#infobox", "slug": "calvin-ayre", "title": "Calvin Ayre", "section": "Summary and infobox", "text": "Bodog founder and the main financial backer of the BSV camp: linked to Craig Wright from 2016, owner of CoinGeek, and controlling owner of nChain from 2023. Born: 25 May 1961 [wp-ayre]; Known for: Founder of Bodog and the Ayre Group [wp-ayre]; CoinGeek: Acquired August 2017 [wp-ayre]; nChain: Ayre Group took a controlling interest in 2023 [wp-ayre]; 2017 plea: Pled guilty to a single misdemeanor; other charges dropped [wp-ayre]; Fork: Backed Bitcoin SV in 2018 [btk-bsv]", "aliases": "ayre bodog coingeek", "refs": ["btk-bsv", "wp-ayre"], "url": "/wiki/calvin-ayre/"}, {"id": "calvin-ayre#takeover", "slug": "calvin-ayre", "title": "Calvin Ayre", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: on S17 E39 Kurt Wuckert Jr., who works on the BSV side, still called Ayre “the most significant player… since the beginning”. Every account of the BSV split, friendly or hostile, runs through his money. [ep-s17e39-ayre] [btk-bsv]", "aliases": "ayre bodog coingeek", "refs": ["btk-bsv", "ep-s17e39-ayre"], "url": "/wiki/calvin-ayre/"}, {"id": "calvin-ayre#476", "slug": "calvin-ayre", "title": "Calvin Ayre", "section": "Bodog", "text": "Wikipedia says Ayre launched the online gambling company Bodog in 2000, that its success made him a billionaire, and that he appeared on the cover of Forbes' 2006 billionaires issue [wp-ayre]. It reports that he was indicted in Maryland in 2012 on illegal gambling charges and in 2017 pled guilty to a single misdemeanor, with the other charges dropped [wp-ayre].", "aliases": "ayre bodog coingeek", "refs": ["wp-ayre"], "url": "/wiki/calvin-ayre/"}, {"id": "calvin-ayre#477", "slug": "calvin-ayre", "title": "Calvin Ayre", "section": "Craig Wright and BSV", "text": "Wikipedia says Andrew O'Hagan's June 2016 account named Ayre as part of the business operation behind Craig Wright's claim to be Satoshi and possibly as the financial backer of the $30 million acquisition of Wright's assets [wp-ayre]. Ayre acquired CoinGeek in August 2017, briefly supported Bitcoin Cash and withdrew that support in 2018 because of protocol changes he opposed [wp-ayre]. Bitcoin Takeover's BSV article says his CoinGeek pool and the media outlet of the same name backed Bitcoin SV in the 2018 split [btk-bsv].", "aliases": "ayre bodog coingeek", "refs": ["btk-bsv", "wp-ayre"], "url": "/wiki/calvin-ayre/"}, {"id": "calvin-ayre#478", "slug": "calvin-ayre", "title": "Calvin Ayre", "section": "nChain and mining", "text": "Wikipedia says Ayre sold his Bitcoin mining operations to TAAL in 2020 and that the Ayre Group acquired a controlling interest in nChain in 2023 [wp-ayre]. Kurt Wuckert Jr. estimated on S17 E39 that Ayre has invested “hundreds of millions of dollars or something to that effect” [ep-s17e39-nchain]. On S17 E26 Steve Thurmond called Ayre Wright's financial backer, which is his characterisation [ep-s17e26-ayre].", "aliases": "ayre bodog coingeek", "refs": ["ep-s17e26-ayre", "ep-s17e39-nchain", "wp-ayre"], "url": "/wiki/calvin-ayre/"}, {"id": "casa#infobox", "slug": "casa", "title": "Casa", "section": "Summary and infobox", "text": "Bitcoin self-custody company known for multisig vaults; Jameson Lopp is a co-founder, and Nick Neuman took over as CEO in 2020. Product: Multisig self-custody and inheritance [casa-site]; Keysets (Feb 2019): Mobile Key, 2-of-3 Basic Multisig, 3-of-5 Key Shield [casa-keymaster]; CEO from 2020: Nick Neuman [casa-2019]; Co-founder: Jameson Lopp [lopp-site]; Founded: Not sourced [casa-2019]", "aliases": "casa keymaster multisig welch neuman", "refs": ["casa-2019", "casa-keymaster", "casa-site", "lopp-site"], "url": "/wiki/casa/"}, {"id": "casa#takeover", "slug": "casa", "title": "Casa", "section": "Takeover view (editorial opinion)", "text": "Mentioned on S17 E47, where Vlad named BitGo and Casa as companies offering convenient multisig self-custody. [ep-s17e47-casa]", "aliases": "casa keymaster multisig welch neuman", "refs": ["ep-s17e47-casa"], "url": "/wiki/casa/"}, {"id": "casa#481", "slug": "casa", "title": "Casa", "section": "Company", "text": "Casa's site calls itself “The home for bitcoin wealth” and offers long-term security “for bitcoin and stablecoins” [casa-site]. On 28 February 2019 Jeremy Welch announced that Casa Keymaster supported three keysets: Mobile Key, “2-of-3 Basic Multisig” and “3-of-5 Key Shield” [casa-keymaster].", "aliases": "casa keymaster multisig welch neuman", "refs": ["casa-keymaster", "casa-site"], "url": "/wiki/casa/"}, {"id": "casa#482", "slug": "casa", "title": "Casa", "section": "People", "text": "In January 2020 Welch wrote “I am stepping down as Casa CEO”, naming Nick Neuman CEO and adding Neuman and CTO Jameson Lopp to the board as cofounders [casa-2019]. The same post said Casa had “Shipped thousands of Casa Nodes” in 2019 [casa-2019]. Jameson Lopp's site now lists him as “Casa Co-founder & Chief Security Officer” [lopp-site]. The founding date is not sourced here [casa-2019].", "aliases": "casa keymaster multisig welch neuman", "refs": ["casa-2019", "lopp-site"], "url": "/wiki/casa/"}, {"id": "casey-rodarmor#infobox", "slug": "casey-rodarmor", "title": "Casey Rodarmor", "section": "Summary and infobox", "text": "Creator of Ordinals and inscriptions and the ord software; a Bitcoin Takeover guest in February 2023. Known for: Ordinals and inscriptions [ep-s12e13-witness]; Software: ord (index, explorer, wallet) [ord-readme]; GitHub: casey, since March 2008 [gh-casey]; Website: rodarmor.com [gh-casey]; On the show: 6 Feb 2023 [ep-s12e13-scheme]", "aliases": "casey rodarmor ord ordinals inscriptions", "refs": ["ep-s12e13-scheme", "ep-s12e13-witness", "gh-casey", "ord-readme"], "url": "/wiki/casey-rodarmor/"}, {"id": "casey-rodarmor#takeover", "slug": "casey-rodarmor", "title": "Casey Rodarmor", "section": "Takeover view (editorial opinion)", "text": "Guest on 6 February 2023, weeks after ord 0.4.0. He explained why he did not want to sell NFTs on Ethereum and how Ordinals came out of that. [ep-s12e13-nft] [ep-s12e13-scheme]", "aliases": "casey rodarmor ord ordinals inscriptions", "refs": ["ep-s12e13-nft", "ep-s12e13-scheme"], "url": "/wiki/casey-rodarmor/"}, {"id": "casey-rodarmor#485", "slug": "casey-rodarmor", "title": "Casey Rodarmor", "section": "Ordinals", "text": "Casey Rodarmor's GitHub account, casey, dates from March 2008 and links to rodarmor.com [gh-casey]. On Bitcoin Takeover he said that in late 2021 “I started looking into making NFTs on Ethereum”, but decided he could not feel good about selling them there [ep-s12e13-nft]. He then said: “And I came up with the scheme that now is called ordinals” [ep-s12e13-scheme].", "aliases": "casey rodarmor ord ordinals inscriptions", "refs": ["ep-s12e13-nft", "ep-s12e13-scheme", "gh-casey"], "url": "/wiki/casey-rodarmor/"}, {"id": "casey-rodarmor#486", "slug": "casey-rodarmor", "title": "Casey Rodarmor", "section": "Inscriptions", "text": "He said Ordinals “actually I found out later had been proposed before”, and that the whole protocol “fits on a T-shirt, essentially” [ep-s12e13-prior]. He described putting inscription content “in what is called the witness” [ep-s12e13-witness]. The ord README describes his software as an index, block explorer and command-line wallet [ord-readme]; see Ordinals and inscriptions.", "aliases": "casey rodarmor ord ordinals inscriptions", "refs": ["ep-s12e13-prior", "ep-s12e13-witness", "ord-readme"], "url": "/wiki/casey-rodarmor/"}, {"id": "casey-rodarmor#487", "slug": "casey-rodarmor", "title": "Casey Rodarmor", "section": "On Luke Dashjr", "text": "Asked about Luke Dashjr's opposition, Rodarmor said “I respect Luke deeply as a Bitcoin developer”, and that he had pointed Dashjr to the pattern inscriptions use so a mempool filter could be written [ep-s12e13-luke].", "aliases": "casey rodarmor ord ordinals inscriptions", "refs": ["ep-s12e13-luke"], "url": "/wiki/casey-rodarmor/"}, {"id": "cashtokens#infobox", "slug": "cashtokens", "title": "CashTokens", "section": "Summary and infobox", "text": "Native fungible and non-fungible tokens on Bitcoin Cash, specified in CHIP-2022-02 and activated in the 15 May 2023 network upgrade. Specification: CHIP-2022-02-CashTokens [cashtokens-chip]; Maintainer: Jason Dreyzehner [cashtokens-chip]; Activated: 15 May 2023, 12:00 UTC (median time past 1684152000) [bch-2023-upgrade]; Adds: Fungible tokens and NFTs with commitments [cashtokens-chip]; Same upgrade: P2SH32, minimum transaction size, restricted transaction version [bch-2023-upgrade]; Chain: Bitcoin Cash [bch-2023-upgrade]", "aliases": "cashtokens tokens nft chip", "refs": ["bch-2023-upgrade", "cashtokens-chip"], "url": "/wiki/cashtokens/"}, {"id": "cashtokens#takeover", "slug": "cashtokens", "title": "CashTokens", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: CashTokens is the clearest disagreement between Bitcoin Cash and the man who wrote its first client. Builders on S17 E26 call it a turning point; on S17 E19 Amaury Séchet called it a dead end next to ERC-20. [ep-s17e26-cashtokens] [ep-s17e19-cashtokens]", "aliases": "cashtokens tokens nft chip", "refs": ["ep-s17e19-cashtokens", "ep-s17e26-cashtokens"], "url": "/wiki/cashtokens/"}, {"id": "cashtokens#490", "slug": "cashtokens", "title": "CashTokens", "section": "Specification", "text": "The CHIP “enables two new primitives on Bitcoin Cash: fungible tokens and non-fungible tokens” [cashtokens-chip]. Each NFT carries a commitment, “a short byte string attested to by the issuer”, which the CHIP argues lets contracts issue verifiable messages without a trusted private key [cashtokens-chip].", "aliases": "cashtokens tokens nft chip", "refs": ["cashtokens-chip"], "url": "/wiki/cashtokens/"}, {"id": "cashtokens#491", "slug": "cashtokens", "title": "CashTokens", "section": "Activation", "text": "The Bitcoin Cash Node upgrade specification lists CashTokens with P2SH32, a minimum transaction size and a restricted transaction version, taking effect once median time past reached 1684152000, which is 12:00 UTC on 15 May 2023 [bch-2023-upgrade]. Chipnet activated it six months earlier, on 15 November 2022 [bch-2023-upgrade].", "aliases": "cashtokens tokens nft chip", "refs": ["bch-2023-upgrade"], "url": "/wiki/cashtokens/"}, {"id": "cashtokens#492", "slug": "cashtokens", "title": "CashTokens", "section": "Views on the podcast", "text": "On S17 E26 FiendishCrypto described the 2023 release of CashTokens as “a turning point” that brought new people and energy [ep-s17e26-cashtokens]. On S17 E19 Amaury Séchet said “the CashTokens stuff, I think, is a dead end, because the industry standard is ERC-20” [ep-s17e19-cashtokens], and called it “Unlimited's idea, essentially” [ep-s17e19-buidea].", "aliases": "cashtokens tokens nft chip", "refs": ["ep-s17e19-buidea", "ep-s17e19-cashtokens", "ep-s17e26-cashtokens"], "url": "/wiki/cashtokens/"}, {"id": "cereneum#infobox", "slug": "cereneum", "title": "Cereneum (CER)", "section": "Summary and infobox", "text": "A 2019 Ethereum ERC-20 staking token airdropped by signed claim to BTC, BCH, BSV, ETH and LTC holders, with a snapshot on 31 May 2019. Type: ERC-20 token and contract [cer-readme]; Snapshot: 31 May 2019, 20:00 UTC [cer-site]; Chains: BTC, BCH, BSV, ETH, LTC [cer-readme]; Claim method: Signed message, Merkle proof [cer-site]", "aliases": "cer cereneum erc20 staking", "refs": ["cer-readme", "cer-site"], "url": "/wiki/cereneum/"}, {"id": "cereneum#takeover", "slug": "cereneum", "title": "Cereneum (CER)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Cereneum belongs with the claim-based airdrops: an Ethereum contract that paid holders of five chains for signing a message. [cer-readme]", "aliases": "cer cereneum erc20 staking", "refs": ["cer-readme"], "url": "/wiki/cereneum/"}, {"id": "cereneum#495", "slug": "cereneum", "title": "Cereneum (CER)", "section": "Design", "text": "The README says “Cereneum is an Ethereum ERC20 token and contract that airdrops to BTC, BCH, BSV, ETH and LTC simultaneously” and that tokens can be staked for interest [cer-readme]. The project would publish each chain's UTXOs and Merkle trees after the snapshot [cer-readme]. The archived site, captured on 9 May 2019, says “The snapshot will be taken on May 31, 2019 at 20:00 UTC.” [cer-site]", "aliases": "cer cereneum erc20 staking", "refs": ["cer-readme", "cer-site"], "url": "/wiki/cereneum/"}, {"id": "cereneum#496", "slug": "cereneum", "title": "Cereneum (CER)", "section": "Rules", "text": "Claimants would sign a message such as “Claim_Cereneum_to_ETHADDRESS” [cer-site]. The site says “All MtGox accounts (BTC, BCH, BSV) prohibited from claiming” and “Millionaire claims reduced by 50%” [cer-site]. It also says “There is no ICO for Cereneum and we are not raising money.” [cer-site] forkdrop's data file gives a date of 2019-05-14 and a “Variable” ratio, which conflicts with the site's 31 May snapshot [fd-data].", "aliases": "cer cereneum erc20 staking", "refs": ["cer-site", "fd-data"], "url": "/wiki/cereneum/"}, {"id": "chandler-guo#infobox", "slug": "chandler-guo", "title": "Chandler Guo", "section": "Summary and infobox", "text": "Chinese Bitcoin investor and miner who announced the Bitcoin God fork for Christmas 2017 and later promoted EthereumPoW. Described as: Chinese Bitcoin and blockchain angel investor [god-ct]; Bitcoin God: Announced for 25 Dec 2017, “real” [god-ct]; EthereumPoW: Promoter (per Bob Summerwill) [ep-s17e42-ethpow]", "aliases": "chandler guo ethereumpow ethw", "refs": ["ep-s17e42-ethpow", "god-ct"], "url": "/wiki/chandler-guo/"}, {"id": "chandler-guo#takeover", "slug": "chandler-guo", "title": "Chandler Guo", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Guo appears at two forks five years apart, Bitcoin God in 2017 and EthereumPoW at Ethereum's move to proof of stake, and on the show the second was called a cash grab. [god-ct] [ep-s17e42-ethpow]", "aliases": "chandler guo ethereumpow ethw", "refs": ["ep-s17e42-ethpow", "god-ct"], "url": "/wiki/chandler-guo/"}, {"id": "chandler-guo#499", "slug": "chandler-guo", "title": "Chandler Guo", "section": "Bitcoin God", "text": "Cointelegraph described Chandler Guo as a “Chinese Bitcoin and Blockchain Angel Investor” who announced his own Bitcoin hard fork, Bitcoin God, to fork off on 25 December 2017 “to be symbolic of me giving candy to all Bitcoin Holders” [god-ct]. Asked whether it was a joke, Guo confirmed it was “real” [god-ct]. Bitcoin.com News also reported the plan in December 2017 [god-news].", "aliases": "chandler guo ethereumpow ethw", "refs": ["god-ct", "god-news"], "url": "/wiki/chandler-guo/"}, {"id": "chandler-guo#500", "slug": "chandler-guo", "title": "Chandler Guo", "section": "EthereumPoW", "text": "Bob Summerwill said on Bitcoin Takeover that “EthereumPoW was really promoted by Chandler Guo”, whom he described as “one of the major Chinese miners” who had also been around at the time of the Ethereum and ETC split [ep-s17e42-ethpow]. He called EthereumPoW “blatantly a cash grab” [ep-s17e42-ethpow]. See Ethereum Classic [ep-s17e42-ethpow].", "aliases": "chandler guo ethereumpow ethw", "refs": ["ep-s17e42-ethpow"], "url": "/wiki/chandler-guo/"}, {"id": "charlie-lee#infobox", "slug": "charlie-lee", "title": "Charlie Lee", "section": "Summary and infobox", "text": "Creator of Litecoin (2011), former Coinbase engineering lead, managing director of the Litecoin Foundation. Known for: Created Litecoin (2011) [ltc-ann]; Roles: Ran engineering at Coinbase; managing director, Litecoin Foundation [btk-ltc-e30]; Takeover episodes: S7 E8 (2020), S11 E5 (2022), S15 E30 and S15 E34 (2024) [btk-ep-s7e8] [btk-ep-s11e5] [btk-ep-s15e30] [btk-ep-s15e34]", "aliases": "coblee", "refs": ["btk-ep-s11e5", "btk-ep-s15e30", "btk-ep-s15e34", "btk-ep-s7e8", "btk-ltc-e30", "ltc-ann"], "url": "/wiki/charlie-lee/"}, {"id": "charlie-lee#takeover", "slug": "charlie-lee", "title": "Charlie Lee", "section": "Takeover view (editorial opinion)", "text": "On S15 E34 he said “a bigger block is still good” within limits — a quote the Fork Wars stance board also uses. [ep-s15e34-blocks] [btk-forkwars]", "aliases": "coblee", "refs": ["btk-forkwars", "ep-s15e34-blocks"], "url": "/wiki/charlie-lee/"}, {"id": "charlie-lee#503", "slug": "charlie-lee", "title": "Charlie Lee", "section": "Litecoin", "text": "Charlie Lee announced Litecoin on Bitcointalk in October 2011 as coblee [ltc-ann]. He later ran engineering at Coinbase and is managing director of the Litecoin Foundation [btk-ltc-e30].", "aliases": "coblee", "refs": ["btk-ltc-e30", "ltc-ann"], "url": "/wiki/charlie-lee/"}, {"id": "charlie-lee#504", "slug": "charlie-lee", "title": "Charlie Lee", "section": "Views", "text": "On Bitcoin Takeover S15 E34 he said a bigger block is still good up to a point, while warning about the trade-offs [ep-s15e34-blocks]. He has also said he was disappointed that Lightning did not take off as much as he expected [ep-s15e34-ln].", "aliases": "coblee", "refs": ["ep-s15e34-blocks", "ep-s15e34-ln"], "url": "/wiki/charlie-lee/"}, {"id": "claim-based-airdrops#infobox", "slug": "claim-based-airdrops", "title": "Claim-based airdrops", "section": "Summary and infobox", "text": "Coins that were not chain splits but let Bitcoin holders claim new tokens: CLAMs, Byteball, Stellar, Bitcore, BTCH, MimbleWimbleCoin and HEX. CLAMs (2014): ~4.6 CLAM per BTC, LTC and DOGE address [clam-ann]; Byteball (2016): Link a BTC address, get bytes [byteball-2016]; Stellar (2017): Claim free lumens until 27 Aug 2017 [bth-review]; MimbleWimbleCoin (2019): Claims closed 2 Jan 2020 [mwc-claiming]; HEX (2019): Airdrops to large BTC holders, per the SEC [sec-heart-complaint]", "aliases": "claim airdrop claims", "refs": ["bth-review", "byteball-2016", "clam-ann", "mwc-claiming", "sec-heart-complaint"], "url": "/wiki/claim-based-airdrops/"}, {"id": "claim-based-airdrops#takeover", "slug": "claim-based-airdrops", "title": "Claim-based airdrops", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: claims like MimbleWimbleCoin's asked holders to sign with their Bitcoin keys — the opposite of the 2019 fork reviewer's rule of never importing a private key. [mwc-claiming] [bth-review]", "aliases": "claim airdrop claims", "refs": ["bth-review", "mwc-claiming"], "url": "/wiki/claim-based-airdrops/"}, {"id": "claim-based-airdrops#507", "slug": "claim-based-airdrops", "title": "Claim-based airdrops", "section": "How they differ from forks", "text": "A claim-based airdrop starts a new ledger and lets holders of an existing coin prove their balance to receive tokens; no Bitcoin history is copied. The 2019 fork list keeps such coins apart in its “Honorable mentions” section [bth-review]. There it says Bitcoin holders “could have claimed free lumens until August 27th, 2017” for Stellar, and quotes BTCH: “It is technically NOT A FORK, but a merged airdrop.” [bth-review]", "aliases": "claim airdrop claims", "refs": ["bth-review"], "url": "/wiki/claim-based-airdrops/"}, {"id": "claim-based-airdrops#508", "slug": "claim-based-airdrops", "title": "Claim-based airdrops", "section": "Examples", "text": "CLAMs, announced in May 2014, said “Every person who had Bitcoin at block 300,377, Litecoin at block 565,693, or Dogecoin at block 218,556 was given ~4.6 CLAM” [clam-ann]. Byteball's 2016 plan paid bytes to Bitcoin holders “who link their bitcoin and byteball addresses before the launch” [byteball-2016]. The fork list says the Byteball distribution was “cut short suddenly and without any prior announcement” [bth-review]. MimbleWimbleCoin required “the ability to sign a message from the BTC address that you registered” [mwc-claiming]. The SEC's complaint says HEX tokens were deposited into wallets that Richard Heart, the defendant, “identified as significant holders of Bitcoin” [sec-heart-complaint].", "aliases": "claim airdrop claims", "refs": ["bth-review", "byteball-2016", "clam-ann", "mwc-claiming", "sec-heart-complaint"], "url": "/wiki/claim-based-airdrops/"}, {"id": "claim-based-airdrops#509", "slug": "claim-based-airdrops", "title": "Claim-based airdrops", "section": "Key safety", "text": "The fork reviewer explained that “Since I never import any private key” even a malicious client could not leak his keys [bth-review]. The MimbleWimbleCoin guide, by contrast, required a signature from the registered BTC address [mwc-claiming].", "aliases": "claim airdrop claims", "refs": ["bth-review", "mwc-claiming"], "url": "/wiki/claim-based-airdrops/"}, {"id": "clams#infobox", "slug": "clams", "title": "CLAMs (CLAM)", "section": "Summary and infobox", "text": "A 2014 proof-of-stake coin that gave about 4.6 CLAM to every Bitcoin, Litecoin and Dogecoin address with a balance, to be “dug” with the old private keys. Announced: 24 May 2014 by SuperClam [clam-ann]; Airdrop: ~4.6 CLAM per address [clam-ann]; Snapshot blocks: BTC 300,377; LTC 565,693; DOGE 218,556 [clam-ann]; Snapshot date: 12 May 2014 (project site) [clam-site]; Consensus: Proof of stake [clam-site]; Claim: Import the old private keys (“dig”) [clam-ann]", "aliases": "clam clamcoin dig just-dice superclam", "refs": ["clam-ann", "clam-site"], "url": "/wiki/clams/"}, {"id": "clams#takeover", "slug": "clams", "title": "CLAMs (CLAM)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: CLAMs is the ancestor of the 2017 airdrop wave — three years before Bitcoin Cash, it handed coins to every Bitcoin address and asked owners to import old keys to get them. [clam-ann]", "aliases": "clam clamcoin dig just-dice superclam", "refs": ["clam-ann"], "url": "/wiki/clams/"}, {"id": "clams#512", "slug": "clams", "title": "CLAMs (CLAM)", "section": "Distribution", "text": "The announcement thread, opened by SuperClam on 24 May 2014, says: “Every person who had Bitcoin at block 300,377, Litecoin at block 565,693, or Dogecoin at block 218,556 was given ~4.6 CLAM” [clam-ann]. The project site dates the snapshot to 12 May 2014 and says each address with a balance above dust received “a little over 4.6 CLAMS” [clam-site].", "aliases": "clam clamcoin dig just-dice superclam", "refs": ["clam-ann", "clam-site"], "url": "/wiki/clams/"}, {"id": "clams#513", "slug": "clams", "title": "CLAMs (CLAM)", "section": "Claiming and staking", "text": "The thread says “CLAIMING FREE CLAMs IS EASY!” and tells users to import their wallet into the CLAM client [clam-ann]. The site describes ongoing distribution “Through Proof-of-Stake(POS)” and suggests typing /dig in the Just-Dice chat to check for coins [clam-site]. The thread title gives the coin's consensus names as “Proof-Of-Chain, Proof-Of-Working-Stake” [clam-ann].", "aliases": "clam clamcoin dig just-dice superclam", "refs": ["clam-ann", "clam-site"], "url": "/wiki/clams/"}, {"id": "classicbitcoin#infobox", "slug": "classicbitcoin", "title": "ClassicBitcoin (CBTC)", "section": "Summary and infobox", "text": "An Equihash fork at block 516,095 on 1 April 2018, tied to a BitClassic marketplace; still working in 2019 and releasing a v2 with liquidity mining later. Fork height: 516,095 [bth-review]; Block 516,095 time: 2018-04-01 07:01:43 UTC [btc-516095]; Ratio: 1 BTC = 10000 CBTC [bth-review]; Proof of work: Equihash [cbtc-ann]; Status (Feb 2019 list): “seems to be working, 0.5 GB” [bth-review]; Later: CBTC v2 with “Liquidity Mining” [cbtc-readme]", "aliases": "cbtc classicbitcoin bitclassic", "refs": ["btc-516095", "bth-review", "cbtc-ann", "cbtc-readme"], "url": "/wiki/classicbitcoin/"}, {"id": "classicbitcoin#takeover", "slug": "classicbitcoin", "title": "ClassicBitcoin (CBTC)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: ClassicBitcoin asked to be added to the 2019 fork list itself, in a reply by its own account. [bth-review]", "aliases": "cbtc classicbitcoin bitclassic", "refs": ["bth-review"], "url": "/wiki/classicbitcoin/"}, {"id": "classicbitcoin#516", "slug": "classicbitcoin", "title": "ClassicBitcoin (CBTC)", "section": "Launch", "text": "In an April 2018 reply to the fork list, the account bitclassic wrote: “ClassicBitcoin (CBTC) forked on 1st april 2018 at block 516095” [bth-review]. Block 516,095 was mined on 1 April 2018 [btc-516095]. The list records “ClassicBitcoin (CBTC) (1 BTC = 10000 CBTC)” and, on 26 February 2019, that it “seems to be working, 0.5 GB” [bth-review].", "aliases": "cbtc classicbitcoin bitclassic", "refs": ["btc-516095", "bth-review"], "url": "/wiki/classicbitcoin/"}, {"id": "classicbitcoin#517", "slug": "classicbitcoin", "title": "ClassicBitcoin (CBTC)", "section": "Design", "text": "The announcement thread, opened on 10 March 2018, calls it “Cryptocurrency for the BitClassic MarketPlace” and describes an “ASIC resistant PoW algorithm, Equihash” [cbtc-ann]. Its current OP was last edited in November 2021 [cbtc-ann]. The GitHub README advertises CBTC v2, with “Liquidity Mining starts on Block 170000 to 190000” and “Removal of the Community Fee structure” [cbtc-readme]. Its build steps use a zcutil build script [cbtc-readme].", "aliases": "cbtc classicbitcoin bitclassic", "refs": ["cbtc-ann", "cbtc-readme"], "url": "/wiki/classicbitcoin/"}, {"id": "coingeek#infobox", "slug": "coingeek", "title": "CoinGeek", "section": "Summary and infobox", "text": "BSV-focused news site and events brand founded by Calvin Ayre. Founder: Calvin Ayre per CoinGeek's About page; Wikipedia says he acquired it in August 2017 [coingeek-about] [wp-ayre]; Focus: BSV blockchain [coingeek-about]; Authors include: Kurt Wuckert Jr. [coingeek-about]", "aliases": "coingeek", "refs": ["coingeek-about", "wp-ayre"], "url": "/wiki/coingeek/"}, {"id": "coingeek#takeover", "slug": "coingeek", "title": "CoinGeek", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: CoinGeek is the media arm of the BSV side of the 2018 split, and several voices the show has interviewed about that split wrote for it. [coingeek-about] [ep-s17e39-coingeek]", "aliases": "coingeek", "refs": ["coingeek-about", "ep-s17e39-coingeek"], "url": "/wiki/coingeek/"}, {"id": "coingeek#520", "slug": "coingeek", "title": "CoinGeek", "section": "About", "text": "CoinGeek's About page says it was “Founded by visionary billionaire Calvin Ayre” and describes its focus on the BSV blockchain [coingeek-about]. Its team page lists Kurt Wuckert Jr. among its authors [coingeek-about]. See Calvin Ayre [wp-ayre].", "aliases": "coingeek", "refs": ["coingeek-about", "wp-ayre"], "url": "/wiki/coingeek/"}, {"id": "coingeek#521", "slug": "coingeek", "title": "CoinGeek", "section": "On the show", "text": "Vlad introduced Kurt Wuckert Jr. on S17 E39 as “a journalist for CoinGeek” [ep-s17e39-coingeek]. Kurt called Calvin Ayre BSV's most significant player [ep-s17e39-ayre]. The Takeover BSV feature covers the Bitcoin SV fork that CoinGeek supported [btk-bsv].", "aliases": "coingeek", "refs": ["btk-bsv", "ep-s17e39-ayre", "ep-s17e39-coingeek"], "url": "/wiki/coingeek/"}, {"id": "craig-wright#infobox", "slug": "craig-wright", "title": "Craig Wright", "section": "Summary and infobox", "text": "Australian computer scientist who claimed to be Satoshi Nakamoto; the UK High Court ruled in 2024 that he is not, and found he forged documents. Born: October 1970, Australia [wp-wright]; Claim: To be Satoshi Nakamoto [copa-judgment]; Court: COPA v Wright, [2024] EWHC 1198 (Ch), Mellor J [copa-judgment]; Declarations (14 Mar 2024): Not the author of the White Paper; not the person operating as Satoshi 2008–2011; not the creator of the Bitcoin system; not the author of the initial versions of the Bitcoin software [copa-judgment]; Written judgment: 20 May 2024 [copa-judgment]; Contempt: December 2024: twelve-month sentence, suspended [btk-bsv]; Associated chain: Bitcoin SV [wp-bsv]", "aliases": "csw faketoshi copa nchain", "refs": ["btk-bsv", "copa-judgment", "wp-bsv", "wp-wright"], "url": "/wiki/craig-wright/"}, {"id": "craig-wright#takeover", "slug": "craig-wright", "title": "Craig Wright", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: strictly what the courts found. Wright matters to fork history because Bitcoin SV formed around him, and several guests on the show, including Jonathan Bier, argue he damaged the big-block cause. [wp-bsv] [ep-s16e60-wright]", "aliases": "csw faketoshi copa nchain", "refs": ["ep-s16e60-wright", "wp-bsv"], "url": "/wiki/craig-wright/"}, {"id": "craig-wright#524", "slug": "craig-wright", "title": "Craig Wright", "section": "The claim", "text": "Wright claims to be Satoshi Nakamoto: the person who wrote and published the first version of the Bitcoin White Paper on 31 October 2008, released the first Bitcoin source code and created the Bitcoin system [copa-judgment]. In December 2015 Wired and Gizmodo suggested he might be the inventor of Bitcoin, and a 2 May 2016 blog post associated him with Satoshi using a signature that critics said had been reused from a 2009 transaction [wp-wright].", "aliases": "csw faketoshi copa nchain", "refs": ["copa-judgment", "wp-wright"], "url": "/wiki/craig-wright/"}, {"id": "craig-wright#525", "slug": "craig-wright", "title": "Craig Wright", "section": "COPA v Wright", "text": "The Crypto Open Patent Alliance sued in the High Court in London, with hearings in February and March 2024 [wp-wright]. At the end of the trial Mr Justice Mellor declared that Wright is not the author of the Bitcoin White Paper, not the person who adopted or operated under the pseudonym Satoshi Nakamoto between 2008 and 2011, and not the person who created the Bitcoin system [copa-judgment]. The judgment's fourth declaration is that he is not the author of the initial versions of the Bitcoin software [copa-judgment].", "aliases": "csw faketoshi copa nchain", "refs": ["copa-judgment", "wp-wright"], "url": "/wiki/craig-wright/"}, {"id": "craig-wright#526", "slug": "craig-wright", "title": "Craig Wright", "section": "Findings on evidence", "text": "In the written judgment of 20 May 2024, the judge said he was “entirely satisfied that Dr Wright lied to the Court extensively and repeatedly”, mostly about “documents he had forged” to support the claim [copa-judgment]. In July 2024 a High Court judge referred Wright to UK prosecutors over alleged perjury [wp-wright]. In December 2024 he was found in contempt over a fresh £911 billion claim and received a twelve-month suspended sentence [btk-bsv].", "aliases": "csw faketoshi copa nchain", "refs": ["btk-bsv", "copa-judgment", "wp-wright"], "url": "/wiki/craig-wright/"}, {"id": "craig-wright#527", "slug": "craig-wright", "title": "Craig Wright", "section": "Other litigation", "text": "In December 2021 the Kleiman v Wright verdict cleared him of most claims but ordered him to pay $100 million to W&K Info Defense Research [btk-bsv].", "aliases": "csw faketoshi copa nchain", "refs": ["btk-bsv"], "url": "/wiki/craig-wright/"}, {"id": "craig-wright#528", "slug": "craig-wright", "title": "Craig Wright", "section": "Bitcoin SV", "text": "Bitcoin SV was created in November 2018 by a group led by Wright [wp-bsv]. On S16 E60 Jonathan Bier said Wright “inadvertently had a huge positive impact for the small blockers” [ep-s16e60-wright].", "aliases": "csw faketoshi copa nchain", "refs": ["ep-s16e60-wright", "wp-bsv"], "url": "/wiki/craig-wright/"}, {"id": "craig-wright#529", "slug": "craig-wright", "title": "Craig Wright", "section": "Heard on Bitcoin Takeover", "text": "On S17 E10 (March 2026), Mark Karpelès said of the Mt. Gox coins that Wright “he claims to have bought those Bitcoins in 2012.” [ep-s17e10-q6986] An earlier episode was devoted to him: S5 E10, ‘Arthur van Pelt on Craig Wright’ (July 2020) [btk-ep-s5e10].", "aliases": "csw faketoshi copa nchain", "refs": ["btk-ep-s5e10", "ep-s17e10-q6986"], "url": "/wiki/craig-wright/"}, {"id": "ctor#infobox", "slug": "ctor", "title": "CTOR (canonical transaction ordering)", "section": "Summary and infobox", "text": "Bitcoin Cash's November 2018 rule that transactions in a block, after the coinbase, be sorted by txid — one of the two changes behind the BCH/BSV split. Activated: BCH upgrade, MTP ≥ 1542300000 (15 Nov 2018) [bch-nov2018]; Rule: Non-coinbase transactions in ascending txid order [bch-nov2018]; Shipped with: OP_CHECKDATASIG, 100-byte minimum, push-only, clean stack [bch-nov2018]; Opposed by: nChain / Bitcoin SV [btk-bsv]", "aliases": "ctor canonical transaction ordering ttor", "refs": ["bch-nov2018", "btk-bsv"], "url": "/wiki/ctor/"}, {"id": "ctor#takeover", "slug": "ctor", "title": "CTOR (canonical transaction ordering)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: a block-ordering rule that most users would never see split Bitcoin Cash in two, because one side saw it as scaling and the other as an unauthorised redesign. [btk-bsv] [ep-s17e19-cds]", "aliases": "ctor canonical transaction ordering ttor", "refs": ["btk-bsv", "ep-s17e19-cds"], "url": "/wiki/ctor/"}, {"id": "ctor#532", "slug": "ctor", "title": "CTOR (canonical transaction ordering)", "section": "Rule", "text": "The Bitcoin Cash specification for the 15 November 2018 upgrade activates when the median time past of the last 11 blocks reaches UNIX time 1542300000 [bch-nov2018]. It says that, “With the exception of the coinbase transaction, transactions within a block MUST be sorted in numerically ascending order of the transaction id” [bch-nov2018]. The same upgrade enabled OP_CHECKDATASIG, a 100-byte minimum transaction size, and push-only and clean-stack rules [bch-nov2018].", "aliases": "ctor canonical transaction ordering ttor", "refs": ["bch-nov2018"], "url": "/wiki/ctor/"}, {"id": "ctor#533", "slug": "ctor", "title": "CTOR (canonical transaction ordering)", "section": "Dispute", "text": "The Takeover BSV feature says CTOR and OP_CHECKDATASIG were “two changes that nobody outside the ABC team had asked for”; ABC said CTOR would enable faster block propagation, while nChain called it an unauthorised redesign and announced Bitcoin SV to reject both [btk-bsv]. On the show Amaury Séchet called CTOR “like a scalability technology” [ep-s17e19-cds]. The split that followed is covered in the hash war [btk-bsv].", "aliases": "ctor canonical transaction ordering ttor", "refs": ["btk-bsv", "ep-s17e19-cds"], "url": "/wiki/ctor/"}, {"id": "ctv-covenant-debates#infobox", "slug": "ctv-covenant-debates", "title": "CTV and the covenant activation debates", "section": "Summary and infobox", "text": "The long fight over OP_CHECKTEMPLATEVERIFY (BIP-119): Jeremy Rubin's 2022 Speedy Trial plan, a 2025 open letter, and a 2026 activation meeting. BIP: 119, CHECKTEMPLATEVERIFY [bip119]; Author: Jeremy Rubin [bip119]; Mechanism: Redefines OP_NOP4 [bip119]; 2022 plan: Speedy Trial, signalling from 5 May 2022 [rubin-2022]; 2025: Open letter, 66 signers [optech-2025-07]; 2026: Activation meeting favours BIP9, long periods [optech-2026-01]", "aliases": "ctv bip119 bip-119 checktemplateverify covenants rubin op_secure_the_bag", "refs": ["bip119", "optech-2025-07", "optech-2026-01", "rubin-2022"], "url": "/wiki/ctv-covenant-debates/"}, {"id": "ctv-covenant-debates#takeover", "slug": "ctv-covenant-debates", "title": "CTV and the covenant activation debates", "section": "Takeover view (editorial opinion)", "text": "On S17 E38 Vlad recalled that “Jeremy Rubin tried to do a Speedy Trial for CTV”, and Keagan McClelland explained the opcode's old name, OP_SECURE_THE_BAG. [ep-s17e38-ctv] [ep-s17e38-stb]", "aliases": "ctv bip119 bip-119 checktemplateverify covenants rubin op_secure_the_bag", "refs": ["ep-s17e38-ctv", "ep-s17e38-stb"], "url": "/wiki/ctv-covenant-debates/"}, {"id": "ctv-covenant-debates#536", "slug": "ctv-covenant-debates", "title": "CTV and the covenant activation debates", "section": "The opcode", "text": "BIP-119, by Jeremy Rubin, proposes “a new opcode, OP_CHECKTEMPLATEVERIFY, to be activated as a change to the semantics of OP_NOP4” [bip119]. Bitcoin Optech says CTV lets an output specify how its funds may be spent, “a design known in Bitcoin as a covenant” [optech-ctv]. On S17 E38 Keagan McClelland said it “used to be called OP_SECURE_THE_BAG” [ep-s17e38-stb].", "aliases": "ctv bip119 bip-119 checktemplateverify covenants rubin op_secure_the_bag", "refs": ["bip119", "ep-s17e38-stb", "optech-ctv"], "url": "/wiki/ctv-covenant-debates/"}, {"id": "ctv-covenant-debates#537", "slug": "ctv-covenant-debates", "title": "CTV and the covenant activation debates", "section": "2022: Speedy Trial", "text": "On 17 April 2022 Rubin proposed a “Speedy Trial release similar to Taproots”, with signalling from May 5th, 2022, a timeout of August 12th, 2022 and activation height 762048 [rubin-2022]. Optech summarised a 90% signalling threshold and objections: Anthony Towns noted that nearly all signet transactions seemed built with the same software, and Matt Corallo questioned whether CTV was the best covenant design [optech-197]. Vlad recalled the attempt on S17 E38 [ep-s17e38-ctv]. See Speedy Trial.", "aliases": "ctv bip119 bip-119 checktemplateverify covenants rubin op_secure_the_bag", "refs": ["ep-s17e38-ctv", "optech-197", "rubin-2022"], "url": "/wiki/ctv-covenant-debates/"}, {"id": "ctv-covenant-debates#538", "slug": "ctv-covenant-debates", "title": "CTV and the covenant activation debates", "section": "2025–2026", "text": "In July 2025 Optech reported an open letter posted by James O'Beirne, signed by 66 individuals, asking Core contributors to prioritise review of CTV and CSFS “within the next six months” [optech-2025-07]. In January 2026 Optech reported a CTV activation meeting whose attendees agreed on “conservative parameters” and BIP9 [optech-2026-01]. The BIP's status is still Draft in the repository fetched for this wiki [bip119].", "aliases": "ctv bip119 bip-119 checktemplateverify covenants rubin op_secure_the_bag", "refs": ["bip119", "optech-2025-07", "optech-2026-01"], "url": "/wiki/ctv-covenant-debates/"}, {"id": "ctv-covenant-debates#539", "slug": "ctv-covenant-debates", "title": "CTV and the covenant activation debates", "section": "Heard on Bitcoin Takeover", "text": "On S16 E23 (May 2025), James O'Beirne said: “CTV, CheckSigFromStack, those things are pretty well understood by everybody not to have any kind of MEV risk.” [ep-s16e23-q334]", "aliases": "ctv bip119 bip-119 checktemplateverify covenants rubin op_secure_the_bag", "refs": ["ep-s16e23-q334"], "url": "/wiki/ctv-covenant-debates/"}, {"id": "cve-2018-17144#infobox", "slug": "cve-2018-17144", "title": "CVE-2018-17144 (duplicate-input inflation bug)", "section": "Summary and infobox", "text": "A 2018 Bitcoin Core bug that could crash nodes and, in 0.15.x–0.16.2, let a miner inflate supply by spending one input twice in a block; patched in 0.16.3 before any known exploit. Reported: 17 Sep 2018, 14:57 UTC [core-cve-17144]; Fixed in: Bitcoin Core 0.16.3 and 0.17.0rc4 [core-cve-17144]; Type: Denial of service and “critical inflation vulnerability” [core-cve-17144]; Root cause: Optimisation in PR #9049 (0.14) [core-cve-17144]; Exploited?: “We are unaware of any attempts to exploit” [core-cve-17144]", "aliases": "cve-2018-17144 17144 duplicate inputs inflation bug 0.16.3", "refs": ["core-cve-17144"], "url": "/wiki/cve-2018-17144/"}, {"id": "cve-2018-17144#takeover", "slug": "cve-2018-17144", "title": "CVE-2018-17144 (duplicate-input inflation bug)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: the closest Bitcoin came to an accidental inflation fork after 2010 was found by someone outside Core and reported to Bitcoin Cash developers too, a reminder that the forked projects still shared one codebase's bugs. [btk-allforks] [core-cve-17144]", "aliases": "cve-2018-17144 17144 duplicate inputs inflation bug 0.16.3", "refs": ["btk-allforks", "core-cve-17144"], "url": "/wiki/cve-2018-17144/"}, {"id": "cve-2018-17144#542", "slug": "cve-2018-17144", "title": "CVE-2018-17144 (duplicate-input inflation bug)", "section": "Disclosure", "text": "The Bitcoin Core disclosure says the issue, fixed in Bitcoin Core 0.16.3 and 0.17.0rc4, “includes both a Denial of Service component and a critical inflation vulnerability” [core-cve-17144]. Its timeline says that on 17 September 2018 at 14:57 UTC an “anonymous reporter reports crash bug” to Pieter Wuille, Greg Maxwell and Wladimir van der Laan of Bitcoin Core, deadalnix of Bitcoin ABC and sickpig of Bitcoin Unlimited [core-cve-17144]. At 17:47 UTC Matt Corallo identified the inflation bug [core-cve-17144]. Bitcoin Takeover's forks overview says the bug was disclosed “by a Bitcoin Cash developer”, while the Core notice calls the reporter anonymous [btk-allforks].", "aliases": "cve-2018-17144 17144 duplicate inputs inflation bug 0.16.3", "refs": ["btk-allforks", "core-cve-17144"], "url": "/wiki/cve-2018-17144/"}, {"id": "cve-2018-17144#543", "slug": "cve-2018-17144", "title": "CVE-2018-17144 (duplicate-input inflation bug)", "section": "Cause", "text": "The notice says that in Bitcoin Core 0.14 an optimisation (PR #9049) skipped a costly check that multiple inputs within a single transaction did not spend the same input twice, leaving only an assertion; later changes meant that in 0.15.x to 0.16.2 the case could be exploited for inflation rather than a crash [core-cve-17144]. The Bitcoin Wiki lists the bug as “Missing check for duplicate inputs” [bw-cve-list].", "aliases": "cve-2018-17144 17144 duplicate inputs inflation bug 0.16.3", "refs": ["bw-cve-list", "core-cve-17144"], "url": "/wiki/cve-2018-17144/"}, {"id": "cve-2018-17144#544", "slug": "cve-2018-17144", "title": "CVE-2018-17144 (duplicate-input inflation bug)", "section": "Outcome", "text": "The notice says “We are unaware of any attempts to exploit this vulnerability” [core-cve-17144]. The Takeover overview notes that no block ever exploited it, so no split occurred, but that the affected versions had loosened a rule unnoticed [btk-allforks].", "aliases": "cve-2018-17144 17144 duplicate inputs inflation bug 0.16.3", "refs": ["btk-allforks", "core-cve-17144"], "url": "/wiki/cve-2018-17144/"}, {"id": "dalilcoin#infobox", "slug": "dalilcoin", "title": "Dalilcoin (DLC)", "section": "Summary and infobox", "text": "A fork of the Qeditas formal-mathematics project, carrying its Bitcoin block-350,000 airdrop, and anchoring its blocks into Litecoin by proof of burn. Based on: Qeditas [dlc-readme]; Airdrop snapshot: Bitcoin block 350,000 (from Qeditas) [fd-data]; Block 350,000 time: 2015-03-30 22:17:14 UTC [btc-350000]; Consensus: Proof of burn anchored in Litecoin [dlc-readme]", "aliases": "dlc dalilcoin qeditas proof of burn", "refs": ["btc-350000", "dlc-readme", "fd-data"], "url": "/wiki/dalilcoin/"}, {"id": "dalilcoin#takeover", "slug": "dalilcoin", "title": "Dalilcoin (DLC)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Dalilcoin did not take its own snapshot; forkdrop lists it at the 2015 Qeditas height. [fd-data]", "aliases": "dlc dalilcoin qeditas proof of burn", "refs": ["fd-data"], "url": "/wiki/dalilcoin/"}, {"id": "dalilcoin#547", "slug": "dalilcoin", "title": "Dalilcoin (DLC)", "section": "Design", "text": "The README calls Dalilcoin “A Formal Library as a Bitcoin Spin-Off” and says it “is a fork of Qeditas (qeditas.org) which was designed to use a blockchain to support a revival of the QED Project” [dlc-readme]. It says Dalilcoin “changes the consensus protocol of Qeditas by using Proof of Burn to anchor Dalilcoin blocks into a Proof of Work blockchain (Litecoin's)” [dlc-readme].", "aliases": "dlc dalilcoin qeditas proof of burn", "refs": ["dlc-readme"], "url": "/wiki/dalilcoin/"}, {"id": "dalilcoin#548", "slug": "dalilcoin", "title": "Dalilcoin (DLC)", "section": "Airdrop", "text": "The README says claims can be made with Bitcoin signed messages, without importing a Bitcoin private key [dlc-readme]. forkdrop's data file lists a registration airdrop at block 350000 on 2015-03-30, the Qeditas snapshot height [fd-data]. Block 350,000 was mined on 30 March 2015 [btc-350000].", "aliases": "dlc dalilcoin qeditas proof of burn", "refs": ["btc-350000", "dlc-readme", "fd-data"], "url": "/wiki/dalilcoin/"}, {"id": "dash#infobox", "slug": "dash", "title": "Dash", "section": "Summary and infobox", "text": "Evan Duffield's 2014 code fork of Bitcoin, launched as XCoin, renamed Darkcoin, then Dash; masternodes, X11 and an on-chain treasury. Ticker: DASH (earlier XCO, DRK) [dash-ann]; Type: Code fork of Bitcoin [dash-wp]; Creator: Evan Duffield [dash-ann]; Launch: 18 January 2014, as XCoin [dash-ann]; Renamed: Darkcoin (2014); Dash (March 2015) [dash-wp]; Proof of work: X11 [dash-ann]; Second layer: Masternodes: InstantSend, PrivateSend, governance [dash-ann]; Block time: 2.5 minutes [dash-wp]", "aliases": "darkcoin xcoin x11 masternodes", "refs": ["dash-ann", "dash-wp"], "url": "/wiki/dash/"}, {"id": "dash#takeover", "slug": "dash", "title": "Dash", "section": "Takeover view (editorial opinion)", "text": "Vlad admitted on air that Dash was always “sort of a mystery” to him, then gave Joël Valenzuela nearly five hours to explain why it became his everyday money. [ep-s17e33-dash] [btk-feed]", "aliases": "darkcoin xcoin x11 masternodes", "refs": ["btk-feed", "ep-s17e33-dash"], "url": "/wiki/dash/"}, {"id": "dash#551", "slug": "dash", "title": "Dash", "section": "Launch and names", "text": "Evan Duffield opened the Bitcointalk announcement thread on 18 January 2014 for a coin then called XCoin; the thread's surviving titles show its later names, Darkcoin (DRK) and Dash [dash-ann]. Wikipedia, citing Fortune, dates the rebrand to Dash, a portmanteau of \"digital cash\", to March 2015 [dash-wp].", "aliases": "darkcoin xcoin x11 masternodes", "refs": ["dash-ann", "dash-wp"], "url": "/wiki/dash/"}, {"id": "dash#552", "slug": "dash", "title": "Dash", "section": "Design", "text": "Dash uses the X11 hashing algorithm and adds a second-layer network of masternodes that provide InstantSend, PrivateSend and a governance and budgeting system that funds work from the block reward [dash-ann]. The announcement describes a launch with no premine [dash-ann], while Wikipedia records criticism that an early distribution mishap concentrated coins among early adopters [dash-wp].", "aliases": "darkcoin xcoin x11 masternodes", "refs": ["dash-ann", "dash-wp"], "url": "/wiki/dash/"}, {"id": "dash#553", "slug": "dash", "title": "Dash", "section": "On the podcast", "text": "Joël Valenzuela told Bitcoin Takeover S17 E33 how Dash became his primary money a year before the Bitcoin Cash split [ep-s17e33-dash].", "aliases": "darkcoin xcoin x11 masternodes", "refs": ["ep-s17e33-dash"], "url": "/wiki/dash/"}, {"id": "digibyte#infobox", "slug": "digibyte", "title": "DigiByte (DGB)", "section": "Summary and infobox", "text": "A multi-algorithm UTXO chain launched in January 2014 with 15-second blocks, five mining algorithms and a 21 billion coin cap. Genesis motto: “USA Today: 10/Jan/2014, Target: Data stolen from up to 110M customers” [dgb-readme]; Algorithms: SHA256, Scrypt, Odocrypt, Skein, Qubit [dgb-readme]; Block interval: 15 seconds [dgb-readme]; Max supply: 21 billion over 21 years (2035) [dgb-readme]; DigiShield hard fork: Block 67,200, 28 Feb 2014 [dgb-readme]; SegWit: Activated April 2017 (project claim: first major altcoin) [dgb-readme]", "aliases": "dgb digishield multi-algo", "refs": ["dgb-readme"], "url": "/wiki/digibyte/"}, {"id": "digibyte#takeover", "slug": "digibyte", "title": "DigiByte (DGB)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: DigiByte answered Bitcoin's one-algorithm mining with five, and was early with SegWit in 2017 while Bitcoin itself was still stuck in the activation fight. [dgb-readme] [btk-forkwars]", "aliases": "dgb digishield multi-algo", "refs": ["btk-forkwars", "dgb-readme"], "url": "/wiki/digibyte/"}, {"id": "digibyte#556", "slug": "digibyte", "title": "DigiByte (DGB)", "section": "Launch", "text": "The DigiByte Core README says DigiByte was “founded in early 2014” and lists its genesis block text as “USA Today: 10/Jan/2014, Target: Data stolen from up to 110M customers” [dgb-readme]. The README describes the chain as public, UTXO based and multi-algorithm, and compares it with Bitcoin point by point; this wiki has not yet sourced which codebase the project started from [dgb-readme].", "aliases": "dgb digishield multi-algo", "refs": ["dgb-readme"], "url": "/wiki/digibyte/"}, {"id": "digibyte#557", "slug": "digibyte", "title": "DigiByte (DGB)", "section": "Design", "text": "Per the README, DigiByte mines on five algorithms — SHA256, Scrypt, Odocrypt, Skein and Qubit — each taking about 20% of blocks, with 15-second blocks and a cap of 21 billion DigiBytes reached in 2035 [dgb-readme]. It lists five hard forks: DigiShield at block 67,200 on 28 February 2014, MultiAlgo, MultiShield, DigiSpeed and, in July 2019, Odocrypt [dgb-readme].", "aliases": "dgb digishield multi-algo", "refs": ["dgb-readme"], "url": "/wiki/digibyte/"}, {"id": "digibyte#558", "slug": "digibyte", "title": "DigiByte (DGB)", "section": "SegWit", "text": "The README claims DigiByte was the “First major altcoin to successfully activate Segwit” in April 2017, months before SegWit activated on Bitcoin [dgb-readme].", "aliases": "dgb digishield multi-algo", "refs": ["dgb-readme"], "url": "/wiki/digibyte/"}, {"id": "dogecoin#infobox", "slug": "dogecoin", "title": "Dogecoin", "section": "Summary and infobox", "text": "The 2013 joke coin by Billy Markus and Jackson Palmer, a Scrypt code fork in the Litecoin line, merge-mined via AuxPoW. Ticker: DOGE [doge-ann]; Type: Code fork of Lucky Coin and Litecoin [doge-devs]; Creators: Billy Markus, Jackson Palmer [doge-history]; Launch: 6 December 2013 [doge-history]; Proof of work: Scrypt with AuxPoW [doge-ann]; Block time: 60 seconds [doge-ann]; Difficulty retarget: DigiShield [doge-ann]; Reward from block 600,000: 10,000 DOGE per block [doge-ann]", "aliases": "doge scrypt auxpow", "refs": ["doge-ann", "doge-devs", "doge-history"], "url": "/wiki/dogecoin/"}, {"id": "dogecoin#takeover", "slug": "dogecoin", "title": "Dogecoin", "section": "Takeover view (editorial opinion)", "text": "No Bitcoin Takeover episode is dedicated to Dogecoin yet. That gap is marked here rather than filled with guesses — a candidate guest for a future episode. [doge-history]", "aliases": "doge scrypt auxpow", "refs": ["doge-history"], "url": "/wiki/dogecoin/"}, {"id": "dogecoin#561", "slug": "dogecoin", "title": "Dogecoin", "section": "Origins", "text": "Dogecoin was created as a joke in late 2013 by Billy Markus and Jackson Palmer and launched on 6 December 2013, based on the Doge meme [doge-history]. Palmer created the Dogecoin.com website; Markus worked as the solo developer on the first four releases [doge-history].", "aliases": "doge scrypt auxpow", "refs": ["doge-history"], "url": "/wiki/dogecoin/"}, {"id": "dogecoin#562", "slug": "dogecoin", "title": "Dogecoin", "section": "Design", "text": "The Bitcointalk announcement thread, in its archived and later-edited form, lists Scrypt with AuxPoW (merged mining), a 60-second block time, DigiShield difficulty retargeting, no premine, and a block reward that stepped down until a fixed 10,000 DOGE per block from block 600,000 [doge-ann]. Dogecoin Core started as a fork of Lucky Coin and Litecoin, themselves forks of Bitcoin Core [doge-devs].", "aliases": "doge scrypt auxpow", "refs": ["doge-ann", "doge-devs"], "url": "/wiki/dogecoin/"}, {"id": "dogecoin#563", "slug": "dogecoin", "title": "Dogecoin", "section": "Community", "text": "Both founders left development in 2014, and a Dogecoin Core development team took over [doge-history]. In 2014 the community raised 26.5 million DOGE to send the Jamaican bobsled team to the Sochi Winter Olympics [doge-history].", "aliases": "doge scrypt auxpow", "refs": ["doge-history"], "url": "/wiki/dogecoin/"}, {"id": "drivechains#infobox", "slug": "drivechains", "title": "Drivechains (BIP-300/301)", "section": "Summary and infobox", "text": "Sidechains whose two-way peg is secured by miners (BIP-300) with blind merged mining (BIP-301). BIP-300: Hashrate Escrows [bip300]; BIP-301: Blind Merged Mining [bip301]; Author: Paul Sztorc [bip300]; Status on Bitcoin: Not activated [btk-ecx]; Live on: eCash (ECX), from 29 October 2026 [btk-ecx]", "aliases": "bip300 bip301", "refs": ["bip300", "bip301", "btk-ecx"], "url": "/wiki/drivechains/"}, {"id": "drivechains#takeover", "slug": "drivechains", "title": "Drivechains (BIP-300/301)", "section": "Takeover view (editorial opinion)", "text": "Vlad on S17 E37: the difference from other L2s is that all transaction fees go to miners. Peter Todd's 2023 analysis is the standard critique and is linked here too. [ep-s17e37-outro] [ptodd-drivechains]", "aliases": "bip300 bip301", "refs": ["ep-s17e37-outro", "ptodd-drivechains"], "url": "/wiki/drivechains/"}, {"id": "drivechains#566", "slug": "drivechains", "title": "Drivechains (BIP-300/301)", "section": "Definition", "text": "Drivechains are a design for Bitcoin sidechains specified in two proposals: BIP-300, hashrate escrows for the peg, and BIP-301, blind merged mining [bip300] [bip301]. Project documentation is at drivechain.info [drivechain-info].", "aliases": "bip300 bip301", "refs": ["bip300", "bip301", "drivechain-info"], "url": "/wiki/drivechains/"}, {"id": "drivechains#567", "slug": "drivechains", "title": "Drivechains (BIP-300/301)", "section": "Status", "text": "Neither BIP has activated on Bitcoin. Paul Sztorc's eCash (ECX) fork was built to activate them natively [btk-ecx]. Peter Todd published a detailed critical analysis in 2023 [ptodd-drivechains].", "aliases": "bip300 bip301", "refs": ["btk-ecx", "ptodd-drivechains"], "url": "/wiki/drivechains/"}, {"id": "drivechains#568", "slug": "drivechains", "title": "Drivechains (BIP-300/301)", "section": "Heard on Bitcoin Takeover", "text": "On S17 E21 (April 2026), Paul Sztorc said of his eCash fork: “even when we activate the drivechains, I'm going to use the same Core Untouched Soft Fork, so that won't even be in the changes for the L1.” [ep-s17e21-q190] Earlier drivechain episodes with Sztorc, listed in the show's feed: S9 E4, ‘Paul Sztorc on the Philosophy of BIP 300 & Prediction Markets’ (July 2021) [btk-ep-s9e4]; S14 E10, ‘Paul Sztorc on Drivechains & Attacking Bitcoin’ (August 2023) [btk-ep-s14e10]; S14 E13, ‘Paul Sztorc Reacts to Drivechains Reactions’ (September 2023) [btk-ep-s14e13]; S15 E16, ‘Paul Sztorc Talks Bitcoin Scaling, But Can't Say Drivechains’ (January 2024) [btk-ep-s15e16]; S15 E68, ‘Paul Sztorc on Activating Drivechains via CUSF (Core Untouched Soft Fork)’ (December 2024) [btk-ep-s15e68].", "aliases": "bip300 bip301", "refs": ["btk-ep-s14e10", "btk-ep-s14e13", "btk-ep-s15e16", "btk-ep-s15e68", "btk-ep-s9e4", "ep-s17e21-q190"], "url": "/wiki/drivechains/"}, {"id": "ecash-ecx#infobox", "slug": "ecash-ecx", "title": "eCash (ECX)", "section": "Summary and infobox", "text": "Paul Sztorc's 2026 hard fork of Bitcoin that activates drivechains (BIP-300/301) natively. Not XEC. Ticker: ECX (practice coins: pECX) [btk-ecx]; Type: UTXO hard fork of Bitcoin with BIP-300/301 [ecx-faq]; Announced: 24 April 2026; on Bitcoin Takeover S17 E21 [ep-s17e21-announce]; Alpha: Forked from block 963,647 on 23 Aug 2026 [btk-ecx]; Beta: 19 September 2026, block 967,680 [ecx-faq]; Mainnet: Forked at block 973,728 on 29 October 2026 [btk-ecx]; Distribution: 1:1 to Bitcoin addresses at the snapshot [btk-ecx]; Proof of work: SHA-256d, difficulty reset at the fork [btk-ecx]; Replay protection: Opt-in, one-directional (nLockTime 499999999) [btk-ecx]; Sidechains at mainnet: BitNames, BitAssets, Thunder, Truthcoin, zSide (Photon, CoinShift later) [ecx-ct]; Satoshi's coins: Part of the Patoshi-pattern coins reassigned on the ECX ledger only [btk-ecx]", "aliases": "ecx drivechain fork layertwo", "refs": ["btk-ecx", "ecx-ct", "ecx-faq", "ep-s17e21-announce"], "url": "/wiki/ecash-ecx/"}, {"id": "ecash-ecx#takeover", "slug": "ecash-ecx", "title": "eCash (ECX)", "section": "Takeover view (editorial opinion)", "text": "Vlad has supported drivechains since about 2018 and said on air that not backing the fork would make him a hypocrite. LayerTwo Labs is a show sponsor. Read this article with that disclosure in mind. [ep-s17e37-outro] [ep-s17e19-sponsors]", "aliases": "ecx drivechain fork layertwo", "refs": ["ep-s17e19-sponsors", "ep-s17e37-outro"], "url": "/wiki/ecash-ecx/"}, {"id": "ecash-ecx#571", "slug": "ecash-ecx", "title": "eCash (ECX)", "section": "Announcement", "text": "Paul Sztorc announced a hard fork of Bitcoin on Bitcoin Takeover S17 E21 in April 2026, saying he was not sure how far Bitcoin could go \"without a new competing coin\" [ep-s17e21-announce]. In the same episode he said he picked \"a completely different name\", eCash, unlike Bitcoin Cash [ep-s17e21-name].", "aliases": "ecx drivechain fork layertwo", "refs": ["ep-s17e21-announce", "ep-s17e21-name"], "url": "/wiki/ecash-ecx/"}, {"id": "ecash-ecx#572", "slug": "ecash-ecx", "title": "eCash (ECX)", "section": "Three-stage launch", "text": "On 8 August 2026 the project switched to a staged launch: an Alpha network forked from Bitcoin block 963,647 on 23 August, a Beta on 19 September, then a permanent mainnet [btk-ecx] [ecx-faq]. Sztorc explained the change on S17 E37: the software was ready, but people were distracted and the team wanted to let them practise first [ep-s17e37-launch].", "aliases": "ecx drivechain fork layertwo", "refs": ["btk-ecx", "ecx-faq", "ep-s17e37-launch"], "url": "/wiki/ecash-ecx/"}, {"id": "ecash-ecx#573", "slug": "ecash-ecx", "title": "eCash (ECX)", "section": "Mainnet", "text": "Mainnet forked from Bitcoin at block 973,728 on 29 October 2026. The public target had been 31 October, the white paper's 18th anniversary, but the fork was set by height and arrived two days early [btk-ecx]. Every Bitcoin address at the snapshot is credited 1:1 [btk-ecx]. Cointelegraph reported five sidechains at launch (BitNames, BitAssets, Thunder, Truthcoin, zSide), with Photon and CoinShift to follow [ecx-ct].", "aliases": "ecx drivechain fork layertwo", "refs": ["btk-ecx", "ecx-ct"], "url": "/wiki/ecash-ecx/"}, {"id": "ecash-ecx#574", "slug": "ecash-ecx", "title": "eCash (ECX)", "section": "Controversy", "text": "The ECX ledger includes 220 hard-coded transactions that reassign part of the Patoshi-pattern coins on the ECX chain only; Bitcoin itself is unchanged [btk-ecx].", "aliases": "ecx drivechain fork layertwo", "refs": ["btk-ecx"], "url": "/wiki/ecash-ecx/"}, {"id": "ecash-ecx#575", "slug": "ecash-ecx", "title": "eCash (ECX)", "section": "Not XEC", "text": "The project's own FAQ says ECX is not XEC, the ticker of Amaury Séchet's eCash [ecx-faq].", "aliases": "ecx drivechain fork layertwo", "refs": ["ecx-faq"], "url": "/wiki/ecash-ecx/"}, {"id": "ecash-xec#infobox", "slug": "ecash-xec", "title": "eCash (XEC)", "section": "Summary and infobox", "text": "Amaury Séchet's Bitcoin ABC chain, split from Bitcoin Cash in November 2020 over a developer fund; renamed eCash in 2021. Not to be confused with Paul Sztorc's eCash (ECX). Ticker: XEC (BCHA from 15 Nov 2020 to 1 Jul 2021) [btk-xec]; Type: UTXO hard fork of Bitcoin Cash [btk-xec]; Split: 15 November 2020 [btk-xec]; Last common block: 661,647 [btk-xec]; Founder: Amaury Séchet (Bitcoin ABC) [btk-xec]; Proof of work: SHA-256d [btk-xec]; Finality: Avalanche: blocks since 14 Sep 2022, transactions since 15 Nov 2025 [btk-xec]; Units: 1 XEC = 100 satoshis [btk-xec]; Block reward split: 58% miners, 16% Bitcoin ABC, 16% Global Network Council, 10% stakers [btk-xec]; Not the same as: eCash (ECX), Paul Sztorc's 2026 Bitcoin fork [ecx-faq]", "aliases": "xec bcha bitcoin abc", "refs": ["btk-xec", "ecx-faq"], "url": "/wiki/ecash-xec/"}, {"id": "ecash-xec#takeover", "slug": "ecash-xec", "title": "eCash (XEC)", "section": "Takeover view (editorial opinion)", "text": "Two Bitcoin forks now answer to “eCash”. This wiki always disambiguates by ticker: XEC is Séchet's chain from Bitcoin Cash, ECX is Sztorc's chain from Bitcoin. [btk-xec] [ecx-faq]", "aliases": "xec bcha bitcoin abc", "refs": ["btk-xec", "ecx-faq"], "url": "/wiki/ecash-xec/"}, {"id": "ecash-xec#578", "slug": "ecash-xec", "title": "eCash (XEC)", "section": "Split", "text": "eCash began as Bitcoin ABC's side of the 15 November 2020 Bitcoin Cash upgrade. ABC's Infrastructure Funding Plan, which directed part of the block reward to development, was rejected by the majority, and ABC's chain became BCHA [btk-bch] [xec-ifp]. The last common block was 661,647 [btk-xec]. It traded as BCHA until it was renamed eCash on 1 July 2021 [btk-xec] [xec-bcha].", "aliases": "xec bcha bitcoin abc", "refs": ["btk-bch", "btk-xec", "xec-bcha", "xec-ifp"], "url": "/wiki/ecash-xec/"}, {"id": "ecash-xec#579", "slug": "ecash-xec", "title": "eCash (XEC)", "section": "Design", "text": "eCash keeps SHA-256d proof of work and adds Avalanche, a finality layer written by Bitcoin ABC: blocks have been finalized since 14 September 2022 and transactions since 15 November 2025 [btk-xec]. On Bitcoin Takeover, Amaury Séchet described it as a fork of BCH, and of Bitcoin by extension, with another consensus layer on top [ep-s17e19-ecash]. Supply is the same 21 million coins in base units, displayed as 21 trillion XEC (1 XEC = 100 satoshis) [btk-xec].", "aliases": "xec bcha bitcoin abc", "refs": ["btk-xec", "ep-s17e19-ecash"], "url": "/wiki/ecash-xec/"}, {"id": "ecash-xec#580", "slug": "ecash-xec", "title": "eCash (XEC)", "section": "Funding", "text": "The block reward is split 58% to miners, 16% to Bitcoin ABC, 16% to the Global Network Council and 10% to stakers [btk-xec].", "aliases": "xec bcha bitcoin abc", "refs": ["btk-xec"], "url": "/wiki/ecash-xec/"}, {"id": "ecash-xec#581", "slug": "ecash-xec", "title": "eCash (XEC)", "section": "Name clash", "text": "eCash (XEC) is a different chain from eCash (ECX), the 2026 Bitcoin fork associated with Paul Sztorc; ecash.com states plainly that the e.cash project uses the ticker XEC and that the shared name does not mean the same asset [ecx-faq].", "aliases": "xec bcha bitcoin abc", "refs": ["ecx-faq"], "url": "/wiki/ecash-xec/"}, {"id": "eric-lombrozo#infobox", "slug": "eric-lombrozo", "title": "Eric Lombrozo", "section": "Summary and infobox", "text": "Bitcoin developer and co-author of the SegWit BIPs 141 and 144 and of the CHECKSEQUENCEVERIFY proposal, and an early Ethereum participant. GitHub: CodeShark, since July 2011 [lombrozo-gh]; BIP-141: Segregated Witness (Consensus layer), with Johnson Lau and Pieter Wuille [bips-list]; BIP-144: Segregated Witness (Peer Services), with Pieter Wuille [bips-list]; BIP-112: CHECKSEQUENCEVERIFY, with BtcDrak and Mark Friedenbach [bips-list]; Other BIPs: 83, 123 (BIP Classification), 124 [bips-list]", "aliases": "lombrozo codeshark", "refs": ["bips-list", "lombrozo-gh"], "url": "/wiki/eric-lombrozo/"}, {"id": "eric-lombrozo#takeover", "slug": "eric-lombrozo", "title": "Eric Lombrozo", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Lombrozo's name is first on the SegWit consensus BIP, the soft fork the whole 2015–2017 war was fought over, and he also appears in Ethereum's early contributor list. [bips-list] [ep-s17e42-lombrozo]", "aliases": "lombrozo codeshark", "refs": ["bips-list", "ep-s17e42-lombrozo"], "url": "/wiki/eric-lombrozo/"}, {"id": "eric-lombrozo#584", "slug": "eric-lombrozo", "title": "Eric Lombrozo", "section": "Specifications", "text": "The bitcoin/bips index lists Eric Lombrozo, Johnson Lau and Pieter Wuille as authors of BIP-141, “Segregated Witness (Consensus layer)”, and Lombrozo with Wuille on BIP-144, its peer-services companion [bips-list]. The index also lists him on BIP-112 (CHECKSEQUENCEVERIFY), BIP-83 (dynamic hierarchical deterministic key trees), BIP-123 (BIP Classification) and BIP-124 [bips-list]. His GitHub account, CodeShark, was created in July 2011 [lombrozo-gh].", "aliases": "lombrozo codeshark", "refs": ["bips-list", "lombrozo-gh"], "url": "/wiki/eric-lombrozo/"}, {"id": "eric-lombrozo#585", "slug": "eric-lombrozo", "title": "Eric Lombrozo", "section": "On the show", "text": "Vlad noted on Bitcoin Takeover that Lombrozo appears on the Early Days of Ethereum contributor grid, calling him “one of the architects of SegWit” [ep-s17e42-lombrozo]. In another episode Vlad cited Lombrozo's argument that in 2016 it was unclear whether Bitcoin would survive another year [ep-s17e19-lombrozo].", "aliases": "lombrozo codeshark", "refs": ["ep-s17e19-lombrozo", "ep-s17e42-lombrozo"], "url": "/wiki/eric-lombrozo/"}, {"id": "ethereum-classic#infobox", "slug": "ethereum-classic", "title": "Ethereum Classic (comparison — not a Bitcoin fork)", "section": "Summary and infobox", "text": "Not a Bitcoin fork: the original Ethereum chain that kept running when the Ethereum Foundation's July 2016 hard fork reversed the DAO theft, included here as a comparison case for “code is law”. Relation to Bitcoin: None by descent; comparison article [wp-etc]; Parent chain: Ethereum (Frontier, 30 July 2015) [wp-etc]; Split: 20 July 2016, DAO hard fork [wp-etc]; First ETC-only block: 1,920,000 [wp-etc]; DAO funds taken: 3.6 million Ether, about a third of The DAO [wp-dao]; Principle: “code is law” [wp-etc]", "aliases": "etc ethereum classic dao code is law not a bitcoin fork", "refs": ["wp-dao", "wp-etc"], "url": "/wiki/ethereum-classic/"}, {"id": "ethereum-classic#takeover", "slug": "ethereum-classic", "title": "Ethereum Classic (comparison — not a Bitcoin fork)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: ETC is the cleanest outside test of the Bitcoin fork argument — the chain that refused to rewrite history kept the old rules, and on the show Bob Summerwill called its ethos “Bitcoin philosophy, Ethereum technology”. [ep-s17e42-ethos] [wp-etc]", "aliases": "etc ethereum classic dao code is law not a bitcoin fork", "refs": ["ep-s17e42-ethos", "wp-etc"], "url": "/wiki/ethereum-classic/"}, {"id": "ethereum-classic#588", "slug": "ethereum-classic", "title": "Ethereum Classic (comparison — not a Bitcoin fork)", "section": "Not a Bitcoin fork", "text": "Ethereum Classic does not descend from Bitcoin's code or chain: it continues the Ethereum mainnet, first released via Frontier on 30 July 2015 [wp-etc]. This wiki includes it only as a comparison, because the 2016 split turned on a question Bitcoin's forks keep raising — whether a chain's history can be changed by social agreement [wp-etc].", "aliases": "etc ethereum classic dao code is law not a bitcoin fork", "refs": ["wp-etc"], "url": "/wiki/ethereum-classic/"}, {"id": "ethereum-classic#589", "slug": "ethereum-classic", "title": "Ethereum Classic (comparison — not a Bitcoin fork)", "section": "The DAO", "text": "Wikipedia's article on The DAO says an attacker used a vulnerability to transfer “3.6 million Ether - around a third of the 11.5 million Ether that had been committed to The DAO”, then worth about $50 million [wp-dao]. On 20 July 2016 the Ethereum Foundation released a new version of mainnet with what Wikipedia calls an “irregular state change” that erased the theft; the unaltered chain continued as Ethereum Classic, and block 1,920,000 was the first ETC block not in the forked chain [wp-etc].", "aliases": "etc ethereum classic dao code is law not a bitcoin fork", "refs": ["wp-dao", "wp-etc"], "url": "/wiki/ethereum-classic/"}, {"id": "ethereum-classic#590", "slug": "ethereum-classic", "title": "Ethereum Classic (comparison — not a Bitcoin fork)", "section": "Code is law", "text": "Wikipedia says supporters argue that blockchain immutability is paramount and that code should be treated as final (“code is law”), while opponents including the Ethereum Foundation contended that recovering stolen DAO funds “was justified to preserve user trust” [wp-etc]. On Bitcoin Takeover, Vlad summarised the split as a choice between “deciding that code is law” and “hard forking to return the money to the investors” [ep-s17e42-intro]. Bob Summerwill described the minority as the “typical cypherpunk original mindset” and the fork as “an irregular state transition” rather than a rewind of blocks [ep-s17e42-schism] [ep-s17e42-irregular].", "aliases": "etc ethereum classic dao code is law not a bitcoin fork", "refs": ["ep-s17e42-intro", "ep-s17e42-irregular", "ep-s17e42-schism", "wp-etc"], "url": "/wiki/ethereum-classic/"}, {"id": "ethereum-classic#591", "slug": "ethereum-classic", "title": "Ethereum Classic (comparison — not a Bitcoin fork)", "section": "Later history", "text": "Wikipedia records a series of 51% attacks on Ethereum Classic in 2020, followed by the ETChash (Thanos) change to its mining algorithm, and says that after Ethereum's move to proof of stake in 2022 ETC became the largest smart contract platform secured by proof of work [wp-etc]. Bob Summerwill said on the show that Grayscale fund fees supported the ETC Cooperative, of which he was later executive director for six years [ep-s17e42-silbert]. He also described EthereumPoW, a proof-of-work fork of Ethereum at its move to proof of stake, promoted by Chandler Guo, as “blatantly a cash grab” [ep-s17e42-ethpow].", "aliases": "etc ethereum classic dao code is law not a bitcoin fork", "refs": ["ep-s17e42-ethpow", "ep-s17e42-silbert", "wp-etc"], "url": "/wiki/ethereum-classic/"}, {"id": "ethereum-classic#592", "slug": "ethereum-classic", "title": "Ethereum Classic (comparison — not a Bitcoin fork)", "section": "Bitcoin parallels", "text": "Summerwill said the ETC community saw its ethos as “Bitcoin philosophy, Ethereum technology” [ep-s17e42-ethos]. In the same episode he described the BIP-110 chain grinding to a halt, a Bitcoin fork debate discussed in Bitcoin Knots [ep-s17e42-stall].", "aliases": "etc ethereum classic dao code is law not a bitcoin fork", "refs": ["ep-s17e42-ethos", "ep-s17e42-stall"], "url": "/wiki/ethereum-classic/"}, {"id": "ethereum-classic#593", "slug": "ethereum-classic", "title": "Ethereum Classic (comparison — not a Bitcoin fork)", "section": "Heard on Bitcoin Takeover", "text": "In the show's first episode (S1 E1, remastered August 2026), Donald McIntyre said: “I work for Ethereum Classic, which is the original Ethereum. Ethereum, without the term classic after it, is the fork of Ethereum Classic.” [ep-s1e1-q5723]", "aliases": "etc ethereum classic dao code is law not a bitcoin fork", "refs": ["ep-s1e1-q5723"], "url": "/wiki/ethereum-classic/"}, {"id": "f2pool#infobox", "slug": "f2pool", "title": "F2Pool", "section": "Summary and infobox", "text": "One of the first Chinese Bitcoin mining pools, co-founded by Wang Chun, who signed both the Hong Kong Roundtable and the New York Agreement. Co-founder: Wang Chun (Chun Wang) [wp-chunwang]; Founded: By 2013 [wp-chunwang]; Hong Kong Roundtable: Signed by Wang Chun, “Admin, F2Pool” [hk-letter]; New York Agreement: Signatory [nya-letter]; Scaling Bitcoin Hong Kong: On the December 2015 mining panel [btk-forkwars]", "aliases": "f2pool wang chun discus fish", "refs": ["btk-forkwars", "hk-letter", "nya-letter", "wp-chunwang"], "url": "/wiki/f2pool/"}, {"id": "f2pool#takeover", "slug": "f2pool", "title": "F2Pool", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: F2Pool is the miners' signature on both compromise documents of the war. It signed the 2016 Roundtable that promised a hard fork after SegWit and the 2017 agreement that tried again. [hk-letter] [nya-letter]", "aliases": "f2pool wang chun discus fish", "refs": ["hk-letter", "nya-letter"], "url": "/wiki/f2pool/"}, {"id": "f2pool#596", "slug": "f2pool", "title": "F2Pool", "section": "Founding", "text": "Wikipedia says Chun Wang borrowed $40,000 from his father in 2011 to invest in early cryptocurrency ventures and had co-founded F2Pool by 2013, and that for a time F2Pool was the world's largest bitcoin mining operation [wp-chunwang].", "aliases": "f2pool wang chun discus fish", "refs": ["wp-chunwang"], "url": "/wiki/f2pool/"}, {"id": "f2pool#597", "slug": "f2pool", "title": "F2Pool", "section": "In the war", "text": "Fork Wars lists F2Pool among the mining companies on the programme of the Scaling Bitcoin workshop in Hong Kong in December 2015 [btk-forkwars]. Wang Chun signed the February 2016 Roundtable statement as “Admin, F2Pool” [hk-letter], and F2Pool is among the New York Agreement signatories [nya-letter]. See Hong Kong Roundtable and New York Agreement.", "aliases": "f2pool wang chun discus fish", "refs": ["btk-forkwars", "hk-letter", "nya-letter"], "url": "/wiki/f2pool/"}, {"id": "fastbitcoin#infobox", "slug": "fastbitcoin", "title": "FastBitcoin (FBTC)", "section": "Summary and infobox", "text": "A fork at block 501,225 that replaced UTXOs with an account model and DPoS; the 2019 reviewer noted its code was not based on Bitcoin Core. Fork height: 501,225 [fbtc-site]; Block 501,225 time: 2017-12-27 06:55:44 UTC [btc-501225]; Ratio: 1 BTC : 1 FBTC [fbtc-site]; Consensus: DPOS, 10s block interval [fbtc-site]; Codebase: “(not based on Bitcoin Core)” [bth-review]", "aliases": "fbtc fast bitcoin", "refs": ["btc-501225", "bth-review", "fbtc-site"], "url": "/wiki/fastbitcoin/"}, {"id": "fastbitcoin#takeover", "slug": "fastbitcoin", "title": "FastBitcoin (FBTC)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: FastBitcoin's own README misstates its snapshot as block 5001225, a typo for 501,225. [fbtc-readme] [fbtc-site]", "aliases": "fbtc fast bitcoin", "refs": ["fbtc-readme", "fbtc-site"], "url": "/wiki/fastbitcoin/"}, {"id": "fastbitcoin#600", "slug": "fastbitcoin", "title": "FastBitcoin (FBTC)", "section": "Pitch", "text": "The archived site says “FBTC is a hard fork of Bitcoin at block 501225 on December 27, 2017” with holders receiving FBTC “at the ratio of 1 BTC : 1 FBTC” [fbtc-site]. Block 501,225 was mined that day [btc-501225]. It proposes solving UTXO inefficiency “by deploying account model” and lists DPOS consensus with a 10s block interval [fbtc-site].", "aliases": "fbtc fast bitcoin", "refs": ["btc-501225", "fbtc-site"], "url": "/wiki/fastbitcoin/"}, {"id": "fastbitcoin#601", "slug": "fastbitcoin", "title": "FastBitcoin (FBTC)", "section": "Code", "text": "The GitHub README says “All Bitcoin holders as of block 5001225 are now owners of Fast Bitcoin”, one zero more than the site's block 501225 [fbtc-readme] [fbtc-site]. The 2019 fork list links that repository with the note “(not based on Bitcoin Core)” [bth-review].", "aliases": "fbtc fast bitcoin", "refs": ["bth-review", "fbtc-readme", "fbtc-site"], "url": "/wiki/fastbitcoin/"}, {"id": "feathercoin#infobox", "slug": "feathercoin", "title": "Feathercoin", "section": "Summary and infobox", "text": "An April 2013 Litecoin-based coin with 60-second blocks and a 336 million supply, later moved to NeoScrypt. Type: Codebase fork in the Litecoin line (“New Litecoin based coin”) [ftc-ann]; Announced: 16 April 2013 by bushstar [ftc-ann]; Proof of work: NeoScrypt (per the later-edited thread) [ftc-ann]; Block time: 60 seconds [ftc-ann]; Supply: 336 million coins [ftc-ann]; Halving: Every 2,100,000 blocks [ftc-ann]", "aliases": "ftc neoscrypt", "refs": ["ftc-ann"], "url": "/wiki/feathercoin/"}, {"id": "feathercoin#takeover", "slug": "feathercoin", "title": "Feathercoin", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Feathercoin is a grandchild of Bitcoin by way of Litecoin, a reminder that the family tree branches through altcoins as well as from Bitcoin itself. [ftc-ann]", "aliases": "ftc neoscrypt", "refs": ["ftc-ann"], "url": "/wiki/feathercoin/"}, {"id": "feathercoin#604", "slug": "feathercoin", "title": "Feathercoin", "section": "Launch", "text": "The Feathercoin announcement thread was opened by bushstar on 16 April 2013, and early replies carry the title “FeatherCoin - New Litecoin based coin” [ftc-ann]. The current first post describes Feathercoin as “an upgraded and customised version of Bitcoin” [ftc-ann].", "aliases": "ftc neoscrypt", "refs": ["ftc-ann"], "url": "/wiki/feathercoin/"}, {"id": "feathercoin#605", "slug": "feathercoin", "title": "Feathercoin", "section": "Parameters", "text": "The thread, in its archived and later-edited form, lists NeoScrypt block hashing, a 60-second block target, 336 million coins in total and a block reward that halves every 2,100,000 blocks [ftc-ann]. It also describes its own difficulty algorithm, eHRC, and an automatic checkpointing system intended to resist 51% attacks [ftc-ann].", "aliases": "ftc neoscrypt", "refs": ["ftc-ann"], "url": "/wiki/feathercoin/"}, {"id": "firo#infobox", "slug": "firo", "title": "Firo (formerly Zcoin)", "section": "Summary and infobox", "text": "The first coin to implement the Zerocoin protocol, launched as Zcoin in September 2016 and renamed Firo in October 2020; its team says it is not a Zcash fork. Type: Independent privacy coin; not a fork of Zcash, per its project steward [ep-s16e5-rebrand]; Launched: 28 September 2016 as Zcoin [wp-firo]; Founder: Poramin Insom [wp-firo]; Renamed: Firo, October 2020 [wp-firo]; Privacy protocol: Zerocoin, then Sigma (2019), Lelantus, then Spark [wp-firo]; Proof of work: FiroPoW, a ProgPoW variant, since 26 Oct 2021 [wp-firo]; Consensus extras: LLMQ ChainLocks [firo-readme]", "aliases": "zcoin xzc firo lelantus zerocoin", "refs": ["ep-s16e5-rebrand", "firo-readme", "wp-firo"], "url": "/wiki/firo/"}, {"id": "firo#takeover", "slug": "firo", "title": "Firo (formerly Zcoin)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Firo is in a Bitcoin fork wiki because people keep calling it one, and because its own steward spent part of S16 E5 explaining that it is not a Zcash fork. Yap says that confusion was the main reason for the rename, and rejects the suggestion that it was meant to hide the project’s history. [ep-s16e5-rebrand]", "aliases": "zcoin xzc firo lelantus zerocoin", "refs": ["ep-s16e5-rebrand"], "url": "/wiki/firo/"}, {"id": "firo#608", "slug": "firo", "title": "Firo (formerly Zcoin)", "section": "Zcoin", "text": "Wikipedia says Poramin Insom wrote a paper on implementing Zerocoin with Matthew Green as faculty member, and launched Zcoin, the first cryptocurrency to implement the protocol, on 28 September 2016, with Roger Ver as initial investor [wp-firo]. On S16 E5 Reuben Yap said Poramin was essentially a lone developer and that Zcoin launched in September 2016 [ep-s16e5-launch].", "aliases": "zcoin xzc firo lelantus zerocoin", "refs": ["ep-s16e5-launch", "wp-firo"], "url": "/wiki/firo/"}, {"id": "firo#609", "slug": "firo", "title": "Firo (formerly Zcoin)", "section": "The 2017 bug", "text": "Wikipedia reports that in February 2017 an attack on the Zerocoin code created 370,000 fake tokens, which the attackers sold for more than 400 BTC, and that the team called it a single-symbol error [wp-firo]. Yap described it on the show as “a really, really basic bug… missing some equal sign”, which meant about 400,000 coins were created “out of thin air” [ep-s16e5-bug].", "aliases": "zcoin xzc firo lelantus zerocoin", "refs": ["ep-s16e5-bug", "wp-firo"], "url": "/wiki/firo/"}, {"id": "firo#610", "slug": "firo", "title": "Firo (formerly Zcoin)", "section": "From Zcoin to Firo", "text": "Wikipedia says Zcoin adopted the Sigma protocol in July 2019 and announced the rebrand to Firo in October 2020 [wp-firo]. Yap said the main reason was constant confusion with Zcash: “people were like, oh, Zcoin is a Zcash fork when it's not”, because Zerocoin and Zerocash are different protocols [ep-s16e5-rebrand]. The README describes Firo today as using the Spark protocol, FiroPoW mining and LLMQ ChainLocks against 51% attacks [firo-readme].", "aliases": "zcoin xzc firo lelantus zerocoin", "refs": ["ep-s16e5-rebrand", "firo-readme", "wp-firo"], "url": "/wiki/firo/"}, {"id": "firo#611", "slug": "firo", "title": "Firo (formerly Zcoin)", "section": "Lineage", "text": "This wiki has not verified which codebase Zcoin was originally built on, so it draws Firo without a parent line on the lineage map [wp-firo]. Wikipedia reports that Firo itself suffered a 51% attack in January 2021 [wp-firo].", "aliases": "zcoin xzc firo lelantus zerocoin", "refs": ["wp-firo"], "url": "/wiki/firo/"}, {"id": "fork-list-2019#infobox", "slug": "fork-list-2019", "title": "Source note: the 2019 fork list (johnsmithx)", "section": "Summary and infobox", "text": "The Bitcointalk list of 43 reviewed Bitcoin forks that this wiki cites as bth-review: who wrote it, how it tested forks, and its limits. Author: johnsmithx (Bitcointalk) [bth-review]; Opened: 18 January 2018 [bth-review]; Last update: February 26th, 2019 [bth-review]; Scope: 43 Bitcoin forks + 3 Bitcoin Cash forks [bth-review]; Working (Feb 2019): 16 (214.59 GB) [bth-review]", "aliases": "johnsmithx fork list review 43 reviewed", "refs": ["bth-review"], "url": "/wiki/fork-list-2019/"}, {"id": "fork-list-2019#takeover", "slug": "fork-list-2019", "title": "Source note: the 2019 fork list (johnsmithx)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: much of the fork-wave section rests on this one hands-on review, so its status strings are quoted, dated and never upgraded into facts about today. [bth-review]", "aliases": "johnsmithx fork list review 43 reviewed", "refs": ["bth-review"], "url": "/wiki/fork-list-2019/"}, {"id": "fork-list-2019#614", "slug": "fork-list-2019", "title": "Source note: the 2019 fork list (johnsmithx)", "section": "What it is", "text": "“My list of 43(+3) reviewed Bitcoin forks” was opened on Bitcointalk by johnsmithx on 18 January 2018 and last edited on 1 March 2019, although its own “last update” line says 26 February 2019 [bth-review]. It covers “43 (mostly) reviewed Bitcoin forks (+3 Bitcoin Cash forks)” and gives its last update as February 26th, 2019 [bth-review].", "aliases": "johnsmithx fork list review 43 reviewed", "refs": ["bth-review"], "url": "/wiki/fork-list-2019/"}, {"id": "fork-list-2019#615", "slug": "fork-list-2019", "title": "Source note: the 2019 fork list (johnsmithx)", "section": "Method", "text": "The author says he would “personally compile the source code, run the software, sync or import all the shared pre-fork blockchain data”, then load his Bitcoin Core wallet.dat and check his balances [bth-review]. He was “only interested in forks with full-node source code based on Bitcoin Core”, and pruned each chain to the fork block so the listed GB figure shows how much it grew [bth-review].", "aliases": "johnsmithx fork list review 43 reviewed", "refs": ["bth-review"], "url": "/wiki/fork-list-2019/"}, {"id": "fork-list-2019#616", "slug": "fork-list-2019", "title": "Source note: the 2019 fork list (johnsmithx)", "section": "Results and limits", "text": "Of 43 forks, it counts 16 that “seem to be working”, 5 that first worked then stopped, 1 with no nodes, 11 without full-node source code based on Bitcoin Core, 3 not tested, 2 abandoned and 5 that no longer seemed to exist [bth-review]. The author warns “This list is not comprehensive” and stopped adding forks that had only a website [bth-review]. This wiki cites it as bth-review and quotes its status lines with their 2019 date [bth-review].", "aliases": "johnsmithx fork list review 43 reviewed", "refs": ["bth-review"], "url": "/wiki/fork-list-2019/"}, {"id": "fox-btc#infobox", "slug": "fox-btc", "title": "Fox BTC (FBTC)", "section": "Summary and infobox", "text": "An April 2018 fork at block 520,419 by a company called Z-Magnetars, with 10MB blocks, GPU mining and a 5 million premine. Fork height: 520,419 [fox-pr]; Block 520,419 time: 2018-04-29 10:43:10 UTC [btc-520419]; Block size: 10MB [fox-site]; Supply: 27M, 5M premined [fox-site]", "aliases": "fbtc fox foxbtc z-magnetars", "refs": ["btc-520419", "fox-pr", "fox-site"], "url": "/wiki/fox-btc/"}, {"id": "fox-btc#takeover", "slug": "fox-btc", "title": "Fox BTC (FBTC)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Fox BTC pitched itself as company-based forking, with a premine for its own airdrop programme. [fox-site]", "aliases": "fbtc fox foxbtc z-magnetars", "refs": ["fox-site"], "url": "/wiki/fox-btc/"}, {"id": "fox-btc#619", "slug": "fox-btc", "title": "Fox BTC (FBTC)", "section": "Record", "text": "A Bitcoin PR Buzz release says “FOXBTC hard fork, performed by tech company Z-Magnetars will happen on April 30th at block height 520419” [fox-pr]. Block 520,419 was mined on 29 April 2018 UTC [btc-520419]. The archived site says “FOXBTC aims to empower company-based forking in the crypto markets by enabling users to store and exchange any airdrop” [fox-site]. It lists 10MB blocks, a three-minute interval and GPU mining, and a 27M supply “of which 5M are premined (4M allocated for airdrop and 1M for the team)” [fox-site]. The README is the stock Bitcoin Core text renamed to FBTC [fox-readme]. The FBTC ticker is shared with FastBitcoin [fd-data].", "aliases": "fbtc fox foxbtc z-magnetars", "refs": ["btc-520419", "fd-data", "fox-pr", "fox-readme", "fox-site"], "url": "/wiki/fox-btc/"}, {"id": "gavin-andresen#infobox", "slug": "gavin-andresen", "title": "Gavin Andresen", "section": "Summary and infobox", "text": "Satoshi Nakamoto's successor as Bitcoin's lead developer, author of BIP-101 and BIP-109, and later a casualty of Craig Wright's claim. Born: 1966, as Gavin Bell [wp-gavin]; Known for: Lead developer after Satoshi; founder of the Bitcoin Foundation (2012) [wp-gavin]; Proposals: BIP-101 (8 MB, doubling) and BIP-109 (2 MB) [bip101]; Clients: Bitcoin XT, with Mike Hearn [xt-bw]; New York Agreement: Named individually as a supporter [nya-letter]; 2016: Supported Craig Wright's claim to be Satoshi; commit access revoked [wp-gavin]; Replay draft (Jun 2017): OP_RETURN “!segwit2x” patch (gist) [gavin-gist]", "aliases": "gavin", "refs": ["bip101", "gavin-gist", "nya-letter", "wp-gavin", "xt-bw"], "url": "/wiki/gavin-andresen/"}, {"id": "gavin-andresen#takeover", "slug": "gavin-andresen", "title": "Gavin Andresen", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: a central big-block figure in Fork Wars, and on S16 E60 Jonathan Bier argued his support for Craig Wright did the big-block side lasting damage. [btk-forkwars] [ep-s16e60-wright]", "aliases": "gavin", "refs": ["btk-forkwars", "ep-s16e60-wright"], "url": "/wiki/gavin-andresen/"}, {"id": "gavin-andresen#622", "slug": "gavin-andresen", "title": "Gavin Andresen", "section": "Early Bitcoin", "text": "Andresen first encountered Bitcoin in 2010 and created the Bitcoin Faucet, which gave away bitcoin [wp-gavin]. In September 2010 Satoshi Nakamoto told him he was working on other projects and, over the following months, handed him control of the SourceForge repository and the network alert key [wp-gavin]. He founded the Bitcoin Foundation in 2012 and stepped back as lead maintainer in 2014 to focus on it [wp-gavin].", "aliases": "gavin", "refs": ["wp-gavin"], "url": "/wiki/gavin-andresen/"}, {"id": "gavin-andresen#623", "slug": "gavin-andresen", "title": "Gavin Andresen", "section": "Block size proposals", "text": "Andresen authored BIP-101, which proposed 8 MB blocks from January 2016 doubling every two years, and shipped it in Bitcoin XT [bip101] [xt-bw]. He withdrew BIP-101 in February 2016 [bip101-withdraw]. He also authored BIP-109, the one-time 2 MB increase behind Bitcoin Classic [bip109]. In May 2017 he was named individually on the New York Agreement supporter list [nya-letter].", "aliases": "gavin", "refs": ["bip101", "bip101-withdraw", "bip109", "nya-letter", "xt-bw"], "url": "/wiki/gavin-andresen/"}, {"id": "gavin-andresen#624", "slug": "gavin-andresen", "title": "Gavin Andresen", "section": "Craig Wright", "text": "In May 2016 Andresen supported Craig Wright's claim to be Satoshi, a claim that was later discredited [wp-gavin]. His ability to change Bitcoin's main code was revoked [wp-gavin]. On S16 E60, Jonathan Bier said that “Gavin coming out in support of Craig Wright hugely damaged Gavin's reputation” [ep-s16e60-wright].", "aliases": "gavin", "refs": ["ep-s16e60-wright", "wp-gavin"], "url": "/wiki/gavin-andresen/"}, {"id": "gavin-andresen#625", "slug": "gavin-andresen", "title": "Gavin Andresen", "section": "2017 replay-protection draft", "text": "On 15 June 2017 Andresen published a GitHub gist titled “OP_RETURN replay protection patch” [gavin-gist]. The patch marks a transaction as replay-protected when one of its outputs is exactly an OP_RETURN carrying the bytes of “!segwit2x”; patched nodes treat such a transaction as non-standard and reject any block containing one with the error “bad-blk-replay” [gavin-gist]. The block rule carries the comment “TODO: hard fork condition...”, so the draft did not yet say from which block it applied [gavin-gist]. In August 2017 Jeff Garzik's btc1 pull request #117 for SegWit2x said it was based on this gist, using a different marker, “OP_RETURN 'RP=!>1x'” [btc1-pr117]. See Replay protection in the 2017 forks [btc1-pr117].", "aliases": "gavin", "refs": ["btc1-pr117", "gavin-gist"], "url": "/wiki/gavin-andresen/"}, {"id": "gorillapool#infobox", "slug": "gorillapool", "title": "GorillaPool", "section": "Summary and infobox", "text": "A BSV mining pool run by Kurt Wuckert Jr. and partners, which says it works with the Teranode team. Chain: BSV [gorilla-site]; Fee: 2% pool fee, daily payouts [gorilla-site]; Payouts (pool.io site): PPLNS, direct to address, no accounts [gorilla-io]; Operator: Kurt Wuckert Jr. and two partners (his account) [ep-s17e39-gorilla]; Teranode: “actively working with the Teranode team” [gorilla-site]", "aliases": "gorillapool gorilla pool kurt bsv", "refs": ["ep-s17e39-gorilla", "gorilla-io", "gorilla-site"], "url": "/wiki/gorillapool/"}, {"id": "gorillapool#takeover", "slug": "gorillapool", "title": "GorillaPool", "section": "Takeover view (editorial opinion)", "text": "Kurt Wuckert Jr. described GorillaPool on S17 E39 as “me and two buddies” who put in enough money to mine for about five years. [ep-s17e39-gorilla] [ep-s17e39-coingeek]", "aliases": "gorillapool gorilla pool kurt bsv", "refs": ["ep-s17e39-coingeek", "ep-s17e39-gorilla"], "url": "/wiki/gorillapool/"}, {"id": "gorillapool#628", "slug": "gorillapool", "title": "GorillaPool", "section": "Pool", "text": "GorillaPool's site calls itself a BSV mining pool, offers a “2% pool fee with daily payouts”, and says it is one of the only pools “actively working with the Teranode team” [gorilla-site]. Its gorillapool.io page describes a “Permissionless Stratum interface between your ASICs and a BSV node” with PPLNS and direct payouts [gorilla-io].", "aliases": "gorillapool gorilla pool kurt bsv", "refs": ["gorilla-io", "gorilla-site"], "url": "/wiki/gorillapool/"}, {"id": "gorillapool#629", "slug": "gorillapool", "title": "GorillaPool", "section": "Operators", "text": "On S17 E39 Vlad introduced Kurt Wuckert Jr. as a CoinGeek journalist “running Gorilla Pool, which is a mining pool for SHA-256” [ep-s17e39-coingeek]. Wuckert said: “It's me and two buddies, put in a chunk of money, enough to mine for, like, five years” [ep-s17e39-gorilla]. The pool's founding date is not sourced here [ep-s17e39-gorilla].", "aliases": "gorillapool gorilla pool kurt bsv", "refs": ["ep-s17e39-coingeek", "ep-s17e39-gorilla"], "url": "/wiki/gorillapool/"}, {"id": "great-consensus-cleanup#infobox", "slug": "great-consensus-cleanup", "title": "Great Consensus Cleanup (BIP-54)", "section": "Summary and infobox", "text": "A soft fork bundling fixes for the timewarp bug, slow-to-validate blocks, 64-byte transactions and duplicate coinbases; first drafted in 2019 and specified as BIP-54 in 2025. BIP: 54, “Consensus Cleanup” [bip54]; Authors: Antoine Poinsot, Matt Corallo [bip54]; Assigned: 2025-04-11 [bip54]; BIP status: Complete [bip54]; Fixes: Timewarp, slow blocks, 64-byte txs, duplicate txs [optech-gcc]; History: 2019 draft deferred; renewed from 2023 [optech-gcc]", "aliases": "gcc bip54 bip-54 consensus cleanup timewarp poinsot", "refs": ["bip54", "optech-gcc"], "url": "/wiki/great-consensus-cleanup/"}, {"id": "great-consensus-cleanup#takeover", "slug": "great-consensus-cleanup", "title": "Great Consensus Cleanup (BIP-54)", "section": "Takeover view (editorial opinion)", "text": "On S17 E48 Robin Linus said Peter Todd guessed the Cleanup would come in 2029, and that if that was all Bitcoin got, “I'm out”. [ep-s17e48-gcc]", "aliases": "gcc bip54 bip-54 consensus cleanup timewarp poinsot", "refs": ["ep-s17e48-gcc"], "url": "/wiki/great-consensus-cleanup/"}, {"id": "great-consensus-cleanup#632", "slug": "great-consensus-cleanup", "title": "Great Consensus Cleanup (BIP-54)", "section": "Proposal", "text": "BIP-54 names Antoine Poinsot and Matt Corallo as authors and proposes rules “to fix the timewarp attack, reduce the worst case block validation time, prevent Merkle tree weaknesses, and avoid duplicate transactions without” BIP-30 validation [bip54]. It says that in the worst case a timewarp attacker “can bring down the difficulty to its minimum within 38 days” [bip54].", "aliases": "gcc bip54 bip-54 consensus cleanup timewarp poinsot", "refs": ["bip54"], "url": "/wiki/great-consensus-cleanup/"}, {"id": "great-consensus-cleanup#633", "slug": "great-consensus-cleanup", "title": "Great Consensus Cleanup (BIP-54)", "section": "History", "text": "Bitcoin Optech says the effort followed “a prior draft in 2019” that was deferred, with renewed work since 2023 that became BIP54 [optech-gcc]. Optech lists the four fixes as the time warp bug, slow-to-validate blocks, the Merkle tree weakness of 64-byte transactions, and the duplicate transaction vector [optech-gcc]. The BIP's status is Complete [bip54]. Optech's 2026 entries include a summary of “the remaining steps before activation”, so it had not activated by then [optech-gcc].", "aliases": "gcc bip54 bip-54 consensus cleanup timewarp poinsot", "refs": ["bip54", "optech-gcc"], "url": "/wiki/great-consensus-cleanup/"}, {"id": "great-consensus-cleanup#634", "slug": "great-consensus-cleanup", "title": "Great Consensus Cleanup (BIP-54)", "section": "On the show", "text": "Robin Linus said on S17 E48 that Peter Todd had guessed “the Great Consensus Cleanup will come in, like, '29” [ep-s17e48-gcc]. In the same conversation he said “We're going to get BIP 448, TEMPLATEHASH” [ep-s17e48-template].", "aliases": "gcc bip54 bip-54 consensus cleanup timewarp poinsot", "refs": ["ep-s17e48-gcc", "ep-s17e48-template"], "url": "/wiki/great-consensus-cleanup/"}, {"id": "gregory-maxwell#infobox", "slug": "gregory-maxwell", "title": "Gregory Maxwell", "section": "Summary and infobox", "text": "Bitcoin Core developer behind CoinJoin and a Blockstream co-founder, central to the SegWit-first capacity roadmap. Known for: CoinJoin (proposed 22 August 2013) [coinjoin]; Company: Blockstream co-founder (2014) [wp-blockstream]; 2015 roadmap: Signatory of “Capacity increases for the Bitcoin system” [roadmap-2015]; Stance: Hard forks only if “almost completely uncontroversial” (May 2015) [btk-forkwars]", "aliases": "gmaxwell greg maxwell coinjoin", "refs": ["btk-forkwars", "coinjoin", "roadmap-2015", "wp-blockstream"], "url": "/wiki/gregory-maxwell/"}, {"id": "gregory-maxwell#takeover", "slug": "gregory-maxwell", "title": "Gregory Maxwell", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Maxwell is the conservative pole of Fork Wars, the person whose December 2015 roadmap became the small-block side's founding document. [btk-forkwars]", "aliases": "gmaxwell greg maxwell coinjoin", "refs": ["btk-forkwars"], "url": "/wiki/gregory-maxwell/"}, {"id": "gregory-maxwell#637", "slug": "gregory-maxwell", "title": "Gregory Maxwell", "section": "CoinJoin", "text": "On 22 August 2013 Maxwell, posting as gmaxwell, opened the Bitcointalk thread “CoinJoin: Bitcoin privacy for the real world”, arguing that Bitcoin's only privacy came from pseudonymous addresses that are “fragile and easily compromised” [coinjoin].", "aliases": "gmaxwell greg maxwell coinjoin", "refs": ["coinjoin"], "url": "/wiki/gregory-maxwell/"}, {"id": "gregory-maxwell#638", "slug": "gregory-maxwell", "title": "Gregory Maxwell", "section": "Block size war", "text": "Fork Wars cites a May 2015 bitcoin-dev post in which he argued that hard-fork changes “should only be made if they're almost completely uncontroversial” [btk-forkwars]. It treats his December 2015 “Capacity increases for the Bitcoin system” as a SegWit-first plan with further increases “when justified”, not a 2 MB pledge [btk-forkwars]. He is listed among the signatories of that roadmap [roadmap-2015].", "aliases": "gmaxwell greg maxwell coinjoin", "refs": ["btk-forkwars", "roadmap-2015"], "url": "/wiki/gregory-maxwell/"}, {"id": "gregory-maxwell#639", "slug": "gregory-maxwell", "title": "Gregory Maxwell", "section": "Blockstream", "text": "Blockstream was founded in 2014 by Adam Back with developers including Pieter Wuille and Gregory Maxwell [wp-blockstream].", "aliases": "gmaxwell greg maxwell coinjoin", "refs": ["wp-blockstream"], "url": "/wiki/gregory-maxwell/"}, {"id": "groestlcoin#infobox", "slug": "groestlcoin", "title": "Groestlcoin (GRS)", "section": "Summary and infobox", "text": "A March 2014 code fork of Bitcoin 0.8.6 that swapped SHA-256 for Grøstl and still tracks Bitcoin Core releases. Forked from: Bitcoin reference wallet 0.8.6, March 2014 [grs-readme]; Genesis timestamp: 2014-03-20 19:13:49 UTC [grs-chainparams]; Genesis motto: “Pressure must be put on Vladimir Putin over Crimea” [grs-chainparams]; Launched: 22 Mar 2014, 21:00 GMT (announcement) [grs-ann]; Developer: gruve_p (announcement author) [grs-ann]; Claim: “1st to activate Segwit & Taproot” [grs-ann]", "aliases": "grs groestl grøstl", "refs": ["grs-ann", "grs-chainparams", "grs-readme"], "url": "/wiki/groestlcoin/"}, {"id": "groestlcoin#takeover", "slug": "groestlcoin", "title": "Groestlcoin (GRS)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Groestlcoin is a code fork that stayed close to its parent: it forked 0.8.6 in 2014 and kept merging Bitcoin Core work, including SegWit and Taproot, which it claims it activated first. [grs-readme] [grs-ann]", "aliases": "grs groestl grøstl", "refs": ["grs-ann", "grs-readme"], "url": "/wiki/groestlcoin/"}, {"id": "groestlcoin#642", "slug": "groestlcoin", "title": "Groestlcoin (GRS)", "section": "Fork", "text": "The Groestlcoin Core README opens with “Forked from Bitcoin reference wallet 0.8.6 on March 2014” [grs-readme]. Its chain parameters give a genesis timestamp of 1395342829, which is 20 March 2014 at 19:13:49 UTC, and the genesis text “Pressure must be put on Vladimir Putin over Crimea” [grs-chainparams].", "aliases": "grs groestl grøstl", "refs": ["grs-chainparams", "grs-readme"], "url": "/wiki/groestlcoin/"}, {"id": "groestlcoin#643", "slug": "groestlcoin", "title": "Groestlcoin (GRS)", "section": "Launch and claims", "text": "The Bitcointalk announcement by gruve_p says Groestlcoin “Launched 22nd March, 2014 at 09:00 PM GMT” [grs-ann]. The thread title claims Groestlcoin was the “1st to activate Segwit & Taproot”; this wiki has not independently checked that claim against other chains' activation dates [grs-ann].", "aliases": "grs groestl grøstl", "refs": ["grs-ann"], "url": "/wiki/groestlcoin/"}, {"id": "haipo-yang#infobox", "slug": "haipo-yang", "title": "Haipo Yang", "section": "Summary and infobox", "text": "Founder and CEO of ViaBTC, who wrote the pool's code in May 2016; ViaBTC suggested the name Bitcoin Cash and mined its first block. Founded: ViaBTC (pool code completed May 2016) [viabtc-blog]; First ViaBTC block: 5 June 2016 [viabtc-blog]; Later businesses: CoinEx Exchange, CoinEx Wallet, CSC, ViaBTC Capital [viabtc-blog]; Bitcoin Cash: ViaBTC suggested the name, July 2017 [wp-bch]; First BCH block: 478,559, mined by ViaBTC [btk-forkwars]", "aliases": "haipo yang viabtc coinex", "refs": ["btk-forkwars", "viabtc-blog", "wp-bch"], "url": "/wiki/haipo-yang/"}, {"id": "haipo-yang#takeover", "slug": "haipo-yang", "title": "Haipo Yang", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: a single developer's mining pool, a year old at the time, named the most important Bitcoin fork and mined its first block — a measure of how much a pool operator could shape the split. [viabtc-blog] [wp-bch] [btk-forkwars]", "aliases": "haipo yang viabtc coinex", "refs": ["btk-forkwars", "viabtc-blog", "wp-bch"], "url": "/wiki/haipo-yang/"}, {"id": "haipo-yang#646", "slug": "haipo-yang", "title": "Haipo Yang", "section": "ViaBTC", "text": "A 2024 ViaBTC interview says that “In May 2016, Haipo Yang single-handedly completed all the code for the ViaBTC Pool”, and that the pool mined its first block on 5 June 2016 [viabtc-blog]. The same interview lists the businesses that followed: CoinEx Exchange, CoinEx Wallet, CSC (CoinEx Smart Chain) and ViaBTC Capital [viabtc-blog].", "aliases": "haipo yang viabtc coinex", "refs": ["viabtc-blog"], "url": "/wiki/haipo-yang/"}, {"id": "haipo-yang#647", "slug": "haipo-yang", "title": "Haipo Yang", "section": "Bitcoin Cash", "text": "Wikipedia says that in July 2017 “the mining pool ViaBTC suggested the name Bitcoin Cash for the fork” [wp-bch]. Bitcoin Takeover's Fork Wars timeline records that the first Bitcoin Cash block, 478,559, was mined by ViaBTC [btk-forkwars]. See ViaBTC for the pool's history [viabtc-blog].", "aliases": "haipo yang viabtc coinex", "refs": ["btk-forkwars", "viabtc-blog", "wp-bch"], "url": "/wiki/haipo-yang/"}, {"id": "hard-fork-vs-soft-fork#infobox", "slug": "hard-fork-vs-soft-fork", "title": "Hard fork vs soft fork", "section": "Summary and infobox", "text": "The two ways to change Bitcoin's rules: soft forks tighten them and stay backward-compatible; hard forks loosen them and need everyone to upgrade. Soft fork: Only previously valid blocks become invalid; backward-compatible [bw-softfork]; Hard fork: Previously invalid blocks become valid; all users must upgrade [bw-hardfork]; MASF / UASF: Miner-activated vs user-activated soft fork [bw-softfork]; Accidental hard forks: 2013 (BIP 50, BerkeleyDB; chain split) and CVE-2018-17144 (no split; fixed by soft fork) [bw-hardfork]; Bitcoin's record: Every deliberate Bitcoin upgrade in the Forks! magazine's fork table was a soft fork [btk-allforks]", "aliases": "hardfork softfork masf uasf", "refs": ["btk-allforks", "bw-hardfork", "bw-softfork"], "url": "/wiki/hard-fork-vs-soft-fork/"}, {"id": "hard-fork-vs-soft-fork#takeover", "slug": "hard-fork-vs-soft-fork", "title": "Hard fork vs soft fork", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: every chain in this wiki's Forks category that really forked Bitcoin is, from Bitcoin's point of view, a hard fork that did not win, while Bitcoin itself has upgraded only by soft fork. [btk-allforks]", "aliases": "hardfork softfork masf uasf", "refs": ["btk-allforks"], "url": "/wiki/hard-fork-vs-soft-fork/"}, {"id": "hard-fork-vs-soft-fork#650", "slug": "hard-fork-vs-soft-fork", "title": "Hard fork vs soft fork", "section": "Definitions", "text": "A soft fork is a change in which only previously valid blocks or transactions are made invalid; because old nodes still accept the new blocks, it is backward-compatible [bw-softfork]. A hard fork makes previously invalid blocks or transactions valid, and therefore requires all users to upgrade [bw-hardfork]. When miners coordinate to enforce new rules it is a miner-activated soft fork (MASF); when full nodes do it without miner support it is a user-activated soft fork (UASF) [bw-softfork].", "aliases": "hardfork softfork masf uasf", "refs": ["bw-hardfork", "bw-softfork"], "url": "/wiki/hard-fork-vs-soft-fork/"}, {"id": "hard-fork-vs-soft-fork#651", "slug": "hard-fork-vs-soft-fork", "title": "Hard fork vs soft fork", "section": "Activation methods", "text": "Bitcoin Takeover's fork table traces how soft forks were activated: a flag day after a coinbase poll for P2SH, IsSuperMajority version counting for BIP-34, 66 and 65, BIP-9 version bits for CSV and SegWit, and Speedy Trial for Taproot [btk-allforks]. BIP-9 locks in when 1,916 of 2,016 blocks in a retarget period signal, which the table says gave miners an effective veto [btk-allforks].", "aliases": "hardfork softfork masf uasf", "refs": ["btk-allforks"], "url": "/wiki/hard-fork-vs-soft-fork/"}, {"id": "hard-fork-vs-soft-fork#652", "slug": "hard-fork-vs-soft-fork", "title": "Hard fork vs soft fork", "section": "Accidents", "text": "The Bitcoin Wiki counts two accidental hard forks in Bitcoin Core: the 2013 BerkeleyDB split described in BIP 50, and CVE-2018-17144 in Bitcoin Core 0.15, which caused no chain split and was fixed by a soft fork in 0.16.3 [bw-hardfork]. The August 2010 value overflow is covered separately.", "aliases": "hardfork softfork masf uasf", "refs": ["bw-hardfork"], "url": "/wiki/hard-fork-vs-soft-fork/"}, {"id": "hard-fork-vs-soft-fork#653", "slug": "hard-fork-vs-soft-fork", "title": "Hard fork vs soft fork", "section": "Chain splits", "text": "When a hard fork is contested, both chains can survive, as with Bitcoin Cash in 2017 [btk-bch]. The UASF showed that a soft fork can also threaten a split if nodes reject blocks that miners still produce [bip148].", "aliases": "hardfork softfork masf uasf", "refs": ["bip148", "btk-bch"], "url": "/wiki/hard-fork-vs-soft-fork/"}, {"id": "hex#infobox", "slug": "hex", "title": "HEX", "section": "Summary and infobox", "text": "Richard Heart's ERC-20 token, offered from December 2019 with airdrops to large Bitcoin holders; the SEC sued in 2023 and the court dismissed the case in 2025. Type: ERC-20 token on Ethereum [sec-heart-complaint]; Founder: Richard Heart (Richard J. Schueler) [sec-heart-pr]; Offering period (SEC): 3 Dec 2019 – at least 19 Nov 2020 [sec-heart-complaint]; SEC suit: Filed 31 Jul 2023, E.D.N.Y. [sec-heart-lr]; Outcome: Motion to dismiss granted; SEC did not amend (21 Apr 2025) [heart-dismissal] [csv-heart]; Contract: 0x2b591e99afE9f32eAA6214f7B7629768c40Eeb39 [hex-site]", "aliases": "richard heart schueler pulsechain pulsex sec erc-20", "refs": ["csv-heart", "heart-dismissal", "hex-site", "sec-heart-complaint", "sec-heart-lr", "sec-heart-pr"], "url": "/wiki/hex/"}, {"id": "hex#takeover", "slug": "hex", "title": "HEX", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: HEX is on the list because of its Bitcoin-holder airdrops, not its chain. It is a reminder that free coins for BTC holders outlived the 2017 fork wave. [sec-heart-complaint]", "aliases": "richard heart schueler pulsechain pulsex sec erc-20", "refs": ["sec-heart-complaint"], "url": "/wiki/hex/"}, {"id": "hex#656", "slug": "hex", "title": "HEX", "section": "Token and launch", "text": "The SEC's complaint describes Hex as an ERC-20 token and “an unincorporated entity established by Heart” and dates the Hex offering from December 3, 2019 “through at least November 19, 2020” [sec-heart-complaint]. According to the complaint, Heart conducted two airdrops in which Hex tokens were deposited into wallets “that he identified as significant holders of Bitcoin”, and a similar airdrop to large ETH holders [sec-heart-complaint].", "aliases": "richard heart schueler pulsechain pulsex sec erc-20", "refs": ["sec-heart-complaint"], "url": "/wiki/hex/"}, {"id": "hex#657", "slug": "hex", "title": "HEX", "section": "SEC case", "text": "On 31 July 2023 the SEC charged Heart, Hex, PulseChain and PulseX with unregistered offerings that “raised more than $1 billion in crypto assets”, and charged Heart and PulseChain with fraud over at least $12 million of alleged misappropriation [sec-heart-pr]. The litigation release says the SEC alleged Heart began marketing Hex in 2018 as the first high-yield “blockchain certificate of deposit” [sec-heart-lr].", "aliases": "richard heart schueler pulsechain pulsex sec erc-20", "refs": ["sec-heart-lr", "sec-heart-pr"], "url": "/wiki/hex/"}, {"id": "hex#658", "slug": "hex", "title": "HEX", "section": "Dismissal", "text": "Judge Carol Bagley Amon's memorandum and order states: “For the reasons stated below, the motion to dismiss is GRANTED” [heart-dismissal]. Heart's counsel wrote that on 21 April 2025 “the SEC declined to file an amended complaint”, after a February ruling that dismissed all the SEC's claims [csv-heart]. The hex.com homepage still lists the HEX contract address [hex-site].", "aliases": "richard heart schueler pulsechain pulsex sec erc-20", "refs": ["csv-heart", "heart-dismissal", "hex-site"], "url": "/wiki/hex/"}, {"id": "hex#659", "slug": "hex", "title": "HEX", "section": "Heard on Bitcoin Takeover", "text": "Vlad recalled on S16 E49 (October 2025): “I was one of the first people to debate Richard Heart in 2018, when he was about to call it BitcoinHEX.” [ep-s16e49-q12929]", "aliases": "richard heart schueler pulsechain pulsex sec erc-20", "refs": ["ep-s16e49-q12929"], "url": "/wiki/hex/"}, {"id": "hong-kong-roundtable#infobox", "slug": "hong-kong-roundtable", "title": "Hong Kong Roundtable", "section": "Summary and infobox", "text": "The February 2016 meeting where miners and some Core contributors agreed SegWit first, then a roughly 2 MB hard fork that never shipped. Date: 21 February 2016 (statement posted 20 February) [hk-letter]; Place: Cyberport, Hong Kong [hk-letter]; SegWit: Expected release April 2016 [hk-letter]; Hard fork: Non-witness data around 2 MB, total no more than 4 MB; code by July 2016 [hk-letter]; Activation: “Likely … around July 2017” with strong community support [hk-letter]; Signers include: Adam Back, Luke Dashjr, Peter Todd, Matt Corallo, Jihan Wu, Bobby Lee, Wang Chun [hk-letter]", "aliases": "hong kong agreement hk roundtable consensus", "refs": ["hk-letter"], "url": "/wiki/hong-kong-roundtable/"}, {"id": "hong-kong-roundtable#takeover", "slug": "hong-kong-roundtable", "title": "Hong Kong Roundtable", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: the most argued-over text of the war. Fork Wars shows Roger Ver and Jonathan Bier agreeing the letter was published and the hard fork never came on schedule, while disagreeing on what it promised. [btk-forkwars]", "aliases": "hong kong agreement hk roundtable consensus", "refs": ["btk-forkwars"], "url": "/wiki/hong-kong-roundtable/"}, {"id": "hong-kong-roundtable#662", "slug": "hong-kong-roundtable", "title": "Hong Kong Roundtable", "section": "The statement", "text": "The statement says that on 21 February 2016, in Hong Kong's Cyberport, representatives of the Bitcoin industry and members of the development community agreed on a series of points [hk-letter]. SegWit would continue as a soft fork, and the Bitcoin Core contributors present would have a hard-fork implementation available as a recommendation within three months of SegWit's release [hk-letter]. That hard fork was expected to raise non-witness data to around 2 MB, with total size no more than 4 MB, and would only be adopted with broad support [hk-letter].", "aliases": "hong kong agreement hk roundtable consensus", "refs": ["hk-letter"], "url": "/wiki/hong-kong-roundtable/"}, {"id": "hong-kong-roundtable#663", "slug": "hong-kong-roundtable", "title": "Hong Kong Roundtable", "section": "Timeline and commitments", "text": "The letter projected SegWit for April 2016, hard-fork code by July 2016 and, with strong community support, activation around July 2017 [hk-letter]. Signers committed to run only Bitcoin Core-compatible consensus systems for the foreseeable future [hk-letter].", "aliases": "hong kong agreement hk roundtable consensus", "refs": ["hk-letter"], "url": "/wiki/hong-kong-roundtable/"}, {"id": "hong-kong-roundtable#664", "slug": "hong-kong-roundtable", "title": "Hong Kong Roundtable", "section": "Who signed", "text": "Signers included Bitcoin Core contributors Cory Fields, Johnson Lau, Luke Dashjr, Matt Corallo and Peter Todd, Bitmain's Jihan Wu and Micree Zhan, Blockstream's Adam Back, BTCC's Bobby Lee and Samson Mow, F2Pool's Wang Chun, and Jack Liao of LightningASIC [hk-letter]. Jack Liao later became the public face of Bitcoin Gold [btk-btg].", "aliases": "hong kong agreement hk roundtable consensus", "refs": ["btk-btg", "hk-letter"], "url": "/wiki/hong-kong-roundtable/"}, {"id": "hong-kong-roundtable#665", "slug": "hong-kong-roundtable", "title": "Hong Kong Roundtable", "section": "Legacy", "text": "The SegWit2x project later cited the roundtable as the first agreement on 2 MB blocks [s2x-announce].", "aliases": "hong kong agreement hk roundtable consensus", "refs": ["s2x-announce"], "url": "/wiki/hong-kong-roundtable/"}, {"id": "ixcoin-and-i0coin#infobox", "slug": "ixcoin-and-i0coin", "title": "Ixcoin and I0coin", "section": "Summary and infobox", "text": "Ixcoin (August 2011), a premined Bitcoin code fork with double the block reward, and I0coin, its no-premine copy a week later. Ixcoin announced: 10 Aug 2011 by Nasakioto (PGP-signed) [ixc-ann]; Reward: 96 IXC per block, 21 million cap [ixc-ann]; Coins on launch day: ~580K “as of 10th August 2011” [ixc-ann]; I0coin idea: 11 Aug 2011, “Ixcoin with 0 pregenerated blocks” [i0c-thread]; I0coin launch: 16 Aug 2011, kr105 (Litecoin Wiki) [ltcwiki-history]; Ixcoin today: “merged mined with Bitcoin” (README) [ixc-readme]", "aliases": "ixcoin ixc i0coin premine", "refs": ["i0c-thread", "ixc-ann", "ixc-readme", "ltcwiki-history"], "url": "/wiki/ixcoin-and-i0coin/"}, {"id": "ixcoin-and-i0coin#takeover", "slug": "ixcoin-and-i0coin", "title": "Ixcoin and I0coin", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: the Ixcoin and I0coin pair is the 2011 template for every fork argument that followed — a premined copy, then a 'fair' copy of the copy within a week. [ixc-ann] [i0c-thread]", "aliases": "ixcoin ixc i0coin premine", "refs": ["i0c-thread", "ixc-ann"], "url": "/wiki/ixcoin-and-i0coin/"}, {"id": "ixcoin-and-i0coin#668", "slug": "ixcoin-and-i0coin", "title": "Ixcoin and I0coin", "section": "Ixcoin", "text": "Nasakioto's PGP-signed announcement of 10 August 2011 said “Ixcoin is a fork of Bitcoin with twice the inflation rate of 96 Ixcoins per block and the same 21 million total limit” [ixc-ann]. It used a new genesis block, so “Bitcoins will not be valid in the Ixcoin blockchain and vice-versa”, moved the ports to 8337 and 8338, and said there were “~580K Ixcoins (as of 10th August 2011) in existence” [ixc-ann]. The Litecoin Wiki's history table describes Ixcoin as “Higher block reward, premined” [ltcwiki-history].", "aliases": "ixcoin ixc i0coin premine", "refs": ["ixc-ann", "ltcwiki-history"], "url": "/wiki/ixcoin-and-i0coin/"}, {"id": "ixcoin-and-i0coin#669", "slug": "ixcoin-and-i0coin", "title": "Ixcoin and I0coin", "section": "I0coin", "text": "On 11 August 2011 BitcoinBug proposed “I0coin (= Ixcoin with 0 pregenerated blocks)”, predicting that people “would jump from Ixcoin in notime” [i0c-thread]. The Litecoin Wiki dates I0coin to 16 August 2011 by kr105, described as “Ixcoin without premine” [ltcwiki-history].", "aliases": "ixcoin ixc i0coin premine", "refs": ["i0c-thread", "ltcwiki-history"], "url": "/wiki/ixcoin-and-i0coin/"}, {"id": "ixcoin-and-i0coin#670", "slug": "ixcoin-and-i0coin", "title": "Ixcoin and I0coin", "section": "Later", "text": "The current IXCoin Core README describes Ixcoin as “merged mined with Bitcoin”, the same route Namecoin uses [ixc-readme]. When Ixcoin adopted merged mining is not yet sourced in this wiki [ixc-readme].", "aliases": "ixcoin ixc i0coin premine", "refs": ["ixc-readme"], "url": "/wiki/ixcoin-and-i0coin/"}, {"id": "james-hilliard#infobox", "slug": "james-hilliard", "title": "James Hilliard", "section": "Summary and infobox", "text": "Author of BIP-91, the reduced-threshold SegWit activation that locked in in July 2017. Known for: BIP-91 (Reduced threshold Segwit MASF) [bip91]; BIP-91 lock-in: 21 Jul 2017 [btk-forkwars]; Hong Kong, Feb 2016: A “James Hilliard” signed as “Pool/Farm Admin” (same person not confirmed) [hk-letter]; GitHub: jameshilliard, since January 2013 [gh-hilliard]", "aliases": "hilliard bip91", "refs": ["bip91", "btk-forkwars", "gh-hilliard", "hk-letter"], "url": "/wiki/james-hilliard/"}, {"id": "james-hilliard#takeover", "slug": "james-hilliard", "title": "James Hilliard", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Hilliard wrote the compromise that let miners avoid the UASF chain split in 2017; the Fork Wars timeline lists him among the key actors of SegWit activation. [btk-forkwars]", "aliases": "hilliard bip91", "refs": ["btk-forkwars"], "url": "/wiki/james-hilliard/"}, {"id": "james-hilliard#673", "slug": "james-hilliard", "title": "James Hilliard", "section": "BIP-91", "text": "BIP-91, “Reduced threshold Segwit MASF”, lists James Hilliard as its author [bip91] [bips-list]. Bitcoin Takeover's Fork Wars timeline calls it “A miner-friendly compromise” that used a lower threshold, 269 of 336 blocks, and says it locked in on 21 July 2017 and activated on 26 July [btk-forkwars]. See BIP-91.", "aliases": "hilliard bip91", "refs": ["bip91", "bips-list", "btk-forkwars"], "url": "/wiki/james-hilliard/"}, {"id": "james-hilliard#674", "slug": "james-hilliard", "title": "James Hilliard", "section": "Hong Kong and GitHub", "text": "The February 2016 Hong Kong Roundtable statement lists a James Hilliard as “Pool/Farm Admin” at BitmainWarranty [hk-letter]. This wiki has not confirmed that the signer and the BIP-91 author are the same person [hk-letter]. His GitHub account, jameshilliard, dates from January 2013 [gh-hilliard].", "aliases": "hilliard bip91", "refs": ["gh-hilliard", "hk-letter"], "url": "/wiki/james-hilliard/"}, {"id": "jameson-lopp#infobox", "slug": "jameson-lopp", "title": "Jameson Lopp", "section": "Summary and infobox", "text": "Co-founder and Chief Security Officer of Casa, writer of Cypherpunk Cogitations, and a speaker at events across the fork divide. Role: Casa Co-founder & Chief Security Officer [lopp-site]; Self-description: “Cypherpunk” [lopp-gh]; Publication: Cypherpunk Cogitations (launched Aug 2024) [lopp-blog]; GitHub: jlopp, since May 2010 [lopp-gh]; Proof of Work Summit: Spoke both years (per Bob Summerwill) [ep-s17e42-lopp]", "aliases": "lopp casa", "refs": ["ep-s17e42-lopp", "lopp-blog", "lopp-gh", "lopp-site"], "url": "/wiki/jameson-lopp/"}, {"id": "jameson-lopp#takeover", "slug": "jameson-lopp", "title": "Jameson Lopp", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Lopp shows up in this wiki in rooms where small blockers are rarely seen — an Ethereum Classic summit and, by Kurt Wuckert's account, a stage next to Craig Wright. [ep-s17e42-lopp] [ep-s17e39-lopp]", "aliases": "lopp casa", "refs": ["ep-s17e39-lopp", "ep-s17e42-lopp"], "url": "/wiki/jameson-lopp/"}, {"id": "jameson-lopp#677", "slug": "jameson-lopp", "title": "Jameson Lopp", "section": "Work", "text": "Lopp's site lists him as “Casa Co-founder & Chief Security Officer”, an angel investor and an adviser to CCSS and AnchorWatch [lopp-site]. His GitHub account, jlopp, dates from May 2010 and gives his company as Casa [lopp-gh]. Cypherpunk Cogitations describes itself as “an independent publication launched in August 2024 by Jameson Lopp” [lopp-blog].", "aliases": "lopp casa", "refs": ["lopp-blog", "lopp-gh", "lopp-site"], "url": "/wiki/jameson-lopp/"}, {"id": "jameson-lopp#678", "slug": "jameson-lopp", "title": "Jameson Lopp", "section": "On the show", "text": "Bob Summerwill said on Bitcoin Takeover that “Jameson Lopp spoke both times” at the Proof of Work Summit he organised [ep-s17e42-lopp]. Kurt Wuckert Jr. recalled that Lopp appeared at an event right before or after Craig Wright and said, in Kurt's paraphrase, that he did not know whether Wright was Satoshi [ep-s17e39-lopp]. Charlie Spears said Lopp gave a dynamic block size increase talk at an OP_NEXT event [ep-s17e13-opnext].", "aliases": "lopp casa", "refs": ["ep-s17e13-opnext", "ep-s17e39-lopp", "ep-s17e42-lopp"], "url": "/wiki/jameson-lopp/"}, {"id": "jeff-garzik#infobox", "slug": "jeff-garzik", "title": "Jeff Garzik", "section": "Summary and infobox", "text": "Early Bitcoin Core contributor who proposed a bigger block in 2010 and later led the engineering of SegWit2x. Role: Bitcoin Core contributor up to 2015; co-founder of Bloq [garzik-bw]; 2010: “[PATCH] increase block size limit”, 3 October 2010 [garzik-patch]; Proposals: BIP-100 (miner vote) and BIP-102 (2 MB) [bip100]; SegWit2x: Technical lead of btc1; co-signed the 8 Nov 2017 suspension [s2x-suspend]", "aliases": "garzik jgarzik", "refs": ["bip100", "garzik-bw", "garzik-patch", "s2x-suspend"], "url": "/wiki/jeff-garzik/"}, {"id": "jeff-garzik#takeover", "slug": "jeff-garzik", "title": "Jeff Garzik", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Garzik appears at both ends of the war in Fork Wars, from the 2010 patch Satoshi answered to the 2017 letter that ended SegWit2x. [btk-forkwars] [s2x-suspend]", "aliases": "garzik jgarzik", "refs": ["btk-forkwars", "s2x-suspend"], "url": "/wiki/jeff-garzik/"}, {"id": "jeff-garzik#681", "slug": "jeff-garzik", "title": "Jeff Garzik", "section": "The 2010 patch", "text": "On 3 October 2010 Garzik posted a patch to raise the block size limit, arguing “We should be able to at least match Paypal's average transaction rate” [garzik-patch]. Satoshi Nakamoto replied in the same thread, an exchange the Fork Wars timeline treats as its own phase [satoshi-15139] [btk-forkwars].", "aliases": "garzik jgarzik", "refs": ["btk-forkwars", "garzik-patch", "satoshi-15139"], "url": "/wiki/jeff-garzik/"}, {"id": "jeff-garzik#682", "slug": "jeff-garzik", "title": "Jeff Garzik", "section": "Proposals", "text": "Garzik authored BIP-100, a dynamic block size limit set by miner vote, and BIP-102, a one-time increase to 2 MB [bip100] [bip102].", "aliases": "garzik jgarzik", "refs": ["bip100", "bip102"], "url": "/wiki/jeff-garzik/"}, {"id": "jeff-garzik#683", "slug": "jeff-garzik", "title": "Jeff Garzik", "section": "SegWit2x", "text": "Fork Wars lists Garzik as technical lead of btc1, the SegWit2x client [btk-forkwars]. He was one of six signatories of the 8 November 2017 message suspending the 2 MB upgrade [s2x-suspend].", "aliases": "garzik jgarzik", "refs": ["btk-forkwars", "s2x-suspend"], "url": "/wiki/jeff-garzik/"}, {"id": "jeff-garzik#684", "slug": "jeff-garzik", "title": "Jeff Garzik", "section": "Other", "text": "In 2016 Garzik said the evidence Craig Wright had publicly provided did not prove anything [wp-wright]. The Bitcoin Wiki lists him as co-founder of Bloq [garzik-bw].", "aliases": "garzik jgarzik", "refs": ["garzik-bw", "wp-wright"], "url": "/wiki/jeff-garzik/"}, {"id": "jeremy-rubin#infobox", "slug": "jeremy-rubin", "title": "Jeremy Rubin", "section": "Summary and infobox", "text": "Author of BIP-119 (CHECKTEMPLATEVERIFY), co-founder of the MIT Digital Currency Initiative and Scaling Bitcoin, creator of Sapio and Judica, now building Char. Known for: BIP-119, OP_CHECKTEMPLATEVERIFY [bip119]; BIP-119 assigned: 2020-01-06 [bip119]; Co-founded: MIT Digital Currency Initiative; Scaling Bitcoin [rubin-site]; Projects: Sapio, Judica, pleb.fi [rubin-site]; Now: “Building Char Network, a decentralized shared sequencer for Bitcoin Layer 2s” [rubin-site]; On the show: S17 E22 (May 2026) [btk-feed]", "aliases": "jeremy rubin ctv sapio char", "refs": ["bip119", "btk-feed", "rubin-site"], "url": "/wiki/jeremy-rubin/"}, {"id": "jeremy-rubin#takeover", "slug": "jeremy-rubin", "title": "Jeremy Rubin", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: on S17 E22 Rubin described Char, his decentralized sequencer for layer twos; on S17 E38 Vlad recalled his 2022 Speedy Trial attempt for CTV. [ep-s17e22-char] [ep-s17e38-ctv]", "aliases": "jeremy rubin ctv sapio char", "refs": ["ep-s17e22-char", "ep-s17e38-ctv"], "url": "/wiki/jeremy-rubin/"}, {"id": "jeremy-rubin#687", "slug": "jeremy-rubin", "title": "Jeremy Rubin", "section": "CTV", "text": "Rubin is the sole listed author of BIP-119, which “proposes a new opcode, OP_CHECKTEMPLATEVERIFY, to be activated as a change to the semantics of OP_NOP4” [bip119]. On S17 E22 Vlad noted that CTV “used to be called Secure the Bag at some point” [ep-s17e22-stb]. In April 2022 Rubin published “7 Theses on a next step for BIP-119” on his site [rubin-2022], and Optech covered the resulting discussion about activating CTV [optech-197]. See the CTV covenant debates [optech-ctv].", "aliases": "jeremy rubin ctv sapio char", "refs": ["bip119", "ep-s17e22-stb", "optech-197", "optech-ctv", "rubin-2022"], "url": "/wiki/jeremy-rubin/"}, {"id": "jeremy-rubin#688", "slug": "jeremy-rubin", "title": "Jeremy Rubin", "section": "Background and projects", "text": "His site lists “Co-Founded the MIT Digital Currency Initiative” and “Co-Founded Scaling Bitcoin”, an MIT '16 MEng in EECS, and the MIT Bitcoin Project that gave every MIT undergraduate $100 of bitcoin [rubin-site]. It lists Sapio and Judica among his projects [rubin-site]. Keagan McClelland said he left Start9 to join Judica “to work with Jeremy on Sapio” [ep-s17e38-judica].", "aliases": "jeremy rubin ctv sapio char", "refs": ["ep-s17e38-judica", "rubin-site"], "url": "/wiki/jeremy-rubin/"}, {"id": "jeremy-rubin#689", "slug": "jeremy-rubin", "title": "Jeremy Rubin", "section": "Char", "text": "His site says he is “Building Char Network, a decentralized shared sequencer for Bitcoin Layer 2s” [rubin-site]. On S17 E22 he said: “I'm working on Char, which is a decentralized staking and sequencer for Bitcoin, for Bitcoin layer twos” [ep-s17e22-char].", "aliases": "jeremy rubin ctv sapio char", "refs": ["ep-s17e22-char", "rubin-site"], "url": "/wiki/jeremy-rubin/"}, {"id": "jihan-wu#infobox", "slug": "jihan-wu", "title": "Jihan Wu", "section": "Summary and infobox", "text": "Co-founder of Bitmain, a signer of the 2016 Hong Kong Roundtable statement whose company backed the 2017 New York Agreement, and a leading backer of Bitcoin Cash. Born: 1986, Chongqing [wp-jihan]; Company: Co-founded Bitmain with Micree Zhan in 2013 [wp-jihan]; Hong Kong Roundtable: Signed as Co-CEO, Bitmain [hk-letter]; SegWit2x: Co-signed the 8 Nov 2017 suspension [s2x-suspend]; 2018 split: Backed the Bitcoin ABC side with Roger Ver [wp-bsv]; Later: Founded Matrixport (2019); chairman of Bitdeer after leaving Bitmain (2021) [wp-jihan]", "aliases": "jihan bitmain", "refs": ["hk-letter", "s2x-suspend", "wp-bsv", "wp-jihan"], "url": "/wiki/jihan-wu/"}, {"id": "jihan-wu#takeover", "slug": "jihan-wu", "title": "Jihan Wu", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: the most powerful miner in the war, present at every negotiating table that Fork Wars tracks: Hong Kong, New York and the 2x suspension. [btk-forkwars] [hk-letter] [s2x-suspend]", "aliases": "jihan bitmain", "refs": ["btk-forkwars", "hk-letter", "s2x-suspend"], "url": "/wiki/jihan-wu/"}, {"id": "jihan-wu#692", "slug": "jihan-wu", "title": "Jihan Wu", "section": "Early years", "text": "Wu was born in 1986 in Chongqing and earned degrees in economics and psychology from Peking University in 2009 [wp-jihan]. In late 2011 he was the first to translate Satoshi Nakamoto's white paper into Chinese [wp-jihan].", "aliases": "jihan bitmain", "refs": ["wp-jihan"], "url": "/wiki/jihan-wu/"}, {"id": "jihan-wu#693", "slug": "jihan-wu", "title": "Jihan Wu", "section": "Bitmain", "text": "In 2013 he persuaded engineer Micree Zhan to co-found Bitmain, whose first rig, the Antminer S1, appeared in November 2013 [wp-jihan]. He signed the February 2016 Hong Kong Roundtable statement as Bitmain's Co-CEO, and Bitmain appears on the May 2017 New York Agreement supporter list [hk-letter] [nya-letter].", "aliases": "jihan bitmain", "refs": ["hk-letter", "nya-letter", "wp-jihan"], "url": "/wiki/jihan-wu/"}, {"id": "jihan-wu#694", "slug": "jihan-wu", "title": "Jihan Wu", "section": "Bitcoin Cash", "text": "Wu was a vocal supporter of larger blocks, and critics accused him of masterminding the Bitcoin Cash fork, which he denied [wp-jihan]. In November 2018 he and Roger Ver backed the Bitcoin ABC side against Bitcoin SV [wp-bsv]. He co-signed the November 2017 message that suspended SegWit2x [s2x-suspend].", "aliases": "jihan bitmain", "refs": ["s2x-suspend", "wp-bsv", "wp-jihan"], "url": "/wiki/jihan-wu/"}, {"id": "jihan-wu#695", "slug": "jihan-wu", "title": "Jihan Wu", "section": "Later", "text": "He stepped down as co-CEO of Bitmain in 2019 and founded Matrixport; in 2021 he left Bitmain, with Bitdeer spun off under his chairmanship [wp-jihan].", "aliases": "jihan bitmain", "refs": ["wp-jihan"], "url": "/wiki/jihan-wu/"}, {"id": "johnson-lau#infobox", "slug": "johnson-lau", "title": "Johnson Lau", "section": "Summary and infobox", "text": "Co-author of SegWit's BIP-141 and BIP-143, author of several other SegWit-era BIPs, and a 2016 Hong Kong Roundtable signer. GitHub: jl2012, since August 2014 [gh-jl2012]; SegWit BIPs: 141 (with Lombrozo, Wuille), 143 (with Wuille) [bips-list]; Other BIPs: 114, 142, 146, 147 [bips-list]; Hong Kong, Feb 2016: Signed as “Bitcoin Core Contributor” [hk-letter]", "aliases": "jl2012 lau", "refs": ["bips-list", "gh-jl2012", "hk-letter"], "url": "/wiki/johnson-lau/"}, {"id": "johnson-lau#takeover", "slug": "johnson-lau", "title": "Johnson Lau", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Lau co-wrote the SegWit specification that the 2017 forks fought over, and was one of five Core contributors at the Hong Kong table. [btk-forkwars] [bips-list]", "aliases": "jl2012 lau", "refs": ["bips-list", "btk-forkwars"], "url": "/wiki/johnson-lau/"}, {"id": "johnson-lau#698", "slug": "johnson-lau", "title": "Johnson Lau", "section": "BIPs", "text": "The BIP index lists Johnson Lau as a co-author of BIP-141, “Segregated Witness (Consensus layer)”, with Eric Lombrozo and Pieter Wuille, and of BIP-143 with Pieter Wuille [bips-list]. It also lists him on BIP-114 (“Merkelized Abstract Syntax Tree”), 142, 146 and 147 [bips-list]. See Segregated Witness.", "aliases": "jl2012 lau", "refs": ["bips-list"], "url": "/wiki/johnson-lau/"}, {"id": "johnson-lau#699", "slug": "johnson-lau", "title": "Johnson Lau", "section": "Hong Kong and GitHub", "text": "He signed the February 2016 Hong Kong Roundtable statement as a “Bitcoin Core Contributor” [hk-letter] [btk-forkwars]. His GitHub account, jl2012, dates from August 2014 [gh-jl2012].", "aliases": "jl2012 lau", "refs": ["btk-forkwars", "gh-jl2012", "hk-letter"], "url": "/wiki/johnson-lau/"}, {"id": "jonathan-bier#infobox", "slug": "jonathan-bier", "title": "Jonathan Bier", "section": "Summary and infobox", "text": "The man behind BitMEX Research and author of The Blocksize War (2021), the standard small-block-side history of the war. Known for: BitMEX Research; The Blocksize War [ep-s16e60-intro]; The Blocksize War: Published 15 March 2021 [farside-book]; Covers: Mid-2015 to late 2017 [farside-book]; Other book: Reckless (history of crypto interest rates) [ep-s16e60-reckless]; Takeover appearance: S16 E60 (November 2025) [ep-s16e60-intro]", "aliases": "bier bitmex research blocksize war book reckless", "refs": ["ep-s16e60-intro", "ep-s16e60-reckless", "farside-book"], "url": "/wiki/jonathan-bier/"}, {"id": "jonathan-bier#takeover", "slug": "jonathan-bier", "title": "Jonathan Bier", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bier is the war's most-cited chronicler, and on S16 E60 he was candid that he was a participant, not a neutral observer, who went to Hong Kong in 2015 specifically to rebut Peter Rizun. [ep-s16e60-rizun]", "aliases": "bier bitmex research blocksize war book reckless", "refs": ["ep-s16e60-rizun"], "url": "/wiki/jonathan-bier/"}, {"id": "jonathan-bier#702", "slug": "jonathan-bier", "title": "Jonathan Bier", "section": "BitMEX Research", "text": "Vlad introduced Bier on S16 E60 as “the man behind the BitMEX Research account” and author of The Blocksize War [ep-s16e60-intro]. Bier said that instead of writing anonymously on Bitcointalk he began writing professionally for BitMEX's blog [ep-s16e60-bitmex].", "aliases": "bier bitmex research blocksize war book reckless", "refs": ["ep-s16e60-bitmex", "ep-s16e60-intro"], "url": "/wiki/jonathan-bier/"}, {"id": "jonathan-bier#703", "slug": "jonathan-bier", "title": "Jonathan Bier", "section": "The Blocksize War", "text": "Farside's announcement of 15 March 2021 calls it “a new book by BitMEX Research” covering the war “from mid 2015 to late 2017” [farside-book]. On the show Bier also discussed his other book, Reckless, a history of cryptocurrency interest rates [ep-s16e60-reckless].", "aliases": "bier bitmex research blocksize war book reckless", "refs": ["ep-s16e60-reckless", "farside-book"], "url": "/wiki/jonathan-bier/"}, {"id": "jonathan-bier#704", "slug": "jonathan-bier", "title": "Jonathan Bier", "section": "Hong Kong, 2015", "text": "Bier said that after seeing Peter Rizun's presentation he wrote to the organisers and gave a reply presentation at the next conference in the series in Hong Kong, “trying to refute some of the points” [ep-s16e60-rizun].", "aliases": "bier bitmex research blocksize war book reckless", "refs": ["ep-s16e60-rizun"], "url": "/wiki/jonathan-bier/"}, {"id": "jonathan-bier#705", "slug": "jonathan-bier", "title": "Jonathan Bier", "section": "On forks and Wright", "text": "On S16 E60 Bier recalled that after the SegWit2x cancellation Bitcoin Cash briefly reached about 51% of Bitcoin's price [ep-s16e60-2x]. He also discussed Craig Wright's effect on the big-block side [ep-s16e60-wright].", "aliases": "bier bitmex research blocksize war book reckless", "refs": ["ep-s16e60-2x", "ep-s16e60-wright"], "url": "/wiki/jonathan-bier/"}, {"id": "judica#infobox", "slug": "judica", "title": "Judica", "section": "Summary and infobox", "text": "Jeremy Rubin's company for building DAOs and contracts on Bitcoin with the Sapio language, where Keagan McClelland worked. Pitch: “building DAOs and other decentralized applications on bitcoin” [judica-site]; Language: Sapio [rubin-site]; Copyright line: © Judica, Inc 2022 [judica-site]; Staff (on the show): Keagan McClelland, with Jeremy Rubin [ep-s17e38-judica]", "aliases": "judica sapio", "refs": ["ep-s17e38-judica", "judica-site", "rubin-site"], "url": "/wiki/judica/"}, {"id": "judica#takeover", "slug": "judica", "title": "Judica", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Judica is where the CTV story became a company — Rubin's Sapio work, which drew Keagan McClelland away from Start9. [ep-s17e38-judica] [rubin-site]", "aliases": "judica sapio", "refs": ["ep-s17e38-judica", "rubin-site"], "url": "/wiki/judica/"}, {"id": "judica#708", "slug": "judica", "title": "Judica", "section": "Company", "text": "The judica.org homepage says “judica is your partner in building DAOs and other decentralized applications on bitcoin” and offers “an open source platform and utility apis” [judica-site]. Its latest listed posts include “The History and Future of Sapio” of 23 December 2021 and a post of 4 November 2022, and the footer reads “© Judica, Inc 2022” [judica-site]. Whether it is still active is unknown to this wiki [judica-site].", "aliases": "judica sapio", "refs": ["judica-site"], "url": "/wiki/judica/"}, {"id": "judica#709", "slug": "judica", "title": "Judica", "section": "People", "text": "Jeremy Rubin's site lists Sapio and Judica among his projects [rubin-site]. On S17 E38 Keagan McClelland said he left Start9 “joining Judica to work with Jeremy on Sapio” [ep-s17e38-judica].", "aliases": "judica sapio", "refs": ["ep-s17e38-judica", "rubin-site"], "url": "/wiki/judica/"}, {"id": "keagan-mcclelland#infobox", "slug": "keagan-mcclelland", "title": "Keagan McClelland", "section": "Summary and infobox", "text": "Start9 co-founder who left to work on Sapio at Judica, later worked at Lightning Labs, and now verifies Bitcoin consensus code in Lean. GitHub: ProofOfKeags [gh-keags]; Location (GitHub): Denver, CO [gh-keags]; Start9: Co-founder (as introduced on S17 E38) [ep-s17e38-intro]; Judica: Joined to work on Sapio [ep-s17e38-judica]; Now (GitHub bio): Verifying Bitcoin's consensus components in Lean [gh-keags]", "aliases": "keagan keags mcclelland proofofkeags", "refs": ["ep-s17e38-intro", "ep-s17e38-judica", "gh-keags"], "url": "/wiki/keagan-mcclelland/"}, {"id": "keagan-mcclelland#takeover", "slug": "keagan-mcclelland", "title": "Keagan McClelland", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: S17 E38 traced McClelland's path from Salt to Start9, Judica and Lightning Labs, as introduced by Vlad. [ep-s17e38-intro] [ep-s17e38-start9]", "aliases": "keagan keags mcclelland proofofkeags", "refs": ["ep-s17e38-intro", "ep-s17e38-start9"], "url": "/wiki/keagan-mcclelland/"}, {"id": "keagan-mcclelland#712", "slug": "keagan-mcclelland", "title": "Keagan McClelland", "section": "Start9 and Judica", "text": "Introducing S17 E38, Vlad called him a developer who “has worked for Lightning Labs” and “a co-founder of Start9 Labs” [ep-s17e38-intro]. McClelland said that in 2019 core engineers left Salt Lending and “Start9 is what came out of that” [ep-s17e38-start9]. He later “ended up leaving and joining Judica to work with Jeremy on Sapio” [ep-s17e38-judica]. He said he had met Jeremy Rubin in the summer of 2019 [ep-s17e38-judica].", "aliases": "keagan keags mcclelland proofofkeags", "refs": ["ep-s17e38-intro", "ep-s17e38-judica", "ep-s17e38-start9"], "url": "/wiki/keagan-mcclelland/"}, {"id": "keagan-mcclelland#713", "slug": "keagan-mcclelland", "title": "Keagan McClelland", "section": "CTV and now", "text": "On the same episode he recalled that CTV used to be called OP_SECURE_THE_BAG [ep-s17e38-stb]. His GitHub bio reads “Building machine-checked cryptographic protocol infrastructure” and says he is “Currently verifying Bitcoin's consensus components in Lean” [gh-keags].", "aliases": "keagan keags mcclelland proofofkeags", "refs": ["ep-s17e38-stb", "gh-keags"], "url": "/wiki/keagan-mcclelland/"}, {"id": "kevin-pan#infobox", "slug": "kevin-pan", "title": "Kevin Pan", "section": "Summary and infobox", "text": "Signed the 2016 Hong Kong Roundtable statement as AntPool's manager; a Kevin Pan (Zhibiao Pan) later founded the Poolin mining pool. Hong Kong, Feb 2016: Signed as Kevin Pan, Manager, AntPool [hk-letter]; Poolin (2019 interview): CEO Zhibiao Pan, answers labelled Kevin Pan [bm-poolin]; Earlier (per interview): TangPool (2014), Bitmain, BTC.com [bm-poolin]; Same person?: Not confirmed by one source [bm-poolin]", "aliases": "kevin pan zhibiao poolin", "refs": ["bm-poolin", "hk-letter"], "url": "/wiki/kevin-pan/"}, {"id": "kevin-pan#takeover", "slug": "kevin-pan", "title": "Kevin Pan", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: the name sits at both ends of a Bitmain story — an AntPool signature in Hong Kong, then a rival pool after leaving Bitmain — but the link is not confirmed here. [hk-letter] [bm-poolin]", "aliases": "kevin pan zhibiao poolin", "refs": ["bm-poolin", "hk-letter"], "url": "/wiki/kevin-pan/"}, {"id": "kevin-pan#716", "slug": "kevin-pan", "title": "Kevin Pan", "section": "Hong Kong Roundtable", "text": "The February 2016 Bitcoin Roundtable statement lists Kevin Pan, Manager, AntPool first among its signers [hk-letter].", "aliases": "kevin pan zhibiao poolin", "refs": ["hk-letter"], "url": "/wiki/kevin-pan/"}, {"id": "kevin-pan#717", "slug": "kevin-pan", "title": "Kevin Pan", "section": "Poolin", "text": "A 2019 Bitcoin Magazine interview says “CEO Zhibiao Pan started in the mining industry as the founder of TangPool in 2014 before joining Bitmain and later running BTC.com there” [bm-poolin]. It says “He left the company in 2017 amid the hard fork drama” and founded Poolin with former BTC.com employees [bm-poolin]. The interview's answers are labelled Kevin Pan, who said “Personally, I think the current status and power enjoyed by mining pools is a little too much” [bm-poolin].", "aliases": "kevin pan zhibiao poolin", "refs": ["bm-poolin"], "url": "/wiki/kevin-pan/"}, {"id": "kevin-pan#718", "slug": "kevin-pan", "title": "Kevin Pan", "section": "Identity", "text": "The interview does not mention AntPool or the Hong Kong statement, so this wiki does not confirm that the Hong Kong signer and Poolin's CEO are the same person [bm-poolin] [hk-letter].", "aliases": "kevin pan zhibiao poolin", "refs": ["bm-poolin", "hk-letter"], "url": "/wiki/kevin-pan/"}, {"id": "kurt-wuckert-jr#infobox", "slug": "kurt-wuckert-jr", "title": "Kurt Wuckert Jr.", "section": "Summary and infobox", "text": "Self-described Bitcoin historian on the BSV side, CoinGeek author and GorillaPool operator, interviewed on Bitcoin Takeover S17 E39. Bitcoiner since: 2012 [ep-s17e39-intro]; Writing: CoinGeek author [coingeek-about]; Mining: GorillaPool (SHA-256) [ep-s17e39-coingeek]; Earlier: Hosted the Bitcoin Cash meetup in Chicago [ep-s17e39-chicago]; Oslo trial (2022): Covered for CoinGeek with press credentials (his account) [ep-s17e39-oslo]", "aliases": "kurt wuckert gorillapool", "refs": ["coingeek-about", "ep-s17e39-chicago", "ep-s17e39-coingeek", "ep-s17e39-intro", "ep-s17e39-oslo"], "url": "/wiki/kurt-wuckert-jr/"}, {"id": "kurt-wuckert-jr#takeover", "slug": "kurt-wuckert-jr", "title": "Kurt Wuckert Jr.", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Kurt took the BSV branch in 2018 and still argues it on the record, and his account of an OP_RETURN prototype breaking around 2014 links the old data-carrier fight to the 2025 one. [btk-blake] [ep-s17e39-coingeek]", "aliases": "kurt wuckert gorillapool", "refs": ["btk-blake", "ep-s17e39-coingeek"], "url": "/wiki/kurt-wuckert-jr/"}, {"id": "kurt-wuckert-jr#721", "slug": "kurt-wuckert-jr", "title": "Kurt Wuckert Jr.", "section": "Background", "text": "Introducing Kurt Wuckert Jr. on S17 E39, Vlad described him as possibly one of the first people to call themselves a Bitcoin historian, who ran a print shop in Chicago and was offered payment in Bitcoin in 2012 [ep-s17e39-intro]. Kurt said he had hosted a Bitcoin.com-sponsored Bitcoin Cash meetup in Chicago [ep-s17e39-chicago]. He said he was “officially representing CoinGeek” at the 2022 Oslo trial between Hodlonaut and Craig Wright [ep-s17e39-oslo]. CoinGeek's team page lists him as an author [coingeek-about].", "aliases": "kurt wuckert gorillapool", "refs": ["coingeek-about", "ep-s17e39-chicago", "ep-s17e39-intro", "ep-s17e39-oslo"], "url": "/wiki/kurt-wuckert-jr/"}, {"id": "kurt-wuckert-jr#722", "slug": "kurt-wuckert-jr", "title": "Kurt Wuckert Jr.", "section": "BSV and GorillaPool", "text": "Vlad introduced him as “a journalist for CoinGeek” running Gorilla Pool, “a mining pool for SHA-256” [ep-s17e39-coingeek]. Kurt described GorillaPool as “completely independent”, funded by him and two partners to mine for about five years [ep-s17e39-gorilla]. His accounts of the 2018 split are covered in the hash war and Bitcoin SV [ep-s17e39-hashwar].", "aliases": "kurt wuckert gorillapool", "refs": ["ep-s17e39-coingeek", "ep-s17e39-gorilla", "ep-s17e39-hashwar"], "url": "/wiki/kurt-wuckert-jr/"}, {"id": "kurt-wuckert-jr#723", "slug": "kurt-wuckert-jr", "title": "Kurt Wuckert Jr.", "section": "Data carrier", "text": "The Takeover BLAKE2b feature records Kurt saying that around 2014 his OP_RETURN tokenization prototype stopped working when Core cut the data carrier size [btk-blake]. That connects him to the 2025 OP_RETURN fight [btk-blake].", "aliases": "kurt wuckert gorillapool", "refs": ["btk-blake"], "url": "/wiki/kurt-wuckert-jr/"}, {"id": "layertwo-labs#infobox", "slug": "layertwo-labs", "title": "LayerTwo Labs", "section": "Summary and infobox", "text": "Paul Sztorc's company building drivechains and the eCash (ECX) fork. CEO: Paul Sztorc [ep-s17e37-launch]; Seed round: $3M (reported December 2022) [l2l-seed]; Product: Drivechain software; eCash (ECX) [btk-ecx]; Relationship to the show: Sponsor of Bitcoin Takeover [ep-s17e19-sponsors]", "aliases": "", "refs": ["btk-ecx", "ep-s17e19-sponsors", "ep-s17e37-launch", "l2l-seed"], "url": "/wiki/layertwo-labs/"}, {"id": "layertwo-labs#takeover", "slug": "layertwo-labs", "title": "LayerTwo Labs", "section": "Takeover view (editorial opinion)", "text": "Sponsor disclosure lives on the article, not in a footnote nobody reads. [ep-s17e19-sponsors]", "aliases": "", "refs": ["ep-s17e19-sponsors"], "url": "/wiki/layertwo-labs/"}, {"id": "layertwo-labs#726", "slug": "layertwo-labs", "title": "LayerTwo Labs", "section": "Overview", "text": "LayerTwo Labs is led by Paul Sztorc [ep-s17e37-launch]. CoinDesk reported in December 2022 that it had raised $3 million to bring drivechains to Bitcoin [l2l-seed]. It developed the eCash (ECX) fork [btk-ecx]. LayerTwo Labs is a sponsor of Bitcoin Takeover [ep-s17e19-sponsors].", "aliases": "", "refs": ["btk-ecx", "ep-s17e19-sponsors", "ep-s17e37-launch", "l2l-seed"], "url": "/wiki/layertwo-labs/"}, {"id": "lightning-bitcoin#infobox", "slug": "lightning-bitcoin", "title": "Lightning Bitcoin (LBTC)", "section": "Summary and infobox", "text": "A December 2017 fork at block 499,999 that replaced proof of work with delegated proof of stake, unrelated to the Lightning Network despite the name. Type: Hard fork that replaces PoW with DPoS [lbtc-readme]; Fork height: 499,999 (18 Dec 2017) [lbtc-about]; Block 499,999 time: 2017-12-18 18:34:47 UTC [btc-499999]; Ratio: 1:1 to BTC holders at block 499,999 [lbtc-ann]; Block size: 2 MB [lbtc-ann]; Mainnet: 4 Feb 2018, per the project timeline [lbtc-about]; Not to be confused with: The Lightning Network [lbtc-readme]", "aliases": "lbtc dpos", "refs": ["btc-499999", "lbtc-about", "lbtc-ann", "lbtc-readme"], "url": "/wiki/lightning-bitcoin/"}, {"id": "lightning-bitcoin#takeover", "slug": "lightning-bitcoin", "title": "Lightning Bitcoin (LBTC)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: LBTC is a naming hazard. It borrowed the word “Lightning” from Bitcoin's payment-channel network while changing Bitcoin's consensus to delegated proof of stake. It has no stated connection to the Lightning Network found in its README or ANN thread. [lbtc-readme] [lbtc-ann]", "aliases": "lbtc dpos", "refs": ["lbtc-ann", "lbtc-readme"], "url": "/wiki/lightning-bitcoin/"}, {"id": "lightning-bitcoin#729", "slug": "lightning-bitcoin", "title": "Lightning Bitcoin (LBTC)", "section": "Design", "text": "The README says Lightning Bitcoin is forked from Bitcoin Core and that its full node “replaces PoW consensus of Bitcoin with DPoS”, adding replay protection and register, vote and cancel-vote transactions [lbtc-readme]. The README says holders vote on improvement proposals and on the delegates who maintain the network as “Lightning Nodes” [lbtc-readme]. The ANN thread describes 2 MB blocks [lbtc-ann].", "aliases": "lbtc dpos", "refs": ["lbtc-ann", "lbtc-readme"], "url": "/wiki/lightning-bitcoin/"}, {"id": "lightning-bitcoin#730", "slug": "lightning-bitcoin", "title": "Lightning Bitcoin (LBTC)", "section": "Fork and launch", "text": "The ANN thread says Bitcoin holders could claim LBTC 1:1 if they held BTC at block 499,999 on 18 December 2017 [lbtc-ann]. That block's header time is 18:34:47 UTC on 18 December 2017 [btc-499999]. The project's own timeline lists the fork on 18 December 2017 and the mainnet launch on 4 February 2018 [lbtc-about].", "aliases": "lbtc dpos", "refs": ["btc-499999", "lbtc-about", "lbtc-ann"], "url": "/wiki/lightning-bitcoin/"}, {"id": "lightning-bitcoin#731", "slug": "lightning-bitcoin", "title": "Lightning Bitcoin (LBTC)", "section": "Inactive coins", "text": "The ANN thread says there was no premine, but that coins belonging to addresses inactive since 31 January 2013 were taken for “ecological construction” and managed by the LBTC foundation, with an offer to return them on request [lbtc-ann]. The project's timeline says a governance vote in September 2018 approved removing pre-fork data, followed by a remapping in October 2018 [lbtc-about]. Whether the chain still runs is unknown in this wiki [lbtc-about].", "aliases": "lbtc dpos", "refs": ["lbtc-about", "lbtc-ann"], "url": "/wiki/lightning-bitcoin/"}, {"id": "litecoin#infobox", "slug": "litecoin", "title": "Litecoin", "section": "Summary and infobox", "text": "Charlie Lee's 2011 code fork of Bitcoin: “silver to Bitcoin's gold”, Scrypt proof of work, 2.5-minute blocks, MWEB privacy since 2022. Ticker: LTC [btk-ltc-e30]; Type: Code fork of Bitcoin, new genesis block [ltc-ann]; Creator: Charlie Lee (coblee) [ltc-ann]; Launch: 13 October 2011, 03:00 GMT [ltc-ann]; Proof of work: Scrypt [ltc-ann]; Block time: 2.5 minutes [ltc-ann]; Premine: 150 coins (genesis and first two blocks) [ltc-ann]; MWEB: Locked in at block 2,257,920; activated May 2022 [ltc-mweb]; Planned supply: About 84 million LTC, “roughly 4 times as many coins as Bitcoin” [ltc-ann]", "aliases": "ltc scrypt mweb", "refs": ["btk-ltc-e30", "ltc-ann", "ltc-mweb"], "url": "/wiki/litecoin/"}, {"id": "litecoin#takeover", "slug": "litecoin", "title": "Litecoin", "section": "Takeover view (editorial opinion)", "text": "Charlie Lee has been on the show three times. The recurring question: if Lightning exists, why is Litecoin still alive? His answer is in S15 E30 and S15 E34. [btk-ltc-e30] [ep-s15e34-intro]", "aliases": "ltc scrypt mweb", "refs": ["btk-ltc-e30", "ep-s15e34-intro"], "url": "/wiki/litecoin/"}, {"id": "litecoin#734", "slug": "litecoin", "title": "Litecoin", "section": "Launch", "text": "Charlie Lee (coblee) announced Litecoin on Bitcointalk, describing it as \"silver to Bitcoin's gold\"; a later edit to the thread records the launch as 13 October 2011 at 03:00 GMT [ltc-ann]. It was forked directly from the Bitcoin source code, with the stated aim of not changing what works unless there was good reason [ltc-ann].", "aliases": "ltc scrypt mweb", "refs": ["ltc-ann"], "url": "/wiki/litecoin/"}, {"id": "litecoin#735", "slug": "litecoin", "title": "Litecoin", "section": "Design", "text": "Litecoin uses the Scrypt proof of work, which the announcement credits to Tenebrix and ArtForz's implementation, and targets 2.5-minute blocks with 50 coins per block at launch [ltc-ann]. The launch premine was 150 coins: the genesis block and the first two blocks [ltc-ann].", "aliases": "ltc scrypt mweb", "refs": ["ltc-ann"], "url": "/wiki/litecoin/"}, {"id": "litecoin#736", "slug": "litecoin", "title": "Litecoin", "section": "MWEB", "text": "MimbleWimble Extension Blocks, an opt-in confidentiality feature led by David Burkett, reached its 75% miner signalling threshold on 2 May 2022, locked in for activation at block 2,257,920, and was announced as activated on 20 May 2022 [ltc-mweb]. Charlie Lee discussed MWEB and privacy on Bitcoin Takeover S15 E34 [ep-s15e34-intro].", "aliases": "ltc scrypt mweb", "refs": ["ep-s15e34-intro", "ltc-mweb"], "url": "/wiki/litecoin/"}, {"id": "litecoin#737", "slug": "litecoin", "title": "Litecoin", "section": "Heard on Bitcoin Takeover", "text": "Charlie Lee explained MWEB on S15 E34 (April 2024): “So every Litecoin block now has an extension block that has all the MWEB transactions.” [ep-s15e34-q842] In the same episode: “Litecoin doesn't need a second layer right now as much as Bitcoin does.” [ep-s15e34-q438] Other Charlie Lee episodes on Litecoin: S15 E30, ‘Charlie Lee on Lightning & Litecoin’ (April 2024) [btk-ep-s15e30]; S11 E5, ‘Charlie Lee on Mimble Wimble Extension Blocks (MWEB)’ (June 2022) [btk-ep-s11e5].", "aliases": "ltc scrypt mweb", "refs": ["btk-ep-s11e5", "btk-ep-s15e30", "ep-s15e34-q438", "ep-s15e34-q842"], "url": "/wiki/litecoin/"}, {"id": "lucky-coin#infobox", "slug": "lucky-coin", "title": "Lucky Coin (LKY)", "section": "Summary and infobox", "text": "A 2013 Scrypt coin from Litecoin's code with random “super blocks”; Dogecoin's client began as a fork of it. Launch: 24 May 2013, by LuckyC [lky-ann]; Genesis block: May 22, 2013 [lky-ann2]; Codebase: “a fork of Litecoin version with random bonus blocks” [lky-readme]; Proof of work: Scrypt [lky-ann2]; Super blocks: Random x2, x5 and x58 rewards [lky-ann]; Hard fork: Block 69360 (October 2013) [lky-hf]", "aliases": "lky luckycoin lucky coin super blocks", "refs": ["lky-ann", "lky-ann2", "lky-hf", "lky-readme"], "url": "/wiki/lucky-coin/"}, {"id": "lucky-coin#takeover", "slug": "lucky-coin", "title": "Lucky Coin (LKY)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Lucky Coin's own history line reads “Takeover: June 17, 2013 by Titan” — a community takeover, and the code that Dogecoin started from. [lky-ann2] [doge-devs]", "aliases": "lky luckycoin lucky coin super blocks", "refs": ["doge-devs", "lky-ann2"], "url": "/wiki/lucky-coin/"}, {"id": "lucky-coin#740", "slug": "lucky-coin", "title": "Lucky Coin (LKY)", "section": "Launch", "text": "LuckyC announced LuckyCoin on 24 May 2013, offering “super lucky blocks, where your reward can be x2 ,x5 and even x58!” [lky-ann]. The original specs gave 1-minute blocks and 88 coins per block, halving “every 2 years (1,036,800 blocks)”, for a total of around 200 million coins [lky-ann]. The README describes Luckycoin as “a fork of Litecoin version with random bonus blocks” using Scrypt [lky-readme].", "aliases": "lky luckycoin lucky coin super blocks", "refs": ["lky-ann", "lky-readme"], "url": "/wiki/lucky-coin/"}, {"id": "lucky-coin#741", "slug": "lucky-coin", "title": "Lucky Coin (LKY)", "section": "Takeover and hard fork", "text": "A new official thread opened by Titan on 12 April 2014 gives the history “Launch: May 24, 2013 by LuckyC” and “Takeover: June 17, 2013 by Titan” [lky-ann2]. On 15 October 2013 Titan announced a mandatory hard fork at block 69360, warning “Old clients will not work beyond block 69360!” [lky-hf]. The 2014 specs differ from the launch post: the reward “halves every 100,000 blocks” and the total is “around 20 million coins” [lky-ann2].", "aliases": "lky luckycoin lucky coin super blocks", "refs": ["lky-ann2", "lky-hf"], "url": "/wiki/lucky-coin/"}, {"id": "lucky-coin#742", "slug": "lucky-coin", "title": "Lucky Coin (LKY)", "section": "Dogecoin", "text": "Dogecoin Core started as a fork of Lucky Coin and Litecoin, themselves forks of Bitcoin Core [doge-devs]. See Dogecoin [doge-devs].", "aliases": "lky luckycoin lucky coin super blocks", "refs": ["doge-devs"], "url": "/wiki/lucky-coin/"}, {"id": "luke-dashjr#infobox", "slug": "luke-dashjr", "title": "Luke Dashjr", "section": "Summary and infobox", "text": "Bitcoin Knots maintainer; central figure of BIP-110 and the 2026 BLAKE2b fork. Known for: Bitcoin Knots maintainer [btk-blake]; 2026 fork: Bitcoin BLAKE2b (XBT / BTCB2) [btk-blake]; Proposal: Hardfork: new BLAKE2b proof-of-work algorithm (Knots) [bmd-advisory]; 2026 roles: Removed as BIP editor; resigned from OCEAN; leads CONVOY Mining [btk-blake]", "aliases": "knots", "refs": ["bmd-advisory", "btk-blake"], "url": "/wiki/luke-dashjr/"}, {"id": "luke-dashjr#takeover", "slug": "luke-dashjr", "title": "Luke Dashjr", "section": "Takeover view (editorial opinion)", "text": "Not yet a guest. His fork is covered through the magazine and episodes with Lukas Hozda and Bob Summerwill. [ep-s17e17-bip110] [ep-s17e42-stall]", "aliases": "knots", "refs": ["ep-s17e17-bip110", "ep-s17e42-stall"], "url": "/wiki/luke-dashjr/"}, {"id": "luke-dashjr#745", "slug": "luke-dashjr", "title": "Luke Dashjr", "section": "Bitcoin Knots and BIP-110", "text": "Luke Dashjr maintains Bitcoin Knots and is credited on BIP-110, a soft fork to limit arbitrary data on Bitcoin [btk-blake] [bip110].", "aliases": "knots", "refs": ["bip110", "btk-blake"], "url": "/wiki/luke-dashjr/"}, {"id": "luke-dashjr#746", "slug": "luke-dashjr", "title": "Luke Dashjr", "section": "The BLAKE2b fork", "text": "When BIP-110 failed to win SHA-256d hashrate, the project became a hard fork with a new proof of work. Dashjr authored the BLAKE2b block header, the newspaper headline placed in the activation block's coinbase, and the coinbase maturity rule [btk-blake], and his Bitcoin Knots proposal is titled \"Hardfork: New BLAKE2b proof-of-work algorithm\" [bmd-advisory]. See Bitcoin BLAKE2b.", "aliases": "knots", "refs": ["bmd-advisory", "btk-blake"], "url": "/wiki/luke-dashjr/"}, {"id": "luke-dashjr#747", "slug": "luke-dashjr", "title": "Luke Dashjr", "section": "2026", "text": "According to the Forks! magazine, in August 2026 he was removed as a BIP editor, resigned from OCEAN and went on to lead CONVOY Mining; he calls the original majority chain \"Spamcoin\" [btk-blake].", "aliases": "knots", "refs": ["btk-blake"], "url": "/wiki/luke-dashjr/"}, {"id": "march-2013-chain-fork#infobox", "slug": "march-2013-chain-fork", "title": "March 2013 chain fork", "section": "Summary and infobox", "text": "The accidental split of 11–12 March 2013, when Bitcoin 0.8 accepted a large block that older nodes could not process; pools downgraded to 0.7 to end it. Date: 11–12 March 2013 [alert-2013]; Trigger block: 225,430 [alert-2013]; Cause: Pre-0.8 Berkeley DB lock limit; 0.8 used LevelDB [bip50]; Hashpower on 0.8 chain: About 60% [bip50]; Resolution: BTCGuild and Slush downgraded to 0.7 [bip50]; Final break: Block 252,451 on 16 Aug 2013 forked unpatched nodes off [bip50]; Post-mortem: BIP-50, Gavin Andresen [bip50]", "aliases": "2013 fork 0.8 leveldb berkeley bdb locks bip50 225430", "refs": ["alert-2013", "bip50"], "url": "/wiki/march-2013-chain-fork/"}, {"id": "march-2013-chain-fork#takeover", "slug": "march-2013-chain-fork", "title": "March 2013 chain fork", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Takeover's fork history calls this “the closest Bitcoin has come to hard forking”: a limit no one had written down acted as a consensus rule, and the fix was to make it explicit and then remove it. [btk-allforks]", "aliases": "2013 fork 0.8 leveldb berkeley bdb locks bip50 225430", "refs": ["btk-allforks"], "url": "/wiki/march-2013-chain-fork/"}, {"id": "march-2013-chain-fork#750", "slug": "march-2013-chain-fork", "title": "March 2013 chain fork", "section": "What happened", "text": "The bitcoin.org alert says a miner running 0.8.0 created a large block at height 225,430 that was incompatible with earlier versions, and that the chain forked between nodes on the new and old software [alert-2013]. BIP-50 says the 0.8 chain had about 60% of mining hashpower, so the split would not resolve on its own [bip50].", "aliases": "2013 fork 0.8 leveldb berkeley bdb locks bip50 225430", "refs": ["alert-2013", "bip50"], "url": "/wiki/march-2013-chain-fork/"}, {"id": "march-2013-chain-fork#751", "slug": "march-2013-chain-fork", "title": "March 2013 chain fork", "section": "Cause", "text": "According to BIP-50, versions before 0.8 configured too few Berkeley DB locks to process some large but valid blocks, which made the lock limit an implicit and inconsistent consensus rule [bip50]. Bitcoin 0.8 had switched to LevelDB, which had no such limit [bip50]. Bitcoin Takeover's history adds that the block triggered a split of at least 24 blocks [btk-allforks].", "aliases": "2013 fork 0.8 leveldb berkeley bdb locks bip50 225430", "refs": ["bip50", "btk-allforks"], "url": "/wiki/march-2013-chain-fork/"}, {"id": "march-2013-chain-fork#752", "slug": "march-2013-chain-fork", "title": "March 2013 chain fork", "section": "Resolution", "text": "BTCGuild and Slush downgraded to 0.7 so that majority hashpower moved to the chain without the large block, “despite the fact that this caused them to sacrifice significant amounts of money”, BIP-50 says [bip50]. One large double spend succeeded during the split, by someone experimenting rather than attacking [bip50]. Version 0.8.1 temporarily limited blocks to rules older nodes could handle [bip50].", "aliases": "2013 fork 0.8 leveldb berkeley bdb locks bip50 225430", "refs": ["bip50"], "url": "/wiki/march-2013-chain-fork/"}, {"id": "march-2013-chain-fork#753", "slug": "march-2013-chain-fork", "title": "March 2013 chain fork", "section": "Aftermath", "text": "BIP-50 records that on 16 August 2013 block 252,451 was accepted by the network and forked unpatched nodes off [bip50]. Bitcoin Takeover's fork history notes that BIP-50 later dropped the words “hard fork”, and concludes that this was the closest Bitcoin has come to one [btk-allforks].", "aliases": "2013 fork 0.8 leveldb berkeley bdb locks bip50 225430", "refs": ["bip50", "btk-allforks"], "url": "/wiki/march-2013-chain-fork/"}, {"id": "matt-corallo#infobox", "slug": "matt-corallo", "title": "Matt Corallo", "section": "Summary and infobox", "text": "Long-time Bitcoin developer: author of compact block relay (BIP-152), co-author of BIP-54 Consensus Cleanup, and a signer of the 2016 Hong Kong Roundtable statement. GitHub: TheBlueMatt, since March 2011 [gh-corallo]; BIPs (author/co-author): 21, 37, 54, 111, 152, 321, 323, 353 [bips-list]; Consensus Cleanup: BIP-54 co-author with Antoine Poinsot [bip54]; Hong Kong, Feb 2016: Signed as “Bitcoin Core Contributor” [hk-letter]; CTV, 2022: Publicly sceptical of activation [optech-197]", "aliases": "bluematt corallo compact blocks", "refs": ["bip54", "bips-list", "gh-corallo", "hk-letter", "optech-197"], "url": "/wiki/matt-corallo/"}, {"id": "matt-corallo#takeover", "slug": "matt-corallo", "title": "Matt Corallo", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Corallo appears on both sides of fork history — at the 2016 Hong Kong table with miners, and in 2022 among those asking whether CTV was the right covenant. [btk-forkwars] [optech-197]", "aliases": "bluematt corallo compact blocks", "refs": ["btk-forkwars", "optech-197"], "url": "/wiki/matt-corallo/"}, {"id": "matt-corallo#756", "slug": "matt-corallo", "title": "Matt Corallo", "section": "BIPs", "text": "The BIP index lists Matt Corallo as author or co-author of BIPs 21, 37, 54, 111, 152 (“Compact Block Relay”), 321, 323 and 353 [bips-list]. BIP-54, “Consensus Cleanup”, names Antoine Poinsot and Matt Corallo as authors [bip54]; see the Great Consensus Cleanup. His GitHub account, TheBlueMatt, dates from March 2011 [gh-corallo].", "aliases": "bluematt corallo compact blocks", "refs": ["bip54", "bips-list", "gh-corallo"], "url": "/wiki/matt-corallo/"}, {"id": "matt-corallo#757", "slug": "matt-corallo", "title": "Matt Corallo", "section": "Fork politics", "text": "He signed the February 2016 Hong Kong Roundtable statement as a “Bitcoin Core Contributor”, alongside Cory Fields, Johnson Lau, Luke Dashjr and Peter Todd [hk-letter] [btk-forkwars]. In the 2022 CTV activation debate, Bitcoin Optech reported him arguing that soft forks should wait until a proposal gives the most value, and quoted: “from what I have seen it's not been clear that CTV is really a good option” [optech-197].", "aliases": "bluematt corallo compact blocks", "refs": ["btk-forkwars", "hk-letter", "optech-197"], "url": "/wiki/matt-corallo/"}, {"id": "merged-mining#infobox", "slug": "merged-mining", "title": "Merged mining", "section": "Summary and infobox", "text": "Reusing the same proof of work on a parent chain and one or more auxiliary chains, pioneered by Namecoin with Bitcoin as the parent. Also called: AuxPoW (auxiliary proof of work) [bw-merged]; Parent chain: Where the mining work happens; needs no AuxPoW logic [bw-merged]; Auxiliary chain: Accepts the parent's work as its own [bw-merged]; First use: Namecoin, from block 19,200 [nmc-chainparams]; Other users: Dogecoin (Scrypt with AuxPoW) [doge-ann]; Related: Blind merged mining, BIP-301 [bip301]", "aliases": "auxpow merge mining", "refs": ["bip301", "bw-merged", "doge-ann", "nmc-chainparams"], "url": "/wiki/merged-mining/"}, {"id": "merged-mining#takeover", "slug": "merged-mining", "title": "Merged mining", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: merged mining is the oldest answer to the question drivechains reopened: how can a new chain borrow Bitcoin's hashpower without forking Bitcoin's ledger? [bw-merged] [bip301]", "aliases": "auxpow merge mining", "refs": ["bip301", "bw-merged"], "url": "/wiki/merged-mining/"}, {"id": "merged-mining#760", "slug": "merged-mining", "title": "Merged mining", "section": "How it works", "text": "Merged mining is the act of using work done on one blockchain on more than one chain, through auxiliary proof of work (AuxPoW) [bw-merged]. The parent blockchain is where the mining actually happens and does not need to know about AuxPoW; the auxiliary chain is modified to accept the parent's work as valid [bw-merged].", "aliases": "auxpow merge mining", "refs": ["bw-merged"], "url": "/wiki/merged-mining/"}, {"id": "merged-mining#761", "slug": "merged-mining", "title": "Merged mining", "section": "History", "text": "The Bitcoin Wiki's merged mining specification is the standard used by Namecoin [bw-merged]. Namecoin Core starts accepting auxiliary proof of work at height 19,200 [nmc-chainparams]. Dogecoin's announcement lists Scrypt with AuxPoW [doge-ann].", "aliases": "auxpow merge mining", "refs": ["bw-merged", "doge-ann", "nmc-chainparams"], "url": "/wiki/merged-mining/"}, {"id": "merged-mining#762", "slug": "merged-mining", "title": "Merged mining", "section": "Drivechains", "text": "BIP-301 proposes blind merged mining, part of the drivechain design [bip301].", "aliases": "auxpow merge mining", "refs": ["bip301"], "url": "/wiki/merged-mining/"}, {"id": "merged-mining#763", "slug": "merged-mining", "title": "Merged mining", "section": "Heard on Bitcoin Takeover", "text": "On S16 E28 (May 2025), Charles Chong said: “I think the benefit merge mining offers is to solve the bootstrap problem that I mentioned earlier, which is getting miners involved.” The downside, he added, is that “as a miner, I view that as free money.” [ep-s16e28-q2624]", "aliases": "auxpow merge mining", "refs": ["ep-s16e28-q2624"], "url": "/wiki/merged-mining/"}, {"id": "microbitcoin#infobox", "slug": "microbitcoin", "title": "MicroBitcoin (MBC)", "section": "Summary and infobox", "text": "A 2018 hard fork at a 1 BTC = 10,000 MBC ratio that changed proof of work three times and in 2019 restarted on a new network, burning coins that had not moved. Launched: 11 Jul 2018 as a hard fork [mbc-wp]; First MBC block: 525,001 [mbc-readme]; Ratio: 1 BTC = 10,000 MBC [mbc-wp]; Proof of work: Groestl → Rainforest (6 Mar 2019) → RFv2 (7 May 2019) → YesPower (new network) [mbc-wp]; New network: 9 Oct 2019; unmoved coins not snapshotted [mbc-wp]; Supply: 61,000,000,000 MBC cap [mbc-wp]", "aliases": "mbc groestl rainforest yespower", "refs": ["mbc-readme", "mbc-wp"], "url": "/wiki/microbitcoin/"}, {"id": "microbitcoin#takeover", "slug": "microbitcoin", "title": "MicroBitcoin (MBC)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: MicroBitcoin is the fork that admitted inheriting Bitcoin's history was a burden — after a year it dropped the old chain, kept a snapshot, and burned the coins nobody had claimed. [mbc-wp]", "aliases": "mbc groestl rainforest yespower", "refs": ["mbc-wp"], "url": "/wiki/microbitcoin/"}, {"id": "microbitcoin#766", "slug": "microbitcoin", "title": "MicroBitcoin (MBC)", "section": "Fork", "text": "The whitepaper says MicroBitcoin was “launched 11 July 2018 as an hard fork of Bitcoin network”, with the decimal point shifted “making 1 BTC equal to 10,000 MBC” [mbc-wp]. The README treats block 525001 as the “first MBC block” [mbc-readme]. Bitcoin block 525,000 was mined on 29 May 2018, six weeks before the July launch date [btc-525000].", "aliases": "mbc groestl rainforest yespower", "refs": ["btc-525000", "mbc-readme", "mbc-wp"], "url": "/wiki/microbitcoin/"}, {"id": "microbitcoin#767", "slug": "microbitcoin", "title": "MicroBitcoin (MBC)", "section": "Proof of work", "text": "The first blocks replaced sha256d with Groestl, which the whitepaper says proved not to be ASIC resistant once Baikal's BK-G28 supported it [mbc-wp]. The network hard-forked to Rainforest on 6 March 2019 and to RFv2 on 7 May 2019 [mbc-wp]. The new network uses “YesPower Proof-of-Work” on the Bitcoin Core 22 codebase [mbc-readme].", "aliases": "mbc groestl rainforest yespower", "refs": ["mbc-readme", "mbc-wp"], "url": "/wiki/microbitcoin/"}, {"id": "microbitcoin#768", "slug": "microbitcoin", "title": "MicroBitcoin (MBC)", "section": "New network", "text": "On 9 October 2019 the community “switched to new network essentially abandoning old one” [mbc-wp]. Coins that had not moved since block 525,000 were not snapshotted “and essentially burned”; 44,386,397,362.4252 MBC were activated, out of a 61,000,000,000 MBC cap [mbc-wp].", "aliases": "mbc groestl rainforest yespower", "refs": ["mbc-wp"], "url": "/wiki/microbitcoin/"}, {"id": "mike-hearn#infobox", "slug": "mike-hearn", "title": "Mike Hearn", "section": "Summary and infobox", "text": "Former Google engineer, bitcoinj author and co-creator of Bitcoin XT, who declared Bitcoin a failed experiment in January 2016. Background: Former Google engineer; original author of bitcoinj [hearn-bw]; Client: Created Bitcoin XT in 2014 [xt-bw]; Proposal: BIP 64 (UTXO lookups), shipped in XT 0.10 [xt-bw]; Left: January 2016, with the essay “The resolution of the Bitcoin experiment” [hearn-resolution]", "aliases": "hearn bitcoinj", "refs": ["hearn-bw", "hearn-resolution", "xt-bw"], "url": "/wiki/mike-hearn/"}, {"id": "mike-hearn#takeover", "slug": "mike-hearn", "title": "Mike Hearn", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Hearn's exit essay is the block size war's most quoted primary document, and Fork Wars pairs it with the XT release as the bookends of his chapter. [btk-forkwars] [hearn-resolution]", "aliases": "hearn bitcoinj", "refs": ["btk-forkwars", "hearn-resolution"], "url": "/wiki/mike-hearn/"}, {"id": "mike-hearn#771", "slug": "mike-hearn", "title": "Mike Hearn", "section": "Developer", "text": "Hearn is a former Google engineer and the original author of bitcoinj [hearn-bw]. The Fork Wars timeline notes that Satoshi's April 2009 letter on Visa-scale volume was a reply to him [btk-forkwars].", "aliases": "hearn bitcoinj", "refs": ["btk-forkwars", "hearn-bw"], "url": "/wiki/mike-hearn/"}, {"id": "mike-hearn#772", "slug": "mike-hearn", "title": "Mike Hearn", "section": "Bitcoin XT", "text": "Hearn created Bitcoin XT in 2014, and in 2015 it adopted Gavin Andresen's BIP-101 [xt-bw]. In his own words, “some long-term developers (including me) got together and developed the necessary code to raise the limit” and released it “in a modified version of the software that we branded Bitcoin XT” [hearn-resolution].", "aliases": "hearn bitcoinj", "refs": ["hearn-resolution", "xt-bw"], "url": "/wiki/mike-hearn/"}, {"id": "mike-hearn#773", "slug": "mike-hearn", "title": "Mike Hearn", "section": "Exit", "text": "On 14 January 2016 Hearn wrote that “the now inescapable conclusion” was that Bitcoin had failed, and that he would no longer take part in development and had sold all his coins [hearn-resolution]. He argued the capacity limit had not been raised because the chain was “controlled by Chinese miners, just two of whom control more than 50% of the hash power” [hearn-resolution].", "aliases": "hearn bitcoinj", "refs": ["hearn-resolution"], "url": "/wiki/mike-hearn/"}, {"id": "mimblewimblecoin#infobox", "slug": "mimblewimblecoin", "title": "MimbleWimbleCoin (MWC)", "section": "Summary and infobox", "text": "A MimbleWimble coin launched in November 2019 with a 20 million cap, whose airdrop to registered Bitcoin holders closed on 2 January 2020. Mainnet: 11 Nov 2019 [mwc-roadmap]; Protocol: MimbleWimble, one-minute blocks [mwc-readme]; Cap: 20,000,000 MWC [mwc-readme]; BTC airdrop: Claims closed 2 Jan 2020 [mwc-claiming]; Airdrop claimed: 5,400,037.41 MWC [mwc-roadmap]", "aliases": "mwc mimblewimble airdrop", "refs": ["mwc-claiming", "mwc-readme", "mwc-roadmap"], "url": "/wiki/mimblewimblecoin/"}, {"id": "mimblewimblecoin#takeover", "slug": "mimblewimblecoin", "title": "MimbleWimbleCoin (MWC)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: MWC is the claim-based airdrop done carefully — registration first, then a signed message from the BTC address — and the funds table shows how much went unclaimed. [mwc-claiming] [mwc-roadmap]", "aliases": "mwc mimblewimble airdrop", "refs": ["mwc-claiming", "mwc-roadmap"], "url": "/wiki/mimblewimblecoin/"}, {"id": "mimblewimblecoin#776", "slug": "mimblewimblecoin", "title": "MimbleWimbleCoin (MWC)", "section": "Protocol", "text": "The node README describes “an in-progress implementation of the MimbleWimble protocol” with one-minute blocks and a fixed limit of 20 000 000 MWC [mwc-readme]. The roadmap gives the mainnet launch as 11/11/2019 [mwc-roadmap].", "aliases": "mwc mimblewimble airdrop", "refs": ["mwc-readme", "mwc-roadmap"], "url": "/wiki/mimblewimblecoin/"}, {"id": "mimblewimblecoin#777", "slug": "mimblewimblecoin", "title": "MimbleWimbleCoin (MWC)", "section": "The Bitcoin airdrop", "text": "The wallet's claiming guide opens: “Important: Claims will close on January 2, 2020” [mwc-claiming]. Claimants needed “the ability to sign a message from the BTC address that you registered” [mwc-claiming]. The roadmap's distribution table records 5,400,037.41 MWC claimed by Bitcoin holders when the airdrop closed on 1/2/20; later rounds went to MWC holders, including unclaimed airdrop coins [mwc-roadmap].", "aliases": "mwc mimblewimble airdrop", "refs": ["mwc-claiming", "mwc-roadmap"], "url": "/wiki/mimblewimblecoin/"}, {"id": "namecoin#infobox", "slug": "namecoin", "title": "Namecoin", "section": "Summary and infobox", "text": "The first fork of Bitcoin's code to run its own network: a naming system for the .bit domain that pioneered merged mining. Type: Codebase fork of Bitcoin with its own genesis block; no airdrop [nmc-ann]; Founder: Vincent Durham (vinced) [nmc-ann]; Genesis time: Timestamp 1303000001 (17 April 2011 00:26:41 UTC) [nmc-chainparams]; Proof of work: SHA-256d, merged-mined with a parent chain from block 19,200 [nmc-chainparams]; Name rules: name_new, name_firstupdate, name_update; names expired after 12,000 blocks at launch [nmc-ann]; Namespaces: DNS (a new TLD, “possibly .bit”) and personal [nmc-ann]; Soft forks: P2SH, CSV and SegWit at block 475,000 [nmc-chainparams]", "aliases": "nmc .bit vinced", "refs": ["nmc-ann", "nmc-chainparams"], "url": "/wiki/namecoin/"}, {"id": "namecoin#takeover", "slug": "namecoin", "title": "Namecoin", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Namecoin is Bitcoin's oldest sibling and the original merged-mining chain, a cypherpunk naming project rather than a monetary rival. [nmc-ann] [bw-merged]", "aliases": "nmc .bit vinced", "refs": ["bw-merged", "nmc-ann"], "url": "/wiki/namecoin/"}, {"id": "namecoin#780", "slug": "namecoin", "title": "Namecoin", "section": "Announcement", "text": "Vincent Durham, posting as vinced, announced Namecoin on Bitcointalk as “a distributed naming system based on Bitcoin”, with code at github.com/vinced/namecoin [nmc-ann]. Names were registered with name_new, name_firstupdate and name_update, and expired after 12,000 blocks unless renewed [nmc-ann]. Two namespaces were defined at launch: DNS, aimed at a new distributed TLD, “possibly .bit”, and personal [nmc-ann].", "aliases": "nmc .bit vinced", "refs": ["nmc-ann"], "url": "/wiki/namecoin/"}, {"id": "namecoin#781", "slug": "namecoin", "title": "Namecoin", "section": "Chain parameters", "text": "Namecoin Core's chain parameters create the genesis block with timestamp 1303000001 and a 50 NMC reward [nmc-chainparams]. Auxiliary proof of work starts at height 19,200, before which only legacy blocks are valid [nmc-chainparams]. P2SH, CSV and SegWit are enforced from height 475,000 [nmc-chainparams].", "aliases": "nmc .bit vinced", "refs": ["nmc-chainparams"], "url": "/wiki/namecoin/"}, {"id": "namecoin#782", "slug": "namecoin", "title": "Namecoin", "section": "Merged mining", "text": "The merged mining specification on the Bitcoin Wiki notes that its standard is the one used by Namecoin, with work done on a parent chain such as Bitcoin accepted on the auxiliary chain [bw-merged]. See Merged mining.", "aliases": "nmc .bit vinced", "refs": ["bw-merged"], "url": "/wiki/namecoin/"}, {"id": "namecoin#783", "slug": "namecoin", "title": "Namecoin", "section": "Heard on Bitcoin Takeover", "text": "Mike Carson of Impervious, discussing his Spaces naming protocol on S15 E51 (August 2024), noted that the “first altcoin was Namecoin”. [ep-s15e51-q602]", "aliases": "nmc .bit vinced", "refs": ["ep-s15e51-q602"], "url": "/wiki/namecoin/"}, {"id": "nchain#infobox", "slug": "nchain", "title": "nChain", "section": "Summary and infobox", "text": "Craig Wright's company in the Bitcoin SV split: it announced the Bitcoin SV client in August 2018, and the Ayre Group took control of it in 2023. Associated with: Craig Wright [btk-bsv]; Bitcoin SV client: Announced August 2018 [btk-bsv]; Controlling owner: Ayre Group, from 2023 [wp-ayre]; Headcount: About 300 for most of a decade (Kurt Wuckert Jr.'s estimate) [ep-s17e39-nchain]", "aliases": "nchain", "refs": ["btk-bsv", "ep-s17e39-nchain", "wp-ayre"], "url": "/wiki/nchain/"}, {"id": "nchain#takeover", "slug": "nchain", "title": "nChain", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: in the BSV story nChain is the institution and Wright the voice. Kurt Wuckert Jr. remembers it as a company built to scale Bitcoin that was “very roundly rejected”; BCH developers remember it as the side that forked off. [ep-s17e39-nchain] [ep-s17e26-nchain]", "aliases": "nchain", "refs": ["ep-s17e26-nchain", "ep-s17e39-nchain"], "url": "/wiki/nchain/"}, {"id": "nchain#786", "slug": "nchain", "title": "nChain", "section": "Bitcoin SV", "text": "Bitcoin Takeover's BSV article says that in 2018 “Craig Wright's nChain” called Bitcoin ABC's proposed changes an unauthorized redesign, and in August 2018 announced its own client, Bitcoin SV, which would reject them and raise the default block size from 32 MB to 128 MB [btk-bsv]. Exchanges kept the BCH ticker on the ABC chain and listed the nChain chain as BSV [btk-bsv]. See BCH–BSV hash war.", "aliases": "nchain", "refs": ["btk-bsv"], "url": "/wiki/nchain/"}, {"id": "nchain#787", "slug": "nchain", "title": "nChain", "section": "Accounts from both sides", "text": "On S17 E26 Calin Culianu said the nChain people produced research arguing the changes were not needed yet and “got really pissed off and they forked off” [ep-s17e26-nchain]. On S17 E39 Kurt Wuckert Jr. said nChain had “like, 300 employees at it for the better part of a decade”, fewer now, which is his estimate [ep-s17e39-nchain].", "aliases": "nchain", "refs": ["ep-s17e26-nchain", "ep-s17e39-nchain"], "url": "/wiki/nchain/"}, {"id": "nchain#788", "slug": "nchain", "title": "nChain", "section": "Ownership", "text": "Wikipedia says the Ayre Group acquired a controlling interest in nChain in 2023 [wp-ayre]. Founding date, founders and patent counts are not verified in this wiki [wp-ayre].", "aliases": "nchain", "refs": ["wp-ayre"], "url": "/wiki/nchain/"}, {"id": "new-bitcoin#infobox", "slug": "new-bitcoin", "title": "New Bitcoin (NBTC)", "section": "Summary and infobox", "text": "A Chinese snapshot fork at block 501,225 with 42 million coins, 8 MB blocks and Equihash; its site claimed replay protection, and a May 2018 tool post warned that one of three newly listed forks lacked it. Snapshot height: 501,225 [nbtc-site]; Block 501,225 time: 2017-12-27 06:55:44 UTC [btc-501225]; Supply: 42 million, 34 million airdropped 1 BTC : 2 NBTC [nbtc-site]; Proof of work: Equihash [nbtc-site]; Block size: 8M [nbtc-site]; Replay protection: Site claimed it; a May 2018 tool post warned one of three new forks had none [ayms-nbtc]", "aliases": "nbtc new bitcoin 新比特币 snapshot", "refs": ["ayms-nbtc", "btc-501225", "nbtc-site"], "url": "/wiki/new-bitcoin/"}, {"id": "new-bitcoin#takeover", "slug": "new-bitcoin", "title": "New Bitcoin (NBTC)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: New Bitcoin is easy to confuse with “Bitcoin New (BTN)”, a separate entry at block 501,000 in the 2019 fork list. [bth-review]", "aliases": "nbtc new bitcoin 新比特币 snapshot", "refs": ["bth-review"], "url": "/wiki/new-bitcoin/"}, {"id": "new-bitcoin#791", "slug": "new-bitcoin", "title": "New Bitcoin (NBTC)", "section": "Site", "text": "The archived site (新比特币, captured 4 March 2018, in Chinese) describes a snapshot fork (“快照分叉”) at Bitcoin block 501225 [nbtc-site]. It gives a total of 42 million coins, 34 million handed to Bitcoin holders at 1:2 and the rest mined, 8M blocks, a switch from SHA256 to Equihash for GPU mining, and replay protection with SegWit [nbtc-site]. Its roadmap dates the successful fork to 27 December 2017 [nbtc-site]. Block 501,225 was mined that day at 06:55:44 UTC [btc-501225].", "aliases": "nbtc new bitcoin 新比特币 snapshot", "refs": ["btc-501225", "nbtc-site"], "url": "/wiki/new-bitcoin/"}, {"id": "new-bitcoin#792", "slug": "new-bitcoin", "title": "New Bitcoin (NBTC)", "section": "Replay warning", "text": "On 1 May 2018 Ayms, author of a tool for spending coins on forks, announced support for “Big Bitcoin \"BBC\", New Bitcoin \"NBTC\" and Bitcoin Clean \"BCL\" (Warning this fork does not implement any replay protection with BTC)” [ayms-nbtc]. Which of the three coins the warning refers to is not clear from that post [ayms-nbtc].", "aliases": "nbtc new bitcoin 新比特币 snapshot", "refs": ["ayms-nbtc"], "url": "/wiki/new-bitcoin/"}, {"id": "new-bitcoin#793", "slug": "new-bitcoin", "title": "New Bitcoin (NBTC)", "section": "Name", "text": "The 2019 fork list does not include New Bitcoin; it has a different entry, “Bitcoin New (BTN)”, at block 501000 with “no source code available” [bth-review]. This wiki treats them as two coins [bth-review] [nbtc-site].", "aliases": "nbtc new bitcoin 新比特币 snapshot", "refs": ["bth-review", "nbtc-site"], "url": "/wiki/new-bitcoin/"}, {"id": "new-york-agreement#infobox", "slug": "new-york-agreement", "title": "New York Agreement", "section": "Summary and infobox", "text": "The May 2017 industry deal to activate SegWit at 80% and hard fork to 2 MB within six months, which became SegWit2x. Date: 23 May 2017, at Consensus 2017 [nya-letter]; Published by: Digital Currency Group [nya-letter]; Terms: SegWit at 80% signalling on bit 4; a 2 MB hard fork within six months [nya-letter]; Basis: The “Segwit2Mb” proposal [nya-letter]; Claimed support (25 May): 58 companies in 22 countries; 83.28% of hashing power [nya-letter]; Mechanism: BIP-91: 269 of 336 blocks (80%) on bit 4 [bip91]; Outcome: 2 MB upgrade suspended on 8 November 2017 [s2x-suspend]", "aliases": "nya segwit2x dcg consensus 2017", "refs": ["bip91", "nya-letter", "s2x-suspend"], "url": "/wiki/new-york-agreement/"}, {"id": "new-york-agreement#takeover", "slug": "new-york-agreement", "title": "New York Agreement", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: the deal split in two. The miner-signalled SegWit half went through within weeks; the hard-fork half collapsed. The last common block before Bitcoin Cash even carried a /NYA/ coinbase tag. [btk-bch] [s2x-suspend]", "aliases": "nya segwit2x dcg consensus 2017", "refs": ["btk-bch", "s2x-suspend"], "url": "/wiki/new-york-agreement/"}, {"id": "new-york-agreement#796", "slug": "new-york-agreement", "title": "New York Agreement", "section": "Terms", "text": "The agreement committed signers to support two parallel upgrades based on the Segwit2Mb proposal: activating Segregated Witness at an 80% threshold signalling on bit 4, and activating a 2 MB hard fork within six months [nya-letter]. As of 25 May 2017, DCG said the group represented 58 companies in 22 countries and 83.28% of hashing power [nya-letter].", "aliases": "nya segwit2x dcg consensus 2017", "refs": ["nya-letter"], "url": "/wiki/new-york-agreement/"}, {"id": "new-york-agreement#797", "slug": "new-york-agreement", "title": "New York Agreement", "section": "Signers", "text": "The supporter list included Bitmain, Bitcoin.com, BitPay, Blockchain, BTCC, Coinbase, F2Pool, ViaBTC and Xapo, plus Gavin Andresen and Guy Corem as individuals [nya-letter]. DCG later noted that BitGo had been erroneously included in the initial list [nya-letter].", "aliases": "nya segwit2x dcg consensus 2017", "refs": ["nya-letter"], "url": "/wiki/new-york-agreement/"}, {"id": "new-york-agreement#798", "slug": "new-york-agreement", "title": "New York Agreement", "section": "The SegWit half", "text": "BIP-91 implemented the 80% bridge: miners signalling bit 4 in 269 of 336 blocks would make SegWit signalling mandatory, starting 1 June 2017 [bip91]. SegWit locked in from block 479,808 and activated at 481,824 on 24 August 2017 [btk-allforks]. The last block shared by Bitcoin and Bitcoin Cash, 478,558, was mined by BTC.com with a /NYA/ tag in its coinbase [btk-bch].", "aliases": "nya segwit2x dcg consensus 2017", "refs": ["bip91", "btk-allforks", "btk-bch"], "url": "/wiki/new-york-agreement/"}, {"id": "new-york-agreement#799", "slug": "new-york-agreement", "title": "New York Agreement", "section": "The 2 MB half", "text": "The hard fork was scheduled for block 494,784 under the SegWit2x name and suspended on 8 November 2017 [s2x-announce] [s2x-suspend].", "aliases": "nya segwit2x dcg consensus 2017", "refs": ["s2x-announce", "s2x-suspend"], "url": "/wiki/new-york-agreement/"}, {"id": "new-york-agreement#800", "slug": "new-york-agreement", "title": "New York Agreement", "section": "Heard on Bitcoin Takeover", "text": "When Vlad described him as part of the agreement on S17 E43 (September 2026), BitGo CEO Mike Belshe replied: “I was not part of the New York agreement, by the way.” [ep-s17e43-q4397] Later in the same episode he said: “I guess they put BitGo's name on the New York agreement without my permission once, after I explicitly told them not.” [ep-s17e43-nya]", "aliases": "nya segwit2x dcg consensus 2017", "refs": ["ep-s17e43-nya", "ep-s17e43-q4397"], "url": "/wiki/new-york-agreement/"}, {"id": "oil-bitcoin#infobox", "slug": "oil-bitcoin", "title": "Oil Bitcoin (OBTC)", "section": "Summary and infobox", "text": "A December 2017 proof-of-stake fork at block 498,888 with replay protection and O/A address prefixes; not to be confused with the 2019 Bitcoin Oil (OIL) press-release project. Fork height: 498,888 [obtc-readme]; Block 498,888 time: 2017-12-12 10:29:53 UTC [btc-498888]; Consensus: Proof of stake [obtc-readme]; Replay protection: SIGHASH_FORK_ID [obtc-readme]; Address prefixes: O and A [obtc-readme]; Status (Feb 2019 list): Not working; last synced block 524,001 on 7 Mar 2018 [bth-review]", "aliases": "obtc oil bitcoin oilbtc", "refs": ["btc-498888", "bth-review", "obtc-readme"], "url": "/wiki/oil-bitcoin/"}, {"id": "oil-bitcoin#takeover", "slug": "oil-bitcoin", "title": "Oil Bitcoin (OBTC)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: two unrelated projects used almost the same name. Oil Bitcoin (OBTC) is the 2017 chain; Bitcoin Oil (OIL) is a 2019 announcement with no fork block. [obtc-readme] [oil-bw]", "aliases": "obtc oil bitcoin oilbtc", "refs": ["obtc-readme", "oil-bw"], "url": "/wiki/oil-bitcoin/"}, {"id": "oil-bitcoin#803", "slug": "oil-bitcoin", "title": "Oil Bitcoin (OBTC)", "section": "Design", "text": "The README says “OBTC is a fork of Bitcoin, an open autonomous community that distributes lost bitcoin back to block rewards by using POS consensus mechanism” [obtc-readme]. It lists “a fork of Bitcoin after block height 498888”, per-block difficulty adjustment, replay protection with SIGHASH_FORK_ID, and wallet addresses starting with O and A [obtc-readme]. Block 498,888 was mined on 12 December 2017 [btc-498888].", "aliases": "obtc oil bitcoin oilbtc", "refs": ["btc-498888", "obtc-readme"], "url": "/wiki/oil-bitcoin/"}, {"id": "oil-bitcoin#804", "slug": "oil-bitcoin", "title": "Oil Bitcoin (OBTC)", "section": "Record", "text": "forkdrop's data file gives fork block 498888, a date of 2017-12-12 and a 1:1 ratio, with the maximum supply unknown (“???”) [fd-data]. The 2019 fork list found the oilbtc.io site gone and the node “doesn't seem to be working anymore”, last synced at block 524,001 on 7 March 2018 [bth-review].", "aliases": "obtc oil bitcoin oilbtc", "refs": ["bth-review", "fd-data"], "url": "/wiki/oil-bitcoin/"}, {"id": "oil-bitcoin#805", "slug": "oil-bitcoin", "title": "Oil Bitcoin (OBTC)", "section": "Name clash", "text": "This is a different project from Bitcoin Oil (OIL), a Houston company's 2019 press release about a planned proof-of-stake fork [oil-bw]. forkdrop keeps them as two entries with different tickers, sites and dates [fd-data].", "aliases": "obtc oil bitcoin oilbtc", "refs": ["fd-data", "oil-bw"], "url": "/wiki/oil-bitcoin/"}, {"id": "op-checkdatasig#infobox", "slug": "op-checkdatasig", "title": "OP_CHECKDATASIG", "section": "Summary and infobox", "text": "A Bitcoin Cash opcode, enabled in November 2018, that checks a signature over arbitrary data; it enabled oracles and early covenants and was one cause of the BSV split. Activated: BCH upgrade of 15 Nov 2018 [bch-nov2018]; Opcodes: OP_CHECKDATASIG, OP_CHECKDATASIGVERIFY [cds-spec]; Purpose: Check a signature against a message and public key [cds-spec]; Use: Oracles; covenants before later BCH upgrades [ep-s17e26-cds]", "aliases": "checkdatasig cds oracle magnetic anomaly", "refs": ["bch-nov2018", "cds-spec", "ep-s17e26-cds"], "url": "/wiki/op-checkdatasig/"}, {"id": "op-checkdatasig#takeover", "slug": "op-checkdatasig", "title": "OP_CHECKDATASIG", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: one opcode was enough for BSV supporters to call ABC's 2018 roadmap a redesign, and years later BCH developers credited the same opcode with making covenants possible. [btk-bsv] [ep-s17e26-cds]", "aliases": "checkdatasig cds oracle magnetic anomaly", "refs": ["btk-bsv", "ep-s17e26-cds"], "url": "/wiki/op-checkdatasig/"}, {"id": "op-checkdatasig#808", "slug": "op-checkdatasig", "title": "OP_CHECKDATASIG", "section": "Specification", "text": "The specification says OP_CHECKDATASIG and OP_CHECKDATASIGVERIFY “check whether a signature is valid with respect to a message and a public key” [cds-spec]. It adds that OP_CHECKDATASIG “permits data to be imported into a script, and have its validity checked against some signing authority such as an \"Oracle\"” [cds-spec]. The opcodes were enabled in the 15 November 2018 Bitcoin Cash upgrade with CTOR [bch-nov2018].", "aliases": "checkdatasig cds oracle magnetic anomaly", "refs": ["bch-nov2018", "cds-spec"], "url": "/wiki/op-checkdatasig/"}, {"id": "op-checkdatasig#809", "slug": "op-checkdatasig", "title": "OP_CHECKDATASIG", "section": "On the show", "text": "Vlad asked Amaury Séchet about “the Magnetic Anomaly hard fork with OP_CHECKDATASIG and CTOR” [ep-s17e19-mag]. Séchet called the opcode “a big enabler” for scripts [ep-s17e19-cds]. Rosco Kalis said that before later upgrades “the only thing that kind of was there that really did enable interesting smart contracts on BCH was CheckDataSig”, which allowed covenants [ep-s17e26-cds]. nChain's objection is covered in Bitcoin SV [btk-bsv].", "aliases": "checkdatasig cds oracle magnetic anomaly", "refs": ["btk-bsv", "ep-s17e19-cds", "ep-s17e19-mag", "ep-s17e26-cds"], "url": "/wiki/op-checkdatasig/"}, {"id": "op-return-2025#infobox", "slug": "op-return-2025", "title": "The 2025 OP_RETURN fight", "section": "Summary and infobox", "text": "The 2025 dispute over Bitcoin Core lifting its default OP_RETURN limit, which pushed opponents to Bitcoin Knots and fed the BIP-110 fork effort. Core PR: #32406 “policy: uncap datacarrier by default” (instagibbs) [core-pr32406]; Merged: 9 Jun 2025 [core-pr32406]; Core statement: 6 Jun 2025, relay policy [core-relay-2025]; Released in: Bitcoin Core 30.0 (-datacarriersize 100,000 default) [core-30]; Opposition: Bitcoin Knots, BIP-110 [btk-blake]", "aliases": "op_return opreturn datacarrier datacarriersize 32406 core 30 spam filters", "refs": ["btk-blake", "core-30", "core-pr32406", "core-relay-2025"], "url": "/wiki/op-return-2025/"}, {"id": "op-return-2025#takeover", "slug": "op-return-2025", "title": "The 2025 OP_RETURN fight", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: the first major fork fight since 2017 to be about what goes in blocks, not how big they are, and it put Bitcoin Knots in the role Bitcoin Classic and Unlimited once played. [btk-blake] [core-relay-2025]", "aliases": "op_return opreturn datacarrier datacarriersize 32406 core 30 spam filters", "refs": ["btk-blake", "core-relay-2025"], "url": "/wiki/op-return-2025/"}, {"id": "op-return-2025#812", "slug": "op-return-2025", "title": "The 2025 OP_RETURN fight", "section": "Change", "text": "Bitcoin Core PR #32406, “policy: uncap datacarrier by default”, was opened by instagibbs on 2 May 2025 and merged on 9 June 2025 [core-pr32406]. The Bitcoin Core 30.0 release notes say that -datacarriersize “is increased to 100,000 by default, which effectively uncaps the limit”, that it can be overridden with -datacarriersize=83 to revert, and that multiple OP_RETURN outputs are now permitted [core-30].", "aliases": "op_return opreturn datacarrier datacarriersize 32406 core 30 spam filters", "refs": ["core-30", "core-pr32406"], "url": "/wiki/op-return-2025/"}, {"id": "op-return-2025#813", "slug": "op-return-2025", "title": "The 2025 OP_RETURN fight", "section": "Core's statement", "text": "On 6 June 2025 Bitcoin Core published “Bitcoin Core development and transaction relay policy”, which said: “This is not endorsing or condoning non-financial data usage, but accepting that as a censorship-resistant system, Bitcoin can and will be used for use cases not everyone agrees on” [core-relay-2025].", "aliases": "op_return opreturn datacarrier datacarriersize 32406 core 30 spam filters", "refs": ["core-relay-2025"], "url": "/wiki/op-return-2025/"}, {"id": "op-return-2025#814", "slug": "op-return-2025", "title": "The 2025 OP_RETURN fight", "section": "Opposition", "text": "The Takeover BLAKE2b feature says that since the Ordinals wave of 2023 a vocal part of the community has seen inscriptions and large OP_RETURN outputs as spam, that Core “went the other way” in 2025, and that Bitcoin Knots “became the home of the opposition” [btk-blake]. Charlie Spears said on the show that the modern debate kicked off from a mailing-list issue after a Citrea presentation at OP_NEXT [ep-s17e13-opnext]. Bob Summerwill argued that data carrying could be disliked without being banned by consensus [ep-s17e42-stfu]. See Ordinals and Bitcoin BLAKE2b [btk-blake].", "aliases": "op_return opreturn datacarrier datacarriersize 32406 core 30 spam filters", "refs": ["btk-blake", "ep-s17e13-opnext", "ep-s17e42-stfu"], "url": "/wiki/op-return-2025/"}, {"id": "ordinals#infobox", "slug": "ordinals", "title": "Ordinals and inscriptions", "section": "Summary and infobox", "text": "Casey Rodarmor's numbering scheme for satoshis and the inscriptions built on it, which put arbitrary data in Taproot witnesses from 2023 and set off the data-carrier dispute. Creator: Casey Rodarmor [ep-s12e13-witness]; Numbering: Satoshis numbered in mining order, transferred first-in-first-out [ord-overview]; Inscriptions: Taproot script-path “envelopes”, commit/reveal [ord-inscriptions]; ord 0.4.0: Released 2023-01-20 [ord-040]; Consequence: Ordinals wave of 2023; OP_RETURN fight [btk-blake]", "aliases": "ordinals inscriptions rodarmor ord sats envelope", "refs": ["btk-blake", "ep-s12e13-witness", "ord-040", "ord-inscriptions", "ord-overview"], "url": "/wiki/ordinals/"}, {"id": "ordinals#takeover", "slug": "ordinals", "title": "Ordinals and inscriptions", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Ordinals needed no fork at all, yet they produced the next fork fight, because they changed what people thought blocks were for. [btk-blake] [ord-inscriptions]", "aliases": "ordinals inscriptions rodarmor ord sats envelope", "refs": ["btk-blake", "ord-inscriptions"], "url": "/wiki/ordinals/"}, {"id": "ordinals#817", "slug": "ordinals", "title": "Ordinals and inscriptions", "section": "Theory", "text": "The ord handbook says “Ordinals are a numbering scheme for satoshis that allows tracking and transferring individual sats”, with sats numbered in the order they are mined and transferred “first-in-first-out” [ord-overview]. The ord README describes the software as an index, block explorer and command-line wallet [ord-readme].", "aliases": "ordinals inscriptions rodarmor ord sats envelope", "refs": ["ord-overview", "ord-readme"], "url": "/wiki/ordinals/"}, {"id": "ordinals#818", "slug": "ordinals", "title": "Ordinals and inscriptions", "section": "Inscriptions", "text": "The handbook says inscription content “is entirely on-chain, stored in taproot script-path spend scripts”, made with a two-phase commit/reveal procedure and wrapped in “envelopes” of the form OP_FALSE OP_IF … OP_ENDIF [ord-inscriptions]. The ord 0.4.0 release was published on 20 January 2023 [ord-040]. On Bitcoin Takeover in February 2023 Casey Rodarmor said the design he settled on puts the inscription content “in what is called the witness” [ep-s12e13-witness]. In the same episode he compared Ordinals and inscriptions with Taro and RGB [ep-s12e13-sats]. The episode's transcript is titled S13 E3 while its file name says s12_e13; the wiki cites it by date [ep-s12e13-witness].", "aliases": "ordinals inscriptions rodarmor ord sats envelope", "refs": ["ep-s12e13-sats", "ep-s12e13-witness", "ord-040", "ord-inscriptions"], "url": "/wiki/ordinals/"}, {"id": "ordinals#819", "slug": "ordinals", "title": "Ordinals and inscriptions", "section": "Debate", "text": "Murch argued on S15 E50 against the claim that Taproot caused ordinals [ep-s15e50-ordinals]. The Takeover BLAKE2b feature traces the 2025 OP_RETURN fight to “the Ordinals wave of 2023” [btk-blake].", "aliases": "ordinals inscriptions rodarmor ord sats envelope", "refs": ["btk-blake", "ep-s15e50-ordinals"], "url": "/wiki/ordinals/"}, {"id": "paul-sztorc#infobox", "slug": "paul-sztorc", "title": "Paul Sztorc", "section": "Summary and infobox", "text": "LayerTwo Labs CEO, author of the drivechain proposals BIP-300/301, launcher of the eCash (ECX) fork. Role: CEO, LayerTwo Labs [ep-s17e37-launch]; Proposals: BIP-300, BIP-301 (drivechains) [bip300]; Fork: eCash (ECX), mainnet 29 October 2026 [btk-ecx]; Takeover episodes: Many, incl. S9 E4, S12 E10, S15 E68, S17 E21, S17 E37, S17 E46 [ep-s17e21-announce]", "aliases": "truthcoin drivechains", "refs": ["bip300", "btk-ecx", "ep-s17e21-announce", "ep-s17e37-launch"], "url": "/wiki/paul-sztorc/"}, {"id": "paul-sztorc#takeover", "slug": "paul-sztorc", "title": "Paul Sztorc", "section": "Takeover view (editorial opinion)", "text": "The most frequent fork guest on the show. Disclosure: LayerTwo Labs sponsors Bitcoin Takeover, and Vlad has said he backs the drivechain experiment. [ep-s17e19-sponsors] [ep-s17e37-outro]", "aliases": "truthcoin drivechains", "refs": ["ep-s17e19-sponsors", "ep-s17e37-outro"], "url": "/wiki/paul-sztorc/"}, {"id": "paul-sztorc#822", "slug": "paul-sztorc", "title": "Paul Sztorc", "section": "Drivechains", "text": "Paul Sztorc is the author of the drivechain proposals BIP-300 (hashrate escrows) and BIP-301 (blind merged mining) [bip300] [bip301]. He runs LayerTwo Labs [ep-s17e37-launch].", "aliases": "truthcoin drivechains", "refs": ["bip300", "bip301", "ep-s17e37-launch"], "url": "/wiki/paul-sztorc/"}, {"id": "paul-sztorc#823", "slug": "paul-sztorc", "title": "Paul Sztorc", "section": "eCash (ECX)", "text": "After years of trying to get drivechains activated on Bitcoin, Sztorc announced a hard fork on Bitcoin Takeover in April 2026 [ep-s17e21-announce], named it eCash [ep-s17e21-name], and launched mainnet at Bitcoin block 973,728 on 29 October 2026 [btk-ecx]. See eCash (ECX).", "aliases": "truthcoin drivechains", "refs": ["btk-ecx", "ep-s17e21-announce", "ep-s17e21-name"], "url": "/wiki/paul-sztorc/"}, {"id": "peercoin#infobox", "slug": "peercoin", "title": "Peercoin", "section": "Summary and infobox", "text": "The first cryptocurrency to use proof of stake, launched in August 2012 on a Bitcoin-based codebase. Type: Codebase based on Bitcoin; own genesis, no airdrop [ppc-readme]; Launch: Chain started 19 August 2012, 18:00:00 UTC [ppc-ann]; Previously: PPCoin [ppc-readme]; Authors: Paper credited to Scott Nadal and Sunny King (a pseudonym) [wp-peercoin]; Consensus: Hybrid proof of stake and proof of work [wp-peercoin]; Fees: Burned rather than paid to miners [wp-peercoin]", "aliases": "ppc ppcoin proof of stake", "refs": ["ppc-ann", "ppc-readme", "wp-peercoin"], "url": "/wiki/peercoin/"}, {"id": "peercoin#takeover", "slug": "peercoin", "title": "Peercoin", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Peercoin is where proof of stake entered the Bitcoin family tree, a decade before the idea took over other ecosystems. [ppc-readme] [wp-peercoin]", "aliases": "ppc ppcoin proof of stake", "refs": ["ppc-readme", "wp-peercoin"], "url": "/wiki/peercoin/"}, {"id": "peercoin#826", "slug": "peercoin", "title": "Peercoin", "section": "Launch", "text": "Sunny King announced on Bitcointalk that the PPCoin block chain “officially started at 2012-08-19 18:00:00 UTC” [ppc-ann]. The project README says Peercoin, previously known as PPCoin, is based on Bitcoin and was the first cryptocurrency design to introduce proof-of-stake consensus as a security model [ppc-readme].", "aliases": "ppc ppcoin proof of stake", "refs": ["ppc-ann", "ppc-readme"], "url": "/wiki/peercoin/"}, {"id": "peercoin#827", "slug": "peercoin", "title": "Peercoin", "section": "Design", "text": "Peercoin is based on an August 2012 paper credited to Scott Nadal and Sunny King, a pseudonym [wp-peercoin]. It uses both proof of work and proof of stake to distribute new coins, with proof of stake securing the chain [wp-peercoin]. Transaction fees are burned instead of being collected by a miner [wp-peercoin].", "aliases": "ppc ppcoin proof of stake", "refs": ["wp-peercoin"], "url": "/wiki/peercoin/"}, {"id": "peter-rizun#infobox", "slug": "peter-rizun", "title": "Peter Rizun", "section": "Summary and infobox", "text": "Chief scientist at Bitcoin Unlimited and author of the 2015 paper arguing that a fee market exists without a block size limit. Role: Chief Scientist, Bitcoin Unlimited [ep-s16e30-intro]; Known for: “A Transaction Fee Market Exists Without a Block Size Limit” (4 Aug 2015) [rizun-feemarket]; Scaling target: About 1 GB blocks (“Earth scale”) [ep-s16e30-gb]; Takeover appearance: S16 E30 (June 2025) [ep-s16e30-intro]", "aliases": "rizun fee market gigabyte", "refs": ["ep-s16e30-gb", "ep-s16e30-intro", "rizun-feemarket"], "url": "/wiki/peter-rizun/"}, {"id": "peter-rizun#takeover", "slug": "peter-rizun", "title": "Peter Rizun", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Rizun gave the big-block side its economics. On S16 E30 he still defended Bitcoin Unlimited's design but conceded that a 2017 bug “killed Bitcoin Unlimited as a … viable implementation on BTC”. [ep-s16e30-bug]", "aliases": "rizun fee market gigabyte", "refs": ["ep-s16e30-bug"], "url": "/wiki/peter-rizun/"}, {"id": "peter-rizun#830", "slug": "peter-rizun", "title": "Peter Rizun", "section": "The fee-market paper", "text": "Rizun's working paper of 4 August 2015 argues that, accounting for orphaning risk, a rational miner faces a “block space supply curve”, and that an unhealthy fee market in which miners produce arbitrarily large blocks “cannot exist since it requires communicating information at an arbitrarily fast rate” [rizun-feemarket]. On S16 E30 Vlad relayed Paul Sztorc's view that the paper was wrong about orphan risk but right in its title [ep-s16e30-fee]. Jonathan Bier said on S16 E60 that after seeing Rizun's presentation he asked to speak at the next Scaling Bitcoin conference in Hong Kong to refute it [ep-s16e60-rizun].", "aliases": "rizun fee market gigabyte", "refs": ["ep-s16e30-fee", "ep-s16e60-rizun", "rizun-feemarket"], "url": "/wiki/peter-rizun/"}, {"id": "peter-rizun#831", "slug": "peter-rizun", "title": "Peter Rizun", "section": "Bitcoin Unlimited", "text": "Introduced on S16 E30 as Chief Scientist at Bitcoin Unlimited [ep-s16e30-intro], Rizun described XT and Classic as attempts to reach consensus, and Unlimited as a mechanism that let people run larger limits and show that miners had to raise the block size in sync [ep-s16e30-bu]. Asked about weaknesses, he said “Bitcoin Unlimited had a bug and a bunch of nodes were taken down”, which he thinks took the momentum out of the movement in 2017 [ep-s16e30-bug].", "aliases": "rizun fee market gigabyte", "refs": ["ep-s16e30-bu", "ep-s16e30-bug", "ep-s16e30-intro"], "url": "/wiki/peter-rizun/"}, {"id": "peter-rizun#832", "slug": "peter-rizun", "title": "Peter Rizun", "section": "Scale", "text": "Rizun told Vlad that what he liked about Dan Kaminsky's 2011 talk was that it set an upper limit on how far Bitcoin must scale, “around one gigabyte blocks” [ep-s16e30-gb]. Fork Wars quotes him from the same episode on the 1 MB constant as a hard-coded limit that would be hard to remove [btk-forkwars].", "aliases": "rizun fee market gigabyte", "refs": ["btk-forkwars", "ep-s16e30-gb"], "url": "/wiki/peter-rizun/"}, {"id": "peter-todd#infobox", "slug": "peter-todd", "title": "Peter Todd", "section": "Summary and infobox", "text": "Bitcoin developer behind CHECKLOCKTIMEVERIFY and replace-by-fee, a Hong Kong Roundtable signer and a SegWit2x opponent. BIP-65: Author of OP_CHECKLOCKTIMEVERIFY [bip65]; BIP-125: Co-author of opt-in replace-by-fee signalling [bip125]; Hong Kong Roundtable: Signed as a Bitcoin Core contributor [hk-letter]; SegWit2x: Publicly recorded a lack of support (July 2017) [btk-forkwars]; Zcash: Took part in the 2016 trusted setup ceremony [ptodd-zcash]", "aliases": "petertodd rbf cltv", "refs": ["bip125", "bip65", "btk-forkwars", "hk-letter", "ptodd-zcash"], "url": "/wiki/peter-todd/"}, {"id": "peter-todd#takeover", "slug": "peter-todd", "title": "Peter Todd", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Todd is a useful corrective to camp labels. He signed the Hong Kong statement that promised a hard fork, then opposed SegWit2x, and later wrote the most detailed critique of drivechains. [hk-letter] [btk-forkwars] [ptodd-drivechains]", "aliases": "petertodd rbf cltv", "refs": ["btk-forkwars", "hk-letter", "ptodd-drivechains"], "url": "/wiki/peter-todd/"}, {"id": "peter-todd#835", "slug": "peter-todd", "title": "Peter Todd", "section": "Protocol work", "text": "Peter Todd is the author of BIP-65, which added OP_CHECKLOCKTIMEVERIFY to Bitcoin [bip65]. He co-authored BIP-125, opt-in full replace-by-fee signalling, with David A. Harding [bip125].", "aliases": "petertodd rbf cltv", "refs": ["bip125", "bip65"], "url": "/wiki/peter-todd/"}, {"id": "peter-todd#836", "slug": "peter-todd", "title": "Peter Todd", "section": "Block size war", "text": "He signed the February 2016 Hong Kong Roundtable statement as a Bitcoin Core contributor [hk-letter]. Fork Wars records that in July 2017 he publicly noted his lack of support for SegWit2x [btk-forkwars].", "aliases": "petertodd rbf cltv", "refs": ["btk-forkwars", "hk-letter"], "url": "/wiki/peter-todd/"}, {"id": "peter-todd#837", "slug": "peter-todd", "title": "Peter Todd", "section": "Other work", "text": "Todd wrote about his role in the 2016 Zcash trusted setup ceremony [ptodd-zcash]. In 2023 he published “Drivechains: A Detailed Analysis” [ptodd-drivechains].", "aliases": "petertodd rbf cltv", "refs": ["ptodd-drivechains", "ptodd-zcash"], "url": "/wiki/peter-todd/"}, {"id": "pieter-wuille#infobox", "slug": "pieter-wuille", "title": "Pieter Wuille", "section": "Summary and infobox", "text": "Bitcoin Core developer (sipa), co-founder of Blockstream, and author or co-author of the BIPs behind SegWit, version bits and Taproot. Handle: sipa [sipa-gh]; Known for: SegWit, Schnorr signatures, Taproot [bip341]; BIPs: Sole author of 66; first-listed author of 9, 340, 341 and 342; co-author of 141 [bips-list]; Co-founded: Blockstream (2014) [wp-blockstream]; Current affiliation: Chaincode Labs (GitHub bio, Nov 2026) [sipa-gh]", "aliases": "sipa wuille schnorr", "refs": ["bip341", "bips-list", "sipa-gh", "wp-blockstream"], "url": "/wiki/pieter-wuille/"}, {"id": "pieter-wuille#takeover", "slug": "pieter-wuille", "title": "Pieter Wuille", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: if you trace the soft forks that actually activated after 2015, Wuille's name is on nearly every specification, from SegWit's consensus BIP to all three Taproot BIPs. Fork Wars treats his December 2015 SegWit talk as the technical origin of the path that activated in 2017. [btk-forkwars] [bip141] [bip341]", "aliases": "sipa wuille schnorr", "refs": ["bip141", "bip341", "btk-forkwars"], "url": "/wiki/pieter-wuille/"}, {"id": "pieter-wuille#840", "slug": "pieter-wuille", "title": "Pieter Wuille", "section": "Specifications", "text": "Wuille is the sole author of BIP-66, strict DER signatures [bip66]. He co-authored BIP-9, the version-bits mechanism, with Peter Todd, Greg Maxwell and Rusty Russell [bip9], and BIP-141, Segregated Witness, with Eric Lombrozo and Johnson Lau [bip141]. He is the first-listed author of BIP-340 (Schnorr signatures, with Jonas Nick and Tim Ruffing) [bip340] and of BIP-341 and BIP-342 (Taproot and Tapscript, with Jonas Nick and Anthony Towns) [bip341] [bip342].", "aliases": "sipa wuille schnorr", "refs": ["bip141", "bip340", "bip341", "bip342", "bip66", "bip9"], "url": "/wiki/pieter-wuille/"}, {"id": "pieter-wuille#841", "slug": "pieter-wuille", "title": "Pieter Wuille", "section": "SegWit and Hong Kong", "text": "Bitcoin Takeover's Fork Wars timeline records that Wuille presented Segregated Witness at the Scaling Bitcoin workshop in Hong Kong on 6–7 December 2015, and calls that talk “the technical origin of the path that would, eventually, activate on Bitcoin in August 2017” [btk-forkwars]. See Segregated Witness.", "aliases": "sipa wuille schnorr", "refs": ["btk-forkwars"], "url": "/wiki/pieter-wuille/"}, {"id": "pieter-wuille#842", "slug": "pieter-wuille", "title": "Pieter Wuille", "section": "Blockstream and after", "text": "Wikipedia lists Wuille, with Gregory Maxwell, among the developers who founded Blockstream with Adam Back in 2014 [wp-blockstream]. His GitHub profile now describes him as a Bitcoin developer at Chaincode Labs, “Formerly @Blockstream” [sipa-gh]. In January 2021 Wladimir van der Laan's count of Bitcoin Core merges in 2020 listed 7 by Wuille [laanwj-gyre].", "aliases": "sipa wuille schnorr", "refs": ["laanwj-gyre", "sipa-gh", "wp-blockstream"], "url": "/wiki/pieter-wuille/"}, {"id": "poloniex#infobox", "slug": "poloniex", "title": "Poloniex", "section": "Summary and infobox", "text": "Exchange that listed Ethereum Classic days after the DAO fork, froze stolen ETC, listed CLAMs, and was owned by Circle from 2018 to 2019. ETC listing: 23 Jul 2016 [etc-history]; Stolen ETC (Aug 2016): 86% frozen, later returned [wp-etc]; DAO token: Delisted September 2016 [wp-dao]; Owner 2018–2019: Circle, bought for $400 million [wp-circle]", "aliases": "poloniex polo exchange", "refs": ["etc-history", "wp-circle", "wp-dao", "wp-etc"], "url": "/wiki/poloniex/"}, {"id": "poloniex#takeover", "slug": "poloniex", "title": "Poloniex", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: an exchange listing decided early whether a minority chain had a market — for ETC in 2016, as for the Bitcoin forks that announced exchange snapshots in 2017–18. [etc-history] [bpay-site]", "aliases": "poloniex polo exchange", "refs": ["bpay-site", "etc-history"], "url": "/wiki/poloniex/"}, {"id": "poloniex#845", "slug": "poloniex", "title": "Poloniex", "section": "Ethereum Classic", "text": "The Ethereum Classic history page records “Poloniex Lists ETC” on 23 July 2016 as “The largest Ethereum exchange signals long-term support for the original chain” [etc-history]. Wikipedia says that on 10 August 2016 the Robin Hood Group sent 2.9 million stolen ETC to Poloniex, “86% was frozen by Poloniex”, and “On 30 August 2016, Poloniex returned the ETC funds to the RHG” [wp-etc]. In September 2016 Poloniex delisted DAO trading pairs [wp-dao]. See Ethereum Classic [etc-history].", "aliases": "poloniex polo exchange", "refs": ["etc-history", "wp-dao", "wp-etc"], "url": "/wiki/poloniex/"}, {"id": "poloniex#846", "slug": "poloniex", "title": "Poloniex", "section": "Other listings and owners", "text": "The CLAM announcement thread advertised “CLAM added to Poloniex for Margin Trading!” [clam-ann]. Circle bought Poloniex in February 2018 for $400 million and sold it to an investment firm in October 2019 [wp-circle]. Poloniex's founding date and later history are not sourced here [wp-circle].", "aliases": "poloniex polo exchange", "refs": ["clam-ann", "wp-circle"], "url": "/wiki/poloniex/"}, {"id": "qeditas#infobox", "slug": "qeditas", "title": "Qeditas (QED)", "section": "Summary and infobox", "text": "A 2015 Bitcoin spin-off by Bill White for a library of formalized mathematics, with its distribution taken from a snapshot up to Bitcoin block 350,000. Announced: 21 March 2015 [qed-ann]; Snapshot: Bitcoin ledger up to (not including) block 350,000 [qed-ann]; Block 350,000 time: 2015-03-30 22:17:14 UTC [btc-350000]; Lead: Bill White; IOHK named as leading the project [qed-ann]", "aliases": "qed qeditas bill white iohk formal mathematics spin-off", "refs": ["btc-350000", "qed-ann"], "url": "/wiki/qeditas/"}, {"id": "qeditas#takeover", "slug": "qeditas", "title": "Qeditas (QED)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Qeditas is a March 2015 spin-off that told holders to move coins off exchanges before its snapshot. [qed-ann]", "aliases": "qed qeditas bill white iohk formal mathematics spin-off", "refs": ["qed-ann"], "url": "/wiki/qeditas/"}, {"id": "qeditas#849", "slug": "qeditas", "title": "Qeditas (QED)", "section": "Pitch", "text": "Bill White's pre-announcement of 21 March 2015 says “Qeditas is a project to apply block chain technology to support the construction of a library of formalized mathematics” [qed-ann]. Its short version: “Bitcoin is for money; Ethereum is for computation; Qeditas is for deduction.” [qed-ann] The post says “IOHK is leading the Qeditas project” [qed-ann].", "aliases": "qed qeditas bill white iohk formal mathematics spin-off", "refs": ["qed-ann"], "url": "/wiki/qeditas/"}, {"id": "qeditas#850", "slug": "qeditas", "title": "Qeditas (QED)", "section": "Snapshot", "text": "The plan was “to take a snapshot of the Bitcoin block chain up to (not iincluding [sic]) the block at height 350,000” [qed-ann]. The post urged holders to keep coins under their own control, preferably in a p2pkh address [qed-ann]. An update says “The 350,000th block has been mined” and links the snapshot [qed-ann]. Block 350,000 was mined on 30 March 2015 [btc-350000]. Replies in the thread compare its distribution with that of CLAMs [qed-ann]. Dalilcoin later forked Qeditas [dlc-readme].", "aliases": "qed qeditas bill white iohk formal mathematics spin-off", "refs": ["btc-350000", "dlc-readme", "qed-ann"], "url": "/wiki/qeditas/"}, {"id": "quantum-bitcoin#infobox", "slug": "quantum-bitcoin", "title": "Quantum Bitcoin (QBTC)", "section": "Summary and infobox", "text": "A fork claimed at block 501,368 on 28 December 2017 with a 210,000-coin premine and a long feature list; this wiki found no source code. Fork height: 501,368 (project site) [qbtc-site]; Date: 28 Dec 2017 (project site) [qbtc-site]; Ratio: 1:1 [qbtc-site]; Supply: 21.21 million, 210,000 pre-mined [qbtc-site]; Source code: Not found by this wiki [qbtc-site]", "aliases": "qbtc quantum", "refs": ["qbtc-site"], "url": "/wiki/quantum-bitcoin/"}, {"id": "quantum-bitcoin#takeover", "slug": "quantum-bitcoin", "title": "Quantum Bitcoin (QBTC)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: despite the name, nothing in Quantum Bitcoin's archived site describes quantum-resistant cryptography — compare Bitcoin Post-Quantum, which actually changed the signature scheme. [qbtc-site] [bpq-ann]", "aliases": "qbtc quantum", "refs": ["bpq-ann", "qbtc-site"], "url": "/wiki/quantum-bitcoin/"}, {"id": "quantum-bitcoin#853", "slug": "quantum-bitcoin", "title": "Quantum Bitcoin (QBTC)", "section": "Claims", "text": "The archived project site says “On December 28, 2017, QBTC split from block height 501368 of BTC main network successfully” with coins dropped “according to the 1:1 ratio” [qbtc-site]. It gives a total of 21.21 million QBTC, “of which 210,000 are pre-excavated for nodes” [qbtc-site].", "aliases": "qbtc quantum", "refs": ["qbtc-site"], "url": "/wiki/quantum-bitcoin/"}, {"id": "quantum-bitcoin#854", "slug": "quantum-bitcoin", "title": "Quantum Bitcoin (QBTC)", "section": "Features and founder", "text": "The site lists lightning network support, “8M large block”, zero knowledge proof and smart contracts, but no quantum-resistant signatures [qbtc-site]. It names Zhang Jianguo as founder [qbtc-site]. This wiki found no published source code; the claims are the project's own [qbtc-site].", "aliases": "qbtc quantum", "refs": ["qbtc-site"], "url": "/wiki/quantum-bitcoin/"}, {"id": "replay-protection-2017#infobox", "slug": "replay-protection-2017", "title": "Replay protection in the 2017 forks", "section": "Summary and infobox", "text": "How the 2017 forks did, or did not, make their transactions invalid on Bitcoin: Bitcoin Cash's SIGHASH_FORKID, its copies, and SegWit2x's late opt-in marker. Bitcoin Cash (Aug 2017): SIGHASH_FORKID (0x40) [rp-sighash]; Bitcoin Gold: Two-way SIGHASH_FORKID, fork ID 79 [btk-btg]; SegWit2x: Opt-in OP_RETURN “RP=!>1x” marker (PR #117/#134) [btc1-pr117]; SegWit2x outcome: PR closed 8 Nov 2017, same day as the suspension [btc1-pr134]; Copied by: BCP, Bithereum, Bitcoin Platinum, Bitcoin Uranium [bcp-readme] [bth2-readme] [btp-site] [bum-ann]", "aliases": "replay rp=!>1x sighash_forkid opt-in", "refs": ["bcp-readme", "btc1-pr117", "btc1-pr134", "bth2-readme", "btk-btg", "btp-site", "bum-ann", "rp-sighash"], "url": "/wiki/replay-protection-2017/"}, {"id": "replay-protection-2017#takeover", "slug": "replay-protection-2017", "title": "Replay protection in the 2017 forks", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: replay protection was the line between a fork that meant to be a separate coin and one that meant to replace Bitcoin. SegWit2x only proposed an opt-in version, and it was closed the day the fork was called off. [btc1-pr134] [s2x-suspend]", "aliases": "replay rp=!>1x sighash_forkid opt-in", "refs": ["btc1-pr134", "s2x-suspend"], "url": "/wiki/replay-protection-2017/"}, {"id": "replay-protection-2017#857", "slug": "replay-protection-2017", "title": "Replay protection in the 2017 forks", "section": "Bitcoin Cash and its copies", "text": "The Bitcoin Cash specification introduced a new signature digest used when the SIGHASH_FORKID bit is set [rp-sighash]. Bitcoin Gold used two-way SIGHASH_FORKID with fork ID 79 [btk-btg]. Later 2017–18 forks advertised the same idea: Bitcoin Cash Plus lists “2-way Replay protection (SIGHASH_FORK_ID)” and Bithereum “Replay protection (SIGHASH_FORK_ID)” [bcp-readme] [bth2-readme]. Bitcoin Platinum's site and Bitcoin Uranium's announcement also claimed replay protection [btp-site] [bum-ann].", "aliases": "replay rp=!>1x sighash_forkid opt-in", "refs": ["bcp-readme", "bth2-readme", "btk-btg", "btp-site", "bum-ann", "rp-sighash"], "url": "/wiki/replay-protection-2017/"}, {"id": "replay-protection-2017#858", "slug": "replay-protection-2017", "title": "Replay protection in the 2017 forks", "section": "SegWit2x", "text": "On 23 August 2017 Jeff Garzik opened btc1 pull request #117, “Add opt-in transaction avoidance”, based on a gist by Gavin Andresen [btc1-pr117]. Transactions with the marker “OP_RETURN 'RP=!>1x'” would be non-standard before the fork and invalid after the BIP102 hard fork point [btc1-pr117]. It was re-opened as #134 on 12 October 2017 and closed on 8 November 2017 with no GitHub merge recorded [btc1-pr134], the day SegWit2x was suspended [s2x-suspend].", "aliases": "replay rp=!>1x sighash_forkid opt-in", "refs": ["btc1-pr117", "btc1-pr134", "s2x-suspend"], "url": "/wiki/replay-protection-2017/"}, {"id": "replay-protection-2017#859", "slug": "replay-protection-2017", "title": "Replay protection in the 2017 forks", "section": "What is not sourced", "text": "This wiki has not found a primary source documenting specific losses from replayed transactions in 2017; such reports are marked unknown here [rp-sighash]. The general concept is covered under Replay protection [rp-sighash].", "aliases": "replay rp=!>1x sighash_forkid opt-in", "refs": ["rp-sighash"], "url": "/wiki/replay-protection-2017/"}, {"id": "replay-protection#infobox", "slug": "replay-protection", "title": "Replay protection", "section": "Summary and infobox", "text": "Making a transaction valid on only one side of a chain split, so that spending coins on one chain cannot be replayed on the other. Problem: A transaction signed on one chain can be valid on the other after a split [rp-sighash]; Bitcoin Cash method: SIGHASH_FORKID (0x40) with a 24-bit fork ID in the sighash type [rp-sighash]; Bitcoin Gold: Two-way SIGHASH_FORKID, fork ID 79 [btk-btg]; Counter-example: Bitcoin SV's node had none at the 2018 split, per Kurt Wuckert Jr. [ep-s17e39-replay]", "aliases": "replay sighash_forkid forkid", "refs": ["btk-btg", "ep-s17e39-replay", "rp-sighash"], "url": "/wiki/replay-protection/"}, {"id": "replay-protection#takeover", "slug": "replay-protection", "title": "Replay protection", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: replay protection is how a fork says it intends to be a separate coin. On the podcast, its absence in 2018 was cited as a sign of which side expected the split. [ep-s17e39-replay] [rp-sighash]", "aliases": "replay sighash_forkid forkid", "refs": ["ep-s17e39-replay", "rp-sighash"], "url": "/wiki/replay-protection/"}, {"id": "replay-protection#862", "slug": "replay-protection", "title": "Replay protection", "section": "The Bitcoin Cash approach", "text": "The Bitcoin Cash specification introduced a new signature digest that is used when the SIGHASH_FORKID bit (0x40) is set, and the reference implementation rejects such signatures before the UAHF activates [rp-sighash]. The sighash type is altered to include a 24-bit fork ID in its most significant bits [rp-sighash].", "aliases": "replay sighash_forkid forkid", "refs": ["rp-sighash"], "url": "/wiki/replay-protection/"}, {"id": "replay-protection#863", "slug": "replay-protection", "title": "Replay protection", "section": "Later forks", "text": "Bitcoin Gold used two-way SIGHASH_FORKID replay protection with fork ID 79 [btk-btg]. Bitcoin Diamond's README claims an anti-replay function in both directions, and Bitcoin Interest listed “Replay Protection (v2)” among its features [bcd-readme] [bci-readme].", "aliases": "replay sighash_forkid forkid", "refs": ["bcd-readme", "bci-readme", "btk-btg"], "url": "/wiki/replay-protection/"}, {"id": "replay-protection#864", "slug": "replay-protection", "title": "Replay protection", "section": "When it is missing", "text": "On S17 E39, Kurt Wuckert Jr. said the SV node “didn't have replay protection” at the November 2018 split, which forced the SV side to scramble because wallets stopped working [ep-s17e39-replay].", "aliases": "replay sighash_forkid forkid", "refs": ["ep-s17e39-replay"], "url": "/wiki/replay-protection/"}, {"id": "robin-linus#infobox", "slug": "robin-linus", "title": "Robin Linus", "section": "Summary and infobox", "text": "Author of the BitVM whitepaper, which verifies Turing-complete contracts on Bitcoin without a consensus change; a repeat Bitcoin Takeover guest. Known for: BitVM [bitvm-wp]; Whitepaper: “BitVM: Compute Anything on Bitcoin” [bitvm-wp]; GitHub bio: “Bitcoin scalability, privacy, and usability” [gh-linus]; Organization (GitHub): @BitVM [gh-linus]; On the show: S15 E13, S15 E58, S17 E4, S17 E48 [btk-feed]", "aliases": "robin linus bitvm", "refs": ["bitvm-wp", "btk-feed", "gh-linus"], "url": "/wiki/robin-linus/"}, {"id": "robin-linus#takeover", "slug": "robin-linus", "title": "Robin Linus", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Linus appears in four episode titles in the show's feed; on S17 E48 he predicted “We're going to get BIP 448, TEMPLATEHASH”. [btk-feed] [ep-s17e48-template]", "aliases": "robin linus bitvm", "refs": ["btk-feed", "ep-s17e48-template"], "url": "/wiki/robin-linus/"}, {"id": "robin-linus#867", "slug": "robin-linus", "title": "Robin Linus", "section": "BitVM", "text": "The whitepaper on bitvm.org, “BitVM: Compute Anything on Bitcoin” by Robin Linus, is dated 12 December 2023 [bitvm-wp]. Its abstract says “BitVM is a computing paradigm to express Turing-complete Bitcoin contracts” and that this “requires no changes to the network's consensus rules” [bitvm-wp]. Computations are not executed on Bitcoin but verified, and a false claim can be met with a fraud proof [bitvm-wp]. The project site calls BitVM the foundation “to bridge BTC to second layers” [bitvm-site].", "aliases": "robin linus bitvm", "refs": ["bitvm-site", "bitvm-wp"], "url": "/wiki/robin-linus/"}, {"id": "robin-linus#868", "slug": "robin-linus", "title": "Robin Linus", "section": "On Bitcoin Takeover", "text": "The show's feed lists “S15 E13: Robin Linus on BitVM & Permissionless Bitcoin Development”, an S15 E58 episode on shielded client-side validation, “S17 E4: {ideal} BitVM Optimizations” and “S17 E48: Robin Linus in the 1000 BTC Car, Driving to BitDevs Atlanta” [btk-feed]. On S17 E48 he said BIP 448 TEMPLATEHASH would “reduce the interactivity requirements of BitVM bridges” [ep-s17e48-template]. In the same episode he discussed Peter Todd's guess of a 2029 Great Consensus Cleanup [ep-s17e48-gcc].", "aliases": "robin linus bitvm", "refs": ["btk-feed", "ep-s17e48-gcc", "ep-s17e48-template"], "url": "/wiki/robin-linus/"}, {"id": "roger-ver#infobox", "slug": "roger-ver", "title": "Roger Ver", "section": "Summary and infobox", "text": "Early Bitcoin investor and leading Bitcoin Cash advocate; co-author of Hijacking Bitcoin (2024). Book: Hijacking Bitcoin (2024), with Steve Patterson [btk-forkwars]; Fork: Bitcoin Cash supporter [btk-bch]; Takeover episode: S15 E26 (2024) [ep-s15e26]", "aliases": "", "refs": ["btk-bch", "btk-forkwars", "ep-s15e26"], "url": "/wiki/roger-ver/"}, {"id": "roger-ver#takeover", "slug": "roger-ver", "title": "Roger Ver", "section": "Takeover view (editorial opinion)", "text": "His book and Jonathan Bier's The Blocksize War are compared point by point on Fork Wars. The wiki quotes neither at length. [btk-forkwars]", "aliases": "", "refs": ["btk-forkwars"], "url": "/wiki/roger-ver/"}, {"id": "roger-ver#871", "slug": "roger-ver", "title": "Roger Ver", "section": "Block size war", "text": "Roger Ver backed bigger blocks during the block size war and then Bitcoin Cash [btk-forkwars]. Vlad's magazine notes that Bitcoin.com became a BCH website in that period [btk-bch].", "aliases": "", "refs": ["btk-bch", "btk-forkwars"], "url": "/wiki/roger-ver/"}, {"id": "roger-ver#872", "slug": "roger-ver", "title": "Roger Ver", "section": "Hijacking Bitcoin", "text": "His 2024 book Hijacking Bitcoin, co-written with Steve Patterson, gives the big-block account of the war; Fork Wars sets it beside Jonathan Bier's The Blocksize War [btk-forkwars]. He discussed his views on Bitcoin Takeover S15 E26 [ep-s15e26].", "aliases": "", "refs": ["btk-forkwars", "ep-s15e26"], "url": "/wiki/roger-ver/"}, {"id": "roger-ver#873", "slug": "roger-ver", "title": "Roger Ver", "section": "Heard on Bitcoin Takeover", "text": "Asked about his allegiances on S15 E26 (March 2024), Roger Ver said: “I was never a BTC maximalist. I was never a BCH maximalist.” … “I've been a freedom maximalist the entire time.” [ep-s15e26-q326] He has also been the subject of other episodes: S16 E11, ‘Paul Sztorc on Roger Ver’ (March 2025) [btk-ep-s16e11]; S15 E31, ‘Ray Youssef on NoOnes & Why Roger Ver Was Right’ (April 2024) [btk-ep-s15e31].", "aliases": "", "refs": ["btk-ep-s15e31", "btk-ep-s16e11", "ep-s15e26-q326"], "url": "/wiki/roger-ver/"}, {"id": "ryan-x-charles#infobox", "slug": "ryan-x-charles", "title": "Ryan X. Charles", "section": "Summary and infobox", "text": "Developer who wrote Bitcore at BitPay and ran Money Button from 2015 to 2021; after the COPA trial, by Vlad's account, he was among those who said they had been fooled by Craig Wright. Later built EarthBucks. BitPay: 2013–14, “Wrote Bitcore” [rxc-site]; Money Button: 2015–21 [rxc-site]; Now: AI software (Astrohacker, Ironlight) [rxc-site]; Coinbase: “one of their founding engineers” (Kurt Wuckert Jr.'s account) [ep-s17e39-rxc]; Later project: EarthBucks [ep-s17e33-earthbucks]", "aliases": "ryan x charles moneybutton money button bitcore earthbucks", "refs": ["ep-s17e33-earthbucks", "ep-s17e39-rxc", "rxc-site"], "url": "/wiki/ryan-x-charles/"}, {"id": "ryan-x-charles#takeover", "slug": "ryan-x-charles", "title": "Ryan X. Charles", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Charles went from Bitcore to the BSV side to a public apology after the COPA trial, a path the show has followed across several episodes. [ep-s17e39-rxc-sorry] [rxc-site]", "aliases": "ryan x charles moneybutton money button bitcore earthbucks", "refs": ["ep-s17e39-rxc-sorry", "rxc-site"], "url": "/wiki/ryan-x-charles/"}, {"id": "ryan-x-charles#876", "slug": "ryan-x-charles", "title": "Ryan X. Charles", "section": "Career", "text": "Ryan X. Charles's site lists BitPay (2013–14), where he “Wrote Bitcore”, Money Button (2015–21), whose payment APIs it says processed $100M, and current work on AI software factories [rxc-site]. Kurt Wuckert Jr. said on S17 E39 that Charles “used to work at Coinbase” and was “one of their founding engineers”; this wiki has not checked that against a Coinbase source [ep-s17e39-rxc].", "aliases": "ryan x charles moneybutton money button bitcore earthbucks", "refs": ["ep-s17e39-rxc", "rxc-site"], "url": "/wiki/ryan-x-charles/"}, {"id": "ryan-x-charles#877", "slug": "ryan-x-charles", "title": "Ryan X. Charles", "section": "After COPA", "text": "Kurt recalled that after the 2018 hash war Charles was among those who “ended up on the SV side” [ep-s17e39-rxc]. Vlad said in the same episode that after the COPA trial “Ryan X. Charles and a bunch of others decided that it's a good moment to say that they're sorry because they have been fooled” [ep-s17e39-rxc-sorry]. Joël Valenzuela described Charles's later EarthBucks project, where “Address reuse is banned at the protocol level” [ep-s17e33-earthbucks].", "aliases": "ryan x charles moneybutton money button bitcore earthbucks", "refs": ["ep-s17e33-earthbucks", "ep-s17e39-rxc", "ep-s17e39-rxc-sorry"], "url": "/wiki/ryan-x-charles/"}, {"id": "samson-mow#infobox", "slug": "samson-mow", "title": "Samson Mow", "section": "Summary and infobox", "text": "BTCC's chief operating officer at the 2016 Hong Kong Roundtable and now CEO of JAN3; his Blockstream years are not yet sourced here. 2016 role: COO, BTCC (Hong Kong Roundtable signatory) [hk-letter]; Later: Blockstream [jan3-about]; Current role: Chief Executive Officer, JAN3 [jan3-about]; Before Bitcoin: Credited on the games Dawn of War and Company of Heroes [jan3-about]", "aliases": "samson jan3", "refs": ["hk-letter", "jan3-about"], "url": "/wiki/samson-mow/"}, {"id": "samson-mow#takeover", "slug": "samson-mow", "title": "Samson Mow", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Vlad's own read on S17 E26 was that in the 2018 debate with Roger Ver, “in many ways, he [Roger] was right”, recalling Mow answering that Lightning could buy hats in his store. [ep-s17e26-samson]", "aliases": "samson jan3", "refs": ["ep-s17e26-samson"], "url": "/wiki/samson-mow/"}, {"id": "samson-mow#880", "slug": "samson-mow", "title": "Samson Mow", "section": "BTCC and Hong Kong", "text": "The February 2016 Bitcoin Roundtable statement lists Samson Mow as COO of BTCC, next to BTCC's CEO Bobby Lee [hk-letter]. See Hong Kong Roundtable.", "aliases": "samson jan3", "refs": ["hk-letter"], "url": "/wiki/samson-mow/"}, {"id": "samson-mow#881", "slug": "samson-mow", "title": "Samson Mow", "section": "Blockstream and JAN3", "text": "JAN3's team page names Mow as Chief Executive Officer and credits him on two real-time strategy games, “Dawn of War” and “Company of Heroes” [jan3-about]. The same page says JAN3's director of finance previously “was at Blockstream working alongside Samson Mow” [jan3-about]. His exact title and dates at Blockstream are not verified in this wiki [jan3-about].", "aliases": "samson jan3", "refs": ["jan3-about"], "url": "/wiki/samson-mow/"}, {"id": "samson-mow#882", "slug": "samson-mow", "title": "Samson Mow", "section": "On the podcast", "text": "On S17 E26 Vlad recalled a 2018 debate, which he placed at Deconomy in South Korea, between Roger Ver and Mow [ep-s17e26-samson]. Vlad recalled Roger asking what Lightning could buy, and Mow answering that you could buy hats in his store [ep-s17e26-samson].", "aliases": "samson jan3", "refs": ["ep-s17e26-samson"], "url": "/wiki/samson-mow/"}, {"id": "segregated-witness#infobox", "slug": "segregated-witness", "title": "Segregated Witness", "section": "Summary and infobox", "text": "The 2017 soft fork that moved signatures out of the legacy block, fixed malleability and became the centre of the block size war. BIPs: BIP-141, BIP-143, BIP-147 (BIP-144 for P2P) [btk-allforks]; Deployment: BIP-9 bit 1, helped by BIP-91 and BIP-148 [btk-allforks]; Locked in: From block 479,808 (9 August 2017) [btk-allforks]; Active: Block 481,824, 24 August 2017 [btk-allforks]; Block weight: 4,000,000 weight units [s2x-announce]; Rejected by: Bitcoin Cash; kept by Bitcoin Gold [btk-btg]", "aliases": "segwit bip141 witness", "refs": ["btk-allforks", "btk-btg", "s2x-announce"], "url": "/wiki/segregated-witness/"}, {"id": "segregated-witness#takeover", "slug": "segregated-witness", "title": "Segregated Witness", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: SegWit is the reason most of the forks in this wiki exist. Bitcoin Cash split on 1 August 2017 rather than accept it. [btk-bch] [btk-allforks]", "aliases": "segwit bip141 witness", "refs": ["btk-allforks", "btk-bch"], "url": "/wiki/segregated-witness/"}, {"id": "segregated-witness#885", "slug": "segregated-witness", "title": "Segregated Witness", "section": "What it changed", "text": "BIP-141 specifies Segregated Witness at the consensus layer [bip141]. The SegWit2x announcement summarised what it required of upgrading software: changes to transaction serialisation, signature hashing, block weight, the scripting engine, a new address scheme and P2P messages, while noting that SegWit was opt-in for existing wallets [s2x-announce].", "aliases": "segwit bip141 witness", "refs": ["bip141", "s2x-announce"], "url": "/wiki/segregated-witness/"}, {"id": "segregated-witness#886", "slug": "segregated-witness", "title": "Segregated Witness", "section": "Activation", "text": "Bitcoin Takeover's fork table records SegWit as a BIP-9 deployment on bit 1 that locked in from block 479,808 and became active at block 481,824 on 24 August 2017, “pushed over the line by BIP91 and BIP148” [btk-allforks]. See UASF (BIP-148) and New York Agreement.", "aliases": "segwit bip141 witness", "refs": ["btk-allforks"], "url": "/wiki/segregated-witness/"}, {"id": "segregated-witness#887", "slug": "segregated-witness", "title": "Segregated Witness", "section": "Forks over SegWit", "text": "Bitcoin Cash split from Bitcoin on 1 August 2017, before SegWit activated [btk-bch]. Bitcoin Gold, by contrast, kept SegWit [btk-btg]. The 2016 Hong Kong Roundtable had planned SegWit first and a hard fork afterwards [hk-letter].", "aliases": "segwit bip141 witness", "refs": ["btk-bch", "btk-btg", "hk-letter"], "url": "/wiki/segregated-witness/"}, {"id": "segwit2x#infobox", "slug": "segwit2x", "title": "SegWit2x", "section": "Summary and infobox", "text": "The planned 2 MB hard fork that was meant to follow SegWit under the New York Agreement, suspended a week before its block height. Type: Planned hard fork after the SegWit soft fork; never executed [s2x-announce]; Agreement: New York Agreement, 23 May 2017 [nya-letter]; Planned height: Block 494,784, about 90 days after SegWit activation [s2x-announce]; Planned change: Base block 1 MB to 2 MB; block weight 4,000,000 to 8,000,000 [s2x-announce]; Suspended: 8 November 2017 [s2x-suspend]; Signatories of suspension: Mike Belshe, Wences Casares, Jihan Wu, Jeff Garzik, Peter Smith, Erik Voorhees [s2x-suspend]", "aliases": "b2x btc1 2x nya 2mb", "refs": ["nya-letter", "s2x-announce", "s2x-suspend"], "url": "/wiki/segwit2x/"}, {"id": "segwit2x#takeover", "slug": "segwit2x", "title": "SegWit2x", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: SegWit2x is the half of a deal that never shipped. The SegWit half activated in August 2017; the 2 MB half was suspended, which Bitcoin Takeover's fork table treats as the end of hard-fork attempts on the main chain. [btk-allforks] [s2x-suspend]", "aliases": "b2x btc1 2x nya 2mb", "refs": ["btk-allforks", "s2x-suspend"], "url": "/wiki/segwit2x/"}, {"id": "segwit2x#890", "slug": "segwit2x", "title": "SegWit2x", "section": "The plan", "text": "The SegWit2x project announced that about 90 days after SegWit activated, miners would produce a block between 1 MB and 2 MB, and it expected more than 90% of hashpower to keep mining on top of it [s2x-announce]. Most clients would only need to change two constants: maximum block weight from 4,000,000 to 8,000,000 and sigops per block from 80,000 to 160,000 [s2x-announce].", "aliases": "b2x btc1 2x nya 2mb", "refs": ["s2x-announce"], "url": "/wiki/segwit2x/"}, {"id": "segwit2x#891", "slug": "segwit2x", "title": "SegWit2x", "section": "Where it came from", "text": "The announcement says the 2 MB upgrade was first agreed at the Bitcoin Roundtable in Hong Kong in February 2016 and ratified by the New York Agreement in May 2017 [s2x-announce]. The New York text committed signers to activate SegWit at an 80% threshold signalling on bit 4, and to activate a 2 MB hard fork within six months [nya-letter].", "aliases": "b2x btc1 2x nya 2mb", "refs": ["nya-letter", "s2x-announce"], "url": "/wiki/segwit2x/"}, {"id": "segwit2x#892", "slug": "segwit2x", "title": "SegWit2x", "section": "Suspension", "text": "On 8 November 2017 Mike Belshe posted that “it is clear that we have not built sufficient consensus for a clean blocksize upgrade at this time” and that the group was “suspending our plans for the upcoming 2MB upgrade” [s2x-suspend]. The message was signed by Belshe, Wences Casares, Jihan Wu, Jeff Garzik, Peter Smith and Erik Voorhees [s2x-suspend].", "aliases": "b2x btc1 2x nya 2mb", "refs": ["s2x-suspend"], "url": "/wiki/segwit2x/"}, {"id": "segwit2x#893", "slug": "segwit2x", "title": "SegWit2x", "section": "Aftermath on the podcast", "text": "On S16 E60, Jonathan Bier recalled that after the cancellation email the Bitcoin Cash price briefly reached about 51% of Bitcoin's, a moment he attributes largely to retail speculation on Korean exchanges [ep-s16e60-2x]. On S17 E19, Amaury Séchet said Roger Ver joined Bitcoin Cash only after SegWit2x failed, “two months later … something like that”, a recollection this wiki has not checked against the record [ep-s17e19-roger2x].", "aliases": "b2x btc1 2x nya 2mb", "refs": ["ep-s16e60-2x", "ep-s17e19-roger2x"], "url": "/wiki/segwit2x/"}, {"id": "segwit2x#894", "slug": "segwit2x", "title": "SegWit2x", "section": "Heard on Bitcoin Takeover", "text": "BTCPay Server creator Nicolas Dorier said on S15 E14 (December 2023): “I was definitely against SegWit2x. It's basically what made me start BTCPay Server”. [ep-s15e14-q1542] In the same episode he summarised the 2017 split: “Most developers were for just SegWit. Most big companies were for SegWit2x, most miners were for SegWit2x.” [ep-s15e14-q1752]", "aliases": "b2x btc1 2x nya 2mb", "refs": ["ep-s15e14-q1542", "ep-s15e14-q1752"], "url": "/wiki/segwit2x/"}, {"id": "semux#infobox", "slug": "semux", "title": "Semux (SEM)", "section": "Summary and infobox", "text": "A 2017 BFT smart-contract platform that forkdrop lists as a registration airdrop keyed to Bitcoin block 480,000. Consensus: Semux BFT [sem-ann]; Block time: 30 seconds [sem-ann]; Airdrop height (forkdrop): 480,000 [fd-data]; Block 480,000 time: 2017-08-10 23:25:59 UTC [btc-480000]; Max supply (forkdrop): 100,000,000 [fd-data]", "aliases": "sem semux bft", "refs": ["btc-480000", "fd-data", "sem-ann"], "url": "/wiki/semux/"}, {"id": "semux#takeover", "slug": "semux", "title": "Semux (SEM)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Semux is an unrelated chain that used a Bitcoin-holder registration airdrop to find users. [fd-data]", "aliases": "sem semux bft", "refs": ["fd-data"], "url": "/wiki/semux/"}, {"id": "semux#897", "slug": "semux", "title": "Semux (SEM)", "section": "Design", "text": "The Bitcointalk thread, opened on 7 September 2017, says “Semux is a decentralized application platform, powered by the Semux BFT consensus engine” and lists a 30-second block time [sem-ann].", "aliases": "sem semux bft", "refs": ["sem-ann"], "url": "/wiki/semux/"}, {"id": "semux#898", "slug": "semux", "title": "Semux (SEM)", "section": "Airdrop", "text": "forkdrop's data file lists Semux as a registration airdrop at block 480000 on 2017-08-10, with no ratio, a maximum supply of 100,000,000 and the reason “Airdrop Over” [fd-data]. Block 480,000 was mined on 10 August 2017 [btc-480000]. The first post as edited in August 2019 does not describe the airdrop, so its terms are unverified [sem-ann].", "aliases": "sem semux bft", "refs": ["btc-480000", "fd-data", "sem-ann"], "url": "/wiki/semux/"}, {"id": "smart-bitcoin#infobox", "slug": "smart-bitcoin", "title": "Smart Bitcoin (SBC)", "section": "Summary and infobox", "text": "An April 2018 fork at block 520,000 that pitched DPoS, 3,000 TPS and atomic swaps with EOS; no source code was found. Fork height: 520,000 [bth-review]; Block 520,000 time: 2018-04-26 10:40:17 UTC [btc-520000]; Consensus: DPoS [sbc-site]; Claimed throughput: Up to 3000 TPS [sbc-site]; Source code: “no source code available” [bth-review]", "aliases": "sbc smart bitcoin dpos", "refs": ["btc-520000", "bth-review", "sbc-site"], "url": "/wiki/smart-bitcoin/"}, {"id": "smart-bitcoin#takeover", "slug": "smart-bitcoin", "title": "Smart Bitcoin (SBC)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Smart Bitcoin's site listed the exchanges that had agreed to snapshot balances for it — a distribution announced through exchanges as much as through code. [sbc-site]", "aliases": "sbc smart bitcoin dpos", "refs": ["sbc-site"], "url": "/wiki/smart-bitcoin/"}, {"id": "smart-bitcoin#901", "slug": "smart-bitcoin", "title": "Smart Bitcoin (SBC)", "section": "Pitch", "text": "The archived site, captured on 21 May 2018, offers to “Make Bitcoin faster and smarter” [sbc-site]. It says “SBC is capable of handling up to 3000 TPS” and that adopting DPoS consensus would cut energy use [sbc-site]. It promises “atomic cross-chain trading between EOS, ONE and SBC” [sbc-site].", "aliases": "sbc smart bitcoin dpos", "refs": ["sbc-site"], "url": "/wiki/smart-bitcoin/"}, {"id": "smart-bitcoin#902", "slug": "smart-bitcoin", "title": "Smart Bitcoin (SBC)", "section": "Snapshots", "text": "The site says exchanges that “already agreed to take snapshot for SBC are: Huobi, AEX(btc38), Octaex, GBCAX, Bitpie” [sbc-site]. Wallet holders were told SBC would be added to their private key and to claim it “under the official guidance” [sbc-site].", "aliases": "sbc smart bitcoin dpos", "refs": ["sbc-site"], "url": "/wiki/smart-bitcoin/"}, {"id": "smart-bitcoin#903", "slug": "smart-bitcoin", "title": "Smart Bitcoin (SBC)", "section": "Record", "text": "The 2019 fork list gives “fork at 520000” and “no source code available” [bth-review]. Block 520,000 was mined on 26 April 2018 [btc-520000]. It should not be confused with Bitcoin Smart (BCS) [bth-review].", "aliases": "sbc smart bitcoin dpos", "refs": ["btc-520000", "bth-review"], "url": "/wiki/smart-bitcoin/"}, {"id": "snapshot-forks#infobox", "slug": "snapshot-forks", "title": "Snapshot forks vs chain splits", "section": "Summary and infobox", "text": "Why some “forks” share Bitcoin's history and others only copy its balances, and why it matters for claiming coins. Chain split: New chain shares Bitcoin's history up to the fork block [btt-readme]; Snapshot fork: “no shared pre-fork blockchain history” [bth-review]; Examples (2019 list): Bitcoin CBC, Bitcoin Pizza, Bitcoin 2, Bitcoin Private [bth-review]; Exchange snapshots: Bitcoin Pay, Smart Bitcoin, Bitcoin Ore [bpay-site] [sbc-site] [bco-site]", "aliases": "snapshot fork chain split airdrop", "refs": ["bco-site", "bpay-site", "bth-review", "btt-readme", "sbc-site"], "url": "/wiki/snapshot-forks/"}, {"id": "snapshot-forks#takeover", "slug": "snapshot-forks", "title": "Snapshot forks vs chain splits", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: whether a fork kept Bitcoin's history decides what holding at a fork block meant — a key in a wallet, or a row in an exchange's database. [bth-review] [sbc-site]", "aliases": "snapshot fork chain split airdrop", "refs": ["bth-review", "sbc-site"], "url": "/wiki/snapshot-forks/"}, {"id": "snapshot-forks#906", "slug": "snapshot-forks", "title": "Snapshot forks vs chain splits", "section": "Chain splits", "text": "In a chain split the new coin keeps Bitcoin's blocks up to the fork. The Bitcoin Top README puts it this way: “It shares the same transaction history with Bitcoin until it starts branching” [btt-readme]. The 2019 fork reviewer tested such coins by importing “all the shared pre-fork blockchain data” and swapping in his Bitcoin Core wallet.dat [bth-review].", "aliases": "snapshot fork chain split airdrop", "refs": ["bth-review", "btt-readme"], "url": "/wiki/snapshot-forks/"}, {"id": "snapshot-forks#907", "slug": "snapshot-forks", "title": "Snapshot forks vs chain splits", "section": "Snapshot forks", "text": "The same list marks four coins as “snapshot fork (no shared pre-fork blockchain history)”: Bitcoin CBC, Bitcoin Pizza, Bitcoin 2 and Bitcoin Private [bth-review]. For Bitcoin 2 it quotes the plan that “the blockchain data will be pruned from over 150 GB to around 2 GB” [bth-review]. Bitcoin Private's README describes it as “a fork of Zclassic, merging in a snapshotted UTXO set of Bitcoin” [btcp-readme]. BitcoinCash Zero went further and announced snapshots of four chains at once [bcz-ann].", "aliases": "snapshot fork chain split airdrop", "refs": ["bcz-ann", "btcp-readme", "bth-review"], "url": "/wiki/snapshot-forks/"}, {"id": "snapshot-forks#908", "slug": "snapshot-forks", "title": "Snapshot forks vs chain splits", "section": "Exchange snapshots", "text": "Some forks handed the snapshot to exchanges. Bitcoin Pay said “EXX.COM And OURDAX.COM A snapshot has been given first” [bpay-site]. Smart Bitcoin listed exchanges that had “agreed to take snapshot” for it [sbc-site]. Bitcoin Ore issued its first coins only “to users of these four exchanges at block height of 501949” [bco-site]. New Bitcoin called itself a snapshot fork (“快照分叉”) at block 501225 [nbtc-site].", "aliases": "snapshot fork chain split airdrop", "refs": ["bco-site", "bpay-site", "nbtc-site", "sbc-site"], "url": "/wiki/snapshot-forks/"}, {"id": "solidcoin#infobox", "slug": "solidcoin", "title": "SolidCoin (SC)", "section": "Summary and infobox", "text": "An August 2011 Bitcoin code fork by CoinHunter (RealSolid) with 3-minute blocks and fixed fees, whose incompatible 2.0 chain and hostile posts made it a byword of the early altcoin era. Started: 20 Aug 2011 (announced 21 Aug) [slc-ann]; Creator: CoinHunter on Bitcointalk; RealSolid in the Litecoin Wiki [ltcwiki-history]; Premine: “940 blocks or 30080 coins” for bounties [slc-ann]; Block time and reward: 3 minutes, 32 SC [slc-ann]; Max supply: 18.9 million by ~2022 [slc-ann]; SolidCoin 2.0: New block format and hashing algorithm (Sep 2011) [slc-v2]", "aliases": "solidcoin coinhunter realsolid", "refs": ["ltcwiki-history", "slc-ann", "slc-v2"], "url": "/wiki/solidcoin/"}, {"id": "solidcoin#takeover", "slug": "solidcoin", "title": "SolidCoin (SC)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: SolidCoin's founder called Tenebrix a dead chain and Litecoin a dying copy in October 2011; the record shows which of those predictions aged badly. [slc-gpu] [ltcwiki-history]", "aliases": "solidcoin coinhunter realsolid", "refs": ["ltcwiki-history", "slc-gpu"], "url": "/wiki/solidcoin/"}, {"id": "solidcoin#911", "slug": "solidcoin", "title": "SolidCoin (SC)", "section": "Launch", "text": "CoinHunter's announcement of 21 August 2011 describes SolidCoin as “based on the cryptocurrency Bitcoin” and says it “officially started on the 20th of August 2011” [slc-ann]. It says “Only 940 blocks or 30080 coins were premined for bounties” and lists 3-minute blocks, 32 SolidCoins per block, twice-daily retargets, fixed transaction fees and a maximum of 18.9 million coins by about 2022 [slc-ann]. The Litecoin Wiki credits SolidCoin to RealSolid on 21.08.2011 [ltcwiki-history].", "aliases": "solidcoin coinhunter realsolid", "refs": ["ltcwiki-history", "slc-ann"], "url": "/wiki/solidcoin/"}, {"id": "solidcoin#912", "slug": "solidcoin", "title": "SolidCoin (SC)", "section": "SolidCoin 2.0", "text": "On 17 September 2011 CoinHunter wrote that in SolidCoin v2.0 “the blockchain format has changed” and that block headers would be hashed so that CPUs were more efficient [slc-v2]. On 21 October 2011 he called Tenebrix “now a dead chain” and wrote of “fairbrix/litecoin since they are both also dying and just copied tenebrix” [slc-gpu].", "aliases": "solidcoin coinhunter realsolid", "refs": ["slc-gpu", "slc-v2"], "url": "/wiki/solidcoin/"}, {"id": "speedy-trial#infobox", "slug": "speedy-trial", "title": "Speedy Trial", "section": "Summary and infobox", "text": "The 2021 version-bits variant used to activate Taproot: a short miner-signalling window at 90% with a delayed minimum activation height. Core PR: #21377 “Speedy trial support for versionbits” (ajtowns) [core-pr21377]; Merged: 15 Apr 2021 [core-pr21377]; Threshold: 1,815 of 2,016 blocks (90%) [btk-allforks]; Window: About three months, plus min_activation_height [btk-allforks]; Used for: Taproot, locked in within seven weeks [btk-allforks]", "aliases": "speedy trial 21377 min_activation_height", "refs": ["btk-allforks", "core-pr21377"], "url": "/wiki/speedy-trial/"}, {"id": "speedy-trial#takeover", "slug": "speedy-trial", "title": "Speedy Trial", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: after the 2017 war, Core chose an activation method that gave miners a short, high-threshold vote and nothing more, while a separate LOT=true client stayed compatible with it. [btk-allforks] [bip341]", "aliases": "speedy trial 21377 min_activation_height", "refs": ["bip341", "btk-allforks"], "url": "/wiki/speedy-trial/"}, {"id": "speedy-trial#915", "slug": "speedy-trial", "title": "Speedy Trial", "section": "Mechanism", "text": "Bitcoin Core PR #21377, “Speedy trial support for versionbits”, was opened by ajtowns on 6 March 2021 and merged on 15 April 2021 [core-pr21377]. The Takeover forks overview describes Speedy Trial as a BIP-9 variant described in BIP-341 with a short signalling window of about three months, a 90% threshold of 1,815 of 2,016 blocks, and a min_activation_height that delays enforcement [btk-allforks]. Bitcoin Core 0.21.1 shipped the Taproot deployment parameters [core-0211].", "aliases": "speedy trial 21377 min_activation_height", "refs": ["btk-allforks", "core-0211", "core-pr21377"], "url": "/wiki/speedy-trial/"}, {"id": "speedy-trial#916", "slug": "speedy-trial", "title": "Speedy Trial", "section": "Reception", "text": "The overview records that Taproot “Locked in within seven weeks” [btk-allforks]. On S15 E50 Vlad described a developer who “got some backlash from the community because he went for activation via speedy trial” [ep-s15e50-st].", "aliases": "speedy trial 21377 min_activation_height", "refs": ["btk-allforks", "ep-s15e50-st"], "url": "/wiki/speedy-trial/"}, {"id": "start9#infobox", "slug": "start9", "title": "Start9", "section": "Summary and infobox", "text": "Maker of StartOS and home servers for self-hosting, which Keagan McClelland says grew out of a group of core engineers leaving Salt Lending in 2019. Origin: Engineers leaving Salt Lending, 2019 [ep-s17e38-start9]; Product: StartOS, “an open-source Linux distribution for running a personal server” [startos-readme]; StartOS 0.4.0: “a ground-up rewrite of the operating system for your personal data center” [start9-site]; Hardware: Server One; a RISC-V router running StartWRT [start9-site]", "aliases": "start9 startos matt hill", "refs": ["ep-s17e38-start9", "start9-site", "startos-readme"], "url": "/wiki/start9/"}, {"id": "start9#takeover", "slug": "start9", "title": "Start9", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: on S17 E38 Vlad said Start9's Matt Hill is “a very hardcore supporter of BIP 110”, while adding that he could not blame him for siding with his customers. [ep-s17e38-hill]", "aliases": "start9 startos matt hill", "refs": ["ep-s17e38-hill"], "url": "/wiki/start9/"}, {"id": "start9#919", "slug": "start9", "title": "Start9", "section": "Origin", "text": "On S17 E38 Keagan McClelland said that in 2019 a group of core engineers left Salt Lending and “Start9 is what came out of that” [ep-s17e38-start9]. He said Start9 “got started” in the summer of 2019 [ep-s17e38-judica].", "aliases": "start9 startos matt hill", "refs": ["ep-s17e38-judica", "ep-s17e38-start9"], "url": "/wiki/start9/"}, {"id": "start9#920", "slug": "start9", "title": "Start9", "section": "Products", "text": "The Start9 GitHub monorepo calls its flagship StartOS “an open-source Linux distribution for running a personal server” that handles installation, networking and backups of self-hosted services [startos-readme]. The company's site describes StartOS 0.4.0 as “a ground-up rewrite of the operating system for your personal data center” after nearly three years of work [start9-site]. It also sells Server One and a RISC-V router running StartWRT [start9-site].", "aliases": "start9 startos matt hill", "refs": ["start9-site", "startos-readme"], "url": "/wiki/start9/"}, {"id": "start9#921", "slug": "start9", "title": "Start9", "section": "BIP-110", "text": "Vlad said on S17 E38 that he does not agree with Start9's Matt Hill much nowadays “because he's a very hardcore supporter of BIP 110” [ep-s17e38-hill]. See BIP-110 [ep-s17e38-hill].", "aliases": "start9 startos matt hill", "refs": ["ep-s17e38-hill"], "url": "/wiki/start9/"}, {"id": "super-bitcoin#infobox", "slug": "super-bitcoin", "title": "Super Bitcoin", "section": "Summary and infobox", "text": "A December 2017 fork marketed with smart contracts and 8 MB blocks, listed by a long roster of exchanges at launch. Fork height: Block 498,888 [sbtc-ann]; Fork time: Bitcoin block 498,888, header time 12 December 2017 10:29:53 UTC [btc-498888]; Self-description: “An experimental hard fork of Bitcoin” [sbtc-readme]; Marketing: Smart contracts, 8 MB blocks, privacy [sbtc-ann]; Exchanges at launch: OKEx, Huobi, Bitfinex, Binance, HitBTC and others announced support [sbtc-ann]", "aliases": "sbtc", "refs": ["btc-498888", "sbtc-ann", "sbtc-readme"], "url": "/wiki/super-bitcoin/"}, {"id": "super-bitcoin#takeover", "slug": "super-bitcoin", "title": "Super Bitcoin", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Super Bitcoin shows how cheaply exchange support came in December 2017. Twenty-plus venues announced support for a fork whose own README called it experimental. [sbtc-ann] [sbtc-readme]", "aliases": "sbtc", "refs": ["sbtc-ann", "sbtc-readme"], "url": "/wiki/super-bitcoin/"}, {"id": "super-bitcoin#924", "slug": "super-bitcoin", "title": "Super Bitcoin", "section": "Launch", "text": "The official announcement thread states that the fork happened at block height 498,888 [sbtc-ann]. Bitcoin block 498,888 has a header time of 12 December 2017, 10:29:53 UTC [btc-498888].", "aliases": "sbtc", "refs": ["btc-498888", "sbtc-ann"], "url": "/wiki/super-bitcoin/"}, {"id": "super-bitcoin#925", "slug": "super-bitcoin", "title": "Super Bitcoin", "section": "Pitch", "text": "The project's README calls Super Bitcoin “an experimental hard fork of Bitcoin” that tries to implement features Bitcoin community members had long requested [sbtc-readme]. Its announcement thread headline advertised smart contracts, 8 MB blocks and privacy, and listed more than twenty exchanges that supported the fork, including OKEx, Huobi, Bitfinex, Binance and HitBTC [sbtc-ann].", "aliases": "sbtc", "refs": ["sbtc-ann", "sbtc-readme"], "url": "/wiki/super-bitcoin/"}, {"id": "syscoin#infobox", "slug": "syscoin", "title": "Syscoin (SYS)", "section": "Summary and infobox", "text": "A merge-minable SHA-256 coin with masternodes, ZDAG fast payments and an EVM-compatible NEVM layer. Mining: SHA-256, mineable alone or merge-mined with any SHA-256 coin [sys-readme]; AuxPoW chain ID: 16 [sys-chainparams]; Current mainnet genesis: 1559520000 (3 June 2019) [sys-chainparams]; Features: ZDAG, masternodes, NEVM [sys-readme]; Masternode collateral: 100,000 SYS [sys-readme]", "aliases": "sys zdag nevm", "refs": ["sys-chainparams", "sys-readme"], "url": "/wiki/syscoin/"}, {"id": "syscoin#takeover", "slug": "syscoin", "title": "Syscoin (SYS)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Syscoin rides on Bitcoin's hashpower through merged mining instead of competing for it, the same route Namecoin opened in 2011. [sys-readme] [sys-chainparams]", "aliases": "sys zdag nevm", "refs": ["sys-chainparams", "sys-readme"], "url": "/wiki/syscoin/"}, {"id": "syscoin#928", "slug": "syscoin", "title": "Syscoin (SYS)", "section": "Design", "text": "The Syscoin Core README calls Syscoin “a merge-minable SHA256 coin which provides an array of useful services which leverage the bitcoin protocol and blockchain technology” [sys-readme]. It lists masternodes with a 100,000 SYS collateral, ZDAG technology for point-of-sale speeds and an EVM-compatible NEVM layer, and says the coin is “Mineable either exclusively or via merge-mining any SHA256 PoW coin” [sys-readme].", "aliases": "sys zdag nevm", "refs": ["sys-readme"], "url": "/wiki/syscoin/"}, {"id": "syscoin#929", "slug": "syscoin", "title": "Syscoin (SYS)", "section": "Chain parameters", "text": "The current chain parameters set an AuxPoW chain ID of 16 for merged mining and a mainnet genesis timestamp of 1559520000, 3 June 2019 [sys-chainparams]. That genesis reuses Bitcoin's “The Times 03/Jan/2009” text [sys-chainparams]. The history of Syscoin before this genesis is not yet sourced in this wiki and is marked unknown [sys-chainparams].", "aliases": "sys zdag nevm", "refs": ["sys-chainparams"], "url": "/wiki/syscoin/"}, {"id": "taproot-activation#infobox", "slug": "taproot-activation", "title": "Taproot activation (2021)", "section": "Summary and infobox", "text": "The Schnorr/Taproot soft fork, signalled through Speedy Trial in 2021, locked in at block 687,285 and activated at block 709,632 on 14 November 2021. BIPs: 340 (Schnorr), 341 (Taproot), 342 (Tapscript) [bip341]; Mechanism: Speedy Trial: BIP9 variant, bit 2, 90% of 2,016 blocks [core-0211]; Client: Bitcoin Core 0.21.1 [core-0211]; Locked in: Block 687,285, 12 June 2021 [btk-allforks]; Activated: Block 709,632, 2021-11-14 05:15:27 UTC [btk-allforks]", "aliases": "taproot speedy trial schnorr 709632 bip341", "refs": ["bip341", "btk-allforks", "core-0211"], "url": "/wiki/taproot-activation/"}, {"id": "taproot-activation#takeover", "slug": "taproot-activation", "title": "Taproot activation (2021)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Taproot is the last soft fork Bitcoin activated, and it turned out to be the one whose most popular use nobody planned. Murch on S15 E50 rejected “Taproot caused ordinals” but admitted the inscription boom saddened him. [ep-s15e50-ordinals] [btk-allforks]", "aliases": "taproot speedy trial schnorr 709632 bip341", "refs": ["btk-allforks", "ep-s15e50-ordinals"], "url": "/wiki/taproot-activation/"}, {"id": "taproot-activation#932", "slug": "taproot-activation", "title": "Taproot activation (2021)", "section": "The specifications", "text": "Taproot is defined in BIP-341 with Schnorr signatures in BIP-340 and Tapscript in BIP-342 [bip341] [bip340] [bip342]. Bitcoin Takeover's fork history summarises it as introducing Schnorr signatures and an output type in which “a single key and a tree of scripts look identical on chain” [btk-allforks].", "aliases": "taproot speedy trial schnorr 709632 bip341", "refs": ["bip340", "bip341", "bip342", "btk-allforks"], "url": "/wiki/taproot-activation/"}, {"id": "taproot-activation#933", "slug": "taproot-activation", "title": "Taproot activation (2021)", "section": "Speedy Trial", "text": "The Bitcoin Core 0.21.1 release notes say activation used “a variation of BIP9 versionbits called Speedy Trial”, on bit 2, with lock-in if 90% of blocks in a 2,016-block period signalled before the timeout, and activation at block 709,632 [core-0211]. BIP-8, the height-based alternative with an optional forced lock-in, was debated but never used on mainnet, Bitcoin Takeover's history notes [btk-allforks] [bip8].", "aliases": "taproot speedy trial schnorr 709632 bip341", "refs": ["bip8", "btk-allforks", "core-0211"], "url": "/wiki/taproot-activation/"}, {"id": "taproot-activation#934", "slug": "taproot-activation", "title": "Taproot activation (2021)", "section": "Lock-in and activation", "text": "Taproot locked in at block 687,285 on 12 June 2021, “within seven weeks” of signalling, and activated at block 709,632 with a header time of 05:15:27 UTC on 14 November 2021 [btk-allforks]. BIP-341 itself records: “The deployment did activate at height 709632 on Bitcoin mainnet” [bip341].", "aliases": "taproot speedy trial schnorr 709632 bip341", "refs": ["bip341", "btk-allforks"], "url": "/wiki/taproot-activation/"}, {"id": "taproot-activation#935", "slug": "taproot-activation", "title": "Taproot activation (2021)", "section": "After activation", "text": "On S15 E50 Murch said Taproot had been discussed for about five years before it activated [ep-s15e50-taproot]. He called the claim that Taproot caused ordinals not tenable, while saying the use for inscriptions “saddens me greatly” [ep-s15e50-ordinals]. BIP-110's 2026 restrictions on Taproot features are covered under Bitcoin Knots [btk-blake].", "aliases": "taproot speedy trial schnorr 709632 bip341", "refs": ["btk-blake", "ep-s15e50-ordinals", "ep-s15e50-taproot"], "url": "/wiki/taproot-activation/"}, {"id": "tenebrix-and-fairbrix#infobox", "slug": "tenebrix-and-fairbrix", "title": "Tenebrix and Fairbrix", "section": "Summary and infobox", "text": "The first scrypt coin (Tenebrix, September 2011, heavily premined) and its low-premine relaunch by Charlie Lee (Fairbrix, October 2011), days before Litecoin. Tenebrix announced: 26 Sep 2011 by Lolcust; code mostly by ArtForz [tbx-ann]; Tenebrix premine: “I premined 7 million coins” (Lolcust) [tbx-ann]; Tenebrix parameters: 1 block per 5 minutes, 25 coins per block [tbx-ann]; Fairbrix relaunch: 2 Oct 2011 by coblee [fbx-relaunch]; Fairbrix premine: “only 100 blocks were premined” [fbx-relaunch]; Litecoin: 13 Oct 2011, also by coblee [ltcwiki-history]", "aliases": "tenebrix tbx fairbrix scrypt premine artforz lolcust", "refs": ["fbx-relaunch", "ltcwiki-history", "tbx-ann"], "url": "/wiki/tenebrix-and-fairbrix/"}, {"id": "tenebrix-and-fairbrix#takeover", "slug": "tenebrix-and-fairbrix", "title": "Tenebrix and Fairbrix", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Litecoin's lineage runs through two failed coins in three weeks — Tenebrix for scrypt, Fairbrix for the low-premine lesson — and Charlie Lee ran the second before launching the third. [fbx-relaunch] [ltcwiki-history]", "aliases": "tenebrix tbx fairbrix scrypt premine artforz lolcust", "refs": ["fbx-relaunch", "ltcwiki-history"], "url": "/wiki/tenebrix-and-fairbrix/"}, {"id": "tenebrix-and-fairbrix#938", "slug": "tenebrix-and-fairbrix", "title": "Tenebrix and Fairbrix", "section": "Tenebrix", "text": "Lolcust announced Tenebrix on Bitcointalk on 26 September 2011 as “a CPU-friendly, GPU-hostile cryptocurrency” built mostly by ArtForz, with Lolcust contributing “the name, some minor tweaks and the logo” [tbx-ann]. The post gave “1 block per 5 minutes, retargets every week, no upper bound on mining and 25 coins per block”, and admitted “I premined 7 million coins” [tbx-ann]. The Bitcoin Wiki says scrypt proof of work was “Originally introduced as part of the altcoin Tenebrix (TBX) by ArtForz and Lolcust”, and that the aim of keeping only CPU mining profitable “completely failed in that goal” [bw-scrypt].", "aliases": "tenebrix tbx fairbrix scrypt premine artforz lolcust", "refs": ["bw-scrypt", "tbx-ann"], "url": "/wiki/tenebrix-and-fairbrix/"}, {"id": "tenebrix-and-fairbrix#939", "slug": "tenebrix-and-fairbrix", "title": "Tenebrix and Fairbrix", "section": "Fairbrix", "text": "Fairbrix was first announced on 1 October 2011 by michaelmclees, who soon warned that a config error had caused “all blocks past 100 mined to generate 0 coins” [fbx-ann]. On 2 October 2011 coblee relaunched it as “a GPU-unfriendly coin based on Lolcust's Tenebrix” that “does not come with 7.7 million premined coins. In fact, only 100 blocks were premined” [fbx-relaunch]. The two posts disagree on the size of the Tenebrix premine (7 million and 7.7 million) [tbx-ann] [fbx-relaunch].", "aliases": "tenebrix tbx fairbrix scrypt premine artforz lolcust", "refs": ["fbx-ann", "fbx-relaunch", "tbx-ann"], "url": "/wiki/tenebrix-and-fairbrix/"}, {"id": "tenebrix-and-fairbrix#940", "slug": "tenebrix-and-fairbrix", "title": "Tenebrix and Fairbrix", "section": "Litecoin", "text": "The Litecoin Wiki's history table lists Tenebrix (26.09.2011, Lolcust & ArtForz) as the “First cryptocurrency using scrypt, premined”, Fairbrix (02.10.2011, coblee) as “Tenebrix without premine”, and Litecoin (13.10.2011, coblee) eleven days later [ltcwiki-history]. coblee is the Bitcointalk handle under which Charlie Lee announced Litecoin [ltc-ann].", "aliases": "tenebrix tbx fairbrix scrypt premine artforz lolcust", "refs": ["ltc-ann", "ltcwiki-history"], "url": "/wiki/tenebrix-and-fairbrix/"}, {"id": "timewarp-bug#infobox", "slug": "timewarp-bug", "title": "The timewarp bug", "section": "Summary and infobox", "text": "A flaw in Bitcoin's difficulty adjustment that lets a hashrate majority lower difficulty by faking block timestamps; BIP-54 proposes the fix. What: Exploit of the difficulty adjustment algorithm [optech-timewarp]; Who can use it: Miners with a majority of hashrate [optech-timewarp]; Worst case (BIP-54): Minimum difficulty within 38 days [bip54]; Fix: First block of a period not earlier than the previous block, with a two-hour grace period [bip54]; Testnet4: Ten-minute grace period [bip54]", "aliases": "timewarp time warp difficulty", "refs": ["bip54", "optech-timewarp"], "url": "/wiki/timewarp-bug/"}, {"id": "timewarp-bug#takeover", "slug": "timewarp-bug", "title": "The timewarp bug", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: the timewarp fix is the headline item in the Consensus Cleanup that Robin Linus discussed on S17 E48. [ep-s17e48-gcc] [bip54]", "aliases": "timewarp time warp difficulty", "refs": ["bip54", "ep-s17e48-gcc"], "url": "/wiki/timewarp-bug/"}, {"id": "timewarp-bug#943", "slug": "timewarp-bug", "title": "The timewarp bug", "section": "The bug", "text": "Optech describes time warp as “an exploit of Bitcoin's difficulty adjustment algorithm that allows miners controlling a large amount of hashrate to prevent difficulty from increasing even as the rate of block production increases” [optech-timewarp]. Header times only need to exceed the median of the previous 11 blocks, so a majority can keep most timestamps low and set the last block of each 2016-block period to the current time [optech-timewarp]. Repeated, this halves difficulty and lets miners speed up block production [optech-timewarp].", "aliases": "timewarp time warp difficulty", "refs": ["optech-timewarp"], "url": "/wiki/timewarp-bug/"}, {"id": "timewarp-bug#944", "slug": "timewarp-bug", "title": "The timewarp bug", "section": "Consequences", "text": "BIP-54 says that “In the worst case, an attacker can bring down the difficulty to its minimum within 38 days of starting the attack” [bip54]. Optech notes the original fear that miners could claim all remaining subsidy, and that faster blocks and slower median time could also harm timelocked contracts and overload nodes [optech-timewarp].", "aliases": "timewarp time warp difficulty", "refs": ["bip54", "optech-timewarp"], "url": "/wiki/timewarp-bug/"}, {"id": "timewarp-bug#945", "slug": "timewarp-bug", "title": "The timewarp bug", "section": "The fix", "text": "BIP-54 fixes it “by preventing the timestamp of the first block of a difficulty period from being lower than the previous block's, with a two-hour grace period” [bip54]. An earlier proposal used a ten-minute grace period, which was adopted for testnet4 [bip54]. See Great Consensus Cleanup and Antoine Poinsot [bip54].", "aliases": "timewarp time warp difficulty", "refs": ["bip54"], "url": "/wiki/timewarp-bug/"}, {"id": "uasf-bip148#infobox", "slug": "uasf-bip148", "title": "UASF (BIP-148)", "section": "Summary and infobox", "text": "The 2017 user-activated soft fork that threatened to reject non-SegWit-signalling blocks from 1 August 2017. Proposal: BIP-148, by Shaolin Fry [bip148]; Flag day: 1 August 2017 00:00 UTC (median time past 1501545600) [bip148]; Rule: Blocks must signal SegWit bit 1 or be rejected [bip148]; Window ends: 15 November 2017, or when SegWit locks in [bip148]; Miner response: BIP-91 forced signalling at 80% before the flag day [bip91]; Result: SegWit active at block 481,824 [btk-allforks]", "aliases": "uasf bip148 bip91 user activated soft fork", "refs": ["bip148", "bip91", "btk-allforks"], "url": "/wiki/uasf-bip148/"}, {"id": "uasf-bip148#takeover", "slug": "uasf-bip148", "title": "UASF (BIP-148)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: the UASF was the small-block side's chain-split threat, the mirror image of the big-block side's hard-fork threats. Whether it forced SegWit or merely coincided with BIP-91 is still argued; this wiki records both mechanisms and the dates. [btk-allforks] [bip148] [bip91]", "aliases": "uasf bip148 bip91 user activated soft fork", "refs": ["bip148", "bip91", "btk-allforks"], "url": "/wiki/uasf-bip148/"}, {"id": "uasf-bip148#948", "slug": "uasf-bip148", "title": "UASF (BIP-148)", "section": "The rule", "text": "BIP-148 specified a flag-day soft fork: between midnight 1 August 2017 (median time past 1501545600) and midnight 15 November 2017, every block must signal the existing SegWit deployment bit, and blocks that did not would be rejected [bip148]. It would only take effect if SegWit was not already locked in by 1 August, and would cease once SegWit locked in [bip148]. The BIP's author is Shaolin Fry [bip148].", "aliases": "uasf bip148 bip91 user activated soft fork", "refs": ["bip148"], "url": "/wiki/uasf-bip148/"}, {"id": "uasf-bip148#949", "slug": "uasf-bip148", "title": "UASF (BIP-148)", "section": "Advocacy", "text": "Fork Wars links Luke Dashjr's guide “How you can help ensure BIP148 is a success” as his stance for this phase [btk-forkwars].", "aliases": "uasf bip148 bip91 user activated soft fork", "refs": ["btk-forkwars"], "url": "/wiki/uasf-bip148/"}, {"id": "uasf-bip148#950", "slug": "uasf-bip148", "title": "UASF (BIP-148)", "section": "BIP-91 and the outcome", "text": "BIP-91, from James Hilliard, let miners lock in mandatory SegWit signalling with 269 of 336 blocks signalling bit 4, the bit named in the New York Agreement [bip91]. Bitcoin Takeover's soft-fork table records SegWit as “pushed over the line by BIP91 and BIP148”, locking in from block 479,808 and activating at 481,824 [btk-allforks]. The same table classes BIP-148 as an activation tactic rather than a new feature [btk-allforks].", "aliases": "uasf bip148 bip91 user activated soft fork", "refs": ["bip91", "btk-allforks"], "url": "/wiki/uasf-bip148/"}, {"id": "uasf-bip148#951", "slug": "uasf-bip148", "title": "UASF (BIP-148)", "section": "Heard on Bitcoin Takeover", "text": "On S15 E50 (August 2024), Murch said: “The UASF code was never run in the sense that it enforced anything. The miners saw the UASF and they activated SegWit before the date that the UASF would have activated.” [ep-s15e50-q5772] Pete Rizzo framed it more broadly on S15 E39 (May 2024): “it's the economic majority that determines forks”. [ep-s15e39-q3349]", "aliases": "uasf bip148 bip91 user activated soft fork", "refs": ["ep-s15e39-q3349", "ep-s15e50-q5772"], "url": "/wiki/uasf-bip148/"}, {"id": "united-bitcoin#infobox", "slug": "united-bitcoin", "title": "United Bitcoin (UBTC)", "section": "Summary and infobox", "text": "A December 2017 fork with 8 MB blocks and smart contracts, linked in the press to Jeff Garzik, that distributed coins only to addresses that had moved recently and was declared discontinued in early 2019. Type: Hard fork; same supply, block time and halving as Bitcoin, lower initial difficulty [ubtc-readme]; Fork height: 498,777 (UBCHeight) [ubtc-chainparams]; Block 498,777 time: 2017-12-11 18:19:12 UTC (12 Dec in Beijing) [btc-498777]; Changes: SegWit, 8 MB blocks, smart contracts [ubtc-readme]; Distribution: 1:1, only to addresses with an outgoing transaction from block 494,000 [ubtc-ann-p5]; People named: Jeff Garzik, Songxiu Hua, Matthew Roszak (press report) [ubtc-news]; Status: “Failed to gain traction and discontinued early 2019” [ubtc-ann]", "aliases": "ubtc garzik", "refs": ["btc-498777", "ubtc-ann", "ubtc-ann-p5", "ubtc-chainparams", "ubtc-news", "ubtc-readme"], "url": "/wiki/united-bitcoin/"}, {"id": "united-bitcoin#takeover", "slug": "united-bitcoin", "title": "United Bitcoin (UBTC)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: United Bitcoin is where the SegWit2x story leaked into the airdrop era. A month after the 2x plan was suspended, the press tied one of the suspension letter's signatories to a fork that planned to put the balances of inactive wallets to work. [ubtc-news] [s2x-suspend]", "aliases": "ubtc garzik", "refs": ["s2x-suspend", "ubtc-news"], "url": "/wiki/united-bitcoin/"}, {"id": "united-bitcoin#954", "slug": "united-bitcoin", "title": "United Bitcoin (UBTC)", "section": "Fork", "text": "The UnitedBitcoin client sets UBCHeight, and the UB fork block number, to 498,777 [ubtc-chainparams]. That Bitcoin block has a header time of 18:19:12 UTC on 11 December 2017 [btc-498777], which matches ZB's notice that UBTC forked at 02:19:12 Beijing time on 12 December [zb-ubtc].", "aliases": "ubtc garzik", "refs": ["btc-498777", "ubtc-chainparams", "zb-ubtc"], "url": "/wiki/united-bitcoin/"}, {"id": "united-bitcoin#955", "slug": "united-bitcoin", "title": "United Bitcoin (UBTC)", "section": "Design", "text": "The README says UBTC keeps Bitcoin's total supply, block speed and halving time and the same proof of work, “only initial difficulty is lowered” [ubtc-readme]. It adds SegWit and 8 MB blocks and a new smart-contract system, and cites Qtum as a technical reference for contracts on a UTXO model [ubtc-readme].", "aliases": "ubtc garzik", "refs": ["ubtc-readme"], "url": "/wiki/united-bitcoin/"}, {"id": "united-bitcoin#956", "slug": "united-bitcoin", "title": "United Bitcoin (UBTC)", "section": "Who was behind it", "text": "Bitcoin.com News reported on 14 December 2017 that Jeff Garzik, Bitbank Group's Songxiu Hua and Bloq chairman Matthew Roszak had launched the project [ubtc-news]. The replies in the ANN thread appear under the heading “Launched in Silicon Valley on Dec 12 by Jeff Garzik” [ubtc-ann-p5]. This wiki has not found a statement from Garzik himself, so his exact role is unverified [ubtc-news].", "aliases": "ubtc garzik", "refs": ["ubtc-ann-p5", "ubtc-news"], "url": "/wiki/united-bitcoin/"}, {"id": "united-bitcoin#957", "slug": "united-bitcoin", "title": "United Bitcoin (UBTC)", "section": "Distribution", "text": "The ANN thread explained that holders received UBTC automatically only if they held bitcoin at block 498,777 and had made an outgoing transaction between blocks 494,000 and the fork, with a second phase for outgoing transactions up to block 502,315 [ubtc-ann-p5]. Bitcoin.com News reported that the team planned to use the balances of inactive addresses, with 30% for “influential communities” and 70% as reserves for fiat-pegged tokens [ubtc-news].", "aliases": "ubtc garzik", "refs": ["ubtc-ann-p5", "ubtc-news"], "url": "/wiki/united-bitcoin/"}, {"id": "united-bitcoin#958", "slug": "united-bitcoin", "title": "United Bitcoin (UBTC)", "section": "End", "text": "The first post of the ANN thread was rewritten to say that UnitedBitcoin “failed to gain traction and discontinued early 2019” [ubtc-ann]. The exact date is not given, so the lineage map ends the line at the start of 2019 as an approximation [ubtc-ann].", "aliases": "ubtc garzik", "refs": ["ubtc-ann"], "url": "/wiki/united-bitcoin/"}, {"id": "value-overflow-2010#infobox", "slug": "value-overflow-2010", "title": "Value overflow incident (2010)", "section": "Summary and infobox", "text": "The August 2010 bug that let a transaction create about 184 billion bitcoin; Satoshi shipped 0.3.10 within hours and the good chain overtook the bad one at block 74,691. Date: 15 August 2010 [btt-822]; Bad block: 74,638 (hash 0000000000790ab3…) [bw-overflow]; Created: About 184 billion BTC in two outputs [btk-allforks]; Fix: Bitcoin 0.3.10, a soft fork, within about five hours [bw-overflow]; Recovery: Good chain overtook the bad chain at block 74,691 [bw-overflow]; CVE: CVE-2010-5139 [bw-overflow]", "aliases": "value overflow cve-2010-5139 74638 184 billion inflation bug", "refs": ["btk-allforks", "btt-822", "bw-overflow"], "url": "/wiki/value-overflow-2010/"}, {"id": "value-overflow-2010#takeover", "slug": "value-overflow-2010", "title": "Value overflow incident (2010)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Bitcoin Takeover's soft-fork history counts this as a soft fork with “an unusually violent activation”, one of the few times Bitcoin's chain has split by accident. [btk-allforks]", "aliases": "value overflow cve-2010-5139 74638 184 billion inflation bug", "refs": ["btk-allforks"], "url": "/wiki/value-overflow-2010/"}, {"id": "value-overflow-2010#961", "slug": "value-overflow-2010", "title": "Value overflow incident (2010)", "section": "Discovery", "text": "On 15 August 2010 a Bitcointalk user posted “Strange block 74638”, noting that the value out of the block was “quite strange” [btt-822]. Within the hour another thread, “overflow bug SERIOUS”, said the block used “an integer overflow to make a negative total transaction”, with two outputs of 92,233,720,368.54 BTC each [btt-823]. Satoshi later edited that post to add the download links for the 0.3.10 patch [btt-823].", "aliases": "value overflow cve-2010-5139 74638 184 billion inflation bug", "refs": ["btt-822", "btt-823"], "url": "/wiki/value-overflow-2010/"}, {"id": "value-overflow-2010#962", "slug": "value-overflow-2010", "title": "Value overflow incident (2010)", "section": "Why it worked", "text": "The Bitcoin Wiki explains that the code checking transactions before they entered a block did not account for outputs so large that they overflowed when summed [bw-overflow]. Bitcoin Takeover's fork history puts the total at roughly 184 billion bitcoin [btk-allforks].", "aliases": "value overflow cve-2010-5139 74638 184 billion inflation bug", "refs": ["btk-allforks", "bw-overflow"], "url": "/wiki/value-overflow-2010/"}, {"id": "value-overflow-2010#963", "slug": "value-overflow-2010", "title": "Value overflow incident (2010)", "section": "The fix and the reorganisation", "text": "A new client was published within five hours with a soft-forking rule rejecting output overflows and any output above 21 million BTC [bw-overflow]. Many unpatched nodes kept building on the bad chain until the good chain overtook it at height 74,691, after which every node accepted it [bw-overflow]. Block 74,691 on today's chain has a header time of 08:20:08 UTC on 16 August 2010 [btc-74691].", "aliases": "value overflow cve-2010-5139 74638 184 billion inflation bug", "refs": ["btc-74691", "bw-overflow"], "url": "/wiki/value-overflow-2010/"}, {"id": "value-overflow-2010#964", "slug": "value-overflow-2010", "title": "Value overflow incident (2010)", "section": "Classification", "text": "Bitcoin Takeover's soft-fork history calls the fix “a tightening”, so it counts the event as “a soft fork with an unusually violent activation” [btk-allforks]. See Hard fork vs soft fork.", "aliases": "value overflow cve-2010-5139 74638 184 billion inflation bug", "refs": ["btk-allforks"], "url": "/wiki/value-overflow-2010/"}, {"id": "vertcoin#infobox", "slug": "vertcoin", "title": "Vertcoin (VTC)", "section": "Summary and infobox", "text": "A 2014 code fork of Bitcoin built to resist ASIC mining, with 2.5-minute blocks, 84 million coins and a history of 51% attacks. Type: Code fork of Bitcoin with its own genesis block [vtc-readme]; Genesis timestamp: 1389311371 (9 Jan 2014, 23:49 UTC) [vtc-chainparams]; Block time: 2.5 minutes [vtc-readme]; Supply: 84 million [vtc-readme]; Proof of work: Verthash [vtc-readme]; 51% attacks: October–December 2018 and 1 December 2019 [wp-vtc]", "aliases": "vtc lyra2rev2 verthash", "refs": ["vtc-chainparams", "vtc-readme", "wp-vtc"], "url": "/wiki/vertcoin/"}, {"id": "vertcoin#takeover", "slug": "vertcoin", "title": "Vertcoin (VTC)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Vertcoin is the cleanest test of the ASIC-resistance promise. It kept changing algorithms to keep miners decentralised and was 51% attacked anyway, which is the risk every small proof-of-work chain in this wiki shares. [wp-vtc] [vtc-readme]", "aliases": "vtc lyra2rev2 verthash", "refs": ["vtc-readme", "wp-vtc"], "url": "/wiki/vertcoin/"}, {"id": "vertcoin#967", "slug": "vertcoin", "title": "Vertcoin (VTC)", "section": "Design", "text": "The README calls Vertcoin “a fork of Bitcoin that is designed to resist the monopolisation of mining power”, with 2.5-minute blocks, halvings every 840,000 blocks, 84 million coins, per-block difficulty retargeting and the Verthash proof of work [vtc-readme]. Its mainnet genesis block carries the timestamp 1389311371 and the headline “01/09/2014 Germany to Help in Disposal of Syrian Chemical Weapons” [vtc-chainparams].", "aliases": "vtc lyra2rev2 verthash", "refs": ["vtc-chainparams", "vtc-readme"], "url": "/wiki/vertcoin/"}, {"id": "vertcoin#968", "slug": "vertcoin", "title": "Vertcoin (VTC)", "section": "Attacks", "text": "Wikipedia reports that Vertcoin suffered 51% attacks from October through December 2018, changed its proof-of-work algorithm, and was attacked again on 1 December 2019 [wp-vtc]. It also cites a December 2018 paper arguing that Vertcoin's difficulty adjustment was “very sensitive to hash rate change” because the chain was not very popular [wp-vtc].", "aliases": "vtc lyra2rev2 verthash", "refs": ["wp-vtc"], "url": "/wiki/vertcoin/"}, {"id": "vertcoin#969", "slug": "vertcoin", "title": "Vertcoin (VTC)", "section": "Date", "text": "The infobox uses the genesis timestamp; Wikipedia only says the coin was created in early 2014 [vtc-chainparams] [wp-vtc].", "aliases": "vtc lyra2rev2 verthash", "refs": ["vtc-chainparams", "wp-vtc"], "url": "/wiki/vertcoin/"}, {"id": "viabtc#infobox", "slug": "viabtc", "title": "ViaBTC", "section": "Summary and infobox", "text": "The mining pool founded by Haipo Yang in 2016 that suggested the name Bitcoin Cash, listed it before the split, and mined its first block. Founded: May 2016, by Haipo Yang [viabtc-blog]; First Bitcoin block: 5 June 2016 [viabtc-blog]; Bitcoin Cash: Suggested the name, July 2017 [wp-bch]; First BCH-only block: 478,559, mined by ViaBTC [btk-bch]; New York Agreement: Signatory [nya-letter]; Related businesses: CoinEx exchange, CoinEx Wallet, ViaBTC Capital [viabtc-blog]", "aliases": "viabtc haipo yang coinex", "refs": ["btk-bch", "nya-letter", "viabtc-blog", "wp-bch"], "url": "/wiki/viabtc/"}, {"id": "viabtc#takeover", "slug": "viabtc", "title": "ViaBTC", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: ViaBTC is the pool that turned a contingency plan into a coin: it named Bitcoin Cash, sold futures on it before the fork, and then mined the block that made the split real. [wp-bch] [btk-bch]", "aliases": "viabtc haipo yang coinex", "refs": ["btk-bch", "wp-bch"], "url": "/wiki/viabtc/"}, {"id": "viabtc#972", "slug": "viabtc", "title": "ViaBTC", "section": "Founding", "text": "ViaBTC's own interview with its CEO says that in May 2016 Haipo Yang “single-handedly completed all the code for the ViaBTC Pool”, and that the pool mined its first BTC block on 5 June 2016 [viabtc-blog]. The company later launched the CoinEx exchange, CoinEx Wallet, CoinEx Smart Chain and ViaBTC Capital [viabtc-blog].", "aliases": "viabtc haipo yang coinex", "refs": ["viabtc-blog"], "url": "/wiki/viabtc/"}, {"id": "viabtc#973", "slug": "viabtc", "title": "ViaBTC", "section": "Bitcoin Cash", "text": "Wikipedia says that in July 2017 ViaBTC suggested the name Bitcoin Cash for the fork [wp-bch]. Bitcoin Takeover's BCH article says ViaBTC listed futures before the split and mined the first BCH-only block, 478,559, roughly six hours after the last common block [btk-bch]. Wikipedia's Jihan Wu article describes ViaBTC as a company Bitmain had invested in and says it “orchestrated” the fork, and notes that Wu denied that he or Bitmain had so much influence [wp-jihan].", "aliases": "viabtc haipo yang coinex", "refs": ["btk-bch", "wp-bch", "wp-jihan"], "url": "/wiki/viabtc/"}, {"id": "viabtc#974", "slug": "viabtc", "title": "ViaBTC", "section": "New York", "text": "ViaBTC (China) is on the list of New York Agreement signatories of May 2017 [nya-letter].", "aliases": "viabtc haipo yang coinex", "refs": ["nya-letter"], "url": "/wiki/viabtc/"}, {"id": "wang-chun#infobox", "slug": "wang-chun", "title": "Wang Chun", "section": "Summary and infobox", "text": "Co-founder of F2Pool, signer of the 2016 Hong Kong Roundtable statement, founder of Stakefish, and commander of the 2025 Fram2 polar spaceflight. Born: Around 1982, Tianjin [wp-chunwang]; Co-founded: F2Pool (by 2013) [wp-chunwang]; Hong Kong statement: Signed as “Admin F2Pool”, Feb 2016 [hk-letter]; Later venture: Stakefish (2018) [wp-chunwang]; Spaceflight: Commander, Fram2 (31 Mar – 4 Apr 2025) [wp-chunwang]; Citizenship: Malta (from Aug 2023), Saint Kitts and Nevis (from 2017) [wp-chunwang]", "aliases": "wang chun discus fish f2pool fram2", "refs": ["hk-letter", "wp-chunwang"], "url": "/wiki/wang-chun/"}, {"id": "wang-chun#takeover", "slug": "wang-chun", "title": "Wang Chun", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Wang Chun's pool signed the 2016 compromise that promised a hard fork later, which never came on Bitcoin; F2Pool's founder then went on to the most literal exit of any block size war figure — orbit. [hk-letter] [wp-chunwang]", "aliases": "wang chun discus fish f2pool fram2", "refs": ["hk-letter", "wp-chunwang"], "url": "/wiki/wang-chun/"}, {"id": "wang-chun#977", "slug": "wang-chun", "title": "Wang Chun", "section": "Early years", "text": "Wikipedia says Wang Chun was born around 1982 in Tianjin, borrowed $40,000 from his father in 2011 to invest in early cryptocurrency ventures, and had made gains by 2013, when he co-founded F2Pool [wp-chunwang]. It adds that for a time F2Pool was the world's largest bitcoin mining operation [wp-chunwang].", "aliases": "wang chun discus fish f2pool fram2", "refs": ["wp-chunwang"], "url": "/wiki/wang-chun/"}, {"id": "wang-chun#978", "slug": "wang-chun", "title": "Wang Chun", "section": "Block size war", "text": "The Hong Kong Roundtable statement of February 2016 lists “Wang Chun Admin F2Pool” among its signers [hk-letter]. Bitcoin Takeover's Fork Wars timeline also records Wang Chun of F2Pool among the signers of the earlier Roundtable letter “A Call for Consensus” of 11 February 2016 [btk-forkwars].", "aliases": "wang chun discus fish f2pool fram2", "refs": ["btk-forkwars", "hk-letter"], "url": "/wiki/wang-chun/"}, {"id": "wang-chun#979", "slug": "wang-chun", "title": "Wang Chun", "section": "Later", "text": "Wikipedia says Wang launched Stakefish in 2018, privately funded and commanded the Fram2 Crew Dragon mission, launched on 31 March 2025 as the first human flight in a polar retrograde orbit, and became the first person from Malta to travel to space [wp-chunwang]. It gives Maltese citizenship since August 2023 and Saint Kitts and Nevis citizenship since 2017 [wp-chunwang].", "aliases": "wang chun discus fish f2pool fram2", "refs": ["wp-chunwang"], "url": "/wiki/wang-chun/"}, {"id": "wladimir-van-der-laan#infobox", "slug": "wladimir-van-der-laan", "title": "Wladimir (Mara) van der Laan", "section": "Summary and infobox", "text": "Bitcoin Core's lead maintainer from 2014 under the name Wladimir van der Laan, chosen by Gavin Andresen; began handing off the role in 2021 and gave up merge rights in 2023. The laanwj profile now shows the name Mara van der Laan. Handle: laanwj [bw-wladimir]; Name in 2011–2024 sources: Wladimir van der Laan [bw-wladimir]; Current name (GitHub, Nov 2026): Mara van der Laan; bio “former bitcoin maintainer” [laanwj-gh]; Date of name change: Unknown (not sourced) [laanwj-gh]; Active in Bitcoin: From 2011 [laanwj-gyre]; Bitcoin Core maintainer: Succeeded Gavin Andresen, 7 Apr 2014 [bw-wladimir]; Stepping back: “The widening gyre”, 21 Jan 2021 [laanwj-gyre]; Merge rights removed: February 2023 (Bitcoin Core PR #27054) [bw-wladimir]", "aliases": "laanwj wladimir wlad maintainer mara van der laan", "refs": ["bw-wladimir", "laanwj-gh", "laanwj-gyre"], "url": "/wiki/wladimir-van-der-laan/"}, {"id": "wladimir-van-der-laan#takeover", "slug": "wladimir-van-der-laan", "title": "Wladimir (Mara) van der Laan", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: the person who held Bitcoin Core's release keys through the whole block size war wrote, in 2021, that being a central bottleneck was the problem. The blog reads as a running record of what Craig Wright's lawsuits cost developers, ending with relief at the COPA ruling. [laanwj-gyre] [laanwj-finally]", "aliases": "laanwj wladimir wlad maintainer mara van der laan", "refs": ["laanwj-finally", "laanwj-gyre"], "url": "/wiki/wladimir-van-der-laan/"}, {"id": "wladimir-van-der-laan#982", "slug": "wladimir-van-der-laan", "title": "Wladimir (Mara) van der Laan", "section": "Name", "text": "This article uses two names by period. For 2011 to 2024, the years in which the cited sources were published under the name Wladimir van der Laan, it uses that name [bw-wladimir]. For the period after the name change it uses Mara van der Laan, the name the laanwj GitHub profile shows as of 13 November 2026, with the bio “former bitcoin maintainer” [laanwj-gh]. The date of the change is not sourced and is marked unknown; the article avoids pronouns [laanwj-gh].", "aliases": "laanwj wladimir wlad maintainer mara van der laan", "refs": ["bw-wladimir", "laanwj-gh"], "url": "/wiki/wladimir-van-der-laan/"}, {"id": "wladimir-van-der-laan#983", "slug": "wladimir-van-der-laan", "title": "Wladimir (Mara) van der Laan", "section": "Maintainer", "text": "The Bitcoin Wiki says that on 7 April 2014 Gavin Andresen stepped down as Bitcoin Core maintainer and nominated Wladimir van der Laan as successor [bw-wladimir]. In 2021 Wladimir van der Laan wrote of contributing to Bitcoin since 2011 and of a project that had grown into “a 600 billion dollar system” [laanwj-gyre]. In 2018 the Bitcoin Core disclosure of CVE-2018-17144 listed Wladimir van der Laan among the developers who received the first report [core-cve-17144].", "aliases": "laanwj wladimir wlad maintainer mara van der laan", "refs": ["bw-wladimir", "core-cve-17144", "laanwj-gyre"], "url": "/wiki/wladimir-van-der-laan/"}, {"id": "wladimir-van-der-laan#984", "slug": "wladimir-van-der-laan", "title": "Wladimir (Mara) van der Laan", "section": "Decentralising the role", "text": "In “The widening gyre” (21 January 2021) Wladimir van der Laan wrote “I realize I am myself somewhat of a centralized bottleneck” and planned to delegate tasks: move bitcoincore.org to an organisation, decentralise release signing, rename the release key, and look beyond GitHub [laanwj-gyre]. The post noted that van der Laan had made only about 24% of 2020's merges [laanwj-gyre]. The Bitcoin Wiki says van der Laan then stepped down gradually and in February 2023 removed the account's own merge privileges in pull request #27054 [bw-wladimir].", "aliases": "laanwj wladimir wlad maintainer mara van der laan", "refs": ["bw-wladimir", "laanwj-gyre"], "url": "/wiki/wladimir-van-der-laan/"}, {"id": "wladimir-van-der-laan#985", "slug": "wladimir-van-der-laan", "title": "Wladimir (Mara) van der Laan", "section": "Craig Wright", "text": "In May 2016 Wladimir van der Laan wrote of a project in which attacks were “agitated by someone that purports to be part of your own project” and of the need to break ties with individuals seen as “a toxic influence” [laanwj-2016]. In February 2023 the post “Of regrets” said of the MIT license's no-warranty clause that it “apparently doesn't hold up in court (at least in the UK)” [laanwj-regrets]. On 19 March 2024 “Finally” quoted the judge's declarations that Craig Wright is not Satoshi; the post itself called him “a fraud” and said van der Laan's first post about him dated from 2016, “back when Gavin fell under his influence” [laanwj-finally].", "aliases": "laanwj wladimir wlad maintainer mara van der laan", "refs": ["laanwj-2016", "laanwj-finally", "laanwj-regrets"], "url": "/wiki/wladimir-van-der-laan/"}, {"id": "wladimir-van-der-laan#986", "slug": "wladimir-van-der-laan", "title": "Wladimir (Mara) van der Laan", "section": "Today", "text": "As Mara van der Laan, the laanwj GitHub profile describes a “former bitcoin maintainer” [laanwj-gh]. This wiki has no sourced account of activity under that name beyond the profile [laanwj-gh].", "aliases": "laanwj wladimir wlad maintainer mara van der laan", "refs": ["laanwj-gh"], "url": "/wiki/wladimir-van-der-laan/"}, {"id": "world-bitcoin#infobox", "slug": "world-bitcoin", "title": "World Bitcoin (WBTC)", "section": "Summary and infobox", "text": "A January 2018 fork at block 503,888 at 1 BTC = 100 WBTC, with 21 million of its 2.121 billion coins held by a foundation. Fork height: 503,888 [wbtc-site]; Block 503,888 time: 2018-01-12 16:44:38 UTC [btc-503888]; Ratio: 1:100 [wbtc-site]; Supply: 2.121 billion, 21 million to the foundation [wbtc-site]; Status (Feb 2019 list): Stopped; last synced block 537946 on 8/8/2018 [bth-review]", "aliases": "wbtc world bitcoin", "refs": ["btc-503888", "bth-review", "wbtc-site"], "url": "/wiki/world-bitcoin/"}, {"id": "world-bitcoin#takeover", "slug": "world-bitcoin", "title": "World Bitcoin (WBTC)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: the ticker WBTC is also used by Wrapped Bitcoin, for which Wikipedia lists BitGo as sole custodian — a different thing from this 2018 fork. [wp-bitgo] [wbtc-site]", "aliases": "wbtc world bitcoin", "refs": ["wbtc-site", "wp-bitgo"], "url": "/wiki/world-bitcoin/"}, {"id": "world-bitcoin#989", "slug": "world-bitcoin", "title": "World Bitcoin (WBTC)", "section": "Pitch", "text": "The archived site, captured on 22 February 2018, says WBTC “will start to bifurcate at Bitcoin 503888” and that Bitcoin addresses would receive WBTC “in the ratio of 1: 100” [wbtc-site]. It states “The total amount of WBTC is 2.121 billion, of which 21 million WBTC will be managed by foundations” and sets the initial issuing time for 2018/1/12 [wbtc-site]. Block 503,888 was mined on 12 January 2018 [btc-503888]. The site names Jackson Zhang as initiator [wbtc-site].", "aliases": "wbtc world bitcoin", "refs": ["btc-503888", "wbtc-site"], "url": "/wiki/world-bitcoin/"}, {"id": "world-bitcoin#990", "slug": "world-bitcoin", "title": "World Bitcoin (WBTC)", "section": "Record", "text": "The GitHub README says World Bitcoin “will be based on Bitcoin and add new features” [wbtc-readme]. The 2019 fork list says it “doesn't seem to be working anymore, 0.4 GB, last synced block 537946 on 8/8/2018” [bth-review].", "aliases": "wbtc world bitcoin", "refs": ["bth-review", "wbtc-readme"], "url": "/wiki/world-bitcoin/"}, {"id": "xenon#infobox", "slug": "xenon", "title": "Xenon (XNN)", "section": "Summary and infobox", "text": "An EOS alt-chain project whose ERC-20 XNN tokens went to Ethereum addresses in October 2017, with a BTC-holder airdrop announced later. Type: ERC-20 token (EOS alt-chain plan) [xnn-ann]; ETH airdrop: Over 750,000 addresses with more than 0.1 ETH (Oct 2017) [xnn-ann]; Date (forkdrop): 2018-06-30 [fd-data]; forkdrop reason: “Airdrop Over” [fd-data]", "aliases": "xnn xenon eos", "refs": ["fd-data", "xnn-ann"], "url": "/wiki/xenon/"}, {"id": "xenon#takeover", "slug": "xenon", "title": "Xenon (XNN)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Xenon is mostly an Ethereum airdrop; its thread mentions a later round for BTC holders. [xnn-ann]", "aliases": "xnn xenon eos", "refs": ["xnn-ann"], "url": "/wiki/xenon/"}, {"id": "xenon#993", "slug": "xenon", "title": "Xenon (XNN)", "section": "Record", "text": "The Bitcointalk thread, opened on 26 September 2017, calls XenonNetwork a “Massively Distributed EOS Altchain” [xnn-ann]. A 23 October 2017 update says an airdrop of XNN tokens to “>750,000 Ethereum addresses with >0.1 ETH” had begun, with 300,000,000 tokens to be airdropped [xnn-ann]. A 1 December 2017 update mentions “the BTC holder airdrop” and extends distribution to developers and block producers [xnn-ann].", "aliases": "xnn xenon eos", "refs": ["xnn-ann"], "url": "/wiki/xenon/"}, {"id": "xenon#994", "slug": "xenon", "title": "Xenon (XNN)", "section": "Listing", "text": "forkdrop's data file lists a registration airdrop dated 2018-06-30 with block and supply “???”, an Etherscan token link and the reason “Airdrop Over” [fd-data]. The BTC round's terms are unverified [xnn-ann].", "aliases": "xnn xenon eos", "refs": ["fd-data", "xnn-ann"], "url": "/wiki/xenon/"}, {"id": "zcash#infobox", "slug": "zcash", "title": "Zcash", "section": "Summary and infobox", "text": "The 2016 shielded-payments chain built on the Zerocash research — “the privacy upgrade Bitcoin never accepted”. Ticker: ZEC [btk-zec]; Type: Codebase fork of Bitcoin Core, own genesis, no airdrop [btk-zec]; Block time: 75 seconds (150 s before Blossom) [btk-zec]; Launch: 28 October 2016 (genesis released) [zec-begins]; Research basis: Zerocash paper (2014) [zerocash]; Proof of work: Equihash [btk-zec]; Shielded pools: Sprout, Sapling, Orchard [btk-zec]; Counterfeiting bug: Disclosed and remediated, February 2019 [zec-counterfeit]; Co-founder: Zooko Wilcox [ep-s16e29]", "aliases": "zec zerocash shielded", "refs": ["btk-zec", "ep-s16e29", "zec-begins", "zec-counterfeit", "zerocash"], "url": "/wiki/zcash/"}, {"id": "zcash#takeover", "slug": "zcash", "title": "Zcash", "section": "Takeover view (editorial opinion)", "text": "Zcash is the most-covered privacy chain on the show: Zooko, Sean Bowe, Josh Swihart, Kris Nuttycombe and Daira-Emma Hopwood. The magazine frames it as a Bitcoin upgrade that went elsewhere. [btk-zec] [ep-s16e29] [btk-forksmag]", "aliases": "zec zerocash shielded", "refs": ["btk-forksmag", "btk-zec", "ep-s16e29"], "url": "/wiki/zcash/"}, {"id": "zcash#997", "slug": "zcash", "title": "Zcash", "section": "Origins", "text": "Zcash grew out of academic work on private payments for Bitcoin: Zerocoin in 2013 and Zerocash in 2014, whose authors were Eli Ben-Sasson, Alessandro Chiesa, Christina Garman, Matthew Green, Ian Miers, Eran Tromer and Madars Virza [btk-zec] [zerocash] [zerocash]. Zerocash hides sender, recipient and amount, where Zerocoin hid only the link between deposit and withdrawal [btk-zec].", "aliases": "zec zerocash shielded", "refs": ["btk-zec", "zerocash"], "url": "/wiki/zcash/"}, {"id": "zcash#998", "slug": "zcash", "title": "Zcash", "section": "Launch", "text": "The Electric Coin Company announced on 28 October 2016 that the Zcash blockchain was live and the genesis block had been released [zec-begins].", "aliases": "zec zerocash shielded", "refs": ["zec-begins"], "url": "/wiki/zcash/"}, {"id": "zcash#999", "slug": "zcash", "title": "Zcash", "section": "Upgrades and incidents", "text": "Zcash has upgraded through named network upgrades including Sapling, Blossom, Canopy, NU5 (Orchard) and NU6.1 [btk-zec]. In February 2019 the Electric Coin Company disclosed a counterfeiting vulnerability that had been remediated [zec-counterfeit].", "aliases": "zec zerocash shielded", "refs": ["btk-zec", "zec-counterfeit"], "url": "/wiki/zcash/"}, {"id": "zcash#1000", "slug": "zcash", "title": "Zcash", "section": "On the podcast", "text": "Co-founder Zooko Wilcox argued on S16 E29 that a shielded pool does about the best possible job of privacy at the blockchain level, and that privacy is added to money at rest rather than in flight [ep-s16e29].", "aliases": "zec zerocash shielded", "refs": ["ep-s16e29"], "url": "/wiki/zcash/"}, {"id": "zcash#1001", "slug": "zcash", "title": "Zcash", "section": "Heard on Bitcoin Takeover", "text": "Asked on S16 E51 (October 2025) when he realised Bitcoin was not really private, Zcash engineer Sean Bowe said: “Oh, it was obvious it wasn't private from the beginning.” [ep-s16e51-q848] Other Zcash episodes: S16 E55, ‘Mert Mumtaz on Zcash, Privacy & Zillions’ (November 2025) [btk-ep-s16e55]; S17 E28, ‘Josh Swihart on Zcash & ZODL’ (June 2026) [btk-ep-s17e28]; S17 E49, ‘Kris Nuttycombe on Zcash at Ten, Hard Forks, the Dev Fund & Why Ossification Is Death’ (November 2026) [btk-ep-s17e49]; S17 E50, ‘Daira-Emma Hopwood on Zcash at 10, Halo, ZSAs and the Fight Over Grants’ (November 2026) [btk-ep-s17e50].", "aliases": "zec zerocash shielded", "refs": ["btk-ep-s16e55", "btk-ep-s17e28", "btk-ep-s17e49", "btk-ep-s17e50", "ep-s16e51-q848"], "url": "/wiki/zcash/"}, {"id": "zclassic#infobox", "slug": "zclassic", "title": "Zclassic (ZCL)", "section": "Summary and infobox", "text": "A November 2016 fork of the Zcash code that removed the 20% founders' reward and the slow start, later the Zcash-side parent of Bitcoin Private. Type: Code fork of Zcash 1.0.1 [zcl-ann]; Announced: 6 November 2016 on Bitcointalk [zcl-ann]; Changes: No 20% founders' reward; no slow start [zcl-ann]; Proof of work: Equihash [zcl-ann]; Block reward: 12.5 ZCL every 2.5 minutes at launch [zcl-ann]; Trusted setup: Reuses the Zcash parameters [zcl-ann]; Child: Bitcoin Private (ZCL plus BTC snapshot, 2018) [btcp-readme]", "aliases": "zcl zclassic", "refs": ["btcp-readme", "zcl-ann"], "url": "/wiki/zclassic/"}, {"id": "zclassic#takeover", "slug": "zclassic", "title": "Zclassic (ZCL)", "section": "Takeover view (editorial opinion)", "text": "The wiki's angle: Zclassic is the Zcash founders' reward argument turned into a coin. It kept Zcash's cryptography and trusted setup and removed only the money that went to the company, which is the same funding fight that later split Bitcoin Cash. [zcl-ann] [btk-xec]", "aliases": "zcl zclassic", "refs": ["btk-xec", "zcl-ann"], "url": "/wiki/zclassic/"}, {"id": "zclassic#1004", "slug": "zclassic", "title": "Zclassic (ZCL)", "section": "Announcement", "text": "The Bitcointalk announcement, opened on 6 November 2016, describes Zclassic as “a fork of Zcash 1.0.1 with minimal changes except for 2 major things”: the 20% founders' reward is removed and the slow start is removed, so blocks start at 12.5 ZCL [zcl-ann]. It keeps Equihash, a four-year halving, a 21 million supply and Digishield difficulty adjustment [zcl-ann].", "aliases": "zcl zclassic", "refs": ["zcl-ann"], "url": "/wiki/zclassic/"}, {"id": "zclassic#1005", "slug": "zclassic", "title": "Zclassic (ZCL)", "section": "Trusted setup", "text": "The announcement says Zclassic “uses the exact same trusted parameters Zcash uses”, explaining that anyone with the destroyed key could mint unlimited coins and that Zcash's ceremony split that key among six people [zcl-ann]. It says reusing them “is also what Peter Todd suggests”, linking a Reddit thread on the subject [zcl-ann].", "aliases": "zcl zclassic", "refs": ["zcl-ann"], "url": "/wiki/zclassic/"}, {"id": "zclassic#1006", "slug": "zclassic", "title": "Zclassic (ZCL)", "section": "Bitcoin Private", "text": "In 2018 Zclassic became one parent of Bitcoin Private, which combined a snapshot of Zclassic with a snapshot of Bitcoin [btcp-readme]. The Bitcoin Private README calls it “a fork of Zclassic, merging in a snapshotted UTXO set of Bitcoin” [btcp-readme]. The current Zclassic README, version 2.1.2-beta6, describes it as “Based on Bitcoin's code and derived from Zcash” [zcl-readme]. Its current market data and node count are unknown in this wiki [zcl-readme].", "aliases": "zcl zclassic", "refs": ["btcp-readme", "zcl-readme"], "url": "/wiki/zclassic/"}], "refs": {"wp": {"kind": "primary", "title": "Satoshi Nakamoto, “Bitcoin P2P e-cash paper”, Cryptography mailing list, 31 Oct 2008", "url": "https://www.metzdowd.com/pipermail/cryptography/2008-October/014810.html", "archive_url": "https://web.archive.org/web/20261024000631/https://www.metzdowd.com/pipermail/cryptography/2008-October/014810.html", "archive_date": "20261024000631", "archive_how": "existing"}, "genesis": {"kind": "primary", "title": "Block 0 (genesis), mempool.space", "url": "https://mempool.space/block/000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f", "archive_url": "https://web.archive.org/web/20261031154321/https://mempool.space/block/000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f", "archive_date": "20261031154321", "archive_how": "existing"}, "c-1mb": {"kind": "primary", "title": "Bitcoin commit a30b56e, 15 Jul 2010 (adds MAX_BLOCK_SIZE = 1000000)", "url": "https://github.com/bitcoin/bitcoin/commit/a30b56ebe76ffff9f9cc8a6667186179413c6349", "archive_url": "https://web.archive.org/web/20251211202350/https://github.com/bitcoin/bitcoin/commit/a30b56ebe76ffff9f9cc8a6667186179413c6349", "archive_date": "20251211202350", "archive_how": "existing"}, "satoshi-15139": {"kind": "primary", "title": "Satoshi Nakamoto, reply to Garzik's block-size patch, Bitcointalk msg 15139, 3 Oct 2010", "url": "https://bitcointalk.org/index.php?topic=1347.msg15139#msg15139", "archive_url": "https://web.archive.org/web/20260802033626/https://bitcointalk.org/index.php?topic=1347.msg15139", "archive_date": "20260802033626", "archive_how": "existing"}, "bips": {"kind": "primary", "title": "bitcoin/bips repository", "url": "https://github.com/bitcoin/bips", "archive_url": "https://web.archive.org/web/20261020232912/https://github.com/bitcoin/bips", "archive_date": "20261020232912", "archive_how": "existing"}, "bip300": {"kind": "primary", "title": "BIP-300 (Hashrate Escrows)", "url": "https://github.com/bitcoin/bips/blob/master/bip-0300.mediawiki", "archive_url": "https://web.archive.org/web/20261108131207/https://github.com/bitcoin/bips/blob/master/bip-0300.mediawiki", "archive_date": "20261108131207", "archive_how": "existing"}, "bip301": {"kind": "primary", "title": "BIP-301 (Blind Merged Mining)", "url": "https://github.com/bitcoin/bips/blob/master/bip-0301.mediawiki", "archive_url": "https://web.archive.org/web/20261108131207/https://github.com/bitcoin/bips/blob/master/bip-0301.mediawiki", "archive_date": "20261108131207", "archive_how": "existing"}, "bip110": {"kind": "primary", "title": "BIP-110 specification", "url": "https://github.com/bitcoin/bips/blob/master/bip-0110.mediawiki", "archive_url": "https://web.archive.org/web/20261107103449/https://github.com/bitcoin/bips/blob/master/bip-0110.mediawiki", "archive_date": "20261107103449", "archive_how": "existing"}, "drivechain-info": {"kind": "primary", "title": "drivechain.info", "url": "https://drivechain.info/", "archive_url": "https://web.archive.org/web/20261009004559/https://drivechain.info/", "archive_date": "20261009004559", "archive_how": "existing"}, "ptodd-drivechains": {"kind": "secondary", "title": "Peter Todd, “Drivechains: A Detailed Analysis” (2023)", "url": "https://petertodd.org/2023/drivechains", "archive_url": "https://web.archive.org/web/20260516180757/https://petertodd.org/2023/drivechains", "archive_date": "20260516180757", "archive_how": "existing"}, "btk-forkwars": {"kind": "btk", "title": "Fork Wars: the block size war timeline (Bitcoin Takeover)", "url": "https://bitcoin-takeover.com/fork-wars/", "archive_url": "https://web.archive.org/web/20261113140526/https://bitcoin-takeover.com/fork-wars/", "archive_date": "20261113140526", "archive_how": "saved"}, "btk-forksmag": {"kind": "btk", "title": "BTCTKVR: Forks! (2026 magazine)", "url": "https://bitcoin-takeover.com/forksmag/", "archive_url": "https://web.archive.org/web/20261007190832/https://bitcoin-takeover.com/forksmag/", "archive_date": "20261007190832", "archive_how": "existing"}, "btk-allforks": {"kind": "btk", "title": "Bitcoin: All the Hard Forks and Soft Forks (BTCTKVR: Forks!)", "url": "https://bitcoin-takeover.com/bitcoin-all-the-hard-forks-and-soft-forks/", "archive_url": "https://web.archive.org/web/20261113135819/https://bitcoin-takeover.com/bitcoin-all-the-hard-forks-and-soft-forks/", "archive_date": "20261113135819", "archive_how": "saved"}, "btk-bch": {"kind": "btk", "title": "Bitcoin Cash: The Big Block Breakaway (BTCTKVR: Forks!)", "url": "https://bitcoin-takeover.com/bitcoin-cash-big-block-breakaway/", "archive_url": "https://web.archive.org/web/20261113135948/https://bitcoin-takeover.com/bitcoin-cash-big-block-breakaway/", "archive_date": "20261113135948", "archive_how": "saved"}, "btk-bsv": {"kind": "btk", "title": "Bitcoin SV: Big Blocks All the Way (BTCTKVR: Forks!)", "url": "https://bitcoin-takeover.com/bitcoin-sv-bsv-big-blocks-all-the-way/", "archive_url": "https://web.archive.org/web/20261113140248/https://bitcoin-takeover.com/bitcoin-sv-bsv-big-blocks-all-the-way/", "archive_date": "20261113140248", "archive_how": "saved"}, "btk-btg": {"kind": "btk", "title": "Bitcoin Gold: One GPU, One Vote (BTCTKVR: Forks!)", "url": "https://bitcoin-takeover.com/bitcoin-gold-one-gpu-one-vote/", "archive_url": "https://web.archive.org/web/20261113140033/https://bitcoin-takeover.com/bitcoin-gold-one-gpu-one-vote/", "archive_date": "20261113140033", "archive_how": "saved"}, "btk-xec": {"kind": "btk", "title": "eCash (XEC): The Fork That Taxed Itself (BTCTKVR: Forks!)", "url": "https://bitcoin-takeover.com/ecash-xec-the-fork-that-taxed-itself/", "archive_url": "https://web.archive.org/web/20261113140437/https://bitcoin-takeover.com/ecash-xec-the-fork-that-taxed-itself/", "archive_date": "20261113140437", "archive_how": "saved"}, "btk-blake": {"kind": "btk", "title": "Bitcoin BLAKE2b: The Fork That Fired the Miners (BTCTKVR: Forks!)", "url": "https://bitcoin-takeover.com/bitcoin-blake2b-the-fork-that-fired-the-miners/", "archive_url": "https://web.archive.org/web/20261113135903/https://bitcoin-takeover.com/bitcoin-blake2b-the-fork-that-fired-the-miners/", "archive_date": "20261113135903", "archive_how": "saved"}, "btk-ecx": {"kind": "btk", "title": "eCash (ECX): Paul Sztorc Forks Bitcoin to Prove a Point (BTCTKVR: Forks!)", "url": "https://bitcoin-takeover.com/ecash-ecx-paul-sztorc-forks-bitcoin-to-prove-a-point/", "archive_url": "https://web.archive.org/web/20261113140351/https://bitcoin-takeover.com/ecash-ecx-paul-sztorc-forks-bitcoin-to-prove-a-point/", "archive_date": "20261113140351", "archive_how": "saved"}, "btk-zec": {"kind": "btk", "title": "Zcash: The Privacy Moon Math Bitcoin Was Afraid to Include (BTCTKVR: Forks!)", "url": "https://bitcoin-takeover.com/zcash-the-privacy-upgrade-bitcoin-never-accepted/", "archive_url": "https://web.archive.org/web/20261113140802/https://bitcoin-takeover.com/zcash-the-privacy-upgrade-bitcoin-never-accepted/", "archive_date": "20261113140802", "archive_how": "saved"}, "btk-ltc-e30": {"kind": "btk", "title": "S15 E30 show notes: Charlie Lee on Lightning, Litecoin & Why Payment Coins Survived", "url": "https://bitcoin-takeover.com/s15-e30-charlie-lee-on-lightning-litecoin-why-payment-coins-survived/", "archive_url": "https://web.archive.org/web/20261113140611/https://bitcoin-takeover.com/s15-e30-charlie-lee-on-lightning-litecoin-why-payment-coins-survived/", "archive_date": "20261113140611", "archive_how": "saved"}, "ep-s17e19-ecash": {"kind": "episode", "title": "S17 E19: Deadalnix (Amaury Séchet) on Forking Bitcoin & Ecash — eCash as a fork of BCH", "url": "https://bitcoin-takeover.com/audio/media/2026-04-18_s17_e19_deadalnix_amaury_sechet_on_forking_bitcoin_ecash.mp3", "t": 2777, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153144/https://bitcoin-takeover.com/s17-e19-amaury-sechet-on-forking-bitcoin-twice-quantum-fud-scars-from-the-block-size-wars/", "archive_date": "20261113153144", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e19-abc": {"kind": "episode", "title": "S17 E19: Amaury Séchet — Bitcoin ABC was its own fork of Core, not XT/Classic/Unlimited", "url": "https://bitcoin-takeover.com/audio/media/2026-04-18_s17_e19_deadalnix_amaury_sechet_on_forking_bitcoin_ecash.mp3", "t": 3395, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153144/https://bitcoin-takeover.com/s17-e19-amaury-sechet-on-forking-bitcoin-twice-quantum-fud-scars-from-the-block-size-wars/", "archive_date": "20261113153144", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e19-daa": {"kind": "episode", "title": "S17 E19: Amaury Séchet — why many big blockers resisted changing BCH's difficulty algorithm", "url": "https://bitcoin-takeover.com/audio/media/2026-04-18_s17_e19_deadalnix_amaury_sechet_on_forking_bitcoin_ecash.mp3", "t": 6336, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153144/https://bitcoin-takeover.com/s17-e19-amaury-sechet-on-forking-bitcoin-twice-quantum-fud-scars-from-the-block-size-wars/", "archive_date": "20261113153144", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e39-split": {"kind": "episode", "title": "S17 E39: Kurt Wuckert Jr. — on the BCH/BSV split", "url": "https://bitcoin-takeover.com/audio/media/2026-08-23_s17_e39_kurt_wuckert_jr._on_bsv_big_block_bitcoin.mp3", "t": 3890, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135410/https://bitcoin-takeover.com/s17-e39-kurt-wuckert-jr-on-the-big-block-wars-bsv-craig-wright-the-road-not-taken/", "archive_date": "20261113135410", "archive_how": "saved"}, "ep-s17e39-avalanche": {"kind": "episode", "title": "S17 E39: Kurt Wuckert Jr. — Avalanche pre-consensus and the fight with Amaury", "url": "https://bitcoin-takeover.com/audio/media/2026-08-23_s17_e39_kurt_wuckert_jr._on_bsv_big_block_bitcoin.mp3", "t": 3956, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135410/https://bitcoin-takeover.com/s17-e39-kurt-wuckert-jr-on-the-big-block-wars-bsv-craig-wright-the-road-not-taken/", "archive_date": "20261113135410", "archive_how": "saved"}, "ep-s15e34-intro": {"kind": "episode", "title": "S15 E34: Charlie Lee on Privacy & MWEB — introduction", "url": "https://bitcoin-takeover.com/audio/media/2024-04-29_s15_e34_charlie_lee_on_privacy_mweb_mimble_wimble_extension_block_-_26.04.2024_23.52.mp3", "t": 47, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824032205/https://bitcoin-takeover.com/audio/media/2024-04-29_s15_e34_charlie_lee_on_privacy_mweb_mimble_wimble_extension_block_-_26.04.2024_23.52.mp3", "archive_date": "20260824032205", "archive_how": "existing"}, "ep-s15e34-blocks": {"kind": "episode", "title": "S15 E34: Charlie Lee — “a bigger block is still good”, with trade-offs", "url": "https://bitcoin-takeover.com/audio/media/2024-04-29_s15_e34_charlie_lee_on_privacy_mweb_mimble_wimble_extension_block_-_26.04.2024_23.52.mp3", "t": 572, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824032205/https://bitcoin-takeover.com/audio/media/2024-04-29_s15_e34_charlie_lee_on_privacy_mweb_mimble_wimble_extension_block_-_26.04.2024_23.52.mp3", "archive_date": "20260824032205", "archive_how": "existing"}, "ep-s17e33-dash": {"kind": "episode", "title": "S17 E33: Joël Valenzuela — how Dash became his primary money", "url": "https://bitcoin-takeover.com/audio/media/2026-07-27_s17_e33_joel_valenzuela_on_private_digital_cash_living_without_banks_mono.mp3", "t": 2786, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824022744/https://bitcoin-takeover.com/audio/media/2026-07-27_s17_e33_joel_valenzuela_on_private_digital_cash_living_without_banks_mono.mp3", "archive_date": "20260824022744", "archive_how": "existing"}, "ep-s17e37-launch": {"kind": "episode", "title": "S17 E37: Paul Sztorc on the eCash three-stage launch", "url": "https://bitcoin-takeover.com/audio/media/2026-08-13_s17_e37_paul_sztorc_on_launching_ecash_ecx_.mp3", "t": 80, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153615/https://bitcoin-takeover.com/s17-e37-paul-sztorc-on-the-ecash-three-stage-launch-free-coins-12-drivechains/", "archive_date": "20261113153615", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e21-announce": {"kind": "episode", "title": "S17 E21: Paul Sztorc announces a hard fork of Bitcoin", "url": "https://bitcoin-takeover.com/audio/media/2026-04-24_s17_e21_paul_sztorc_on_launching_drivechains_on_ecash_in_2026_-_22.04.2026_02.17.mp3", "t": 82, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153228/https://bitcoin-takeover.com/s17-e21-paul-sztorc-hard-forks-bitcoin-to-launch-ecash-with-drivechains/", "archive_date": "20261113153228", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e21-name": {"kind": "episode", "title": "S17 E21: Paul Sztorc — “the name is eCash”", "url": "https://bitcoin-takeover.com/audio/media/2026-04-24_s17_e21_paul_sztorc_on_launching_drivechains_on_ecash_in_2026_-_22.04.2026_02.17.mp3", "t": 853, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153228/https://bitcoin-takeover.com/s17-e21-paul-sztorc-hard-forks-bitcoin-to-launch-ecash-with-drivechains/", "archive_date": "20261113153228", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e17-bip110": {"kind": "episode", "title": "S17 E17: Lukas Hozda on BIP-110 — Vlad on a possible Knots/BIP-110 fork", "url": "https://bitcoin-takeover.com/audio/media/2026-04-07_s17_e17_lukas_hozda_on_bip110_bitcoin_rust.mp3", "t": 4721, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824042244/https://bitcoin-takeover.com/audio/media/2026-04-07_s17_e17_lukas_hozda_on_bip110_bitcoin_rust.mp3", "archive_date": "20260824042244", "archive_how": "existing"}, "ep-s17e42-stall": {"kind": "episode", "title": "S17 E42: Bob Summerwill — the BIP-110 chain ground to a halt", "url": "https://bitcoin-takeover.com/audio/media/2026-09-12_s17_e42_bob_summerwill_on_ethereum_classic_bitcoin_forks_-_12_09_2026_05.24.mp3", "t": 2306, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135521/https://bitcoin-takeover.com/s17-e42-bob-summerwill-on-ethereum-classic-bitcoins-fork-season/", "archive_date": "20261113135521", "archive_how": "saved"}, "ep-s17e26-forkday": {"kind": "episode", "title": "S17 E26: Calin Culianu — “I was there on Fork Day”", "url": "https://bitcoin-takeover.com/audio/media/2026-05-27_s17_e26_steve_thurmond_calin_culianu_the_phenomenal_big_blockers_master.mp3", "t": 287, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824035024/https://bitcoin-takeover.com/audio/media/2026-05-27_s17_e26_steve_thurmond_calin_culianu_the_phenomenal_big_blockers_master.mp3", "archive_date": "20260824035024", "archive_how": "existing"}, "ep-s16e29": {"kind": "episode", "title": "S16 E29: Zooko on Ecash, Bitcoin & Zcash — privacy at rest vs in flight", "url": "https://bitcoin-takeover.com/audio/media/2025-06-04_s16_e29_zooko_on_ecash_bitcoin_zcash.mp3", "t": 5507, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824043320/https://bitcoin-takeover.com/audio/media/2025-06-04_s16_e29_zooko_on_ecash_bitcoin_zcash.mp3", "archive_date": "20260824043320", "archive_how": "existing"}, "ep-s16e60": {"kind": "episode", "title": "S16 E60: Jonathan Bier on Bitcoin Civil Wars & BitMEX Research", "url": "https://bitcoin-takeover.com/audio/media/2025-11-24_s16_e60_jonathan_bier_on_bitcoin_civil_wars_bitmex_research.mp3", "t": 8005, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113152918/https://bitcoin-takeover.com/episodes/s16-e60-jonathan-bier-on-bitcoin-civil-wars-bitmex-research/", "archive_date": "20261113152918", "archive_how": "saved", "archive_of": "episode page"}, "ep-s15e26": {"kind": "episode", "title": "S15 E26: Roger Ver on Bitcoin", "url": "https://bitcoin-takeover.com/audio/media/2024-03-28_s15_e26_roger_ver_on_bitcoin.mp3", "t": 458, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113151839/https://bitcoin-takeover.com/s15-e26-roger-ver-on-hijacking-bitcoin-freedom-maximalism/", "archive_date": "20261113151839", "archive_how": "saved", "archive_of": "episode page"}, "ltc-ann": {"kind": "primary", "title": "coblee, “[ANN] Litecoin - a lite version of Bitcoin. Launched!”, Bitcointalk topic 47417 (opened 9 Oct 2011; launch noted as 13 Oct 2011 03:00 GMT)", "url": "https://bitcointalk.org/index.php?topic=47417.0", "archive_url": "https://web.archive.org/web/20261015070725/https://bitcointalk.org/index.php?topic=47417.0", "archive_date": "20261015070725", "archive_how": "existing"}, "ltc-mweb": {"kind": "primary", "title": "Litecoin Foundation, “MWEB Has Officially Activated”, 20 May 2022", "url": "https://litecoin.com/news/mweb-has-officially-activated", "archive_url": "https://web.archive.org/web/20250908062847/https://litecoin.com/news/mweb-has-officially-activated", "archive_date": "20250908062847", "archive_how": "existing"}, "doge-ann": {"kind": "primary", "title": "“[ANN][DOGE] Dogecoin - very currency many coin”, Bitcointalk topic 361813 (opened 8 Dec 2013)", "url": "https://bitcointalk.org/index.php?topic=361813.0", "archive_url": "https://web.archive.org/web/20261107224418/https://bitcointalk.org/index.php?topic=361813.0", "archive_date": "20261107224418", "archive_how": "existing"}, "doge-history": {"kind": "primary", "title": "Dogecoin.com, “The History of Dogecoin” (Dogepedia)", "url": "https://dogecoin.com/dogepedia/articles/history-of-dogecoin/", "archive_url": "https://web.archive.org/web/20261016115951/https://dogecoin.com/dogepedia/articles/history-of-dogecoin/", "archive_date": "20261016115951", "archive_how": "existing"}, "dash-ann": {"kind": "primary", "title": "eduffield, “[ANN][DASH] Dash” (opened as XCoin, 18 Jan 2014), Bitcointalk topic 421615", "url": "https://bitcointalk.org/index.php?topic=421615.0", "archive_url": "https://web.archive.org/web/20261029035022/https://bitcointalk.org/index.php?topic=421615.0", "archive_date": "20261029035022", "archive_how": "existing"}, "dash-wp": {"kind": "secondary", "title": "Wikipedia, “Dash (cryptocurrency)” — rebrand to Dash in March 2015 (cites Fortune, 26 Jun 2017)", "url": "https://en.wikipedia.org/wiki/Dash_(cryptocurrency)", "archive_url": "https://web.archive.org/web/20261031203906/https://en.wikipedia.org/wiki/Dash_(cryptocurrency)", "archive_date": "20261031203906", "archive_how": "existing"}, "zec-begins": {"kind": "primary", "title": "Electric Coin Co., “Zcash begins”, 28 Oct 2016 (archived on zodl.com)", "url": "https://zodl.com/zcash-begins/", "archive_url": "https://web.archive.org/web/20261113151609/https://zodl.com/zcash-begins/", "archive_date": "20261113151609", "archive_how": "saved"}, "zerocash": {"kind": "primary", "title": "Ben-Sasson et al., “Zerocash: Decentralized Anonymous Payments from Bitcoin” (2014)", "url": "https://zerocash-project.org/paper", "archive_url": "https://web.archive.org/web/20260826045753/https://zerocash-project.org/paper", "archive_date": "20260826045753", "archive_how": "existing", "dead": "TLS certificate invalid on 2026-11-13"}, "zec-counterfeit": {"kind": "primary", "title": "ECC, “Zcash Counterfeiting Vulnerability Successfully Remediated” (Feb 2019)", "url": "https://electriccoin.co/blog/zcash-counterfeiting-vulnerability-successfully-remediated/", "archive_url": "https://web.archive.org/web/20260823054342/https://electriccoin.co/blog/zcash-counterfeiting-vulnerability-successfully-remediated/", "archive_date": "20260823054342", "archive_how": "existing"}, "ecx-faq": {"kind": "primary", "title": "ecash.com FAQ — eCash (ECX), “not XEC”", "url": "https://ecash.com/faq/", "archive_url": "https://web.archive.org/web/20261023031238/https://ecash.com/faq/", "archive_date": "20261023031238", "archive_how": "existing"}, "ecx-facts": {"kind": "primary", "title": "ecash-com/fast-facts (GitHub)", "url": "https://github.com/ecash-com/fast-facts", "archive_url": "https://web.archive.org/web/20261113143232/https://github.com/ecash-com/fast-facts", "archive_date": "20261113143232", "archive_how": "saved"}, "ecx-ct": {"kind": "secondary", "title": "Cointelegraph Magazine, “Bitcoin Holders Have Received eCash — What Can You Do With It?”", "url": "https://cointelegraph.com/magazine/bitcoin-holders-have-received-ecash-what-can-you-with-it", "archive_url": "https://web.archive.org/web/20261108153433/https://cointelegraph.com/magazine/bitcoin-holders-have-received-ecash-what-can-you-with-it", "archive_date": "20261108153433", "archive_how": "existing"}, "l2l-seed": {"kind": "secondary", "title": "CoinDesk, LayerTwo Labs raises $3M to bring drivechains to Bitcoin (20 Dec 2022)", "url": "https://www.coindesk.com/tech/2022/12/20/bitcoin-development-company-layer-2-labs-raises-3m-to-bring-drivechains-to-network", "archive_url": "https://web.archive.org/web/20240416111359/https://www.coindesk.com/tech/2022/12/20/bitcoin-development-company-layer-2-labs-raises-3m-to-bring-drivechains-to-network/", "archive_date": "20240416111359", "archive_how": "existing"}, "blake-dev": {"kind": "primary", "title": "bitcoin-blake2b.org, “Bitcoin for developers”", "url": "https://bitcoin-blake2b.org/developers", "archive_url": "https://web.archive.org/web/20261012192516/https://bitcoin-blake2b.org/developers", "archive_date": "20261012192516", "archive_how": "existing"}, "blake-faq": {"kind": "primary", "title": "bitcoin-blake2b.org FAQ", "url": "https://bitcoin-blake2b.org/faq", "archive_url": "https://web.archive.org/web/20261010033519/https://bitcoin-blake2b.org/faq", "archive_date": "20261010033519", "archive_how": "existing"}, "knots-2941": {"kind": "primary", "title": "Bitcoin Knots 29.4.1 release files", "url": "https://bitcoinknots.org/files/29.x/29.4.1.knots20260508/", "archive_url": "https://web.archive.org/web/20261113140847/https://bitcoinknots.org/files/29.x/29.4.1.knots20260508/", "archive_date": "20261113140847", "archive_how": "saved"}, "bmd-advisory": {"kind": "secondary", "title": "Bitcoin Marketing Department, BLAKE2b fork media advisory (XBT naming)", "url": "https://btcmkdept.com/news/blake2b-fork-media-advisory/", "archive_url": "https://web.archive.org/web/20261113141623/https://btcmkdept.com/news/blake2b-fork-media-advisory/", "archive_date": "20261113141623", "archive_how": "saved"}, "xec-ifp": {"kind": "primary", "title": "eCash, Infrastructure Funding Plan", "url": "https://e.cash/blog/IFP", "archive_url": "https://web.archive.org/web/20261023183814/https://e.cash/blog/IFP", "archive_date": "20261023183814", "archive_how": "existing"}, "xec-bcha": {"kind": "primary", "title": "Bitcoin ABC, BCHA rebrand page", "url": "https://www.bitcoinabc.org/bcha/", "archive_url": "https://web.archive.org/web/20261023195225/https://www.bitcoinabc.org/bcha/", "archive_date": "20261023195225", "archive_how": "existing"}, "forkdrop": {"kind": "secondary", "title": "forkdrop.io, “How many Bitcoin forks are there?” (105 projects)", "url": "https://forkdrop.io/how-many-bitcoin-forks-are-there", "archive_url": "https://web.archive.org/web/20260410110238/https://forkdrop.io/how-many-bitcoin-forks-are-there", "archive_date": "20260410110238", "archive_how": "existing", "dead": "TLS certificate invalid on 2026-11-13"}, "ep-s17e37-outro": {"kind": "episode", "title": "S17 E37: Vlad on why he backs the drivechain fork (solo outro)", "url": "https://bitcoin-takeover.com/audio/media/2026-08-13_s17_e37_paul_sztorc_on_launching_ecash_ecx_.mp3", "t": 1434, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153615/https://bitcoin-takeover.com/s17-e37-paul-sztorc-on-the-ecash-three-stage-launch-free-coins-12-drivechains/", "archive_date": "20261113153615", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e19-sponsors": {"kind": "episode", "title": "S17 E19: opening — sponsor read (includes LayerTwo Labs) and Vlad's introduction of Amaury Séchet", "url": "https://bitcoin-takeover.com/audio/media/2026-04-18_s17_e19_deadalnix_amaury_sechet_on_forking_bitcoin_ecash.mp3", "t": 92, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153144/https://bitcoin-takeover.com/s17-e19-amaury-sechet-on-forking-bitcoin-twice-quantum-fud-scars-from-the-block-size-wars/", "archive_date": "20261113153144", "archive_how": "saved", "archive_of": "episode page"}, "doge-devs": {"kind": "primary", "title": "Dogecoin.com, “Who are the current Dogecoin developers?” (Dogepedia)", "url": "https://dogecoin.com/dogepedia/articles/dogecoin-developers/", "archive_url": "https://web.archive.org/web/20250909183955/https://dogecoin.com/dogepedia/articles/dogecoin-developers/", "archive_date": "20250909183955", "archive_how": "existing"}, "ep-s15e34-ln": {"kind": "episode", "title": "S15 E34: Charlie Lee — disappointed that Lightning did not take off as expected", "url": "https://bitcoin-takeover.com/audio/media/2024-04-29_s15_e34_charlie_lee_on_privacy_mweb_mimble_wimble_extension_block_-_26.04.2024_23.52.mp3", "t": 283, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824032205/https://bitcoin-takeover.com/audio/media/2024-04-29_s15_e34_charlie_lee_on_privacy_mweb_mimble_wimble_extension_block_-_26.04.2024_23.52.mp3", "archive_date": "20260824032205", "archive_how": "existing"}, "bip9": {"kind": "primary", "title": "BIP-9 (Version bits with timeout and delay)", "url": "https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki", "archive_url": "https://web.archive.org/web/20261104000756/https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki", "archive_date": "20261104000756", "archive_how": "existing"}, "bip91": {"kind": "primary", "title": "BIP-91 (Reduced threshold Segwit MASF)", "url": "https://github.com/bitcoin/bips/blob/master/bip-0091.mediawiki", "archive_url": "https://web.archive.org/web/20261009054845/https://github.com/bitcoin/bips/blob/master/bip-0091.mediawiki", "archive_date": "20261009054845", "archive_how": "existing"}, "bip100": {"kind": "primary", "title": "BIP-100 (Dynamic maximum block size by miner vote), Jeff Garzik", "url": "https://github.com/bitcoin/bips/blob/master/bip-0100.mediawiki", "archive_url": "https://web.archive.org/web/20261009054845/https://github.com/bitcoin/bips/blob/master/bip-0100.mediawiki", "archive_date": "20261009054845", "archive_how": "existing"}, "bip101": {"kind": "primary", "title": "BIP-101 (Increase maximum block size), Gavin Andresen", "url": "https://github.com/bitcoin/bips/blob/master/bip-0101.mediawiki", "archive_url": "https://web.archive.org/web/20261020103853/https://github.com/bitcoin/bips/blob/master/bip-0101.mediawiki", "archive_date": "20261020103853", "archive_how": "existing"}, "bip102": {"kind": "primary", "title": "BIP-102 (Block size increase to 2MB), Jeff Garzik", "url": "https://github.com/bitcoin/bips/blob/master/bip-0102.mediawiki", "archive_url": "https://web.archive.org/web/20261009054845/https://github.com/bitcoin/bips/blob/master/bip-0102.mediawiki", "archive_date": "20261009054845", "archive_how": "existing"}, "bip109": {"kind": "primary", "title": "BIP-109 (Two million byte size limit with sigop and sighash limits)", "url": "https://github.com/bitcoin/bips/blob/master/bip-0109.mediawiki", "archive_url": "https://web.archive.org/web/20261009054846/https://github.com/bitcoin/bips/blob/master/bip-0109.mediawiki", "archive_date": "20261009054846", "archive_how": "existing"}, "bip141": {"kind": "primary", "title": "BIP-141 (Segregated Witness, consensus layer)", "url": "https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki", "archive_url": "https://web.archive.org/web/20261023172913/https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki", "archive_date": "20261023172913", "archive_how": "existing"}, "bip148": {"kind": "primary", "title": "BIP-148 (Mandatory activation of segwit deployment), Shaolin Fry", "url": "https://github.com/bitcoin/bips/blob/master/bip-0148.mediawiki", "archive_url": "https://web.archive.org/web/20261017061814/https://github.com/bitcoin/bips/blob/master/bip-0148.mediawiki", "archive_date": "20261017061814", "archive_how": "existing"}, "bip65": {"kind": "primary", "title": "BIP-65 (OP_CHECKLOCKTIMEVERIFY), author Peter Todd", "url": "https://github.com/bitcoin/bips/blob/master/bip-0065.mediawiki", "archive_url": "https://web.archive.org/web/20261105175251/https://github.com/bitcoin/bips/blob/master/bip-0065.mediawiki", "archive_date": "20261105175251", "archive_how": "existing"}, "bip125": {"kind": "primary", "title": "BIP-125 (Opt-in Full Replace-by-Fee Signaling), authors David A. Harding and Peter Todd", "url": "https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki", "archive_url": "https://web.archive.org/web/20261013185646/https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki", "archive_date": "20261013185646", "archive_how": "existing"}, "bip101-withdraw": {"kind": "primary", "title": "bitcoin/bips pull request #329, “Withdraw BIP 101 proposal” (Gavin Andresen, Feb 2016)", "url": "https://github.com/bitcoin/bips/pull/329", "archive_url": "https://web.archive.org/web/20221130002956/https://github.com/bitcoin/bips/pull/329", "archive_date": "20221130002956", "archive_how": "existing"}, "xt-bw": {"kind": "secondary", "title": "Bitcoin Wiki (en.bitcoin.it), “Bitcoin XT”", "url": "https://en.bitcoin.it/wiki/Bitcoin_XT", "archive_url": "https://web.archive.org/web/20260227083737/https://en.bitcoin.it/wiki/Bitcoin_XT", "archive_date": "20260227083737", "archive_how": "existing"}, "hearn-resolution": {"kind": "primary", "title": "Mike Hearn, “The resolution of the Bitcoin experiment”, 14 Jan 2016 (archived copy)", "url": "https://blog.plan99.net/the-resolution-of-the-bitcoin-experiment-dabb30201f7", "archive_url": "https://web.archive.org/web/20261030024522/https://blog.plan99.net/the-resolution-of-the-bitcoin-experiment-dabb30201f7", "archive_date": "20261030024522", "archive_how": "cdx"}, "hearn-bw": {"kind": "secondary", "title": "Bitcoin Wiki (en.bitcoin.it), “Mike Hearn”", "url": "https://en.bitcoin.it/wiki/Mike_Hearn", "archive_url": "https://web.archive.org/web/20260714190841/https://en.bitcoin.it/wiki/Mike_Hearn", "archive_date": "20260714190841", "archive_how": "existing"}, "classic-rel": {"kind": "primary", "title": "Bitcoin Classic 0.11.2 release announcement (GitHub, 10 Feb 2016)", "url": "https://github.com/bitcoinclassic/bitcoinclassic/releases/tag/v0.11.2.cl1", "archive_url": "https://web.archive.org/web/20261030012508/https://github.com/bitcoinclassic/bitcoinclassic/releases/tag/v0.11.2.cl1", "archive_date": "20261030012508", "archive_how": "existing"}, "bu-articles": {"kind": "primary", "title": "Bitcoin Unlimited, “Articles of Federation” (PDF)", "url": "https://www.bitcoinunlimited.info/resources/BUarticles.pdf", "archive_url": "https://web.archive.org/web/20250819231456/https://www.bitcoinunlimited.info/resources/BUarticles.pdf", "archive_date": "20250819231456", "archive_how": "existing"}, "wp-bu": {"kind": "secondary", "title": "Wikipedia, “Bitcoin Unlimited”", "url": "https://en.wikipedia.org/wiki/Bitcoin_Unlimited", "archive_url": "https://web.archive.org/web/20261022101536/https://en.wikipedia.org/wiki/Bitcoin_Unlimited", "archive_date": "20261022101536", "archive_how": "existing"}, "uahf-spec": {"kind": "primary", "title": "Bitcoin ABC / bitcoincash.org, UAHF technical specification (activation 1501590000)", "url": "https://github.com/bitcoincashorg/bitcoincash.org/blob/master/spec/uahf-technical-spec.md", "archive_url": "https://web.archive.org/web/20261113142944/https://github.com/bitcoincashorg/bitcoincash.org/blob/master/spec/uahf-technical-spec.md", "archive_date": "20261113142944", "archive_how": "saved"}, "rp-sighash": {"kind": "primary", "title": "bitcoincash.org, “BUIP-HF Digest for replay protected signature verification across hard forks” (SIGHASH_FORKID)", "url": "https://github.com/bitcoincashorg/bitcoincash.org/blob/master/spec/replay-protected-sighash.md", "archive_url": "https://web.archive.org/web/20260712143600/https://github.com/bitcoincashorg/bitcoincash.org/blob/master/spec/replay-protected-sighash.md", "archive_date": "20260712143600", "archive_how": "existing"}, "wp-bch": {"kind": "secondary", "title": "Wikipedia, “Bitcoin Cash”", "url": "https://en.wikipedia.org/wiki/Bitcoin_Cash", "archive_url": "https://web.archive.org/web/20261102160443/https://en.wikipedia.org/wiki/Bitcoin_Cash", "archive_date": "20261102160443", "archive_how": "existing"}, "wp-bsv": {"kind": "secondary", "title": "Wikipedia, “Bitcoin Satoshi Vision”", "url": "https://en.wikipedia.org/wiki/Bitcoin_Satoshi_Vision", "archive_url": "https://web.archive.org/web/20261022101535/https://en.wikipedia.org/wiki/Bitcoin_Satoshi_Vision", "archive_date": "20261022101535", "archive_how": "existing"}, "hk-letter": {"kind": "primary", "title": "Bitcoin Roundtable, “Bitcoin Roundtable Consensus”, Medium, 20 Feb 2016 (Wayback Machine copy)", "url": "https://web.archive.org/web/2016/https://medium.com/@bitcoinroundtable/bitcoin-roundtable-consensus-266d475a61ff", "archive_url": "https://web.archive.org/web/2016/https://medium.com/@bitcoinroundtable/bitcoin-roundtable-consensus-266d475a61ff", "archive_date": "2016", "archive_how": "already-wayback"}, "nya-letter": {"kind": "primary", "title": "Digital Currency Group, “Bitcoin Scaling Agreement at Consensus 2017”, Medium, 23 May 2017 (Wayback Machine copy)", "url": "https://web.archive.org/web/2017/https://medium.com/@DCGco/bitcoin-scaling-agreement-at-consensus-2017-133521fe9a77", "archive_url": "https://web.archive.org/web/2017/https://medium.com/@DCGco/bitcoin-scaling-agreement-at-consensus-2017-133521fe9a77", "archive_date": "2017", "archive_how": "already-wayback"}, "s2x-announce": {"kind": "primary", "title": "segwit2x.github.io, “Bitcoin Upgrade at Block 494,784”", "url": "https://github.com/segwit2x/segwit2x.github.io/blob/master/segwit2x-announce.md", "archive_url": "https://web.archive.org/web/20230721174905/https://github.com/segwit2x/segwit2x.github.io/blob/master/segwit2x-announce.md", "archive_date": "20230721174905", "archive_how": "existing"}, "s2x-suspend": {"kind": "primary", "title": "Mike Belshe et al., “Segwit2x Final Steps”, bitcoin-segwit2x mailing list, 8 Nov 2017 (Wayback Machine copy)", "url": "https://web.archive.org/web/2017/https://lists.linuxfoundation.org/pipermail/bitcoin-segwit2x/2017-November/000685.html", "archive_url": "https://web.archive.org/web/2017/https://lists.linuxfoundation.org/pipermail/bitcoin-segwit2x/2017-November/000685.html", "archive_date": "2017", "archive_how": "already-wayback"}, "roadmap-2015": {"kind": "primary", "title": "Bitcoin Core, “Capacity increases for the Bitcoin system” (signatories), 21 Dec 2015", "url": "https://bitcoincore.org/en/2015/12/21/capacity-increase/", "archive_url": "https://web.archive.org/web/20260622102319/https://bitcoincore.org/en/2015/12/21/capacity-increase/", "archive_date": "20260622102319", "archive_how": "existing"}, "garzik-patch": {"kind": "primary", "title": "jgarzik, “[PATCH] increase block size limit”, Bitcointalk, 3 Oct 2010", "url": "https://bitcointalk.org/index.php?topic=1347.msg15121#msg15121", "archive_url": "https://web.archive.org/web/20260307185256/https://bitcointalk.org/index.php?topic=1347.msg15121", "archive_date": "20260307185256", "archive_how": "existing"}, "garzik-bw": {"kind": "secondary", "title": "Bitcoin Wiki (en.bitcoin.it), “Jeff Garzik”", "url": "https://en.bitcoin.it/wiki/Jeff_Garzik", "archive_url": "https://web.archive.org/web/20260519132607/https://en.bitcoin.it/wiki/Jeff_Garzik", "archive_date": "20260519132607", "archive_how": "existing"}, "coinjoin": {"kind": "primary", "title": "gmaxwell, “CoinJoin: Bitcoin privacy for the real world”, Bitcointalk, 22 Aug 2013", "url": "https://bitcointalk.org/index.php?topic=279249.0", "archive_url": "https://web.archive.org/web/20261021082220/https://bitcointalk.org/index.php?topic=279249.0", "archive_date": "20261021082220", "archive_how": "existing"}, "ptodd-zcash": {"kind": "primary", "title": "Peter Todd, “Cypherpunk Desert Bus: My Role In The 2016 Zcash Trusted Setup Ceremony”", "url": "https://petertodd.org/2016/cypherpunk-desert-bus-zcash-trusted-setup-ceremony", "archive_url": "https://web.archive.org/web/20261028020307/https://petertodd.org/2016/cypherpunk-desert-bus-zcash-trusted-setup-ceremony", "archive_date": "20261028020307", "archive_how": "existing"}, "wp-gavin": {"kind": "secondary", "title": "Wikipedia, “Gavin Andresen”", "url": "https://en.wikipedia.org/wiki/Gavin_Andresen", "archive_url": "https://web.archive.org/web/20261109133707/https://en.wikipedia.org/wiki/Gavin_Andresen", "archive_date": "20261109133707", "archive_how": "existing"}, "wp-wright": {"kind": "secondary", "title": "Wikipedia, “Craig Steven Wright”", "url": "https://en.wikipedia.org/wiki/Craig_Steven_Wright", "archive_url": "https://web.archive.org/web/20261022123212/https://en.wikipedia.org/wiki/Craig_Steven_Wright", "archive_date": "20261022123212", "archive_how": "existing"}, "wp-jihan": {"kind": "secondary", "title": "Wikipedia, “Jihan Wu”", "url": "https://en.wikipedia.org/wiki/Jihan_Wu", "archive_url": "https://web.archive.org/web/20261023094803/https://en.wikipedia.org/wiki/Jihan_Wu", "archive_date": "20261023094803", "archive_how": "existing"}, "wp-back": {"kind": "secondary", "title": "Wikipedia, “Adam Back”", "url": "https://en.wikipedia.org/wiki/Adam_Back", "archive_url": "https://web.archive.org/web/20261109134219/https://en.wikipedia.org/wiki/Adam_Back", "archive_date": "20261109134219", "archive_how": "existing"}, "wp-bitmain": {"kind": "secondary", "title": "Wikipedia, “Bitmain”", "url": "https://en.wikipedia.org/wiki/Bitmain", "archive_url": "https://web.archive.org/web/20261022101537/https://en.wikipedia.org/wiki/Bitmain", "archive_date": "20261022101537", "archive_how": "existing"}, "wp-blockstream": {"kind": "secondary", "title": "Wikipedia, “Blockstream”", "url": "https://en.wikipedia.org/wiki/Blockstream", "archive_url": "https://web.archive.org/web/20261018161316/https://en.wikipedia.org/wiki/Blockstream", "archive_date": "20261018161316", "archive_how": "existing"}, "copa-judgment": {"kind": "primary", "title": "COPA v Wright, [2024] EWHC 1198 (Ch), judgment of Mellor J, 20 May 2024", "url": "https://www.judiciary.uk/wp-content/uploads/2024/05/COPA-v-Wright-Judgment.pdf", "archive_url": "https://web.archive.org/web/20261104071131/https://www.judiciary.uk/wp-content/uploads/2024/05/COPA-v-Wright-Judgment.pdf", "archive_date": "20261104071131", "archive_how": "existing"}, "nmc-ann": {"kind": "primary", "title": "vinced, “[announce] Namecoin - a distributed naming system based on Bitcoin”, Bitcointalk topic 6017 (18 Apr 2011)", "url": "https://bitcointalk.org/index.php?topic=6017.0", "archive_url": "https://web.archive.org/web/20261018041713/https://bitcointalk.org/index.php?topic=6017.0", "archive_date": "20261018041713", "archive_how": "existing"}, "nmc-chainparams": {"kind": "primary", "title": "Namecoin Core, src/kernel/chainparams.cpp (genesis time, AuxPoW start height, soft-fork heights)", "url": "https://github.com/namecoin/namecoin-core/blob/master/src/kernel/chainparams.cpp", "archive_url": "https://web.archive.org/web/20261113143330/https://github.com/namecoin/namecoin-core/blob/master/src/kernel/chainparams.cpp", "archive_date": "20261113143330", "archive_how": "saved"}, "bw-merged": {"kind": "secondary", "title": "Bitcoin Wiki (en.bitcoin.it), “Merged mining specification”", "url": "https://en.bitcoin.it/wiki/Merged_mining_specification", "archive_url": "https://web.archive.org/web/20261015070725/https://en.bitcoin.it/wiki/Merged_mining_specification", "archive_date": "20261015070725", "archive_how": "existing"}, "bw-softfork": {"kind": "secondary", "title": "Bitcoin Wiki (en.bitcoin.it), “Softfork”", "url": "https://en.bitcoin.it/wiki/Softfork", "archive_url": "https://web.archive.org/web/20261011114929/https://en.bitcoin.it/wiki/Softfork", "archive_date": "20261011114929", "archive_how": "existing"}, "bw-hardfork": {"kind": "secondary", "title": "Bitcoin Wiki (en.bitcoin.it), “Hardfork”", "url": "https://en.bitcoin.it/wiki/Hardfork", "archive_url": "https://web.archive.org/web/20260929151555/https://en.bitcoin.it/wiki/Hardfork", "archive_date": "20260929151555", "archive_how": "existing"}, "ppc-ann": {"kind": "primary", "title": "Sunny King, “[ANN] [PPC] PPCoin Released!”, Bitcointalk topic 101820, 19 Aug 2012", "url": "https://bitcointalk.org/index.php?topic=101820.0", "archive_url": "https://web.archive.org/web/20261004043649/https://bitcointalk.org/index.php?topic=101820.0", "archive_date": "20261004043649", "archive_how": "existing"}, "ppc-readme": {"kind": "primary", "title": "peercoin/peercoin README (GitHub)", "url": "https://github.com/peercoin/peercoin", "archive_url": "https://web.archive.org/web/20260802184554/https://github.com/peercoin/peercoin", "archive_date": "20260802184554", "archive_how": "existing"}, "wp-peercoin": {"kind": "secondary", "title": "Wikipedia, “Peercoin”", "url": "https://en.wikipedia.org/wiki/Peercoin", "archive_url": "https://web.archive.org/web/20261105094754/https://en.wikipedia.org/wiki/Peercoin", "archive_date": "20261105094754", "archive_how": "existing"}, "ftc-ann": {"kind": "primary", "title": "bushstar, “Feathercoin [FTC]” announcement thread, Bitcointalk topic 178286 (opened 16 Apr 2013)", "url": "https://bitcointalk.org/index.php?topic=178286.0", "archive_url": "https://web.archive.org/web/20260313051957/https://bitcointalk.org/index.php?topic=178286.0", "archive_date": "20260313051957", "archive_how": "existing"}, "bcd-readme": {"kind": "primary", "title": "eveybcd/BitcoinDiamond README (GitHub)", "url": "https://github.com/eveybcd/BitcoinDiamond", "archive_url": "https://web.archive.org/web/20260526112910/https://github.com/eveybcd/bitcoindiamond", "archive_date": "20260526112910", "archive_how": "existing"}, "btc-495866": {"kind": "primary", "title": "mempool.space, Bitcoin block 495,866 (header time 2017-11-24 09:20:12 UTC)", "url": "https://mempool.space/block/495866", "archive_url": "https://web.archive.org/web/20261113143824/https://mempool.space/block/495866", "archive_date": "20261113143824", "archive_how": "saved"}, "btcp-readme": {"kind": "primary", "title": "BTCPrivate/BitcoinPrivate-legacy README (GitHub)", "url": "https://github.com/BTCPrivate/BitcoinPrivate-legacy", "archive_url": "https://web.archive.org/web/20260201113811/https://github.com/BTCPrivate/BitcoinPrivate-legacy", "archive_date": "20260201113811", "archive_how": "existing"}, "btcp-bw": {"kind": "secondary", "title": "BitcoinWiki (bitcoinwiki.org), “Hardfork Bitcoin Private”", "url": "https://bitcoinwiki.org/wiki/Hardfork_Bitcoin_Private", "archive_url": "https://web.archive.org/web/20261113141538/https://bitcoinwiki.org/wiki/Hardfork_Bitcoin_Private", "archive_date": "20261113141538", "archive_how": "saved"}, "btcp-51": {"kind": "secondary", "title": "news.Bitcoin.com, “Hacker Livestreams 51% Attack on Bitcoin Private”, 14 Oct 2018", "url": "https://news.bitcoin.com/hacker-livestreams-51-attack-on-bitcoin-private/", "archive_url": "https://web.archive.org/web/20260212224121/https://news.bitcoin.com/hacker-livestreams-51-attack-on-bitcoin-private/", "archive_date": "20260212224121", "archive_how": "existing"}, "btc-511346": {"kind": "primary", "title": "mempool.space, Bitcoin block 511,346 (header time 2018-02-28 17:06:58 UTC)", "url": "https://mempool.space/block/511346", "archive_url": "https://web.archive.org/web/20261113145941/https://mempool.space/block/511346", "archive_date": "20261113145941", "archive_how": "saved"}, "sbtc-ann": {"kind": "primary", "title": "“Super Bitcoin” official announcement thread, Bitcointalk topic 2546577 (opened 8 Dec 2017)", "url": "https://bitcointalk.org/index.php?topic=2546577.0", "archive_url": "https://web.archive.org/web/20260812064813/https://bitcointalk.org/index.php?topic=2546577.0", "archive_date": "20260812064813", "archive_how": "existing"}, "sbtc-readme": {"kind": "primary", "title": "superbitcoin/SuperBitcoin README (GitHub)", "url": "https://github.com/superbitcoin/SuperBitcoin", "archive_url": "https://web.archive.org/web/20260308004946/https://github.com/superbitcoin/SuperBitcoin", "archive_date": "20260308004946", "archive_how": "existing"}, "btc-498888": {"kind": "primary", "title": "mempool.space, Bitcoin block 498,888 (header time 2017-12-12 10:29:53 UTC)", "url": "https://mempool.space/block/498888", "archive_url": "https://web.archive.org/web/20261113144232/https://mempool.space/block/498888", "archive_date": "20261113144232", "archive_how": "saved"}, "bca-readme": {"kind": "primary", "title": "bitcoin-atom/bitcoin-atom README (GitHub)", "url": "https://github.com/bitcoin-atom/bitcoin-atom", "archive_url": "https://web.archive.org/web/20251120004111/https://github.com/bitcoin-atom/bitcoin-atom", "archive_date": "20251120004111", "archive_how": "existing"}, "btc-505888": {"kind": "primary", "title": "mempool.space, Bitcoin block 505,888 (header time 2018-01-24 14:26:41 UTC)", "url": "https://mempool.space/block/505888", "archive_url": "https://web.archive.org/web/20261113145356/https://mempool.space/block/505888", "archive_date": "20261113145356", "archive_how": "saved"}, "bci-readme": {"kind": "primary", "title": "BitcoinInterestOfficial/BitcoinInterest README (GitHub)", "url": "https://github.com/BitcoinInterestOfficial/BitcoinInterest", "archive_url": "https://web.archive.org/web/20230115080107/https://github.com/BitcoinInterestOfficial/BitcoinInterest", "archive_date": "20230115080107", "archive_how": "existing"}, "btc-505083": {"kind": "primary", "title": "mempool.space, Bitcoin block 505,083 (header time 2018-01-20 02:04:45 UTC)", "url": "https://mempool.space/block/505083", "archive_url": "https://web.archive.org/web/20261113145329/https://mempool.space/block/505083", "archive_date": "20261113145329", "archive_how": "saved"}, "ep-s17e19-clashic": {"kind": "episode", "title": "S17 E19: Amaury Séchet — Bitcoin Clashic as “more or less of a troll fork”", "url": "https://bitcoin-takeover.com/audio/media/2026-04-18_s17_e19_deadalnix_amaury_sechet_on_forking_bitcoin_ecash.mp3", "t": 6465, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153144/https://bitcoin-takeover.com/s17-e19-amaury-sechet-on-forking-bitcoin-twice-quantum-fud-scars-from-the-block-size-wars/", "archive_date": "20261113153144", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e19-ifp": {"kind": "episode", "title": "S17 E19: Amaury Séchet — the funding dispute at the core of the 2020 split", "url": "https://bitcoin-takeover.com/audio/media/2026-04-18_s17_e19_deadalnix_amaury_sechet_on_forking_bitcoin_ecash.mp3", "t": 8785, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153144/https://bitcoin-takeover.com/s17-e19-amaury-sechet-on-forking-bitcoin-twice-quantum-fud-scars-from-the-block-size-wars/", "archive_date": "20261113153144", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e19-roger2x": {"kind": "episode", "title": "S17 E19: Amaury Séchet — Roger Ver joined BCH after SegWit2x failed", "url": "https://bitcoin-takeover.com/audio/media/2026-04-18_s17_e19_deadalnix_amaury_sechet_on_forking_bitcoin_ecash.mp3", "t": 13739, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153144/https://bitcoin-takeover.com/s17-e19-amaury-sechet-on-forking-bitcoin-twice-quantum-fud-scars-from-the-block-size-wars/", "archive_date": "20261113153144", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e39-replay": {"kind": "episode", "title": "S17 E39: Kurt Wuckert Jr. — the SV node had no replay protection", "url": "https://bitcoin-takeover.com/audio/media/2026-08-23_s17_e39_kurt_wuckert_jr._on_bsv_big_block_bitcoin.mp3", "t": 4015, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135410/https://bitcoin-takeover.com/s17-e39-kurt-wuckert-jr-on-the-big-block-wars-bsv-craig-wright-the-road-not-taken/", "archive_date": "20261113135410", "archive_how": "saved"}, "ep-s17e39-hashwar": {"kind": "episode", "title": "S17 E39: Kurt Wuckert Jr. on the 2018 hash war", "url": "https://bitcoin-takeover.com/audio/media/2026-08-23_s17_e39_kurt_wuckert_jr._on_bsv_big_block_bitcoin.mp3", "t": 4188, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135410/https://bitcoin-takeover.com/s17-e39-kurt-wuckert-jr-on-the-big-block-wars-bsv-craig-wright-the-road-not-taken/", "archive_date": "20261113135410", "archive_how": "saved"}, "ep-s17e39-checkpoint": {"kind": "episode", "title": "S17 E39: Kurt Wuckert Jr. — ABC’s rolling checkpoint during the hash war", "url": "https://bitcoin-takeover.com/audio/media/2026-08-23_s17_e39_kurt_wuckert_jr._on_bsv_big_block_bitcoin.mp3", "t": 4383, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135410/https://bitcoin-takeover.com/s17-e39-kurt-wuckert-jr-on-the-big-block-wars-bsv-craig-wright-the-road-not-taken/", "archive_date": "20261113135410", "archive_how": "saved"}, "ep-s17e26-bchn": {"kind": "episode", "title": "S17 E26: Calin Culianu — from Bitcoin ABC to Bitcoin Cash Node", "url": "https://bitcoin-takeover.com/audio/media/2026-05-27_s17_e26_steve_thurmond_calin_culianu_the_phenomenal_big_blockers_master.mp3", "t": 8703, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824035024/https://bitcoin-takeover.com/audio/media/2026-05-27_s17_e26_steve_thurmond_calin_culianu_the_phenomenal_big_blockers_master.mp3", "archive_date": "20260824035024", "archive_how": "existing"}, "ep-s16e60-2x": {"kind": "episode", "title": "S16 E60: Jonathan Bier — the SegWit2x cancellation and the BCH price spike", "url": "https://bitcoin-takeover.com/audio/media/2025-11-24_s16_e60_jonathan_bier_on_bitcoin_civil_wars_bitmex_research.mp3", "t": 7274, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113152918/https://bitcoin-takeover.com/episodes/s16-e60-jonathan-bier-on-bitcoin-civil-wars-bitmex-research/", "archive_date": "20261113152918", "archive_how": "saved", "archive_of": "episode page"}, "ep-s16e60-wright": {"kind": "episode", "title": "S16 E60: Jonathan Bier — Craig Wright “inadvertently” helped the small blockers", "url": "https://bitcoin-takeover.com/audio/media/2025-11-24_s16_e60_jonathan_bier_on_bitcoin_civil_wars_bitmex_research.mp3", "t": 8447, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113152918/https://bitcoin-takeover.com/episodes/s16-e60-jonathan-bier-on-bitcoin-civil-wars-bitmex-research/", "archive_date": "20261113152918", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e19-otherforks": {"kind": "episode", "title": "S17 E19: Vlad asks why no later Bitcoin fork (Bitcoin Diamond and others) matched BCH", "url": "https://bitcoin-takeover.com/audio/media/2026-04-18_s17_e19_deadalnix_amaury_sechet_on_forking_bitcoin_ecash.mp3", "t": 11884, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153144/https://bitcoin-takeover.com/s17-e19-amaury-sechet-on-forking-bitcoin-twice-quantum-fud-scars-from-the-block-size-wars/", "archive_date": "20261113153144", "archive_how": "saved", "archive_of": "episode page"}, "bchn-site": {"kind": "primary", "title": "Bitcoin Cash Node, project website", "url": "https://bitcoincashnode.org/en/", "archive_url": "https://web.archive.org/web/20261002112609/https://bitcoincashnode.org/en/", "archive_date": "20261002112609", "archive_how": "existing"}, "ep-s17e19-bsv": {"kind": "episode", "title": "S17 E19: Amaury Séchet on Bitcoin SV — “whatever Craig says is gospel”", "url": "https://bitcoin-takeover.com/audio/media/2026-04-18_s17_e19_deadalnix_amaury_sechet_on_forking_bitcoin_ecash.mp3", "t": 7002, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153144/https://bitcoin-takeover.com/s17-e19-amaury-sechet-on-forking-bitcoin-twice-quantum-fud-scars-from-the-block-size-wars/", "archive_date": "20261113153144", "archive_how": "saved", "archive_of": "episode page"}, "btx-readme": {"kind": "primary", "title": "BitCore (BTX) README, GitHub LIMXTEC/BitCore", "url": "https://github.com/LIMXTEC/BitCore/blob/master/README.md", "archive_url": "https://web.archive.org/web/20261113142436/https://github.com/LIMXTEC/BitCore/blob/master/README.md", "archive_date": "20261113142436", "archive_how": "saved"}, "btx-chainparams": {"kind": "primary", "title": "BitCore (BTX) src/chainparams.cpp (genesis block, timestamp 1492973331)", "url": "https://github.com/LIMXTEC/BitCore/blob/master/src/chainparams.cpp", "archive_url": "https://web.archive.org/web/20261113142503/https://github.com/LIMXTEC/BitCore/blob/master/src/chainparams.cpp", "archive_date": "20261113142503", "archive_how": "saved"}, "btx-ann": {"kind": "primary", "title": "“[ANN][Main] Bitcore-BTX- Bitcoin UTXO Fork 2017”, Bitcointalk topic 1883902 (opened 23 Apr 2017, OP Limx Dev)", "url": "https://bitcointalk.org/index.php?topic=1883902.0", "archive_url": "https://web.archive.org/web/20260518131637/https://bitcointalk.org/index.php?topic=1883902.0", "archive_date": "20260518131637", "archive_how": "existing"}, "bcx-readme": {"kind": "primary", "title": "BitcoinX Core README, GitHub bitcoinx-project/bitcoinx", "url": "https://github.com/bitcoinx-project/bitcoinx/blob/master/README.md", "archive_url": "https://web.archive.org/web/20261113143016/https://github.com/bitcoinx-project/bitcoinx/blob/master/README.md", "archive_date": "20261113143016", "archive_how": "saved"}, "bcx-chainparams": {"kind": "primary", "title": "BitcoinX src/chainparams.cpp (BCXHeight 498889, premine parameters)", "url": "https://github.com/bitcoinx-project/bitcoinx/blob/master/src/chainparams.cpp", "archive_url": "https://web.archive.org/web/20261113143112/https://github.com/bitcoinx-project/bitcoinx/blob/master/src/chainparams.cpp", "archive_date": "20261113143112", "archive_how": "saved"}, "bcx-amount": {"kind": "primary", "title": "BitcoinX src/amount.h (BTC_2_BCX_RATE = 10000)", "url": "https://github.com/bitcoinx-project/bitcoinx/blob/master/src/amount.h", "archive_url": "https://web.archive.org/web/20261113143048/https://github.com/bitcoinx-project/bitcoinx/blob/master/src/amount.h", "archive_date": "20261113143048", "archive_how": "saved"}, "bcx-gate": {"kind": "primary", "title": "Gate.io, “BCX is listed on gate.io” exchange notice, 9 Dec 2017 (ChainWhy archive)", "url": "https://chainwhy.com/notice/3815.html", "archive_url": "https://web.archive.org/web/20261113141730/https://chainwhy.com/notice/3815.html", "archive_date": "20261113141730", "archive_how": "saved"}, "okex-bcx": {"kind": "primary", "title": "OKEx, notice on opening SBTC and BCX claims and trading, 12 Dec 2017 (ChainWhy archive, Chinese)", "url": "https://chainwhy.com/notice/3837.html", "archive_url": "https://web.archive.org/web/20261113141810/https://chainwhy.com/notice/3837.html", "archive_date": "20261113141810", "archive_how": "saved"}, "cdy-readme": {"kind": "primary", "title": "Bitcoin Candy README, GitHub bitcoincandyofficial/bitcoincandy", "url": "https://github.com/bitcoincandyofficial/bitcoincandy/blob/master/README.md", "archive_url": "https://web.archive.org/web/20261113142851/https://github.com/bitcoincandyofficial/bitcoincandy/blob/master/README.md", "archive_date": "20261113142851", "archive_how": "saved"}, "cdy-chainparams": {"kind": "primary", "title": "Bitcoin Candy src/chainparams.cpp (cdyHeight 512666; Equihash fork height 656960)", "url": "https://github.com/bitcoincandyofficial/bitcoincandy/blob/master/src/chainparams.cpp", "archive_url": "https://web.archive.org/web/20261113142918/https://github.com/bitcoincandyofficial/bitcoincandy/blob/master/src/chainparams.cpp", "archive_date": "20261113142918", "archive_how": "saved"}, "cdy-ann": {"kind": "primary", "title": "“[ANN] Bitcoin Candy - Fork 1:1000 of Bitcoin Cash”, Bitcointalk topic 2715832 (opened 9 Jan 2018)", "url": "https://bitcointalk.org/index.php?topic=2715832.0", "archive_url": "https://web.archive.org/web/20250403142455/https://bitcointalk.org/index.php?topic=2715832.0", "archive_date": "20250403142455", "archive_how": "existing"}, "cdy-site": {"kind": "primary", "title": "Bitcoin Candy official website, cdy.one (read 13 Nov 2026)", "url": "https://cdy.one/", "archive_url": "https://web.archive.org/web/20260718211342/https://cdy.one/", "archive_date": "20260718211342", "archive_how": "existing"}, "bch-512666": {"kind": "primary", "title": "Blockchair, Bitcoin Cash block 512,666 (header time 1515799972 = 2018-01-12 23:32:52 UTC)", "url": "https://blockchair.com/bitcoin-cash/block/512666", "archive_url": "https://web.archive.org/web/20210725020957/https://blockchair.com/bitcoin-cash/block/512666", "archive_date": "20210725020957", "archive_how": "existing"}, "god-readme": {"kind": "primary", "title": "Bitcoin God README, GitHub BitcoinGod/BitcoinGod", "url": "https://github.com/BitcoinGod/BitcoinGod/blob/master/README.md", "archive_url": "https://web.archive.org/web/20261113142125/https://github.com/BitcoinGod/BitcoinGod/blob/master/README.md", "archive_date": "20261113142125", "archive_how": "saved"}, "god-consensus": {"kind": "primary", "title": "Bitcoin God src/consensus/consensus.h (SUPER_BLOCK_HEIGHT 501226)", "url": "https://github.com/BitcoinGod/BitcoinGod/blob/master/src/consensus/consensus.h", "archive_url": "https://web.archive.org/web/20261113142153/https://github.com/BitcoinGod/BitcoinGod/blob/master/src/consensus/consensus.h", "archive_date": "20261113142153", "archive_how": "saved"}, "god-news": {"kind": "secondary", "title": "Bitcoin.com News, “More Bitcoin Fork Clones on the Way: Bitcoin God Will Be Born Xmas Day” (quotes Chandler Guo's tweet of 4 Dec 2017)", "url": "https://news.bitcoin.com/more-bitcoin-fork-clones-on-the-way-bitcoin-god-will-be-born-on-xmas-day/", "archive_url": "https://web.archive.org/web/20260217142539/https://news.bitcoin.com/more-bitcoin-fork-clones-on-the-way-bitcoin-god-will-be-born-on-xmas-day/", "archive_date": "20260217142539", "archive_how": "existing"}, "god-ct": {"kind": "secondary", "title": "Cointelegraph, “Forgive Me, Father, For I Have Forked: Investor To Release Bitcoin God”, 5 Dec 2017", "url": "https://cointelegraph.com/news/forgive-me-father-for-i-have-forked-investor-to-release-bitcoin-god", "archive_url": "https://web.archive.org/web/20231130090905/https://cointelegraph.com/news/forgive-me-father-for-i-have-forked-investor-to-release-bitcoin-god", "archive_date": "20231130090905", "archive_how": "existing"}, "kucoin-god": {"kind": "primary", "title": "KuCoin, “Announcement regarding the Bitcoin Fork and permanent support for all forked tokens”, 27 Dec 2017", "url": "https://www.kucoin.com/announcement/en-annoucement-regarding-the-bitcoin-fork-and-permanent-support-for-all-forked-tokens", "archive_url": "https://web.archive.org/web/20261113151534/https://www.kucoin.com/announcement/en-annoucement-regarding-the-bitcoin-fork-and-permanent-support-for-all-forked-tokens", "archive_date": "20261113151534", "archive_how": "saved"}, "btc-501225": {"kind": "primary", "title": "mempool.space, Bitcoin block 501,225 (header time 2017-12-27 06:55:44 UTC)", "url": "https://mempool.space/block/501225", "archive_url": "https://web.archive.org/web/20261113144824/https://mempool.space/block/501225", "archive_date": "20261113144824", "archive_how": "saved"}, "ubtc-readme": {"kind": "primary", "title": "UnitedBitcoin README, GitHub UnitedBitcoin/UnitedBitcoin", "url": "https://github.com/UnitedBitcoin/UnitedBitcoin/blob/master/README.md", "archive_url": "https://web.archive.org/web/20261113142611/https://github.com/UnitedBitcoin/UnitedBitcoin/blob/master/README.md", "archive_date": "20261113142611", "archive_how": "saved"}, "ubtc-chainparams": {"kind": "primary", "title": "UnitedBitcoin src/chainparams.cpp (UBCHeight 498777)", "url": "https://github.com/UnitedBitcoin/UnitedBitcoin/blob/master/src/chainparams.cpp", "archive_url": "https://web.archive.org/web/20261113142709/https://github.com/UnitedBitcoin/UnitedBitcoin/blob/master/src/chainparams.cpp", "archive_date": "20261113142709", "archive_how": "saved"}, "ubtc-ann": {"kind": "primary", "title": "“ANN: UnitedBitcoin - UBTC - Launched in Silicon Valley on Dec 12, 2017”, Bitcointalk topic 2607140 (OP united-bitcoin, last edited 21 Oct 2023)", "url": "https://bitcointalk.org/index.php?topic=2607140.0", "archive_url": "https://web.archive.org/web/20220815132509/https://bitcointalk.org/index.php?topic=2607140.0", "archive_date": "20220815132509", "archive_how": "existing"}, "ubtc-ann-p5": {"kind": "primary", "title": "UnitedBitcoin ANN thread, replies of 11–12 Jan 2018 on phase 1 and phase 2 distribution", "url": "https://bitcointalk.org/index.php?topic=2607140.80", "archive_url": "https://web.archive.org/web/20210623050245/https://bitcointalk.org/index.php?topic=2607140.80", "archive_date": "20210623050245", "archive_how": "existing"}, "ubtc-news": {"kind": "secondary", "title": "Bitcoin.com News, “After Segwit2x Failed Jeff Garzik Reveals ‘United Bitcoin’”, 14 Dec 2017", "url": "https://news.bitcoin.com/after-segwit2x-failed-jeff-garzik-reveals-united-bitcoin/", "archive_url": "https://web.archive.org/web/20250306215958/https://news.bitcoin.com/after-segwit2x-failed-jeff-garzik-reveals-united-bitcoin/", "archive_date": "20250306215958", "archive_how": "existing"}, "zb-ubtc": {"kind": "primary", "title": "ZB exchange, notice that UBTC and SBTC were distributed, 12 Dec 2017 (ChainWhy archive, Chinese)", "url": "https://chainwhy.com/notice/3664.html", "archive_url": "https://web.archive.org/web/20261113141651/https://chainwhy.com/notice/3664.html", "archive_date": "20261113141651", "archive_how": "saved"}, "btc-498777": {"kind": "primary", "title": "mempool.space, Bitcoin block 498,777 (header time 2017-12-11 18:19:12 UTC)", "url": "https://mempool.space/block/498777", "archive_url": "https://web.archive.org/web/20261113144025/https://mempool.space/block/498777", "archive_date": "20261113144025", "archive_how": "saved"}, "lbtc-readme": {"kind": "primary", "title": "Lightning Bitcoin Core README, GitHub lbtcio/lbtc-core", "url": "https://github.com/lbtcio/lbtc-core/blob/master/README.md", "archive_url": "https://web.archive.org/web/20261113143302/https://github.com/lbtcio/lbtc-core/blob/master/README.md", "archive_date": "20261113143302", "archive_how": "saved"}, "lbtc-ann": {"kind": "primary", "title": "“[ANN][LBTC] Lightning Bitcoin | First DPoS fork of BTC”, Bitcointalk topic 2908497 (opened 9 Feb 2018)", "url": "https://bitcointalk.org/index.php?topic=2908497.0", "archive_url": "https://web.archive.org/web/20251025221613/https://bitcointalk.org/index.php?topic=2908497.0", "archive_date": "20251025221613", "archive_how": "existing"}, "lbtc-about": {"kind": "primary", "title": "Lightning Bitcoin, “About” page with project timeline (Wayback Machine copy, Chinese)", "url": "https://web.archive.org/web/2020/https://www.lbtc.io/EN/about.html", "archive_url": "https://web.archive.org/web/2020/https://www.lbtc.io/EN/about.html", "archive_date": "2020", "archive_how": "already-wayback"}, "btc-499999": {"kind": "primary", "title": "mempool.space, Bitcoin block 499,999 (header time 2017-12-18 18:34:47 UTC)", "url": "https://mempool.space/block/499999", "archive_url": "https://web.archive.org/web/20261113144500/https://mempool.space/block/499999", "archive_date": "20261113144500", "archive_how": "saved"}, "knots-site": {"kind": "primary", "title": "Bitcoin Knots official website, bitcoinknots.org (read 13 Nov 2026)", "url": "https://bitcoinknots.org/", "archive_url": "https://web.archive.org/web/20261006110728/https://bitcoinknots.org/", "archive_date": "20261006110728", "archive_how": "existing"}, "knots-gh": {"kind": "primary", "title": "GitHub, bitcoinknots/bitcoin repository metadata (created 25 Feb 2016)", "url": "https://github.com/bitcoinknots/bitcoin", "archive_url": "https://web.archive.org/web/20260815095456/https://github.com/bitcoinknots/bitcoin", "archive_date": "20260815095456", "archive_how": "existing"}, "bw-knots": {"kind": "secondary", "title": "Bitcoin Wiki, “Bitcoin Knots” (revision 65116, March 2018)", "url": "https://en.bitcoin.it/wiki/Bitcoin_Knots", "archive_url": "https://web.archive.org/web/20261019175524/https://en.bitcoin.it/wiki/Bitcoin_Knots", "archive_date": "20261019175524", "archive_how": "existing"}, "zcl-ann": {"kind": "primary", "title": "“[ANN] Zclassic, Zcash Fork No Premine, No 20% Founders Tax”, Bitcointalk topic 1671982 (opened 6 Nov 2016)", "url": "https://bitcointalk.org/index.php?topic=1671982.0", "archive_url": "https://web.archive.org/web/20260913160757/https://bitcointalk.org/index.php?topic=1671982.0", "archive_date": "20260913160757", "archive_how": "existing"}, "zcl-readme": {"kind": "primary", "title": "Zclassic README, GitHub ZclassicCommunity/zclassic", "url": "https://github.com/ZclassicCommunity/zclassic/blob/master/README.md", "archive_url": "https://web.archive.org/web/20241217175026/https://github.com/ZclassicCommunity/zclassic/blob/master/README.md", "archive_date": "20241217175026", "archive_how": "existing"}, "wp-firo": {"kind": "secondary", "title": "Wikipedia, “Firo (cryptocurrency)”", "url": "https://en.wikipedia.org/wiki/Firo_(cryptocurrency)", "archive_url": "https://web.archive.org/web/20261030225754/https://en.wikipedia.org/wiki/Firo_(cryptocurrency)", "archive_date": "20261030225754", "archive_how": "existing"}, "firo-readme": {"kind": "primary", "title": "Firo README, GitHub firoorg/firo", "url": "https://github.com/firoorg/firo/blob/master/README.md", "archive_url": "https://web.archive.org/web/20241215005535/https://github.com/firoorg/firo/blob/master/README.md", "archive_date": "20241215005535", "archive_how": "existing"}, "ep-s16e5-launch": {"kind": "episode", "title": "S16 E5: Reuben Yap on Zcoin's launch and the 2017 Zerocoin bug", "url": "https://bitcoin-takeover.com/audio/media/2025-01-30_s16_e5_reuben_yap_on_firo_zk_privacy_research_-_16.01.2025_18.07_-_30.01.2025_02.33.mp3", "t": 3328, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824031821/https://bitcoin-takeover.com/audio/media/2025-01-30_s16_e5_reuben_yap_on_firo_zk_privacy_research_-_16.01.2025_18.07_-_30.01.2025_02.33.mp3", "archive_date": "20260824031821", "archive_how": "existing"}, "ep-s16e5-bug": {"kind": "episode", "title": "S16 E5: Reuben Yap on the missing equal sign", "url": "https://bitcoin-takeover.com/audio/media/2025-01-30_s16_e5_reuben_yap_on_firo_zk_privacy_research_-_16.01.2025_18.07_-_30.01.2025_02.33.mp3", "t": 3575, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824031821/https://bitcoin-takeover.com/audio/media/2025-01-30_s16_e5_reuben_yap_on_firo_zk_privacy_research_-_16.01.2025_18.07_-_30.01.2025_02.33.mp3", "archive_date": "20260824031821", "archive_how": "existing"}, "ep-s16e5-rebrand": {"kind": "episode", "title": "S16 E5: Reuben Yap on why Zcoin became Firo", "url": "https://bitcoin-takeover.com/audio/media/2025-01-30_s16_e5_reuben_yap_on_firo_zk_privacy_research_-_16.01.2025_18.07_-_30.01.2025_02.33.mp3", "t": 3760, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824031821/https://bitcoin-takeover.com/audio/media/2025-01-30_s16_e5_reuben_yap_on_firo_zk_privacy_research_-_16.01.2025_18.07_-_30.01.2025_02.33.mp3", "archive_date": "20260824031821", "archive_how": "existing"}, "vtc-readme": {"kind": "primary", "title": "Vertcoin Core README, GitHub vertcoin-project/vertcoin-core", "url": "https://github.com/vertcoin-project/vertcoin-core/blob/master/README.md", "archive_url": "https://web.archive.org/web/20230214182516/https://github.com/vertcoin-project/vertcoin-core/blob/master/README.md", "archive_date": "20230214182516", "archive_how": "existing"}, "vtc-chainparams": {"kind": "primary", "title": "Vertcoin Core src/chainparams.cpp (mainnet genesis timestamp 1389311371)", "url": "https://github.com/vertcoin-project/vertcoin-core/blob/master/src/chainparams.cpp", "archive_url": "https://web.archive.org/web/20250117164314/https://github.com/vertcoin-project/vertcoin-core/blob/master/src/chainparams.cpp", "archive_date": "20250117164314", "archive_how": "existing"}, "wp-vtc": {"kind": "secondary", "title": "Wikipedia, “Vertcoin”", "url": "https://en.wikipedia.org/wiki/Vertcoin", "archive_url": "https://web.archive.org/web/20261022101523/https://en.wikipedia.org/wiki/Vertcoin", "archive_date": "20261022101523", "archive_how": "existing"}, "bip340": {"kind": "primary", "title": "BIP-340 (Schnorr Signatures for secp256k1), Wuille, Nick, Ruffing", "url": "https://github.com/bitcoin/bips/blob/master/bip-0340.mediawiki", "archive_url": "https://web.archive.org/web/20261028034101/https://github.com/bitcoin/bips/blob/master/bip-0340.mediawiki", "archive_date": "20261028034101", "archive_how": "existing"}, "bip341": {"kind": "primary", "title": "BIP-341 (Taproot: SegWit version 1 spending rules), Wuille, Nick, Towns", "url": "https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki", "archive_url": "https://web.archive.org/web/20261101215205/https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki", "archive_date": "20261101215205", "archive_how": "existing"}, "bip342": {"kind": "primary", "title": "BIP-342 (Validation of Taproot Scripts), Wuille, Nick, Towns", "url": "https://github.com/bitcoin/bips/blob/master/bip-0342.mediawiki", "archive_url": "https://web.archive.org/web/20261103091205/https://github.com/bitcoin/bips/blob/master/bip-0342.mediawiki", "archive_date": "20261103091205", "archive_how": "existing"}, "bip66": {"kind": "primary", "title": "BIP-66 (Strict DER signatures), Pieter Wuille", "url": "https://github.com/bitcoin/bips/blob/master/bip-0066.mediawiki", "archive_url": "https://web.archive.org/web/20261019173042/https://github.com/bitcoin/bips/blob/master/bip-0066.mediawiki", "archive_date": "20261019173042", "archive_how": "existing"}, "bip8": {"kind": "primary", "title": "BIP-8 (Version bits with lock-in by height), Shaolin Fry and Luke Dashjr", "url": "https://github.com/bitcoin/bips/blob/master/bip-0008.mediawiki", "archive_url": "https://web.archive.org/web/20261019205621/https://github.com/bitcoin/bips/blob/master/bip-0008.mediawiki", "archive_date": "20261019205621", "archive_how": "existing"}, "sipa-gh": {"kind": "primary", "title": "GitHub profile of sipa (Pieter Wuille), read 13 Nov 2026", "url": "https://github.com/sipa", "archive_url": "https://web.archive.org/web/20261018031247/https://github.com/sipa", "archive_date": "20261018031247", "archive_how": "existing"}, "laanwj-gh": {"kind": "primary", "title": "GitHub profile of laanwj, read 13 Nov 2026", "url": "https://github.com/laanwj", "archive_url": "https://web.archive.org/web/20261028182751/https://github.com/laanwj", "archive_date": "20261028182751", "archive_how": "existing"}, "bw-wladimir": {"kind": "secondary", "title": "Bitcoin Wiki, “Wladimir van der Laan” (revision 70532)", "url": "https://en.bitcoin.it/wiki/Wladimir_van_der_Laan", "archive_url": "https://web.archive.org/web/20261019185522/https://en.bitcoin.it/wiki/Wladimir_van_der_Laan", "archive_date": "20261019185522", "archive_how": "existing"}, "laanwj-gyre": {"kind": "primary", "title": "laanwj, “The widening gyre”, Laanwj's blog, 21 Jan 2021", "url": "https://laanwj.github.io/2021/01/21/decentralize.html", "archive_url": "https://web.archive.org/web/20261020144546/https://laanwj.github.io/2021/01/21/decentralize.html", "archive_date": "20261020144546", "archive_how": "existing"}, "laanwj-regrets": {"kind": "primary", "title": "laanwj, “Of regrets”, Laanwj's blog, 6 Feb 2023", "url": "https://laanwj.github.io/2023/02/06/regrets.html", "archive_url": "https://web.archive.org/web/20261105112149/https://laanwj.github.io/2023/02/06/regrets.html", "archive_date": "20261105112149", "archive_how": "existing"}, "laanwj-finally": {"kind": "primary", "title": "laanwj, “Finally”, Laanwj's blog, 19 Mar 2024", "url": "https://laanwj.github.io/2024/03/19/finally.html", "archive_url": "https://web.archive.org/web/20261105112149/https://laanwj.github.io/2024/03/19/finally.html", "archive_date": "20261105112149", "archive_how": "existing"}, "laanwj-2016": {"kind": "primary", "title": "laanwj, “Dazed and confused, but trying to continue”, Laanwj's blog, 6 May 2016", "url": "https://laanwj.github.io/2016/05/06/hostility-scams-and-moving-forward.html", "archive_url": "https://web.archive.org/web/20261105112149/https://laanwj.github.io/2016/05/06/hostility-scams-and-moving-forward.html", "archive_date": "20261105112149", "archive_how": "existing"}, "rizun-feemarket": {"kind": "primary", "title": "Peter R. Rizun, “A Transaction Fee Market Exists Without a Block Size Limit”, working paper, 4 Aug 2015", "url": "https://www.bitcoinunlimited.info/resources/feemarket.pdf", "archive_url": "https://web.archive.org/web/20261108011704/https://www.bitcoinunlimited.info/resources/feemarket.pdf", "archive_date": "20261108011704", "archive_how": "existing"}, "ep-s16e30-intro": {"kind": "episode", "title": "S16 E30: Peter Rizun on Scaling Bitcoin with Hardware — introduction", "url": "https://bitcoin-takeover.com/audio/media/2025-06-14_s16_e30_peter_rizun_on_scaling_bitcoin_with_hardware_-_14.06.2025_16.39.mp3", "t": 49, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113152704/https://bitcoin-takeover.com/episodes/s16-e30-peter-rizun-on-scaling-bitcoin-with-hardware/", "archive_date": "20261113152704", "archive_how": "saved", "archive_of": "episode page"}, "ep-s16e30-gb": {"kind": "episode", "title": "S16 E30: Peter Rizun on gigabyte blocks as the upper target", "url": "https://bitcoin-takeover.com/audio/media/2025-06-14_s16_e30_peter_rizun_on_scaling_bitcoin_with_hardware_-_14.06.2025_16.39.mp3", "t": 692, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113152704/https://bitcoin-takeover.com/episodes/s16-e30-peter-rizun-on-scaling-bitcoin-with-hardware/", "archive_date": "20261113152704", "archive_how": "saved", "archive_of": "episode page"}, "ep-s16e30-bu": {"kind": "episode", "title": "S16 E30: Peter Rizun on what Bitcoin Unlimited was trying to show", "url": "https://bitcoin-takeover.com/audio/media/2025-06-14_s16_e30_peter_rizun_on_scaling_bitcoin_with_hardware_-_14.06.2025_16.39.mp3", "t": 4759, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113152704/https://bitcoin-takeover.com/episodes/s16-e30-peter-rizun-on-scaling-bitcoin-with-hardware/", "archive_date": "20261113152704", "archive_how": "saved", "archive_of": "episode page"}, "ep-s16e30-fee": {"kind": "episode", "title": "S16 E30: Paul Sztorc's question on the fee-market paper", "url": "https://bitcoin-takeover.com/audio/media/2025-06-14_s16_e30_peter_rizun_on_scaling_bitcoin_with_hardware_-_14.06.2025_16.39.mp3", "t": 7419, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113152704/https://bitcoin-takeover.com/episodes/s16-e30-peter-rizun-on-scaling-bitcoin-with-hardware/", "archive_date": "20261113152704", "archive_how": "saved", "archive_of": "episode page"}, "ep-s16e30-bug": {"kind": "episode", "title": "S16 E30: Peter Rizun on the Bitcoin Unlimited bug of 2017", "url": "https://bitcoin-takeover.com/audio/media/2025-06-14_s16_e30_peter_rizun_on_scaling_bitcoin_with_hardware_-_14.06.2025_16.39.mp3", "t": 8986, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113152704/https://bitcoin-takeover.com/episodes/s16-e30-peter-rizun-on-scaling-bitcoin-with-hardware/", "archive_date": "20261113152704", "archive_how": "saved", "archive_of": "episode page"}, "jan3-about": {"kind": "primary", "title": "JAN3, “About the Company” page with team biographies (read 13 Nov 2026)", "url": "https://jan3.com/about/", "archive_url": "https://web.archive.org/web/20261012023013/https://jan3.com/about", "archive_date": "20261012023013", "archive_how": "existing"}, "ep-s17e26-samson": {"kind": "episode", "title": "S17 E26: Vlad on the 2018 Roger Ver vs Samson Mow debate", "url": "https://bitcoin-takeover.com/audio/media/2026-05-27_s17_e26_steve_thurmond_calin_culianu_the_phenomenal_big_blockers_master.mp3", "t": 10934, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824035024/https://bitcoin-takeover.com/audio/media/2026-05-27_s17_e26_steve_thurmond_calin_culianu_the_phenomenal_big_blockers_master.mp3", "archive_date": "20260824035024", "archive_how": "existing"}, "wp-ayre": {"kind": "secondary", "title": "Wikipedia, “Calvin Ayre”", "url": "https://en.wikipedia.org/wiki/Calvin_Ayre", "archive_url": "https://web.archive.org/web/20260926134703/https://en.wikipedia.org/wiki/Calvin_Ayre", "archive_date": "20260926134703", "archive_how": "existing"}, "ep-s17e39-ayre": {"kind": "episode", "title": "S17 E39: Kurt Wuckert Jr. on Calvin Ayre as BSV's most significant player", "url": "https://bitcoin-takeover.com/audio/media/2026-08-23_s17_e39_kurt_wuckert_jr._on_bsv_big_block_bitcoin.mp3", "t": 5354, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135410/https://bitcoin-takeover.com/s17-e39-kurt-wuckert-jr-on-the-big-block-wars-bsv-craig-wright-the-road-not-taken/", "archive_date": "20261113135410", "archive_how": "saved"}, "ep-s17e39-nchain": {"kind": "episode", "title": "S17 E39: Kurt Wuckert Jr. on Calvin's investment and nChain's headcount", "url": "https://bitcoin-takeover.com/audio/media/2026-08-23_s17_e39_kurt_wuckert_jr._on_bsv_big_block_bitcoin.mp3", "t": 5456, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135410/https://bitcoin-takeover.com/s17-e39-kurt-wuckert-jr-on-the-big-block-wars-bsv-craig-wright-the-road-not-taken/", "archive_date": "20261113135410", "archive_how": "saved"}, "ep-s17e26-ayre": {"kind": "episode", "title": "S17 E26: Steve Thurmond on Calvin Ayre's financial backing of Craig Wright", "url": "https://bitcoin-takeover.com/audio/media/2026-05-27_s17_e26_steve_thurmond_calin_culianu_the_phenomenal_big_blockers_master.mp3", "t": 3216, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824035024/https://bitcoin-takeover.com/audio/media/2026-05-27_s17_e26_steve_thurmond_calin_culianu_the_phenomenal_big_blockers_master.mp3", "archive_date": "20260824035024", "archive_how": "existing"}, "wp-btcc": {"kind": "secondary", "title": "Wikipedia, “BTCC (cryptocurrency exchange)”", "url": "https://en.wikipedia.org/wiki/BTCC_(company)", "archive_url": "https://web.archive.org/web/20260909055028/https://en.wikipedia.org/wiki/BTCC_(company)", "archive_date": "20260909055028", "archive_how": "existing"}, "ep-s15e34-bobby": {"kind": "episode", "title": "S15 E34: Charlie Lee on a Consensus panel with “my brother Bobby”", "url": "https://bitcoin-takeover.com/audio/media/2024-04-29_s15_e34_charlie_lee_on_privacy_mweb_mimble_wimble_extension_block_-_26.04.2024_23.52.mp3", "t": 4667, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824032205/https://bitcoin-takeover.com/audio/media/2024-04-29_s15_e34_charlie_lee_on_privacy_mweb_mimble_wimble_extension_block_-_26.04.2024_23.52.mp3", "archive_date": "20260824032205", "archive_how": "existing"}, "ep-s15e34-ballet": {"kind": "episode", "title": "S15 E34: Charlie Lee on Ballet wallets", "url": "https://bitcoin-takeover.com/audio/media/2024-04-29_s15_e34_charlie_lee_on_privacy_mweb_mimble_wimble_extension_block_-_26.04.2024_23.52.mp3", "t": 3175, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824032205/https://bitcoin-takeover.com/audio/media/2024-04-29_s15_e34_charlie_lee_on_privacy_mweb_mimble_wimble_extension_block_-_26.04.2024_23.52.mp3", "archive_date": "20260824032205", "archive_how": "existing"}, "farside-book": {"kind": "primary", "title": "Jonathan Bier, “Book Published: The Blocksize War”, Farside Investors / BitMEX Research, 15 Mar 2021", "url": "https://farside.co.uk/the-blocksize-war/", "archive_url": "https://web.archive.org/web/20261113142025/https://farside.co.uk/the-blocksize-war/", "archive_date": "20261113142025", "archive_how": "saved"}, "ep-s16e60-intro": {"kind": "episode", "title": "S16 E60: Jonathan Bier — introduction", "url": "https://bitcoin-takeover.com/audio/media/2025-11-24_s16_e60_jonathan_bier_on_bitcoin_civil_wars_bitmex_research.mp3", "t": 46, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113152918/https://bitcoin-takeover.com/episodes/s16-e60-jonathan-bier-on-bitcoin-civil-wars-bitmex-research/", "archive_date": "20261113152918", "archive_how": "saved", "archive_of": "episode page"}, "ep-s16e60-bitmex": {"kind": "episode", "title": "S16 E60: Jonathan Bier on how BitMEX Research started", "url": "https://bitcoin-takeover.com/audio/media/2025-11-24_s16_e60_jonathan_bier_on_bitcoin_civil_wars_bitmex_research.mp3", "t": 234, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113152918/https://bitcoin-takeover.com/episodes/s16-e60-jonathan-bier-on-bitcoin-civil-wars-bitmex-research/", "archive_date": "20261113152918", "archive_how": "saved", "archive_of": "episode page"}, "ep-s16e60-reckless": {"kind": "episode", "title": "S16 E60: Jonathan Bier on his book Reckless", "url": "https://bitcoin-takeover.com/audio/media/2025-11-24_s16_e60_jonathan_bier_on_bitcoin_civil_wars_bitmex_research.mp3", "t": 1034, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113152918/https://bitcoin-takeover.com/episodes/s16-e60-jonathan-bier-on-bitcoin-civil-wars-bitmex-research/", "archive_date": "20261113152918", "archive_how": "saved", "archive_of": "episode page"}, "ep-s16e60-rizun": {"kind": "episode", "title": "S16 E60: Jonathan Bier on replying to Peter Rizun in Hong Kong", "url": "https://bitcoin-takeover.com/audio/media/2025-11-24_s16_e60_jonathan_bier_on_bitcoin_civil_wars_bitmex_research.mp3", "t": 3536, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113152918/https://bitcoin-takeover.com/episodes/s16-e60-jonathan-bier-on-bitcoin-civil-wars-bitmex-research/", "archive_date": "20261113152918", "archive_how": "saved", "archive_of": "episode page"}, "bw-overflow": {"kind": "secondary", "title": "Bitcoin Wiki, “Value overflow incident” (revision 61347)", "url": "https://en.bitcoin.it/wiki/Value_overflow_incident", "archive_url": "https://web.archive.org/web/20261105155911/https://en.bitcoin.it/wiki/Value_overflow_incident", "archive_date": "20261105155911", "archive_how": "existing"}, "btt-822": {"kind": "primary", "title": "“Strange block 74638”, Bitcointalk topic 822, 15 Aug 2010", "url": "https://bitcointalk.org/index.php?topic=822.0", "archive_url": "https://web.archive.org/web/20261101081729/https://bitcointalk.org/index.php?topic=822.0", "archive_date": "20261101081729", "archive_how": "existing"}, "btt-823": {"kind": "primary", "title": "“overflow bug SERIOUS”, Bitcointalk topic 823, 15 Aug 2010 (edited by satoshi with the 0.3.10 patch link)", "url": "https://bitcointalk.org/index.php?topic=823.0", "archive_url": "https://web.archive.org/web/20261017191948/https://bitcointalk.org/index.php?topic=823.0", "archive_date": "20261017191948", "archive_how": "existing"}, "btc-74691": {"kind": "primary", "title": "mempool.space, Bitcoin block 74,691 (header time 2010-08-16 08:20:08 UTC)", "url": "https://mempool.space/block/74691", "archive_url": "https://web.archive.org/web/20261113151424/https://mempool.space/block/74691", "archive_date": "20261113151424", "archive_how": "saved"}, "bip50": {"kind": "primary", "title": "BIP-50 (March 2013 Chain Fork Post-Mortem), Gavin Andresen", "url": "https://github.com/bitcoin/bips/blob/master/bip-0050.mediawiki", "archive_url": "https://web.archive.org/web/20261104193113/https://github.com/bitcoin/bips/blob/master/bip-0050.mediawiki", "archive_date": "20261104193113", "archive_how": "existing"}, "alert-2013": {"kind": "primary", "title": "bitcoin.org, “11/12 March 2013 Chain Fork Information” network alert", "url": "https://bitcoin.org/en/alert/2013-03-11-chain-fork", "archive_url": "https://web.archive.org/web/20260710072948/https://bitcoin.org/en/alert/2013-03-11-chain-fork", "archive_date": "20260710072948", "archive_how": "existing"}, "btc-225430": {"kind": "primary", "title": "mempool.space, Bitcoin block 225,430 (header time 2013-03-11 23:24:19 UTC)", "url": "https://mempool.space/block/225430", "archive_url": "https://web.archive.org/web/20261002183526/https://mempool.space/block/225430", "archive_date": "20261002183526", "archive_how": "existing"}, "core-0211": {"kind": "primary", "title": "Bitcoin Core 0.21.1 release notes (Taproot activation parameters)", "url": "https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-0.21.1.md", "archive_url": "https://web.archive.org/web/20261030031516/https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-0.21.1.md", "archive_date": "20261030031516", "archive_how": "existing"}, "optech-taproot": {"kind": "secondary", "title": "Bitcoin Optech, “Taproot” topic page", "url": "https://bitcoinops.org/en/topics/taproot/", "archive_url": "https://web.archive.org/web/20261031205616/https://bitcoinops.org/en/topics/taproot/", "archive_date": "20261031205616", "archive_how": "existing"}, "ep-s15e50-taproot": {"kind": "episode", "title": "S15 E50: Murch on Taproot and inscriptions", "url": "https://bitcoin-takeover.com/audio/media/2024-08-16_s15_e50__murch_on_bitcoin_popular_myths.mp3", "t": 3236, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260829161201/https://bitcoin-takeover.com/audio/media/2024-08-16_s15_e50__murch_on_bitcoin_popular_myths.mp3", "archive_date": "20260829161201", "archive_how": "existing"}, "ep-s15e50-ordinals": {"kind": "episode", "title": "S15 E50: Murch on “Taproot caused ordinals”", "url": "https://bitcoin-takeover.com/audio/media/2024-08-16_s15_e50__murch_on_bitcoin_popular_myths.mp3", "t": 3285, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260829161201/https://bitcoin-takeover.com/audio/media/2024-08-16_s15_e50__murch_on_bitcoin_popular_myths.mp3", "archive_date": "20260829161201", "archive_how": "existing"}, "cashtokens-chip": {"kind": "primary", "title": "CHIP-2022-02-CashTokens: Token Primitives for Bitcoin Cash, Jason Dreyzehner (v2.2.2, final)", "url": "https://github.com/cashtokens/cashtokens", "archive_url": "https://web.archive.org/web/20260417130358/https://github.com/cashtokens/cashtokens", "archive_date": "20260417130358", "archive_how": "existing"}, "bch-2023-upgrade": {"kind": "primary", "title": "Bitcoin Cash Node, “2023-05-15 Network Upgrade Specification”", "url": "https://upgradespecs.bitcoincashnode.org/2023-05-15-upgrade/", "archive_url": "https://web.archive.org/web/20260220164528/https://upgradespecs.bitcoincashnode.org/2023-05-15-upgrade/", "archive_date": "20260220164528", "archive_how": "existing"}, "ep-s17e19-cashtokens": {"kind": "episode", "title": "S17 E19: Amaury Séchet on CashTokens and ERC-20", "url": "https://bitcoin-takeover.com/audio/media/2026-04-18_s17_e19_deadalnix_amaury_sechet_on_forking_bitcoin_ecash.mp3", "t": 9936, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153144/https://bitcoin-takeover.com/s17-e19-amaury-sechet-on-forking-bitcoin-twice-quantum-fud-scars-from-the-block-size-wars/", "archive_date": "20261113153144", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e19-buidea": {"kind": "episode", "title": "S17 E19: Amaury Séchet on CashTokens as Bitcoin Unlimited's idea", "url": "https://bitcoin-takeover.com/audio/media/2026-04-18_s17_e19_deadalnix_amaury_sechet_on_forking_bitcoin_ecash.mp3", "t": 8837, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153144/https://bitcoin-takeover.com/s17-e19-amaury-sechet-on-forking-bitcoin-twice-quantum-fud-scars-from-the-block-size-wars/", "archive_date": "20261113153144", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e26-cashtokens": {"kind": "episode", "title": "S17 E26: FiendishCrypto on CashTokens as a 2023 turning point", "url": "https://bitcoin-takeover.com/audio/media/2026-05-27_s17_e26_steve_thurmond_calin_culianu_the_phenomenal_big_blockers_master.mp3", "t": 11001, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824035024/https://bitcoin-takeover.com/audio/media/2026-05-27_s17_e26_steve_thurmond_calin_culianu_the_phenomenal_big_blockers_master.mp3", "archive_date": "20260824035024", "archive_how": "existing"}, "avalanche-paper": {"kind": "primary", "title": "Team Rocket, Yin, Sekniqi, van Renesse, Sirer, “Scalable and Probabilistic Leaderless BFT Consensus through Metastability”, arXiv:1906.08936", "url": "https://arxiv.org/abs/1906.08936", "archive_url": "https://web.archive.org/web/20261101023842/https://arxiv.org/abs/1906.08936", "archive_date": "20261101023842", "archive_how": "existing"}, "ep-s17e19-aval": {"kind": "episode", "title": "S17 E19: Amaury Séchet on Avalanche on top of Nakamoto consensus", "url": "https://bitcoin-takeover.com/audio/media/2026-04-18_s17_e19_deadalnix_amaury_sechet_on_forking_bitcoin_ecash.mp3", "t": 2777, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153144/https://bitcoin-takeover.com/s17-e19-amaury-sechet-on-forking-bitcoin-twice-quantum-fud-scars-from-the-block-size-wars/", "archive_date": "20261113153144", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e19-avalwhy": {"kind": "episode", "title": "S17 E19: Amaury Séchet on why Avalanche", "url": "https://bitcoin-takeover.com/audio/media/2026-04-18_s17_e19_deadalnix_amaury_sechet_on_forking_bitcoin_ecash.mp3", "t": 9682, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153144/https://bitcoin-takeover.com/s17-e19-amaury-sechet-on-forking-bitcoin-twice-quantum-fud-scars-from-the-block-size-wars/", "archive_date": "20261113153144", "archive_how": "saved", "archive_of": "episode page"}, "wp-chunwang": {"kind": "secondary", "title": "Wikipedia, “Chun Wang” (F2Pool co-founder)", "url": "https://en.wikipedia.org/wiki/Chun_Wang", "archive_url": "https://web.archive.org/web/20260522184001/https://en.wikipedia.org/wiki/Chun_Wang", "archive_date": "20260522184001", "archive_how": "existing"}, "viabtc-blog": {"kind": "primary", "title": "ViaBTC, “Interview with ViaBTC CEO: Reflections on Eight Years of Entrepreneurship”, 7 Jun 2024", "url": "https://www.viabtc.com/en/blog/328?category=0", "archive_url": "https://web.archive.org/web/20260108085520/https://www.viabtc.com/en/blog/328?category=0", "archive_date": "20260108085520", "archive_how": "existing"}, "wp-bitcoincom": {"kind": "secondary", "title": "Wikipedia, “Bitcoin.com”", "url": "https://en.wikipedia.org/wiki/Bitcoin.com", "archive_url": "https://web.archive.org/web/20261027214113/https://en.wikipedia.org/wiki/Bitcoin.com", "archive_date": "20261027214113", "archive_how": "existing"}, "ep-s15e26-owner": {"kind": "episode", "title": "S15 E26: Roger Ver on owning Bitcoin.com", "url": "https://bitcoin-takeover.com/audio/media/2024-03-28_s15_e26_roger_ver_on_bitcoin.mp3", "t": 164, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113151839/https://bitcoin-takeover.com/s15-e26-roger-ver-on-hijacking-bitcoin-freedom-maximalism/", "archive_date": "20261113151839", "archive_how": "saved", "archive_of": "episode page"}, "ep-s15e26-focus": {"kind": "episode", "title": "S15 E26: Roger Ver on Bitcoin.com stopping its focus on Bitcoin", "url": "https://bitcoin-takeover.com/audio/media/2024-03-28_s15_e26_roger_ver_on_bitcoin.mp3", "t": 3916, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113151839/https://bitcoin-takeover.com/s15-e26-roger-ver-on-hijacking-bitcoin-freedom-maximalism/", "archive_date": "20261113151839", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e26-nchain": {"kind": "episode", "title": "S17 E26: Calin Culianu on nChain leaving Bitcoin Cash", "url": "https://bitcoin-takeover.com/audio/media/2026-05-27_s17_e26_steve_thurmond_calin_culianu_the_phenomenal_big_blockers_master.mp3", "t": 24930, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824035024/https://bitcoin-takeover.com/audio/media/2026-05-27_s17_e26_steve_thurmond_calin_culianu_the_phenomenal_big_blockers_master.mp3", "archive_date": "20260824035024", "archive_how": "existing"}, "ep-s16e56-knots": {"kind": "episode", "title": "S16 E56: Super Testnet on Knots nodes and bandwidth", "url": "https://bitcoin-takeover.com/audio/media/2025-11-08_s16_e56_super_testnet_on_papa_swaps_bip_444_prediction_markets.mp3", "t": 2204, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824052552/https://bitcoin-takeover.com/audio/media/2025-11-08_s16_e56_super_testnet_on_papa_swaps_bip_444_prediction_markets.mp3", "archive_date": "20260824052552", "archive_how": "existing"}, "bth-readme": {"kind": "primary", "title": "Bitcoin Hot README, GitHub BitcoinHot/Bitcoinhot-EOL (fork at block 498848)", "url": "https://github.com/BitcoinHot/Bitcoinhot-EOL", "archive_url": "https://web.archive.org/web/20250823183247/https://github.com/BitcoinHot/Bitcoinhot-EOL", "archive_date": "20250823183247", "archive_how": "existing"}, "bth-review": {"kind": "secondary", "title": "“My list of 43(+3) reviewed Bitcoin forks”, Bitcointalk topic 2777849 (last update 26 Feb 2019)", "url": "https://bitcointalk.org/index.php?topic=2777849.0", "archive_url": "https://web.archive.org/web/20250822111657/https://bitcointalk.org/index.php?topic=2777849.0", "archive_date": "20250822111657", "archive_how": "existing"}, "bth-ws": {"kind": "secondary", "title": "Walleting.Services claiming thread, Bitcointalk topic 2434261, page 20 (June 2018 posts on BTH)", "url": "https://bitcointalk.org/index.php?topic=2434261.380", "archive_url": "https://web.archive.org/web/20261113140947/https://bitcointalk.org/index.php?topic=2434261.380", "archive_date": "20261113140947", "archive_how": "saved"}, "btc-498848": {"kind": "primary", "title": "mempool.space, Bitcoin block 498,848 (header time 2017-12-12 04:44:12 UTC)", "url": "https://mempool.space/block/498848", "archive_url": "https://web.archive.org/web/20261113144151/https://mempool.space/block/498848", "archive_date": "20261113144151", "archive_how": "saved"}, "bpa-ann": {"kind": "primary", "title": "“[ANN][BPA] Bitcoin Pizza - 1st daglized Bitcoin, Fork 1:1, then 1:1,000,000,000”, Bitcointalk topic 2572775 (opened 12 Dec 2017)", "url": "https://bitcointalk.org/index.php?topic=2572775.0", "archive_url": "https://web.archive.org/web/20230207161153/https://bitcointalk.org/index.php?topic=2572775.0", "archive_date": "20230207161153", "archive_how": "existing"}, "bpa-readme": {"kind": "primary", "title": "Bitcoin Pizza README, GitHub DAGBPA/bitcoin-pizza", "url": "https://github.com/DAGBPA/bitcoin-pizza", "archive_url": "https://web.archive.org/web/20221221095051/https://github.com/DAGBPA/bitcoin-pizza", "archive_date": "20221221095051", "archive_how": "existing"}, "btc-501888": {"kind": "primary", "title": "mempool.space, Bitcoin block 501,888 (header time 2017-12-31 12:32:38 UTC)", "url": "https://mempool.space/block/501888", "archive_url": "https://web.archive.org/web/20261113145012/https://mempool.space/block/501888", "archive_date": "20261113145012", "archive_how": "saved"}, "xrc-faq": {"kind": "primary", "title": "r/BitcoinRhodium, “Bitcoin Rhodium FAQ” (Reddit post by u/BitcoinRh, 23 Oct 2019)", "url": "https://www.reddit.com/r/BitcoinRhodium/comments/dlz9dd/bitcoin_rhodium_faq/", "archive_url": "https://web.archive.org/web/20230612061407/https://www.reddit.com/r/BitcoinRhodium/comments/dlz9dd/bitcoin_rhodium_faq/", "archive_date": "20230612061407", "archive_how": "existing"}, "xrc-medium": {"kind": "primary", "title": "xRhodium, “xRhodium FAQ”, Medium, 23 Oct 2019", "url": "https://medium.com/xrhodium/faq-97cff95898cf", "archive_url": "https://web.archive.org/web/20251010035519/https://medium.com/xrhodium/faq-97cff95898cf", "archive_date": "20251010035519", "archive_how": "existing"}, "bzx-ann": {"kind": "primary", "title": "“[ANN] Bitcoin Zero- The Privacy Standard”, Bitcointalk topic 4973001 (opened 28 Aug 2018 by BitcoinZeroX)", "url": "https://bitcointalk.org/index.php?topic=4973001.0", "archive_url": "https://web.archive.org/web/20251207230942/https://bitcointalk.org/index.php?topic=4973001.0", "archive_date": "20251207230942", "archive_how": "existing"}, "bzx-readme-2018": {"kind": "primary", "title": "Bitcoinzero [BZX] Core 2018 README, GitHub bzxcoin/bitcoinzero", "url": "https://github.com/bzxcoin/bitcoinzero", "archive_url": "https://web.archive.org/web/20201106102137/https://github.com/bzxcoin/bitcoinzero", "archive_date": "20201106102137", "archive_how": "existing"}, "bzx-readme": {"kind": "primary", "title": "Bitcoinzero [BZX] (Lelantus) Core 2024 README, GitHub SpecialCoins/BitcoinZero", "url": "https://github.com/SpecialCoins/BitcoinZero", "archive_url": "https://web.archive.org/web/20250907115056/https://github.com/SpecialCoins/BitcoinZero", "archive_date": "20250907115056", "archive_how": "existing"}, "btch-ann": {"kind": "primary", "title": "clamoring, “[ANN] BTCH R&D Privacy Cryptocurrency - KMD Asset Chain - Merged Airdrop”, Bitcointalk topic 2827088 (26 Jan 2018)", "url": "https://bitcointalk.org/index.php?topic=2827088.0", "archive_url": "https://web.archive.org/web/20260411233239/https://bitcointalk.org/index.php?topic=2827088.0", "archive_date": "20260411233239", "archive_how": "existing"}, "btch-gh": {"kind": "primary", "title": "Bitcoin Hush, bitcoinhush.github.io README (“BTCH, The Immaculate Merge Drop”)", "url": "https://github.com/bitcoinhush/bitcoinhush.github.io", "archive_url": "https://web.archive.org/web/20250828163449/https://github.com/bitcoinhush/bitcoinhush.github.io", "archive_date": "20250828163449", "archive_how": "existing"}, "dgb-readme": {"kind": "primary", "title": "DigiByte Core README, GitHub DigiByte-Core/digibyte", "url": "https://github.com/DigiByte-Core/digibyte", "archive_url": "https://web.archive.org/web/20260421015301/https://github.com/DigiByte-Core/digibyte", "archive_date": "20260421015301", "archive_how": "existing"}, "dgb-chainparams": {"kind": "primary", "title": "DigiByte src/kernel/chainparams.cpp (genesis timestamp text)", "url": "https://github.com/DigiByte-Core/digibyte/blob/develop/src/kernel/chainparams.cpp", "archive_url": "https://web.archive.org/web/20261113142252/https://github.com/DigiByte-Core/digibyte/blob/develop/src/kernel/chainparams.cpp", "archive_date": "20261113142252", "archive_how": "saved"}, "grs-readme": {"kind": "primary", "title": "Groestlcoin Core README, GitHub Groestlcoin/groestlcoin", "url": "https://github.com/Groestlcoin/groestlcoin", "archive_url": "https://web.archive.org/web/20260115023410/https://github.com/GroestlCoin/groestlcoin", "archive_date": "20260115023410", "archive_how": "existing"}, "grs-chainparams": {"kind": "primary", "title": "Groestlcoin src/kernel/chainparams.cpp (genesis 1395342829 = 2014-03-20 19:13:49 UTC)", "url": "https://github.com/Groestlcoin/groestlcoin/blob/master/src/kernel/chainparams.cpp", "archive_url": "https://web.archive.org/web/20261113142407/https://github.com/Groestlcoin/groestlcoin/blob/master/src/kernel/chainparams.cpp", "archive_date": "20261113142407", "archive_how": "saved"}, "grs-ann": {"kind": "primary", "title": "gruve_p, “[ANN][GRS] Groestlcoin | 1st to activate Segwit & Taproot”, Bitcointalk topic 525926 (22 Mar 2014)", "url": "https://bitcointalk.org/index.php?topic=525926.0", "archive_url": "https://web.archive.org/web/20260810050834/https://bitcointalk.org/index.php?topic=525926.0", "archive_date": "20260810050834", "archive_how": "existing"}, "sys-readme": {"kind": "primary", "title": "Syscoin Core README, GitHub syscoin/syscoin", "url": "https://github.com/syscoin/syscoin", "archive_url": "https://web.archive.org/web/20260416024138/https://github.com/syscoin/syscoin", "archive_date": "20260416024138", "archive_how": "existing"}, "sys-chainparams": {"kind": "primary", "title": "Syscoin src/kernel/chainparams.cpp (nAuxpowChainId 16; mainnet genesis 1559520000 = 2019-06-03 UTC)", "url": "https://github.com/syscoin/syscoin/blob/master/src/kernel/chainparams.cpp", "archive_url": "https://web.archive.org/web/20261113143614/https://github.com/syscoin/syscoin/blob/master/src/kernel/chainparams.cpp", "archive_date": "20261113143614", "archive_how": "saved"}, "tbx-ann": {"kind": "primary", "title": "Lolcust, “[ANNOUNCE] Tenebrix, a CPU-friendly, GPU-hostile cryptocurrency”, Bitcointalk topic 45667 (26 Sep 2011)", "url": "https://bitcointalk.org/index.php?topic=45667.0", "archive_url": "https://web.archive.org/web/20261013023304/https://bitcointalk.org/index.php?topic=45667.0", "archive_date": "20261013023304", "archive_how": "existing"}, "fbx-ann": {"kind": "primary", "title": "michaelmclees, “FAIRBRIX - Announcement - CPU friendly - GPU hostile - Tiny premine”, Bitcointalk topic 46478 (1 Oct 2011)", "url": "https://bitcointalk.org/index.php?topic=46478.0", "archive_url": "https://web.archive.org/web/20250402010749/https://bitcointalk.org/index.php?topic=46478.0", "archive_date": "20250402010749", "archive_how": "existing"}, "fbx-relaunch": {"kind": "primary", "title": "coblee, “[Announce] Fairbrix relaunched!”, Bitcointalk topic 46528 (2 Oct 2011)", "url": "https://bitcointalk.org/index.php?topic=46528.0", "archive_url": "https://web.archive.org/web/20260804085431/https://bitcointalk.org/index.php?topic=46528.0", "archive_date": "20260804085431", "archive_how": "existing"}, "bw-scrypt": {"kind": "secondary", "title": "Bitcoin Wiki (en.bitcoin.it), “Scrypt proof of work” (Tenebrix redirects here)", "url": "https://en.bitcoin.it/wiki/Scrypt_proof_of_work", "archive_url": "https://web.archive.org/web/20261016163725/https://en.bitcoin.it/wiki/Scrypt_proof_of_work", "archive_date": "20261016163725", "archive_how": "existing"}, "ltcwiki-history": {"kind": "secondary", "title": "Litecoin Wiki, “History of cryptocurrency” (Wayback Machine copy, 11 Jun 2016)", "url": "https://web.archive.org/web/20160611133738/litecoin.info/History_of_cryptocurrency", "archive_url": "https://web.archive.org/web/20160611133738/litecoin.info/History_of_cryptocurrency", "archive_date": "20160611133738", "archive_how": "already-wayback"}, "ixc-ann": {"kind": "primary", "title": "Nasakioto, “[ANNOUNCE] Ixcoin - a new Bitcoin fork”, Bitcointalk topic 36218 (10 Aug 2011, PGP-signed)", "url": "https://bitcointalk.org/index.php?topic=36218.0", "archive_url": "https://web.archive.org/web/20260609203112/https://bitcointalk.org/index.php?topic=36218.0", "archive_date": "20260609203112", "archive_how": "existing"}, "i0c-thread": {"kind": "primary", "title": "BitcoinBug, “New Ixcoin fork -> I0coin”, Bitcointalk topic 36425 (11 Aug 2011)", "url": "https://bitcointalk.org/index.php?topic=36425.0", "archive_url": "https://web.archive.org/web/20260325041010/https://bitcointalk.org/index.php?topic=36425.0", "archive_date": "20260325041010", "archive_how": "existing"}, "ixc-readme": {"kind": "primary", "title": "IXCoin Core README, GitHub IXCore/IXCoin", "url": "https://github.com/IXCore/IXCoin", "archive_url": "https://web.archive.org/web/20260307000915/https://github.com/ixcore/ixcoin", "archive_date": "20260307000915", "archive_how": "existing"}, "slc-ann": {"kind": "primary", "title": "CoinHunter, “[ANNOUNCE] SolidCoin - new and improved block chain. Secure from pools”, Bitcointalk topic 38453 (21 Aug 2011)", "url": "https://bitcointalk.org/index.php?topic=38453.0", "archive_url": "https://web.archive.org/web/20261013023304/https://bitcointalk.org/index.php?topic=38453.0", "archive_date": "20261013023304", "archive_how": "existing"}, "slc-v2": {"kind": "primary", "title": "CoinHunter, “SolidCoin v2.0 features new hashing algorithm, faster on CPUs”, Bitcointalk topic 44423 (17 Sep 2011)", "url": "https://bitcointalk.org/index.php?topic=44423.0", "archive_url": "https://web.archive.org/web/20200626004355/https://bitcointalk.org/index.php?topic=44423.0", "archive_date": "20200626004355", "archive_how": "existing"}, "slc-gpu": {"kind": "primary", "title": "CoinHunter, “SolidCoin 2 - GPU mining and the future”, Bitcointalk topic 49219 (21 Oct 2011)", "url": "https://bitcointalk.org/index.php?topic=49219.0", "archive_url": "https://web.archive.org/web/20210509231742/https://bitcointalk.org/index.php?topic=49219.0", "archive_date": "20210509231742", "archive_how": "existing"}, "wp-etc": {"kind": "secondary", "title": "Wikipedia, “Ethereum Classic”", "url": "https://en.wikipedia.org/wiki/Ethereum_Classic", "archive_url": "https://web.archive.org/web/20261022101522/https://en.wikipedia.org/wiki/Ethereum_Classic", "archive_date": "20261022101522", "archive_how": "existing"}, "wp-dao": {"kind": "secondary", "title": "Wikipedia, “The DAO”", "url": "https://en.wikipedia.org/wiki/The_DAO", "archive_url": "https://web.archive.org/web/20261031122718/https://en.wikipedia.org/wiki/The_DAO", "archive_date": "20261031122718", "archive_how": "existing"}, "ep-s17e42-intro": {"kind": "episode", "title": "S17 E42: Vlad on the DAO split and “code is law”", "url": "https://bitcoin-takeover.com/audio/media/2026-09-12_s17_e42_bob_summerwill_on_ethereum_classic_bitcoin_forks_-_12_09_2026_05.24.mp3", "t": 140, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135521/https://bitcoin-takeover.com/s17-e42-bob-summerwill-on-ethereum-classic-bitcoins-fork-season/", "archive_date": "20261113135521", "archive_how": "saved"}, "ep-s17e42-schism": {"kind": "episode", "title": "S17 E42: Bob Summerwill on the DAO schism and immutability", "url": "https://bitcoin-takeover.com/audio/media/2026-09-12_s17_e42_bob_summerwill_on_ethereum_classic_bitcoin_forks_-_12_09_2026_05.24.mp3", "t": 968, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135521/https://bitcoin-takeover.com/s17-e42-bob-summerwill-on-ethereum-classic-bitcoins-fork-season/", "archive_date": "20261113135521", "archive_how": "saved"}, "ep-s17e42-irregular": {"kind": "episode", "title": "S17 E42: Bob Summerwill — the fork was an irregular state transition", "url": "https://bitcoin-takeover.com/audio/media/2026-09-12_s17_e42_bob_summerwill_on_ethereum_classic_bitcoin_forks_-_12_09_2026_05.24.mp3", "t": 1608, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135521/https://bitcoin-takeover.com/s17-e42-bob-summerwill-on-ethereum-classic-bitcoins-fork-season/", "archive_date": "20261113135521", "archive_how": "saved"}, "ep-s17e42-silbert": {"kind": "episode", "title": "S17 E42: Bob Summerwill on Barry Silbert, Grayscale and the ETC Cooperative", "url": "https://bitcoin-takeover.com/audio/media/2026-09-12_s17_e42_bob_summerwill_on_ethereum_classic_bitcoin_forks_-_12_09_2026_05.24.mp3", "t": 2623, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135521/https://bitcoin-takeover.com/s17-e42-bob-summerwill-on-ethereum-classic-bitcoins-fork-season/", "archive_date": "20261113135521", "archive_how": "saved"}, "ep-s17e42-ethos": {"kind": "episode", "title": "S17 E42: Bob Summerwill — “Bitcoin philosophy, Ethereum technology”", "url": "https://bitcoin-takeover.com/audio/media/2026-09-12_s17_e42_bob_summerwill_on_ethereum_classic_bitcoin_forks_-_12_09_2026_05.24.mp3", "t": 2768, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135521/https://bitcoin-takeover.com/s17-e42-bob-summerwill-on-ethereum-classic-bitcoins-fork-season/", "archive_date": "20261113135521", "archive_how": "saved"}, "ep-s17e42-ethpow": {"kind": "episode", "title": "S17 E42: Bob Summerwill on EthereumPoW and Chandler Guo", "url": "https://bitcoin-takeover.com/audio/media/2026-09-12_s17_e42_bob_summerwill_on_ethereum_classic_bitcoin_forks_-_12_09_2026_05.24.mp3", "t": 9376, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135521/https://bitcoin-takeover.com/s17-e42-bob-summerwill-on-ethereum-classic-bitcoins-fork-season/", "archive_date": "20261113135521", "archive_how": "saved"}, "ep-s17e42-lopp": {"kind": "episode", "title": "S17 E42: Bob Summerwill on Jameson Lopp at the Proof of Work Summit", "url": "https://bitcoin-takeover.com/audio/media/2026-09-12_s17_e42_bob_summerwill_on_ethereum_classic_bitcoin_forks_-_12_09_2026_05.24.mp3", "t": 12662, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135521/https://bitcoin-takeover.com/s17-e42-bob-summerwill-on-ethereum-classic-bitcoins-fork-season/", "archive_date": "20261113135521", "archive_how": "saved"}, "ep-s17e42-lombrozo": {"kind": "episode", "title": "S17 E42: Vlad on Eric Lombrozo in Early Days of Ethereum", "url": "https://bitcoin-takeover.com/audio/media/2026-09-12_s17_e42_bob_summerwill_on_ethereum_classic_bitcoin_forks_-_12_09_2026_05.24.mp3", "t": 13803, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135521/https://bitcoin-takeover.com/s17-e42-bob-summerwill-on-ethereum-classic-bitcoins-fork-season/", "archive_date": "20261113135521", "archive_how": "saved"}, "ep-s17e42-stfu": {"kind": "episode", "title": "S17 E42: Bob Summerwill on BIP-110 and data-carrying", "url": "https://bitcoin-takeover.com/audio/media/2026-09-12_s17_e42_bob_summerwill_on_ethereum_classic_bitcoin_forks_-_12_09_2026_05.24.mp3", "t": 3790, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135521/https://bitcoin-takeover.com/s17-e42-bob-summerwill-on-ethereum-classic-bitcoins-fork-season/", "archive_date": "20261113135521", "archive_how": "saved"}, "bips-list": {"kind": "primary", "title": "bitcoin/bips README (BIP index with authors)", "url": "https://github.com/bitcoin/bips/blob/master/README.mediawiki", "archive_url": "https://web.archive.org/web/20261108085924/https://github.com/bitcoin/bips/blob/master/README.mediawiki", "archive_date": "20261108085924", "archive_how": "existing"}, "lombrozo-gh": {"kind": "primary", "title": "GitHub profile CodeShark (Eric Lombrozo), account created 4 Jul 2011", "url": "https://github.com/CodeShark", "archive_url": "https://web.archive.org/web/20260622203427/https://github.com/CodeShark", "archive_date": "20260622203427", "archive_how": "existing"}, "ep-s17e19-lombrozo": {"kind": "episode", "title": "S17 E19: Vlad on Eric Lombrozo and 2016", "url": "https://bitcoin-takeover.com/audio/media/2026-04-18_s17_e19_deadalnix_amaury_sechet_on_forking_bitcoin_ecash.mp3", "t": 13869, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153144/https://bitcoin-takeover.com/s17-e19-amaury-sechet-on-forking-bitcoin-twice-quantum-fud-scars-from-the-block-size-wars/", "archive_date": "20261113153144", "archive_how": "saved", "archive_of": "episode page"}, "lopp-site": {"kind": "primary", "title": "Jameson Lopp, lopp.net (read 13 Nov 2026)", "url": "https://www.lopp.net/", "archive_url": "https://web.archive.org/web/20261113154457/https://www.lopp.net/", "archive_date": "20261113154457", "archive_how": "saved"}, "lopp-blog": {"kind": "primary", "title": "Cypherpunk Cogitations, “About this site” (Jameson Lopp’s publication)", "url": "https://blog.lopp.net/about/", "archive_url": "https://web.archive.org/web/20250620135916/https://blog.lopp.net/about/", "archive_date": "20250620135916", "archive_how": "existing"}, "lopp-gh": {"kind": "primary", "title": "GitHub profile jlopp (Jameson Lopp), company Casa", "url": "https://github.com/jlopp", "archive_url": "https://web.archive.org/web/20260825195104/https://github.com/jlopp", "archive_date": "20260825195104", "archive_how": "existing"}, "ep-s17e39-lopp": {"kind": "episode", "title": "S17 E39: Kurt Wuckert Jr. recalls Jameson Lopp on Craig Wright", "url": "https://bitcoin-takeover.com/audio/media/2026-08-23_s17_e39_kurt_wuckert_jr._on_bsv_big_block_bitcoin.mp3", "t": 9760, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135410/https://bitcoin-takeover.com/s17-e39-kurt-wuckert-jr-on-the-big-block-wars-bsv-craig-wright-the-road-not-taken/", "archive_date": "20261113135410", "archive_how": "saved"}, "ep-s17e13-opnext": {"kind": "episode", "title": "S17 E13: Charlie Spears on OP_NEXT and the OP_RETURN debate", "url": "https://bitcoin-takeover.com/audio/media/2026-03-17_s17_e13_charlie_spears_on_blockspace_bitcoin_culture_op_next.mp3", "t": 4984, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824021227/https://bitcoin-takeover.com/audio/media/2026-03-17_s17_e13_charlie_spears_on_blockspace_bitcoin_culture_op_next.mp3", "archive_date": "20260824021227", "archive_how": "existing"}, "ep-s17e39-intro": {"kind": "episode", "title": "S17 E39: Vlad introduces Kurt Wuckert Jr.", "url": "https://bitcoin-takeover.com/audio/media/2026-08-23_s17_e39_kurt_wuckert_jr._on_bsv_big_block_bitcoin.mp3", "t": 79, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135410/https://bitcoin-takeover.com/s17-e39-kurt-wuckert-jr-on-the-big-block-wars-bsv-craig-wright-the-road-not-taken/", "archive_date": "20261113135410", "archive_how": "saved"}, "ep-s17e39-oslo": {"kind": "episode", "title": "S17 E39: Kurt Wuckert Jr. on covering the Oslo Hodlonaut v Wright trial for CoinGeek", "url": "https://bitcoin-takeover.com/audio/media/2026-08-23_s17_e39_kurt_wuckert_jr._on_bsv_big_block_bitcoin.mp3", "t": 246, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135410/https://bitcoin-takeover.com/s17-e39-kurt-wuckert-jr-on-the-big-block-wars-bsv-craig-wright-the-road-not-taken/", "archive_date": "20261113135410", "archive_how": "saved"}, "ep-s17e39-coingeek": {"kind": "episode", "title": "S17 E39: Kurt Wuckert Jr. as CoinGeek journalist and GorillaPool operator", "url": "https://bitcoin-takeover.com/audio/media/2026-08-23_s17_e39_kurt_wuckert_jr._on_bsv_big_block_bitcoin.mp3", "t": 112, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135410/https://bitcoin-takeover.com/s17-e39-kurt-wuckert-jr-on-the-big-block-wars-bsv-craig-wright-the-road-not-taken/", "archive_date": "20261113135410", "archive_how": "saved"}, "ep-s17e39-chicago": {"kind": "episode", "title": "S17 E39: Kurt Wuckert Jr. on hosting the Bitcoin Cash meetup in Chicago", "url": "https://bitcoin-takeover.com/audio/media/2026-08-23_s17_e39_kurt_wuckert_jr._on_bsv_big_block_bitcoin.mp3", "t": 3860, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135410/https://bitcoin-takeover.com/s17-e39-kurt-wuckert-jr-on-the-big-block-wars-bsv-craig-wright-the-road-not-taken/", "archive_date": "20261113135410", "archive_how": "saved"}, "ep-s17e39-gorilla": {"kind": "episode", "title": "S17 E39: Kurt Wuckert Jr. on GorillaPool", "url": "https://bitcoin-takeover.com/audio/media/2026-08-23_s17_e39_kurt_wuckert_jr._on_bsv_big_block_bitcoin.mp3", "t": 5312, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135410/https://bitcoin-takeover.com/s17-e39-kurt-wuckert-jr-on-the-big-block-wars-bsv-craig-wright-the-road-not-taken/", "archive_date": "20261113135410", "archive_how": "saved"}, "rxc-site": {"kind": "primary", "title": "Ryan X. Charles, ryanxcharles.com (CV summary, read 13 Nov 2026)", "url": "https://ryanxcharles.com/", "archive_url": "https://web.archive.org/web/20260714213334/https://ryanxcharles.com/", "archive_date": "20260714213334", "archive_how": "existing"}, "rxc-gh": {"kind": "primary", "title": "GitHub profile ryanxcharles", "url": "https://github.com/ryanxcharles", "archive_url": "https://web.archive.org/web/20260608122703/https://github.com/ryanxcharles", "archive_date": "20260608122703", "archive_how": "existing"}, "ep-s17e39-rxc": {"kind": "episode", "title": "S17 E39: Kurt Wuckert Jr. on Ryan X. Charles after the hash war", "url": "https://bitcoin-takeover.com/audio/media/2026-08-23_s17_e39_kurt_wuckert_jr._on_bsv_big_block_bitcoin.mp3", "t": 4413, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135410/https://bitcoin-takeover.com/s17-e39-kurt-wuckert-jr-on-the-big-block-wars-bsv-craig-wright-the-road-not-taken/", "archive_date": "20261113135410", "archive_how": "saved"}, "ep-s17e39-rxc-sorry": {"kind": "episode", "title": "S17 E39: Vlad on Ryan X. Charles after the COPA trial", "url": "https://bitcoin-takeover.com/audio/media/2026-08-23_s17_e39_kurt_wuckert_jr._on_bsv_big_block_bitcoin.mp3", "t": 11577, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135410/https://bitcoin-takeover.com/s17-e39-kurt-wuckert-jr-on-the-big-block-wars-bsv-craig-wright-the-road-not-taken/", "archive_date": "20261113135410", "archive_how": "saved"}, "ep-s17e33-earthbucks": {"kind": "episode", "title": "S17 E33: Joël Valenzuela on Ryan X. Charles' EarthBucks", "url": "https://bitcoin-takeover.com/audio/media/2026-07-27_s17_e33_joel_valenzuela_on_private_digital_cash_living_without_banks_mono.mp3", "t": 12335, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824022744/https://bitcoin-takeover.com/audio/media/2026-07-27_s17_e33_joel_valenzuela_on_private_digital_cash_living_without_banks_mono.mp3", "archive_date": "20260824022744", "archive_how": "existing"}, "core-cve-17144": {"kind": "primary", "title": "Bitcoin Core, “Disclosure of CVE-2018-17144” (20 Sep 2018)", "url": "https://bitcoincore.org/en/2018/09/20/notice/", "archive_url": "https://web.archive.org/web/20261025122935/https://bitcoincore.org/en/2018/09/20/notice/", "archive_date": "20261025122935", "archive_how": "existing"}, "bw-cve-list": {"kind": "secondary", "title": "Bitcoin Wiki (en.bitcoin.it), “Common Vulnerabilities and Exposures”", "url": "https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures", "archive_url": "https://web.archive.org/web/20261020051842/https://en.bitcoin.it/wiki/Common_Vulnerabilities_and_Exposures", "archive_date": "20261020051842", "archive_how": "existing"}, "bw-bip91": {"kind": "secondary", "title": "Bitcoin Wiki mirror of BIP 91 (Created: 2017-05-22; Status: Final)", "url": "https://en.bitcoin.it/wiki/BIP_0091", "archive_url": "https://web.archive.org/web/20260608113751/https://en.bitcoin.it/wiki/BIP_0091", "archive_date": "20260608113751", "archive_how": "existing"}, "bch-nov2018": {"kind": "primary", "title": "Bitcoin Cash, “2018 November 15 Network Upgrade Specification” (activation 1542300000)", "url": "https://github.com/bitcoincashorg/bitcoincash.org/blob/master/spec/2018-nov-upgrade.md", "archive_url": "https://web.archive.org/web/20260828080511/https://github.com/bitcoincashorg/bitcoincash.org/blob/master/spec/2018-nov-upgrade.md", "archive_date": "20260828080511", "archive_how": "existing"}, "cds-spec": {"kind": "primary", "title": "Bitcoin Cash, OP_CHECKDATASIG and OP_CHECKDATASIGVERIFY specification", "url": "https://github.com/bitcoincashorg/bitcoincash.org/blob/master/spec/op_checkdatasig.md", "archive_url": "https://web.archive.org/web/20261009031713/https://github.com/bitcoincashorg/bitcoincash.org/blob/master/spec/op_checkdatasig.md", "archive_date": "20261009031713", "archive_how": "existing"}, "ep-s17e19-mag": {"kind": "episode", "title": "S17 E19: Vlad on the November 2018 Magnetic Anomaly fork", "url": "https://bitcoin-takeover.com/audio/media/2026-04-18_s17_e19_deadalnix_amaury_sechet_on_forking_bitcoin_ecash.mp3", "t": 6561, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153144/https://bitcoin-takeover.com/s17-e19-amaury-sechet-on-forking-bitcoin-twice-quantum-fud-scars-from-the-block-size-wars/", "archive_date": "20261113153144", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e19-cds": {"kind": "episode", "title": "S17 E19: Amaury Séchet explains OP_CHECKDATASIG and CTOR", "url": "https://bitcoin-takeover.com/audio/media/2026-04-18_s17_e19_deadalnix_amaury_sechet_on_forking_bitcoin_ecash.mp3", "t": 6577, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153144/https://bitcoin-takeover.com/s17-e19-amaury-sechet-on-forking-bitcoin-twice-quantum-fud-scars-from-the-block-size-wars/", "archive_date": "20261113153144", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e26-cds": {"kind": "episode", "title": "S17 E26: Rosco Kalis on CheckDataSig covenants", "url": "https://bitcoin-takeover.com/audio/media/2026-05-27_s17_e26_steve_thurmond_calin_culianu_the_phenomenal_big_blockers_master.mp3", "t": 21031, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824035024/https://bitcoin-takeover.com/audio/media/2026-05-27_s17_e26_steve_thurmond_calin_culianu_the_phenomenal_big_blockers_master.mp3", "archive_date": "20260824035024", "archive_how": "existing"}, "core-pr21377": {"kind": "primary", "title": "Bitcoin Core PR #21377, “Speedy trial support for versionbits” (ajtowns; opened 6 Mar 2021, merged 15 Apr 2021)", "url": "https://github.com/bitcoin/bitcoin/pull/21377", "archive_url": "https://web.archive.org/web/20260622103838/https://github.com/bitcoin/bitcoin/pull/21377", "archive_date": "20260622103838", "archive_how": "existing"}, "ep-s15e50-st": {"kind": "episode", "title": "S15 E50: Vlad on the Speedy Trial backlash", "url": "https://bitcoin-takeover.com/audio/media/2024-08-16_s15_e50__murch_on_bitcoin_popular_myths.mp3", "t": 2333, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260829161201/https://bitcoin-takeover.com/audio/media/2024-08-16_s15_e50__murch_on_bitcoin_popular_myths.mp3", "archive_date": "20260829161201", "archive_how": "existing"}, "core-relay-2025": {"kind": "primary", "title": "Bitcoin Core, “Bitcoin Core development and transaction relay policy” (6 Jun 2025)", "url": "https://bitcoincore.org/en/2025/06/06/relay-statement/", "archive_url": "https://web.archive.org/web/20260719003747/https://bitcoincore.org/en/2025/06/06/relay-statement/", "archive_date": "20260719003747", "archive_how": "existing"}, "core-pr32406": {"kind": "primary", "title": "Bitcoin Core PR #32406, “policy: uncap datacarrier by default” (instagibbs; opened 2 May 2025, merged 9 Jun 2025)", "url": "https://github.com/bitcoin/bitcoin/pull/32406", "archive_url": "https://web.archive.org/web/20261023073828/https://github.com/bitcoin/bitcoin/pull/32406", "archive_date": "20261023073828", "archive_how": "existing"}, "core-30": {"kind": "primary", "title": "Bitcoin Core 30.0 release notes (datacarriersize default 100,000; multiple OP_RETURN outputs)", "url": "https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-30.0.md", "archive_url": "https://web.archive.org/web/20261113142734/https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-30.0.md", "archive_date": "20261113142734", "archive_how": "saved"}, "ord-overview": {"kind": "primary", "title": "ord handbook, “Ordinal Theory Overview”", "url": "https://github.com/ordinals/ord/blob/master/docs/src/overview.md", "archive_url": "https://web.archive.org/web/20261113143519/https://github.com/ordinals/ord/blob/master/docs/src/overview.md", "archive_date": "20261113143519", "archive_how": "saved"}, "ord-inscriptions": {"kind": "primary", "title": "ord handbook, “Inscriptions”", "url": "https://github.com/ordinals/ord/blob/master/docs/src/inscriptions.md", "archive_url": "https://web.archive.org/web/20240704013024/https://github.com/ordinals/ord/blob/master/docs/src/inscriptions.md", "archive_date": "20240704013024", "archive_how": "existing"}, "ord-readme": {"kind": "primary", "title": "ord README, GitHub ordinals/ord", "url": "https://github.com/ordinals/ord", "archive_url": "https://web.archive.org/web/20260720111959/https://github.com/ordinals/ord/", "archive_date": "20260720111959", "archive_how": "existing"}, "ord-040": {"kind": "primary", "title": "ord release 0.4.0 (published 2023-01-20 18:45 UTC)", "url": "https://github.com/ordinals/ord/releases/tag/0.4.0", "archive_url": "https://web.archive.org/web/20261113143546/https://github.com/ordinals/ord/releases/tag/0.4.0", "archive_date": "20261113143546", "archive_how": "saved"}, "ep-s12e13-witness": {"kind": "episode", "title": "Casey Rodarmor on Ordinals (6 Feb 2023; transcript titled S13 E3, file s12_e13): inscriptions in the witness", "url": "https://bitcoin-takeover.com/audio/media/2023-02-06_s12_e13_casey_rodarmor_on_ordinals__inscriptions__bitcoin_culture.mp3", "t": 524, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824044058/https://bitcoin-takeover.com/audio/media/2023-02-06_s12_e13_casey_rodarmor_on_ordinals__inscriptions__bitcoin_culture.mp3", "archive_date": "20260824044058", "archive_how": "existing"}, "ep-s12e13-sats": {"kind": "episode", "title": "Casey Rodarmor on Ordinals (6 Feb 2023): Ordinals and inscriptions compared with Taro and RGB", "url": "https://bitcoin-takeover.com/audio/media/2023-02-06_s12_e13_casey_rodarmor_on_ordinals__inscriptions__bitcoin_culture.mp3", "t": 3012, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824044058/https://bitcoin-takeover.com/audio/media/2023-02-06_s12_e13_casey_rodarmor_on_ordinals__inscriptions__bitcoin_culture.mp3", "archive_date": "20260824044058", "archive_how": "existing"}, "coingeek-about": {"kind": "primary", "title": "CoinGeek, “About Us” (read 13 Nov 2026)", "url": "https://coingeek.com/about-us/", "archive_url": "https://web.archive.org/web/20261021161635/https://coingeek.com/about-us/", "archive_date": "20261021161635", "archive_how": "existing"}, "ep-s16e54-bitfury": {"kind": "episode", "title": "S16 E54: Ros on Bitfury as one of the biggest miners and ASIC makers", "url": "https://bitcoin-takeover.com/audio/media/2025-11-01_s16_e54_slava_zhygulin_ros_on_stroom_network_bitcoin_staking.mp3", "t": 558, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824045248/https://bitcoin-takeover.com/audio/media/2025-11-01_s16_e54_slava_zhygulin_ros_on_stroom_network_bitcoin_staking.mp3", "archive_date": "20260824045248", "archive_how": "existing"}, "btccom-site": {"kind": "primary", "title": "btc.com homepage, now “BTC.com Museum” (read 13 Nov 2026)", "url": "https://btc.com/", "archive_url": "https://web.archive.org/web/20261025065247/https://www.btc.com/", "archive_date": "20261025065247", "archive_how": "existing"}, "wp-roszak": {"kind": "secondary", "title": "Wikipedia, “Matthew Roszak” (Bloq co-founder and chairman)", "url": "https://en.wikipedia.org/wiki/Matthew_Roszak", "archive_url": "https://web.archive.org/web/20260416162717/https://en.wikipedia.org/wiki/Matthew_Roszak", "archive_date": "20260416162717", "archive_how": "existing"}, "bloq-site": {"kind": "primary", "title": "Bloq homepage (read 13 Nov 2026)", "url": "https://www.bloq.com/", "archive_url": "https://web.archive.org/web/20261021171640/https://bloq.com/", "archive_date": "20261021171640", "archive_how": "existing"}, "bpq-ann": {"kind": "primary", "title": "pq, “[ANN] Bitcoin Post-Quantum”, Bitcointalk topic 5082692 (10 Dec 2018)", "url": "https://bitcointalk.org/index.php?topic=5082692.0", "archive_url": "https://web.archive.org/web/20201112013702/https://bitcointalk.org/index.php?topic=5082692.0", "archive_date": "20201112013702", "archive_how": "existing"}, "bpq-site": {"kind": "primary", "title": "Bitcoin Post-Quantum website, bitcoinpq.github.io", "url": "https://bitcoinpq.github.io/", "archive_url": "https://web.archive.org/web/20260710111736/https://bitcoinpq.github.io/", "archive_date": "20260710111736", "archive_how": "existing"}, "obyte-ann": {"kind": "primary", "title": "tonych, “[ANN] Obyte: Totally new consensus algorithm + private untraceable payments”, Bitcointalk topic 1608859 (5 Sep 2016; current OP)", "url": "https://bitcointalk.org/index.php?topic=1608859.0", "archive_url": "https://web.archive.org/web/20260809200906/https://bitcointalk.org/index.php?topic=1608859.0", "archive_date": "20260809200906", "archive_how": "existing"}, "byteball-2016": {"kind": "primary", "title": "Byteball announcement text of 5 Sep 2016 as quoted in reply #18 (EpyxZ, 5 Sep 2016), Bitcointalk topic 1608859", "url": "https://bitcointalk.org/index.php?topic=1608859.0", "archive_url": "https://web.archive.org/web/20260809200906/https://bitcointalk.org/index.php?topic=1608859.0", "archive_date": "20260809200906", "archive_how": "existing"}, "clam-ann": {"kind": "primary", "title": "SuperClam, “[ANN][CLAM] CLAMs, Proof-Of-Chain, Proof-Of-Working-Stake, a.k.a. “Clamcoin””, Bitcointalk topic 623147 (24 May 2014)", "url": "https://bitcointalk.org/index.php?topic=623147.0", "archive_url": "https://web.archive.org/web/20260711203405/https://bitcointalk.org/index.php?topic=623147.0", "archive_date": "20260711203405", "archive_how": "existing"}, "clam-site": {"kind": "primary", "title": "clamcoin.org, “Introduction to Clams” (read 13 Nov 2026)", "url": "https://clamcoin.org/", "archive_url": "https://web.archive.org/web/20261113141950/https://clamcoin.org/", "archive_date": "20261113141950", "archive_how": "saved"}, "sec-heart-pr": {"kind": "primary", "title": "SEC press release 2023-143, “SEC Charges Hex Founder Richard Heart …”, 31 Jul 2023", "url": "https://www.sec.gov/newsroom/press-releases/2023-143", "archive_url": "https://web.archive.org/web/20261021050724/https://www.sec.gov/newsroom/press-releases/2023-143", "archive_date": "20261021050724", "archive_how": "existing"}, "sec-heart-lr": {"kind": "primary", "title": "SEC Litigation Release No. 25794, SEC v. Schueler a/k/a Richard Heart, Hex, PulseChain, and PulseX (31 Jul 2023)", "url": "https://www.sec.gov/enforcement-litigation/litigation-releases/lr-25794", "archive_url": "https://web.archive.org/web/20261105042239/https://www.sec.gov/enforcement-litigation/litigation-releases/lr-25794", "archive_date": "20261105042239", "archive_how": "existing"}, "sec-heart-complaint": {"kind": "primary", "title": "SEC complaint, SEC v. Schueler, No. 1:23-cv-05749 (E.D.N.Y., filed 31 Jul 2023)", "url": "https://www.sec.gov/files/litigation/complaints/2023/comp-pr2023-143.pdf", "archive_url": "https://web.archive.org/web/20261021050734/https://www.sec.gov/files/litigation/complaints/2023/comp-pr2023-143.pdf", "archive_date": "20261021050734", "archive_how": "existing"}, "heart-dismissal": {"kind": "primary", "title": "Memorandum & Order (Amon, J.), SEC v. Schueler, 23-cv-5749, ECF No. 57 (CourtListener copy)", "url": "https://storage.courtlistener.com/recap/gov.uscourts.nyed.501047/gov.uscourts.nyed.501047.57.0.pdf", "archive_url": "https://web.archive.org/web/20261016182556/https://storage.courtlistener.com/recap/gov.uscourts.nyed.501047/gov.uscourts.nyed.501047.57.0.pdf", "archive_date": "20261016182556", "archive_how": "existing"}, "csv-heart": {"kind": "secondary", "title": "Clark Smith Villazor LLP (Heart's counsel), “SEC Declines to File Amended Complaint …”, 23 Apr 2025", "url": "https://www.csvllp.com/latest-news/sec-declines-to-file-amended-complaint-against-csv-client-richard-heart-cementing-a-complete-victory-for-mr-heart-in-the-secs-case-against-him", "archive_url": "https://web.archive.org/web/20251114065858/https://www.csvllp.com/latest-news/sec-declines-to-file-amended-complaint-against-csv-client-richard-heart-cementing-a-complete-victory-for-mr-heart-in-the-secs-case-against-him", "archive_date": "20251114065858", "archive_how": "existing"}, "hex-site": {"kind": "primary", "title": "hex.com homepage (read 13 Nov 2026; lists the HEX contract address)", "url": "https://hex.com/", "archive_url": "https://web.archive.org/web/20260918074328/https://hex.com/", "archive_date": "20260918074328", "archive_how": "existing"}, "mbc-wp": {"kind": "primary", "title": "MicroBitcoin whitepaper, “MicroBitcoin: decentralized peer-to-peer payment platform for the micro-economy”", "url": "https://microbitcoin.org/assets/files/MicroBitcoin_Whitepaper(ENG).pdf", "archive_url": "https://web.archive.org/web/20210308141021/https://microbitcoin.org/assets/files/MicroBitcoin_Whitepaper(ENG).pdf", "archive_date": "20210308141021", "archive_how": "existing"}, "mbc-readme": {"kind": "primary", "title": "MicroBitcoin README, GitHub MicroBitcoinOrg/MicroBitcoin", "url": "https://github.com/MicroBitcoinOrg/MicroBitcoin", "archive_url": "https://web.archive.org/web/20251121074142/https://github.com/MicroBitcoinOrg/MicroBitcoin", "archive_date": "20251121074142", "archive_how": "existing"}, "bcp-readme": {"kind": "primary", "title": "Bitcoin Cash Plus README, GitHub bitcoincashplus/bitcoincashplus", "url": "https://github.com/bitcoincashplus/bitcoincashplus", "archive_url": "https://web.archive.org/web/20230313011313/https://github.com/bitcoincashplus/bitcoincashplus", "archive_date": "20230313011313", "archive_how": "existing"}, "btp-ct": {"kind": "secondary", "title": "Cointelegraph, “Bitcoin Platinum Created By South Korean Teenager As a Scam, Local Market Erupts”, 10 Dec 2017", "url": "https://cointelegraph.com/news/bitcoin-platinum-created-by-south-korean-teenager-as-a-scam-local-market-erupts", "archive_url": "https://web.archive.org/web/20261020000042/https://cointelegraph.com/news/bitcoin-platinum-created-by-south-korean-teenager-as-a-scam-local-market-erupts", "archive_date": "20261020000042", "archive_how": "existing"}, "btp-site": {"kind": "primary", "title": "Bitcoin Platinum website, bitcoinplatinum.github.io (Wayback Machine copy, 11 Dec 2017)", "url": "https://web.archive.org/web/20171211135132/https://bitcoinplatinum.github.io", "archive_url": "https://web.archive.org/web/20171211135132/https://bitcoinplatinum.github.io", "archive_date": "20171211135132", "archive_how": "already-wayback"}, "btsi-ann": {"kind": "primary", "title": "Simonsolo, “Bitcoin Silver - Make Bitcoin Decentralized Again”, Bitcointalk topic 2311582 (24 Oct 2017)", "url": "https://bitcointalk.org/index.php?topic=2311582.0", "archive_url": "https://web.archive.org/web/20260218004854/https://bitcointalk.org/index.php?topic=2311582.0", "archive_date": "20260218004854", "archive_how": "existing"}, "nano-readme": {"kind": "primary", "title": "Bitcoin Nano README, GitHub bitcoinnano/Bitcoin-Nano", "url": "https://github.com/bitcoinnano/Bitcoin-Nano", "archive_url": "https://web.archive.org/web/20250822124534/https://github.com/bitcoinnano/Bitcoin-Nano", "archive_date": "20250822124534", "archive_how": "existing"}, "bcs-site": {"kind": "primary", "title": "Bitcoin Smart website, bcs.info (Wayback Machine copy, 30 Jan 2018)", "url": "https://web.archive.org/web/20180130204437/http://bcs.info:80/", "archive_url": "https://web.archive.org/web/20180130204437/http://bcs.info:80/", "archive_date": "20180130204437", "archive_how": "already-wayback"}, "btf-site": {"kind": "primary", "title": "Bitcoin Faith website, bitcoinfaith.org (Wayback Machine copy, 1 Jan 2018)", "url": "https://web.archive.org/web/20180101194727/http://www.bitcoinfaith.org/", "archive_url": "https://web.archive.org/web/20180101194727/http://www.bitcoinfaith.org/", "archive_date": "20180101194727", "archive_how": "already-wayback"}, "bum-ann": {"kind": "primary", "title": "BitcoinUranium, “Bitcoin Uranium- Make Bitcoin Great Again”, Bitcointalk topic 2316506 (25 Oct 2017)", "url": "https://bitcointalk.org/index.php?topic=2316506.0", "archive_url": "https://web.archive.org/web/20260618053107/https://bitcointalk.org/index.php?topic=2316506.0", "archive_date": "20260618053107", "archive_how": "existing"}, "bum-readme": {"kind": "primary", "title": "Bitcoin Uranium README, GitHub BitcoinUranium/bitcoin", "url": "https://github.com/BitcoinUranium/bitcoin", "archive_url": "https://web.archive.org/web/20250822120740/https://github.com/BitcoinUranium/bitcoin", "archive_date": "20250822120740", "archive_how": "existing"}, "qbtc-site": {"kind": "primary", "title": "Quantum Bitcoin website, qbtc.world/en (Wayback Machine copy, 14 May 2018)", "url": "https://web.archive.org/web/20180514071634/http://qbtc.world:80/en/", "archive_url": "https://web.archive.org/web/20180514071634/http://qbtc.world:80/en/", "archive_date": "20180514071634", "archive_how": "already-wayback"}, "bth2-readme": {"kind": "primary", "title": "Bithereum README, GitHub BTHPOS/BTH", "url": "https://github.com/BTHPOS/BTH", "archive_url": "https://web.archive.org/web/20220621221347/https://github.com/BTHPOS/BTH", "archive_date": "20220621221347", "archive_how": "existing"}, "btc2-ann": {"kind": "primary", "title": "jackleszz, “[BTC2] Bitcoin 2, BTC Fork 1:1, PoS”, Bitcointalk topic 2871452 (3 Feb 2018)", "url": "https://bitcointalk.org/index.php?topic=2871452.0", "archive_url": "https://web.archive.org/web/20260423002052/https://bitcointalk.org/index.php?topic=2871452.0", "archive_date": "20260423002052", "archive_how": "existing"}, "btc2-readme": {"kind": "primary", "title": "Bitcoin 2 README, GitHub BITC2/bitcoin2", "url": "https://github.com/BITC2/bitcoin2", "archive_url": "https://web.archive.org/web/20260512042016/https://github.com/BITC2/bitcoin2", "archive_date": "20260512042016", "archive_how": "existing"}, "mwc-readme": {"kind": "primary", "title": "MWC node README, GitHub mwcproject/mwc-node", "url": "https://github.com/mwcproject/mwc-node", "archive_url": "https://web.archive.org/web/20260411205352/https://github.com/mwcproject/mwc-node", "archive_date": "20260411205352", "archive_how": "existing"}, "mwc-roadmap": {"kind": "primary", "title": "MWC roadmap and funds-distribution table, GitHub mwcproject/mwc-node doc/roadmap.md", "url": "https://github.com/mwcproject/mwc-node/blob/master/doc/roadmap.md", "archive_url": "https://web.archive.org/web/20260222014900/https://github.com/mwcproject/mwc-node/blob/master/doc/roadmap.md", "archive_date": "20260222014900", "archive_how": "existing"}, "mwc-claiming": {"kind": "primary", "title": "MWC Qt wallet, “Claiming” guide for the airdrop, GitHub mwcproject/mwc-qt-wallet DOC/claiming.md", "url": "https://github.com/mwcproject/mwc-qt-wallet/blob/master/DOC/claiming.md", "archive_url": "https://web.archive.org/web/20211030172918/https://github.com/mwcproject/mwc-qt-wallet/blob/master/DOC/claiming.md", "archive_date": "20211030172918", "archive_how": "existing"}, "gh-casey": {"kind": "primary", "title": "GitHub profile casey (Casey Rodarmor), account created 2 Mar 2008", "url": "https://github.com/casey", "archive_url": "https://web.archive.org/web/20261031045136/https://github.com/casey", "archive_date": "20261031045136", "archive_how": "existing"}, "ep-s12e13-nft": {"kind": "episode", "title": "Casey Rodarmor on Ordinals (6 Feb 2023): looking into NFTs on Ethereum in late 2021", "url": "https://bitcoin-takeover.com/audio/media/2023-02-06_s12_e13_casey_rodarmor_on_ordinals__inscriptions__bitcoin_culture.mp3", "t": 361, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824044058/https://bitcoin-takeover.com/audio/media/2023-02-06_s12_e13_casey_rodarmor_on_ordinals__inscriptions__bitcoin_culture.mp3", "archive_date": "20260824044058", "archive_how": "existing"}, "ep-s12e13-scheme": {"kind": "episode", "title": "Casey Rodarmor on Ordinals (6 Feb 2023): “the scheme that now is called ordinals”", "url": "https://bitcoin-takeover.com/audio/media/2023-02-06_s12_e13_casey_rodarmor_on_ordinals__inscriptions__bitcoin_culture.mp3", "t": 448, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824044058/https://bitcoin-takeover.com/audio/media/2023-02-06_s12_e13_casey_rodarmor_on_ordinals__inscriptions__bitcoin_culture.mp3", "archive_date": "20260824044058", "archive_how": "existing"}, "ep-s12e13-prior": {"kind": "episode", "title": "Casey Rodarmor on Ordinals (6 Feb 2023): ordinals “had been proposed before”", "url": "https://bitcoin-takeover.com/audio/media/2023-02-06_s12_e13_casey_rodarmor_on_ordinals__inscriptions__bitcoin_culture.mp3", "t": 492, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824044058/https://bitcoin-takeover.com/audio/media/2023-02-06_s12_e13_casey_rodarmor_on_ordinals__inscriptions__bitcoin_culture.mp3", "archive_date": "20260824044058", "archive_how": "existing"}, "ep-s12e13-luke": {"kind": "episode", "title": "Casey Rodarmor on Ordinals (6 Feb 2023): on Luke Dashjr and a mempool filter patch", "url": "https://bitcoin-takeover.com/audio/media/2023-02-06_s12_e13_casey_rodarmor_on_ordinals__inscriptions__bitcoin_culture.mp3", "t": 1115, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824044058/https://bitcoin-takeover.com/audio/media/2023-02-06_s12_e13_casey_rodarmor_on_ordinals__inscriptions__bitcoin_culture.mp3", "archive_date": "20260824044058", "archive_how": "existing"}, "bob-about": {"kind": "primary", "title": "Bob Summerwill, “About Bob”, bobsummerwill.com (read 13 Nov 2026)", "url": "https://bobsummerwill.com/about/", "archive_url": "https://web.archive.org/web/20260422182439/https://bobsummerwill.com/about/", "archive_date": "20260422182439", "archive_how": "existing"}, "gh-bob": {"kind": "primary", "title": "GitHub profile bobsummerwill (Bob Summerwill)", "url": "https://github.com/bobsummerwill", "archive_url": "https://web.archive.org/web/20261020173725/https://github.com/bobsummerwill", "archive_date": "20261020173725", "archive_how": "existing"}, "ep-s17e42-coop": {"kind": "episode", "title": "S17 E42: Bob Summerwill — the ETC Cooperative role began in early 2019", "url": "https://bitcoin-takeover.com/audio/media/2026-09-12_s17_e42_bob_summerwill_on_ethereum_classic_bitcoin_forks_-_12_09_2026_05.24.mp3", "t": 116, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135521/https://bitcoin-takeover.com/s17-e42-bob-summerwill-on-ethereum-classic-bitcoins-fork-season/", "archive_date": "20261113135521", "archive_how": "saved"}, "ep-s17e42-cpp": {"kind": "episode", "title": "S17 E42: Bob Summerwill — at the Ethereum Foundation on the C++ client in 2016", "url": "https://bitcoin-takeover.com/audio/media/2026-09-12_s17_e42_bob_summerwill_on_ethereum_classic_bitcoin_forks_-_12_09_2026_05.24.mp3", "t": 187, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135521/https://bitcoin-takeover.com/s17-e42-bob-summerwill-on-ethereum-classic-bitcoins-fork-season/", "archive_date": "20261113135521", "archive_how": "saved"}, "gh-corallo": {"kind": "primary", "title": "GitHub profile TheBlueMatt (Matt Corallo), account created 3 Mar 2011", "url": "https://github.com/TheBlueMatt", "archive_url": "https://web.archive.org/web/20261113142530/https://github.com/TheBlueMatt", "archive_date": "20261113142530", "archive_how": "saved"}, "bip54": {"kind": "primary", "title": "BIP-54, “Consensus Cleanup” (Antoine Poinsot, Matt Corallo)", "url": "https://github.com/bitcoin/bips/blob/master/bip-0054.md", "archive_url": "https://web.archive.org/web/20260713152221/https://github.com/bitcoin/bips/blob/master/bip-0054.md", "archive_date": "20260713152221", "archive_how": "existing"}, "optech-197": {"kind": "secondary", "title": "Bitcoin Optech Newsletter, 27 Apr 2022, “Discussion about activating CTV”", "url": "https://bitcoinops.org/en/newsletters/2022/04/27/#discussion-about-activating-ctv", "archive_url": "https://web.archive.org/web/20261113140916/https://bitcoinops.org/en/newsletters/2022/04/27/", "archive_date": "20261113140916", "archive_how": "saved"}, "gh-hilliard": {"kind": "primary", "title": "GitHub profile jameshilliard (James Hilliard), account created 17 Jan 2013", "url": "https://github.com/jameshilliard", "archive_url": "https://web.archive.org/web/20261013014238/https://github.com/jameshilliard", "archive_date": "20261013014238", "archive_how": "existing"}, "gh-jl2012": {"kind": "primary", "title": "GitHub profile jl2012 (Johnson Lau), account created 9 Aug 2014", "url": "https://github.com/jl2012", "archive_url": "https://web.archive.org/web/20260622203639/https://github.com/jl2012", "archive_date": "20260622203639", "archive_how": "existing"}, "optech-gcc": {"kind": "secondary", "title": "Bitcoin Optech topic, “Consensus cleanup soft fork” (also covering BIP54)", "url": "https://bitcoinops.org/en/topics/consensus-cleanup-soft-fork/", "archive_url": "https://web.archive.org/web/20261010224138/https://bitcoinops.org/en/topics/consensus-cleanup-soft-fork/", "archive_date": "20261010224138", "archive_how": "existing"}, "ep-s17e48-gcc": {"kind": "episode", "title": "S17 E48: Robin Linus on Peter Todd's guess of a 2029 Great Consensus Cleanup", "url": "https://bitcoin-takeover.com/audio/media/2026-10-24_s17_e48_robin_linus_in_the_1000_btc_car_at_bitdevs_in_atlanta_-_23_10_2026_09.45.mp3", "t": 2354, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135732/https://bitcoin-takeover.com/episodes/s17-e48-robin-linus-in-the-1000-btc-car-driving-to-bitdevs-atlanta/", "archive_date": "20261113135732", "archive_how": "saved"}, "ep-s17e48-template": {"kind": "episode", "title": "S17 E48: Robin Linus — “We're going to get BIP 448, TEMPLATEHASH”", "url": "https://bitcoin-takeover.com/audio/media/2026-10-24_s17_e48_robin_linus_in_the_1000_btc_car_at_bitdevs_in_atlanta_-_23_10_2026_09.45.mp3", "t": 2426, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135732/https://bitcoin-takeover.com/episodes/s17-e48-robin-linus-in-the-1000-btc-car-driving-to-bitdevs-atlanta/", "archive_date": "20261113135732", "archive_how": "saved"}, "bip119": {"kind": "primary", "title": "BIP-119, “CHECKTEMPLATEVERIFY” (Jeremy Rubin)", "url": "https://github.com/bitcoin/bips/blob/master/bip-0119.mediawiki", "archive_url": "https://web.archive.org/web/20261013000340/https://github.com/bitcoin/bips/blob/master/bip-0119.mediawiki", "archive_date": "20261013000340", "archive_how": "existing"}, "rubin-2022": {"kind": "primary", "title": "Jeremy Rubin, “7 Theses on a next step for BIP-119”, rubin.io, 17 Apr 2022", "url": "https://rubin.io/bitcoin/2022/04/17/next-steps-bip119/", "archive_url": "https://web.archive.org/web/20260120221334/https://rubin.io/bitcoin/2022/04/17/next-steps-bip119/", "archive_date": "20260120221334", "archive_how": "existing"}, "optech-ctv": {"kind": "secondary", "title": "Bitcoin Optech topic, “OP_CHECKTEMPLATEVERIFY”", "url": "https://bitcoinops.org/en/topics/op_checktemplateverify/", "archive_url": "https://web.archive.org/web/20260626064300/https://bitcoinops.org/en/topics/op_checktemplateverify/", "archive_date": "20260626064300", "archive_how": "existing"}, "optech-2025-07": {"kind": "secondary", "title": "Bitcoin Optech Newsletter, 4 Jul 2025, “Open letter about CTV and CSFS”", "url": "https://bitcoinops.org/en/newsletters/2025/07/04/#open-letter-about-ctv-and-csfs", "archive_url": "https://web.archive.org/web/20260417113529/https://bitcoinops.org/en/newsletters/2025/07/04/", "archive_date": "20260417113529", "archive_how": "existing"}, "optech-2026-01": {"kind": "secondary", "title": "Bitcoin Optech Newsletter, 2 Jan 2026, “CTV activation meeting”", "url": "https://bitcoinops.org/en/newsletters/2026/01/02/#ctv-activation-meeting", "archive_url": "https://web.archive.org/web/20261011175907/https://bitcoinops.org/en/newsletters/2026/01/02/", "archive_date": "20261011175907", "archive_how": "existing"}, "ep-s17e38-ctv": {"kind": "episode", "title": "S17 E38: Vlad on Jeremy Rubin's 2022 Speedy Trial attempt for CTV", "url": "https://bitcoin-takeover.com/audio/media/2026-08-18_s17_e38_keagan_mcclelland_on_bitcoin_development_lightning.mp3", "t": 473, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153659/https://bitcoin-takeover.com/s17-e38-keagan-mcclelland-on-lightning-metrics-covenants-consensus-politics-verifying-bitcoin/", "archive_date": "20261113153659", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e38-stb": {"kind": "episode", "title": "S17 E38: Keagan McClelland — CTV “used to be called OP_SECURE_THE_BAG”", "url": "https://bitcoin-takeover.com/audio/media/2026-08-18_s17_e38_keagan_mcclelland_on_bitcoin_development_lightning.mp3", "t": 617, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153659/https://bitcoin-takeover.com/s17-e38-keagan-mcclelland-on-lightning-metrics-covenants-consensus-politics-verifying-bitcoin/", "archive_date": "20261113153659", "archive_how": "saved", "archive_of": "episode page"}, "btc1-pr117": {"kind": "primary", "title": "jgarzik, btc1/bitcoin PR #117 “[consensus] Add opt-in transaction avoidance” (opened 23 Aug 2017, closed 12 Oct 2017)", "url": "https://github.com/btc1/bitcoin/pull/117", "archive_url": "https://web.archive.org/web/20250822124437/https://github.com/btc1/bitcoin/pull/117", "archive_date": "20250822124437", "archive_how": "existing"}, "btc1-pr134": {"kind": "primary", "title": "jgarzik, btc1/bitcoin PR #134 “[consensus] Add opt-in transaction avoidance” (re-branched; opened 12 Oct 2017, closed 8 Nov 2017, no GitHub merge recorded)", "url": "https://github.com/btc1/bitcoin/pull/134", "archive_url": "https://web.archive.org/web/20251002165927/https://github.com/btc1/bitcoin/pull/134", "archive_date": "20251002165927", "archive_how": "existing"}, "antpool-site": {"kind": "primary", "title": "ANTPOOL homepage, antpool.com (read 13 Nov 2026; title only, the page is a JavaScript app)", "url": "https://www.antpool.com/", "archive_url": "https://web.archive.org/web/20261109161856/https://www.antpool.com/", "archive_date": "20261109161856", "archive_how": "existing"}, "casa-site": {"kind": "primary", "title": "Casa homepage, casa.io (read 13 Nov 2026)", "url": "https://casa.io/", "archive_url": "https://web.archive.org/web/20261107151618/https://casa.io/", "archive_date": "20261107151618", "archive_how": "existing"}, "casa-2019": {"kind": "primary", "title": "Jeremy Welch, “Casa 2019 In Review and a Personal Update”, Casa blog, 31 Jan 2020", "url": "https://blog.casa.io/casa-2019-in-review-and-personal-update/", "archive_url": "https://web.archive.org/web/20260610032949/https://blog.casa.io/casa-2019-in-review-and-personal-update/", "archive_date": "20260610032949", "archive_how": "existing"}, "casa-keymaster": {"kind": "primary", "title": "Jeremy Welch, “Multisig Security for Everyone!”, Casa blog, 28 Feb 2019", "url": "https://blog.casa.io/multisig-security-for-everyone-keymaster/", "archive_url": "https://web.archive.org/web/20260610024848/https://blog.casa.io/multisig-security-for-everyone-keymaster/", "archive_date": "20260610024848", "archive_how": "existing"}, "ep-s17e47-casa": {"kind": "episode", "title": "S17 E47: Vlad on BitGo and Casa multisig custody", "url": "https://bitcoin-takeover.com/audio/media/2026-10-18_s17_e47-_tabconf_8_livestream_with_kevin_loaec_ekrem_bal_spaces_protocol_the_bitcoin_pivot.mp3", "t": 10077, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135646/https://bitcoin-takeover.com/s17-e47-tabconf-8-livestream-with-kevin-loaec-ekrem-bal-spaces-protocol-the-bitcoin-pivot/", "archive_date": "20261113135646", "archive_how": "saved"}, "gorilla-site": {"kind": "primary", "title": "GorillaPool, gorillapool.com (read 13 Nov 2026)", "url": "https://gorillapool.com/", "archive_url": "https://web.archive.org/web/20260719190017/https://gorillapool.com/", "archive_date": "20260719190017", "archive_how": "existing"}, "gorilla-io": {"kind": "primary", "title": "GorillaPool, gorillapool.io (read 13 Nov 2026)", "url": "https://gorillapool.io/", "archive_url": "https://web.archive.org/web/20260811185325/https://gorillapool.io/", "archive_date": "20260811185325", "archive_how": "existing"}, "etc-history": {"kind": "secondary", "title": "Ethereum Classic, “History” timeline, ethereumclassic.org (entry of 26 Jul 2022)", "url": "https://ethereumclassic.org/knowledge/history", "archive_url": "https://web.archive.org/web/20261010174916/https://ethereumclassic.org/knowledge/history/", "archive_date": "20261010174916", "archive_how": "existing"}, "btc-501407": {"kind": "primary", "title": "mempool.space, Bitcoin block 501,407 (header time 2017-12-28 10:52:58 UTC)", "url": "https://mempool.space/block/501407", "archive_url": "https://web.archive.org/web/20261113144918/https://mempool.space/block/501407", "archive_date": "20261113144918", "archive_how": "saved"}, "btc-509696": {"kind": "primary", "title": "mempool.space, Bitcoin block 509,696 (header time 2018-02-18 02:33:41 UTC)", "url": "https://mempool.space/block/509696", "archive_url": "https://web.archive.org/web/20261113145846/https://mempool.space/block/509696", "archive_date": "20261113145846", "archive_how": "saved"}, "btc-505050": {"kind": "primary", "title": "mempool.space, Bitcoin block 505,050 (header time 2018-01-19 21:58:53 UTC)", "url": "https://mempool.space/block/505050", "archive_url": "https://web.archive.org/web/20261113145301/https://mempool.space/block/505050", "archive_date": "20261113145301", "archive_how": "saved"}, "btc-507850": {"kind": "primary", "title": "mempool.space, Bitcoin block 507,850 (header time 2018-02-05 21:16:26 UTC)", "url": "https://mempool.space/block/507850", "archive_url": "https://web.archive.org/web/20261113145725/https://mempool.space/block/507850", "archive_date": "20261113145725", "archive_how": "saved"}, "btc-508888": {"kind": "primary", "title": "mempool.space, Bitcoin block 508,888 (header time 2018-02-12 22:26:22 UTC)", "url": "https://mempool.space/block/508888", "archive_url": "https://web.archive.org/web/20261113145819/https://mempool.space/block/508888", "archive_date": "20261113145819", "archive_how": "saved"}, "btc-555000": {"kind": "primary", "title": "mempool.space, Bitcoin block 555,000 (header time 2018-12-22 23:41:03 UTC)", "url": "https://mempool.space/block/555000", "archive_url": "https://web.archive.org/web/20261113151353/https://mempool.space/block/555000", "archive_date": "20261113151353", "archive_how": "saved"}, "btc-525000": {"kind": "primary", "title": "mempool.space, Bitcoin block 525,000 (header time 2018-05-29 20:24:42 UTC)", "url": "https://mempool.space/block/525000", "archive_url": "https://web.archive.org/web/20261113150845/https://mempool.space/block/525000", "archive_date": "20261113150845", "archive_how": "saved"}, "btc-500000": {"kind": "primary", "title": "mempool.space, Bitcoin block 500,000 (header time 2017-12-18 18:35:25 UTC)", "url": "https://mempool.space/block/500000", "archive_url": "https://web.archive.org/web/20261113144617/https://mempool.space/block/500000", "archive_date": "20261113144617", "archive_how": "saved"}, "btfl-site": {"kind": "primary", "title": "Bitcoin Flash website, bitcoinflash.io (Wayback Machine copy, 1 Jan 2018)", "url": "https://web.archive.org/web/20180101135255/https://bitcoinflash.io/", "archive_url": "https://web.archive.org/web/20180101135255/https://bitcoinflash.io/", "archive_date": "20180101135255", "archive_how": "already-wayback"}, "btv-readme": {"kind": "primary", "title": "Bitvote README, GitHub bitcoinvote/bitcoin", "url": "https://github.com/bitcoinvote/bitcoin", "archive_url": "https://web.archive.org/web/20241212071947/https://github.com/bitcoinvote/bitcoin", "archive_date": "20241212071947", "archive_how": "existing"}, "btv-site": {"kind": "primary", "title": "Bitvote website, bitvote.one (Wayback Machine copy, 1 Feb 2018)", "url": "https://web.archive.org/web/20180201193019/https://bitvote.one/", "archive_url": "https://web.archive.org/web/20180201193019/https://bitvote.one/", "archive_date": "20180201193019", "archive_how": "already-wayback"}, "btt-readme": {"kind": "primary", "title": "Bitcoin Top README, GitHub bitcointop/bitcointop", "url": "https://github.com/bitcointop/bitcointop", "archive_url": "https://web.archive.org/web/20250819225403/https://github.com/bitcointop/bitcointop", "archive_date": "20250819225403", "archive_how": "existing"}, "btt-site": {"kind": "primary", "title": "Bitcoin Top website, bitcointop.org (Wayback Machine copy, 3 Feb 2018)", "url": "https://web.archive.org/web/20180203141707/https://bitcointop.org/", "archive_url": "https://web.archive.org/web/20180203141707/https://bitcointop.org/", "archive_date": "20180203141707", "archive_how": "already-wayback"}, "bck-site": {"kind": "primary", "title": "Bitcoin King website, btcking.org (Wayback Machine copy, 31 Aug 2018)", "url": "https://web.archive.org/web/20180831121211/https://btcking.org/", "archive_url": "https://web.archive.org/web/20180831121211/https://btcking.org/", "archive_date": "20180831121211", "archive_how": "already-wayback"}, "nbtc-site": {"kind": "primary", "title": "New Bitcoin (新比特币) website, newbitcoin.org (Wayback Machine copy, 4 Mar 2018)", "url": "https://web.archive.org/web/20180304153514/http://www.newbitcoin.org:80/", "archive_url": "https://web.archive.org/web/20180304153514/http://www.newbitcoin.org:80/", "archive_date": "20180304153514", "archive_how": "already-wayback"}, "ayms-nbtc": {"kind": "primary", "title": "Ayms, reply of 1 May 2018 in “Bitcoin and forks transactions tool …”, Bitcointalk topic 2827163 (page 3)", "url": "https://bitcointalk.org/index.php?topic=2827163.40", "archive_url": "https://web.archive.org/web/20200516233717/https://bitcointalk.org/index.php?topic=2827163.40", "archive_date": "20200516233717", "archive_how": "existing"}, "bco-site": {"kind": "primary", "title": "Bitcoin Ore website, bitcoinore.org (Wayback Machine copy, 20 Feb 2018)", "url": "https://web.archive.org/web/20180220224053/http://bitcoinore.org:80/", "archive_url": "https://web.archive.org/web/20180220224053/http://bitcoinore.org:80/", "archive_date": "20180220224053", "archive_how": "already-wayback"}, "btcl-site": {"kind": "primary", "title": "Bitcoin Lite website, bitcoinlite.us (Wayback Machine copy, 17 Jan 2018)", "url": "https://web.archive.org/web/20180117002408/http://www.bitcoinlite.us:80/", "archive_url": "https://web.archive.org/web/20180117002408/http://www.bitcoinlite.us:80/", "archive_date": "20180117002408", "archive_how": "already-wayback"}, "bcl-site": {"kind": "primary", "title": "bitcoinClean website, bitcoinclean.org (Wayback Machine copy, 10 May 2018)", "url": "https://web.archive.org/web/20180510051046/https://bitcoinclean.org/", "archive_url": "https://web.archive.org/web/20180510051046/https://bitcoinclean.org/", "archive_date": "20180510051046", "archive_how": "already-wayback"}, "btw-readme": {"kind": "primary", "title": "Bitcoin World README, GitHub btwone/btwcore", "url": "https://github.com/btwone/btwcore", "archive_url": "https://web.archive.org/web/20241212030727/https://github.com/btwone/btwcore", "archive_date": "20241212030727", "archive_how": "existing"}, "wbtc-readme": {"kind": "primary", "title": "World Bitcoin README, GitHub worldbitcoin/worldbitcoin", "url": "https://github.com/worldbitcoin/worldbitcoin", "archive_url": "https://web.archive.org/web/20201022053248/https://github.com/worldbitcoin/worldbitcoin", "archive_date": "20201022053248", "archive_how": "existing"}, "wbtc-site": {"kind": "primary", "title": "World Bitcoin website, wbtcteam.org (Wayback Machine copy, 22 Feb 2018)", "url": "https://web.archive.org/web/20180222064415/http://www.wbtcteam.org:80/", "archive_url": "https://web.archive.org/web/20180222064415/http://www.wbtcteam.org:80/", "archive_date": "20180222064415", "archive_how": "already-wayback"}, "cbtc-readme": {"kind": "primary", "title": "ClassicBitcoin (CBTC) README, GitHub classicbitcoins/cbitcoin", "url": "https://github.com/classicbitcoins/cbitcoin", "archive_url": "https://web.archive.org/web/20251012002000/https://github.com/classicbitcoins/cbitcoin", "archive_date": "20251012002000", "archive_how": "existing"}, "cbtc-ann": {"kind": "primary", "title": "bitclassic, “ClassicBitcoin (CBTC). Cryptocurrency for the BitClassic MarketPlace.”, Bitcointalk topic 3095296 (opened 10 Mar 2018; current OP)", "url": "https://bitcointalk.org/index.php?topic=3095296.0", "archive_url": "https://web.archive.org/web/20230415073926/https://bitcointalk.org/index.php?topic=3095296.0", "archive_date": "20230415073926", "archive_how": "existing"}, "sbc-site": {"kind": "primary", "title": "Smart Bitcoin website, smartbitcoin.one (Wayback Machine copy, 21 May 2018)", "url": "https://web.archive.org/web/20180521145157/http://www.smartbitcoin.one:80/index-en.html", "archive_url": "https://web.archive.org/web/20180521145157/http://www.smartbitcoin.one:80/index-en.html", "archive_date": "20180521145157", "archive_how": "already-wayback"}, "fbtc-readme": {"kind": "primary", "title": "FastBitcoin README, GitHub fastbitcoin/fastbitcoin", "url": "https://github.com/fastbitcoin/fastbitcoin", "archive_url": "https://web.archive.org/web/20250819235945/https://github.com/fastbitcoin/fastbitcoin", "archive_date": "20250819235945", "archive_how": "existing"}, "fbtc-site": {"kind": "primary", "title": "FastBitcoin website, fbtc.pro (Wayback Machine copy, 31 Aug 2018)", "url": "https://web.archive.org/web/20180831143443/https://fbtc.pro/index-en.html", "archive_url": "https://web.archive.org/web/20180831143443/https://fbtc.pro/index-en.html", "archive_date": "20180831143443", "archive_how": "already-wayback"}, "btcs-site": {"kind": "primary", "title": "BitcoinStake website, btcscoin.com (Chinese; Wayback Machine copy, 28 Dec 2017)", "url": "https://web.archive.org/web/20171228144023/http://btcscoin.com:80/", "archive_url": "https://web.archive.org/web/20171228144023/http://btcscoin.com:80/", "archive_date": "20171228144023", "archive_how": "already-wayback"}, "bcz-ann": {"kind": "primary", "title": "BitcoinCash Zero, “[ANN] [NEW] [FORK] BitcoinCash Zero $BCZ - 2019, January the 4th”, Bitcointalk topic 5086626 (18 Dec 2018)", "url": "https://bitcointalk.org/index.php?topic=5086626.0", "archive_url": "https://web.archive.org/web/20230415201630/https://bitcointalk.org/index.php?topic=5086626.0", "archive_date": "20230415201630", "archive_how": "existing"}, "bpay-site": {"kind": "primary", "title": "Bitcoin Pay website, btceasypay.com (Wayback Machine copy, 1 Feb 2018)", "url": "https://web.archive.org/web/20180201203049/http://www.btceasypay.com:80/", "archive_url": "https://web.archive.org/web/20180201203049/http://www.btceasypay.com:80/", "archive_date": "20180201203049", "archive_how": "already-wayback"}, "btsq-readme": {"kind": "primary", "title": "Bitcoin Community README, GitHub BTSQ/BitcoinCommunity", "url": "https://github.com/BTSQ/BitcoinCommunity", "archive_url": "https://web.archive.org/web/20220621221319/https://github.com/BTSQ/BitcoinCommunity", "archive_date": "20220621221319", "archive_how": "existing"}, "btsq-site": {"kind": "primary", "title": "Bitcoin Community website, btsq.top (Wayback Machine copy, 10 Mar 2018)", "url": "https://web.archive.org/web/20180310184004/http://btsq.top:80/en/index.html", "archive_url": "https://web.archive.org/web/20180310184004/http://btsq.top:80/en/index.html", "archive_date": "20180310184004", "archive_how": "already-wayback"}, "bltg-ann": {"kind": "primary", "title": "aperture, “[LAUNCH] | BLTG | Bitcoin Lightning | Masternodes | PoS”, Bitcointalk topic 2695744 (5 Jan 2018; current OP)", "url": "https://bitcointalk.org/index.php?topic=2695744.0", "archive_url": "https://web.archive.org/web/20260111230429/https://bitcointalk.org/index.php?topic=2695744.0", "archive_date": "20260111230429", "archive_how": "existing"}, "lky-ann": {"kind": "primary", "title": "LuckyC, “[ANN] LuckyCoin LKY | Lucky Blocks | Fast | Fun | Fair”, Bitcointalk topic 214614 (24 May 2013)", "url": "https://bitcointalk.org/index.php?topic=214614.0", "archive_url": "https://web.archive.org/web/20260815173954/https://bitcointalk.org/index.php?topic=214614.0", "archive_date": "20260815173954", "archive_how": "existing"}, "lky-ann2": {"kind": "primary", "title": "Titan, “[ANN] Luckycoin LKY | New Official Thread | Get Lucky!”, Bitcointalk topic 568287 (12 Apr 2014)", "url": "https://bitcointalk.org/index.php?topic=568287.0", "archive_url": "https://web.archive.org/web/20250521052321/https://bitcointalk.org/index.php?topic=568287.0", "archive_date": "20250521052321", "archive_how": "existing"}, "lky-hf": {"kind": "primary", "title": "Titan, “[ANN][LKY] Luckycoin hard fork successful! …”, Bitcointalk topic 310851 (15 Oct 2013)", "url": "https://bitcointalk.org/index.php?topic=310851.0", "archive_url": "https://web.archive.org/web/20160211150349/https://bitcointalk.org/index.php?topic=310851.0", "archive_date": "20160211150349", "archive_how": "existing"}, "lky-readme": {"kind": "primary", "title": "Luckycoin README, GitHub LuckyCoinProject/Luckycoin", "url": "https://github.com/LuckyCoinProject/Luckycoin", "archive_url": "https://web.archive.org/web/20260318030113/https://github.com/LuckyCoinProject/Luckycoin", "archive_date": "20260318030113", "archive_how": "existing"}, "btc-499345": {"kind": "primary", "title": "mempool.space, Bitcoin block 499,345 (header time 2017-12-15 00:15:00 UTC)", "url": "https://mempool.space/block/499345", "archive_url": "https://web.archive.org/web/20261113144339/https://mempool.space/block/499345", "archive_date": "20261113144339", "archive_how": "saved"}, "btc-499777": {"kind": "primary", "title": "mempool.space, Bitcoin block 499,777 (header time 2017-12-17 12:11:17 UTC)", "url": "https://mempool.space/block/499777", "archive_url": "https://web.archive.org/web/20261113144406/https://mempool.space/block/499777", "archive_date": "20261113144406", "archive_how": "saved"}, "btc-501118": {"kind": "primary", "title": "mempool.space, Bitcoin block 501,118 (header time 2017-12-26 13:50:32 UTC)", "url": "https://mempool.space/block/501118", "archive_url": "https://web.archive.org/web/20261113144756/https://mempool.space/block/501118", "archive_date": "20261113144756", "archive_how": "saved"}, "btc-501949": {"kind": "primary", "title": "mempool.space, Bitcoin block 501,949 (header time 2017-12-31 22:53:08 UTC)", "url": "https://mempool.space/block/501949", "archive_url": "https://web.archive.org/web/20261113145040/https://mempool.space/block/501949", "archive_date": "20261113145040", "archive_how": "saved"}, "btc-502502": {"kind": "primary", "title": "mempool.space, Bitcoin block 502,502 (header time 2018-01-04 08:00:26 UTC)", "url": "https://mempool.space/block/502502", "archive_url": "https://web.archive.org/web/20261113145140/https://mempool.space/block/502502", "archive_date": "20261113145140", "archive_how": "saved"}, "btc-503888": {"kind": "primary", "title": "mempool.space, Bitcoin block 503,888 (header time 2018-01-12 16:44:38 UTC)", "url": "https://mempool.space/block/503888", "archive_url": "https://web.archive.org/web/20261113145234/https://mempool.space/block/503888", "archive_date": "20261113145234", "archive_how": "saved"}, "btc-506066": {"kind": "primary", "title": "mempool.space, Bitcoin block 506,066 (header time 2018-01-25 15:20:45 UTC)", "url": "https://mempool.space/block/506066", "archive_url": "https://web.archive.org/web/20261113145423/https://mempool.space/block/506066", "archive_date": "20261113145423", "archive_how": "saved"}, "btc-508000": {"kind": "primary", "title": "mempool.space, Bitcoin block 508,000 (header time 2018-02-06 19:28:06 UTC)", "url": "https://mempool.space/block/508000", "archive_url": "https://web.archive.org/web/20261113145752/https://mempool.space/block/508000", "archive_date": "20261113145752", "archive_how": "saved"}, "btc-516095": {"kind": "primary", "title": "mempool.space, Bitcoin block 516,095 (header time 2018-04-01 07:01:43 UTC)", "url": "https://mempool.space/block/516095", "archive_url": "https://web.archive.org/web/20261113150255/https://mempool.space/block/516095", "archive_date": "20261113150255", "archive_how": "saved"}, "btc-518800": {"kind": "primary", "title": "mempool.space, Bitcoin block 518,800 (header time 2018-04-18 15:26:13 UTC)", "url": "https://mempool.space/block/518800", "archive_url": "https://web.archive.org/web/20261113150412/https://mempool.space/block/518800", "archive_date": "20261113150412", "archive_how": "saved"}, "btc-520000": {"kind": "primary", "title": "mempool.space, Bitcoin block 520,000 (header time 2018-04-26 10:40:17 UTC)", "url": "https://mempool.space/block/520000", "archive_url": "https://web.archive.org/web/20261113150538/https://mempool.space/block/520000", "archive_date": "20261113150538", "archive_how": "saved"}, "gavin-gist": {"kind": "primary", "title": "Gavin Andresen, “OP_RETURN replay protection patch”, GitHub gist (created 15 Jun 2017)", "url": "https://gist.github.com/gavinandresen/2a7474a3dd5b834ed3a7d10c74ec84c5", "archive_url": "https://web.archive.org/web/20260518010401/https://gist.github.com/gavinandresen/2a7474a3dd5b834ed3a7d10c74ec84c5", "archive_date": "20260518010401", "archive_how": "existing"}, "rubin-site": {"kind": "primary", "title": "Jeremy Rubin, rubin.io homepage (read 13 Nov 2026)", "url": "https://rubin.io/", "archive_url": "https://web.archive.org/web/20261009114551/https://rubin.io/", "archive_date": "20261009114551", "archive_how": "existing"}, "ep-s17e22-char": {"kind": "episode", "title": "S17 E22: Jeremy Rubin — “I'm working on Char”", "url": "https://bitcoin-takeover.com/audio/media/2026-05-06_s17_e11_jeremy_rubin_on_ctv_char_building_on_bitcoin.mp3", "t": 3960, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153315/https://bitcoin-takeover.com/s17-e22-jeremy-rubin-on-ctv-char-relentless-building-in-an-adversarial-environment/", "archive_date": "20261113153315", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e22-stb": {"kind": "episode", "title": "S17 E22: Vlad on CTV's earlier name, Secure the Bag", "url": "https://bitcoin-takeover.com/audio/media/2026-05-06_s17_e11_jeremy_rubin_on_ctv_char_building_on_bitcoin.mp3", "t": 206, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153315/https://bitcoin-takeover.com/s17-e22-jeremy-rubin-on-ctv-char-relentless-building-in-an-adversarial-environment/", "archive_date": "20261113153315", "archive_how": "saved", "archive_of": "episode page"}, "gh-darosior": {"kind": "primary", "title": "GitHub profile darosior (Antoine Poinsot), read 13 Nov 2026", "url": "https://github.com/darosior", "archive_url": "https://web.archive.org/web/20261113143157/https://github.com/darosior", "archive_date": "20261113143157", "archive_how": "saved"}, "gh-linus": {"kind": "primary", "title": "GitHub profile RobinLinus, read 13 Nov 2026", "url": "https://github.com/RobinLinus", "archive_url": "https://web.archive.org/web/20261005023520/https://github.com/RobinLinus", "archive_date": "20261005023520", "archive_how": "existing"}, "bitvm-wp": {"kind": "primary", "title": "Robin Linus, “BitVM: Compute Anything on Bitcoin” (whitepaper on bitvm.org, dated 12 Dec 2023)", "url": "https://bitvm.org/bitvm.pdf", "archive_url": "https://web.archive.org/web/20261109013824/https://bitvm.org/bitvm.pdf", "archive_date": "20261109013824", "archive_how": "existing"}, "bitvm-site": {"kind": "primary", "title": "bitvm.org, “BitVM - Smarter Bitcoin Contracts” (read 13 Nov 2026)", "url": "https://bitvm.org/", "archive_url": "https://web.archive.org/web/20261014024759/https://bitvm.org/", "archive_date": "20261014024759", "archive_how": "existing"}, "btk-feed": {"kind": "primary", "title": "Bitcoin Takeover podcast RSS feed, bitcoin-takeover.com/audio/feed.xml (read 13 Nov 2026)", "url": "https://bitcoin-takeover.com/audio/feed.xml", "archive_url": "https://web.archive.org/web/20261016084252/https://bitcoin-takeover.com/audio/feed.xml", "archive_date": "20261016084252", "archive_how": "existing"}, "gh-keags": {"kind": "primary", "title": "GitHub profile ProofOfKeags (Keagan McClelland), read 13 Nov 2026", "url": "https://github.com/ProofOfKeags", "archive_url": "https://web.archive.org/web/20261030140048/https://github.com/ProofOfKeags", "archive_date": "20261030140048", "archive_how": "existing"}, "ep-s17e38-intro": {"kind": "episode", "title": "S17 E38: Vlad introduces Keagan McClelland", "url": "https://bitcoin-takeover.com/audio/media/2026-08-18_s17_e38_keagan_mcclelland_on_bitcoin_development_lightning.mp3", "t": 46, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153659/https://bitcoin-takeover.com/s17-e38-keagan-mcclelland-on-lightning-metrics-covenants-consensus-politics-verifying-bitcoin/", "archive_date": "20261113153659", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e38-start9": {"kind": "episode", "title": "S17 E38: Keagan McClelland — “Start9 is what came out of that”", "url": "https://bitcoin-takeover.com/audio/media/2026-08-18_s17_e38_keagan_mcclelland_on_bitcoin_development_lightning.mp3", "t": 418, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153659/https://bitcoin-takeover.com/s17-e38-keagan-mcclelland-on-lightning-metrics-covenants-consensus-politics-verifying-bitcoin/", "archive_date": "20261113153659", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e38-hill": {"kind": "episode", "title": "S17 E38: Vlad on Matt Hill of Start9 and BIP-110", "url": "https://bitcoin-takeover.com/audio/media/2026-08-18_s17_e38_keagan_mcclelland_on_bitcoin_development_lightning.mp3", "t": 440, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153659/https://bitcoin-takeover.com/s17-e38-keagan-mcclelland-on-lightning-metrics-covenants-consensus-politics-verifying-bitcoin/", "archive_date": "20261113153659", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e38-judica": {"kind": "episode", "title": "S17 E38: Keagan McClelland on joining Judica to work on Sapio", "url": "https://bitcoin-takeover.com/audio/media/2026-08-18_s17_e38_keagan_mcclelland_on_bitcoin_development_lightning.mp3", "t": 581, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153659/https://bitcoin-takeover.com/s17-e38-keagan-mcclelland-on-lightning-metrics-covenants-consensus-politics-verifying-bitcoin/", "archive_date": "20261113153659", "archive_how": "saved", "archive_of": "episode page"}, "bm-poolin": {"kind": "secondary", "title": "Colin Harper, “Upstart Poolin Discusses Growth, State of Mining and Bitcoin in China”, Bitcoin Magazine, 11 Oct 2019", "url": "https://bitcoinmagazine.com/business/upstart-poolin-discusses-growth-state-of-mining-and-bitcoin-in-china", "archive_url": "https://web.archive.org/web/20260416233243/https://bitcoinmagazine.com/business/upstart-poolin-discusses-growth-state-of-mining-and-bitcoin-in-china", "archive_date": "20260416233243", "archive_how": "existing"}, "optech-timewarp": {"kind": "secondary", "title": "Bitcoin Optech topic, “Time warp”", "url": "https://bitcoinops.org/en/topics/time-warp/", "archive_url": "https://web.archive.org/web/20260613191518/https://bitcoinops.org/en/topics/time-warp/", "archive_date": "20260613191518", "archive_how": "existing"}, "wp-bitgo": {"kind": "secondary", "title": "Wikipedia, “BitGo”", "url": "https://en.wikipedia.org/wiki/BitGo", "archive_url": "https://web.archive.org/web/20261025092143/https://en.wikipedia.org/wiki/BitGo", "archive_date": "20261025092143", "archive_how": "existing"}, "ep-s17e43-2013": {"kind": "episode", "title": "S17 E43: Mike Belshe — “We've been in the space since 2013”", "url": "https://bitcoin-takeover.com/audio/media/2026-09-16_s17_e43_mike_belshe_on_bitgo_quantum_clarity.mp3", "t": 1442, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135601/https://bitcoin-takeover.com/s17-e43-mike-belshe-on-bitgo-quantum-clarity/", "archive_date": "20261113135601", "archive_how": "saved"}, "ep-s17e43-2of3": {"kind": "episode", "title": "S17 E43: Mike Belshe on BitGo's two-of-three wallets", "url": "https://bitcoin-takeover.com/audio/media/2026-09-16_s17_e43_mike_belshe_on_bitgo_quantum_clarity.mp3", "t": 1275, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135601/https://bitcoin-takeover.com/s17-e43-mike-belshe-on-bitgo-quantum-clarity/", "archive_date": "20261113135601", "archive_how": "saved"}, "ep-s17e43-silly": {"kind": "episode", "title": "S17 E43: Mike Belshe — “These agreements were silly in my view”", "url": "https://bitcoin-takeover.com/audio/media/2026-09-16_s17_e43_mike_belshe_on_bitgo_quantum_clarity.mp3", "t": 4534, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135601/https://bitcoin-takeover.com/s17-e43-mike-belshe-on-bitgo-quantum-clarity/", "archive_date": "20261113135601", "archive_how": "saved"}, "ep-s17e43-nya": {"kind": "episode", "title": "S17 E43: Mike Belshe on BitGo's name on the New York Agreement", "url": "https://bitcoin-takeover.com/audio/media/2026-09-16_s17_e43_mike_belshe_on_bitgo_quantum_clarity.mp3", "t": 7720, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135601/https://bitcoin-takeover.com/s17-e43-mike-belshe-on-bitgo-quantum-clarity/", "archive_date": "20261113135601", "archive_how": "saved"}, "ep-s17e43-2x": {"kind": "episode", "title": "S17 E43: Mike Belshe — “I supported the SegWit2x”", "url": "https://bitcoin-takeover.com/audio/media/2026-09-16_s17_e43_mike_belshe_on_bitgo_quantum_clarity.mp3", "t": 7885, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135601/https://bitcoin-takeover.com/s17-e43-mike-belshe-on-bitgo-quantum-clarity/", "archive_date": "20261113135601", "archive_how": "saved"}, "start9-site": {"kind": "primary", "title": "start9.com homepage (read 13 Nov 2026)", "url": "https://start9.com/", "archive_url": "https://web.archive.org/web/20261106205143/https://start9.com/", "archive_date": "20261106205143", "archive_how": "existing"}, "startos-readme": {"kind": "primary", "title": "Start9 monorepo README (StartOS), GitHub Start9Labs/start-os", "url": "https://github.com/Start9Labs/start-os", "archive_url": "https://web.archive.org/web/20260515134430/https://github.com/Start9Labs/start-os", "archive_date": "20260515134430", "archive_how": "existing"}, "judica-site": {"kind": "primary", "title": "judica.org homepage (read 13 Nov 2026)", "url": "https://judica.org/", "archive_url": "https://web.archive.org/web/20260807185216/https://judica.org/", "archive_date": "20260807185216", "archive_how": "existing"}, "wp-circle": {"kind": "secondary", "title": "Wikipedia, “Circle Internet Group” (the “Poloniex” article redirects here)", "url": "https://en.wikipedia.org/wiki/Circle_Internet_Group", "archive_url": "https://web.archive.org/web/20261104092357/https://en.wikipedia.org/wiki/Circle_Internet_Group", "archive_date": "20261104092357", "archive_how": "existing"}, "fd-data": {"kind": "secondary", "title": "forkdrop.io data file json/index.json, the per-coin table behind its fork pages (Wayback Machine copy, 13 Jan 2021)", "url": "https://web.archive.org/web/20210113015549id_/https://forkdrop.io/json/index.json", "archive_url": "https://web.archive.org/web/20210113015549/https://forkdrop.io/json/index.json", "archive_date": "20210113015549", "archive_how": "already-wayback"}, "btc-350000": {"kind": "primary", "title": "mempool.space, Bitcoin block 350,000 (header time 2015-03-30 22:17:14 UTC)", "url": "https://mempool.space/block/350000", "archive_url": "https://web.archive.org/web/20261113143642/https://mempool.space/block/350000", "archive_date": "20261113143642", "archive_how": "saved"}, "btc-480000": {"kind": "primary", "title": "mempool.space, Bitcoin block 480,000 (header time 2017-08-10 23:25:59 UTC)", "url": "https://mempool.space/block/480000", "archive_url": "https://web.archive.org/web/20261113143708/https://mempool.space/block/480000", "archive_date": "20261113143708", "archive_how": "saved"}, "btc-498754": {"kind": "primary", "title": "mempool.space, Bitcoin block 498,754 (header time 2017-12-11 15:07:40 UTC)", "url": "https://mempool.space/block/498754", "archive_url": "https://web.archive.org/web/20261113143955/https://mempool.space/block/498754", "archive_date": "20261113143955", "archive_how": "saved"}, "btc-498960": {"kind": "primary", "title": "mempool.space, Bitcoin block 498,960 (header time 2017-12-12 21:39:19 UTC)", "url": "https://mempool.space/block/498960", "archive_url": "https://web.archive.org/web/20261113144311/https://mempool.space/block/498960", "archive_date": "20261113144311", "archive_how": "saved"}, "btc-499888": {"kind": "primary", "title": "mempool.space, Bitcoin block 499,888 (header time 2017-12-18 02:55:58 UTC)", "url": "https://mempool.space/block/499888", "archive_url": "https://web.archive.org/web/20261113144433/https://mempool.space/block/499888", "archive_date": "20261113144433", "archive_how": "saved"}, "btc-500283": {"kind": "primary", "title": "mempool.space, Bitcoin block 500,283 (header time 2017-12-20 15:57:32 UTC)", "url": "https://mempool.space/block/500283", "archive_url": "https://web.archive.org/web/20261113144701/https://mempool.space/block/500283", "archive_date": "20261113144701", "archive_how": "saved"}, "btc-501000": {"kind": "primary", "title": "mempool.space, Bitcoin block 501,000 (header time 2017-12-25 17:42:45 UTC)", "url": "https://mempool.space/block/501000", "archive_url": "https://web.archive.org/web/20261113144728/https://mempool.space/block/501000", "archive_date": "20261113144728", "archive_how": "saved"}, "btc-501300": {"kind": "primary", "title": "mempool.space, Bitcoin block 501,300 (header time 2017-12-27 18:30:53 UTC)", "url": "https://mempool.space/block/501300", "archive_url": "https://web.archive.org/web/20261113144851/https://mempool.space/block/501300", "archive_date": "20261113144851", "archive_how": "saved"}, "btc-501488": {"kind": "primary", "title": "mempool.space, Bitcoin block 501,488 (header time 2017-12-29 00:06:52 UTC)", "url": "https://mempool.space/block/501488", "archive_url": "https://web.archive.org/web/20261113144945/https://mempool.space/block/501488", "archive_date": "20261113144945", "archive_how": "saved"}, "btc-502233": {"kind": "primary", "title": "mempool.space, Bitcoin block 502,233 (header time 2018-01-02 16:30:22 UTC)", "url": "https://mempool.space/block/502233", "archive_url": "https://web.archive.org/web/20261113145113/https://mempool.space/block/502233", "archive_date": "20261113145113", "archive_how": "saved"}, "btc-502999": {"kind": "primary", "title": "mempool.space, Bitcoin block 502,999 (header time 2018-01-07 11:17:10 UTC)", "url": "https://mempool.space/block/502999", "archive_url": "https://web.archive.org/web/20261113145208/https://mempool.space/block/502999", "archive_date": "20261113145208", "archive_how": "saved"}, "btc-506984": {"kind": "primary", "title": "mempool.space, Bitcoin block 506,984 (header time 2018-01-31 15:31:13 UTC)", "url": "https://mempool.space/block/506984", "archive_url": "https://web.archive.org/web/20261113145451/https://mempool.space/block/506984", "archive_date": "20261113145451", "archive_how": "saved"}, "btc-507000": {"kind": "primary", "title": "mempool.space, Bitcoin block 507,000 (header time 2018-01-31 18:58:44 UTC)", "url": "https://mempool.space/block/507000", "archive_url": "https://web.archive.org/web/20261113145524/https://mempool.space/block/507000", "archive_date": "20261113145524", "archive_how": "saved"}, "btc-507777": {"kind": "primary", "title": "mempool.space, Bitcoin block 507,777 (header time 2018-02-05 12:58:13 UTC)", "url": "https://mempool.space/block/507777", "archive_url": "https://web.archive.org/web/20261113145655/https://mempool.space/block/507777", "archive_date": "20261113145655", "archive_how": "saved"}, "btc-510048": {"kind": "primary", "title": "mempool.space, Bitcoin block 510,048 (header time 2018-02-20 08:20:59 UTC)", "url": "https://mempool.space/block/510048", "archive_url": "https://web.archive.org/web/20261113145913/https://mempool.space/block/510048", "archive_date": "20261113145913", "archive_how": "saved"}, "btc-512480": {"kind": "primary", "title": "mempool.space, Bitcoin block 512,480 (header time 2018-03-07 20:05:31 UTC)", "url": "https://mempool.space/block/512480", "archive_url": "https://web.archive.org/web/20261113150029/https://mempool.space/block/512480", "archive_date": "20261113150029", "archive_how": "saved"}, "btc-515000": {"kind": "primary", "title": "mempool.space, Bitcoin block 515,000 (header time 2018-03-24 19:52:57 UTC)", "url": "https://mempool.space/block/515000", "archive_url": "https://web.archive.org/web/20261113150144/https://mempool.space/block/515000", "archive_date": "20261113150144", "archive_how": "saved"}, "btc-515350": {"kind": "primary", "title": "mempool.space, Bitcoin block 515,350 (header time 2018-03-27 05:46:52 UTC)", "url": "https://mempool.space/block/515350", "archive_url": "https://web.archive.org/web/20261113150228/https://mempool.space/block/515350", "archive_date": "20261113150228", "archive_how": "saved"}, "btc-520419": {"kind": "primary", "title": "mempool.space, Bitcoin block 520,419 (header time 2018-04-29 10:43:10 UTC)", "url": "https://mempool.space/block/520419", "archive_url": "https://web.archive.org/web/20261113150645/https://mempool.space/block/520419", "archive_date": "20261113150645", "archive_how": "saved"}, "btc-523118": {"kind": "primary", "title": "mempool.space, Bitcoin block 523,118 (header time 2018-05-17 12:48:14 UTC)", "url": "https://mempool.space/block/523118", "archive_url": "https://web.archive.org/web/20261113150733/https://mempool.space/block/523118", "archive_date": "20261113150733", "archive_how": "saved"}, "btc-531650": {"kind": "primary", "title": "mempool.space, Bitcoin block 531,650 (header time 2018-07-12 19:03:53 UTC)", "url": "https://mempool.space/block/531650", "archive_url": "https://web.archive.org/web/20261113150917/https://mempool.space/block/531650", "archive_date": "20261113150917", "archive_how": "saved"}, "btc-537746": {"kind": "primary", "title": "mempool.space, Bitcoin block 537,746 (header time 2018-08-21 03:56:27 UTC)", "url": "https://mempool.space/block/537746", "archive_url": "https://web.archive.org/web/20261113151035/https://mempool.space/block/537746", "archive_date": "20261113151035", "archive_how": "saved"}, "btc-540870": {"kind": "primary", "title": "mempool.space, Bitcoin block 540,870 (header time 2018-09-11 00:59:09 UTC)", "url": "https://mempool.space/block/540870", "archive_url": "https://web.archive.org/web/20261113154428/https://mempool.space/block/540870", "archive_date": "20261113154428", "archive_how": "saved"}, "btc-551000": {"kind": "primary", "title": "mempool.space, Bitcoin block 551,000 (header time 2018-11-21 23:50:39 UTC)", "url": "https://mempool.space/block/551000", "archive_url": "https://web.archive.org/web/20261113151321/https://mempool.space/block/551000", "archive_date": "20261113151321", "archive_how": "saved"}, "xap-ann": {"kind": "primary", "title": "Parodium (bounty manager), “[ANN] Bitcoin Air … World's First Multi Blockchain Fork”, Bitcointalk topic 5044039 (4 Oct 2018)", "url": "https://bitcointalk.org/index.php?topic=5044039.0", "archive_url": "https://web.archive.org/web/20260214061723/https://bitcointalk.org/index.php?topic=5044039.0", "archive_date": "20260214061723", "archive_how": "existing"}, "btcv-ann": {"kind": "primary", "title": "BLVCK, “[ANN] BTC BLVCK [BTCV] CryptoNote ALGO - BTC Fork 1:1+10% ACO”, Bitcointalk topic 2660394 (28 Dec 2017)", "url": "https://bitcointalk.org/index.php?topic=2660394", "archive_url": "https://web.archive.org/web/20261113141203/https://bitcointalk.org/index.php?topic=2660394", "archive_date": "20261113141203", "archive_how": "saved"}, "bcs-class-ann": {"kind": "primary", "title": "bitcoin.class, “[ANN] Bitcoin Class - Fork 1:1 of Bitcoin Cash”, Bitcointalk topic 3384409 (24 Apr 2018)", "url": "https://bitcointalk.org/index.php?topic=3384409.0", "archive_url": "https://web.archive.org/web/20230415085045/https://bitcointalk.org/index.php?topic=3384409.0", "archive_date": "20230415085045", "archive_how": "existing"}, "btcc-ann": {"kind": "primary", "title": "BTCCore, “[ANN] Bitcoin Core [BTCC] | The return to the Core values of Bitcoin.”, Bitcointalk topic 4354609 (29 May 2018)", "url": "https://bitcointalk.org/index.php?topic=4354609.0", "archive_url": "https://web.archive.org/web/20221205111336/https://bitcointalk.org/index.php?topic=4354609.0", "archive_date": "20221205111336", "archive_how": "existing"}, "btd-dao-ann": {"kind": "primary", "title": "daomanager, “[PRE-ANN] [AIRDROP] BITCOIN DAO - GET MASTERNODES FREE!”, Bitcointalk topic 3585668 (6 May 2018)", "url": "https://bitcointalk.org/index.php?topic=3585668", "archive_url": "https://web.archive.org/web/20250828141550/https://bitcointalk.org/index.php?topic=3585668", "archive_date": "20250828141550", "archive_how": "existing"}, "btd-dollar-ann": {"kind": "primary", "title": "bitcoin.dollar, “[ANN] Bitcoin Dollar - 1:1 Bitcoin Fork : Artificial intelligence Bitcoin”, Bitcointalk topic 2803979 (22 Jan 2018)", "url": "https://bitcointalk.org/index.php?topic=2803979.0", "archive_url": "https://web.archive.org/web/20221221052836/https://bitcointalk.org/index.php?topic=2803979.0", "archive_date": "20221221052836", "archive_how": "existing"}, "bec-allcoin": {"kind": "secondary", "title": "celine_allcoin (Allcoin exchange), “Bitcoin ECO (BEC) Will be Listed on Allcoin”, Bitcointalk topic 2697845 (6 Jan 2018)", "url": "https://bitcointalk.org/index.php?topic=2697845.0", "archive_url": "https://web.archive.org/web/20261113141510/https://bitcointalk.org/index.php?topic=2697845.0", "archive_date": "20261113141510", "archive_how": "saved"}, "bthol-ann": {"kind": "primary", "title": "isreallybitcoin, “[New Bitcoin Fork][Announcement] Bitcoin Holocaust”, Bitcointalk topic 2469155 (27 Nov 2017)", "url": "https://bitcointalk.org/index.php?topic=2469155.0", "archive_url": "https://web.archive.org/web/20250622113707/https://bitcointalk.org/index.php?topic=2469155.0", "archive_date": "20250622113707", "archive_how": "existing"}, "btl-ann": {"kind": "primary", "title": "BitcoinLambo, “[ANN][BTL] Bitcoin LAMBO | POW| PSD”, Bitcointalk topic 4329759 (28 May 2018)", "url": "https://bitcointalk.org/index.php?topic=4329759", "archive_url": "https://web.archive.org/web/20220922051748/https://bitcointalk.org/index.php?topic=4329759", "archive_date": "20220922051748", "archive_how": "existing"}, "bcm-ann": {"kind": "primary", "title": "PeerMine, “[ANN][FORK] BitcoinMaster (BCM) - Bitcoin faster - Fork at block 515000 1:1”, Bitcointalk topic 3174577 (21 Mar 2018)", "url": "https://bitcointalk.org/index.php?topic=3174577.0", "archive_url": "https://web.archive.org/web/20230416035321/https://bitcointalk.org/index.php?topic=3174577.0", "archive_date": "20230416035321", "archive_how": "existing"}, "btcm-ann": {"kind": "primary", "title": "bitcoinmetalbtcm, “[ANN] [BTCM] BitcoinMetal: Safe, Reliable and Fast Bitcoin Blockchain hardfork”, Bitcointalk topic 3242627 (2 Apr 2018)", "url": "https://bitcointalk.org/index.php?topic=3242627", "archive_url": "https://web.archive.org/web/20220621221258/https://bitcointalk.org/index.php?topic=3242627", "archive_date": "20220621221258", "archive_how": "existing"}, "ocho-ann": {"kind": "primary", "title": "goku1997, “[ANN] [OCHO] Bitcoin Ocho aka The Future [OCHO] NOW MINING”, Bitcointalk topic 1712184 (12 Dec 2016)", "url": "https://bitcointalk.org/index.php?topic=1712184.0", "archive_url": "https://web.archive.org/web/20250821134544/https://bitcointalk.org/index.php?topic=1712184.0", "archive_date": "20250821134544", "archive_how": "existing"}, "pieta-ann": {"kind": "primary", "title": "frankbeli, “BITCOIN PIETA”, Bitcointalk topic 2678772 (2 Jan 2018)", "url": "https://bitcointalk.org/index.php?topic=2678772.0", "archive_url": "https://web.archive.org/web/20261113141333/https://bitcointalk.org/index.php?topic=2678772.0", "archive_date": "20261113141333", "archive_how": "saved"}, "point-ann": {"kind": "primary", "title": "bitcoinpoint, “[ANN] Bitcoin Point - Fork 1:1 of Bitcoin”, Bitcointalk topic 2624373 (21 Dec 2017)", "url": "https://bitcointalk.org/index.php?topic=2624373.0", "archive_url": "https://web.archive.org/web/20200730230633/https://bitcointalk.org/index.php?topic=2624373.0", "archive_date": "20200730230633", "archive_how": "existing"}, "btpro-ann": {"kind": "primary", "title": "BitcoinPRO.Team, “[ANN] BitcoinPRO (BTP) - SHA256 POW + POS [ Bounties Available ] Free Airdrop”, Bitcointalk topic 2836500 (28 Jan 2018)", "url": "https://bitcointalk.org/index.php?topic=2836500.0", "archive_url": "https://web.archive.org/web/20250818094032/https://bitcointalk.org/index.php?topic=2836500.0", "archive_date": "20250818094032", "archive_how": "existing"}, "bcrm-ann": {"kind": "primary", "title": "BitcoinRM, “[ANN] [BCRM] Bitcoin RM”, Bitcointalk topic 4735005 (24 Jul 2018; first post last edited 19 Feb 2021)", "url": "https://bitcointalk.org/index.php?topic=4735005.0", "archive_url": "https://web.archive.org/web/20250613172711/https://bitcointalk.org/index.php?topic=4735005.0", "archive_date": "20250613172711", "archive_how": "existing"}, "sudu-ann": {"kind": "primary", "title": "Bitcoin__Sudu, “Bitcoin Sudu: Fast & Fully Anonymous Bitcoin Fork”, Bitcointalk topic 2535861 (6 Dec 2017)", "url": "https://bitcointalk.org/index.php?topic=2535861.0", "archive_url": "https://web.archive.org/web/20261113141111/https://bitcointalk.org/index.php?topic=2535861.0", "archive_date": "20261113141111", "archive_how": "saved"}, "bcbc-thread": {"kind": "primary", "title": "Buzaath, Bitcointalk topic 3109563, forkdrop's announcement link for Bitcoin@CBC (opened 12 Mar 2018; now titled “[CLOSED]: unnamed coin”)", "url": "https://bitcointalk.org/index.php?topic=3109563.0", "archive_url": "https://web.archive.org/web/20230415170618/https://bitcointalk.org/index.php?topic=3109563.0", "archive_date": "20230415170618", "archive_how": "existing"}, "bti-ann": {"kind": "primary", "title": "Bitcoin Ti, “[ANN] Bitcoin Ti : Think In Bitcoin”, Bitcointalk topic 2591037 (15 Dec 2017)", "url": "https://bitcointalk.org/index.php?topic=2591037.0", "archive_url": "https://web.archive.org/web/20261113141136/https://bitcointalk.org/index.php?topic=2591037.0", "archive_date": "20261113141136", "archive_how": "saved"}, "qed-ann": {"kind": "primary", "title": "Bill White, “[PRE-ANN] Qeditas: A Formal Library as a Bitcoin Spin-Off”, Bitcointalk topic 998559 (21 Mar 2015)", "url": "https://bitcointalk.org/index.php?topic=998559.0", "archive_url": "https://web.archive.org/web/20260311171046/https://bitcointalk.org/index.php?topic=998559.0", "archive_date": "20260311171046", "archive_how": "existing"}, "sem-ann": {"kind": "primary", "title": "semux, “[ANN][SEM] Semux - Official Thread”, Bitcointalk topic 2159012 (7 Sep 2017; first post last edited 30 Aug 2019)", "url": "https://bitcointalk.org/index.php?topic=2159012.0", "archive_url": "https://web.archive.org/web/20260210103149/https://bitcointalk.org/index.php?topic=2159012.0", "archive_date": "20260210103149", "archive_how": "existing"}, "xnn-ann": {"kind": "primary", "title": "WhyMe126, “[ANN][AIRDROP] XNN - XENON - Massively Distributed EOS Alt-chain”, Bitcointalk topic 2209559 (26 Sep 2017)", "url": "https://bitcointalk.org/index.php?topic=2209559", "archive_url": "https://web.archive.org/web/20251211204247/https://bitcointalk.org/index.php?topic=2209559", "archive_date": "20251211204247", "archive_how": "existing"}, "bicc-readme": {"kind": "primary", "title": "BitClassic Coin README, GitHub bitunity/BitClassicCoin-BICC", "url": "https://github.com/bitunity/BitClassicCoin-BICC", "archive_url": "https://web.archive.org/web/20251220022600/https://github.com/bitunity/BitClassicCoin-BICC", "archive_date": "20251220022600", "archive_how": "existing"}, "btcc-readme": {"kind": "primary", "title": "Bitcoin Core Squared (BTCC) README, GitHub bitcoin-cored/bitcoin-cored", "url": "https://github.com/bitcoin-cored/bitcoin-cored", "archive_url": "https://web.archive.org/web/20200927010132/https://github.com/bitcoin-cored/bitcoin-cored", "archive_date": "20200927010132", "archive_how": "existing"}, "btn-readme": {"kind": "primary", "title": "Bitcoin New README, GitHub bitcoin-new/bitcoin-new", "url": "https://github.com/bitcoin-new/bitcoin-new", "archive_url": "https://web.archive.org/web/20201127091700/https://github.com/bitcoin-new/bitcoin-new", "archive_date": "20201127091700", "archive_how": "existing"}, "ocho-readme": {"kind": "primary", "title": "Bitcoin Ocho README, GitHub goku1997/bitcoin", "url": "https://github.com/goku1997/bitcoin", "archive_url": "https://web.archive.org/web/20250821142930/https://github.com/goku1997/bitcoin", "archive_date": "20250821142930", "archive_how": "existing"}, "btpro-readme": {"kind": "primary", "title": "BitcoinPRO README, GitHub BitcoinPROTeam/BitcoinPRO", "url": "https://github.com/BitcoinPROTeam/BitcoinPRO", "archive_url": "https://web.archive.org/web/20250823181845/https://github.com/BitcoinPROTeam/BitcoinPRO/", "archive_date": "20250823181845", "archive_how": "existing"}, "bcrm-readme": {"kind": "primary", "title": "Bitcoin RM README, GitHub BitcoinRM/BCRM", "url": "https://github.com/BitcoinRM/BCRM", "archive_url": "https://web.archive.org/web/20260507220639/https://github.com/BitcoinRM/BCRM", "archive_date": "20260507220639", "archive_how": "existing"}, "bsh-readme": {"kind": "primary", "title": "Bitcoin Stash README, GitHub bstash/BitcoinStash", "url": "https://github.com/bstash/BitcoinStash", "archive_url": "https://web.archive.org/web/20250810231629/https://github.com/bstash/BitcoinStash", "archive_date": "20250810231629", "archive_how": "existing"}, "bti-readme": {"kind": "primary", "title": "Bitcoin Ti README, GitHub BTCTI/btcti", "url": "https://github.com/BTCTI/btcti", "archive_url": "https://web.archive.org/web/20201106101239/https://github.com/btcti/btcti", "archive_date": "20201106101239", "archive_how": "existing"}, "cer-readme": {"kind": "primary", "title": "Cereneum README, GitHub Cereneum/Cereneum", "url": "https://github.com/Cereneum/Cereneum", "archive_url": "https://web.archive.org/web/20230116194226/https://github.com/Cereneum/Cereneum", "archive_date": "20230116194226", "archive_how": "existing"}, "dlc-readme": {"kind": "primary", "title": "Dalilcoin README, GitHub aliibrahim80/dalilcoin", "url": "https://github.com/aliibrahim80/dalilcoin", "archive_url": "https://web.archive.org/web/20251226172637/https://github.com/aliibrahim80/dalilcoin", "archive_date": "20251226172637", "archive_how": "existing"}, "obtc-readme": {"kind": "primary", "title": "OilBitCoin README, GitHub oilbtc2017/oilbtc", "url": "https://github.com/oilbtc2017/oilbtc", "archive_url": "https://web.archive.org/web/20261113143358/https://github.com/oilbtc2017/oilbtc", "archive_date": "20261113143358", "archive_how": "saved"}, "anon-readme": {"kind": "primary", "title": "ANON README, GitHub anonymousbitcoin/anon", "url": "https://github.com/anonymousbitcoin/anon", "archive_url": "https://web.archive.org/web/20250403003902/https://github.com/anonymousbitcoin/anon", "archive_date": "20250403003902", "archive_how": "existing"}, "bclc-readme": {"kind": "primary", "title": "BitcoinCloud README, GitHub bitcoincloudcore/BitcoinCloud", "url": "https://github.com/bitcoincloudcore/BitcoinCloud", "archive_url": "https://web.archive.org/web/20220621221312/https://github.com/bitcoincloudcore/BitcoinCloud", "archive_date": "20220621221312", "archive_how": "existing"}, "btl-readme": {"kind": "primary", "title": "BitcoinLambo README, GitHub btclambo/BitcoinLambo", "url": "https://github.com/btclambo/BitcoinLambo", "archive_url": "https://web.archive.org/web/20250823233646/https://github.com/btclambo/BitcoinLambo", "archive_date": "20250823233646", "archive_how": "existing"}, "fox-readme": {"kind": "primary", "title": "FBTC README, GitHub fbtc1/FBTC", "url": "https://github.com/fbtc1/FBTC", "archive_url": "https://web.archive.org/web/20220621221319/https://github.com/fbtc1/FBTC", "archive_date": "20220621221319", "archive_how": "existing"}, "bcb-readme": {"kind": "primary", "title": "Bitcoin Boy README, GitHub bitcoinboy/bitcoinboy", "url": "https://github.com/bitcoinboy/bitcoinboy", "archive_url": "https://web.archive.org/web/20201013001725/https://github.com/bitcoinboy/bitcoinboy", "archive_date": "20201013001725", "archive_how": "existing"}, "bthol-readme": {"kind": "primary", "title": "README of GitHub isreallybitcoin/bitcoin (forkdrop's Bitcoin Holocaust repository)", "url": "https://github.com/isreallybitcoin/bitcoin", "archive_url": "https://web.archive.org/web/20220621221345/https://github.com/isreallybitcoin/bitcoin", "archive_date": "20220621221345", "archive_how": "existing"}, "anon-site": {"kind": "primary", "title": "ANON website, anonfork.io (Wayback Machine copy, 25 Aug 2018)", "url": "https://web.archive.org/web/20180825130327/http://www.anonfork.io:80/", "archive_url": "https://web.archive.org/web/20180825130327/http://www.anonfork.io:80/", "archive_date": "20180825130327", "archive_how": "already-wayback"}, "bta-site": {"kind": "primary", "title": "Bitcoin ALL (比特币荣耀) website, bitcoinall.org (Chinese; Wayback Machine copy, 27 Mar 2018)", "url": "https://web.archive.org/web/20180327181813/http://bitcoinall.org:80/", "archive_url": "https://web.archive.org/web/20180327181813/http://bitcoinall.org:80/", "archive_date": "20180327181813", "archive_how": "already-wayback"}, "bicc-site": {"kind": "primary", "title": "Bitclassic Coin website, bicc.io/en (Wayback Machine copy, 27 Mar 2018)", "url": "https://web.archive.org/web/20180327064828/http://www.bicc.io:80/en", "archive_url": "https://web.archive.org/web/20180327064828/http://www.bicc.io:80/en", "archive_date": "20180327064828", "archive_how": "already-wayback"}, "bite-site": {"kind": "primary", "title": "BitEthereum website, bitethereum.io (Chinese; Wayback Machine copy, 30 Aug 2018)", "url": "https://web.archive.org/web/20180830224130/https://www.bitethereum.io/", "archive_url": "https://web.archive.org/web/20180830224130/https://www.bitethereum.io/", "archive_date": "20180830224130", "archive_how": "already-wayback"}, "bcb-site": {"kind": "primary", "title": "Bitcoin Boy website, bitcoinboy.org (Wayback Machine copy, 8 Apr 2018)", "url": "https://web.archive.org/web/20180408110716/http://www.bitcoinboy.org:80/", "archive_url": "https://web.archive.org/web/20180408110716/http://www.bitcoinboy.org:80/", "archive_date": "20180408110716", "archive_how": "already-wayback"}, "bclc-site": {"kind": "primary", "title": "Bitcoin Cloud website, bitcoincloud.cash (Wayback Machine copy, 14 Aug 2018)", "url": "https://web.archive.org/web/20180814060018/https://bitcoincloud.cash/", "archive_url": "https://web.archive.org/web/20180814060018/https://bitcoincloud.cash/", "archive_date": "20180814060018", "archive_how": "already-wayback"}, "btco-site": {"kind": "primary", "title": "Bitcoin Coral website, bitcoincoral.com (Wayback Machine copy, 17 Dec 2017)", "url": "https://web.archive.org/web/20171217100726/http://www.bitcoincoral.com:80/", "archive_url": "https://web.archive.org/web/20171217100726/http://www.bitcoincoral.com:80/", "archive_date": "20171217100726", "archive_how": "already-wayback"}, "bec-site": {"kind": "primary", "title": "Bitcoin Eco website, biteco.io (Wayback Machine copy, 26 Mar 2018)", "url": "https://web.archive.org/web/20180326105216/http://biteco.io:80/", "archive_url": "https://web.archive.org/web/20180326105216/http://biteco.io:80/", "archive_date": "20180326105216", "archive_how": "already-wayback"}, "lunar-site": {"kind": "primary", "title": "Bitcoin Lunar website, bitcoinlunar.org (Wayback Machine copy, 4 Apr 2018)", "url": "https://web.archive.org/web/20180404233617/http://www.bitcoinlunar.org:80/", "archive_url": "https://web.archive.org/web/20180404233617/http://www.bitcoinlunar.org:80/", "archive_date": "20180404233617", "archive_how": "already-wayback"}, "origin-site": {"kind": "primary", "title": "Bitcoin Origin website, bitcoinorigin.io (Wayback Machine copy, 4 May 2018)", "url": "https://web.archive.org/web/20180504222505/https://bitcoinorigin.io/", "archive_url": "https://web.archive.org/web/20180504222505/https://bitcoinorigin.io/", "archive_date": "20180504222505", "archive_how": "already-wayback"}, "bcp-site": {"kind": "primary", "title": "Bitcoin Parallel website, bitcoinparallel.org (Wayback Machine copy, 30 Aug 2018)", "url": "https://web.archive.org/web/20180830194922/https://www.bitcoinparallel.org/", "archive_url": "https://web.archive.org/web/20180830194922/https://www.bitcoinparallel.org/", "archive_date": "20180830194922", "archive_how": "already-wayback"}, "bcp-medium": {"kind": "primary", "title": "The Bitcoin Parallel Foundation, “Hello, everyone.”, Medium (12 Feb 2018)", "url": "https://medium.com/@bitcoinparallel/hello-everyone-d696a7b88311", "archive_url": "https://web.archive.org/web/20191111203348/https://medium.com/@bitcoinparallel/hello-everyone-d696a7b88311", "archive_date": "20191111203348", "archive_how": "existing"}, "prime-site": {"kind": "primary", "title": "bitcoinprime.org (Wayback Machine copy, 7 Mar 2018)", "url": "https://web.archive.org/web/20180307022436/http://bitcoinprime.org/", "archive_url": "https://web.archive.org/web/20180307022436/http://bitcoinprime.org/", "archive_date": "20180307022436", "archive_how": "already-wayback"}, "reco-site": {"kind": "primary", "title": "bitcoinreferenceline.com (Wayback Machine copy, 16 Nov 2019)", "url": "https://web.archive.org/web/20191116215417/https://bitcoinreferenceline.com/", "archive_url": "https://web.archive.org/web/20191116215417/https://bitcoinreferenceline.com/", "archive_date": "20191116215417", "archive_how": "already-wayback"}, "bcw-site": {"kind": "primary", "title": "Bitcoin Wonder website, bitcoinwonder.io (Wayback Machine copy, 5 Apr 2018)", "url": "https://web.archive.org/web/20180405011136/http://www.bitcoinwonder.io:80/", "archive_url": "https://web.archive.org/web/20180405011136/http://www.bitcoinwonder.io:80/", "archive_date": "20180405011136", "archive_how": "already-wayback"}, "x2-site": {"kind": "primary", "title": "BTCX2 website, btcx2.com (Wayback Machine copy, 26 Apr 2018)", "url": "https://web.archive.org/web/20180426233638/http://btcx2.com:80/", "archive_url": "https://web.archive.org/web/20180426233638/http://btcx2.com:80/", "archive_date": "20180426233638", "archive_how": "already-wayback"}, "fox-site": {"kind": "primary", "title": "Fox BTC website, foxbtc.io (Wayback Machine copy, 11 Aug 2018)", "url": "https://web.archive.org/web/20180811034218/https://foxbtc.io/", "archive_url": "https://web.archive.org/web/20180811034218/https://foxbtc.io/", "archive_date": "20180811034218", "archive_how": "already-wayback"}, "fox-pr": {"kind": "primary", "title": "“FOXBTC announce hard fork to commence in April”, Bitcoin PR Buzz (Wayback Machine copy, 21 Apr 2018)", "url": "https://web.archive.org/web/20180421061018/http://bitcoinprbuzz.com:80/foxbtc-announce-hard-fork-commence-april/", "archive_url": "https://web.archive.org/web/20180421061018/http://bitcoinprbuzz.com:80/foxbtc-announce-hard-fork-commence-april/", "archive_date": "20180421061018", "archive_how": "already-wayback"}, "xap-site": {"kind": "primary", "title": "Bitcoin Air website, bitcoinair.org (Wayback Machine copy, 27 Oct 2018)", "url": "https://web.archive.org/web/20181027225143/https://bitcoinair.org/", "archive_url": "https://web.archive.org/web/20181027225143/https://bitcoinair.org/", "archive_date": "20181027225143", "archive_how": "already-wayback"}, "cer-site": {"kind": "primary", "title": "Cereneum website, cereneum.com (Wayback Machine copy, 9 May 2019)", "url": "https://web.archive.org/web/20190509213251/https://www.cereneum.com/", "archive_url": "https://web.archive.org/web/20190509213251/https://www.cereneum.com/", "archive_date": "20190509213251", "archive_how": "already-wayback"}, "oil-bw": {"kind": "primary", "title": "Bitcoin Oil, “Bitcoin Oil Announces Its Intentions To Go Green And Solve Bitcoin's Energy Consumption Problems”, Business Wire press release (4 Feb 2019; Wayback Machine copy)", "url": "https://web.archive.org/web/20190820212741/https://www.businesswire.com/news/home/20190204005243/en/Bitcoin-Oil-Announces-Intentions-Green-Solve-Bitcoins", "archive_url": "https://web.archive.org/web/20190820212741/https://www.businesswire.com/news/home/20190204005243/en/Bitcoin-Oil-Announces-Intentions-Green-Solve-Bitcoins", "archive_date": "20190820212741", "archive_how": "already-wayback"}, "ep-s16e30-q5577": {"kind": "episode", "title": "S16 E30: Peter Rizun on the timing of the Bitcoin Cash fork", "url": "https://bitcoin-takeover.com/audio/media/2025-06-14_s16_e30_peter_rizun_on_scaling_bitcoin_with_hardware_-_14.06.2025_16.39.mp3", "t": 5577, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113152704/https://bitcoin-takeover.com/episodes/s16-e30-peter-rizun-on-scaling-bitcoin-with-hardware/", "archive_date": "20261113152704", "archive_how": "saved", "archive_of": "episode page"}, "ep-s15e26-q639": {"kind": "episode", "title": "S15 E26: Roger Ver on why Bitcoin Cash exists", "url": "https://bitcoin-takeover.com/audio/media/2024-03-28_s15_e26_roger_ver_on_bitcoin.mp3", "t": 639, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113151839/https://bitcoin-takeover.com/s15-e26-roger-ver-on-hijacking-bitcoin-freedom-maximalism/", "archive_date": "20261113151839", "archive_how": "saved", "archive_of": "episode page"}, "ep-s17e44-q1104": {"kind": "episode", "title": "S17 E44: Marc De Mesel on Bitcoin Cash's record", "url": "https://bitcoin-takeover.com/audio/media/2026-09-25_s17_e44_marc_de_mesel_on_early_bitcoin_investing_polygamy.mp3", "t": 1104, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113154040/https://bitcoin-takeover.com/s17-e44-marc-de-mesel-on-the-bitcoin-cash-bet-the-privacy-coin-basket-the-price-of-conviction/", "archive_date": "20261113154040", "archive_how": "saved"}, "ep-s17e44-q496": {"kind": "episode", "title": "S17 E44: Marc De Mesel on opposing the ABC dev tax", "url": "https://bitcoin-takeover.com/audio/media/2026-09-25_s17_e44_marc_de_mesel_on_early_bitcoin_investing_polygamy.mp3", "t": 496, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113154040/https://bitcoin-takeover.com/s17-e44-marc-de-mesel-on-the-bitcoin-cash-bet-the-privacy-coin-basket-the-price-of-conviction/", "archive_date": "20261113154040", "archive_how": "saved"}, "ep-s17e35-q545": {"kind": "episode", "title": "S17 E35: Vinny Lingham on what the block size limit produced", "url": "https://bitcoin-takeover.com/audio/media/2026-08-01_s17_e35_vinny_lingham_on_bitcoin_risk_management.mp3", "t": 545, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824051816/https://bitcoin-takeover.com/audio/media/2026-08-01_s17_e35_vinny_lingham_on_bitcoin_risk_management.mp3", "archive_date": "20260824051816", "archive_how": "existing"}, "ep-s15e26-q326": {"kind": "episode", "title": "S15 E26: Roger Ver on being a freedom maximalist", "url": "https://bitcoin-takeover.com/audio/media/2024-03-28_s15_e26_roger_ver_on_bitcoin.mp3", "t": 326, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113151839/https://bitcoin-takeover.com/s15-e26-roger-ver-on-hijacking-bitcoin-freedom-maximalism/", "archive_date": "20261113151839", "archive_how": "saved", "archive_of": "episode page"}, "btk-ep-s16e11": {"kind": "episode", "title": "S16 E11: Paul Sztorc on Roger Ver", "url": "https://bitcoin-takeover.com/audio/?name=2025-03-04_s16_e11_paul_sztorc_on_roger_ver_-_03.03.2025_19.13.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2025-03-04_s16_e11_paul_sztorc_on_roger_ver_-_03.03.2025_19.13.mp3", "date": "Tue, 04 Mar 2025 12:17:00 +0200", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113152500/https://bitcoin-takeover.com/s16-e11-paul-sztorc-on-roger-ver/", "archive_date": "20261113152500", "archive_how": "saved"}, "btk-ep-s15e31": {"kind": "episode", "title": "S15 E31: Ray Youssef on NoOnes & Why Roger Ver Was Right", "url": "https://bitcoin-takeover.com/audio/?name=2024-04-16_s15_e31_ray_youssef_on_noones_why_roger_ver_was_right.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2024-04-16_s15_e31_ray_youssef_on_noones_why_roger_ver_was_right.mp3", "date": "Tue, 16 Apr 2024 05:09:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113152110/https://bitcoin-takeover.com/s15-e31-ray-youssef-on-noones-freedom-money-why-roger-ver-was-right/", "archive_date": "20261113152110", "archive_how": "saved"}, "ep-s17e43-q4397": {"kind": "episode", "title": "S17 E43: Mike Belshe on the New York Agreement", "url": "https://bitcoin-takeover.com/audio/media/2026-09-16_s17_e43_mike_belshe_on_bitgo_quantum_clarity.mp3", "t": 4397, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135601/https://bitcoin-takeover.com/s17-e43-mike-belshe-on-bitgo-quantum-clarity/", "archive_date": "20261113135601", "archive_how": "saved"}, "ep-s15e14-q1542": {"kind": "episode", "title": "S15 E14: Nicolas Dorier on opposing SegWit2x", "url": "https://bitcoin-takeover.com/audio/media/2023-12-31_s15_e14_nicolas_dorier_on_btcpay__nbitcoin__tumblebit__coding_bitcoin_in_c.mp3", "t": 1542, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824033954/https://bitcoin-takeover.com/audio/media/2023-12-31_s15_e14_nicolas_dorier_on_btcpay__nbitcoin__tumblebit__coding_bitcoin_in_c.mp3", "archive_date": "20260824033954", "archive_how": "existing"}, "ep-s15e14-q1752": {"kind": "episode", "title": "S15 E14: Nicolas Dorier on who backed SegWit2x", "url": "https://bitcoin-takeover.com/audio/media/2023-12-31_s15_e14_nicolas_dorier_on_btcpay__nbitcoin__tumblebit__coding_bitcoin_in_c.mp3", "t": 1752, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824033954/https://bitcoin-takeover.com/audio/media/2023-12-31_s15_e14_nicolas_dorier_on_btcpay__nbitcoin__tumblebit__coding_bitcoin_in_c.mp3", "archive_date": "20260824033954", "archive_how": "existing"}, "ep-s15e50-q5772": {"kind": "episode", "title": "S15 E50: Murch on what the UASF did", "url": "https://bitcoin-takeover.com/audio/media/2024-08-16_s15_e50__murch_on_bitcoin_popular_myths.mp3", "t": 5772, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260829161201/https://bitcoin-takeover.com/audio/media/2024-08-16_s15_e50__murch_on_bitcoin_popular_myths.mp3", "archive_date": "20260829161201", "archive_how": "existing"}, "ep-s15e39-q3349": {"kind": "episode", "title": "S15 E39: Pete Rizzo on the economic majority", "url": "https://bitcoin-takeover.com/audio/media/2024-05-30_s15_e39_pete_rizzo_on_bitcoin_history_culture.mp3", "t": 3349, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824044912/https://bitcoin-takeover.com/audio/media/2024-05-30_s15_e39_pete_rizzo_on_bitcoin_history_culture.mp3", "archive_date": "20260824044912", "archive_how": "existing"}, "ep-s16e42-q2435": {"kind": "episode", "title": "S16 E42: Michael Tidwell on the size of the Knots diff", "url": "https://bitcoin-takeover.com/audio/media/2025-09-09_s16_e42_michael_tidwell_on_bitcoin_drama_tabconf.mp3", "t": 2435, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824040949/https://bitcoin-takeover.com/audio/media/2025-09-09_s16_e42_michael_tidwell_on_bitcoin_drama_tabconf.mp3", "archive_date": "20260824040949", "archive_how": "existing"}, "ep-s17e21-q190": {"kind": "episode", "title": "S17 E21: Paul Sztorc on activating drivechains on eCash", "url": "https://bitcoin-takeover.com/audio/media/2026-04-24_s17_e21_paul_sztorc_on_launching_drivechains_on_ecash_in_2026_-_22.04.2026_02.17.mp3", "t": 190, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153228/https://bitcoin-takeover.com/s17-e21-paul-sztorc-hard-forks-bitcoin-to-launch-ecash-with-drivechains/", "archive_date": "20261113153228", "archive_how": "saved", "archive_of": "episode page"}, "btk-ep-s9e4": {"kind": "episode", "title": "S9 E4: Paul Sztorc on the Philosophy of BIP 300 & Prediction Markets", "url": "https://bitcoin-takeover.com/audio/?name=2021-07-05_btctkvr_s9_e4_paul_sztorc_on_drive_chains_and_prediction_markets_final.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2021-07-05_btctkvr_s9_e4_paul_sztorc_on_drive_chains_and_prediction_markets_final.mp3", "date": "Mon, 05 Jul 2021 17:18:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20250423050622/https://bitcoin-takeover.com/audio/?name=2021-07-05_btctkvr_s9_e4_paul_sztorc_on_drive_chains_and_prediction_markets_final.mp3", "archive_date": "20250423050622", "archive_how": "existing"}, "btk-ep-s14e10": {"kind": "episode", "title": "S14 E10: Paul Sztorc on Drivechains & Attacking Bitcoin", "url": "https://bitcoin-takeover.com/audio/?name=2023-08-31_s14_e10_paul_sztorc_on_drivechains__attacking_bitcoin_final.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2023-08-31_s14_e10_paul_sztorc_on_drivechains__attacking_bitcoin_final.mp3", "date": "Thu, 31 Aug 2023 00:12:33 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20240807101322/https://bitcoin-takeover.com/audio/?name=2023-08-31_s14_e10_paul_sztorc_on_drivechains__attacking_bitcoin_final.mp3", "archive_date": "20240807101322", "archive_how": "existing"}, "btk-ep-s14e13": {"kind": "episode", "title": "S14 E13: Paul Sztorc Reacts to Drivechains Reactions", "url": "https://bitcoin-takeover.com/audio/?name=2023-09-20_s14_e13_paul_sztorc_reacts_on_drivechains_reactions.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2023-09-20_s14_e13_paul_sztorc_reacts_on_drivechains_reactions.mp3", "date": "Wed, 20 Sep 2023 04:40:50 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20251110040649/https://bitcoin-takeover.com/audio/?name=2023-09-20_s14_e13_paul_sztorc_reacts_on_drivechains_reactions.mp3", "archive_date": "20251110040649", "archive_how": "existing"}, "btk-ep-s15e16": {"kind": "episode", "title": "S15 E16: Paul Sztorc Talks Bitcoin Scaling, But Can't Say Drivechains", "url": "https://bitcoin-takeover.com/audio/?name=2024-01-20_s15_e16__paul_sztorc_talks_bitcoin_scaling__but_cant_say_drivechains.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2024-01-20_s15_e16__paul_sztorc_talks_bitcoin_scaling__but_cant_say_drivechains.mp3", "date": "Sat, 20 Jan 2024 03:06:00 +0200", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113151753/https://bitcoin-takeover.com/s15-e16-paul-sztorc-talks-bitcoin-scaling-but-cant-say-drivechains/", "archive_date": "20261113151753", "archive_how": "saved"}, "btk-ep-s15e68": {"kind": "episode", "title": "S15 E68: Paul Sztorc on Activating Drivechains via CUSF (Core Untouched Soft Fork)", "url": "https://bitcoin-takeover.com/audio/?name=2024-12-10_s15_e68_paul_sztorc_on_activating_drivechains_without_a_soft_fork_cusf_-_09.12.2024_21.07.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2024-12-10_s15_e68_paul_sztorc_on_activating_drivechains_without_a_soft_fork_cusf_-_09.12.2024_21.07.mp3", "date": "Tue, 10 Dec 2024 00:36:00 +0200", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113152327/https://bitcoin-takeover.com/episodes/s15-e68-paul-sztorc-on-activating-drivechains-via-cusf-core-untouched-soft-fork/", "archive_date": "20261113152327", "archive_how": "saved"}, "ep-s17e14-q4233": {"kind": "episode", "title": "S17 E14: Kristian Csepcsar on Bitmain's market position", "url": "https://bitcoin-takeover.com/audio/media/2026-03-20_s17_e14_kristian_czepczar_on_braiins_the_history_of_bitcoin_mining_final.mp3", "t": 4233, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824031718/https://bitcoin-takeover.com/audio/media/2026-03-20_s17_e14_kristian_czepczar_on_braiins_the_history_of_bitcoin_mining_final.mp3", "archive_date": "20260824031718", "archive_how": "existing"}, "ep-s16e23-q334": {"kind": "episode", "title": "S16 E23: James O'Beirne on CTV and MEV", "url": "https://bitcoin-takeover.com/audio/media/2025-05-01_s16_e23_james_o_beirne_on_developing_bitcoin_-_30.04.2025_21.52.mp3", "t": 334, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824052804/https://bitcoin-takeover.com/audio/media/2025-05-01_s16_e23_james_o_beirne_on_developing_bitcoin_-_30.04.2025_21.52.mp3", "archive_date": "20260824052804", "archive_how": "existing"}, "ep-s16e28-q2624": {"kind": "episode", "title": "S16 E28: Charles Chong on merged mining", "url": "https://bitcoin-takeover.com/audio/media/2025-05-31_s16_e28_proof_of_work_alliance_with_charles_chong_summer_meng_spencer_yang_-_31.05.2025_12.57.mp3", "t": 2624, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824042051/https://bitcoin-takeover.com/audio/media/2025-05-31_s16_e28_proof_of_work_alliance_with_charles_chong_summer_meng_spencer_yang_-_31.05.2025_12.57.mp3", "archive_date": "20260824042051", "archive_how": "existing"}, "ep-s15e51-q602": {"kind": "episode", "title": "S15 E51: Mike Carson on Namecoin and Spaces", "url": "https://bitcoin-takeover.com/audio/media/2024-08-22_s15_e51__mike_carson_on_impervious_spaces_domains_on_bitcoin.mp3", "t": 602, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824032952/https://bitcoin-takeover.com/audio/media/2024-08-22_s15_e51__mike_carson_on_impervious_spaces_domains_on_bitcoin.mp3", "archive_date": "20260824032952", "archive_how": "existing"}, "ep-s1e1-q5723": {"kind": "episode", "title": "S1 E1: Donald McIntyre on Ethereum Classic", "url": "https://bitcoin-takeover.com/audio/media/2026-08-25_s1_e1_donald_mcintyre_on_bitcoin_the_teachings_of_tim_may_and_nick_szabo_and_the_history_of_money_remastered_2026_-_25_08_2026_10-39.mp3", "t": 5723, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113153954/https://bitcoin-takeover.com/remembering-donald-mcintyre-s1-e1-remaster-on-bitcoin-tim-may-nick-szabo-and-the-history-of-money/", "archive_date": "20261113153954", "archive_how": "saved"}, "ep-s17e39-q2900": {"kind": "episode", "title": "S17 E39: Kurt Wuckert Jr. on the DDoS attacks on XT nodes", "url": "https://bitcoin-takeover.com/audio/media/2026-08-23_s17_e39_kurt_wuckert_jr._on_bsv_big_block_bitcoin.mp3", "t": 2900, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20261113135410/https://bitcoin-takeover.com/s17-e39-kurt-wuckert-jr-on-the-big-block-wars-bsv-craig-wright-the-road-not-taken/", "archive_date": "20261113135410", "archive_how": "saved"}, "ep-s17e10-q6954": {"kind": "episode", "title": "S17 E10: Mark Karpelès on BSV and the Mt. Gox coins", "url": "https://bitcoin-takeover.com/audio/media/2026-03-01_s16_e10_mark_karpeles_on_mt._gox_80000_bitcoins_chief_p_ssy.mp3", "t": 6954, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824043349/https://bitcoin-takeover.com/audio/media/2026-03-01_s16_e10_mark_karpeles_on_mt._gox_80000_bitcoins_chief_p_ssy.mp3", "archive_date": "20260824043349", "archive_how": "existing"}, "ep-s17e10-q6986": {"kind": "episode", "title": "S17 E10: Mark Karpelès on Craig Wright's Mt. Gox claim", "url": "https://bitcoin-takeover.com/audio/media/2026-03-01_s16_e10_mark_karpeles_on_mt._gox_80000_bitcoins_chief_p_ssy.mp3", "t": 6986, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824043349/https://bitcoin-takeover.com/audio/media/2026-03-01_s16_e10_mark_karpeles_on_mt._gox_80000_bitcoins_chief_p_ssy.mp3", "archive_date": "20260824043349", "archive_how": "existing"}, "btk-ep-s5e10": {"kind": "episode", "title": "S5 E10: Arthur van Pelt on Craig Wright", "url": "https://bitcoin-takeover.com/audio/?name=2020-07-14_s5_e10_arthur_van_pelt_on_craig_wright.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2020-07-14_s5_e10_arthur_van_pelt_on_craig_wright.mp3", "date": "Tue, 14 Jul 2020 17:00:32 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20250418141200/https://bitcoin-takeover.com/audio/?name=2020-07-14_s5_e10_arthur_van_pelt_on_craig_wright.mp3", "archive_date": "20250418141200", "archive_how": "existing"}, "ep-s16e49-q12929": {"kind": "episode", "title": "S16 E49: Vlad Costea on debating Richard Heart", "url": "https://bitcoin-takeover.com/audio/media/2025-10-10_s16_e49_jay_berg_on_bitcoin_sidepit_maximalism.mp3", "t": 12929, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824021453/https://bitcoin-takeover.com/audio/media/2025-10-10_s16_e49_jay_berg_on_bitcoin_sidepit_maximalism.mp3", "archive_date": "20260824021453", "archive_how": "existing"}, "ep-s15e34-q842": {"kind": "episode", "title": "S15 E34: Charlie Lee on MWEB", "url": "https://bitcoin-takeover.com/audio/media/2024-04-29_s15_e34_charlie_lee_on_privacy_mweb_mimble_wimble_extension_block_-_26.04.2024_23.52.mp3", "t": 842, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824032205/https://bitcoin-takeover.com/audio/media/2024-04-29_s15_e34_charlie_lee_on_privacy_mweb_mimble_wimble_extension_block_-_26.04.2024_23.52.mp3", "archive_date": "20260824032205", "archive_how": "existing"}, "ep-s15e34-q438": {"kind": "episode", "title": "S15 E34: Charlie Lee on second layers", "url": "https://bitcoin-takeover.com/audio/media/2024-04-29_s15_e34_charlie_lee_on_privacy_mweb_mimble_wimble_extension_block_-_26.04.2024_23.52.mp3", "t": 438, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824032205/https://bitcoin-takeover.com/audio/media/2024-04-29_s15_e34_charlie_lee_on_privacy_mweb_mimble_wimble_extension_block_-_26.04.2024_23.52.mp3", "archive_date": "20260824032205", "archive_how": "existing"}, "btk-ep-s15e30": {"kind": "episode", "title": "S15 E30: Charlie Lee on Lightning & Litecoin", "url": "https://bitcoin-takeover.com/audio/?name=2024-04-16_s15_e30_charlie_lee_on_litecoin_lightning.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2024-04-16_s15_e30_charlie_lee_on_litecoin_lightning.mp3", "date": "Tue, 16 Apr 2024 04:26:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113152026/https://bitcoin-takeover.com/s15-e30-charlie-lee-on-lightning-litecoin-why-payment-coins-survived/", "archive_date": "20261113152026", "archive_how": "saved"}, "btk-ep-s11e5": {"kind": "episode", "title": "S11 E5: Charlie Lee on Mimble Wimble Extension Blocks (MWEB)", "url": "https://bitcoin-takeover.com/audio/?name=2022-06-07_s11_e5_charlie_lee_on_privacy_through_mimble_wimble_extension_blocks_mweb.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2022-06-07_s11_e5_charlie_lee_on_privacy_through_mimble_wimble_extension_blocks_mweb.mp3", "date": "Tue, 07 Jun 2022 23:17:18 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20250322052003/https://bitcoin-takeover.com/audio/?name=2022-06-07_s11_e5_charlie_lee_on_privacy_through_mimble_wimble_extension_blocks_mweb.mp3", "archive_date": "20250322052003", "archive_how": "existing"}, "ep-s16e51-q848": {"kind": "episode", "title": "S16 E51: Sean Bowe on Bitcoin's privacy", "url": "https://bitcoin-takeover.com/audio/media/2025-10-18_s16_e51_sean_bowe_on_bitcoin_zcash_scaling_privacy.mp3", "t": 848, "tnote": "transcript-derived, pending a listen", "archive_url": "https://web.archive.org/web/20260824043141/https://bitcoin-takeover.com/audio/media/2025-10-18_s16_e51_sean_bowe_on_bitcoin_zcash_scaling_privacy.mp3", "archive_date": "20260824043141", "archive_how": "existing"}, "btk-ep-s16e55": {"kind": "episode", "title": "S16 E55: Mert Mumtaz on Zcash, Privacy & Zillions", "url": "https://bitcoin-takeover.com/audio/?name=2025-11-04_s16_e55_mert_mumtaz_on_zcash_privacy_zillions.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2025-11-04_s16_e55_mert_mumtaz_on_zcash_privacy_zillions.mp3", "date": "Tue, 04 Nov 2025 16:25:00 +0200", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113152832/https://bitcoin-takeover.com/episodes/s16-e55-mert-mumtaz-on-zcash-privacy-zillions/", "archive_date": "20261113152832", "archive_how": "saved"}, "btk-ep-s17e28": {"kind": "episode", "title": "S17 E28: Josh Swihart on Zcash & ZODL", "url": "https://bitcoin-takeover.com/audio/?name=2026-06-13_s16_e28_josh_swihart_on_zcash_zodl.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2026-06-13_s16_e28_josh_swihart_on_zcash_zodl.mp3", "date": "Sat, 13 Jun 2026 20:31:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113153455/https://bitcoin-takeover.com/s17-e28-josh-swihart-on-zcashs-comeback-the-orchard-bug-forking-the-company/", "archive_date": "20261113153455", "archive_how": "saved"}, "btk-ep-s17e49": {"kind": "episode", "title": "S17 E49: Kris Nuttycombe on Zcash at Ten, Hard Forks, the Dev Fund & Why Ossification Is Death", "url": "https://bitcoin-takeover.com/audio/?name=2026-11-01_s17_e49_kris_nuttycombe_on_zcash_at_ten_hard_forks_the_dev_fund_and_why_ossification_is_death.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2026-11-01_s17_e49_kris_nuttycombe_on_zcash_at_ten_hard_forks_the_dev_fund_and_why_ossification_is_death.mp3", "date": "Sun, 01 Nov 2026 19:17:41 +0200", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113153829/https://bitcoin-takeover.com/audio/?name=2026-11-01_s17_e49_kris_nuttycombe_on_zcash_at_ten_hard_forks_the_dev_fund_and_why_ossification_is_death.mp3", "archive_date": "20261113153829", "archive_how": "saved"}, "btk-ep-s17e50": {"kind": "episode", "title": "S17 E50: Daira-Emma Hopwood on Zcash at 10, Halo, ZSAs and the Fight Over Grants", "url": "https://bitcoin-takeover.com/audio/?name=2026-11-04_s17_e50_daira_emma_hopwood_on_zcash_at_ten_the_destroyed_ceremony_laptop_and_the_cost_of_getting_privacy_right.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2026-11-04_s17_e50_daira_emma_hopwood_on_zcash_at_ten_the_destroyed_ceremony_laptop_and_the_cost_of_getting_privacy_right.mp3", "date": "Sat, 07 Nov 2026 18:10:00 +0200", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113153909/https://bitcoin-takeover.com/audio/?name=2026-11-04_s17_e50_daira_emma_hopwood_on_zcash_at_ten_the_destroyed_ceremony_laptop_and_the_cost_of_getting_privacy_right.mp3", "archive_date": "20261113153909", "archive_how": "saved"}, "btk-ep-s16e1": {"kind": "episode", "title": "S16 E1: Mike Belshe on BitGo, Self Custody & The Future of Bitcoin", "url": "https://bitcoin-takeover.com/audio/?name=2025-01-03_s16_e1_mike_belshe_on_bitgo_the_future_of_bitcoin.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2025-01-03_s16_e1_mike_belshe_on_bitgo_the_future_of_bitcoin.mp3", "date": "Fri, 03 Jan 2025 20:14:00 +0200", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113152412/https://bitcoin-takeover.com/episodes/s16-e1-mike-belshe-on-bitgo-self-custody-the-future-of-bitcoin/", "archive_date": "20261113152412", "archive_how": "saved"}, "btk-ep-s17e43": {"kind": "episode", "title": "S17 E43: Mike Belshe on BitGo, Quantum & Clarity", "url": "https://bitcoin-takeover.com/audio/?name=2026-09-16_s17_e43_mike_belshe_on_bitgo_quantum_clarity.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2026-09-16_s17_e43_mike_belshe_on_bitgo_quantum_clarity.mp3", "date": "Wed, 16 Sep 2026 17:37:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113135601/https://bitcoin-takeover.com/s17-e43-mike-belshe-on-bitgo-quantum-clarity/", "archive_date": "20261113135601", "archive_how": "saved"}, "btk-ep-s17e19": {"kind": "episode", "title": "S17 E19: Deadalnix (Amaury Séchet) on Forking Bitcoin & Ecash", "url": "https://bitcoin-takeover.com/audio/?name=2026-04-18_s17_e19_deadalnix_amaury_sechet_on_forking_bitcoin_ecash.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2026-04-18_s17_e19_deadalnix_amaury_sechet_on_forking_bitcoin_ecash.mp3", "date": "Sat, 18 Apr 2026 14:31:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113153144/https://bitcoin-takeover.com/s17-e19-amaury-sechet-on-forking-bitcoin-twice-quantum-fud-scars-from-the-block-size-wars/", "archive_date": "20261113153144", "archive_how": "saved"}, "btk-ep-s15e28": {"kind": "episode", "title": "S15 E28: Deadalnix (Amoury Séchet) on Forking Bitcoin, Big Blocks & Scaling", "url": "https://bitcoin-takeover.com/audio/?name=2024-04-05_s15_e28_deadalnix_amaury_s_chet_on_forking_bitcoin_bch_ecash.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2024-04-05_s15_e28_deadalnix_amaury_s_chet_on_forking_bitcoin_bch_ecash.mp3", "date": "Fri, 05 Apr 2024 17:55:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20240530003717/https://bitcoin-takeover.com/audio/?name=2024-04-05_s15_e28_deadalnix_amaury_s_chet_on_forking_bitcoin_bch_ecash.mp3", "archive_date": "20240530003717", "archive_how": "existing"}, "btk-ep-s17e42": {"kind": "episode", "title": "S17 E42: Bob Summerwill on Ethereum Classic & Bitcoin's Fork Season", "url": "https://bitcoin-takeover.com/audio/?name=2026-09-12_s17_e42_bob_summerwill_on_ethereum_classic_bitcoin_forks_-_12_09_2026_05.24.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2026-09-12_s17_e42_bob_summerwill_on_ethereum_classic_bitcoin_forks_-_12_09_2026_05.24.mp3", "date": "Sat, 12 Sep 2026 05:54:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113135521/https://bitcoin-takeover.com/s17-e42-bob-summerwill-on-ethereum-classic-bitcoins-fork-season/", "archive_date": "20261113135521", "archive_how": "saved"}, "btk-ep-s5e1": {"kind": "episode", "title": "S5 E1: Bobby Lee on Ballet Cold Storage & Returning to the Real Bitcoin", "url": "https://bitcoin-takeover.com/audio/?name=2020-05-05_s5e1_bobby_lee_on_ballet_crypto_and_meeting_bruce_willis.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2020-05-05_s5e1_bobby_lee_on_ballet_crypto_and_meeting_bruce_willis.mp3", "date": "Fri, 01 May 2020 01:00:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20240912150959/https://bitcoin-takeover.com/audio/?name=2020-05-05_s5e1_bobby_lee_on_ballet_crypto_and_meeting_bruce_willis.mp3", "archive_date": "20240912150959", "archive_how": "existing"}, "btk-ep-s13e3": {"kind": "episode", "title": "S13 E3: Casey Rodarmor on Ordinals, Inscriptions & Bitcoin Culture", "url": "https://bitcoin-takeover.com/audio/?name=2023-02-06_s12_e13_casey_rodarmor_on_ordinals__inscriptions__bitcoin_culture.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2023-02-06_s12_e13_casey_rodarmor_on_ordinals__inscriptions__bitcoin_culture.mp3", "date": "Mon, 06 Feb 2023 23:51:50 +0200", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20251217054538/https://bitcoin-takeover.com/audio/?name=2023-02-06_s12_e13_casey_rodarmor_on_ordinals__inscriptions__bitcoin_culture.mp3", "archive_date": "20251217054538", "archive_how": "existing"}, "btk-ep-s15e34": {"kind": "episode", "title": "S15 E34: Charlie Lee on Privacy & MWEB (Mimble Wimble Extension Block)", "url": "https://bitcoin-takeover.com/audio/?name=2024-04-29_s15_e34_charlie_lee_on_privacy_mweb_mimble_wimble_extension_block_-_26.04.2024_23.52.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2024-04-29_s15_e34_charlie_lee_on_privacy_mweb_mimble_wimble_extension_block_-_26.04.2024_23.52.mp3", "date": "Mon, 29 Apr 2024 01:20:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20250623094544/https://bitcoin-takeover.com/audio/?name=2024-04-29_s15_e34_charlie_lee_on_privacy_mweb_mimble_wimble_extension_block_-_26.04.2024_23.52.mp3", "archive_date": "20250623094544", "archive_how": "existing"}, "btk-ep-s7e8": {"kind": "episode", "title": "S7 E8: Charlie Lee on Video Games, Star Wars & Investing", "url": "https://bitcoin-takeover.com/audio/?name=2020-12-25_s7_e8_charlie_lee_on_video_games__star_wars__investing.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2020-12-25_s7_e8_charlie_lee_on_video_games__star_wars__investing.mp3", "date": "Fri, 25 Dec 2020 20:50:00 +0200", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20241114195712/https://bitcoin-takeover.com/audio/?name=2020-12-25_s7_e8_charlie_lee_on_video_games__star_wars__investing.mp3", "archive_date": "20241114195712", "archive_how": "existing"}, "btk-ep-s15e66": {"kind": "episode", "title": "S15 E66: Jameson Lopp on Michael Saylor, Bitcoin Ossification & Paranoid Crypto Anarchism", "url": "https://bitcoin-takeover.com/audio/?name=2024-11-20_s15_e66_jameson_lopp_on_michael_saylor_bitcoin_ossification_paranoid_crypto_anarchism_.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2024-11-20_s15_e66_jameson_lopp_on_michael_saylor_bitcoin_ossification_paranoid_crypto_anarchism_.mp3", "date": "Wed, 20 Nov 2024 15:37:00 +0200", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113152241/https://bitcoin-takeover.com/episodes/s15-e66-jameson-lopp-on-michael-saylor-bitcoin-ossification-paranoid-crypto-anarchism/", "archive_date": "20261113152241", "archive_how": "saved"}, "btk-ep-s14e9": {"kind": "episode", "title": "S14 E9: Jameson Lopp on Casa, Self Custody & Bitcoin Maximalism", "url": "https://bitcoin-takeover.com/audio/?name=2023-08-23_s13_e9_jameson_lopp_on_self_custody_and_bitcoin_maximalism.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2023-08-23_s13_e9_jameson_lopp_on_self_custody_and_bitcoin_maximalism.mp3", "date": "Wed, 23 Aug 2023 22:56:28 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20250712155419/https://bitcoin-takeover.com/audio/?name=2023-08-23_s13_e9_jameson_lopp_on_self_custody_and_bitcoin_maximalism.mp3", "archive_date": "20250712155419", "archive_how": "existing"}, "btk-ep-s15e70": {"kind": "episode", "title": "S15 E70: Jeff Garzik on Hemi & Bitcoin Development", "url": "https://bitcoin-takeover.com/audio/?name=2024-12-19_s15_e70_jeff_garzik_on_bitcoin_hemi_bridges_-_19.12.2024_01.32.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2024-12-19_s15_e70_jeff_garzik_on_bitcoin_hemi_bridges_-_19.12.2024_01.32.mp3", "date": "Thu, 19 Dec 2024 02:36:00 +0200", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20241219115932/https://bitcoin-takeover.com/audio/?name=2024-12-19_s15_e70_jeff_garzik_on_bitcoin_hemi_bridges_-_19.12.2024_01.32.mp3", "archive_date": "20241219115932", "archive_how": "existing"}, "btk-ep-s17e22": {"kind": "episode", "title": "S17 E22: Jeremy Rubin on CTV, Char & Building on Bitcoin", "url": "https://bitcoin-takeover.com/audio/?name=2026-05-06_s17_e11_jeremy_rubin_on_ctv_char_building_on_bitcoin.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2026-05-06_s17_e11_jeremy_rubin_on_ctv_char_building_on_bitcoin.mp3", "date": "Wed, 06 May 2026 12:37:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113153315/https://bitcoin-takeover.com/s17-e22-jeremy-rubin-on-ctv-char-relentless-building-in-an-adversarial-environment/", "archive_date": "20261113153315", "archive_how": "saved"}, "btk-ep-s16e60": {"kind": "episode", "title": "S16 E60: Jonathan Bier on Bitcoin Civil Wars & BitMEX Research", "url": "https://bitcoin-takeover.com/audio/?name=2025-11-24_s16_e60_jonathan_bier_on_bitcoin_civil_wars_bitmex_research.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2025-11-24_s16_e60_jonathan_bier_on_bitcoin_civil_wars_bitmex_research.mp3", "date": "Mon, 24 Nov 2025 03:14:00 +0200", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113152918/https://bitcoin-takeover.com/episodes/s16-e60-jonathan-bier-on-bitcoin-civil-wars-bitmex-research/", "archive_date": "20261113152918", "archive_how": "saved"}, "btk-ep-s17e38": {"kind": "episode", "title": "S17 E38: Keagan McClelland (Keags) on Lightning Metrics, Covenants, Consensus Politics & Verifying Bitcoin", "url": "https://bitcoin-takeover.com/audio/?name=2026-08-18_s17_e38_keagan_mcclelland_on_bitcoin_development_lightning.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2026-08-18_s17_e38_keagan_mcclelland_on_bitcoin_development_lightning.mp3", "date": "Tue, 18 Aug 2026 02:37:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113153659/https://bitcoin-takeover.com/s17-e38-keagan-mcclelland-on-lightning-metrics-covenants-consensus-politics-verifying-bitcoin/", "archive_date": "20261113153659", "archive_how": "saved"}, "btk-ep-s17e39": {"kind": "episode", "title": "S17 E39: Kurt Wuckert Jr. on BSV & Big Block Bitcoin", "url": "https://bitcoin-takeover.com/audio/?name=2026-08-23_s17_e39_kurt_wuckert_jr._on_bsv_big_block_bitcoin.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2026-08-23_s17_e39_kurt_wuckert_jr._on_bsv_big_block_bitcoin.mp3", "date": "Sun, 23 Aug 2026 19:54:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113135410/https://bitcoin-takeover.com/s17-e39-kurt-wuckert-jr-on-the-big-block-wars-bsv-craig-wright-the-road-not-taken/", "archive_date": "20261113135410", "archive_how": "saved"}, "btk-ep-s17e48": {"kind": "episode", "title": "S17 E48: Robin Linus in the 1000 BTC Car, Driving to BitDevs Atlanta", "url": "https://bitcoin-takeover.com/audio/?name=2026-10-24_s17_e48_robin_linus_in_the_1000_btc_car_at_bitdevs_in_atlanta_-_23_10_2026_09.45.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2026-10-24_s17_e48_robin_linus_in_the_1000_btc_car_at_bitdevs_in_atlanta_-_23_10_2026_09.45.mp3", "date": "Sat, 24 Oct 2026 07:12:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113135732/https://bitcoin-takeover.com/episodes/s17-e48-robin-linus-in-the-1000-btc-car-driving-to-bitdevs-atlanta/", "archive_date": "20261113135732", "archive_how": "saved"}, "btk-ep-s17e46": {"kind": "episode", "title": "S17 E46: Livestream from Tabconf 8, Part 1 (feat. Paul Sztorc, Andre Beganski, Alex Lewin, Janusz, Christopher Allen, Will & Michael Tidwell)", "url": "https://bitcoin-takeover.com/audio/?name=2026-10-15_s17_e46_livestreaming_at_tabconf_8_feat_paul_sztorc_christopher_allen_michael_tidwell_more.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2026-10-15_s17_e46_livestreaming_at_tabconf_8_feat_paul_sztorc_christopher_allen_michael_tidwell_more.mp3", "date": "Thu, 15 Oct 2026 18:11:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113153745/https://bitcoin-takeover.com/s17-e46-livestream-from-tabconf-8-part-1-feat-paul-sztorc-andre-beganski-alex-lewin-janusz-christopher-allen-will-michael-tidwell/", "archive_date": "20261113153745", "archive_how": "saved"}, "btk-ep-s17e37": {"kind": "episode", "title": "S17 E37: Paul Sztorc on the eCash Three Stage Launch, Free Coins & 12 Drivechains", "url": "https://bitcoin-takeover.com/audio/?name=2026-08-13_s17_e37_paul_sztorc_on_launching_ecash_ecx_.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2026-08-13_s17_e37_paul_sztorc_on_launching_ecash_ecx_.mp3", "date": "Thu, 13 Aug 2026 19:59:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113153615/https://bitcoin-takeover.com/s17-e37-paul-sztorc-on-the-ecash-three-stage-launch-free-coins-12-drivechains/", "archive_date": "20261113153615", "archive_how": "saved"}, "btk-ep-s17e21": {"kind": "episode", "title": "S17 E21: Paul Sztorc Hard Forks Bitcoin to Launch Ecash with Drivechains!", "url": "https://bitcoin-takeover.com/audio/?name=2026-04-24_s17_e21_paul_sztorc_on_launching_drivechains_on_ecash_in_2026_-_22.04.2026_02.17.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2026-04-24_s17_e21_paul_sztorc_on_launching_drivechains_on_ecash_in_2026_-_22.04.2026_02.17.mp3", "date": "Fri, 24 Apr 2026 17:03:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113153228/https://bitcoin-takeover.com/s17-e21-paul-sztorc-hard-forks-bitcoin-to-launch-ecash-with-drivechains/", "archive_date": "20261113153228", "archive_how": "saved"}, "btk-ep-s17e5": {"kind": "episode", "title": "S17 E5: Paul Sztorc on Bitcoin Derangements", "url": "https://bitcoin-takeover.com/audio/?name=2026-01-29_s17_e5_paul_sztorc_on_bitcoin_derangements.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2026-01-29_s17_e5_paul_sztorc_on_bitcoin_derangements.mp3", "date": "Thu, 29 Jan 2026 02:18:00 +0200", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113153058/https://bitcoin-takeover.com/s17-e5-paul-sztorc-bitcoin-derangements/", "archive_date": "20261113153058", "archive_how": "saved"}, "btk-ep-s16e52": {"kind": "episode", "title": "S16 E52: Paul Sztorc on Bitcoin's Culture Wars", "url": "https://bitcoin-takeover.com/audio/?name=2025-10-24_s16_e52_paul_sztorc_on_bitcoin_s_culture_wars.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2025-10-24_s16_e52_paul_sztorc_on_bitcoin_s_culture_wars.mp3", "date": "Fri, 24 Oct 2025 14:20:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113152746/https://bitcoin-takeover.com/episodes/s16-e52-paul-sztorc-on-bitcoin-s-culture-wars/", "archive_date": "20261113152746", "archive_how": "saved"}, "btk-ep-s15e44": {"kind": "episode", "title": "S15 E44: Chris DeRose on Bitcoin Uncensored (feat. Jay Berg, Wayne Vaughan & Paul Sztorc)", "url": "https://bitcoin-takeover.com/audio/?name=2024-06-28_s15_e44_chris_derose_on_bitcoin_uncensored_feat._jay_berg_wayne_vaughan_paul_sztorc_.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2024-06-28_s15_e44_chris_derose_on_bitcoin_uncensored_feat._jay_berg_wayne_vaughan_paul_sztorc_.mp3", "date": "Fri, 28 Jun 2024 00:13:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20250423055349/https://bitcoin-takeover.com/audio/?name=2024-06-28_s15_e44_chris_derose_on_bitcoin_uncensored_feat._jay_berg_wayne_vaughan_paul_sztorc_.mp3", "archive_date": "20250423055349", "archive_how": "existing"}, "btk-ep-s12e10": {"kind": "episode", "title": "S12 E10: Paul Sztorc on Baltic Honeybadger 2022 & BIP 300", "url": "https://bitcoin-takeover.com/audio/?name=2022-11-22_s12_e10_paul_sztorc_on_baltic_honeybadger_2022__bip_300.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2022-11-22_s12_e10_paul_sztorc_on_baltic_honeybadger_2022__bip_300.mp3", "date": "Tue, 22 Nov 2022 01:51:07 +0200", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20250918063146/https://bitcoin-takeover.com/audio/?name=2022-11-22_s12_e10_paul_sztorc_on_baltic_honeybadger_2022__bip_300.mp3", "archive_date": "20250918063146", "archive_how": "existing"}, "btk-ep-s16e30": {"kind": "episode", "title": "S16 E30: Peter Rizun on Scaling Bitcoin with Hardware", "url": "https://bitcoin-takeover.com/audio/?name=2025-06-14_s16_e30_peter_rizun_on_scaling_bitcoin_with_hardware_-_14.06.2025_16.39.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2025-06-14_s16_e30_peter_rizun_on_scaling_bitcoin_with_hardware_-_14.06.2025_16.39.mp3", "date": "Sat, 14 Jun 2025 19:56:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113152704/https://bitcoin-takeover.com/episodes/s16-e30-peter-rizun-on-scaling-bitcoin-with-hardware/", "archive_date": "20261113152704", "archive_how": "saved"}, "btk-ep-s17e47": {"kind": "episode", "title": "S17 E47: Tabconf 8 Livestream with Kevin Loaec, Ekrem Bal, Spaces Protocol & The Bitcoin Pivot (Bonus: Peter Todd)", "url": "https://bitcoin-takeover.com/audio/?name=2026-10-18_s17_e47-_tabconf_8_livestream_with_kevin_loaec_ekrem_bal_spaces_protocol_the_bitcoin_pivot.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2026-10-18_s17_e47-_tabconf_8_livestream_with_kevin_loaec_ekrem_bal_spaces_protocol_the_bitcoin_pivot.mp3", "date": "Sun, 18 Oct 2026 01:50:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113135646/https://bitcoin-takeover.com/s17-e47-tabconf-8-livestream-with-kevin-loaec-ekrem-bal-spaces-protocol-the-bitcoin-pivot/", "archive_date": "20261113135646", "archive_how": "saved"}, "btk-ep-s15e46": {"kind": "episode", "title": "S15 E46: Peter Todd on Bitcoin Covenants, Tail Emission, OpenTimestamps & Why Lightning Rocks", "url": "https://bitcoin-takeover.com/audio/?name=2024-07-19_s15-e46-peter-todd-on-bitcoin-covenants_tail_emission_opentimestamps.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2024-07-19_s15-e46-peter-todd-on-bitcoin-covenants_tail_emission_opentimestamps.mp3", "date": "Fri, 19 Jul 2024 15:12:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20241116221123/https://bitcoin-takeover.com/audio/?name=2024-07-19_s15-e46-peter-todd-on-bitcoin-covenants_tail_emission_opentimestamps.mp3", "archive_date": "20241116221123", "archive_how": "existing"}, "btk-ep-s14e4": {"kind": "episode", "title": "S14 E4: Peter Todd vs Sergej Korliar on Full RBF", "url": "https://bitcoin-takeover.com/audio/?name=2023-07-11_s14_e4_peter_todd_vs_sergej_kotliar_on_full_rbf.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2023-07-11_s14_e4_peter_todd_vs_sergej_kotliar_on_full_rbf.mp3", "date": "Tue, 11 Jul 2023 08:02:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20241012195357/https://bitcoin-takeover.com/audio/?name=2023-07-11_s14_e4_peter_todd_vs_sergej_kotliar_on_full_rbf.mp3", "archive_date": "20241012195357", "archive_how": "existing"}, "btk-ep-s11e11": {"kind": "episode", "title": "S11 E11: Peter Todd on Bitcoin Inflation, Lightning & Privacy", "url": "https://bitcoin-takeover.com/audio/?name=2022-07-25_s11_e11_peter_todd_on_bitcoin_inflation__lightning__privacy.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2022-07-25_s11_e11_peter_todd_on_bitcoin_inflation__lightning__privacy.mp3", "date": "Mon, 25 Jul 2022 21:35:56 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20240807090716/https://bitcoin-takeover.com/audio/?name=2022-07-25_s11_e11_peter_todd_on_bitcoin_inflation__lightning__privacy.mp3", "archive_date": "20240807090716", "archive_how": "existing"}, "btk-ep-s6e9": {"kind": "episode", "title": "S6 E9: Jonas Nick, Peter Todd & Alekos Filini on Bitcoin Development", "url": "https://bitcoin-takeover.com/audio/?name=2020-10-07_s6_e9_jonas_nick__peter_todd__alekos_filini_on_bitcoin_development_and_more.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2020-10-07_s6_e9_jonas_nick__peter_todd__alekos_filini_on_bitcoin_development_and_more.mp3", "date": "Wed, 07 Oct 2020 22:04:27 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20250909094949/https://bitcoin-takeover.com/audio/?name=2020-10-07_s6_e9_jonas_nick__peter_todd__alekos_filini_on_bitcoin_development_and_more.mp3", "archive_date": "20250909094949", "archive_how": "existing"}, "btk-ep-s4e7": {"kind": "episode", "title": "S4 E7: Peter Todd on Hardware Wallets, Security & ProofMarshall", "url": "https://bitcoin-takeover.com/audio/?name=2020-02-04_s4_e7_peter_todd_on_hardware_wallets__security__proofmarshall.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2020-02-04_s4_e7_peter_todd_on_hardware_wallets__security__proofmarshall.mp3", "date": "Tue, 04 Feb 2020 09:27:09 +0200", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113151659/https://bitcoin-takeover.com/s4-e7-peter-todd-on-hardware-wallets-security-proof-marshall/", "archive_date": "20261113151659", "archive_how": "saved"}, "btk-ep-s17e4": {"kind": "episode", "title": "S17 E4: {ideal} BitVM Optimizations (Robin Linus, Liam Eagen, Ying Tong)", "url": "https://bitcoin-takeover.com/audio/?name=2026-01-24_s17_e4_ideal_bitvm_optimizations_robin_linus_liam_eagen_ying_tong_.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2026-01-24_s17_e4_ideal_bitvm_optimizations_robin_linus_liam_eagen_ying_tong_.mp3", "date": "Sat, 24 Jan 2026 14:32:00 +0200", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20260210112529/https://bitcoin-takeover.com/audio/?name=2026-01-24_s17_e4_ideal_bitvm_optimizations_robin_linus_liam_eagen_ying_tong_.mp3", "archive_date": "20260210112529", "archive_how": "existing"}, "btk-ep-s15e58": {"kind": "episode", "title": "S15 E58: Liam Eagen, Robin Linus & Jonas Nick on Shielded Client Side Validation & Bitcoin Privacy", "url": "https://bitcoin-takeover.com/audio/?name=2024-10-10_s15_e58_robin_linus_jonas_nick_liam_eagen_on_shieldeed_client_side_validation_bitcoin_privacy_-_10.10.2024_17.26.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2024-10-10_s15_e58_robin_linus_jonas_nick_liam_eagen_on_shieldeed_client_side_validation_bitcoin_privacy_-_10.10.2024_17.26.mp3", "date": "Thu, 10 Oct 2024 17:48:00 +0300", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113152159/https://bitcoin-takeover.com/episodes/s15-e58-liam-eagen-robin-linus-jonas-nick-on-shielded-client-side-validation-bitcoin-priva/", "archive_date": "20261113152159", "archive_how": "saved"}, "btk-ep-s15e13": {"kind": "episode", "title": "S15 E13: Robin Linus on BitVM & Permissionless Bitcoin Development", "url": "https://bitcoin-takeover.com/audio/?name=2023-12-31_s15_e13_robin_linus_on_bitvm__permissionless_bitcoin_development.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2023-12-31_s15_e13_robin_linus_on_bitvm__permissionless_bitcoin_development.mp3", "date": "Sun, 31 Dec 2023 17:47:00 +0200", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20260205131739/https://bitcoin-takeover.com/audio/?name=2023-12-31_s15_e13_robin_linus_on_bitvm__permissionless_bitcoin_development.mp3", "archive_date": "20260205131739", "archive_how": "existing"}, "btk-ep-s15e26": {"kind": "episode", "title": "S15 E26: Roger Ver on Bitcoin", "url": "https://bitcoin-takeover.com/audio/?name=2024-03-28_s15_e26_roger_ver_on_bitcoin.mp3", "mp3": "https://bitcoin-takeover.com/audio/media/2024-03-28_s15_e26_roger_ver_on_bitcoin.mp3", "date": "Thu, 28 Mar 2024 15:42:00 +0200", "src": "bitcoin-takeover.com feed (audio/feed.xml)", "archive_url": "https://web.archive.org/web/20261113151839/https://bitcoin-takeover.com/s15-e26-roger-ver-on-hijacking-bitcoin-freedom-maximalism/", "archive_date": "20261113151839", "archive_how": "saved"}}}