Skip to content

Syscall Categories

Back to Syscalls

Overview

The embedded runtime registry contains 39 syscall names across 5 categories: the 38 Neo N3 syscall names plus the neo-devpack-solidity System.Runtime.GetMsgValue extension used for host-injected Solidity msg.value. Some host-state queries are intentionally approximated in the embedded runtime; see the category pages for method-level behavior.

CategoryCountPrefixPurpose
Storage11System.Storage.*Persistent key-value state
Runtime20System.Runtime.*Execution context, notifications, and the GetMsgValue extension
Contract4System.Contract.*Cross-contract calls and accounts
Crypto2System.Crypto.*Signature verification
Iterator2System.Iterator.*Traversal of storage search results

INFO

Most cryptographic operations (SHA256, RIPEMD160, keccak256, ECDSA verification, BLS12-381) are exposed through the CryptoLib native contract, not through syscalls. The two System.Crypto.* syscalls handle only signature verification against the current script container.

MIT Licensed