Enter app

Smart Contract Architecture

The contract set the frontend is written against.

Frontend01
Server components, client islands
Protocol adapter02
The only data seam
Contracts03
Not deployed
Events04
Emitted per action
Indexer05
Not connected
Protocol data06
Series, activity, accounting
Protocol architecture — stage 06 returns to stage 01 through the adapter
ContractResponsibility
Liquid tokenFixed-supply ERC-20 traded on external venues.
Claim tokenClaim token minted on wrap, burned on redemption.
WrapperMints and redeems the claim token, charges wrap fees.
Stockpile vaultCustodies acquired assets and reports balances.
Reserve engineRoutes protocol fees into asset acquisitions.
Fee routerCollects and accounts for every fee source.
Oracle registryValuation sources used for NAV and claim value.
Lending marketPhase II. Borrow against the claim token.

Expectations the frontend encodes

  • Stockpile balances are readable per asset without an off-chain service
  • The wrapper exposes a quote function matching the fee arithmetic
  • Every state change emits an event with enough detail to index
  • Fees are attributable to a source at collection time