Skip to main content

Arbiter

The Arbiter is a verification engine that uses Graph-of-Thought (GoT) directed acyclic graphs to decompose and verify every agent transaction before it reaches the blockchain. Each transaction is broken into a structured graph of verification nodes, where each node evaluates a specific constraint: router address correctness, function selector validity, token whitelist membership, slippage bounds, gas reasonableness, and jurisdiction compliance. The graph produces a composite verification score, and only transactions passing verification proceed to execution.

Deterministic Triggers​

Fast, binary checks for hard requirements. These run first and reject immediately on failure:

  • OFAC and sanctions screening
  • Balance sufficiency and address validity
  • Spending limits and frequency constraints
  • Transaction syntax and gas limit validation

If any deterministic trigger fails, the transaction is rejected without invoking the LLM reasoning layer. This keeps verification fast and cheap for straightforward cases.

Graph-of-Thoughts (GoT) Reasoning​

LLM-powered analysis for subjective and complex checks. GoT runs only after all deterministic triggers pass:

  • Intent-transaction alignment: Does the transaction match what the user asked for?
  • Adversarial manipulation detection: Hidden token swaps, slippage exploitation, malicious routing
  • Legal and compliance validation: Jurisdiction-specific rules and regulatory requirements
  • Structured explainability: Every verdict includes a reasoning trail

Verdict Output​

Every Arbiter evaluation produces one of two outcomes:

  • Approve: The transaction passes all checks. The verdict includes a full explanation of the reasoning.
  • Reject: The transaction fails one or more checks. The verdict includes failure reasons and remediation guidance.

Verdicts are recorded on NavaChain as an immutable audit trail.