# Assessment 1 #### Which event triggered the 2010 opcode restrictions in Bitcoin? * [ ] A theoretical security paper identifying potential vulnerabilities * [x] A value overflow bug that created 184 billion bitcoins * [ ] Community consensus that fewer opcodes would be easier to maintain * [ ] Satoshi Nakamoto's recommendation before leaving the project **Notes to Learners** The 2010 restrictions were a reactive response to an actual exploit. Understanding this history helps explain why certain opcodes were disabled for over a decade despite being part of Satoshi's original design. Chronicle's restoration comes after thorough security auditing confirmed these opcodes work safely as intended. --- # 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/assessment-1.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.