❤️ 3 Likes · ⚡ 0 Tips
{
"txid": "4c0464e55d7f369447e07d62a606455a288b388eab5e81b571731ea92059d425",
"block_height": 0,
"time": null,
"app": "treechat",
"type": "post",
"map_content": "Timeline of Chronicle (Bitcoin protocol restoration):\r\n\r\n- Background (2020\u20132022): \r\n It is the direct continuation of the Genesis upgrade from February 2020, which had already restored most of the original Bitcoin protocol (removing arbitrary limits and restoring functionality). Since at least 2022, the pending opcodes (such as OP_VER, OP_VERIF, OP_2MUL, etc.) had already been listed on the BSV wiki/docs as \u201cscheduled for the Chronicle update.\u201d\r\nIt was never a new change, but the final phase of restoration. \r\n Reference: https://docs.bsvblockchain.org/network-topology/nodes/sv-node/chronicle-release\r\n\r\n- Official announcement: \r\n July 1, 2024 (press release from BSV Blockchain / BSVA). \r\n Connor Murray (Director of Stewardship) presented it as the update that would restore the last missing opcodes and remove the remaining restrictions to align \u201cas closely as possible\u201d with Satoshi\u2019s original Bitcoin protocol. At that time it was announced for Q3 2024 (\u201cofficial release later in 2024, with additional details closer to the date\u201d). \r\n Reference: https://www.prnewswire.com/news-releases/chronicle-bsv-blockchain-latest-update-302186812.html\r\n\r\n- Debate and review (2024\u20132025): \r\n There were multiple rounds of developer feedback and input from real network projects (including STAS Token and others). The BSVA collaborated closely with developers on specific projects to determine the exact features needed for maximum flexibility while preserving stability. All historical changes to the Bitcoin protocol were reviewed to justify each restoration. The code was always open on GitHub for community review. No external or public security audit is documented. \r\n\r\n References: https://coingeek.com/chronicle-bsv-blockchain-latest-update/ and https://coingeek.com/chronicle-completes-bsv-mission-to-restore-original-bitcoin-protocol/\r\n\r\n- Original vs. actual deployment: \r\n - Originally scheduled: Q3 2024. \r\n - Final version (SV Node v1.2.0 \u201cChronicle\u201d): Released on January 7, 2026. \r\n - Testnet activation: January 14, 2026 (block 1,713,168 at 12:00 noon). Already activated. \r\n - Mainnet activation: April 7, 2026 (block 943,816 at 12:00 noon). It is mandatory for all full nodes (miners); the new features are opt-in for anyone who wants to use them. \r\n Reference: https://github.com/bitcoin-sv/bitcoin-sv/releases\r\n\r\n- Why it was delayed (more than 1.5 years): \r\n Official main reason: multiple rounds of feedback, refinement, and close collaboration with developers to ensure the upgrade was as stable as possible, maintained backward compatibility, and actually met the real needs of applications (not just restoring opcodes \u201cfor the sake of it\u201d). The BSVA prioritized quality and consensus over speed, to avoid any disruption on the network before moving to Teranode. \r\n Reference: https://coingeek.com/chronicle-completes-bsv-mission-to-restore-original-bitcoin-protocol/\r\n\r\nSummary: Chronicle is the last major hard fork designed to \u201clock\u201d the protocol in its closest form to Satoshi\u2019s original vision. It is already ready and activated on testnet; only the mainnet activation on April 7, 2026 remains. There is no publicly documented external audit; the review was internal + community-driven with developers. \r\n\r\nReference: https://docs.bsvblockchain.org/network-topology/nodes/sv-node/chronicle-release",
"media_type": "text/markdown",
"filename": "|",
"author": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
"display_name": "J1 Pelaez",
"channel": null,
"parent_txid": null,
"ref_txid": null,
"tags": null,
"reply_count": 2,
"like_count": 3,
"timestamp": "2026-03-29T20:29:00.000Z",
"media_url": null,
"aip_verified": true,
"has_access": true,
"attachments": [],
"ui_name": "J1 Pelaez",
"ui_display_name": "J1 Pelaez",
"ui_handle": "J1 Pelaez",
"ui_display_raw": "J1 Pelaez",
"ui_signer": "14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK",
"ref_ui_name": "unknown",
"ref_ui_signer": "unknown"
}