jq, and network access for initial dependency installation. Docker is needed only for the full scaffold/container topology.
From a checked-out copy of the Nautilius repository, run:
testing/tee-harness, starts the pinned tee-node’s loopback sign/decrypt server with a fresh ephemeral key, and runs encrypted create → bid → clear through the real /decrypt endpoint. That harness proves local protocol compatibility, not hardware isolation or attestation.
For live reproduction, copy web/.env.example, insert only explorer-verifiable Nautilius deployments, and follow the deployment guide. An empty configuration is an intentional honest state.
A public clone URL will be added only after repository publication is separately authorized. These source docs do not imply that publication has happened.
Expected verification boundary
Local tests prove handler rules, contract guards, ABI encodings, the official ActionResult hash/signature formula, browser/Go ECIES compatibility, and the pinned tee-node/decrypt boundary. They do not prove an extension is registered, a production TEE is attested, a Coston2 transaction succeeded, or a real test FAsset moved. Verify those separately with the judge walkthrough.