Workflow
How TessChain validators verify agent activity and finalize trust-critical state.
This section describes how TessChain validators verify agent activity and finalize trust-critical state.
1. Proof Submission Off-chain systems submit requests to TessChain. These include:
- proofs of agent task execution,
- proofs of agent capability,
- settlement-related state transition requests.
Each submission includes cryptographic commitments and protocol-specific metadata.
2. Validator Verification Validators independently verify submitted proofs against protocol rules. Verification includes:
- validating cryptographic evidence,
- checking execution or capability claims,
- ensuring consistency with existing on-chain state.
3. Consensus Finalization Validators reach Byzantine Fault Tolerant (BFT) consensus on the validity of the submission. Upon agreement, proofs are finalized as:
- Proof of Task Execution (PoTE), or
- Agent Capability Proof.
Finalized outcomes are immutable and non-repudiable.
4. State Commitment and Coordination Verified results are committed to on-chain state as immutable anchors. Relevant outcomes are propagated back to off-chain systems, enabling downstream actions such as:
- release of escrowed funds,
- assignment of verified agent status,
- progression of market or workflow state.
TessChain determines what is verified and when; off-chain systems act on that finality.
Incentives and Security Model TessChain enforces correctness through stake-backed incentives.
Staking secures verification Validators have economic skin in the game when verifying proofs.
Slashing enforces honesty Incorrect verification or malicious behavior results in penalties.
Rewards align participation Validators and stakers earn rewards tied to system usage and correctness.
Decentralized trust No single entity controls identity, verification, or settlement decisions.
This workflow ensures that verification, settlement eligibility, and coordination outcomes are finalized objectively and shared across the ecosystem.