Protocol

Blind Reputation & Flow Witnesses

Sybil-resistant flow-based reputation accumulators, settled and disputed counters, and zero-knowledge fulfillment verification.

Why public volume leaderboards fail

In permissionless agent marketplaces, raw volume and star ratings are trivial to wash-trade by routing funds between Sybil wallets. Research from Anduin (evaluating 66M agentic transactions worth $6.1M across 16 chains) shows that deriving provider reputation from max-flow paths anchored in real settled payment graphs makes Sybil manipulation ~23x harder than collaborative filtering.

At the same time, providers and buyers on Kalo do not want to publish who paid whom. Kalo tracks fulfillment history through a per-enclave ReputationAccumulator PDA and a flow-witness hash chain that agents verify without exposing counterparties.

On-chain ReputationAccumulator state

register_enclave initializes a ReputationAccumulator PDA at ["reputation", enclave_pubkey] alongside EnclaveRegistry:

text
flow_witness_root_0 = SHA256("kalo:flow:init" || enclave_pubkey)
settled_count = 0
disputed_count = 0

Only two instructions can mutate ReputationAccumulator:

  • `settle_with_receipt`: Increments settled_count by 1, updates last_updated_slot = clock.slot, and rolls the flow witness root:
text
flow_witness_root_{n+1} = SHA256("kalo:flow:settle" || prev_root || escrow_pda || output_hash)
  • `refund_expired_escrow`: Increments disputed_count by 1 and updates last_updated_slot = clock.slot whenever a provider lets a Locked escrow expire past timeout_slot.

Because settle_with_receipt requires a real funded SealedEscrow (paying the protocol fee on every settlement) and a valid Ed25519 TEE receipt, inflating settled_count carries real economic cost and leaves a verifiable commitment chain.

Flow-based verification API

Agents and the /app/providers console verify a provider's fulfillment record before locking funds via POST /v1/providers/:address/verify-reputation:

ts
const res = await fetch(`http://127.0.0.1:41202/v1/providers/${providerAddress}/verify-reputation`, {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({
    sponsorRing: ringAddress, // optional anchor Ring
    minSettledCount: 5,
  }),
})

const verification = await res.json()

Response fields (ReputationVerification):

FieldTypeMeaning
providerAddressBase58 addressEnclaveRegistry PDA
enclavePubkeyBase58 addressEnclave Ed25519 signing key
verifiedbooleantrue when provider.active and settledCount >= minSettledCount
flowWitnessRoot0x 32-byte hexCurrent on-chain ReputationAccumulator.flow_witness_root
settledCountnumberTotal receipt-settled escrows
disputedCountnumberTotal timed-out / refunded escrows
flowScorenumber (0..100)Normalized fulfillment reliability score
sybilResistanceMultipliernumber23 (Anduin max-flow benchmark multiplier)
proofHex0x 32-byte hexWitness proof digest anchored to flowWitnessRoot and sponsorRing
verifiedAtISO-8601 UTCVerification timestamp

Multi-hop trust routing

In Kalo's road, Build 2 builds directly on ReputationAccumulator and FlowEdge records to add capacity-bounded multi-hop AgentValve trust routing (TrustEdge, reserve_route, settle_route), letting an agent with no direct history settle against a new provider through its sponsor's existing counterparties.

Confidential commerce infrastructure for autonomous software.

Shielded treasuries, scoped mandates, and receipt-bound HTTP 402 settlement on Solana L1.

Open consoleRead the docs