Architecture

Three lending products on QOM, sharing four ecosystem primitives — the QNS registry, QNS Staking (with registry-level lien hooks), the QomX AMM with a permanent (LP-burned) ZAP/QOM market, and ZAP itself as collateral. Each product reads exactly the on-chain state it needs and nothing more: Pawn reads only the borrower's NFT contract; Forge reads ZAP balance + the QomX TWAP; the Loaded NFT Pool reads the QNS Staking emission schedule directly. No off-chain feeds, no signer committees, no third-party uptime dependencies above the contract level.

The QOM ecosystem layers

┌─────────────────────────────────────────────────────────────────────┐
│  QOM L1                       (settlement, gas, native asset)       │
└────────────────────┬────────────────────────────────────────────────┘
                     │
   ┌─────────────────┼─────────────────┬─────────────────────┐
   ▼                 ▼                 ▼                     ▼
┌──────┐       ┌──────────┐       ┌──────────┐         ┌──────────┐
│ ZAP  │       │   QNS    │       │  QomX    │         │  QOM     │
│ ERC- │       │  .qom    │       │  AMM     │         │  L1 RPC  │
│  20  │       │ registry │       │ ZAP/QOM  │         │  + WS    │
└──┬───┘       └────┬─────┘       └────┬─────┘         └────┬─────┘
   │                │                  │                    │
   │           ┌────▼─────┐            │ (LP burned —       │
   │           │ QNS      │            │  permanent market) │
   │           │ Staking  │            │                    │
   │           │ + liens  │            │                    │
   │           │          │            │                    │
   │           └────┬─────┘            │                    │
   │                │                  │                    │
   ├────────────────┴──────────────────┴────────────────────┤
   ▼                                                        ▼
┌────────────────────┬────────────────────┬────────────────────┐
│      Pawn          │      Forge      │   Loaded NFT Pool  │
│   (P2P NFT loans)  │  (pool lending)    │  (NFT pool, future)│
│   live             │  in design         │  planned           │
└────────────────────┴────────────────────┴────────────────────┘

Layer-by-layer

Layer	Role
QOM L1	Settlement, native gas asset (QOM), instant finality
ZAP	Ecosystem token. Fixed supply ERC-20. Used as collateral by Forge.
QNS	.qom domain registry and resolver
QNS Staking	Stake .qom domains, earn ZAP on a deterministic schedule, with registry-level lien hooks for collateralization
QomX (AMM)	UniV2-style automated market maker. The ZAP/QOM market here is the price source for Forge.
Pawn	Bilateral, peer-to-peer NFT-collateralized loans (live)
Forge	Pool-based money market (in design)
Loaded NFT Pool	Pool-based lending against staked, reward-bearing .qom (planned)

What each lending product reads from the ecosystem

Pawn

• Reads: the borrower's NFT contract (for ownership transfer), nothing else.
• No oracle. Pricing happens in the lender's head at funding time.
• No external dependency beyond the NFT contract being a valid ERC-721.

Forge

• Collateral asset: ZAP (Phase 1). Additional assets added later as their oracle/liquidity stories mature.
• Borrow asset: QOM. Liquidity comes from QOM-holder deposits.
• Oracle: a 30-minute time-weighted average price (TWAP) read directly from the ZAP/QOM market on QomX. The LP for that market is burned — its liquidity-provider tokens were sent to a dead address, so the pool itself cannot be removed and its liquidity cannot be withdrawn. The oracle has no off-chain dependency, no signer committee, and no rug surface — as long as QOM L1 is alive, the oracle works.
• Bootstrap path: borrowing QOM mints a fresh .qom, the contract stakes it on QNS Staking with a lien held by the lending pool, and the resulting ZAP emissions auto-route back to repay the loan. No collateral up-front; the staked position itself is the collateral.
• Lien hooks: QNS Staking exposes setLien / clearLien so a .qom staking position can collateralize a loan without leaving the staking contract. The borrower's ZAP-emission stream can be redirected to the pool until the debt clears.

Loaded NFT Pool

• Collateral asset: a staked .qom NFT — a "loaded" domain that is actively earning ZAP on QNS Staking.
• Pricing: the future ZAP emission schedule of that specific staking position is a known on-chain quantity. The contract reads it directly from QNS Staking and discounts it to value the collateral. No floor-price oracle, no manipulation surface.
• Borrow asset: QOM, drawn from the same lender pool Forge uses (or a separate pool — final architecture set at design lock).
• Default path: the staking position is unstaked by the contract via the lien; ZAP emissions plus the unstaked .qom itself recover the debt.

Contracts

Each product is a single upgradeable contract behind a UUPS proxy. Storage layout reserves a gap for future asset registries and parameter additions.

External dependencies are limited to:

• ERC-20 interfaces for ZAP and QOM
• ERC-721 interface for NFTs (Pawn) and .qom (Forge Bootstrap, Loaded NFT Pool)
• QNS controller for .qom mints (Forge Bootstrap)
• QNS Staking lien API (Forge Bootstrap, Loaded NFT Pool)
• QomX pair as a price oracle source (Forge)

All contracts will be source-verified on the QOM block explorer at deployment under Business Source License 1.1 (industry-standard for production lending protocols — used by Aave v4, Morpho, Euler v2, Fluid, Silo, Maple, Ajna). BUSL-1.1 keeps the source fully readable while restricting commercial copy-fork-deploy by competitors during the license window. Final addresses, audit reports, verified-source links, and the deployed bytecode hash will be published on this site at launch.