ERC-5192 Soulbound Lock Tool

WHAT IT DOES

This tool enables developers and token holders to lock ERC-5192 tokens, making them soulbound and permanently non-transferable. Soulbound tokens are non-transferable digital assets that are permanently bound to a specific wallet address, representing identity, achievements, credentials, or other personal attributes that should not be transferred. It connects to your wallet and reads the token contract address, token ID, lock status, unlock conditions, lock history, and timestamps. The tool signs and submits transactions to lock soulbound tokens, update lock status, record lock metadata, and emit lock events.

HOW TO USE

1. Connect your wallet using the wallet bridge (supports MetaMask, WalletConnect, and other EVM-compatible wallets).

2. Select the target network that matches your token contract deployment.

3. Enter the token contract address and the token ID, then click "load contract" to initialize the connection.

4. Click "fetch lock status" to retrieve the current lock status, unlock conditions, and lock history.

5. Review the lock status — if the token is already locked, it cannot be locked again and cannot be transferred.

6. Optionally enter unlock conditions as JSON (e.g., time-based or signature-based conditions) if the contract supports them.

7. Click "validate lock" to verify that the token is not already locked and can be locked.

8. Click "check lock history" to view the lock history of the token (if any).

9. Review the token details, lock status, and unlock conditions before executing.

10. Click "lock token (soulbind)" to sign and submit the transaction that permanently locks the token to your address.

TECHNICAL MECHANISM

The tool uses ethers.js v5.7.2 to interact with any EVM-compatible ERC-5192 token contract that implements a standard interface (locked(uint256) view returns (bool), unlockConditions(uint256) view returns (string), lock(uint256, string) external, getLockHistory(uint256) view). The lock function validates that the caller owns the token, the token is not already locked, and (if implemented) the unlock conditions are valid. Once locked, the token's transfer function is disabled — any attempt to transfer the token will revert. The contract typically stores the lock status and conditions in the token's metadata, and emits a Lock event for audit purposes. The getLockHistory view returns timestamps, locker addresses, and action types (lock/unlock) for the token. Transaction handling follows EIP-1559 gas price calculations using receipt.effectiveGasPrice for accurate cost reporting. Lock metadata is recorded both in the contract's history and locally for the user's reference.

WHAT IT CANNOT SEE

This tool operates purely on-chain and cannot verify off-chain identity — it does not confirm that the token holder is the person they claim to be or that the token represents genuine credentials. It cannot validate the soulbound nature — the tool cannot verify that the token should be soulbound or that the lock is appropriate. It cannot detect transfer attempts — the tool cannot identify or prevent attempts to transfer the token through other means (e.g., using a different interface). It cannot ensure permanent locking — while the contract should enforce the lock, there is no guarantee that the contract is correctly implemented or that a future upgrade might bypass the lock. The tool also cannot guarantee that tokens remain soulbound — once locked, they are bound to the current address, but the address itself may change ownership or be compromised.

PLEASE NOTE

This tool works exclusively with EVM-compatible blockchain networks (Ethereum, Polygon, Arbitrum, Optimism, Base, etc.). It requires the token contract to implement the ERC-5192 interface described above. All transactions incur gas fees paid by the connected wallet. The tool maintains no persistent storage — all state is refreshed from the blockchain on each session. Locking a token is a permanent and irreversible action — once locked, the token cannot be transferred to any other address. Only lock tokens that you intend to be permanently bound to your identity. Consider using unlock conditions if supported by the contract, but be aware that conditions may not be enforceable or may be bypassed.