EverClaw Whitepaper

Sovereign AI Agent Infrastructure with On-Chain Identity, Decentralized Memory, and Tokenized Economics

March 2026 · Base Chain · v1.0

WHITEPAPER v1.0

1. Abstract

EverClaw is a decentralized platform for deploying, managing, and trading sovereign AI agents. Unlike traditional agent platforms where the operator controls your agent's lifecycle and data, EverClaw ensures that the agent's identity is owned by the user (as an NFT), the agent's memory is stored on decentralized infrastructure (IPFS/Filecoin), and the agent's compute is provisioned on user-controlled servers.

The platform introduces $ECLAW, a fair-launch token on Base whose value is directly tied to platform activity through a continuous buyback-and-burn mechanism funded by platform revenue. $ECLAW also enables agentic staking — a novel staking paradigm where yield is amplified by running active agents — and on-chain governance.

2. The Problem

The current AI agent landscape suffers from three critical flaws:

2.1 Platform Risk

Every major agent platform (ChatGPT, Claude, custom GPTs) stores your agent's configuration, memory, and learned behaviors on centralized servers. If the company changes its terms, gets acquired, shuts down, or bans your account — your agent and everything it learned ceases to exist.

2.2 Data Sovereignty

Users have no ownership over the data their agents generate. Conversation history, fine-tuning data, and behavioral patterns belong to the platform, not the user. There is no export, no portability, and no guarantee of persistence.

2.3 Technical Barrier

Self-hosting an agent (the only current path to sovereignty) requires DevOps knowledge, server management, and ongoing maintenance. This excludes 95% of potential users from running sovereign agents.

3. The EverClaw Solution

EverClaw bridges the gap between platform convenience and true sovereignty through three pillars:

• On-chain identity — every agent exists as an ERC-721 NFT with verifiable metadata
• Decentralized memory — state pinned to IPFS with Filecoin backup, CID stored on-chain
• Managed compute — dedicated VPS provisioned automatically, no DevOps required

The user owns the NFT. The NFT points to the state. The state is reconstructable from IPFS. No single point of failure can kill the agent.

4. Architecture

┌─────────────────────────────────────────────────────────┐
│                    EverClaw Platform                     │
├─────────────┬─────────────┬─────────────┬───────────────┤
│  Dashboard  │   Wizard    │  Explore    │   Settings    │
│  (app/)     │  (deploy)   │  (market)   │   (IPFS)      │
├─────────────┴─────────────┴─────────────┴───────────────┤
│                    Base Chain (8453)                      │
├──────────────────┬──────────────────┬───────────────────┤
│  AgentIdentity   │  Subscription    │  $ECLAW Token     │
│  NFT (ERC-721)   │  Manager (USDC)  │  + Staking        │
├──────────────────┴──────────────────┴───────────────────┤
│           IPFS / Filecoin (State Layer)                  │
├─────────────────────────────────────────────────────────┤
│        VPS Infrastructure (Compute Layer)                │
│   Hetzner / Vultr / DigitalOcean — user-provisioned     │
└─────────────────────────────────────────────────────────┘
    

5. Agent Identity (ERC-721)

Each deployed agent is minted as an ERC-721 NFT on Base. The token's on-chain metadata includes:

The NFT implements ERC-2981 for royalty enforcement — 5% on every secondary sale. The tokenURI() function generates fully on-chain JSON metadata, eliminating dependency on external servers for NFT display.

6. Decentralized State (IPFS / Filecoin)

Agent state — memory files, conversation history, system prompts, tool configurations — is serialized and pinned to IPFS on every significant state change. The pipeline:

1. Agent runtime detects state change (new memory, config update, etc.)
2. State is serialized to JSON and pinned to IPFS via Pinata
3. New CID is written on-chain via updateState(tokenId, newCID)
4. Filecoin storage deals are created for long-term persistence

At any point, a user can reconstruct their agent from scratch by reading the NFT's stateCID, fetching the data from IPFS, and deploying it to any compatible runtime.

7. Subscription Protocol

The SubscriptionManager contract handles payment lifecycle entirely on-chain in USDC:

Subscriptions are 30-day periods. Tier upgrades are prorated. The contract exposes isActive(tokenId) which the agent runtime checks as cryptographic proof of valid subscription.

8. $ECLAW Token Economics

8.1 Fair Launch

$ECLAW launches with zero presale, zero team allocation, and zero VC involvement. 100% of tokens enter circulation through the fair launch on a Base DEX. The team participates on equal footing with the community.

8.2 Token Utility

• Governance voting — protocol upgrades, fee structures, grants
• Agentic staking — stake alongside agents for yield
• Template marketplace — buy and sell premium agent templates
• Subscription discounts — pay with $ECLAW at reduced rates
• Priority access — early features, higher tiers, beta programs

8.3 Supply & Distribution

There is no team allocation. The founding team earns by building — not by holding a pre-mined bag.

9. Buyback & Burn Mechanism

Every revenue stream in the EverClaw ecosystem feeds a continuous buyback-and-burn pool:

The buyback contract:

1. Accumulates USDC from all revenue streams
2. Executes market buys of $ECLAW on the primary DEX
3. Burns purchased tokens by sending to 0x000...dEaD

This creates continuous deflationary pressure proportional to platform usage. More agents deployed → more revenue → more tokens burned → supply decreases.

10. Agentic Staking

EverClaw introduces agentic staking — a staking model where yield is tied to real platform activity rather than passive token lockup.

10.1 Mechanism

• Users stake $ECLAW in the staking contract
• Base yield is earned by all stakers proportionally
• Agent Activity Multiplier — stakers who also run active, subscribed agents earn bonus yield
• Multiplier scales with number of active agents and their uptime

10.2 Staking Tiers

10.3 Reward Sources

Staking rewards come from two sources:

• Inflationary rewards — from the 5% initial staking allocation (first 6 months)
• Fee sharing — percentage of platform fees distributed to stakers (after month 6)

This ensures the staking program is sustainable long-term without infinite token emission.

11. Governance

$ECLAW holders govern the protocol through on-chain proposals and voting:

Governable Parameters

• Subscription pricing tiers
• Buyback allocation percentages
• Staking reward rates and tier thresholds
• Ecosystem development fund allocation
• New feature prioritization
• Chain expansion decisions

Process

1. Proposal — any holder with ≥10,000 $ECLAW staked can submit
2. Discussion — 5-day community discussion period
3. Voting — 3-day on-chain vote, 1 token = 1 vote (staked tokens only)
4. Execution — passing proposals are executed by the multisig or directly on-chain

Quorum requirement: 10% of staked supply must vote for a proposal to pass.

12. Agent Marketplace

Trained agents have real value. An agent that has been running for months — learning, building knowledge, developing specialized capabilities — is worth more than a fresh deploy.

How It Works

• Agent NFTs can be listed on EverClaw's native marketplace or any ERC-721 platform
• State transfers with the token — buyer gets the full trained agent
• 5% royalty on secondary sales feeds the buyback pool
• Template creators earn 70% of template sale revenue

The marketplace enables a secondary economy of trained AI agents — a first in the industry.

13. Security Considerations

• Smart contracts — built on OpenZeppelin 5.1, compiled with Solidity 0.8.28
• Access control — Ownable pattern, subscription manager authorized separately
• Reentrancy — ReentrancyGuard on all payment functions
• IPFS integrity — CIDs are content-addressed; tampered data produces a different hash
• Key management — user wallets control agent NFTs; no platform custody
• Subscription proofs — isActive() is trustlessly verifiable on-chain

14. Roadmap