Pluto

---

Web Prover

The Web Prover is infrastructure for generating Web Proofs with Trusted Execution Environments (TEEs).

The default option for generating Web Proofs is to use the Pluto-hosted service. We recommend using the Javascript SDK, which uses a Pluto-hosted notary. Learn more here. Developers do not need to set up the prover or host it themselves, unless they explicitly want to self-host this infrastructure or build custom infrastructure.

How to get started

Visit the Pluto documentation for integration guides, conceptual overviews, and reference materials.

If you have any questions, please reach out to any of Pluto's team members or join our Telegram to ask questions. We'd love to hear from you!

Development

Repo layout

• client: contains components for the client that are shared across both WASM and iOS targets.
• fixture: contains testing artifacts such as TLS certificates and configuration files.
• notary: notary server which can notarize TEE proofs.

Usage

cargo run -p notary -- --config ./fixture/notary-config.toml
cargo run -p client -- --config ./fixture/client.proxy.json

Security Status

As of February 2025, the code in this repository is operational on Ethereum testnets, and we have begun the security auditing process.

Following completion of audits, we plan to launch with protective guardrails in place, which will be gradually adjusted and removed as the system demonstrates stability in real-world conditions.

Release

1. Update the version field in the appropriate Cargo.toml file.
2. Create a pull request with the version update.
3. Merge the pull request.

Once merged, the package will be automatically released. Note: Releases are immutable.

The following crates are checked for version changes:

• notary/Cargo.toml
• client/Cargo.toml