How lfdt-paladin/zeto works
Zeto is a toolkit for privacy-preserving EVM fungible and non-fungible tokens. Its central workflow is to generate a zero-knowledge proof with the JavaScript library and circuits, then use a token contract that enforces the selected privacy properties; the Go SDK and recommended Paladin runtime support client interaction. The graph also preserves the documented token-pattern variants and SDK capabilities. Solidity contract implementations are not present in the supplied tree, so deployment modules stand in for that subsystem; links between major subprojects reflect README statements.
Main entry points: index.js JavaScript proof library · modules Token deployment modules · src Go SDK · tokens Token deployment examples
Components 9
Proof generation
- JavaScript proof library
zkp/js/index.js - Proof utilities
zkp/js/lib/util.js - ZK circuits
zkp/circuits
Token contracts
- Token deployment modules
solidity/ignition/modules - Token deployment examples
solidity/scripts/tokens
Client tooling
- Go SDK
go-sdk/src
Client runtime
- Paladin client runtime
Other components
- Token integrator
- EVM network
Connections 9
- Token integrator → JavaScript proof library: generates proofs
- JavaScript proof library → ZK circuits: loads circuits
- JavaScript proof library → Proof utilities: uses utilities
zkp/js/index.js - Token integrator → Token deployment modules: deploys tokens
- Token deployment examples → Token deployment modules: provides examples
solidity/scripts/tokens/Zeto_AnonEnc.ts - Token integrator → Go SDK: interacts via SDK
- Paladin client runtime → EVM network: submits transactions
- Paladin client runtime → Token deployment modules: targets contracts
- Paladin client runtime → Go SDK: shares client role