Native services
The reference node implements common financial operations as native services. They use shared cash balances, policy checks and journaled execution rather than independent accounting islands.
| Service family | What it does | Read next |
|---|---|---|
| Accounts | Multisig, passkeys, recovery and bounded grants | Accounts |
| Markets | Price-time spot matching, firm quotes, lending and native AMM pairs | Orderbook and markets |
| Payments | Atomic plans, schedules, funded vouchers and conditional settlement | Payments |
| Stake | Share-based stake, unbonding and double-sign evidence | Staking |
| Asset policy | Registration, holder permissions, holds and listing state | Asset policy |
| Protection funding | Funded SAFU claims and vesting grants | Staking and funds |
| Readable names, hooks and oracles | ERC-721 aliases, contract policies and signed observations | Native utilities |
| Proof retention | Funded obligations, challenge/answer profiles and authenticated history | State proofs |
Off-chain randomness, callbacks, subscription automation and signed-data distribution are covered separately by the Joltzu Service Network. They submit ordinary transactions and do not run consensus.
Atomic composition
The illustration is a composition pattern, not a prepackaged routing API. Current plans carry exact per-call inputs and limits; generic result mapping and plan-wide debit/minimum-receipt extensions remain separate work. Outer fees are bound separately.
Services described here are development profiles. A compiled endpoint is not evidence of a public market, deployed token adapter or production keeper guarantee.