[!IMPORTANT]
Compute mining is closed to new miners right now. Only approved operators
earn; any other machine earns nothing, even if it passes every check. There is
no application. Cathedral will post an announcement when mining opens.
Earn today with no hardware: the Cathedral Escape Room
is open to any hotkey registered on SN94.
Contents
Cathedral turns independently operated machines from trusted operators into a
verifiable compute network. Miners supply the machines; validators check their
confidential-computing evidence, test their work and score the results.
The Cathedral map
| Repository | What it is | Read it when |
|---|
| cathedral-sandbox (this one) | The sandbox, the sealed host code, and compute mining | You want to mine with a machine, or study the target |
| cathedral-escape | The contest: break out of a sealed sandbox, prove it, earn | You want to attack the sandbox for a reward |
| cathedral-validator | The SN94 validator: how weights are set, with signed updates | You want to validate, or check how miners and breaks are paid |
This repository is for miners running compute workers on Bittensor SN94. It builds the wall, the escape room pays people to break it, and the validator pays both:
about 10% of its weight to approved compute miners, about 10% to proven escapes, and the rest is burned.
How mining works
Validators verify fresh machine evidence, bind it to the live HTTPS key, reject
duplicate machines, and run a bounded SAT task. Each distinct verified machine
adds to its UID's score, if the hotkey is on the approved list. The validator
does not use a weight relay.
Registration, uptime, an attestation quote or an advertised machine count alone
earns nothing. Verification alone earns nothing too: the hotkey must also be
approved (Gated compute). Weight does not guarantee TAO: the subnet needs positive emission.
This mining path is not a customer sandbox API.
Current support
| Machine | Current boundary |
|---|
| AMD SEV-SNP guest | Validator source supports it. Each validator must admit the live measurement and TCB. SN94 admission remains unverified. |
| Intel TDX confidential VM | Mainnet live testing; fresh TDX evidence and SAT must pass. |
| More machines on one UID | Each must independently pass verification; duplicate hardware scores zero. |
| GPU | Not a qualified mining path; see the development contract. |
A machine quote does not remotely prove its container image digest or continuous
runtime integrity after boot. See the mining guide
for the exact evidence boundary.
Customer products
Cathedral's lease and sandbox products are live on SN94. The public sealed
tier runs on AMD SEV-SNP hosts that Cathedral leases. Cathedral does not own
those hosts. There is no self-serve sealed capacity; access is by request.
This repository does not sell or provision that product.
The Escape Room is open, with no cash prize. Rules and a practice harness are in
cathedral-escape.
What you need
- A Linux AMD SEV-SNP guest with
/dev/sev-guest, or an Intel TDX VM with
/sys/kernel/config/tsm/report. Ordinary SEV and a vTPM are not SNP.
- Python 3.12 with
venv, Git, Docker, nft, and curl inside the guest.
- Public IPv4 and inbound TCP
8081.
- A miner-owned control host with Python 3.12 and Git to refresh signed
validator-access snapshots.
- A public Bittensor hotkey; Bittensor CLI
11.1.0 on a separate wallet machine.
Keep the coldkey and wallet off every worker. Workers need only the public
hotkey; each creates its own TLS private key inside its confidential guest.
Check AMD's socket policy
with the validators you expect to score it before renting or registering.
Install and start
Follow the single mining guide in order:
- Rehearse locally
three times before spending or registering. Python 3.11+ is enough for this
rehearsal; its synthetic evidence proves protocol wiring, not hardware.
- Choose the AMD SEV-SNP or
Intel TDX instructions.
Use their pinned image and root-owned launcher; do not run a writable
checkout as root.
- Set up the miner-owned signer and
snapshot refresh.
Keep its signing seed outside the Git checkout.
- Start the worker and check the exact health response before
paid registration and axon announcement.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
