FAQ

No. Lantstool works exclusively in your browser. All data, including private keys and transactions, is stored locally using an SQLite (OPFS) database directly on your device. We do not transfer any information to external servers.

Since Lantstool stores all information locally, completely clearing browser data for the site will lead to the deletion of the local database and the loss of all your spaces, networks, and the data belonging to them. To avoid this, regularly create a backup.

No. Deleting a space is an irreversible action. All associated networks, keys, and accounts are deleted along with it. Without creating a prior backup, it is impossible to recover this data.

1. Spaces: Independent workspaces (projects). Data from one space is completely invisible in another.
2. Networks: Networks within one space (mainnet, testnet) are isolated from each other. Testnet keys and transactions will never be displayed in mainnet.

1. Check if the selected Signer Id matches the key owner.
2. Ensure the key is imported specifically into the current network (mainnet, testnet).
3. Check the key status in the Accounts section: it must be marked as imported ✅ (green checkmark).

Yes. In the Accounts section, open the selected account, go to Associated keys, and find the required key. For each Function Call key, the following are displayed: Contract ID, funds limit (Allowance), and the Allowed Methods list.

Lantstool automatically checks for the presence of an ABI in the contract and, if available, generates a ready-made argument structure in JSON5 format, saving you from the need to investigate the code manually. Using JSON5 allows displaying data type hints and field descriptions directly in comments to arguments, and thanks to the built-in editor, you don’t have to worry about missing quotes or extra commas, as the application automatically highlights syntax errors.

This is a security measure. The public key serves as an identifier to find the corresponding private key in the local Keys storage. Hiding the private key in the interface protects you from accidental compromise during screen demonstrations.

No. Lantstool does this automatically. Although the protocol requires data transfer in base64 format, in our application, you can enter plain text or JSON — the system will encode them directly before sending the request.

This is part of the synchronization system that automatically selects the recipient (Receiver Id) according to your set of actions. Lantstool uses a clear priority hierarchy so that your transaction complies with NEAR protocol rules and you cannot accidentally send it to an incorrect address.

Lantstool automates this process by sending an RPC request to retrieve your access data (Access Key) based on the selected Signer Id and Signer Key. The received nonce value is automatically incremented by 1, and the block hash is taken directly from the current information about the state of this key in the network. This ensures that each transaction will be valid and up-to-date without the need for manual entry of technical parameters.

When a contract with a massive amount of data (Large State) or hundreds of keys is deployed on an account. Regular deletion using the Delete Account action will result in an Exceeded the prepaid gas error. Account Cleaner allows clearing the state in stages.