6 standards
The same script can be a run of bytes, a hex string, or readable assembly. Standards here pin down those forms so two tools agree on what a script says, and one defines a higher level language that compiles down to it.
Also searched as ASM, assembly, hex, compiler, decompiler, BASIC.
6 standards, spread across 2 of the 12 topics.
The same script can be written as raw bytes, as hexadecimal, or in a readable assembly form, and tools disagree about the details. This documents all three so software can convert between them without surprises.
Filed under Scripts
Script encoding is the main subject of these 4.
The same script can be written as raw bytes, as hexadecimal, or in a readable assembly form, and tools disagree about the details. This documents all three so software can convert between them without surprises.
Bitcoin's scripting instructions are numbers, which machines read easily and people do not. This defines a readable way to write them down, so a developer can inspect a script and reason about what it does.
Every library prints Bitcoin script in a slightly different readable form, so output from one tool is not accepted by another. This fixes one form so scripts can be moved between tools and languages.
Bitcoin Script is a low-level stack machine with no names or structure, so a script of any real size is nearly impossible to read, review, or safely edit once written. Because a published covenant can never be changed after it is funded, mistakes hidden in that unreadable stack manipulation are typically found only after it is too late to fix. This gives developers a way to write covenant logic in a readable form and, just as importantly, to read back and verify a script someone else already deployed.
These are about something else, and deal with script encoding on the way.
Most Bitcoin payments lock coins so that only the holder of one particular key can spend them. This documents exactly how that lock is written and later unlocked, which is the pattern behind an ordinary Bitcoin address.
A Bitcoin contract that needs to change some stored value on every spend has only one trustworthy place to keep that value: inside its own locking script. But Bitcoin Script can only cut a script apart at fixed byte positions, so two developers solving this independently end up with two incompatible layouts, and neither their tools nor anyone else's contracts can read the other's state. This describes a shared, self-describing way to lay out that state so any script, wallet, or third-party contract can find and read it without being told anything else about it.
Concepts that keep appearing on the same standards as this one.
Search standards by number, title, author or topic