Q token mark QUADPublic Accountability

Core market path

Core Path

Core is the admitted-value and monetary-accounting surface for QUAD. It tells readers what can be observed, what can be accounted for, and what remains closed until owner evidence exists.

The Fast Answer

Core exists to keep economic state constrained before it is trusted.

QUAD and uquad are public Core metadata for the chain's accounting, fees, staking metadata, supply labels, and observable balances. That metadata is not a sale, allocation schedule, reward campaign, price model, or redemption promise.

Current Core Path

Use this as the public reading order for Core. Current numeric state belongs on Core-owned routes.

1. Observe CoreOpen the Core observatory for chain state, validators, blocks, metadata, receipts, and status labels. 2. Read CoreUnderstand admitted-value posture, custody labels, quarantine, refusal, receiver evidence, and Core law. 3. Read token modelUse the main-domain token model to understand QUAD/uquad without inferring sale or value claims. 4. Check supply policyRead the Core-owned supply policy route for the current public supply-law surface. 5. Check validatorsReview public validator visibility without treating visibility as decentralization proof or future privilege. 6. Check opening gatesMinting policy, distribution, value movement, liquidity, and market activation open only by evidence.

What Core Owns

Core is useful because it says no when the evidence is not strong enough.

Admitted value

Core decides whether value is admitted, pending, quarantined, refused, routed, settled, or terminal under Core law.

Custody labels

Treasury and related account classes publish what can be safely summarized. A balance is not spendable unless its account class says it is.

Supply posture

Supply policy can show cap, allowance, refusal, burn, sink, and failsafe posture without becoming a price or scarcity pitch.

Validator state

Core owns block production, validator visibility, fee/staking metadata, and chain-health observation.

Refusal

Sleep, hold, quarantine, refusal, and downgrade are normal outcomes when truth, safety, route, or funding is missing.

Activation labels

Core economic opening remains staged until the owner routes can carry the claim.

Supply Policy In Plain Terms

Supply law is a constraint system. It is not a redemption story.

Policy areaPublic meaningNot implied
Mint pathMint expansion can happen only when collateral, price truth, safety clearance, epoch allowance, worthiness approval, and hard-cap room all support it.Unconditional issuance, user entitlement, sale access, or reward distribution.
Hard capThe public policy anchor keeps QUAD supply inside a fixed ceiling.Price support, reserve redemption, or guaranteed market value.
Burn pathBurning belongs through the Sink boundary with provenance and source-separated receipts.Buyback promise, redemption event, or market-support guarantee.
Validator supportValidator support comes from already-collected fees retained for distribution.New issuance, mining, hardware reward, or hidden allocation.
Treasury accountingTreasury state is custody and accounting truth where safely published.User claim on assets, protocol sell lane, guaranteed liquidity, or price floor.

Validator Path

Validator credibility comes from observable operation, not a badge on a page.

Full node first

A candidate starts as a non-signing full node and proves sync, stability, resource posture, and clean health evidence.

Dedicated keys

Validator keys should stay separate from wallets, websites, relayers, providers, and other chain services.

Observation window

Disk, memory, CPU, peer churn, clock drift, restart behavior, block lag, and missed signing need public or operator-held evidence.

Promotion gate

Validator promotion should wait until binary/runtime line, genesis/config posture, and matching block results are settled.

Honest label

Project-operated validators should be labeled honestly until independent control can be shown.

No entitlement

Running a node, joining Discord, testing, or validating does not create allocation, ownership, governance rights, or future privilege.

Mainnet Hardening Gates

The public path is evidence-first. A launch label waits for freeze evidence.

Freeze source

Exact source tree, binary hash, genesis hash, chain ID, validator consensus set, and app version need recorded freeze evidence.

Genesis discipline

Mainnet genesis must be produced from a final profile, not a harness profile, with dev balances and test-only accelerators removed.

Public metadata

Chain ID, denom, decimals, address prefixes, RPC/REST boundaries, explorer templates, and asset metadata need stable public publication.

Operating separation

Validator, oracle, relayer, provider, website, and support rails should not blur custody or authority.

Opening statement

Any launch announcement must say what is live on day one and what is still staged.

Closed claims

No public sale, airdrop, reward path, distribution schedule, liquidity, or market activation is open unless owner evidence says so.

Core Is Not

These refusals are part of the product boundary, not decoration.

Not a walletViewing Core pages does not require a wallet connection, seed phrase, signature, or payment.
Not a saleCore pages do not sell QUAD, allocate QUAD, or promise a distribution schedule.
Not a wrapperQUAD should not be summarized as a Bitcoin wrapper, reserve-asset wrapper, lending product, or exposure product.
Not miningCore is Cosmos SDK / CometBFT chain observation, not Proof-of-Work mining, GPU rewards, or hardware earning.
Not inheritedBridge transit, Infra receipts, Liquid motion, listings, and public attention do not become Core admission.
Not a guaranteeSupply labels, burns, fees, staking metadata, or validator visibility do not guarantee price, liquidity, redemption, yield, or future access.