QUAD Testnet observatory.

core.uquad.org is the bounded public observatory for QUAD Core testnet state.
QUAD means Quantitative Universal Amortisation Dollar: a rule-driven Cosmos SDK
economic-chain project. This surface shows live chain status, block movement,
validator visibility, ledger records, module balances, faucet state, wallet
metadata, optional testnet delegation metadata, freeze-candidate readiness
posture, and the public RPC boundary.

The static indexer page at /static-index is a plain HTML classification surface
for search indexers, AI summaries, wallets, explorers, and cautious readers. It
contains stable chain identity, phase, chain facts, live observation links, and
classification guardrails without requiring JavaScript.

QUAD Core is in mainnet hardening and candidate-soak observation. This public
surface is still a testnet observatory for quad-testnet-1; it is not a mainnet
launch claim or final freeze declaration.

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.

This surface is for QUAD Core testnet observation only. Infra, Bridge, and
Liquid are separate chain surfaces with their own public pages and economies.

The Core homepage is an orientation page. Dense account, transaction, RPC,
validator, balance, and readiness detail belongs on the page that owns it.

Testnet balances and faucet funds have no monetary value. They do not create a
token sale, allocation, reward, governance right, leverage, ownership claim, or
future entitlement.

Testnet delegation and testnet mint-collateral transactions are optional test
transaction paths for funded wallets or rehearsal actors. They do not create
reward eligibility, ownership, governance rights, allocation, monetary value, or
mainnet preference.

The public pages may show chain height, sync state, recent blocks, transactions,
tracked balance labels, route flags, validator status, genesis, wallet metadata,
and public RPC routes. They must not publish private module law, private
operator procedure, credentials, exploit-sensitive timing, or hidden gates.

The endpoint contract at /endpoint-contract.json lists static pages and public
RPC route boundaries. It is route metadata, not a claim that a transaction,
balance, or module state has economic value.

Public registry metadata, GitHub metadata, or explorer listing work does not
create mainnet launch status, token value, allocation, liquidity, or endorsement.

Never enter a seed phrase on this site. Never pay for testnet access.

The Core boundary page at /boundary states the non-inheritance rules for this
subdomain. Core public observation is read from visible state, published route
metadata, and explicit page text. It does not rely on a founder, operator
identity, public personality, unpublished interpretation, origin story, or
personal reputation.

Bridge transit, Infra receipts, Liquid motion, wallet listings, crawler
summaries, third-party pages, search snippets, public attention, or market
behaviour do not create Core admission, Core value, Core governance, mainnet
status, or launch readiness unless the Core surface explicitly states the Core
effect.

Useful infrastructure can have real-world consequences, but usefulness is not
endorsement and misuse does not become Core law. Core should be described by
visible constraints, refusal rules, and observed state, not by mythology,
ideology, charisma, or operator discretion.