Q token mark QUADPublic Accountability

Public system model

Economic Model, Governance, And Chain Interaction

This page gives reviewers the plain route through the project: how value is accounted for, why validators matter, how governance is bounded, what security assumptions are being made, what opens when, and how the four chain surfaces interact without inheriting each other's authority.

Current Model Labels

These labels are public posture, not investment terms.

Economic modelRule-driven accounting and utility work
Validator incentivesFees, staking, liveness, and slash-risk alignment
GovernanceOn-chain law after launch; bootstrap authority bounded
SecurityCometBFT/Cosmos assumptions plus surface-owned controls
RolloutPhase-based, evidence-gated, no unsupported mainnet date
Token utilityChain-local gas, staking, settlement, work payment, and accounting roles

Economic Model

The project separates accounting, useful work, passage, and motion instead of pretending one token or one page owns every job.

Core accounts

Core is the conservative accounting surface. It labels admitted value, testnet balances, fees, staking metadata, quarantine state, terminal state, and public economic status.

Infra sells useful work

Infra prices retained work, receipts, storage, query, proof, and contract-work surfaces through BIGHT-labeled work paths. Product work and reserve backing stay separate.

Bridge proves passage

Bridge records movement posture, provenance, refusal, quarantine, and receipt categories. Delivery does not force admission on the destination chain.

Liquid bounds motion

Liquid handles fast movement, positions, clearing, liquidation, explicit-law labels, and settlement requests without letting motion become Core value truth.

Payment follows evidence

Useful work should leave a receipt, export, proof, invoice, retained balance, prefund, or approved liability path before another surface treats it as payable.

Public rule

No page should imply sale access, reward eligibility, allocation, yield, value guarantee, or market opening unless a surface-owned public source supports it.

Validator Incentives

Validators are not a marketing badge. They are the public accountability spine for liveness, signing, ordering, and upgrade discipline.

IncentivePublic meaningBoundary
FeesTransaction fees can compensate block production and network operation when the relevant chain opens the lane.Testnet fees have no monetary value.
StakingBonded stake aligns validators with liveness, uptime, and correct signing behavior.Validator participation does not create allocation, ownership, or future privilege.
SlashingBad signing, downtime, and consensus faults need consequences so public state is worth reading.Exact penalties belong to chain config and governance.
ReputationIndependent validators make the network easier to trust than a single operated node.Reputation is not a reward promise.
Service reliabilityStable validators and public endpoints make explorers, wallets, and status pages useful.Endpoint operation is not mining or DePIN hardware earning.

Governance Structure

The goal is to make block-one rules strong enough that governance can change the system openly instead of relying on private patch authority.

Genesis law first

The public launch posture should put as much durable rule shape as possible into genesis, parameters, module boundaries, and published upgrade paths.

Bootstrap authority is narrow

Bootstrap operation can keep the network alive before decentralization is mature, but it should not be described as personal authority over user value or permanent governance.

On-chain governance later

Once live governance is enabled, parameter changes, upgrades, and economic openings should move through the chain's own governance path or another clearly published process.

Chain-local consequence

Shared risk information can cross surfaces, but each chain decides local consequences under its own rules. One chain's signal does not automatically punish another chain's account.

Public disclosure

Team, operator, audit, custody, and funding disclosures should appear only when approved for public release and needed for the relevant stage.

No hidden entitlement

Discord membership, test transactions, faucet use, node operation, or code review does not create governance rights, allocation, or future economic claim.

Security Assumptions

Security claims stay modest until public evidence catches up.

Consensus assumption

Cosmos SDK / CometBFT chain state depends on validator participation, key security, correct signing, and the standard BFT assumption that malicious voting power stays below the chain's safety threshold.

Endpoint assumption

Public RPC, REST, explorer, and website endpoints are observation surfaces. They help reviewers inspect state, but they are not the chain's authority.

Bridge assumption

Bridge and vault-like movement are high-sensitivity surfaces. Receipts, quarantine, refusal, and destination admission rules matter more than speed.

Liquid assumption

Fast execution needs settlement discipline. A position, wrapper, route, or motion summary is not final balance truth until the settlement owner records it.

Infra assumption

Stored records, receipts, proofs, and retained state are useful only when the receiving surface checks binding, freshness, and local policy before trusting them.

Audit assumption

No external audit is claimed until a report exists. Security pages can reserve report slots, but empty slots are not proof.

Rollout Timeline

The timeline is phase-based because publishing a date before evidence exists creates the wrong behavior.

Now: observe

Core testnet state, chain metadata, public pages, crawler guides, and surface-owned subdomains are available for review.

Now: test utility

Infra public testing can show bounded work paths, receipts, proof, query, contract-work labels, and BIGHT-denominated test flows where open.

Now: bound movement

Bridge and Liquid publish boundary surfaces and public-safe data so reviewers can understand passage and motion before production movement opens.

Next: harden

Stabilize endpoint posture, validator review, registry packets, security report slots, failure labels, and public status feeds.

Next: publish policy

Public minting, distribution, value movement, liquidity, market activation, and governance policies need source-backed language before activation.

Later: open narrowly

Open economic lanes one at a time, with public status labels, explicit boundaries, and dated updates when a lane actually moves.

Token Utility

Token utility is chain-local. A token's job on one surface does not automatically become the job of every other surface.

SurfaceUtilityNot a claim
Core / QUADNative accounting unit, gas/staking denom in current testnet metadata, admitted-value labels, quarantine state, and public economic status.Not a sale, price model, Bitcoin wrapper, yield product, or allocation schedule.
Infra / BIGHTWork-payment label for storage, receipts, query, proof, and contract-work lanes when accepted by Infra.Not raw compute rewards, node earning, airdrop eligibility, or proof that all future workloads are open.
BridgeFee, passage, receipt, provenance, quarantine, and destination-admission support where a lane is opened.Not a promise that delivered assets are admitted, backed, liquid, or immediately redeemable.
LiquidFast movement, positions, clearing, liquidation, explicit-law labels, and settlement requests under Liquid-local rules.Not live public leverage, brokerage, exchange access, or Core value truth.

How The Chains Interact

The chains coordinate through evidence. They do not merge authority.

Core to Infra

Core can export public-safe accounting state or service needs; Infra can remember, price, store, prove, or serve the accepted work.

Infra to Core

Infra can return receipts, proofs, invoices, retained-state labels, and contract-work packets. Core still decides whether and how to account for them.

Bridge to Core

Bridge can deliver provenance and passage evidence. Core decides admission, quarantine, routing, or refusal under Core law.

Core to Bridge

Core can expose admitted status or routing intent. Bridge still owns passage, lane safety, receipt posture, and refusal categories.

Liquid to Core

Liquid can expose motion, position, settlement-request, and risk labels. Core does not inherit worth from speed, attention, wrappers, or liquidity.

All to all

Risk observations can be shared across the stack, but punishment and meaning stay local to the consuming chain.

Review Path

Use these pages when checking the model from outside.

Observe CoreOpen the QUAD Testnet observatory. Core token modelRead QUAD and uquad public-safe utility labels. ActivationRead minting, distribution, movement, liquidity, and market-opening lanes. RoadmapRead phase-based opening order and closed claims. ArchitectureRead the chain relationship and service-stack map. SecurityRead audit posture and security claim limits. VerifyCheck how public evidence should be read. BoundaryRead non-inheritance and public meaning rules.