Operators and $HERMETIC
Operators
An operator runs confidential hardware and serves sessions. To be routed sessions, an operator must:
- run a build listed in the registry, on hardware that produces valid TDX quotes and GPU reports;
- bond $HERMETIC to the operator contract;
- keep its bond above the minimum set by governance.
Slashing
A bond can be slashed for:
| Fault | Evidence |
|---|---|
| Invalid attestation | A receipt whose quote fails verification. |
| Unlisted build | A quote whose measurement was not in the registry at the time. |
| Proven leak | Content matching a session commitment, published or sold, with the salt revealed by the user. |
Part of the slashed amount goes to whoever submitted the evidence. The rest goes to the cover pool.
Fees
Sessions are priced in USDG or in $HERMETIC; paying in $HERMETIC costs less. The proposed split of every session fee, adjustable by governance:
| Share | Recipient |
|---|---|
| 70% | The operator who served the session |
| 20% | The cover pool, which compensates users after a proven leak |
| 10% | Buyback and burn of $HERMETIC |
The token
$HERMETIC launches on Pons on Robinhood Chain. It has three jobs: the operator bond, the discounted payment for sessions, and the vote on the registry. Until the contract address is shown in the strip at the top of this site, the token has not launched.