ZkTLS Contract

The core ZkTLS contracts consist of three components:

• ZkTLSManager: A Manager that handles account and prover setups.
• ZkTLSGateway: A Gateway that handles various TLS requests and emits events for relaying interactions.
• ZkTLSAccount: Gateway Clients that each client/account associates with a single dApp and enableso interactions with The3Cloud ZkTLS Gateway.

Install Dependencies

git clone https://github.com/the3cloud/zktls-contracts
cd zktls-contracts
forge soldeer install

Deployment

# deploy contracts with create2
forge script script/DeployCreate2.sol:Deploy --rpc-url <url> --private-key <key>
# deploy general contracts
forge script script/Deploy.sol:Deploy --rpc-url <url> --private-key <key>

Directory Structure

/zktls-contracts
|-- config (forge cli configuration)
|-- contracts (core contracts)
|-- script (deployment scripts)
      |-- interfaces (interface definitions)
      |-- lib (share struct definitions)
      |-- mock (mock contracts for testing)
      |-- prover (wapper verifier contracts for risc0 and sp verifiers)
      |-- Create2Deployer.sol (deterministic create2 deployer)
      |-- SimpleFaucetsol (The3CloudCoin Faucet contract)
      |-- ZkTLSGateway.sol (the entrypoint contract for ZkTLS)
      |-- ZkTLSManager.sol (the manager contract for ZkTLSGateway)
      |-- ZkTLSAccount.sol (the acount/client contract for ZkTLSGateway, associated with dApps)
|-- test (unit tests for ci)
|-- lib (dependencies installed by forge)
|-- mdbook (mdbook configuration for documentation)
|-- foundry.toml (foundry configuration)

Deployments

Please refer to the config directory and find related chain id to find deployed contract address.

Deployed Prover ID

Prover ID	Native Gas Cost	Payment Fee	Verifier Type
0xe4f395abcf8e2cf08d98b83966e70024139469def2c9bfc97266900c3983454d	1000	1000	mock