Precompile directory
These are development addresses from the inspected node profile. Short addresses are zero-padded to 20 bytes; 0x1009 means 0x0000000000000000000000000000000000001009. Reserved code does not imply that the service's required genesis policy, assets or committees are configured.
Native services
| Address | Service | Boundary | Guide |
|---|---|---|---|
0x1000 | Order registry | Place/read/cancel development registry; separate from matching | Orderbook |
0x1001 | Spot and native ledger | Configured asset 1 / JOLT 0 market and ledger operations | Orderbook |
0x1002 | Privileged asset adapter | Called by admitted token implementations; not the token address | Asset policy |
0x1003 | Firm quotes | Bounded maker quotes and common-ledger settlement | Markets |
0x1004 | Oracle reports | Configured publisher, freshness and sequence checks | Oracle observations |
0x1005 | Security Council | Expiring asset outflow budgets only | Safety controls |
0x1006 | Lending | JOLT cash pool and configured collateral profile | Markets |
0x1007 | Atomic plans | Bounded caller-preserving all-or-nothing calls | Native services |
0x1009 | Native accounts / passkeys | Registration, in-place policy and authorized execution | Accounts |
0x100a | Payment grants | Fixed recipient and bounded JOLT authority | Accounts |
0x100b | Guardian recovery | Delayed owner-cancellable policy replacement | Accounts |
0x100c | Voluntary time locks | Owner lock, extendable but not early-releasable | Safety controls |
0x100d | Recurring payments | Fixed JOLT recipient and schedule | Payments |
0x100e | Funded vouchers | Immutable recipient, cumulative funded claims | Payments |
0x100f | Native token grants | Bounded native asset transfer grants | Accounts |
0x1010 | Time/hash payments | Funded amount and exact claim window | Payments |
0x1011 | Agreed escrows | Accepted funded delivery/dispute terms | Payments |
0x1012 | Inactivity bequests | Funded shares, check-in and notice | Payments |
0x1013 | Operation grants | Exact runtime-pinned call authority | Accounts |
0x1014 | Contract-token grants | Explicit bounded contract-token transfer profile | Accounts |
0x1015 | Attested payments | Owner-selected signer evidence | Payments |
0x1016 | Code admission | Optional runtime-hash eligibility and committee actions | Asset policy |
0x1017 | Issuer asset policy | Non-JOLT issuer permissions, holds and listing state | Asset policy |
0x1018 | Block root history | Recent and accumulated historical root verification | State proofs |
0x1019 | Retention obligations | Funded challenge/answer and retention profiles | State proofs |
0x101a | Composed conditions | Bounded condition composition for funded payments | Payments |
0x101b | Vesting grants | Funded linear grant with cliff | Tokenomics and vesting |
0x101c | Stake positions | Bonding, unbonding and double-sign evidence | Staking |
0x101d | SAFU fund | Committee-authorized claims from funded reserves | Funded services |
0x101e | AMM factory | Authorized native Uniswap V2-compatible pairs | Markets |
0x101f | LP farm | Funded LP-share reward stream | Funded services |
0x1020 | Alias registry | Readable names held as ERC-721 tokens | Aliases |
0x1021 | Pre-call hooks | Contract-configured hook enforcement | Hooks |
0x1022 | Asset registration | Fixed supply or capped non-JOLT issuance | Asset policy |
The gap at 0x1008 is intentional: do not invent an endpoint for an unassigned entry. Energy is a common-ledger policy with a read RPC, not an extra endpoint guessed from this numbering.
The AMM pair addresses are derived by its factory; token adapter addresses come from genesis or asset registration. Neither the pair nor the JOLT token identity should be guessed from this table.
Ethereum system precompiles
The host supports Osaka system precompiles 0x01–0x11 and corrected P-256 verification at 0x0100. Their input layouts, gas costs and failure behavior follow the Osaka execution profile. P-256 verification alone is not a WebAuthn assertion verifier.
Integration rules
Use the cpp-node Solidity SDK for typed calls, service addresses and ABI declarations. Match its version, canonical binary encoding, gas bounds and permission model to the deployed service. Low-level bytes payloads have strict schema; do not improvise their encoding. Native state and EVM state share rollback, while outer transaction fees follow the runner profile.
Start with a read-only native call and the service guide. This directory is an inventory, not a promise of deployed public configuration.