Pluton Terminology
We aim to abstract and simplify any-to-any cross-chain swaps and bridges through an intent-based system. To describe the protocol’s operations, we introduce the following Pluton-specific terminology:
Intent
An Intent is a high-level user request to perform an action, such as swapping or bridging tokens across chains (e.g., move USDT from Arbitrum to SOL on Solana). The intent object contains all necessary parameters: source/destination chains, tokens, amounts, and recipient details. Intents are the starting point for all protocol operations.
interface Intent {
id: string
fromChainId: number
fromToken: Token
fromAmount: string
toChainId: number
toToken: Token
toAddress: string
affiliate?: string
referrer?: string
slippage: number
}Quote
A Quote is a solver’s offer to fulfill a specific intent. It details the execution plan, including source and destination amounts, fees, rates, and estimated execution time. Quotes are submitted during the auction phase and are evaluated by the protocol to select the optimal solution.
interface Quote {
id: string
solverId: string
fromAmount: string
toAmount: string
fee: string
rate: string
estimatedDuration: number
executionPlan: ExecutionStep[]
}Solver
A Solver is an independent entity that listens for intents, generates quotes, and executes the required on-chain steps when selected. Solvers manage their own liquidity and infrastructure, and compete in real-time auctions to fulfill user intents.
Auction
The Auction is the process where the protocol broadcasts an intent to all registered solvers, collects their quotes within a defined window, and selects the best offer based on protocol and user criteria.
Claim
A Claim is the process by which a solver, after successfully fulfilling an intent and passing on-chain verification, receives a cryptographic signature from the protocol. This signature allows the solver to claim their reward from the protocol’s smart contract.
Affiliate & Referrer
Affiliate: An entity that integrates Pluton and may receive a share of protocol fees for referred transactions.
Referrer: A party that brings users or volume to the protocol, potentially earning a referral fee.
Error
Pluton standardizes error codes and messages for all protocol operations. Each error is documented and mapped to a specific failure scenario (e.g., no solver available, invalid quote, execution failure, verification failure).
Example: Multi-Step Execution
An intent (e.g., bridge USDT from Arbitrum to SOL on Solana) may require multiple ExecutionSteps:
Swap USDT to USDC on Arbitrum.
Bridge USDC from Arbitrum to Solana.
Swap USDC to SOL on Solana.
Each step is executed in order by the solver, with the protocol tracking progress and verifying completion.
Note: Pluton’s intent-based model enables flexible, composable, and secure cross-chain operations, with all actions transparently tracked and verified on-chain.
Last updated