# Key Takeaways

The Chronicle Release represents **complete restoration** of Bitcoin Script to Satoshi's original vision—all historically disabled opcodes now function exactly as designed, with new cryptographic capabilities added for modern requirements.

**All historically disabled opcodes are restored:** OP\_MUL, OP\_DIV, OP\_MOD, OP\_LSHIFT, OP\_RSHIFT, OP\_AND, OP\_OR, OP\_XOR, OP\_INVERT, OP\_2MUL, OP\_2DIV, OP\_CAT, OP\_SUBSTR, OP\_LEFT, OP\_RIGHT, and the version-related opcodes (OP\_VER, OP\_VERIF, OP\_VERNOTIF) all function as Satoshi originally designed them.

**Version-related opcodes enable adaptive scripts:** OP\_VER pushes the transaction version onto the stack. OP\_VERIF checks if the version is greater than or equal to a threshold, enabling scripts that use Chronicle features when available while maintaining compatibility with older transaction versions. Transaction version determines which ruleset applies to validation.

**New cryptographic capabilities extend the original design:** OP\_SHA512 and OP\_SHA512\_256 provide modern hash functions for interoperability with external systems. These additions recognize that blockchain technology has evolved since 2009.

**Backward compatibility is maintained through versioning:** Legacy transactions continue validating under original rulesets. Chronicle opcodes are available in Chronicle-versioned transactions. This approach prevented chain splits and enabled smooth adoption.

**Practical impact is transformative:** Operations requiring dozens of opcodes now take one or two. String manipulation enables efficient data parsing and construction. Mathematical operations enable on-chain calculations. Version-aware scripts can adapt to protocol changes gracefully.

**Chronicle Release Note:** All content in this chapter reflects the current state with Chronicle fully activated. When working with BSV applications, you can confidently use all restored opcodes knowing they're fully supported, professionally tested, and maintained for long-term compatibility. Use transaction versioning and OP\_VERIF to ensure your scripts work correctly across different transaction versions.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://hub.bsvblockchain.org/higher-learning/bsv-academy/bsv-opcodes/historical-opcodes-and-chronicle-restoration/key-takeaways.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.