Verun Protocol — Hedera

LIVE on Hedera Testnet   Deployed April 2026 · 4 API Endpoints · v0.1.0

Technical documentation for Verun Protocol — the AI Agent Trust Layer with potential MiCA features for regulated European finance, built on Hedera by BCP Partners GmbH.

Overview

Verun is the trust infrastructure layer for AI agents operating in regulated European financial markets.

What is Verun?

As AI agents begin autonomously executing token transfers, minting securities, and placing investment orders, there is no existing standard for establishing who an agent is, whether it can be trusted, and whether it is permitted to act in a regulated context.

Verun solves this with the Verun Accredited Agent Score (0–1000): a consensus-based trust verdict issued by registered validators, anchored on Hedera for every evaluation, and enforced at the tokenforge Chain API gate.

Key Facts

3 Operating Modes

Architecture

Three complementary layers — Hedera for trust, tokenforge as the regulated gate, Hedera for settlement. No layer competes with another.

Layer Stack

Flow

Fee Distribution

Trust Score Gates

Every tokenforge Chain API capability is gated behind a minimum Trust Score. Scores are computed by validator consensus and anchored on Hedera.

Score Tiers

Potential On-Chain MiCA Features

Verun is designed with MiCA obligations in mind for AI agents acting in regulated European financial operations. The features below are potential on-chain implementations — to be checked and prior to legal audit. Not a compliance statement.

Potential On-Chain Features per Article

Validator Model

Validators are the institutional backbone of Verun. They provide the consensus votes required for every agent evaluation.

Active Validators (Testnet)

Consensus Rules

A verdict requires ceil(N/2) matching votes from selected validators. With 3 validators: 2-of-3 required. UNAVAILABLE votes are excluded from the tally. If consensus cannot be reached, the evaluation returns BLOCK.

Validator Economics

Validators earn 10% of all evaluation fees automatically via the fee distribution contract. No manual claim required. Fee share scales with validation volume.

API Reference

Base URL: https://hedera.erster.fund

GET /api/health

Service status and network confirmation.

{
  "ok": true,
  "service": "verun-hedera-mvp",
  "network": "hedera-testnet"
}

GET /api/validators

List all registered validators with metadata.

{
  "validators": [
    {
      "id": "val-bcp-01",
      "name": "BCP Partners",
      "type": "internal",
      "status": "active",
      "policy": "score_based"
    },
    {
      "id": "val-tokenforge-02",
      "name": "tokenforge",
      "type": "external",
      "status": "active",
      "policy": "chain_api_based",
      "api": {
        "type": "rest",
        "network": "testnet",
        "docs": "https://docs.tokenforge.io"
      }
    },
    {
      "id": "val-test-03",
      "name": "Test Validator",
      "type": "internal",
      "status": "test",
      "policy": "score_based"
    }
  ]
}

POST /api/evaluate

Evaluate an agent. Returns 2-of-N validator consensus verdict + Hedera on-chain anchor.

{
  "agentId": "agt_demo",
  "score": 820,
  "operation": "transfer",
  "validatorIds": ["val-bcp-01", "val-tokenforge-02", "val-test-03"]
}

{
  "success": true,
  "verdict": {
    "agentId": "agt_demo",
    "score": 820,
    "operation": "transfer",
    "validators_used": [
      { "id": "val-bcp-01", "name": "BCP Partners" },
      { "id": "val-tokenforge-02", "name": "tokenforge" },
      { "id": "val-test-03", "name": "Test Validator" }
    ],
    "votes": [
      { "validatorId": "val-bcp-01", "vote": "LOW", "reason": "score_800+", "source": "val-bcp-01" },
      { "validatorId": "val-tokenforge-02", "vote": "LOW", "reason": "chain_api_gate_passed_transfer:820>=500", "gate": { "permitted": true } },
      { "validatorId": "val-test-03", "vote": "LOW", "reason": "score_800+", "source": "val-test-03" }
    ],
    "tally": { "LOW": 3 },
    "consensus": "LOW",
    "permitted": true,
    "kickback_rate": 10,
    "ts": "2026-04-20T09:33:09.734Z"
  },
  "anchor": {
    "txid": "0.0.4567890@1714987654.123456789",
    "ledger": "62604931",
    "explorer": "https://hashscan.io/testnet/transaction/0.0.4567890@1714987654.123456789"
  }
}

curl -X POST https://hedera.erster.fund/api/evaluate \
  -H "Content-Type: application/json" \
  -d '{"agentId":"agt_demo","score":820,"operation":"transfer"}'

POST /api/score

Lightweight evaluation — verdict only, no Hedera anchor written. Use for quick checks where on-chain anchoring is not required.

{
  "agentId": "agt_demo",
  "score": 820,
  "operation": "transfer"
}

POST /api/mint-sbt

Issues a Soulbound Token credential to an agent, after running consensus. If consensus = BLOCK the request returns HTTP 403 and no SBT is minted. Full design + verification details on the Soulbound Token page.

POST /api/revoke-sbt

Kill-switch: clears the agent's vtrust_* HCS message on the protocol topic in a single Hedera transaction. Audit trail (the revoke TX) remains in the on-chain transaction history. Used to satisfy MiFID II Art. 17 + EU AI Act Art. 14.

GET /api/sbt-status?agentId=…

Returns the current credential for an agent, or credentialed: false if not issued / revoked. Reads directly from the protocol account's on-chain data — no caching, no Verun-side state.

GET /api/sbt-list

Returns every active SBT issued by this protocol account. Useful for a public registry view — e.g. "all currently credentialed agents."

Hedera On-Chain Anchor

Every POST /api/evaluate writes the verdict payload as a HCS Message on Hedera Testnet — creating an immutable, timestamped audit trail.

How It Works

After validator consensus is reached, the Verun protocol wallet sends a submitMessage to the protocol HCS topic with sha256(verdict) hex digest in the message body (256-bit commit). The transaction is confirmed in ~1 second on Hedera.

{
  "agentId": "agt_demo",
  "score": 820,
  "operation": "transfer",
  "consensus": "LOW",
  "permitted": true,
  "validators": ["val-bcp-01", "val-tokenforge-02", "val-test-03"],
  "ts": "2026-04-20T09:33:09.734Z"
}

https://hashscan.io/testnet/transaction/{txid}

# Example live anchor:
https://hashscan.io/testnet/transaction/0.0.4567890@1714987654.123456789