The first mainnet anchor for Nordic Shield is already mined.
- txid:
98e1d6a01614c464c237f982d9dc2138c5f8aa08342f67b867a18a4ce998af9a - block:
3,286,631 - root:
024e36515ea30efc15a0a7962dd8f677455938079430b9eab174f46a4328a07a
Verification path:
- Nordic Shield Verification
- public repo:
https://github.com/Frontier-Compute/zec-pay - independent verifier:
verify_proof.py
This is not a roadmap item. It is already deployed on mainnet.
The claim is straightforward: every state change in the participant lifecycle is committed to Zcash. Payments, ownership assignment, contract anchoring, deployment, monthly hosting, annual shield renewal, transfers, exits, and Merkle root commitments now all exist as protocol event types in the live stack.
What is live
Running today:
zec-payscanner on mainnet- Zebra
4.3.0at chain tip - S-NOMP live and accepting stratum connections
GET /statsGET /lifecycle/{wallet_hash}POST /event
The current anchored leaves are:
PROGRAM_ENTRYOWNERSHIP_ATTEST
for serial Z15P-E2E-001, committed under the root above.
Lifecycle event types
| Type | Name | Meaning |
|---|---|---|
0x01 |
PROGRAM_ENTRY |
participant paid and entered the program |
0x02 |
OWNERSHIP_ATTEST |
wallet hash linked to a machine serial |
0x03 |
CONTRACT_ANCHOR |
hosting contract artifact committed by hash |
0x04 |
DEPLOYMENT |
miner installed at facility |
0x05 |
HOSTING_PAYMENT |
monthly hosting invoice paid |
0x06 |
SHIELD_RENEWAL |
annual privacy shield renewed |
0x07 |
TRANSFER |
ownership moved to a new wallet hash |
0x08 |
EXIT |
participant exit or hardware release recorded |
0x09 |
MERKLE_ROOT |
current lifecycle tree root anchored to Zcash |
This is the part I think is new for Zcash: not just an on-chain payment receipt, but a full lifecycle commitment layer for a real-world program.
How to verify
- Open Nordic Shield Verification .
- Read the leaf hash, proof path, root, txid, and block height.
- Recompute the leaf from the wallet hash and, where applicable, serial number.
- Walk the Merkle proof.
- Confirm the derived root matches
024e36515ea30efc15a0a7962dd8f677455938079430b9eab174f46a4328a07a. - Check txid
98e1d6a01614c464c237f982d9dc2138c5f8aa08342f67b867a18a4ce998af9ain a Zcash explorer or local tooling. - Confirm the transaction is mined in block
3,286,631.
If you want to ignore the website entirely, use the public repo and verifier script.
Why this matters
Hosted mining programs normally depend on opaque operator records. A participant pays, gets updates in chat, and has limited ability to verify ownership, deployment status, billing history, or exit state without trusting the operator database.
Zcash can do better than that.
Shielded memos plus Merkle commitments make it possible to keep participant identity off-chain while still exposing a public audit layer. That is what Nordic Shield is using now.
The commercial program is straightforward:
- Z15 Pro Cohort 0 ships mid-April
- state of the art hosting facility in Norway
- all-in hosting starts at $0.10/kWh effective, targeting $0.09/kWh for Cohort 3 as aggregate volume scales
- Cohort 1 target is 10 slots by mid May
But the technical point is broader than one program. This is an open-source pattern for any Zcash-native operator that wants private payments plus public verifiability.
What’s next
- anchor automation is already live, roots commit automatically every 10 events or 24 hours
- integrate Zaino for compact-block scanner portability
- ship a WebZjs in-browser verification widget (no server trust required)
- add FROST threshold signing for anchor operations when upstream tooling stabilizes
- continue committing the full participant lifecycle as hardware arrives mid-April
If anyone wants to review the protocol surface, the repo is here:
If anyone wants to challenge the proof model, even better. The point of shipping it this way is that the claims are checkable.