WISP Crypto Art

WISP

Private Intent
Execution Protocol

[X] [Gitbook] [Documentation]

What is wisp?

A chain-agnostic privacy layer for intents. Instead of sending a public transaction to a public mempool, Wisp transforms user actions into private, provably valid, solver-executable instructions.

Swap X for Y up to slippage s, then deposit into protocol Z. 
ZK Proof
┌───────────────────────┐
│         USER          │
│          │            │
│          ▼            │
│      ┌────────┐       │
│      │ INTENT │       │
│      └────────┘       │
│          │            │
│          ▼            │
│        SOLVER         │
│          │            │
│          ▼            │
│    ┌───────────┐      │
│    │ EXECUTION │      │
│    └───────────┘      │
└───────────────────────┘
  • validated by zk proofs
  • executed by solvers/relayers on any target chain.

Wisp becomes the "private control plane" for multichain usage.

Become an early user or solver

SCROLL DOWN FOR MAP ↓

How Wisp Works?

01. INTENT CONSTRUCTION LAYER

User Intent Format

A Wisp intent encodes:

  • Goal: High-level action (bridge, buy, stake).
  • Constraints: Slippage, budget, timing, gas.
  • Private Inputs: Address, amounts, tokens.

Represented as Public Metadata + Private Commitments.

Local Validation Proof

Before submission, user generates zk-proof asserting funds/permissions and protocol compliance. Reveals only boolean "valid" signal.

02. PRIVATE MEMPOOL

Intents posted to global encrypted pool. Indexing on abstract metadata.

  • No readable calldata.
  • No timing leaks.
  • Optional batching.
Anti-Leakage Properties

Prevents front-running and trace inference. Solvers see "surface shape" only, not strategy or identity.

03. DECENTRALIZED SOLVERS NETWORK

Solver Capabilities

Agents fetch intents, build execution plans across chains, and execute via AA wallets/bridges.

Solvers do not learn user address or full pipeline.

Execution Mechanics
  • AA/Smart Accounts: Non-custodial.
  • Cross-chain messaging: Sync final states.
  • Relayers: Gasless submission.

04. SOLVERS COMPETITION AND INCENTIVES

Solvers can:

  • Bid for intents.
  • Propose different routes.
  • Get paid on success.
  • Be slashed for invalid execution.

Creates a market-based execution layer with privacy guarantees.

05. SETTLEMENT AND CORRECTNESS PROOFS

Execution Receipts

Solver returns proof-backed receipt. Verified for correct chains, slippage, and constraints.

User-Level Settlement

Assets arrive via Smart accounts (zk-auth) or Anonymous relayed txs.

No link connecting Source address -> Destination address.

DRAG TO PAN / SCROLL TO ZOOM

WISP for Users / Solvers

Intent
ZK Proof
Raydium
PENDLE
Kalshi

Private cross-chain actions

Swap, bridge, lend, farm, vote, mint, rebalance — on any chain through one private intent layer.

Hidden calldata + routing

Transaction inputs and path selection remain private; only minimal correctness signals are revealed.

Private automation

Recurring/conditional intents (e.g., weekly rebalance, stop-loss, yield chase) executed without leaking strategy.

Selective disclosure

Users can reveal proofs, balances, or actions to chosen parties only (optional view keys).

Generate rewards for executing the intent process with a Solver lightweight client.

Privacy-Preserving Input

Receive encrypted / privacy-preserving intents with only the solvable surface exposed.

Generate Plans

Generate execution plans without learning user identity or full intent details.

Return Proofs

Return proof-backed receipts (correctness + constraint satisfaction).

Plug via Client

Plug into the network via a simple client (routing, bidding, settlement, slashing hooks).

SOLVER DOCUMENTATION COMING SOON

WISP TOKEN

Solver Staking

To become a Solver, a participant must have a $WISP stake. User intents are distributed among Solvers based on the size of their stake, ensuring fair routing and economic security.


                


                
                

                    

                        
Fee Token

                        
$WISP token is used as the fee asset when interacting with the protocol's privacy execution layer.

                    

                    

                        
Governance

                        
$WISP token holders govern key protocol parameters, upgrades, integrations, and treasury allocations, ensuring decentralized control over the protocol's evolution.