HiveSovereign: supervisory observability layer

A window regulators can trust into stablecoin flows.

Built for central banks, ministries of finance, and financial-conduct authorities to read directly. Every USDC transaction under a Hive receipt is signed twice, tied to where it came from, and can be shown selectively to the right supervisor without exposing anyone's private business. This is the piece that lets a regulated stablecoin become infrastructure a central bank will sign off on ahead of time.

Talk to Steve Verify a receipt

Why this exists

Right now, every central bank in the developed world is being asked to approve stablecoins for use in its own payments system. The BIS, the Federal Reserve, the ECB, the Bank of England, the MAS, the BOJ, and the SNB have all published papers laying out what kind of oversight they need before they'll sign off. Nobody has built that yet. HiveSovereign is the layer that does: transaction history you can mathematically prove, shown selectively to the supervisor, checkable offline, with signatures built to survive quantum computers.

What a supervisor can do under HiveSovereign

HiveSovereign is a read-only portal for supervisors, signed at every level, that gives a regulator a live view into the stablecoin flows in its jurisdiction. The portal shows:

jurisdiction_view: every transaction touching someone who lives in the supervisor's jurisdiction, with cryptographic proof of where they live, checked at the issuer level.

institution_view: every transaction involving an entity the supervisor licenses, classified as a bank, MSB, broker-dealer, or EMI.

corridor_view: money crossing the border in and out of the jurisdiction, with travel-rule receipts tied to each transfer.

policy_compliance_view: every transaction's NEED, YIELD, and CLEAN-MONEY results, anonymous at the individual level but checkable in aggregate.

sanctions_screening_view: OFAC, EU consolidated, UN, and UK OFSI sanctions hit rates and what happened with each one, with a paper trail.

aggregate_volume_view: domestic, cross-border, intra-bank, and inter-institution stablecoin volume by hour, day, and month, all with signatures you can check offline.

selective_disclosure: the supervisor can ask for more detail on a flagged transaction or account through a defined legal process. That request itself gets signed twice.

regulator_export: every view can be exported as a signed, standardized audit packet for use by parliament, courts, or international information sharing.

Built for USDC on Arc

The piece that gets USDC pre-approved by a central bank.

HiveSovereign runs on Arc as a read layer sitting above settlement. Every receipt on Arc can be seen by the right supervisor without exposing anyone else's business, because that's how the system is built. It's the same receipt rail every counterparty signs against, so what a central bank sees matches, byte for byte, what the counterparty sees of its own transactions. No other stablecoin rail, on any chain, works this way.

Who runs on HiveSovereign

Central banks evaluating regulated stablecoin participation in their domestic payments infrastructure under BIS framework guidance.
Financial-conduct authorities supervising banks, MSBs, EMIs, and stablecoin issuers under MiCA, FSMA, MAS Notice 626, and equivalents.
Ministries of finance evaluating stablecoin policy, capital-flow management, and macroprudential exposure.
BIS, FSB, IMF, and standard-setting bodies publishing cross-jurisdictional guidance on stablecoin oversight.
FATF and FATF-style regional bodies assessing travel-rule compliance at corridor level.

Three things HiveSovereign is not

It's not a surveillance product. Selective disclosure protects everyone's privacy. A supervisor sees totals and flagged transactions, not every user's balance.
It's not a backdoor. A supervisor needs signed legal process to see more detail. The portal logs every elevated request, signed twice and impossible to alter. A meta-supervisor can even check the log of who checked what.
It's not a CBDC. HiveSovereign only reads private, regulated stablecoin flows. The central bank doesn't issue the money, doesn't hold it, and doesn't sit in the middle of a transaction. It supervises.

Pricing

For supervisory bodies

Read access is free for designated supervisory institutions under a memorandum of understanding. The issuer and the counterparties in the supervisor's jurisdiction cover the cost.

$0.001

Per supervisable event: issuer fee

This is what the issuer pays to make each transaction readable by a supervisor. It's less than a basis point on a $100 transaction, basically a rounding line item on any institutional rail.

$49,999

Per month: sovereign tier

A custom build for a national supervisor, with its own views, a verifier running on its own servers, hooks into national audit systems, and a dedicated technical contact.

Why now

In 2025, the BIS published the oversight framework stablecoin issuers will be measured against. No issuer has shipped a product that meets it yet. HiveSovereign is that product.
The GENIUS Act and MiCA both require stablecoin issuers to keep proving ongoing oversight of the flows they enable. Compliance deadlines are close. Issuers without a supervisory layer won't get licensed.
USDC is the stablecoin most likely to get central-bank pre-approval. Hive's supervisory layer is what makes that approval something you can defend.
Hive already runs EU AI Act compliance in production. HiveSovereign meets the AI Act's audit-trail and supervisory-access rules simply because of how the receipt rail works.

A direct conversation, not a procurement cycle

If you're a supervisor, a central-bank policy lead, or a regulated issuer looking at supervisory infrastructure ahead of stablecoin pre-approval, the fastest way in is a direct note. Steve reads them.

Talk to Steve See a verification

Live since 2026-05-18 · Signed twice (Ed25519 + ML-DSA-65) · Lines up with BIS / GENIUS Act / MiCA / FATF / EU AI Act · Selective disclosure, checkable offline