near-connect_skill

This skill helps NEAR dApps integrate multiple wallets securely via sandboxed executors, enabling easy signing and transaction flows.

5

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill near/agent-skills --skill near-connect

SKILL.md10.5 KB

Overview

This skill is a zero-dependency, lightweight wallet connector for the NEAR blockchain that runs wallet code in secure sandboxed iframes. It enables multi-wallet support, independent wallet updates, and safe execution of wallet executors without embedding third-party code into your dApp. Use it to integrate NEAR wallets, sign transactions and messages, or debug custom wallet executors.

How this skill works

Near-Connect fetches wallet manifests and loads each wallet's executor script into an isolated iframe sandbox with granular permissions. Wallets host their own executor code and can update independently; the connector exposes a unified NearWalletBase interface for signIn, signOut, signAndSendTransaction(s), signMessage, and account management. Feature filtering, injected wallet support, and optional WalletConnect integration let you control which wallets are offered to users.

When to use it

Integrating NEAR wallet connectivity into a dApp with minimal dependencies
Supporting multiple wallet providers and WalletConnect-compatible wallets
Signing and sending transactions or signing NEP-413 messages from a browser or mobile web app
Building or testing custom wallet executors in a secure sandbox
Migrating from near-wallet-selector to a lighter, sandboxed connector

Best practices

Filter wallets by required features (signMessage, testnet, etc.) to avoid showing unsupported wallets
Prefer near-api-js action format for reliability and compatibility when constructing transactions
Defer adding limited-access keys until after initial UX to improve conversion and security
Use debug wallet registration for local development and executor testing instead of modifying production manifests
Enable logging during development to diagnose manifest, sandbox, or transaction issues

Example use cases

Show a wallet selector popup and connect users to HOT, NEAR Mobile, OKX, or a WalletConnect wallet
Sign and send a single functionCall transaction using near-api-js transactions
Sign a NEP-413 message for off-chain authentication or attestations
Register a local debug wallet executor to iterate on wallet integration without changing remote manifests
Switch networks (mainnet/testnet) and refresh available wallets based on feature filters

FAQ

No. It is designed to be zero-dependency; wallet executors run in sandboxed iframes so you don't include third-party wallet code in your bundle.

Can I support WalletConnect wallets?

Yes. WalletConnect integration is optional and configured via a projectId and metadata in the connector options.

How do I test a custom wallet during development?

Use registerDebugWallet to register a local executor URL and test the wallet in the sandbox without changing the manifest source.