Q token mark QUADPublic Accountability

Public log

Public Updates

Dated public notes for visible website, chain readiness, docs, Infra, Bridge, Liquid, and security surface changes. Updates point to proof; they do not replace it.

Proof Archive Source Map Readiness Office External References

Update Log

Short notes only. Public updates should point to a surface, not replace one.

Current public posture

Core is observable, Infra has the clearest product path, Bridge publishes live passage evidence with route gates, and Liquid publishes motion posture with market activity closed.

How to read old entries

Older entries are a dated trail. The owning subdomain and current status pages win when a live route has moved on.

What updates do not do

Updates do not open sale access, allocation, production value movement, liquidity, rewards, or market activation.

2026-06-12

Bridge public wording now reflects live Ethereum-mainnet source-pool receipts, owner-vault allocation proof, PAXG source-pool support, host-gas accounting, and Core acknowledgement evidence while keeping self-serve movement lane-gated.

Read Bridge surface
2026-06-12

The main domain has been checked against Hostinger: the deployed public files match the local release source, and the remaining availability dependency is the apex DNS record.

Read status
2026-06-02

Public reference surfaces now include a stack overview, phase guide, reference guide, category guide, and proof archive so reviewers can quote bounded evidence instead of inferring around it.

Read stack overview
2026-06-02

The proof archive now separates dated entries, current evidence routes, source evidence, package evidence, deployed evidence, and superseded evidence.

Read proof archive
2026-05-17

Bridge, Core, Liquid, and Infra gained clearer public evidence labels. Bridge movement remains closed; Infra now frames storage as one lane inside provable memory.

Read readiness
2026-05-13

The Model page now explains economics, validators, governance, security assumptions, rollout, token utility, and chain interaction without opening sale or reward claims.

Read model
Older dated notes
DateSurfaceUpdate
2026-05-12Main domainBoundary and site-map pages were added so readers and reviewers can find the right public surface without guessing.
2026-05-09QUAD CoreCore remains observable at core.uquad.org. The next soak target and indexed genesis stay staged until the intended public state is final.
2026-05-09Public metadataCore wallet metadata is visible at core.uquad.org/chain.json. Registry-style metadata remains staged review material.
2026-05-09InfraInfra public reference bundles describe product-contract receipts and opt-in hook packets without claiming production service state.
2026-05-09LiquidLiquid continues toward runtime logic and app-wiring readiness while keeping public endpoint contracts separate from live market claims.
2026-05-08RoadmapPhase-based roadmap added with current, next, and later labels. No date, sale path, production movement, liquidity, or market activation opens without public evidence.
2026-05-08Economic ActivationActivation path added for minting policy, distribution, value movement, liquidity surfaces, and market module activation.
2026-05-07QUAD CoreQUAD-specific registry and explorer packets remain staged until the intended indexed genesis is frozen.
2026-05-07BridgeBridge app wiring is closed. Mounted runtime execution is the active next phase while public value movement remains closed.
2026-05-07LiquidLiquid has app-wiring guardrails and explicit-law audit staging. Static exports are labels, not settlement truth.
2026-05-07InfraInfra public surface describes BIGHT work intake, byte-based upload quote, query/download quote, balances, ledger, and intake APIs as bounded product-hardening surfaces.
2026-05-06InfraInfra public observatory deployed with BIGHT work intake, upload, query/download, balances, chain metadata, RPC, and public intake routes.
2026-05-06LiquidLiquid public folder gained a static endpoint contract and explicit-law audit contract.
2026-05-06BridgeBridge app-wiring and query-audit work progressed while public value routes remained closed.
2026-05-06Core transport rehearsalOsmosis testnet IBC transport rehearsal recorded as a test lane while money routes remained asleep.
2026-05-05Main domainMain website pages simplified so broad summaries stay on uquad.org while detailed state lives on subdomains.
2026-05-05Infra / Bridge / LiquidPublic folders aligned around status, route posture, proof, receipt, readiness, summary, and assistant-guide pages.
2026-05-04InfraInfra readiness pages added hosting posture and public snapshot labels without private procedure.
2026-05-03WebsiteDocs, readiness, and homepage structure were added or simplified so live data points back to the surface that owns it.

Update Cadence

Update when a public reader would otherwise have to guess whether a claim moved, stalled, closed, or became stale.

TriggerWhat the update should sayWhat it must not imply
Owner route changesName the surface, route, old label, new label, and proof link.Do not imply sibling-chain authority or broader launch status.
Evidence gate movesSay what changed, what proof exists, what remains closed, and what someone can check next.Do not imply sale access, allocation, reward eligibility, live liquidity, or market opening.
Stale route is supersededName the old source, replacement source, freshness, and downgrade rule.Do not quote old state as current state.
External reference appearsName the outside source and its narrow scope, then link the official owner surface.Do not treat discovery, indexing, or discussion as endorsement.
Security or audit state changesName the report slot, scope, date, status, and what remains withheld.Do not imply private procedure, complete safety, or unaudited production movement.
No material changeLeave the old note dated and point to the current owner route instead of manufacturing noise.Do not use silence as proof of failure or success.

Update Types

Use the narrowest update type that fits. Stronger language waits for stronger owner-published evidence.

Status / livenessOwner surface, current label, freshness, and what cannot be verified if the route is stale. Public surface changeNew, moved, retired, or replaced page, route, JSON, receipt, or owner endpoint. Product readinessWhat is usable, staged, blocked, closed, or waiting for proof before stronger claims. Evidence archiveDated proof class, owner route, source/package/deployed status, and superseded-state handling. Security / audit postureReport slot, disclosure state, scope, public boundary, and what remains withheld. Incident / degradationWhat degraded, who owns it, what still works, and the next public check. Deprecation / replacementOld source, replacement source, migration note, and stale-state downgrade rule. Launch gate progressGate moved, proof exists, next gate, and closed economic claims. Validator / community noteCoordination path, role boundary, report shape, and what Discord does not prove.

Dated Update Shape

Every public update should answer the same five questions so readers do not fill gaps with speculation.

What changed?

Name the surface, route, label, or evidence gate that moved.

What proof exists?

Link the owner page, receipt, endpoint contract, artifact, public repo, or accepted external source.

What remains closed?

Say which sale, reward, allocation, liquidity, market, custody, route, or private-support claim is still not open.

What can someone do next?

Point to the next public read, support path, owner route, or readiness check.

What not to infer?

Prevent crawler, community, wallet, listing, and market-status overreach before it starts.

Who owns the next update?

Name Core, Infra, Bridge, Liquid, main website, community, or external reference owner.

Update Rule

Updates should be dated, narrow, and verifiable. A good update names the owner, proof link, boundary, freshness, next check, and what remains closed.

Not An Announcement Feed

This page does not create reward eligibility, allocation, mainnet timing, investment signals, production value movement, or private access rights.

Infra productBIGHT wallet, funding, upload, verify, retrieve, balances, ledger, and proof paths. Bridge productRoute journey, proof, inventory, receipt, refusal, and passage evidence. Liquid motionMovement posture, settlement labels, risk surface, and market-closed state. DocsPlain entry points for different reader paths. RoadmapPhase-based roadmap and evidence gates. PhasesCurrent jobs, phase order, opening gates, and closed-state boundaries. ActivationEconomic opening path and public evidence lanes. ModelEconomics, validators, governance, security assumptions, token utility, rollout, and chain interaction. ReadinessObservation, staged, closed, and production transition labels. BoundaryAuthority, meaning, visibility, and non-inheritance rules. Site MapReader-facing discoverability map. SecurityAudit and disclosure report slots.