Markets and liquidity
Joltzu's native markets settle against the common ledger. Collateral, reserved orders and cash remain distinct obligations.
Spot orderbook and firm quotes
See the dedicated orderbook guide for priority, reservations, ABI, examples and wallet integration status. The presale's bonding curves use different contracts and pricing.
The development spot market quotes native base asset 1 in JOLT 0, with price-time priority, maker-price settlement and partial fills. Balance changes and fills share the journal. Soft reservations prevent the same cash backing incompatible resting bids.
Firm quotes bind maker, assets, size, price, expiry and nonce. Settlement rechecks authority and actual available funds. A quoted or supplied position is not permission to spend cash twice.
Lending
The development lending pool at 0x1006 holds real JOLT cash. Suppliers hold share-based claims; redemption is cash-limited. Borrowers pledge the configured collateral asset, and price/freshness, debt and liquidation rules follow the pool profile.
Supply-backed orders or quotes must redeem to actual cash at settlement. Broader markets and automatic supplied-position sells remain separate scope. Oracle signatures authenticate the publisher; they do not establish independent truth or executable liquidity.
Native AMM
The factory at 0x101e exposes a Uniswap V2-compatible factory/pair/LP-token interface. Pair logic is native, while reserves are common-ledger balances. Pairs accept eligible open listed native assets with current adapters; arbitrary ERC-20 contract storage balances are not automatically usable.
Pair creation is authorized by the configured factory admin. A zero admin leaves it closed. Delisting prevents new exposure while allowing the profile's liquidity exits. Adapter rotation does not migrate existing pools or approvals.
The LP farm at 0x101f streams JOLT rewards from a funded budget to eligible staked LP shares. No advertised APR follows from the code.
Integration checklist
Verify asset IDs, active adapter addresses, listing state, service configuration and the caller's permissions. Use explicit slippage/minimum output and expiry. Inspect successful receipts and events; neither an oracle response nor a simulation promises future settlement.