INTNT PROTOCOL — WHITEPAPER

A General Intent Layer
for Trustless Execution

INTNT is an application-layer protocol that translates user intent into verified onchain execution. Users express what they want. A competitive solver network executes it. A five-layer settlement engine enforces the outcome — without trusting the solver.

Version 1.0 — Draft
Network Base (Base Sepolia testnet)
Date April 2026
Status Pre-mainnet
Abstract

Blockchain adoption has stalled at the execution layer. Despite 119 million verified accounts on Coinbase alone, only 7.3% transact monthly — a dormancy rate that has persisted for five years. The barrier is not education or regulation. It is the requirement that users think like computers: selecting chains, managing gas tokens, navigating bridges, and approving contracts manually for every action.


INTNT Protocol introduces an intent layer that abstracts this complexity entirely. Users sign a declarative intent — specifying desired outcome, acceptable parameters, and expiry — without initiating a transaction. A network of registered solvers competes to fill the intent optimally. A novel five-layer settlement architecture verifies the solver's solution atomically, ensures the user receives at minimum what they specified, and provides optimistic dispute resolution backed by solver stake. The protocol launches on Base and expands to all EVM chains in Phase 4, with Solana support planned thereafter.


The $INTNT token serves three structural functions: access control for solvers via staking, governance over protocol parameters, and yield distribution to stakers from protocol fees. A fourth emergent utility — onchain reputation scoring for solver wallets — positions INTNT as the trust primitive for autonomous AI agents operating onchain.

SECTION 01

The problem with crypto UX

Crypto promised to democratize finance. A decade later, the reality is that most people who own crypto never use it. The infrastructure exists — fast blockchains, deep liquidity, sophisticated financial primitives — but the interface between human intent and onchain execution remains broken.

93%
Monthly wallet dormancy on Coinbase
6+
Steps to execute a simple cross-chain swap
$4.2B
Lost to bridge exploits 2021–2025

The execution gap

When a user wants to swap ETH for USDC at the best available price, the protocol-level reality requires: identifying which chain offers the best rate, ensuring the correct gas token is available, approving the token spend, executing the swap, and — if the best rate is on another chain — bridging first. Each step introduces a new failure mode, a new approval, and a new opportunity for user error.

This is not a user intelligence problem. It is a design problem. The existing model forces users to speak the machine's language rather than their own. INTNT inverts this relationship.

The core insight: Users have intent — a desired outcome. Blockchains execute transactions — a specific sequence of operations. The gap between these two things is what INTNT fills.

Why existing solutions fall short

Current approaches — DEX aggregators, bridge interfaces, portfolio managers — reduce friction at individual steps but do not solve the underlying problem. They still require users to understand chain topology, manage multiple approvals, and accept execution risk at each step. They optimize the machine-language interface rather than replacing it.

Existing intent-adjacent protocols such as UniswapX and CoW Protocol address intent within single ecosystems or specific verticals (token swaps). No general-purpose, cross-chain intent layer with a verifiable settlement guarantee exists today. This is the gap INTNT fills.

SECTION 02

The INTNT solution

INTNT is a coordination protocol. It does not replace existing blockchains, DEXes, or liquidity venues. Instead, it sits above them — translating declarative user intent into verified onchain execution through a competitive solver network and a novel multi-layer settlement architecture.

How it works in three steps

  • Intent creation. The user signs a structured intent using EIP-712 — specifying input token, output token, minimum acceptable output, deadline, and a unique nonce. No transaction is broadcast. No gas is paid. The signed message is posted to the IntentBook contract, which stores it and emits an event.
  • Solver competition. Registered solvers — bots, market makers, or any technical operator — monitor the IntentBook for new intents. Each solver independently calculates the best execution path across available liquidity venues. The solver that can provide the best outcome submits their solution to the SettlementEngine.
  • Atomic verification and settlement. The five-layer SettlementEngine verifies the solver's solution atomically. If the solution satisfies all conditions — valid signature, eligible solver, correct output — it executes and the user receives their output. If any condition fails, the entire transaction reverts. The user loses nothing.

The key property: The user cannot receive less than they specified. The settlement contract enforces this as an invariant — not a trust assumption about the solver's honesty.

What users can express as intents

Intent typeExampleToday's alternative
Token swap"Get me the best price for 1 ETH in USDC"Compare 3 DEXes manually, choose chain, approve, swap
Conditional trade"Buy SOL if BTC drops 5% in the next 24h"Custom bot or centralized exchange limit order
Yield optimization"Deposit my USDC in the highest APY pool under 5% depeg risk"Check 4 protocols across 3 chains weekly
Cross-chain action"Bridge and deposit in one step"Bridge separately, wait for confirmation, then deposit
SECTION 03

Protocol architecture

INTNT's core innovation is the separation of financial logic from verification logic. Traditional smart contracts mix these concerns — a bug anywhere can drain funds. INTNT's five-layer architecture isolates each concern into its own contract, with funds touching only one layer.

L1
Intent validator
Verifies the user's EIP-712 signature and consumes the nonce to prevent replay attacks. No funds ever enter this contract.
NO FUNDS
L2
Solver verifier
Confirms the solver is registered, staked, and in good standing. Manages reputation scores and slashing for bad behavior.
NO FUNDS
L3
Execution sandbox
Simulates the solver's proposed execution before any money moves. Measures actual output token delta. Reverts if output misses the user's minimum.
NO FUNDS
L4
Settlement
The only contract that moves funds. Intentionally under 100 lines of logic. Calls L1→L2→L3 in sequence, then executes the transfer atomically.
FUNDS HERE
L5
Dispute escrow
Holds solver fees in escrow for a 10-minute dispute window. Users can challenge fraud. After the window closes, fees auto-release.
OPTIMISTIC

Why this design matters for security

The blast radius of a bug is contained to the layer in which it exists. A flaw in the signature verification logic (L1) cannot drain funds — L1 holds no funds. A flaw in solver reputation calculation (L2) cannot drain funds — L2 holds no funds. Only L4 touches funds, and L4 is intentionally minimal: its only responsibility is to call the other layers in sequence and execute token transfers if all checks pass.

This means the auditable financial surface is under 100 lines of Solidity — compared to hundreds or thousands of lines in monolithic settlement contracts. Smaller auditable surfaces mean fewer vulnerabilities and more confident deployments.

Governance upgradeability

Each layer is independently upgradeable by governance. If the community votes to change solver verification parameters, only L2 is redeployed. L4 — the financial core — can remain immutable indefinitely. Competitors running monolithic contracts must re-audit everything for any change. INTNT evolves at the edges while the financial core stays frozen and trusted.

The INTNT settlement architecture comprises five independent Solidity contracts deployed on Base. Each contract has a single, narrow responsibility. Inter-contract calls are permissioned — only Layer 4 can invoke Layer 2's recordFill() and slash() functions, and only Layer 4 can invoke Layer 3's simulate().

3.1 Layer 1 — IntentValidator.sol

Responsible for cryptographic verification of user intents using EIP-712 structured signing. The domain separator is bound to the contract address and chain ID at deploy time, preventing cross-chain and cross-contract replay attacks.

// Core intent data structure
struct Intent {
    address user;           // intent creator
    address inputToken;     // ERC-20 being spent
    uint256 inputAmount;    // amount to spend
    address outputToken;    // ERC-20 desired
    uint256 minOutput;      // floor — enforced by L4
    uint256 deadline;       // unix timestamp expiry
    uint256 nonce;          // prevents replay
    bytes32 intentHash;     // keccak256 of above
}

The validateAndConsume() function verifies the signature, checks deadline and nonce freshness, marks the nonce as consumed (state write), and returns the canonical intent hash. Nonce consumption occurs before L3 simulation — a deliberately conservative design that prevents griefing via repeated partial-fill attempts against the same intent.

A read-only isValid() function is available for off-chain solver pre-flight checks without consuming the nonce.

3.2 Layer 2 — SolverVerifier.sol

Manages solver registration, staking, reputation, and slashing. Solvers must hold a minimum $INTNT stake (governance-adjustable, initially 10,000 $INTNT) to be active. Reputation scores range 0–1000 and are computed onchain from fill history.

// Reputation growth curve (fills → points per fill)
fills  1100:   +5 points per fill
fills  101500: +2 points per fill
fills  501+:    +1 point per fill
max:          1000 points

// Slashing mechanics
slash amount = stakedAmount × slashPercent / 100
reputation   = max(0, score − reputationDecayPerSlash)
deactivate   if stakedAmount < minimumStake

Slashed tokens are sent to address(1) — a dead address used as a burn target compatible with all ERC-20 implementations. The slash percentage and minimum stake are governance parameters, allowing the protocol to calibrate solver economics as the network matures.

3.3 Layer 3 — ExecutionSandbox.sol

The most architecturally novel layer. Rather than trusting the solver's claimed output amount, L3 executes the solver's calldata against an approved target contract and measures the actual output token balance delta of the user's address. This simulation runs in the same transaction as settlement — no trusted oracle required.

// Simulation flow
1. Check target is on governance-approved whitelist
2. Snapshot outputToken.balanceOf(user) → balanceBefore
3. Execute solution.callData against solution.target
4. Snapshot outputToken.balanceOf(user) → balanceAfter
5. outputReceived = balanceAfter − balanceBefore
6. Require outputReceived >= intent.minOutput

The approved target whitelist — governed by $INTNT holders — controls which DEX routers, bridge contracts, and liquidity venues solvers can route through. This prevents solvers from calling arbitrary contracts while allowing the network to expand to new venues via governance vote.

A dryRun() view function allows solvers to pre-flight their solutions off-chain using eth_call before spending gas on actual submission.

3.4 Layer 4 — SettlementFinalizer.sol

The only contract that holds or transfers user funds. Intentionally minimal — the entire financial logic is under 100 lines. Implements a manual reentrancy guard (no library dependency) and marks intents as filled before executing transfers.

// Settlement sequence (atomic)
1. Require Layer2.isEligible(solver)          // cheapest check first
2. intentHash = Layer1.validateAndConsume()   // consumes nonce
3. Require !filled[intentHash]                // double-fill guard
4. simResult = Layer3.simulate()              // verify output
5. If sim failed: slash solver, revert
6. filled[intentHash] = true                  // before transfers
7. Pull inputToken from user → this
8. Transfer (inputAmount − fees) → solver
9. Transfer protocolFee → treasury
10. Transfer solverFee → Layer5 escrow
11. Layer2.recordFill(solver)                 // update reputation

Fee parameters: solver fee 0.10% of input amount, protocol fee 0.05%, total 0.15%. Both adjustable by governance with a hard cap of 1% total.

3.5 Layer 5 — DisputeEscrow.sol

Implements an optimistic dispute mechanism inspired by Optimistic Rollup design. Solver fees are escrowed for a configurable dispute window (default 600 seconds, governance range 60–86400 seconds). Any address can raise a dispute within the window by calling raiseDispute(intentHash, reason).

Approved arbiters (initially the founding team, progressively decentralized) resolve disputes by calling resolveDispute(intentHash, fraudProven, refundUser). If fraud is confirmed, the solver's L2 stake is slashed and the escrowed fee is refunded to the challenger. If the dispute fails, the fee is released to the solver immediately.

A batchRelease(bytes32[]) function allows solvers to claim multiple fees in a single transaction — critical for high-volume solvers managing hundreds of fills daily.

SECTION 04

The solver network

Solvers are the execution layer of INTNT. They are independent operators — bots, market makers, or technical individuals — that monitor the IntentBook for open intents and compete to fill them profitably.

Solver architecture

A solver comprises four functional modules:

ModuleResponsibilityTechnology
Event listenerMonitors IntentBook for new IntentPosted events via WebSocketPython asyncio + web3.py
PathfinderQueries approved DEX routers for optimal execution path and output quote0x API, 1inch API, direct pool queries
Execution engineConstructs and submits the solution transaction to SettlementFinalizerweb3.py, custom calldata encoding
Risk managerEvaluates profitability after gas costs; skips negative-EV intentsCustom Kelly-inspired position sizing

Solver economics

Solvers earn 0.10% of the input amount on every filled intent. At $1M in daily volume, a single solver capturing 30% of fills earns approximately $300/day in fees before gas costs. Early solvers additionally receive $INTNT liquidity mining rewards, materially improving unit economics during the bootstrap phase.

solver_daily_earnings = daily_volume × fill_share × 0.001 − gas_costs + $INTNT_rewards

Reputation and competition

Solver reputation scores — computed entirely onchain from fill history — serve two functions. First, they act as a market signal: users and integrating apps can filter for high-reputation solvers. Second, they become the basis for INTNT's AI agent reputation primitive (see Section 6). Early solvers who accumulate reputation during the testnet and bootstrap phases hold a durable competitive advantage as the network scales.

Cold start strategy: The founding team operates the first solver, ensuring all posted intents can be filled from day one. Open-source solver templates lower the barrier for technical operators to join. Liquidity mining incentives from the 40% community allocation pay early solvers above their organic fee earnings until the network reaches self-sustaining volume.

SECTION 05

$INTNT token economics

$INTNT is an ERC-20 token with three structural utilities and one emergent utility. It is not a governance token that happens to exist — each utility is load-bearing to the protocol's operation.

Utility 1 — Solver access

Solvers must stake a minimum of 10,000 $INTNT in the SolverVerifier contract to be eligible to fill intents. This creates demand for the token directly correlated to solver network growth. As intent volume increases, more solvers join, each requiring a minimum stake purchase. Bad actors are slashed — tokens burned permanently — creating deflationary pressure from protocol misuse.

Utility 2 — Governance

$INTNT holders govern all adjustable protocol parameters via Snapshot voting with onchain execution via a Governor contract and Timelock. Governable parameters include: fee rates, minimum solver stake, slash percentages, dispute window duration, approved execution targets (L3 whitelist), and treasury allocation.

Utility 3 — Staker yield

25% of all protocol fees flow to $INTNT stakers proportional to their stake. This creates real yield backed by real transaction volume — not an emission schedule. The yield scales linearly with protocol usage.

staker_yield = (daily_volume × 0.0015 × 0.25) × (your_stake / total_staked)

Supply allocation

AllocationPercentagePurposeVesting
Community incentives40%Liquidity mining, solver rewards, early user grantsDistributed over 36 months via governance
Protocol treasury25%Governed by $INTNT holdersControlled by governance from day 1
Team20%Founding team and future hires4-year vest, 1-year cliff
Ecosystem fund15%Audits, grants, integrations, partnerships2-year vest, deployed as needed

Fee flow

RecipientShareMechanism
Solver60% of total fee (0.09% of intent)Direct transfer on settlement
$INTNT stakers25% of total fee (0.0375% of intent)Distributed pro-rata to stakers
Protocol treasury15% of total fee (0.0225% of intent)Accumulated, deployed by governance

Revenue scenarios

Conservative
$1M daily volume
Protocol fees/day$1,500
Staker yield/day$375
Annual protocol$547K
Base case
$10M daily volume
Protocol fees/day$15,000
Staker yield/day$3,750
Annual protocol$5.4M
Growth case
$100M daily volume
Protocol fees/day$150,000
Staker yield/day$37,500
Annual protocol$54M
SECTION 06

The reputation primitive

The most underappreciated aspect of INTNT's design is its emergent fourth utility: a verifiable onchain trust score for autonomous execution agents.

As AI trading agents, DeFi bots, and autonomous wallets proliferate, every protocol they interact with faces a fundamental question: should this agent be trusted? Today there is no standard answer. Each protocol makes its own assessment, usually defaulting to either full permissionlessness (anyone can interact) or full permissioning (whitelist only).

The INTNT reputation score

Every solver wallet in INTNT accumulates an onchain reputation score based on four factors:

  • Fill rate — the percentage of submitted solutions that successfully settle
  • Execution quality — average output delivered versus minimum required (did the solver beat the floor?)
  • Speed — time from intent posting to fill submission
  • Slash history — permanent record of any slashing events

This score is fully verifiable by any contract, wallet, or protocol that can read Base state. It requires no oracle, no trusted intermediary, and no off-chain attestation.

The AI agent market

DeFi protocols can use INTNT reputation scores to gate access — "only interact with wallets that have INTNT reputation above 800." For AI agents operating autonomously, this score becomes a portable credential: evidence of reliable, non-fraudulent onchain execution history. As autonomous agent wallets become the dominant user archetype in DeFi, INTNT owns the trust primitive they all need.

This positions INTNT not only as an intent execution layer but as foundational infrastructure for the autonomous onchain economy — a market that barely exists today but will be substantial within three years.

SECTION 07

Development roadmap

PhaseTimelineMilestones
Phase 1
Protocol foundation
Months 1–3 Five contracts compiled and tested. Code4rena audit. Named firm audit. Base Sepolia testnet live. First intent filled by founding team solver.
Phase 2
Solver network
Months 4–6 Open-source solver template published. 5–10 early solvers onboarded. Uniswap v3, Curve, 1inch approved as execution targets. Reputation scores activated. Liquidity mining live.
Phase 3
Token launch
Months 7–9 $INTNT deployed. Uniswap v3 liquidity seeded from treasury. Staking activated. Governance live (Snapshot + Governor contract). Whitepaper v2 published.
Phase 4
Scale and reputation
Months 10–18 Ethereum mainnet, Arbitrum, Optimism expansion. TypeScript and Python SDKs. First partner integrations. Cross-chain intent support. AI agent reputation API.
SECTION 08

Risk factors

INTNT is pre-mainnet software. The following risks are material and should be understood by any participant.

Smart contract risk

Despite multiple audits and the architectural isolation of financial logic to Layer 4, smart contract exploits remain possible. Mitigations: staged TVL caps during initial deployment (single intent cap $1,000, total cap $50,000 in the first 90 days), two independent audits before mainnet, formal verification of core L4 invariants, and a bug bounty program.

Solver cold start

A protocol with no solvers cannot fill intents. Mitigations: the founding team operates solver zero from day one; liquidity mining rewards subsidize early solver economics; the open-source solver template minimizes technical onboarding friction.

Regulatory risk

$INTNT may be classified as a security in certain jurisdictions. Mitigations: legal opinion obtained before token launch; foundation or DAO LLC structure in a crypto-favorable jurisdiction; genuine utility from day one reduces the "investment contract" argument; progressive decentralization of governance.

Competitive risk

Established protocols (Anoma, ERC-7521, UniswapX) may expand to address the general intent layer. Mitigation: the reputation primitive is INTNT's durable differentiator — it accumulates with usage and cannot be replicated by a competing protocol starting fresh.

MEV and solver manipulation

Solvers could attempt to frontrun intents or manipulate execution prices within the allowed parameters. Mitigations: L3 simulation enforces minimum output strictly; commit-reveal patterns for high-value intents; private mempool support (Flashbots Protect) as a recommended solver configuration.

SECTION 09

Conclusion

INTNT Protocol addresses a foundational gap in the onchain economy: the translation layer between human intent and machine execution. By separating intent expression from transaction construction, introducing a competitive solver network for optimal execution, and enforcing outcomes through a novel multi-layer settlement architecture, INTNT makes crypto work the way users expect it to — not the way blockchains require it to.

The protocol launches on Base, targeting the 93% of wallet holders who own crypto but never use it. It expands to all major EVM chains and Solana in Phase 4. Its reputation primitive — an emergent byproduct of the solver network's onchain activity — positions INTNT as infrastructure for the autonomous agent economy that is developing alongside it.

$INTNT is a structurally necessary token: without solver staking, there are no solvers; without solvers, there are no fills; without fills, there are no fees. This alignment between token utility and protocol function makes $INTNT one of the few tokens in DeFi whose demand is directly correlated to the protocol's actual usage.

Join the network. The solver waitlist is open at intnt.xyz. Early solvers receive bonus $INTNT rewards, reduced stake requirements, and 2× reputation weighting at launch.

This document is provided for informational purposes only and does not constitute an offer or solicitation to purchase securities. $INTNT tokens have not been registered under the securities laws of any jurisdiction. This whitepaper describes a pre-mainnet protocol and is subject to change. Participation in INTNT Protocol involves significant risk including total loss of funds. Always conduct your own due diligence.