MRV syscall ABI

Locked

The Monolythium RISC-V application-contract host interface is not a released, stable public ABI. No syscall names, selectors, memory layouts, deployment format, constructor behavior, receipt schema, or value-transfer behavior is certified for application developers.

Do not deploy code or move value based on historical ABI drafts. Source names, tests, or internal feature gates do not establish network availability.

Release gates

A public ABI requires a versioned specification, deterministic execution and resource limits, memory-safety rules, receipt semantics, SDK bindings, conformance fixtures, activation evidence tied to the active genesis, security review, and value-less end-to-end tests. Compatibility and deprecation rules must also be defined before applications can depend on it.

Until those gates are complete, MRV app contracts remain planned design work. See Writing an MRV app contract for the same boundary.