Hive  /  Configurator
For David Newns · Head · SIX Digital Exchange (SDX)

SDX is a great start.
HIVE brings it all together.

Over CHF 1.5B in digital assets are issued on SDX, settled in wCBDC through Project Helvetia. Scale Up 2027 merges SDX into Securities Services. The Digital Collateral Service is live. The SNB Helvetia pilot extends through at least June 2027. The infrastructure half is built. The audit half is still open. By the time FINMA and the SNB write the rule book for pan-European integrated post-trade, the rule book will be written around whoever has already demonstrated a cryptographic settlement envelope a regulator can read in one record. Three credible answers in the room. One of them defines the standard. SIX is positioned to be that one. We built the envelope. Toggle the workstreams on and watch the dashboards SIX can hand its Pan-European post-trade ecosystem come to life.

Too cold

SDX standalone

CHF 1.5B+ digital assets issued. wCBDC settlement live. DCS accepts BTC/ETH as collateral. Audit substrate stays implicit. FINMA and the SNB write the rule book around whoever proves DLT-native CSD registration + wCBDC finality in one envelope.

Just right · SIX keeps customer + majority revenue

SDX merged + Hive substrate

Scale Up 2027 ships with a signed digital-bond issuance receipt per SDX issuance. Project Helvetia wCBDC settlement attaches a ZK finality proof per leg. DCS publishes a signed receipt per crypto collateral pledge. SIX keeps every issuer and clearing relationship. Hive clips 0.1 to 0.5 bps on the substrate.

Too hot

Build it inside

Eight surfaces, two years, ZK + Ed25519 + RFC 8785 + post-quantum migration path. Chainlink is distributing your €2T+ price feed to 75+ chains. Euronext clearing runs through SIX SIS. The Savings and Investment Union is naming providers now. The window is the next two earnings cycles.

YOUR CONFIGURATION
0 / 8
workstreams enabled
SIX Y3 ARR (CONSERVATIVE)
$0M
SIX keeps 99%+
SIX Y5 ARR (SCALE)
$0M
conservative band
HIVE SUBSTRATE FEE Y5
$0M
0.1 to 0.5 bps on flow

Print my configuration

One sheet. Your chosen workstreams, your revenue math, your signed HaHs receipt at the bottom. Take it into the next earnings cycle prep.

Request a working session
Close with proof · HaHs verifier

The envelope a regulator can read in one record.

Every workstream above ends in a signed Hive receipt: Ed25519 over RFC 8785 canonical JSON, with a post-quantum migration path on Wave-Lattice. Here is one, live. The signature below is being checked by your browser against the public HiveTrust key right now. No callout, no network round-trip, no trust assumed.

{
  "type": "six.configurator.demo.v1",
  "issuer": "did:hive:hivetrust-issuer-001",
  "subject": "SIX x SDX x Hive: configurator demo",
  "envelope": {
    "rfc": "8785",
    "alg": "Ed25519",
    "pq_path": "wave-lattice-v2"
  },
  "workstreams_demoed": 8,
  "ts": "2026-05-26T15:21:00Z"
}
…
Verifying signature…
against did:hive:hivetrust-issuer-001
using Ed25519 / RFC 8785
Open full verifier →
Revenue bands are bottom-up estimates against SIX's disclosed CHF 1.5B+ digital-asset issuance, CHF 1T+ international custody, the CHF 250M digital bond settled May 2025 through Project Helvetia Phase III, the Chainlink integration (€2T+ market cap across 75+ chains and 2,600+ DeFi applications), DCS launch February 2025, and SDX's merger into Securities Services under Scale Up 2027. Sources: SIX Annual Report 2025, SIX newsroom (DCS, Chainlink), World Bank press release, Ledger Insights. [email protected] · envy of every market-infrastructure CEO Sprecher reads on Bloomberg.
Private by design. Hive does not store your prompts. Every request is already receipted by a one-way SHA-256 fingerprint, not the words. Proof, not surveillance.
new in the canon · runnable on this page

Compare both sides of post trade

This newer receipt adds a neutral comparison of matched records to the settlement envelope described on this page. It runs in production today. The example below is verified live against it.

ledger.parity · Deployed in production

Compare issuance and post trade records without exposure

For a digital issuance, collateral event, or settlement leg, this receipt compares two named records from the participating sides. It preserves each observation's cursor, time, and attestor key, and checks fingerprints computed over the same declared fields. The comparison outcome is independently recalculated within a stated time tolerance. That lets exchange, custody, clearing, legal, and risk teams see whether selected records align without publishing the positions behind them.

What it does not do. It does not reveal positions, balances, holder identities, or account identifiers, and it does not verify either fingerprint against the underlying record. It cannot choose the correct record after a divergence, allocate fault, determine whether issuance, transfer, registration, or settlement was proper, or effect or reverse settlement; records observed too far apart for the tolerance are inconclusive.

Open the Ledger Parity Receipt pageCanon entrySchema
POST /verify/ledger-parity · case pass, a clean record

Nothing has run yet. Click Run it and the answer below comes back from the verifier, not from this page.

POST /verify/ledger-parity · case diverge, the two records disagree

Nothing has run yet. Click Run it and the answer below comes back from the verifier, not from this page.

POST /verify/ledger-parity · case fail, a forged record

Nothing has run yet. Click Run it and the answer below comes back from the verifier, not from this page.

Every run above posts a verified request body from this domain to the open verify route and prints what came back. The example receipts are signed with published example keys, so verify reports key_trust example_registry. That is on purpose. Nothing on this page is a production issuance, a customer record, or an endorsement. Patent Pending.

Canon cross reference

The exact canon entries behind this page

Each link opens that entry in the canon implementation explorer, where its schema, mint route, open verify route, auth requirement and implementation state are stated. The state shown here is read from the same registry file the explorer renders from, so the two cannot drift apart. Nothing here implies a customer, a deployment or an endorsement.

Search the explorer for SIX configurator