@anywalletkit/protocol-swap2-near-intents

NEAR Intents (1Click) cross-chain swaps as a swap2 module: the wallet sends the source asset to a one-time deposit address, the solver network settles on NEAR and delivers on the destination chain. Standalone through NearIntentsSwap2Protocol, or as one provider of the router.

Install

npm install @anywalletkit/protocol-swap2-near-intents @anywalletkit/core
# or: pnpm add @anywalletkit/protocol-swap2-near-intents @anywalletkit/core  ·  yarn add @anywalletkit/protocol-swap2-near-intents @anywalletkit/core

On npm: @anywalletkit/protocol-swap2-near-intents, published from the release workflow with provenance.

Behind remoteProvider

When the provider runs on your server, spread its pins into the app's stub: remoteProvider({name: "near_intents", baseUrl, ...nearIntentsPins}). Every 1Click route pays a deposit address minted per quote, which nothing can pin ahead: nearIntentsPins call no contract, approve no spender, and open the stub to deposit-address routes (depositAddressRoutes). Without it the engine refuses them. The deposit address is your server's word, so run the server you trust.

Activity

Most 1Click legs leave no stable on-chain marker: the source leg is a plain transfer to a deposit address that exists for one swap, and the destination leg is a plain transfer from a solver / bridge account that changes per swap (on Ethereum the wallet's arrivals came from Relay's router or solver EOAs; on TON from fresh addresses). describeActivity(tx, ctx) therefore returns null for EVM / TON / Solana / Tron / BTC — the kit's intent journal (the intentId returned by swap2()) ties those transfers back to the swap, and the generic fallback shows them as send / receive.

What it does recognize is the NEAR side, where the settlement contract is fixed: a NEP-141 transfer between the owner and intents.near →

• owner → intents.near (ft_transfer_call deposit): bridge, "Bridged wNEAR";
• intents.near → owner (execute_intents / ft_withdraw): bridge, "Received JAMBO via NEAR Intents".

Subtitle "NEAR Intents", counterparty intents.near.

Fixtures (fixtures/activity/): two public NEAR transactions from nearblocks (a 20.5 wNEAR deposit through the bridge-mng.near relayer, a 231 JAMBO withdrawal — the test wallet has no NEAR account); negatives: the LI.FI Diamond's NEARIntents facet on Ethereum (LI.FI's transaction, not this module's) and the test wallet's own 13.9 USD₮ 1Click deposit on TON, which must stay unrecognized.