# Backward Compatibility Considerations Chronicle was designed to maintain **full backward compatibility** through transaction versioning: * **Legacy transactions continue working:** Pre-Chronicle transactions validate under their original rulesets * **Version-based activation:** Restored opcodes are available in Chronicle-version transactions * **No chain split:** Universal agreement on version-based opcode availability * **Smooth transition:** Scripts can be written to work across versions using OP\_VERIF ### Development Best Practices **Choose Appropriate Opcodes:** ``` # Good: Direct multiplication OP_MUL # Avoid: Complex workaround when OP_MUL is available OP_DUP OP_ADD OP_ADD ... ``` **Use version opcodes for compatibility:** ``` # Ensure Chronicle features are available OP_VER OP_3 OP_GREATERTHANOREQUAL OP_VERIFY OP_CAT # Safe to use OP_C ``` **Leverage string manipulation for efficiency:** ``` # Extract specific data ranges efficiently OP_8 OP_LEFT # Header OP_8 OP_32 OP_SUBSTR # Body OP_4 OP_RIGHT # Footer ``` **Test thoroughly:** Restored opcodes need testing for edge cases **Document version requirements:** Specify minimum transaction version for your scripts --- # 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/backward-compatibility-considerations.md?ask= ``` 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.