Trusted execution verification
An attestation is useful only when the verifier, trust material, and policy agree.
Check the whole verification chain
TEE acceptance depends on the node build, enabled policy, supported vendor format, approved measurement, pinned trust material, and successful verification. A vendor name in a feature list is not evidence that the network has an active compatible provider.
State what the receipt establishes
Document the workload and measurement being attested, the verifier used, and the freshness/replay rules. Keep TEE hardware attestation separate from ordinary provider signatures, quorum agreement, and zero-knowledge claims.
Treat activation as network-specific
Unsupported proof modes should fail closed. Use selected-network policy and current verifier evidence before exposing a TEE-backed job mode to users.
Know what has been verified.
Build on explicit trust boundaries instead of treating signatures, commitments, attestations, and proofs as interchangeable.
Treasuries: design and boundaries.
A design reference for policy-controlled funds. Direct public treasury transactions remain gated in the inspected executor.