Expand description
Runtime traits for VM execution, proving, and deployment.
Trident is the weapon. Warriors wield it. Trident defines these traits; warriors implement them. A warrior is a target-specific tool (separate crate) that takes compiled Trident output and handles execution, proving, and deployment for a particular VM+OS combination.
Example: Trisha (Triton + Neptune warrior) implements Runner
via triton_vm::simulate(), Prover via triton_vm::prove(),
and Deployer via Neptune RPC — all using Trident’s PrimeField,
Poseidon2, and Claim primitives from crate::field.
No heavy dependencies here — only the interface contract and
the serializable ProgramBundle artifact format.
Re-exports§
pub use artifact::ProgramBundle;
Modules§
- artifact
- Program bundle: self-contained compilation artifact for warrior consumption.
Structs§
- Execution
Result - VM execution result.
- Guess
Result - Result of a successful nonce search.
- Program
Input - Input specification for program execution.
- Proof
Data - Proof artifact: claim + opaque proof bytes.