Capability matrix
What ships today, what's queued next.
Every capability is filed under Now, Next or Later. If it's Later, we say Later — no roadmap-as-marketing.
Now
Now · shipping
- Python-like high-level syntax
- Indent-delimited blocks, def for functions, strong typing — no implicit inference.
- Compile-time ownership checks
- Variables can't be reused after consumption; mirrors BVM's stack-pop semantics. Typical case: Hash160 + CheckSig sharing pubKey requires a Clone.
- Full compile pipeline
- Lexer → Parser → Semantic analysis (type / ownership / scope) → Bytecode generation. Output is JSON-shaped bytecode.
- Built-in interactive debugger
- utxo_compiler file.ct --debug drops into a REPL; drive the passing and failing paths separately.
- Linux / Windows release packages
- Linux, Windows 64-bit and Windows 32-bit. Each ships the executable, install.sh / install.bat, doc/ and VERSION; Windows packages also bundle three runtime DLLs.
- Bilingual official docs
- Overview / Installation / Bitcoin Basics / How-To / Tutorials / Advanced / References, all on docs.utxocompiler.com.
Next
Next · in flight
- More built-in functions and objects
- On top of Hash160, CheckSig, EqualVerify, PartialHash, Sha256, Hash256, BinToNum, Cat, Slice, SetMain, SetAlt, Push(BVM.*) and friends.
- Deeper How-To and advanced patterns
- Ownership system, alt-stack and multi-function coordination, and other advanced topics.
Later
Later · planned
- macOS binaries
- Planned; ship date not yet committed.
- Wider tutorial library
- Beyond P2PKH and Counter — more involved contract patterns and cross-contract coordination.
Progress is mirrored on docs.utxocompiler.com and GitHub. Anything labelled Now is something you can use today.