// ARCHITECTURE
How Quiver is built
Quiver is split into four layers — a frontend, a routing backend, a client SDK and a set of Solana programs. The frontend and SDK both speak to the same routing API, while settlement, staking and the deflationary burn are enforced on-chain so no party needs to be trusted with custody.
Frontend
Next.js App Router UI for the price index, job submission, dashboard, staking and governance. Talks to the backend over REST and to Solana via the wallet adapter.
Backend
A routing service that polls each provider network for live prices and capacity, normalizes them into NCU prices, and returns the cheapest path that satisfies a job spec.
SDK
@quiver/sdk wraps the routing API and escrow program so integrators can route(), submit() and status() jobs programmatically from Node or the browser.
Solana Programs
Anchor programs handle escrow, staking tiers and the on-chain fee split (burn / keeper / treasury). Settlement and the $QVR burn are enforced on-chain.
// JOB LIFECYCLE
Submit→Route→Quote→Escrow→Dispatch→Monitor→Completion→Release→Burn