Architecture
How the Solana program, backend, maker gateway, SDK, and frontend fit together.
Olive is a Solana-only application. The former HyperEVM runtime is not part of the current request, quote, transaction, or settlement path, and there is no dual-chain mode, bridge, or state migration from it.
Five components make up the system:
| Component | Responsibility |
|---|---|
| Anchor program | On-chain accounts, quote verification, credit and collateral accounting, settlement, and redemption |
| Backend | HTTP API, maker WebSocket gateway, finalized-state indexer, keeper, and operator tooling |
@olive-so/solana-sdk | The public npm package: PDA derivation, Ed25519 V4 quote digests, maker authentication, and the managed maker client |
| Frontend | The trading application, using Privy accounts and Solana wallets |
| Docs | This site, including the normative maker wire contract |
The SDK is the only component you install. The program is on-chain and verifiable; the backend and frontend are Olive-operated services you reach over HTTPS and WSS.
Position lifecycle
Request
The frontend submits an authenticated entry RFQ carrying the taker's Solana wallet, market and expiry identity, product, exact size, strike, premium budget, and the reference price the ticket was built against. The backend rejects an inactive market, a disabled product, a strike outside the request policy, and a stale or drifted reference price before anything is persisted.
Auction
The backend persists a short auction deadline — 2 seconds by default — and
pushes a self-contained request to subscribed makers over /maker/v1/ws. Makers
return strict Ed25519 V4 quotes. Olive validates each one, derives every
execution account itself, simulates candidates in rank order, and returns only
the best executable quote to the user.
Execute
The frontend signs the prepared versioned Solana transaction; an Olive sponsor pays the fee and rent. The program revalidates maker state, quote signature and nonce, budget, credit, prefunding, bucket, and exposure limits atomically before creating the position.
Fund and settle
The indexer projects finalized program state into PostgreSQL, the keeper drives funding deadlines and settlement, and the owner either exits early against an original-maker quote or redeems after an immutable settlement price is recorded.
What is authoritative
When this documentation and a shipped artifact disagree, the artifact wins:
- Maker WebSocket API v1 is the normative maker wire contract. Every other maker page on this site is a summary of it.
- The Anchor IDL shipped inside
@olive-so/solana-sdk, together with the program deployed at the ID inGET /v1/config, is authoritative for exact account and instruction layouts. - The JSON Schema catalog and golden fixtures in the SDK package are authoritative for wire encodings, and are what your conformance run is checked against.
- Your reviewed environment onboarding record is authoritative for the deployment identity you sign against. Never take those values from documentation.
Solana program
Core accounts, instruction families, and lifecycle responsibilities.
RFQ & Ed25519
V4 entry and exit quote bindings, ranking, and the execution boundary.
API reference
HTTP surfaces for the app, transaction preparation, and probes.
Maker integration
WebSocket onboarding, quoting, lifecycle, and reconciliation.
Oracle & keeper
Pyth Benchmark settlement and the keeper's job model.
Networks
Deployment identity, manifests, and local development.