NEAR Wallet Selector
The NEAR Wallet Selector makes it easy for users to interact with your dApp. This package presents a modal to switch between a number of supported wallet types:
Preview
React, Vue and Angular variations of the Guest Book dApp can be found in the examples
directory. You can use these to gain a concrete understanding of how to integrate near-wallet-selector
into your own dApp.
Installation and Usage
The easiest way to use near-wallet-selector
is to install it from the NPM registry:
yarn add @near-wallet-selector/core
npm install @near-wallet-selector/core
Then use it in your dApp:
import NearWalletSelector from "@near-wallet-selector/core";
const selector = await NearWalletSelector.init({
wallets: ["near-wallet", "sender-wallet", "ledger-wallet", "math-wallet"],
network: "testnet",
contract: { contractId: "guest-book.testnet" },
});
API Reference
.init(options)
Parameters
options
(object
)
wallets
(Array<string>
): List of wallets you want to support in your dApp.network
(string | object
): Network ID or object matching that of your dApp configuration . Network ID can be either mainnet
, testnet
or betanet
.
networkId
(string
): Custom network ID (e.g. localnet
).nodeUrl
(string
): Custom URL for RPC requests.helperUrl
(string
): Custom URL for creating accounts.explorerUrl
(string
): Custom URL for
contractId
(string
): Account ID of the Smart Contract used for .signIn
and .signAndSendTransaction
.methodNames
(Array<string>?
): Specify limited access to particular methods on the Smart Contract.ui
: (object?
)
theme
(string?
): Specify light/dark theme for UI. Defaults to the browser configuration when omitted or set to 'auto'. This can be either light
, dark
or auto
.description
(string?
): Define a custom description in the UI.
Returns
Promise<NearWalletSelector>
Description
Initialises the selector using the configured options before rendering the UI. If a user has previously signed in, this method will also initialise the selected wallet, ready to handle signing.
Example
await NearWalletSelector.init({
wallets: ["near-wallet", "sender-wallet", "ledger-wallet", "math-wallet"],
network: "testnet",
contract: { contractId: "guest-book.testnet" },
});
.show()
Parameters
Returns
Description
Opens the modal for users to sign in to their preferred wallet. You can also use this method to switch wallets.
Example
selector.show();
.hide()
Parameters
Returns
Description
Closes the modal.
Example
selector.hide();
.signIn(params)
Parameters
params
(object
)
walletId
(string
): ID of the wallet (see example for specific values).accountId
(string?
): Required for hardware wallets (e.g. Ledger Wallet). This is the account ID related to the public key found at derivationPath
.derviationPath
(string?
): Required for hardware wallets (e.g. Ledger Wallet). This is the path to the public key on your device.
Returns
Description
Programmatically sign in to a specific wallet without presenting the UI. Hardware wallets (e.g. Ledger Wallet) require accountId
and derivationPath
to validate access key permissions.
Example
await selector.signIn({
walletId: "near-wallet",
});
await selector.signIn({
walletId: "sender-wallet",
});
await selector.signIn({
walletId: "math-wallet",
});
await selector.signIn({
walletId: "ledger-wallet",
accountId: "account-id.testnet",
derviationPath: "44'/397'/0'/0'/1'",
});
.signOut()
Parameters
Returns
Description
Signs out of the selected wallet.
Example
await selector.signOut();
.isSignedIn()
Parameters
Returns
Description
Determines whether the user is signed in.
Example
const signedIn = await selector.isSignedIn();
console.log(signedIn)
.getAccounts()
Parameters
Returns
Promise<Array<object>>
accountId
: An account id for each account associated with the selected wallet.
Description
Retrieves account information when the user is signed in. Returns an empty array when the user is signed out. This method can be useful for wallets that support accounts at once such as WalletConnect. In this case, you can use an accountId
returned as the signerId
for signAndSendTransaction
.
Example
const accounts = await selector.getAccounts();
console.log(accounts);
.on(event, callback)
Parameters
event
(string
): Name of the event. This can be either signIn
or signOut
.callback
(() => void
): Handler to be triggered when the event
fires.
Returns
object
remove
(() => void
): Removes the event handler.
Description
Attach an event handler to important events.
Example
const subscription = selector.on("signIn", () => {
console.log("User signed in!");
});
subscription.remove();
.off(event, callback)
Parameters
event
(string
): Name of the event. This can be either signIn
or signOut
.callback
(() => void
): Original handler passed to .on(event, callback)
.
Returns
Description
Removes the event handler attached to the given event
.
Example
const handleSignIn = () => {
console.log("User signed in!");
}
selector.on("signIn", handleSignIn);
selector.off("signIn", handleSignIn);
.getContractId()
Parameters
Returns
Description
Retrieves account ID of the configured Smart Contract.
Example
const contractId = selector.getContractId();
console.log(contractId);
.signAndSendTransaction(params)
Parameters
params
(object
)
signerId
(string?
): Account ID used to sign the transaction. Defaults to the first account.actions
(Array<Action>
)
type
(string
): Action type. See below for available values.params
(object?
): Parameters for the Action (if applicable).
Returns
Promise<object>
: More details on this can be found here.
Description
Signs one or more actions before sending to the network. The user must be signed in to call this method as there's at least charges for gas spent.
Note: Sender Wallet only supports "FunctionCall"
action types right now. If you wish to use other NEAR Actions in your dApp, it's recommended to remove this wallet in your configuration.
Below are the 8 supported NEAR Actions:
export interface CreateAccountAction {
type: "CreateAccount";
}
export interface DeployContractAction {
type: "DeployContract";
params: {
code: Uint8Array;
};
}
export interface FunctionCallAction {
type: "FunctionCall";
params: {
methodName: string;
args: object;
gas: string;
deposit: string;
};
}
export interface TransferAction {
type: "Transfer";
params: {
deposit: string;
};
}
export interface StakeAction {
type: "Stake";
params: {
stake: string;
publicKey: string;
};
}
export interface AddKeyAction {
type: "AddKey";
params: {
publicKey: string;
accessKey: {
nonce?: number;
permission:
| "FullAccess"
| {
receiverId: string;
allowance?: string;
methodNames?: Array<string>;
};
};
};
}
export interface DeleteKeyAction {
type: "DeleteKey";
params: {
publicKey: string;
};
}
export interface DeleteAccountAction {
type: "DeleteAccount";
params: {
beneficiaryId: string;
};
}
Example
await selector.signAndSendTransaction({
actions: [{
type: "FunctionCall",
params: {
methodName: "addMessage",
args: { text: "Hello World!" },
gas: "30000000000000",
deposit: "10000000000000000000000",
}
}]
});
Known Issues
At the time of writing, there is an issue with Sender Wallet where the signed in state is lost when navigating back to a dApp you had previously signed in to - this includes browser refreshes.
Contributing
Contributors may find the examples
directory useful as it provides a quick and consistent way to manually test new changes and/or bug fixes. Below is a common workflow you can use:
- Execute
yarn link
in the root directory. - Navigate to the
examples/{framework}
directory. - Execute
yarn link near-wallet-selector
to create a symlink locally. - Execute
yarn start
Editor Setup
This project uses ESLint (with Prettier) to enforce a consistent coding style. It's important that you configure your editor correctly to avoid issues when you're ready to open a Pull Request.
Although this project uses Prettier, it's simply an "internal" dependency to our ESLint configuration. This is because we want Prettier to handle code styling while avoiding conflicts with ESLint which specifically focuses on potentially problematic code. As a result, it's important that you switch off Prettier in your editor and ensure only ESLint is enabled.
License
This repository is distributed under the terms of both the MIT license and the Apache License (Version 2.0). See LICENSE-MIT and LICENSE-APACHE for details.