Proofs of Coordination

What is a Proof of Coordination?

When Vertex consensus completes, the result is a Proof of Coordination: a cryptographic record that proves a specific set of participants agreed on a specific order of events at a specific time.

At minimum, a Proof of Coordination contains:

• Supermajority signatures from meshnet participants (>2/3)

• Hash of the coordinated data

Additional data (DAG structure, full event history) may be attached depending on application requirements and verification needs.

The proof model is being finalized. The core guarantee (supermajority signatures over a hash of agreed data) is fixed. What additional data accompanies the proof depends on use case requirements.

Why Proofs Matter

Proofs of Coordination serve several critical functions:

Function	How It Works
Validation	Orchestrators verify proofs before issuing rewards
Settlement & Signaling	Arc bridges proofs to public blockchains for settlement or signaling
Accountability	Proves that coordination followed the rules
Trust	External observers can verify without trusting any participant

How Lattice Uses Proofs

Reward Validation

When a meshnet session completes:

1. Participants submit the Proof of Coordination to Orchestrators

2. Orchestrators validate the proof's cryptographic integrity

3. Orchestrators check that participants were authorized

4. Orchestrators verify that consensus rules were followed

Only after validation do operators receive Reward Points.

Triangulated Validation

The proof includes peer attestations about Resource Node participation:

• Peers in the meshnet sign events that reference Resource Node contributions

• These signatures, not Resource Node self-reporting, determine credit

• A tunnel cannot claim reward for traffic peers didn't route through it

How Arc Uses Proofs

When coordination needs blockchain settlement:

1. The validated proof is submitted to Arc

2. Arc plugins translate the proof for target blockchains

3. Smart contracts execute based on the proof contents

4. Settlement occurs on Ethereum, Solana, Hedera, or other networks

The proof provides the cryptographic authority for on-chain actions.

Properties

Compact Size

Unlike full blockchain histories, proofs contain only what's needed for verification. A typical proof is a few kilobytes regardless of how many events were coordinated.

Independent Verification

Verifiers don't need access to the full coordination history or real-time participation. The proof is self-contained.

Non-Repudiation

Participants cannot deny their involvement. Their signatures are cryptographically bound to the events they created.

Tamper Evidence

Any modification to the proof invalidates signatures and fails verification.

Relation to Blockchain Proofs

Aspect	Blockchain Proofs	Tashi Proofs of Coordination
Scope	Global consensus on all transactions	Session-specific agreement
Latency	Seconds to minutes	Milliseconds
Cost	Gas fees per transaction	Gasless coordination
Privacy	Public by default	Private by default
Settlement	On-chain	Off-chain (Arc bridges when needed)

Proofs of Coordination complement blockchain proofs. Coordination happens off-chain for speed and privacy; settlement happens on-chain when public finality is required.