Virtual Infrastructure Assets · VIA.miami
A municipal system in which residents hold their own identity, the county's core systems cannot be written to from the public side, and every interaction leaves a receipt the resident keeps and the public can replay.
Not a description of a system. The system, running in a sandbox, with the chains it stands on open for inspection.
Live on this host
A zero is a real zero. Source: /api/stats · replay: /api/receipts/verify
Network topology
A wallet the resident holds. It carries their identifier, the credentials issued to them and the receipts of every interaction. Keys are generated on the device and never leave it — there is no escrow for anyone to compel. Try it: /app creates one in your browser.
An identifier for one municipal service, anchored to a namespace root that exists on three public chains. It evaluates eligibility against its own published rules, issues the credential, emits the receipt. Authoritative for its service and nothing else.
The three pillars
Licences, permits and registrations are issued by a G-code as non-transferable credentials in the resident's own wallet. Where a fact must be proved, the resident proves that single fact — of residency, of an active licence — without disclosing the record behind it.
Every interaction emits a receipt into a chain that commits to the one before it. The resident holds the record of their own dealings with the county; the public can replay the chain without a login or a records request.
Resident wallets are multi-asset: bank rails for fiat, regulated stablecoins, and purpose-built tokens for transit, event access or civic participation. Settlement is tripartite — a digital lock, a physical lock, and an orchestration layer that enforces the rules and never holds the funds.
Design laws
Runs on public verification data. No appropriation, no software on county systems, no vendor lock-in. The county can walk away and lose nothing it started with.
Public verifiers and resident portals can read status but are structurally unable to write to origin county databases. The path a ransomware crew looks for is not hardened — it is absent.
A summary, a press release or a marketing claim is not evidence. Only primary documents and signed hashes count. That rule binds this site too.
Every number, credential or root on this site ships with the query that produced it. Truth by recomputation, not by assurance.
Status
| Item | State | Detail |
|---|---|---|
| Sandbox system | Running | Resident wallets, department G-codes, credential issuance, single-fact presentation, attribution and a replayable receipt chain — live on this host, invented parties only. |
| Namespace layer | 75 roots, 3 chains, full lineage | Anchored on the XRP Ledger (validated), minted on Solana twice (11 and 14 June, the second run with on-chain names), issued on Stellar for 7 roots from locked issuers. A batch sweep on 25 June burned the Solana units; the mint accounts, anchors and Stellar assets stand. Every step is re-verifiable from /namespaces. |
| Pilot design | One department | Scoped as a single-department pilot, one service, measured before anything widens. Department keys move from the sandbox into that department's own key custody on day one. |
| Custodian | Not yet named | Tripartite settlement requires a contracted custodian in the county's own name. None is named until one is engaged for a specific pilot. |
| County adoption | None | Miami-Dade County has not adopted, procured, endorsed or contracted this platform. This host is offered for review and demonstration. |
| Independent audit | None | No third-party security audit exists for this work yet. Sandbox code is demonstration code until an audit says otherwise. |
18 September
Chairman Elijah John Bowdre · Miami-Dade Digital Commission