Hira reconciles your fund register and reserve instructions against onchain supply — every mint, burn, and redemption — so drift surfaces per event, not per quarter.
For tokenized funds, treasury-product issuers, and fund administrators that own their contracts.
The assets are institutional now. The failure mode is still an admin key and a stale snapshot.
Detective controls on the four failure modes that actually take tokenized assets down. Hira monitors and flags — your preventive stack stays in the settlement path.
Every token created onchain must trace to a mint your back office emitted — an unmatched mint raises an exception the moment it settles.
Explore the incident walkthroughSupply, reserves and register are three ledgers that drift silently — Hira checks them against each other on every event.
Explore parity policiesA redemption is clean only when the onchain burn matches your books — stuck or oversized ones surface with a clock on them.
Explore the exception modelWhitelists are enforcement, not evidence — Hira independently verifies holders stay eligible and every upgrade maps to an intended admin.action.
Explore admin controlsA parity breach that lives in a Slack thread dies in a Slack thread. In Hira, every breach opens as an exception — assignee, severity, SLA countdown, append-only record. When the auditor asks what you knew and when, the answer is already written.
Explore the exception modelBetween attestations, drift accumulates: a late burn, a misposted reserve movement, a lapsed eligibility. The board turns that backlog into columns, so you walk into every attestation with the exceptions closed and the working papers written.
See how exceptions are workedA single unauthorized address called mint on Gala Games’ token contract and created five billion GALA — roughly $200 million — in one transaction. No contract bug: the mint function did exactly what it was told, by an address whose admin access nobody had revoked. Around $21 million was sold before the address was blocklisted.
Real incident. Illustrative detection — Hira did not monitor this system.
Detection here assumes the issuer’s backend was instrumented — the point is the mechanism: an onchain mint with no first-party instruction is undetectable to chain analytics, and unmissable to reconciliation.
You already log every mint instruction and reserve movement internally — track() just gives that log a second reader. Nine typed event types, decimal-string amounts, server-side only; instrument it in days while your issuance stack is still being built, not retrofitted after launch.
Read the SDK docshira.track('reserve.snapshot', { reserveBalance: '412874390.55', circulatingSupply: '412110204.00', custodian: 'bny-mellon', attestationRef: 'ATT_2026Q2_F1', correlationId: 'rs_20260705_0900', });
Two feeds. Your backend emits events through one server-side track() call — payouts, transfers, mints, redemptions, reserve moves, admin actions. Hira reads the chain independently and reconciles the two, then evaluates every event against your policies: thresholds, ratios, velocity, sanctions. Anything that crosses a line opens an exception with a named owner and an SLA clock.
Keep them — they screen counterparties against public chain data, and they’re good at it. They’re structurally blind to your own operations: whether a mint was authorized by your back office, whether your register matches your token holders, whether an upgrade was meant to happen — all of it looks perfectly normal on chain. Hira compares your first-party backend events against independent chain state — the gap screening tools can’t see, because they never had your intent to compare against.
No — and that’s deliberate. Hira observes events and chain state out of band: it adds zero latency, never holds keys, and can’t fail closed on your flow. The SDK is fire-and-forget and fail-open — if Hira is ever unreachable, you lose visibility, not availability. Your existing systems keep deciding what moves.
An attestation proves reserves existed at a moment; it doesn’t tie any individual mint or redemption back to an authorized instruction. The SEC’s TrueCoin settlement showed attested backing can be materially misstated for months between snapshots (SEC, Sept 2024). Hira reconciles per event and hands your attestor a period with zero unexplained breaks — continuous reconciliation makes the attestation stronger, not redundant.
Detective controls for tokenized assets — reconciling your register, your reserves, and the chain on every event.