💡 IDEA - BSV Assembly #86
Replies: 2 comments
-
Steps:
|
Beta Was this translation helpful? Give feedback.
-
Relevant for the language spec: https://github.com/bitcoin-sv/BRCs/blob/master/scripts/0015.md |
Beta Was this translation helpful? Give feedback.
-
Summary
Source: YenPoint's Python SDK User Test Report. All credit to Ken Sato of YenPoint
The ASM (Assembly) format is valuable for programming Bitcoin Script. However, there are ambiguities in the ASM format of Bitcoin opcodes between the different SDKs (TypeScript, Python, GO). A standardized ASM format across all infrastructure, libraries, SDKs, etc. is required
The Go SDK, with its apparently comprehensive list of ASM might serve as the baseline for an ASM standard.
Example
The conversion between bytecodes, ASM, and higher-level languages should be seamless and consistent. This will empower developers to program in ASM, creating complex script templates using higher-level languages like Scrypt, and precisely define script templates for NFTs, FTs, and smart contracts. Historically, the ASM format has been poorly defined due to limited use cases and Bitcoin Core's disabling of most opcodes. BSV has re-enabled most opcodes and plans to restore all opcodes in the near future.Consequently, developers will craft increasingly complex smart contract scripts, heightening the need for a well-defined ASM format. This will elevate ASM from an ambiguous pseudo-language to a genuine programming language and foundational tool. This shift will usher in a renaissance for Bitcoin smart contracts
Other information
Examples of the Different ASM formats for each repositories
SVNode
Py-sdk
Typescript SDK
Go SDK
Relevance to BSV
Beta Was this translation helpful? Give feedback.
All reactions