
- Deposit tokens into the Verifier contract. The contract tracks your balance internally. (See Deposits)
- Swap or transfer by submitting intents. Users express their “intent” to perform a transaction (e.g., exchange USDT for USDC, or transfer tokens to another user). Intents can be submitted directly or bundled together by a third party like the Message Bus for atomic execution. (See Intent Types)
- Withdraw tokens to your NEAR account or external chain. For external chain asset transfer, the Verifier settles the withdrawal through the appropriate token bridge, delivering tokens to the destination address. (See Withdrawals)
Who is this documentation for?
Most applications integrating token swaps don’t need to work with the Verifier contract directly. The 1Click Swap API handles intent creation, market maker coordination, and execution for you. This section is for developers who need lower-level control and want to:- Interact with the Verifier smart contract directly
- Create payloads for the Message Bus (a matching system that brings together quotes from market makers with transaction requests)
Prerequisites
Before working directly with the Verifier contract, you should have:- A NEAR account (named account like
yourname.nearor implicit account) - Tokens to deposit (fungible tokens like USDC, USDT, or wrapped NEAR)
- Basic understanding of NEAR transactions and cross-contract calls
- Familiarity with JSON and digital signatures
Deployment
The Verifier smart contract is deployed atintents.near.
Source code
The contract is open source. You can find it on GitHub:NEAR Intents Repository
View the source code for the Verifier smart contract
The former name of the smart contract is “Defuse”. You may still see this name in some places in the codebase. It is planned to be updated in the future.
