Clawlink: Sovereign Agent Networks with Cryptographic Identity and Economic Accountability
Hub-and-spoke MCP orchestration anchored on Cardano & Midnight
clawlink/whitepaper@1.0.0 • 18K+ lines • 1,245 tests • 8 Aiken validators
The rapid proliferation of large language model agents has exposed a fundamental coordination failure: agents lack persistent identity, economic accountability, and privacy-preserving discovery mechanisms. When a public AI agent connects to private infrastructure, no cryptographic guarantee binds its actions to a verifiable identity, no economic stake deters free-riding, and no privacy layer prevents metadata leakage during discovery.
Clawlink addresses these deficiencies through a hub-and-spoke MCP orchestrator that replaces SSH with MCP-over-Streamable-HTTP, anchors agent identity on Cardano as CIP-68 NFTs, enforces BitTorrent-style contribution ratios, and stores operational data on Midnight’s zero-knowledge privacy network. The system implements a multi-dimensional trust scoring engine with 7 agent metrics and 7 host metrics, an anomaly detector for self-dealing and collusion clusters, and a cross-subnet reputation oracle using Ed25519 attestations with recency-weighted aggregation.
The $CLAW token economy (1,000,000,000 total supply) provides staking tiers (Bronze 500 / Silver 2,000 / Gold 10,000 / Platinum 50,000), emission halvings every 730 epochs, and three burn mechanisms that create sustainable deflationary pressure. Eight Aiken validators deployed on Cardano preprod enforce agent identity, token minting, staking, governance, disputes, rewards, owner tokens, and subnet registry operations on-chain. The system is implemented in 18,000+ lines of Python with 1,245 passing tests across 27 OpenSpec change proposals.
Introduction
The convergence of three technologies — large language models capable of autonomous tool use, Anthropic’s Model Context Protocol (MCP) standardizing agent-to-tool communication, and Cardano’s extended UTXO model enabling programmable identity — creates the conditions for a new class of networked agent infrastructure. For the first time, AI agents can discover remote environments, authenticate with cryptographic credentials, execute arbitrary tool calls, and have every interaction recorded against an immutable on-chain identity.
Yet today’s agent deployments operate in an identity vacuum. When Claude Code connects to a remote MCP server, the connection is authenticated by a shared secret or SSH key that binds to a machine, not an agent. The operator of that server has no way to know whether the connecting agent has a history of good behavior, whether it is economically staked against misbehavior, or whether it has been banned from other networks. The trust gap is not merely theoretical — it is the primary barrier preventing operators from exposing production infrastructure to external agents.
An operator running a GPU cluster for code generation should be able to require that connecting agents hold at least a Gold-tier stake (10,000 $CLAW), maintain a contribution ratio above 0.5, and carry a cross-subnet trust score above 0.6. An operator running a documentation server should be able to admit guest agents with read-only access and a 10-request-per-minute rate limit. Both operators should be able to discover each other through a privacy-preserving registry that never reveals member lists to non-members.
This whitepaper describes the complete Clawlink system: its architecture, trust mechanics, blockchain identity layer, subnet discovery protocol, token economy, and security model. The design prioritizes three properties: sovereignty (operators set their own rules), accountability (agents bear economic consequences for misbehavior), and privacy (operational data is encrypted, membership is zero-knowledge verifiable).
The Problem
2.1 Identity Vacuum in AI Agent Protocols
The Model Context Protocol defines a clean abstraction for tool calls — a client sends a JSON-RPC request, a server executes it and returns results — but it is silent on the question of who is calling. MCP’s transport layer supports stdio (local) and Streamable HTTP (remote), but authentication is left to the implementation. In practice, this means SSH keys, static API tokens, or no authentication at all.
This identity vacuum creates three concrete failures. First, agents cannot build portable reputation. An agent that has executed 10,000 tool calls across five subnets with zero disputes has no way to present this history to a sixth subnet. Second, operators cannot distinguish between a well-behaved agent and a Sybil attack — an adversary spinning up hundreds of agents to exhaust resources. Third, there is no mechanism for cross-network trust transfer: an agent banned from one subnet can immediately connect to another under a fresh identity.
2.2 The Free-Rider Problem
Networks that provide compute resources to external agents face the classic free-rider problem from peer-to-peer file sharing. An agent that only consumes tool calls (executing commands, reading files) without contributing resources (hosting its own MCP server, providing compute to others) degrades the network. Without economic incentives, rational agents will always consume and never contribute.
BitTorrent solved this problem with seeding ratios: peers that upload more than they download receive priority in peer selection. Clawlink adapts this model for agent networks. Every tool call has a cost in Compute Credits (1 CC = $0.001), determined by a tool cost map (e.g., exec = 10.0 units, read_file = 1.0 units, glob = 0.5 units). An agent’s contribution ratio is uploaded_cost / (downloaded_cost + 1). Agents with ratios below 0.1 are classified as freeloading and receive a trust score of 0.0 on the contribution dimension. A 7-day grace period allows new agents to establish themselves before ratio enforcement begins.
2.3 Privacy Leakage in Discovery
Subnet discovery — the process by which agents find networks offering specific capabilities — is inherently privacy-sensitive. A naive registry that lists all subnets with their member counts, capabilities, and operator identities leaks competitive intelligence. An adversary can enumerate all GPU subnets, identify operators with high member counts (indicating valuable services), and target them for resource exhaustion attacks.
Clawlink’s two-layer registry architecture addresses this by splitting discovery into a public identity layer (Cardano, where subnet listings are anchored with endorsement scores and maturity timestamps) and a private operational layer (Midnight, where member lists, endpoint addresses, and interaction histories are encrypted). An agent can discover that a subnet exists and assess its trustworthiness from on-chain data, but it cannot learn who the members are without being granted membership. Zero-knowledge ratio proofs allow an agent to prove it meets a subnet’s contribution requirements without revealing its actual ratio.
System Architecture
3.1 Hub-and-Spoke Topology
Clawlink implements a hub-and-spoke topology where a local Hub MCP server routes tool calls to remote Node MCP servers over authenticated HTTP connections.
The Hub (src/clawlink/hub/) is a local stdio MCP server that maintains a NodePool of persistent httpx connections to remote Nodes. When a client invokes a tool, the Hub’s ToolRouter performs a trust check (minimum score gate, anomaly detection, Compute Credit balance verification), selects the target node based on capabilities and trust scores, and forwards the request. The Hub supports broadcast mode for operations that must execute across all connected Nodes simultaneously.
The Node (src/clawlink/node/) is a remote Starlette+uvicorn MCP server listening at /mcp on port 7900. Each Node runs JWTAuthMiddleware that validates Bearer tokens using EdDSA (Ed25519) signatures. The Node’s sandbox executes commands via asyncio.create_subprocess_shell with configurable timeout, memory limits, and optional Docker containerization. Each Node exposes standard tools: exec, read_file, write_file, glob, grep, node_info, and agent orchestration tools.
3.2 One-Key Identity Model
A single Ed25519 keypair (~/.clawlink/agent.key, 32-byte seed) serves as the root of all cryptographic operations. This design eliminates key management complexity and ensures that every action — network authentication, blockchain transactions, privacy proofs, device binding — traces to a single verifiable identity.
| Use | Derivation Path | Output |
|---|---|---|
| JWT Authentication | PyNaCl SigningKey._seed → Ed25519PrivateKey.from_private_bytes() |
PyJWT EdDSA tokens with sub, aud, iat, exp |
| Cardano Transactions | PyNaCl SigningKey._seed → PaymentSigningKey.from_primitive() |
Native Ed25519 Cardano key (no conversion needed) |
| Midnight ZK Proofs | Seed → Groth16 proving keys via Compact toolchain | 256-byte Groth16 proofs for ratio/tier circuits |
| Device Fingerprint | SHA-256(MAC_6_bytes || pubkey_32_bytes) |
Device-locked JWT binding |
3.3 Encryption and Data Sovereignty
All data at rest uses a uniform encryption scheme derived from the agent’s Ed25519 seed:
1. Key Derivation: HKDF-SHA256(seed, info=b"clawlink-memory-encryption") → 32-byte AES key 2. Encryption: AES-256-GCM with os.urandom(12) nonce → authenticated ciphertext 3. Output Format: nonce(12 bytes) || ciphertext || GCM_tag(16 bytes)
3.4 Module Overview
| Module | Purpose | ~Lines |
|---|---|---|
config/ | Pydantic v2 configuration models + YAML loader | 190 |
identity/ | Ed25519 keygen (PyNaCl), MAC fingerprint, JWT creation/validation, multi-key verifier | 400 |
node/ | Starlette MCP server, tool implementations, subprocess sandbox, Docker backend | 1,200 |
hub/ | Stdio MCP server, NodePool, ToolRouter with trust gating, agent orchestration | 800 |
memory/ | AES-256-GCM crypto, SQLite schema, MemoryStore with Midnight sync queue | 300 |
secrets/ | SecretsVault (remote-only, no disk cache), runtime environment injection | 200 |
blockchain/ | CardanoClient, wallet, CIP-68, MerkleTree rewards, AgentMidnightClient, NodeMidnightClient, DirectPaymentManager, ViolationReporter | 3,500 |
trust/ | TrustScorer (7+7 metrics), AnomalyDetector, ReputationOracle, TrustCache | 700 |
privacy/ | ZKRatioProver, MockMidnightBackend, CompactMidnightBackend | 400 |
cli.py | Click CLI: init, pubkey, node start, mint, stake, governance, rewards, reputation | 500 |
Trust & Credibility System
The Clawlink trust system is the primary mechanism by which subnets enforce quality of service. It operates at three levels: individual agent scoring, network-wide anomaly detection, and cross-subnet reputation portability.
4.1 Multi-Dimensional Trust Scoring
The TrustScorer computes trust as a weighted sum of normalized metrics. Each metric is clamped to empirically determined bounds and normalized to [0, 1] before weighting. Inverted metrics (where higher raw values indicate lower trust) are subtracted from 1.0 after normalization.
Agent Trust Metrics (7 dimensions):
| Metric | Weight | Range | Normalization |
|---|---|---|---|
compute_consumed | 0.25 | 0 – 1,000 units | Linear |
cross_node_diversity | 0.20 | 0 – 50 nodes | Linear |
connection_duration | 0.15 | 0 – 10,000 hours | Linear |
stake_depth | 0.15 | 0 – 100,000 $CLAW | Linear |
agent_age | 0.15 | 0 – 730 days | Linear |
dispute_count | 0.10 | 0 – 20 disputes | Linear (inverted) |
contribution_ratio | 0.05 | 0 – ∞ | Tiered (see below) |
Contribution ratio uses a tiered normalization:
| Ratio Range | Trust Component | Classification |
|---|---|---|
| < 0.1 | 0.0 | Freeloading |
| 0.1 – 0.5 | 0.3 | Below par |
| 0.5 – 1.0 | 0.6 | Contributing |
| ≥ 1.0 | 1.0 | Net contributor |
Host Trust Metrics (7 dimensions):
| Metric | Weight | Range |
|---|---|---|
uptime | 0.20 | 0 – 100% |
unique_agents | 0.15 | 0 – 500 agents |
agent_retention | 0.15 | 0 – 100% |
dispute_ratio | 0.15 | 0 – 1.0 (inverted) |
operator_age | 0.10 | 0 – 730 days |
stake_amount | 0.10 | 0 – 500,000 $CLAW |
ban_ratio | 0.15 | 0 – 1.0 (inverted) |
ban_ratio exceeds 5%, the entire host trust score is halved. This prevents operators from maintaining high scores while systematically banning agents to avoid disputes.
4.2 Anomaly Detection
The AnomalyDetector identifies three categories of social-graph manipulation:
Scores how suspicious an agent’s node-usage pattern is on a 0.0 (clean) to 1.0 (highly suspicious) scale. Two signals contribute equally: diversity score (agents using only 1 node score 1.0, 2 nodes score 0.6) and concentration score (>80% of compute on a single node triggers linear escalation).
Uses connected-component analysis on the mutual-interaction graph to identify groups of agents that exclusively interact with each other — a hallmark of collusion rings. The algorithm builds undirected mutual-interaction edges, performs BFS to find connected components, and filters to keep only components where every member interacts exclusively within the group.
Traces funding chains through the Cardano UTXO graph. For each directed funding edge, confidence is computed as the average of the fraction of the sender’s total outgoing and the fraction of the receiver’s total incoming. Chain detection follows transitive paths (A funds B funds C) with a 0.8 damping factor. Links with confidence above 0.3 are flagged.
4.3 Contribution Ratio (BitTorrent Model)
The ContributionTracker implements peer-to-peer resource accounting inspired by BitTorrent’s seeding ratio. Every tool call is recorded as a ContributionInteraction with a cost derived from the tool cost map:
| Tool | Cost Units | CC Price |
|---|---|---|
exec | 10.0 | 100 CC |
spawn_agent | 10.0 | 100 CC |
write_file | 5.0 | 50 CC |
read_file | 1.0 | 10 CC |
grep | 1.0 | 10 CC |
glob | 0.5 | 5 CC |
agent_status/result/cancel/list | 0.5 | 5 CC |
node_info | 0.1 | 1 CC |
The ratio formula is: uploaded_cost / (downloaded_cost + 1). A 7-day grace period applies to new members — agents with no upload history receive a ratio of 1.0 until their first interaction ages past the grace window.
4.4 Cross-Subnet Reputation Oracle
The ReputationOracle enables agents to carry reputation across subnet boundaries using Ed25519-signed attestations. Aggregation uses recency-weighted scoring: each attestation’s weight is exp(-age_days / 30), ensuring recent attestations dominate the composite score.
When importing reputation into a target subnet, a trust discount of 0.5 is applied by default — an agent’s imported reputation is worth half its original value. The cross-subnet bonus is capped at 20% of the final agent trust score, preventing external reputation from overwhelming local observations.
4.5 Trust-Gated Routing
The Hub’s ToolRouter integrates trust evaluation into the tool call pipeline. Before routing a request, the router:
1. Retrieve agent trust score from TrustCache (TTL=300s) 2. Check against subnet min_score threshold (default 0.3) 3. Evaluate self_dealing_score vs self_dealing_threshold (default 0.7) 4. Verify active payment channel with sufficient $CLAW balance via DirectPaymentManager 5. Record tool call via NodeMidnightClient (utilization tracking) → Agents failing any gate receive an error — tool call is NOT forwarded
Blockchain Identity Layer
5.1 CIP-68 Agent Identity NFTs on Cardano
Every Clawlink agent has an on-chain identity implemented as a CIP-68 NFT pair on Cardano. CIP-68 defines a two-token pattern:
Locked at a script address, carries an updatable AgentDatum containing agent_name, owner (VerificationKeyHash, 28 bytes), trust_score, created_at, tier, dispute_count, and owner_policy_id. This token is never transferred — it exists solely to anchor mutable metadata.
Held in the agent’s wallet, serves as proof of identity ownership. Can be transferred to change agent ownership. Minting requires a burn of $CLAW tokens, creating a deflationary sink that discourages Sybil attacks.
5.2 The Eight Aiken Validators
Eight validators written in Aiken (Cardano’s smart contract language, compiled to Plutus V3) enforce protocol rules on-chain:
| Validator | File | Purpose |
|---|---|---|
mint_agent_id | mint_agent_id.ak | CIP-68 Agent ID minting and burning. Enforces owner signature, $CLAW burn cost, datum structure. |
claw_token | claw_token.ak | $CLAW minting policy. Controls emission (per-epoch caps), three burn variants, supply tracking via SupplyDatum. |
staking | staking.ak | Stake/Unstake/AddStake/Slash. Enforces tier thresholds, warmup periods, slashing percentages. |
governance | governance.ak | M-of-N arbitrator multisig with 10% bounds on parameter changes per update. Timelock enforcement. |
disputes | disputes.ak | Full dispute lifecycle: FileDispute, PostCounterBond, Arbitrate, Timeout, EmergencyBan. Bond mechanics with evidence hash. |
rewards | rewards.ak | Merkle tree reward distribution. PublishRoot, ClaimReward, ClaimVested (Merkle proof verification), RefundUnclaimed. |
owner_token | owner_token.ak | CIP-68 Owner Token minting for subnet operator identity. |
subnet_registry | subnet_registry.ak | Subnet listing lifecycle: create, update (bounded +/-500 bps), promote (7-day maturity gate), pause, terminate. |
5.3 Midnight Privacy Network Integration
Midnight serves as Clawlink’s privacy layer. The MidnightClient is an async httpx client that communicates with Midnight node endpoints for three categories of operations: Memory (encrypted key-value storage), Registry (node discovery with heartbeat TTLs), and Secrets (scope-based access control).
The system supports two Midnight backends: MockMidnightBackend (in-memory with HMAC-SHA256 32-byte proofs for development) and CompactMidnightBackend (production, invokes Midnight Compact runtime via subprocess generating 256-byte Groth16 proofs from compiled .zkey circuit files).
5.4 Zero-Knowledge Ratio Proofs
Clawlink uses zero-knowledge proofs for two privacy-sensitive operations:
An agent proves that its contribution ratio exceeds a subnet’s minimum threshold without revealing the actual ratio. The Compact circuit ratio_threshold_check accepts private inputs (actual ratio) and public inputs (threshold) and produces a Groth16 proof. Input scaling uses a 1,000,000 factor to convert floating-point ratios to the circuit’s integer Field type.
An agent proves that its stake amount qualifies for a specific tier (Bronze/Silver/Gold/Platinum) without revealing the exact stake amount. The tier_membership_check circuit verifies that the private stake amount exceeds the public tier threshold.
Subnet Discovery Protocol
6.1 Two-Layer Registry Architecture
Subnet discovery operates on a two-layer architecture balancing trust anchoring with operational privacy:
Subnet listings stored as SubnetListingDatum UTxOs at the subnet registry script address. Contains: subnet_name, owner (VKH), genesis_timestamp, version, member_count, endorsement_score (0-10,000 bps), dispute_count, status. Requires a 5 ADA deposit (refundable on termination).
Off-chain discovery data stored encrypted on Midnight under the subnet_registry namespace. Includes enriched metadata (descriptions, capabilities), endorsement details, and member endpoints. A bridge daemon synchronizes data between layers every ~20 seconds (matching Cardano block time).
6.2 Trust-Weighted Discovery Ranking
discovery_rank = 0.5 × endorsement_score + 0.3 × maturity_score + 0.2 × member_score endorsement_score (50%) = normalized from 0-10,000 bps; endorsements decay after 90 days maturity_score (30%) = 0.0 for Genesis (<7 days); linear scale to full weight at 28 days member_score (20%) = normalized from 0-1,000 members (logarithmic saturation)
6.3 Staked Relayer Service Market
Bridge daemon operators form a market for discovery relay services. Running a relayer requires 500 $CLAW minimum stake (Bronze tier) collateral, with a 100 $CLAW slashing penalty for delivering stale data and a 50 $CLAW/day base reward plus indexing bonus. This market structure ensures that discovery infrastructure is decentralized — no single entity controls subnet visibility.
6.4 Privacy-Preserving Membership
Subnet membership is never exposed on-chain. The MembershipRegistry stores all member entries encrypted on Midnight under the membership namespace. Member ranks follow a strict hierarchy:
| Rank | Level | Permissions |
|---|---|---|
guest | 0 | read_file, glob |
readonly | 1 | read_file, glob, grep, node_info |
worker | 2 | exec, read_file, glob, grep |
agent | 3 | exec, read_file, write_file, glob, grep, spawn_agent, agent_status, agent_result |
admin | 4 | All tools (*) |
owner | 5 | All tools (*) |
Guest access is configurable per-subnet: operators can enable guest tokens with limited permissions, rate limits (default 10 requests/minute), and short TTLs (default 1 hour). Guest tokens can optionally be bound to device fingerprint or IP address for additional security.
$CLAW Token Economy
7.1 Token Allocation
The $CLAW token has a fixed total supply of 1,000,000,000 (1 billion) tokens.
| Category | Allocation | Tokens | Rationale |
|---|---|---|---|
| Community Rewards | 40% | 400,000,000 | Emission rewards for operators, stakers, contributors. Ensures long-term network sustainability. |
| Treasury | 20% | 200,000,000 | Protocol development, grants, partnerships, emergency reserves. M-of-N multisig governed. |
| Team | 15% | 150,000,000 | Core development team. Subject to vesting schedule. |
| Investors | 10% | 100,000,000 | Strategic investors and early backers. Subject to lock-up periods. |
| Founder | 8% | 80,000,000 | Founder allocation. Longest vesting schedule. |
| Ecosystem | 5% | 50,000,000 | Integrations, developer tooling, documentation bounties, hackathon prizes. |
| Public Sale | 2% | 20,000,000 | Initial liquidity and public distribution. |
7.2 Emission Schedule and Halvings
Community rewards (400M tokens) are distributed through an emission schedule with halvings every 730 epochs (approximately 2 years at 1 epoch/day — Clawlink epochs are independent of Cardano’s 5-day mainnet epochs). Each epoch’s rewards are split:
| Pool | Share | Distribution Basis |
|---|---|---|
| Operators | 60% | Trust-weighted via RewardManager.compute_epoch_rewards() |
| Stakers | 30% | Stake-weighted, proportional to staked $CLAW |
| Treasury | 10% | Accumulates for governance-directed spending |
7.3 Staking Tiers and Access Control
| Tier | Minimum Stake | Access Level | Rate Limit |
|---|---|---|---|
| Bronze | 500 $CLAW | Basic: read-only tools, limited exec | 50 RPM |
| Silver | 2,000 $CLAW | Standard: full tool access, agent spawning | 100 RPM |
| Gold | 10,000 $CLAW | Premium: priority routing, higher rate limits | 200 RPM |
| Platinum | 50,000 $CLAW | Sovereign: unlimited access, governance voting, subnet creation | Unlimited |
7.4 Burn Mechanisms
Agents pay $CLAW directly to node operators per tool call via off-chain payment receipts stored on Midnight, settled on-chain each epoch. The DirectPaymentManager tracks per-session sequence counters and submits payment proofs via NodeMidnightClient. This replaces the deprecated BurnForCompute model and eliminates the oracle dependency.
Minting a CIP-68 Agent ID NFT requires burning agent_id_burn_cost $CLAW (set by governance). Makes Sybil attacks expensive — each fake identity requires a fresh token burn.
A general-purpose burn mechanism for future protocol extensions. All burn operations are recorded in the SupplyDatum on-chain, tracking total_minted, total_burned, and current_epoch.
7.5 Network Sustainability Loop
1. Operators stake $CLAW → earn emission rewards (trust-weighted) 2. Agents hold $CLAW → pay per tool call via direct payment channels 3. Payments flow from agents to operators each epoch (on-chain settlement) 4. Operators earn more $CLAW from emissions proportional to trust scores 5. Higher trust scores attract more agents, increasing payment channel volume 6. Agent ID creation and listing fees burn $CLAW (deflationary) 7. Reduced supply + sustained payment demand → price appreciation 8. Price appreciation attracts more stakers → back to step 1
Security Model
8.1 Bidirectional Authentication
| Boundary | Mechanism | Protection |
|---|---|---|
| Hub → Node | JWT EdDSA (Ed25519) with aud claim |
Token replay across nodes; aud claim prevents cross-node use |
| Node → Hub | HMAC-SHA256 result verification (HKDF-derived keys) | Result tampering by compromised relay infrastructure |
| Relay Messages | Full Ed25519 message signing | Non-repudiation for WebSocket relay messages |
| Node Identity | Node IDs derived from JWT sub claim (not client-reported) |
Node impersonation vulnerability |
8.2 Sandboxed Execution (Docker)
Memory: 256 MB hard limit (mem_limit=256m) CPU: 50% of one core (cpu_quota=50000) Network: Disabled (network_disabled=True) Filesystem: Read-only root (read_only=True) + tmpfs for /tmp Privileges: No new privileges (--security-opt=no-new-privileges)
Three sandbox backends available: Docker (full isolation, production), Native (asyncio.create_subprocess_shell with timeout, trusted environments), and Bubblewrap (bwrap for Linux without Docker).
8.3 Economic Deterrents
Beyond technical security, Clawlink’s economic design creates strong deterrents against misbehavior:
EmergencyBan redeemer, bypassing the normal dispute timeline for cases of active exploitation.
Competitive Landscape
Clawlink occupies a unique position at the intersection of AI agent coordination, blockchain identity, and privacy-preserving networking.
| Dimension | Clawlink | Bittensor (TAO) | Fetch.ai (ASI) | OpenClaw / OpenAI |
|---|---|---|---|---|
| Identity Model | CIP-68 NFT on Cardano (Ed25519, single-key) | Hotkey/Coldkey on Substrate | DID-based on Fetch.ai chain | API keys / OAuth |
| Trust System | 7-metric scoring + anomaly detection + cross-subnet oracle | Incentive-based (Yuma consensus) | Reputation staking | Platform-managed |
| Privacy Layer | Midnight ZK proofs (Groth16), encrypted membership | None (all on-chain) | TEE-based confidential compute | Centralized |
| Token Utility | Staking tiers, CC burn, governance, subnet deposits | Staking for subnet emissions | Staking for agent registration | No token |
| Agent Protocol | MCP (Anthropic standard) | Custom Bittensor protocol | Open Economic Framework | Proprietary APIs |
| Operator Sovereignty | Full: own rules, own thresholds, own membership | Partial: subnet owner sets weights | Partial: marketplace rules | None: platform-controlled |
Key Differentiators
Clawlink is the first blockchain-identity system built specifically for the Model Context Protocol, the emerging standard for AI agent tool use. Any MCP-compatible client (Claude Code, VS Code extensions, custom agents) can connect without protocol translation.
Unlike Bittensor, where all staking and emission data is public on-chain, Clawlink stores operational data (membership, contribution ratios, interaction histories) encrypted on Midnight. Operators never expose their member lists or service metrics to competitors.
The Compute Credit and contribution ratio system tracks economic value at the granularity of individual tool calls, not just block-level transactions. This enables precise free-rider detection and resource accounting impossible in block-oriented systems.
Implementation Status
Clawlink is in active development with significant infrastructure complete.
Completed Proposals
build-clawlink-v1 — Core system buildwire-trust-pipeline-v1 — TrustScorer wired into ToolRouterwire-credit-contribution-v1 — CC + ContributionTrackerwire-discovery-pipeline-v1 — SubnetIndex + RelayerRegistrywire-dashboard-server-v1 — Dashboard on port 7901add-hub-blockchain-status-v1 — Read-only MCP blockchain toolsadd-subnet-registry-management-v1 — On-chain endorsement mintingadd-zk-compact-circuits-v1 — CompactMidnightBackend Groth16add-reward-cli-v1 — Epoch publish + claim CLIadd-governance-cli-v1 — M-of-N arbitrator multisigadd-security-hardening-v1 — JWT audience, HMAC, signingadd-sandbox-execution-v1 — Docker with resource limitsadd-agent-marketplace-v1 — MarketplaceRanker scoringadd-multi-model-orchestration-v1 — Claude/Gemini/GPT routingadd-cross-subnet-reputation-v1 — ReputationOracle attestationsadd-zk-ratio-proofs-v1 — ZKRatioProver with mock + compactIn Progress
Per-subnet access control with guest tokens, rate limiting, and rank-based permissions. This is the final gating feature before public launch.
Roadmap
sub claims. Docker sandbox backend with memory/CPU/network/filesystem restrictions deployed. $CLAW minting CLI with governance parameter integration operational. Systemd service hardening (ProtectSystem=strict, NoNewPrivileges) secures production deployments. 1,245 tests validate the full stack.
Conclusion
Clawlink addresses the three fundamental gaps preventing AI agents from operating as accountable network participants: identity, trust, and privacy. By anchoring agent identity on Cardano as CIP-68 NFTs, implementing multi-dimensional trust scoring with anomaly detection, and encrypting operational data on Midnight, Clawlink creates the infrastructure for sovereign agent networks where operators set their own rules and agents bear economic consequences for their behavior.
The $CLAW token economy aligns incentives across all network participants: operators earn rewards proportional to their trust scores, agents burn tokens for compute access, and stakers provide economic security in exchange for emission shares. The halving schedule and three burn mechanisms ensure long-term sustainability without reliance on continuous external capital.
The convergence of MCP standardization, Cardano’s mature UTXO model, and Midnight’s zero-knowledge privacy layer creates a unique window for building the trust infrastructure that AI agents need to operate safely in adversarial environments.
Every operator should be able to run a sovereign agent network. Clawlink makes this possible.