Bitcoins <\/p>\n
The BSV blockchain reached a historic milestone on April 7, 2026, as the Chronicle protocol upgrade was activated<\/a>\u00a0at block height 943,816. It marks the completion of Bitcoin\u2019s original protocol restoration and sets the stage for the coming Teranode Era<\/a>.<\/p>\n The activation occurred at approximately 9:13 PM UTC, representing the final evolution of the SV Node protocol<\/a>. Officially \u201cSV Node v1.2.0,\u201d Chronicle restores the complete technical vision outlined by Satoshi Nakamoto in the original 2008 Bitcoin white paper. It removes the last artificial limitations introduced to Bitcoin<\/a>\u00a0over the years and re-enables capabilities that were always part of the design.<\/p>\n BSV network node operators (\u201cminers\u201d) should already have upgraded their software by now, but running Chronicle is necessary to stay in consensus with the network (unless they\u2019re already running Teranode, that is).<\/p>\n If you operate a BSV exchange or node, we have an important update.<\/p>\n Chronicle (SV Node v1.2.0) activates ~7 April 2026 (block height 943,816).<\/p>\n Nodes must be upgraded before that to remain in consensus.<\/p>\n \u25ba Details + support: https:\/\/t.co\/ZHaaDLu3wT<\/a><\/p>\n<\/div>\n \u2014 BSV Association (@BSVAssociation) March 19, 2026<\/a><\/p><\/blockquote>\n<\/div>\n<\/figure>\n What Chronicle delivers<\/strong><\/p>\n The Chronicle release<\/a>\u00a0expands the BSV protocol\u2019s capabilities, while maintaining full backward compatibility for existing transaction types. Essentially, Chronicle completes the Genesis upgrade process that began in 2020 that had restored many aspects of Bitcoin\u2019s original protocol but left certain technical restrictions in place.<\/p>\n Among Chronicle\u2019s key improvements is the reinstatement of disabled script OP_CODEs, reintroducing functionality present in Bitcoin\u2019s initial release but later removed due to concerns about potential vulnerabilities. These OP_CODEs expand the expressiveness of Bitcoin\u2019s scripting language, enabling more sophisticated smart contracts<\/a>\u00a0and transaction types without requiring off-chain solutions or secondary protocols.<\/p>\n The upgrade also implements the Original Transaction Digest Algorithm<\/a>\u00a0(OTDA), giving developers the option to use Bitcoin\u2019s native signature hashing method rather than the later modified BIP143 algorithm. Users can opt into OTDA by setting the new CHRONICLE [0x20] sighash flag, while existing transactions continue to function exactly as before.<\/p>\n Chronicle v1.2.0. April 7 \ud83d\udcdc <\/p>\n The engine that powers BSV’s data layer is getting a huge upgrade!<\/p>\n Deposits & withdrawals may pause for ~2-3 hours during transition. <\/p>\n While other chains break, BSV builds. See you on the other side. \u26a1<\/p>\n \ud83d\udee0\ufe0f https:\/\/t.co\/NNCuzVqbQv<\/a> pic.twitter.com\/0RSu32bfrA<\/a><\/p>\n<\/div>\n \u2014 Orange Gateway (@orangegatewayx) April 3, 2026<\/a><\/p><\/blockquote>\n<\/div>\n<\/figure>\n Perhaps most significantly, Chronicle<\/a>\u00a0removes malleability-related restrictions for transactions that opt in through version numbers greater than 0x01000000. This removes constraints, including: the minimal encoding requirement; low-S signature requirements; NULLFAIL and NULLDUMMY checks for signature operations; MINIMALIF requirements for conditional logic; and clean stack requirements. These restrictions had been implemented to prevent \u201ctransaction malleability attacks,\u201d but came at the expense of reduced flexibility in Bitcoin Script development.<\/p>\n \u201cTransaction malleability was a concern based on a misunderstanding of the payment flow, and a misunderstanding of nodes themselves,\u201d said Connor Murray<\/a>, Head of Protocol Stability at BSV Association. \u201cBecause they misunderstood how payments should work and are convinced that miners will behave irrationally, they put in a bunch of restrictions on developers.\u201d<\/p>\n The upgrade also expands the consensus limit on Script number size from 750KB to 32MB, while still allowing node operators to maintain their own policy limits through the \u201cmaxscriptnumlengthpolicy\u201d configuration parameter.<\/p>\n Chronicle activates April 7th.<\/p>\n I want to take a moment to explain why this upgrade matters \u2013 not just technically, but personally.<\/p>\n First, huge thanks to everyone involved. The developers who did the actual work, and the community members who contributed to ensuring the scope\u2026<\/p>\n<\/div>\n \u2014 Connor Murray (@Bitcoin_Beyond) March 30, 2026<\/a><\/p><\/blockquote>\n<\/div>\n<\/figure>\n\n
\n
\n