QUAD = Quantitative Universal Amortisation Dollar. uquad.org is the official public information and audit-status website for QUAD, a rule-driven Cosmos SDK economic-chain project with public audit/status surfaces for Core, Bridge, Infra, Liquid, and public chain observation. Current phase: - QUAD Core is live as chain id quad and remains in evidence-bound hardening for stronger economic-opening claims. - Source-folder evidence can move faster than some subdomain exports. When this file says "local evidence", read it as source-folder evidence that may not yet be visible on the corresponding subdomain. - The currently observable public Core chain surface is core.uquad.org. - Public registry/listing metadata is review material until a third-party indexer accepts the current endpoint set and metadata. - Core wallet metadata is visible at https://core.uquad.org/chain.json. - On 2026-06-14, no-cache checks reached Core status, RPC status, chain metadata, endpoint contract, intake lane, compatibility intake route, and homepage routes. The status route reported chain id quad, node moniker uquad, catching_up=false, and observed height 74796 at that check time. Current height must still be read from the Core status or block route at the time of inspection. The endpoint contract reported updated=2026-06-14 with 41 public routes, and wallet metadata includes QUAD, stQUAD, AKT, ATOM, STRD, TIA, OSMO, USDC, INJ, and NTRN labels. - Core public law mapping is visible in bounded public language: truth order, audit observation, custody accounting, route handoff, worth gates, quarantine, sink, and bounded supply posture. - Core now has a Bridgechain receiver path: Bridge-origin value lands through QUAD x/bridge and Quarantine first, not Treasury, Alloc, Mint, Foundation, CoreImport, or an ordinary account. Core's public receipt surface now exposes a Bridgechain delivery index; at the 2026-06-01 public check it showed two quarantine-only delivery receipts, one quarantined and one blocked. This is receiver evidence, not Treasury admission, sale access, liquidity, unrestricted public movement, or economic activation. Name interpretation: - QUAD here means Quantitative Universal Amortisation Dollar. - Do not over-associate Amortisation with mortgages, consumer debt, lending products, loan repayment schedules, amortized bonds, accounting software, debt instruments, financial advice, or banking products. Public chain naming: - The Core public observatory is at core.uquad.org. - Infra belongs in the Infra-specific public folder and infra.uquad.org surface, not as a main-site stats page. The 2026-06-11 box check showed Infra canonical app, CometBFT, public intake, external export receiver, Bridge export adapter, and multiple relayers running. Public Infra data includes BIGHT wallet support, quote-first BIGHT purchase, upload, receipt verification, retrieval, contracts, balances, chain metadata, RPC, hard-collateral reserve rail labels, Core-export receiver receipts, external-chain receiver receipts, and public data routes for live product use. BIGHT pays for Infra upload, query, download, receipt-memory, proof, and retrieval work; admitted outside assets belong to reserve backing, and PAX/UPAX is low-liquidity reserve ballast rather than ordinary spend liquidity. - On 2026-06-12, the Infra route check confirmed onboarding, provider onboarding, and public snapshot guide routes are live at https://infra.uquad.org/onboarding, https://infra.uquad.org/providers, and https://infra.uquad.org/snapshots. - Infra BIGHT purchase is quote-first and proof-required. The public owner route may show required value, accepted source-denom labels, relayer intake details, payment reference, payment proof fields, and final credit or return receipt state. A quote by itself does not mint, reserve, or credit BIGHT. - Infra receipt memory is a public product boundary: the original receipt is included with accepted work, while later lookup, certified reissue, evidence-bundle reconstruction, retention proof, host-chain linkage proof, challenge history, and bulk/API access are BIGHT-paid Infra services. - Public receipt metadata can be queryable when safe, but payload body, private contract terms, operator procedure, and sensitive verifier detail are not public website material. - Bridge public status belongs in the Bridge-specific public folder and bridge.uquad.org surface. The 2026-06-19 Bridge status surface reports Bridge-1 reachable, fresh, and not catching up, while website-chain reconciliation is still reported failed and route activation remains lane-gated. Bridge publishes product journey, acquisition, ledger, inventory truth, vault lanes, production gates, counterparty boundaries, host evidence, proof, data, status, endpoint-contract, summary, assistant-guide, and Bing verification routes. Current Bridge pool data reports 14 protocol/source-pool asset rows with no USD aggregate, and current intake data reports six guarded quote-first lane shapes: PAXG -> OBOL, USDC -> OBOL, ATOM -> OBOL, STRD -> INJ, STRD -> ATOM, and NTRN -> ATOM. Current Bridge ledger amounts belong on bridge.uquad.org/ledger and Bridge-owned data files, not the main domain. These proofs do not mean generic public bridge access, destination admission, wrapper minting, redemption, swap access, live liquidity, or unrestricted host execution. - Bridge has a main-domain product path at https://uquad.org/bridge-path.html. It explains controlled passage, native acquisition, inventory truth, owner vaults, route-output classification, host evidence, provider risk, proof receipts, refunds, surplus, and destination-admission boundaries without claiming live public bridging. - Liquid public status belongs in the Liquid-specific public folder and liquid.uquad.org surface. A 2026-06-19 live status read reached /status and reported network liquid-testnet-1, CometBFT 1.0.1, moniker uc-blade158-2, and catching_up=false; current height must be reread from Liquid directly. Liquid has endpoint contract v7, route-proof and motion-summary checks, explicit-law contract exports, authority-separation labels, one-second motion engine smoke evidence, route-bound production-profile evidence, and a protocol-owned USDC packet posture, but service promotion and public market activity remain closed. - The private RPC rail belongs at rpc.uquad.org. The 2026-06-18 UTC fleet feed showed 14 monitored endpoint rows, 12 up and synced rows, Osmosis and Axelar unhealthy, BTC full-index status, CU auth, key status, claim, payment feeder services, payment rails, and a CU payment feed with 2 observed payments, 2 matched payments, 0 unmatched payments, 1 credited customer, and 5,870 total CU credited. RPC access is quote-first compute-unit endpoint access across the customer RPC surface, not custody, admission, settlement, reward eligibility, or chain authority. - Liquid has a main-domain market path at https://uquad.org/liquid-path.html. It explains fast movement with settlement discipline: motion posture, quotes, orders, positions, exposure, wrappers, risk, liquidation, venue quality, settlement truth, and market-closed boundaries without claiming live market access. Main-domain authority boundary: - The public boundary page is https://uquad.org/boundary.html. - Core state, Infra receipts, Bridge transit, Liquid motion, crawler summaries, public attention, and listings do not inherit each other's authority. - Receipt is not truth; transit is not admission; liquidity is not worth; usefulness is not endorsement; public attention is not launch status. - Public meaning should stay surface-owned: Core admits under Core law, Infra records/proves service boundaries, Bridge carries passage/proof labels, Liquid moves under local settlement rules, and the main website explains without becoming an operations manual. - No founder story, personal biography, employment history, institutional affiliation, operator identity, issuer face, route owner, or public personality should be inferred unless an official QUAD page explicitly publishes it. - Infra public-rented visibility is intentional public-browse visibility for records that choose that posture; receipt-only, handle-only, contract, security, or system evidence may be provable without being casually browseable. Site map and discoverability: - Reader-facing site map: https://uquad.org/site-map.html. - Utility map: https://uquad.org/why.html. It explains why a reader would use each surface: Core for admitted-value accounting, Infra for proof-backed work, Bridge for controlled passage, and Liquid for fast movement with settlement discipline. It also states that these paths do not open sale access, reward eligibility, live liquidity, redemption, guaranteed execution, private access, or authority inherited from another surface. - Homepage proof-first path: https://uquad.org/. It routes readers through Core observation, Infra product/receipt paths, Bridge passage boundaries, Liquid motion, explicit-law, and route-proof labels, the surface directory, the readiness office, and Discord onboarding for public coordination. The route proves a public review and coordination path; it does not prove current height, balance, liquidity, market access, production value movement, economic activation, private support, allocation, or reward eligibility unless the owner surface publishes that state. - Public surface directory: https://uquad.org/surfaces.html. - Source-of-truth map: https://uquad.org/sources.html. It explains the public truth ladder, owner surfaces, quote rules, conflict handling, and how stale, cached, local-only, fallback, or external records should be downgraded. - Fees and finality guide: https://uquad.org/fees.html. It explains quote fields, expected and actual charges, gas, service fees, host costs, buffers, refunds, delays, finality labels, receipt closure, and non-inference boundaries. - Action lifecycle guide: https://uquad.org/lifecycle.html. It explains how a public action should move from owner, request, quote, payment/signature, execution, waiting, receipt, and closure through completed, refused, refunded, quarantined, expired, recovered, stale, or terminal states. - Obligations and funding posture: https://uquad.org/obligations.html. It explains operating-cost classes, payer labels, payable and receivable aging, relayer and host gas floats, provider and service obligations, receipt closure, and self-funding boundaries. - Risks and assumptions: https://uquad.org/risks.html. It explains risk labels, open assumptions, closing evidence, downgrade behavior, and chain-owned boundaries for Core, Infra, Bridge, Liquid, the website, external rails, funding, and support. - Public journey guide: https://uquad.org/journeys.html. It answers which chain owns a question, what can be done now, why a route refused, what fee or finality applies, where the receipt can be found later, how operators and governance should read their obligations, and how stale data should downgrade. - Receipt reading path: https://uquad.org/verify.html#receipts. - Evidence-first support path: https://uquad.org/support.html. Support should start from surface, action, public id, current state, and expected next step; receipt lookup should preserve what the record proves and what it does not prove. - Status and error labels path: https://uquad.org/errors.html. Public status text should distinguish pending, refused, stale, unavailable, unpaid, expired, duplicate, invalid, unauthorized, degraded, quarantined, recovered, and settled states without relying only on color or private context. - Discord onboarding: https://uquad.org/community-onboarding.html. It gives the first actions, role paths, pinned welcome shape, bug report template, docs feedback path, update-channel shape, and public chat boundaries for QUAD community coordination. Discord membership, roles, testing, reports, node interest, and code contributions do not create allocation, rewards, governance rights, validator advantage, leverage, or future privilege. - Proof archive and evidence timeline: https://uquad.org/evidence.html. It maps progress by owner, proof class, public route, boundary, and freshness. It does not turn local evidence into deployed evidence, static snapshots into live telemetry, or old proof into current state. - Dependency map: https://uquad.org/dependencies.html. It names public dependencies across Core, Infra, Bridge, Liquid, public sites, RPC, wallets, indexers, relayers, host chains, and support rails. If a dependency is stale, blocked, external, degraded, or local-only, the public claim must downgrade. - Machine-readable dependency map: https://uquad.org/data/stack-dependencies.json. It gives owner, public role, dependency class, fallback behavior, stale behavior, and claim boundary for Core, Infra, Bridge, Liquid, the main website, and external rails. It is static public dependency data, not current chain state, custody proof, settlement proof, liquidity proof, launch status, sale access, reward eligibility, allocation, private support, or economic activation. - Acceptance paths: https://uquad.org/acceptance.html. It names what a complete-enough journey needs before public copy treats it as more than a partial proof: owner, action, cost, receipt, failure path, support path, and boundary. It does not claim every route is complete or live. - Machine-readable acceptance journey register: https://uquad.org/data/acceptance-journeys.json. It gives owner, entry condition, allowed action, quote/cost label, receipt requirement, failure path, support path, acceptance requirement, and must-not-infer boundaries for Core, Infra, provider settlement, Bridge, Liquid, and support journeys. It is static public journey data, not current route state, payment proof, settlement proof, admission proof, liquidity proof, sale access, reward eligibility, allocation, or economic activation. - Machine-readable failure matrix: https://uquad.org/data/failure-matrix.json. It gives failure class, trigger, expected public state, evidence to bring, next public check, recovery shape, and must-not-infer boundaries for stale data, replay, timeout, bad denom, missing receipt, challenged receipt, underfunded actions, unauthorized actions, stale dependencies, old metadata, stale RPC/indexer views, paused market inputs, and capacity limits. It is static failure guidance, not live drill proof, current route state, funding proof, settlement proof, admission proof, liquidity proof, sale access, reward eligibility, allocation, or economic activation. - Machine-readable recovery drill contract: https://uquad.org/data/recovery-drills.json. It gives triggers, expected public states, recovery action classes, terminal receipt requirements, public summary shapes, next public checks, and must-not-infer boundaries for chain restarts, stale metadata, relayer/RPC outages, stale oracle inputs, bad denoms, failed uploads, missing payloads, provider timeouts, host-chain stale heads, disabled signers, venue pauses, packet timeouts, duplicate receipts, stale public exports, and backup/restore drills. It is static drill guidance, not completed drill proof, live recovery proof, custody proof, settlement proof, admission proof, liquidity proof, sale access, reward eligibility, allocation, or economic activation. - Machine-readable release provenance: https://uquad.org/data/release-provenance.json. It gives release artifact classes, expected checks, main-domain release path, handoff labels, rollback shape, and local-package boundaries. It is static release guidance, not live upload proof, DNS propagation proof, current chain state, current subdomain state, custody proof, settlement proof, admission proof, liquidity proof, sale access, reward eligibility, allocation, or economic activation. - Machine-readable observability contract: https://uquad.org/data/observability-contract.json. It gives telemetry families, owner surfaces, public fields, stale behavior, alert labels, next public checks, and must-not-infer boundaries for chain liveness, export/receipt age, packet and relayer state, market/oracle inputs, Infra service capacity, Bridge host/route failures, Liquid settlement posture, and public-surface freshness. It is static telemetry guidance, not live telemetry, current block height, current transaction state, recovery proof, custody proof, settlement proof, admission proof, liquidity proof, sale access, reward eligibility, allocation, or economic activation. - Machine-readable public data catalog: https://uquad.org/data/public-data-catalog.json. It gives dataset id, owner surface, schema family, evidence class, freshness rule, stale behavior, allowed use, retention, redaction, consumer contract, and must-not-infer boundaries for the main-domain JSON files. It is static catalog guidance, not live chain data, current state, custody proof, settlement proof, admission proof, liquidity proof, external validation, sale access, reward eligibility, allocation, or economic activation. - Machine-readable reconciliation rules: https://uquad.org/data/reconciliation-rules.json. It gives public downgrade rules for owner-route mismatches, static fallback versus live routes, release package versus live domain mismatches, incomplete schemas, duplicate or conflicting receipts, denom or metadata mismatches, outside-reference scope, and broken lineage. It is static reconciliation guidance, not live chain data, route repair proof, dataset completeness, owner acceptance, external validation, custody proof, settlement proof, admission proof, liquidity proof, sale access, reward eligibility, allocation, or economic activation. - Machine-readable lineage map: https://uquad.org/data/lineage-map.json. It gives public source class, source owner, source route, transformation, display routes, freshness signal, redaction rule, aggregation rule, and lineage-break behavior for main-domain JSON files. It is static lineage guidance, not live chain data, current state, dataset completeness, owner acceptance, external validation, custody proof, settlement proof, admission proof, liquidity proof, sale access, reward eligibility, allocation, or economic activation. - Machine-readable freshness policy: https://uquad.org/data/freshness-policy.json. It gives public freshness classes, public labels, machine labels, consumer behavior, downgrade behavior, and must-not-infer boundaries for current, fallback, cached, stale, unavailable, conflicted, local-package-only, and superseded data. It is static stale-state guidance, not owner authority, live chain data, current state, route repair proof, dataset completeness, owner acceptance, external validation, custody proof, settlement proof, admission proof, liquidity proof, sale access, reward eligibility, allocation, or economic activation. - Machine-readable redaction boundary: https://uquad.org/data/redaction-boundary.json. It gives public/private classes, allowed public fields, private field classes, redaction behavior, consumer behavior, and must-not-infer boundaries for public route metadata, receipt metadata, payloads, public-rented visibility, provider labels, host-chain vault labels, financial posture, route proof, doctrine-sensitive material, and support evidence packets. It is static redaction guidance, not live chain data, payload truth, provider identity, private operating procedure, custody proof, settlement proof, admission proof, liquidity proof, external validation, sale access, reward eligibility, allocation, or economic activation. - Machine-readable retention policy: https://uquad.org/data/retention-policy.json. It gives retention, prune, tombstone, restore, and reissue classes for receipt metadata, payload access lifecycle, tombstone records, pruned datasets, owner-touch refresh, cold retention, terminal receipts, restore or reissue, and refusal notes. It is static retention guidance, not live chain data, payload access proof, payload truth, current state, custody proof, settlement proof, admission proof, liquidity proof, external validation, sale access, reward eligibility, allocation, or economic activation. - Machine-readable consumer contracts: https://uquad.org/data/consumer-contracts.json. It gives allowed-use and downgrade rules for public readers, wallets, explorers, website display, chain keepers, cross-chain importers, Infra proof/reissue services, operator dashboards, governance reviewers, external reviewers, product pricing engines, and refusal gates. It is static consumer guidance, not authority to make stale data current, open product routes, prove chain state, create economic rights, or bypass owner-surface proof. - Machine-readable data product readiness gate: https://uquad.org/data/data-product-readiness.json. It gives readiness states and checks for catalog rows, schema versioning, lineage, freshness, stale/refusal states, redaction, retention, reconciliation, consumer contracts, public wording, current evidence artifacts, and owner review. It is static readiness guidance, not authority, current-state proof, route-opening proof, product availability proof, external validation, or economic activation. - Machine-readable data stewardship questions: https://uquad.org/data/data-stewardship-questions.json. It gives standing review questions for dataset purpose, owner, producer, evidence class, freshness, failure behavior, safe inference, forbidden inference, public need, and trust-from-action. It is static review guidance, not authority, current-state proof, route-opening proof, product availability proof, external validation, or economic activation. - Machine-readable information governance: https://uquad.org/data/information-governance.json. It gives public information-state and control-domain rules for active sources, generated artifacts, deployed routes, external references, stale/superseded facts, internal-only material, non-authoritative copies, access/key lifecycle classes, change records, observability/stale-state behavior, runbooks, recovery packets, and closure questions. It is static information-governance guidance, not private procedure, credential exposure, current-state proof, owner acceptance, external validation, or economic activation. - Custody and account map: https://uquad.org/custody.html. It separates who owns, owes, holds, records, refuses, pays, or cannot touch value and state. A visible balance is not spendable until its account class says it is spendable. - Surface first-read paths: https://uquad.org/start.html#first-read-paths. - Reader paths: https://uquad.org/start.html#reader-paths. It gives direct entry points for new visitors, testers, validators, providers, builders, reviewers, security reviewers, route readers, liquidity readers, community members, and crawler/indexer readers. - Category guide: https://uquad.org/category.html. It explains QUAD as a multi-chain economic system for admitted value, verifiable work, controlled passage, and fast settlement; it also names common category misreads, proof routes, and what is not claimed. - Core path: https://uquad.org/core-path.html. It explains Core as the admitted-value and monetary-accounting surface for QUAD, including token model, supply policy, validator path, mainnet hardening gates, activation boundaries, and closed claims. - Infra path: https://uquad.org/infra-path.html. It explains Infra as the store/prove/retrieve/remember product surface for BIGHT work payments, upload, receipt verification, retrieval, contract storage, provider evidence, proof memory, pricing, and public/private payload boundaries. - Bridge path: https://uquad.org/bridge-path.html. It explains Bridge as the controlled-passage product surface for native acquisition, inventory truth, source-pool and owner-vault separation, route-output classification, host evidence, provider risk, proof receipts, refunds, surplus, and destination admission boundaries. - Liquid path: https://uquad.org/liquid-path.html. It explains Liquid as the fast-movement market surface for motion posture, quotes, orders, positions, exposure, wrappers, risk, liquidation, venue quality, endpoint contracts, settlement truth, and market-closed boundaries. - Product comparison: https://uquad.org/product-comparison.html. It compares QUAD by job and proof owner: what people may mistake it for, what QUAD actually does, what proof to check, and what is not claimed. - Data provenance: https://uquad.org/data-provenance.html. It explains how to read public data by owner, route, proof class, freshness, source/package/ deployed state, and boundary without upgrading stale, local, or bounded evidence into current chain state. - Network use: https://uquad.org/adoption.html. It explains usable public product paths, what counts as usage evidence, what still needs owner-published receipts or summaries, and what does not count as traction. Community interest, screenshots, private messages, copied claims, or public attention should not be treated as adoption, partner disclosure, liquidity, reward eligibility, or investment demand. - Public references: https://uquad.org/references.html. It explains how to read official surfaces, public repos, registry packets, explorer/indexer references, wallet metadata, audit slots, forum posts, and assistant or search summaries without inventing outside validation. - External reference path: https://uquad.org/external-references.html. It explains how to share, list, post, submit, or route QUAD outside uquad.org without spam, phishing, false-validation, or token-promo framing. Outside references should name the owner surface, phase, proof, and boundary. They should not claim listings, partnerships, rewards, market access, liquidity, external audits, or third-party validation before the source that owns that status publishes it. - Credibility inventory: https://uquad.org/credibility.html. It lists public proof handles, owner surfaces, evidence classes, pending assets, and what each handle cannot prove. - Phases and opening gates: https://uquad.org/phases.html. It explains the current stack jobs, phase order, opening-gate evidence, what readers can do now, and what remains closed. - Product state labels: https://uquad.org/status.html#product-state-labels. - Operating control plane: https://uquad.org/status.html#operating-control-plane. It gives a public triage view for Core, Infra, Bridge, Liquid, the main website, and external rails by naming current posture, next public action, and boundary without granting protocol authority, governance authority, production launch, financial reconciliation, custody authority, or economic activation. - Financial and admission inference check: https://uquad.org/verify.html#financial-inference-check. - Wallet and balance label guide: https://uquad.org/wallets.html. - Module balance flags: https://uquad.org/wallets.html#module-balance-flags. - Expected and actual denom guide: https://uquad.org/wallets.html#denom-reconciliation. - XML sitemap: https://uquad.org/sitemap.xml. - Plain summary: https://uquad.org/summary.txt. - Assistant quoting guide: https://uquad.org/llms.txt. - Static continuity path: homepage, Start, Status, Public Surfaces, Docs, Verify, Boundary, Site Map, summary.txt, llms.txt, and sitemap.xml should remain useful even when a subdomain or live feed is stale. - Crawler/indexer reading order: start with summary.txt, llms.txt, sitemap.xml, site-map.html, start.html, stack.html, surfaces.html, evidence.html, updates.html, references.html, external-references.html, credibility.html, core-path.html, infra-path.html, bridge-path.html, liquid-path.html, category.html, product-comparison.html, data-provenance.html, phases.html, sources.html, and the public JSON files listed in the data catalog, reconciliation rules, lineage map, freshness policy, redaction boundary, and retention policy. If a crawler or indexer cannot read a live subdomain route, it should quote the current state as unverifiable instead of inventing height, balance, liquidity, launch, or reward state. Plain public explanation of the project: The project is split into separate QUAD-related workstreams and public-site assets. It is not a public product, wallet path, claim page, exchange, node-earning program, or operator manual. Public purpose: QUAD exists to bring discipline to crypto value movement. It turns fragmented digital assets into observable economic state: admitted value, routed value, quarantined value, and settled value. Its purpose is not to sell exposure to Bitcoin or any other reserve asset; its purpose is to make the rule system around value admission, custody, routing, quarantine, and settlement reviewable through bounded public evidence. Core token model: - QUAD is the native Core unit. - uquad is the minimal denom published for the Core chain. - Core wallet metadata uses 6 decimals and the quad address prefix. - uquad is published as the fee and staking denom on the observable Core chain for gas, validator, and transaction testing. - stQUAD may appear as a staged wallet metadata label; it is not a live liquid-staking product, yield promise, or mainnet entitlement. - The Core token model is not a sale, allocation schedule, reward program, price model, investment product, Bitcoin wrapper, lending product, or product that sells exposure to any reserve asset. - The public model is about value admission, custody, routing, quarantine, sink/terminal state, and settlement labels. Economic activation path: - The activation page explains the right public path for minting policy, distribution schedule, mainnet economic launch, value-movement opening, liquidity surfaces, and market module activation. - Minting policy, distribution schedule, production value movement, liquidity, and market module activation are not open unless an official QUAD page says so and points to public evidence. - Activation should proceed through observation, genesis/endpoint freeze, public policy, rail verification, narrow opening, and evidence-backed expansion. - This path enables validators, reviewers, builders, and community coordinators without creating sale access, reward eligibility, allocation, or future entitlement. Public model: - The public model page is https://uquad.org/model.html. - It explains the economic model, validator incentives, governance structure, security assumptions, rollout timeline, token utility, and how Core, Infra, Bridge, and Liquid interact. - The public Readiness Office is https://uquad.org/readiness-office.html. It summarizes product gaps, technical closure, operating readiness, financial-accounting readiness, and market readiness without publishing private procedure or implying production launch. - The public Readiness Lenses page is https://uquad.org/readiness-lenses.html. It explains the executive checkpoint frame: continuity, operations, financial controls, market clarity, technical proof, information governance, data stewardship, and experience readiness. Each lens may inspect the whole stack, but no lens may erase chain boundaries. - The main website itself is being reviewed through those lenses before the chain pages are reworked. The main domain owns identity, routing, readiness language, static fallback files, public summaries, and safe claim boundaries. It does not own chain admission, settlement, balances, Bridge delivery, Infra proof meaning, Liquid finality, governance authority, payment rails, or production launch status. - Core accounts for admitted value and public economic state. - Infra provides useful work, receipts, storage, query, proof, retained state, and BIGHT-denominated service paths. - Bridge proves passage, provenance, receipts, refusal, and quarantine without forcing destination admission. - Liquid handles fast movement, positions, clearing, liquidation, explicit-law labels, and settlement requests without making motion into Core worth. - Validators are incentivized around fees, staking, liveness, correct signing, slash-risk alignment, reputation, and endpoint reliability when a chain opens those lanes; rehearsal or coordination activity has no monetary value and creates no allocation or future privilege. - Governance is described as genesis law first, narrow bootstrap operation, and on-chain or otherwise published process later; public copy should not imply private operator override of live governance. - Governance reading should start from https://uquad.org/governance.html. Proposal pages should name chain, module or surface, requested action, affected authority, threshold class, expected machine consequence, refusal boundary, vote state, failure type, emergency caution, and proof route. - Security assumptions include validator participation, key security, honest voting-power thresholds, surface-owned admission rules, and no external audit claim until a report exists. - The rollout timeline is phase-based: observe, test utility, bound movement, harden, publish policy, then open narrowly only with evidence. - Core public law mapping says Oracle observes, Market frames inputs, Treasury accounts for custody, Economics applies chain-local law, and Actions performs approved effects. Audit observes and exports summaries; it does not command Core. - The Core page has been pulled through the readiness lenses. It now frames Core as a constrained economic machine with a public promise, standalone mode, financial boundary, and reader journey. Core must keep local observation and admission discipline even when Infra, Bridge, Liquid, relayers, providers, or the public website are stale or unavailable. - Infra public memory says receipts are service evidence, not universal truth or Core admission. Later proof, lookup, reissue, reconstruction, retention, linkage, and challenge-history services are paid work lanes. - Bridge public transport posture says record-only IBC readiness is testing evidence, not a live relay promise. Live IBC remains blocked until keeper-owned sequence consumption, message execution, IBC state, capabilities, packet planning, ack/timeout observation, relayer service, and client/connection/channel handshakes exist. - Bridge native acquisition posture says intent, quote, route, held-asset pool labels, reserve and host-fee ledger categories, route-output classification, host-account assignment, and funding evidence can be recorded without claiming AMM law, wrapper minting, sale/redemption/swap access, destination admission, reserve backing, or live counterparty bank debit. - Liquid public authority posture says settlement is the only final balance-truth owner. Position, wrapper, clearing, reserve, Bridge intake, Infra import/export, public views, and Engine output must not mutate balances directly. Roadmap: - The roadmap is phase-based, not date-based. - Current public labels are Core chain live as `quad`, Core evidence-bound hardening, Purpose published, Core token model published, Economic Activation path published, and stronger economic-opening claims still bounded. - Next roadmap work is Core hardening, chain stability, endpoint posture review, registry/listing readiness, public economic policy, and validator review. - The next candidate track includes public metadata review, CoreExport/public-indexer feed checks, endpoint posture review, market-route coverage, and post-reset proof before outside submissions. - Later roadmap work is narrow economic opening only after public evidence exists, with dated updates and surface-owned status. - The roadmap does not open sale access, airdrop eligibility, reward claims, production value movement, live liquidity, or market module activation. Why use or review QUAD: - It exposes public Cosmos SDK chain state, chain metadata, validators, and status labels before asking for trust. - It separates Core, Bridge, Infra, and Liquid so accounting, movement, storage/evidence, and fast execution are not blended into one vague surface. - It labels whether a claim is described, implemented, observed, staged, or live. - It gives validators, reviewers, and builders a plain path to inspect readiness without connecting a wallet or entering a seed phrase. - A reasonable first review path is: observe Core, read Stack Overview, read Purpose, check the Core token model, read Roadmap and Activation, then use Community for chain coordination or docs feedback. - Network-use and partner labels remain empty until a real approved public source exists. Public project map: - website: public information, crawler armour, summaries, stack overview, product comparison, data provenance, proof archive, credibility inventory, Core market path, Infra product path, glossary, status pages, boundary page, source-of-truth map, fees and finality guide, action lifecycle guide, obligations guide, integrator guide, operator guide, reader-facing site map, XML sitemap, and launch exports - quad: QUAD economic-chain workstream and Core chain observatory - infra: separate workstream for evidence, witness, verifiable storage, memory, retained state, BIGHT work payments, receipt verification, hard-collateral reserve rail labels, and Infra public observation - infra normal contracts: public product-contract receipt material for anchor, retention, query, and proof surfaces; private chain logic is excluded - infra hook packets: opt-in, contract-bound packet returns for accepted contract work; not a global scanner, accusation tool, or automatic enforcement authority - infra public hooks: bounded public opt-in contract-work packet envelopes, host-chain requirements, acknowledgement, review flow, and local-policy boundaries; private verifier logic is excluded - bridge: boundary movement, quarantine-facing design, closed app-wiring, mounted-runtime execution work, and receipt surfaces - liquid: parallel execution and market-facing workstream with static endpoint contracts, explicit-law audit staging, and public labels only where safe System doctrine: - The stack is coordinated, not merged. - The stack overview page at https://uquad.org/stack.html gives the one-sitting public map: Core protects admitted value, Infra proves useful work, Bridge carries across boundaries, and Liquid moves under local settlement rules. It also separates observable state, product-active paths, published boundaries, staged/local evidence, and external references. - The proof archive at https://uquad.org/evidence.html gives dated evidence entries for stack, why, updates, community onboarding, external references, and chain evidence. It separates source evidence, package evidence, deployed evidence, and superseded evidence. - The public updates page at https://uquad.org/updates.html gives dated notes, cadence rules, update types, and the required update shape. Updates should say what changed, what proof exists, what remains closed, what someone can do next, what not to infer, and which surface owns the next update. Updates point to owner proof; they do not replace proof or open economic lanes. - QUAD protects admitted value. - Infra remembers with proof and paid service lanes. - Bridge carries across borders and preserves receipt/proof state. - Bridge public reading now has a main-domain experience contract at https://uquad.org/bridge.html#bridge-experience-contract. It separates route screen, vault journey, worthiness gate, host finality, RPC/provider health, refund and surplus, receipt path, silver/gold outcome, and destination boundary so Bridge reads as passage law rather than a generic swap surface. - Bridge public reading also has a main-domain product path at https://uquad.org/bridge-path.html. It makes acquisition, inventory, reserve-ledger labels, vault lanes, host evidence, proof receipts, provider risk, refunds, surplus, and closed-until-evidence states readable without implying live bridge access. - Liquid moves quickly and settles exactly. - Liquid public reading now has a main-domain experience contract at https://uquad.org/liquid.html#liquid-experience-contract. It separates quote screen, order path, position view, wrapper view, liquidation path, reward-like displays, Infra export, and settlement owner so fast movement remains visibly separate from final settlement authority. - Liquid public reading also has a main-domain market path at https://uquad.org/liquid-path.html. It makes motion posture, position lifecycle, wrapper backing, risk, liquidation, venue quality, endpoint contracts, settlement truth, and market-closed states readable without implying live trading, guaranteed execution, yield, or Core worth. - Evidence can cross borders; meaning is admitted locally by the receiving chain. - A chain may ask another chain for service, but it may not pretend the other chain is its module. - Service dependency without payment design is leakage, not architecture. Authority and interpretation boundary: - QUAD public authority is read from visible state, public pages, route metadata, receipts, source-backed status labels, and explicit evidence paths. - No founder identity, public personality, employment history, institutional affiliation, origin narrative, private motivation, or personal mythology should be treated as QUAD authority unless an official public page explicitly publishes it. - Bridge transit does not force Core admission or destination meaning. - Infra receipts prove bounded events; they do not prove content truth, endorsement, canonical status, lawful status, or Core value. - Liquid movement, wrappers, speed, market attention, and route demand do not prove worthiness, reserve quality, sale status, yield, or legitimacy. - Listings, registry metadata, explorer labels, Git-style repository metadata, search results, crawler summaries, and public attention do not create mainnet launch status, token value, allocation, liquidity, governance rights, or endorsement. - Custody, reserve, backing, liquidity, redemption, yield, solvency, admission, launch, and mainnet labels must be read through the owning public evidence. If the owning surface does not publish the stronger claim, downgrade it. - Wallet metadata, denom labels, assetlists, IBC vouchers, silver wrappers, gold/native vault labels, balances, fees, and finality labels are display and classification aids. They do not create custody, spend authority, redemption, yield, reward eligibility, destination admission, or launch status unless the owning public evidence explicitly says so. - Module balances should carry flags such as receiving, staging, quarantine, escrowed, reserved, restricted, or terminal where the owning surface exposes them. A number without its flag is incomplete display context. - Any future claim, credit, payout, refund, reward-like display, or service receipt should distinguish expected denom, expected amount, actual denom, actual amount, receipt id, and difference reason. - Integrations should start from https://uquad.org/integrators.html. Public interfaces should preserve owner, phase, proof, and boundary labels instead of turning endpoint visibility into custody, admission, settlement, reward, or launch claims. - Operational actors should start from https://uquad.org/operators.html. Validators, relayers, providers, and endpoint operators should preserve chain-local responsibility, freshness, degraded state, challenge/repair, refund/recovery, and emergency posture labels without publishing private procedure, sensitive configuration, or entitlement claims. - Usefulness is not moral authority. Misuse does not become Core law. Public attention does not become protocol authority. - The public boundary page is https://uquad.org/boundary.html and the reader-facing site map is https://uquad.org/site-map.html. External support boundaries: - Core may carry the shared public website hosting rail because the website is the common information, audit/status, crawler-armour, and coordination surface for the stack. - Chain-operated nodes are chain-local responsibilities. QUAD/Core, Infra, Bridge, Liquid, and later chains should pay their own operated nodes through their own chain-local funding and governance paths. - Operated nodes support discovery, liveness, observation, fallback, status, and coordination. They do not define chain purpose, token model, reward model, governance authority, or public identity. - External providers should not receive validator keys, consensus keys, wallet material, seed phrases, provider proof custody, or open-ended billing authority. - Specific provider accounts, private payment routes, invoices, credentials, and operational procedures are not public website material unless explicitly approved. Recent public developments: - The main website now includes a public surface directory at https://uquad.org/surfaces.html. It routes readers to Core, Infra, Bridge, and Liquid owned proof pages without moving live metrics onto the main homepage. - The main website now includes support playbooks at https://uquad.org/playbooks.html. They explain common public failure paths such as stuck transactions, wrong denoms, unpaid quotes, stale routes, pending invoices, failed uploads, delayed receipts, and provider issues without asking for secrets or expanding receipt meaning. - The main website now includes a continuity and handoff guide at https://uquad.org/continuity.html. It explains degraded surfaces, release and rollback labels, continuity packet shape, public handoff rules, and downgrade behavior when a chain, endpoint, subdomain, provider, or release artifact is stale. - The main website now includes public contracts at https://uquad.org/contracts.html. They explain public contract shape, schema families, versioning rules, stale and missing values, consumer rules, endpoint boundaries, and must-not-build conditions for public data consumers. - Machine-readable interface contracts are at https://uquad.org/data/interface-contracts.json. The file gives static public schema families, status labels, public routes, evidence classes, replay domains, timeout policies, and must-not-infer boundaries for Core, Infra, Bridge, Liquid, and main-site release contracts. It is not live interop proof, current chain state, custody proof, admission proof, settlement proof, liquidity proof, launch status, sale access, reward eligibility, allocation, private support, or economic activation. - Local source-folder evidence has been checked for Core, Infra, Bridge, and Liquid. Not all of this evidence is deployed on the public subdomains yet; subdomains remain presentation surfaces and can lag the source folders. - Core public routes now include supply-policy, treasury-admission, economic-activation, token-model, readiness, official purchase path, blocks, validators, chain metadata, endpoint contract, and static indexer pages for public Core review. These are public law and observation surfaces, not sale access, redemption, unrestricted public movement, or economic activation. - Infra public routes now include compare, failures, and restart pages in addition to wallet, quote-first BIGHT purchase, upload, verify, retrieve, contracts, contract work, balances, reserve, receipts, proof, status, and public data. The failure and restart pages turn bad paths and reset conditions into named public states. - Bridge public routes now include live-status JSON, reconciliation cards, relayer-health JSON, and provider-change activation contract data beside the acquisition, ledger, inventory, vault, gate, counterparty, host-evidence, proof, data, and status pages. Public self-serve movement remains lane-gated. - Liquid public routes now include status, proof, roles, readiness, endpoint-contract, explicit-law JSON, motion/position JSON, production-profile, protocol-USDC, public data, and stats routes. Liquid reports live status, signed lifecycle smoke, settlement acknowledgement posture, motion-summary contracts, route-bound production-profile evidence, service-promotion blockers, and public market-closed labels; it does not claim live market activity. - Core local evidence now includes a freeze-candidate manifest, production-topology manifest, relayer-gas-float manifest, static indexer page, Bridgechain receiver rehearsal, and native-acquisition acknowledgement law. These are hardening gates, not launch readiness. - Infra local evidence now includes the whole-product evidence gate, BIGHT paid mint gateway, public quote endpoint, deposit-publication gate, reserve yield ingress and Bridge-bound remittance acknowledgement receipts, public intake tests, contract-work loop, and public ledger/balance/evidence labels. Money-bearing and cross-chain proof still gate whole-product or freeze claims. - Bridge public evidence now includes dedicated product pages for acquisition, ledger, inventory truth, vault lanes, production gates, counterparty boundaries, host evidence, proof, data, and status. This is a public product map, not public value movement. - Bridge local evidence now includes host-lane drill funding law, host-contract freeze/audit law, fresh live-RPC refresh records, native acquisition order records, record-only IBC readiness, and long-run soak posture. These do not open public value movement. - Liquid local evidence now includes Comet/ABCI service health, signed position lifecycle smoke, stable query JSON, motion proposal contracts, sustained production-profile evidence, service-promotion blockers, relayer-gas launch blockers, and authority separation. This does not open market activity. - The public Model page is visible at https://uquad.org/model.html. It explains the economic model, validator incentives, governance structure, security assumptions, rollout timeline, token utility, and how Core, Infra, Bridge, and Liquid interact without opening sale access, allocation, rewards, production value movement, or market access. - The public Readiness Office is visible at https://uquad.org/readiness-office.html. It summarizes the current product, technical, operating, financial-accounting, and market gaps as public orientation only. It does not open mainnet, value movement, liquidity, sale access, reward eligibility, allocation, market access, or production activation. - The public Readiness Lenses page is visible at https://uquad.org/readiness-lenses.html. It maps the C-suite checkpoint frame into bounded public language so readers can see how continuity, daily operation, finance, market clarity, technical proof, information ownership, data stewardship, and user journey checks shape the website and readiness claims. - The main website lens pass is now public: Start explains what the main site owns, Verify explains how the main domain is checked, Boundary explains what the website cannot become, and Status explains static continuity, surface ownership, stale-state behavior, and release discipline. - The Verify page now includes a receipt reading path. It explains what Core, Infra, Bridge, Liquid, and main-site receipts can prove and what they cannot prove. - The Start page now includes direct first-read paths for QUAD/Core, Infra, Bridge, Liquid, and the whole stack. - Core, Infra, Bridge, and Liquid pages now include page-reading rules that separate each surface's purpose, posture, public-stat owner, and non-inheritance boundary. - Status now defines shared product-state labels: live, testnet/rehearsal, planned, disabled/closed, stale, and not-yet-public. - QUAD registry/listing metadata is staged for review, not mainnet submission. - QUAD Core wallet metadata is visible at core.uquad.org/chain.json, and the public endpoint boundary is visible at core.uquad.org/endpoint-contract.json. - QUAD Core is live as `quad`; third-party indexer/listing work still depends on the receiving indexer's checks of current genesis, endpoint, and metadata material. - QUAD Core now has a public law map for truth order, audit observation, custody accounting, route handoff, worth gates, quarantine, sink, and bounded supply posture. - QUAD Core now has a main-domain experience contract at https://uquad.org/core.html#core-experience-contract. It explains public value posture, Treasury state, invoice intake, External Affairs payment posture, claim/credit display, quarantine, governance slots, failed actions, and chain health without making those labels spendable money, private override, reward access, or launch status. - QUAD Core now has a public lens pass on the main site: public promise, standalone mode, Core-through-the-lenses, financial boundary, and reader journey. It emphasizes that Treasury is custody/accounting state, uncertain imports are refused or quarantined, and issuance, route volume, expected use, unpaid invoices, sibling services, or unrealized returns are not spendable money. - QUAD Core now has a Bridgechain receiver rehearsal path that stages delivered Bridge-origin value through x/bridge to Quarantine first, preserving delivery-not-admission. The Core receipts page and delivery-index JSON now expose quarantine-only receiver receipts for review. - Infra is active as a verifiable-storage product surface with BIGHT wallet support, quote-first BIGHT purchase, upload quote, receipt verification, query/download quote, contract accounts, contract-work packet staging, balances, receipts, proof, public data, and live public chain labels on infra.uquad.org. - Infra now has a main-domain experience contract at https://uquad.org/infra.html#infra-experience-contract. It explains metadata-light upload, upload, retrieve, contract path, receipt memory, provider journey, challenge, repair, and cross-surface meaning without making Infra a generic cloud drive, raw compute reward system, Core admission engine, Bridge finality source, Liquid settlement source, or payload-truth oracle. - Infra now presents receipt memory as product work: original receipts are included with accepted work; later lookup, certified reissue, evidence-bundle reconstruction, retention proof, host-chain linkage proof, challenge history, and bulk/API access are BIGHT-paid services. - Bridge has live product runtime evidence: resident node posture, IBC transport proof, Bridge-QUAD Hermes transport, source-pool receipts, 14 protocol/source-pool asset rows, quote-first PAXG/USDC/ATOM/STRD/NTRN lane shapes, owner-vault allocation proof, Core acknowledgement evidence, Infra export wires, held-asset pool labels, reserve/fee ledger categories, route-output classification, host-gas accounting, and proof packets. Current amounts belong on the Bridge ledger and Bridge-owned data files. It shows passage and boundary posture, not generic public bridge access. - Bridge IBC readiness and transport proof should be read narrowly: transport and receipt evidence can exist without generic public bridge access, destination admission, wrapper minting, redemption, or market liquidity. - Bridge native acquisition order records are intent and sourcing evidence only. They do not claim host execution, wrapper minting, AMM behavior, sale/redeem/swap access, destination admission, or live counterparty bank debit. - Current Bridge Ethereum-mainnet evidence is lane-specific host/source-pool and owner-vault proof. It should not be summarized as generic production bridging, destination admission, sell-side support, redemption, wrapping, swapping, live liquidity, or public self-serve bridge access. - Liquid has a dedicated public surface with status, proof, roles, readiness, endpoint-contract, explicit-law JSON, motion/position JSON, production-profile, protocol-USDC, public data, and stats routes. It now has runtime motion logic, local meaning records, a concrete CometBFT ABCI adapter, one-second motion engine smoke evidence from 2026-06-01, route-bound production-profile evidence, and authority-separation labels. It does not claim live market activity. - Liquid launch blockers remain publicly bounded: consensus-backed stores, state roots, keeper-owned authority, relayer gas floats, and live endpoint checks are still required before Liquid is chain-ready. - Engine is Liquid/Bridge-adjacent hot-path proposal tooling. It is not a chain, settlement truth, Core authority, admission authority, governance, payment approval, or final routing authority. - Infra normal contract material may be linked by official public pages for product receipt envelopes and downstream trust boundaries; this summary does not publish private repository or account details. - Infra work pricing is visible at https://uquad.org/infra-pricing.html. It presents USD-equivalent target values first and explains that BIGHT is the work-payment unit converted at accepted quote-time value. It separates anonymous MiB-billed upload intake, GB-priced contract-account storage, normal service windows, service-tier boundaries, and security opt-in packet-return economics. It is a public reference and quote guide, not an allocation path, fixed redemption value, yield claim, or reward claim. - Infra contract-work hook packets are opt-in, contract-bound, and host-policy-bound. - Infra public hook material may be linked by official public pages for packet envelopes, acknowledgement, and host-chain review; this summary does not publish private repository or account details. - Infra public intake includes BIGHT wallet support, quote-first BIGHT purchase, upload quote, receipt verification, query/download quote, balances, receipts, and public intake APIs. - Bridge product runtime is active and now carries live route proof for named lanes; public self-serve movement remains lane-gated. - Liquid app-shell posture, endpoint-contract exports, runtime motion logic, local meaning records, production-profile evidence, service-promotion blockers, and explicit-law audit staging are public orientation; live market activity is not claimed. - Engine real-test readiness evidence can be described as hot-path tooling evidence only. Chain-owned validation remains required before any Engine output becomes public chain state. The public goal is to prove liveness, separate chain boundaries, public receipts, and status visibility without publishing validator secrets, operator procedure, exploit paths, or private mechanics. Canonical public surfaces: - uquad.org - core.uquad.org (Core chain observatory) - infra.uquad.org (Infra-specific public surface) - bridge.uquad.org (Bridge-specific public surface) - liquid.uquad.org (Liquid-specific public surface) - About - Boundary - Site Map - Public Surfaces - Purpose - Economic Activation - Model - Readiness Office - Roadmap - Network Use - Core - Bridge - Infra - Infra Work Pricing - Liquid - Genesis - Status - Blocks - RPC boundary - /summary.txt - /llms.txt - network-use labels for traction and partner disclosure state uquad.org is not: - MQUAD - a wallet - a token sale - an airdrop claim page - an airdrop-link project - an investment opportunity - an incentivized testnet - a reward eligibility page - a survey platform - a data-collection platform - program monitoring/evaluation software - Population Council Consulting tooling - Dataverse/survey-hosting/login infrastructure - research data management software - a drone company - Quad Nuclear Verification Partnership - a nuclear verification project - an accessibility/WCAG compliance project - Urdu Question Answering Dataset - UQuAD NLP dataset - UniQuad or a university education hub - an Indo-Pacific diplomatic Quad initiative - a government project - UQD or an unrelated blockchain explorer - Universal Quantitative Asset Data - a generic DePIN/AI chain - an AI training-data network - an AI task-processing network - anti-big-tech decentralized AI as public identity - an IoT protocol - a DePIN sensor or hardware-reward network - raw compute rewards - GPU/CPU-cycle token rewards - a Bitcoin-style Proof-of-Work or mining chain - a quad-tree-based system by implication - a mortgage, loan, bond, accounting, or debt-management product - financial advice or a banking product - a whitepaper/litepaper expectation by default - Telegram/when-moon community framing - node setup to earn tokens - a military or weapons project Future compute workloads may exist in the broader stack, but QUAD is not currently presented as a DePIN, AI, GPU-reward, data-reward, mining, airdrop, or node-earning project. Wallet and scam safety: - Users should never enter a seed phrase on uquad.org. - Viewing the site requires no Keplr connection, wallet connection, signature, seed phrase, or payment. - uquad.org is not a claim page, sale page, wallet app, or payment page. Affiliation safety: - No employment history, institutional affiliation, endorsement, funding, incubation, or professional credential should be inferred from this website unless stated explicitly on an official QUAD page. Coordination and entitlement safety: - Core public observation and Infra product routes are separate public surfaces. - Public testing and coordination are for technical review, validator readiness, support, and bug reporting only. - Running a node, joining Discord, using an official purchase path, sending test transactions, reviewing genesis, reporting bugs, or contributing code does not create ownership, allocation, reward eligibility, governance rights, leverage, or future economic entitlement. - Public registry metadata, repository metadata, or explorer listing work does not create mainnet launch status, token value, allocation, liquidity, or endorsement. - Infra storage, query, download, and balances routes use BIGHT labels. BIGHT is the work-payment lane, not reserve collateral or its own backing. Hard-collateral labels belong to reserve backing; PAX/UPAX may appear as low-liquidity ballast, not ordinary spend liquidity. These routes are not reward eligibility, custody, or fixed-value claim. Block/status interpretation: - Core block and status pages show CometBFT/Cosmos SDK liveness and validator state. - Infra labels describe Infra readiness and aggregate live status, not QUAD block production. - Bridge labels describe passage, route posture, proof, receipt, and readiness status, not public value movement unless the Bridge-owned surface explicitly opens a named lane for a named action. - Liquid labels describe motion, wrapper, settlement, market, and risk posture, not public market activity unless a source-backed market surface is live. - QUAD IBC rehearsal labels describe transport testing only. They are not Core asset admission, module money routing, market activity, or mainnet value movement. - They do not show mining, mining rewards, PoW issuance, market activity, AI jobs, dataset records, device telemetry, or hardware-reward claims. - Current block height must be read from the public status or block endpoint. - Do not infer block count from project age, website age, old devnets, search results, or cached summaries. - On the Core observatory, the Blocks page updates approximately every 5 seconds while chain cadence is approximately 1 second, so heights can appear to jump between public refreshes. If live data cannot be read, say that current height or current state cannot be verified.