MILICORE
Digital Assets · Provable Operations

Run stablecoin operations you can prove — issue, mint, move, swap and settle under enforced authority.

Self-custodied. Chain-portable. Cryptographically governed. Wallet authority is created in-browser, and every governed operation is committed to a verifiable audit record.

Stablecoin
Name
Settlement chain
EVM
Base · Polygon · Kaia
Shared EVM control model; chain-specific assets and gas balances.
High-performance
Solana
Primary demo rail; low-cost token settlement and separate fee payer model.
Sponsored / gasless-native
Sui
Native sponsorship patterns and canonical USDC support.
Institutional cross-border
XRPL
Issued-currency model, payments and native exchange primitives.
Self-issued + USDT settlement
TRON
TRC-20 issuance and USD₮ settlement with delegated network resources.
Outstanding Supply
—
Attested Reserves
—
Backing Ratio
—
Ledger Height
0
Chain Integrity
Verified

Institutional treasury flow, end-to-end

Fiat in → mint → transfer → redeem. Each step commits a signed, hash-linked record — the provable trail runs the full lifecycle, not a monthly reconciliation.

STEP 01
Fiat received
Custodian attests reserve inflow
STEP 02
Mint
Issue tokens against backing
STEP 03
Transfer
Settle to counterparty
STEP 04
Redeem
Burn tokens, release fiat

Run the flow

Live commit

At this amount the transfer crosses the dual-control threshold and will require a second signature — the flow pauses for approval, exactly as policy dictates.

Position

Derived from ledger
Reserve balance (fiat)$0
Tokens outstanding0
Treasury token balance0
Counterparty balance0
Backing ratio—
The redeem step burns tokens and releases the matching fiat in a single committed record — solvency stays provable at every point, not just at attestation time.

Mint · burn · transfer

Every operation is an authorized, signed, committed record. Policy is enforced before commit — an operation that violates backing, velocity, or authorization never reaches the ledger.

Mint

Issue

Requires attested reserves ≥ resulting supply × ratio, and a paired proof-of-backing record.

Transfer

Move

Burn

Redeem

Last committed record

Signed & hash-linked
No operations yet. Mint, transfer, or burn to commit the first record.

Governed asset conversion

Milicore is not the liquidity venue. It governs who may swap, which assets and rails are permitted, what quote was authorized, and what settlement instruction was committed.

Build swap instruction

Cross-asset · cross-rail
→
Choose the route and request a quote. The quote itself is hash-committed before authorization.

Milicore controls

Before execution
Treasury authority✓ required
Dual controlAbove policy threshold
Asset / rail allow-list✓ enforced
Quote commitment✓ SHA-256
Execution modeSigned demo instruction
For a public single-HTML demo, sponsor private keys are intentionally absent. The generated customer authority still signs a real cryptographic instruction; a funded-wallet or sponsor adapter can broadcast the same approved instruction on-chain.

Last swap authorization

Provable instruction
No swap authorized yet.

Enforced multi-party authorization

Dual-control, made cryptographic. Initiator and approver each sign the operation itself — the approval authority is a signature on the committed record, not a line in a log you have to trust.

Policy

Enforced & committed
Approval allow-list (keys permitted to approve)
A key not on the allow-list cannot approve, even with a valid signature. Enabling the initiator as an approver is rejected at commit — dual-control requires two distinct authorities.

Pending approvals

0 queued
Nothing pending. Initiate an operation above the threshold to route it here.

Two-signature record anatomy

What "provable approval" looks like
Commit a dual-control operation to inspect its two independent signatures over the same record hash.

Provable reserves

Reserve evidence is committed alongside issuance. Every mint links to a custodian-signed reserve record, so the represented backing ratio and authorization history can be verified on demand rather than reconstructed from a periodic report.

Solvency

Live
Attested reserves$0
Outstanding supply0
Backing ratio—
Solvent—

Attestation vs. the monthly PDF

Contrast
PDF attestation

Point-in-time. Signed by a person, not a key you can check. Stale between reports. You trust the issuer's word on the reserve balance.

Committed proof

Per-mint. The custodian's key signs each reserve-evidence record, and anyone can recompute the represented backing ratio from the ledger at any time. The ledger proves the committed evidence and authorization; independent verification of the underlying cash depends on the reserve source.

Reserve attestation ledger

Custodian-signed
SeqEventΔ ReserveAttestorRecord hash

Settlement

The operation settles on your chosen chain, while the Milicore ledger remains the canonical governance and audit record. Authorization, policy evidence and reserve evidence are committed independently of the settlement rail, so the control history remains portable across chains.

Select an operation

From the committed ledger

Settlement reflection

One chain · one truth

The reference is a deterministic SHA-256 of the ledger record hash and the chain identifier — a real, reproducible pointer, not a simulated on-chain transaction. Switch the settlement chain in the top bar and the ledger hash above does not move; only the settlement pointer does.

Create a self-custody wallet

A cryptographically secure private key is generated in your browser and never sent to a server. Chain-native addresses are derived for the supported settlement rails, creating the self-custodied authority that authorizes and receives governed operations.

Generate wallet

Loading libraries…

🔒 Key generation runs locally with audited @noble/* primitives. secp256k1 and Ed25519 addresses are derived in-browser; close the tab and the private key is gone.

Wallet

Self-custodied
No wallet yet. Pick a network and generate.

What the auditor sees

Every mint, burn, transfer, and approval as a signed, hash-linked record — independently verifiable from public keys alone. This is the whole ledger. Try to change one number and watch the chain reject it.

Ledger

SeqTypeDetailSignersprevHashbodyHashStatus
Empty ledger. Run operations to populate.

Tamper test

Break it on purpose
A tamperer can recompute the altered record's own hash — but cannot forge the signatures (no private key) and cannot fix the prevHash link in every downstream record. Both defenses fire. Run "Verify entire ledger" after altering.

Mutable log vs. this ledger

The claim
Mutable log

A row in a database. An admin, a bug, or an incident can change it silently. The regulator takes your word that it wasn't touched.

Signed hash-chain

Each record seals the one before it. Any change breaks a signature or a link, visibly, forever. The regulator verifies instead of trusting.