Add the manifest. Done.
Yes, adding ETH wallets to your app is as simple as loading the manifest in NearConnector.
import { NearConnector } from '@hot-labs/near-connect';
const connector = new NearConnector();
const manifest = await fetch('https://evm-on-near.dev/manifest.json').then(r => r.json());
await connector.whenManifestLoaded;
await Promise.all(manifest.wallets.map(wallet => connector.registerWallet(wallet)));
One familiar wallet,
another network.
This adapter lets an Ethereum wallet such as MetaMask approve actions for a NEAR account with the same 0x… address. NEP-518 makes the two transaction models fit together.
From click to finality
-
01
The dApp asks
A NEAR dApp sends a connection or transaction request through near-connect. This approval page verifies the requesting site and shows you what it wants to do.
-
02
The action is translated
The requested NEAR transfer, contract call, or limited access-key change is encoded as Ethereum-style calldata defined by NEP-518.
-
03
You approve
Your Ethereum wallet signs the encoded transaction on NEAR’s EVM-compatible RPC network. The private key stays inside your wallet, and every transaction still needs your approval.
-
04
NEAR executes
A relayer submits the signed payload to your
0x…account on NEAR. Its protocol wallet contract verifies the signature, converts the payload back into a NEAR action, and executes it.
A small, one-time setup
The first time you connect, you will be asked to approve a setup transaction. It adds a restricted function-call key that can call only rlp_execute on your own account.
The relayer key cannot replace your wallet or add a full-access key. Your Ethereum signature remains the authority for the action encoded inside every request.
rlp_execute onlyGo deeper
Important: This is experimental, non-custodial software provided “as is,” without warranties. Blockchain transactions are irreversible; review every transaction before approving and use the software at your own risk.