Current scope
The Version 0.1 design is a payment network first. It defines cryptographic authorization and leaves advanced transaction conditions, contract execution, and scripting architecture unresolved. Developers should not assume compatibility with any existing smart-contract virtual machine, scripting language, or contract bytecode format.
Authorization policies
The base protocol must support secure authorization of transfers. Future extensions may evaluate policy structures such as multiple authorized signers, time-based conditions, spending limits, delegated permissions, or escrow-style workflows. None of those mechanisms should be considered available until formally specified.
Determinism and bounded execution
If programmable payment conditions are introduced, every validating node must be able to reach the same result from the same valid inputs. Resource limits, denial-of-service resistance, serialization, versioning, and state-access rules would need to be part of the specification.
Extension path
Significant programmability should be introduced through an ECIP with a threat model, deterministic execution rules, cost model, compatibility analysis, test vectors, and testnet deployment. Application developers should treat anything else as experimental.