near-connect

Integrate NEAR wallets in dApps via sandboxed iframe executors.

14|3|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/near/agent-skills --skill near-connect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: near-connect
Source: https://github.com/near/agent-skills/tree/main/skills/near-connect
Command: npx skills add https://github.com/near/agent-skills --skill near-connect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Near-connect provides a secure, zero-dependency integration pathway for NEAR wallet functionality in dApps by sandboxing wallet executors in isolated iframes, reducing the risk of host page compromise.

Core Features & Use Cases

  • Secure sandboxed wallets with per-wallet isolation and independent updates
  • Multi-wallet support and seamless migration from near-wallet-selector
  • Manifest-driven configuration and permission model for mainnet and testnet

Quick Start

Use Near-connect to initialize a NearConnector, register a debug wallet if needed, and call wallet methods like signAndSendTransaction against a testnet endpoint.

Frequently Asked Questions about near-connect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate a NEAR wallet into my dApp without adding heavy dependencies?

You can integrate a NEAR wallet into your dApp with zero dependencies by using isolated iframe executors that sandbox wallet operations, reducing host page compromise risks while maintaining full wallet functionality.

How does sandboxed wallet isolation secure NEAR wallet transactions in a browser environment?

Sandboxed wallet isolation secures NEAR transactions by running each wallet executor in a separate iframe with a manifest-based permission model, using a secure postMessage protocol to prevent unauthorized access to the host page.

Can I migrate my existing dApp from near-wallet-selector to a multi-wallet setup?

Yes, you can migrate from near-wallet-selector to a multi-wallet setup that supports per-wallet isolation and independent updates, allowing seamless transitions across mainnet and testnet environments.

How do I configure manifest permissions for NEAR wallet connections on testnet?

You configure manifest permissions for NEAR wallet connections by defining allowed actions in a manifest file, initializing a NearConnector, and registering a debug wallet to test signAndSendTransaction calls against a testnet endpoint.

What front-end frameworks are compatible with sandboxed NEAR wallet executors?

Sandboxed NEAR wallet executors are compatible with various front-end frameworks, implementing dual action formats like ConnectorAction and near-api-js to execute manifest-permissioned transactions across different web environments.

Why does my dApp need dual action formats for NEAR wallet postMessage communication?

Your dApp needs dual action formats like ConnectorAction and near-api-js to standardize postMessage communication, ensuring that manifest-based permissions are enforced consistently across different NEAR wallet implementations and network endpoints.