ERC-3643 Permissioned Token Transfer Tool

WHAT IT DOES

This tool verifies permissioned transfers for ERC-3643 compliant tokens, helping users determine if a proposed transfer satisfies all on-chain identity and permission requirements before execution. Given an ERC-3643 token contract address, sender and receiver addresses, an amount, and an optional agent address, it reads the token's symbol, decimals, balances, and total supply. It then checks the identity registry to verify whether the sender and receiver have valid on-chain identities, queries agent status if an agent address is provided, and calls the canTransfer function to check if the transfer is allowed. The tool then displays a clear permission status—Granted or Denied—along with the permission code and message explaining why a transfer might be blocked. It also displays identity registry details, verification status for both parties, and agent permission status. All data is pulled directly from the blockchain in real time, providing a transparent, auditable permission check before any ERC-3643 token transfer is executed.

HOW TO USE

Connect your wallet using the Connect button in the header. Select the target network from the dropdown—Ethereum Mainnet, Polygon, Optimism, Arbitrum One, Base, or Sepolia testnet. Enter the ERC-3643 token contract address, the sender address, the receiver address, and the transfer amount. Optionally, provide an agent address to check if the agent has permission to facilitate the transfer. Click "Check permission." The tool will fetch the token details, balances, identity registry state, verification status, agent status, and call the compliance check function. Results appear in the card below with a prominent permission status badge, a detailed permission message if the transfer is blocked, identity registry details, verification status for both parties, agent information, transfer details including balances and total supply, and a breakdown of permission factors with checkmarks or crosses. Use this information to verify transfer permission before initiating an ERC-3643 token transaction.

ERC-3643 PERMISSIONED TOKEN TRANSFER VERIFICATION WITH IDENTITY REGISTRY INTEGRATION

The tool provides comprehensive ERC-3643 permissioned token transfer verification through multiple on-chain reads. First, it retrieves the token's symbol and decimals via standard ERC-20 view functions. It then reads the sender's balance, receiver's balance, and total supply using balanceOf and totalSupply. Next, it calls identityRegistry() to get the address of the identity registry contract, then queries the registry for hasIdentity() to verify whether the sender and receiver have registered identities, and getIdentity() to retrieve their identity hashes. It also calls isVerified() directly on the token contract as a fallback verification check. If an agent address is provided, it calls agent() to check if that address has agent permissions. Finally, it calls canTransfer() with the transfer parameters to get the permission decision and a permission code. The permission code is mapped to a human-readable message—0 for allowed, 1 for general failure, 2 for sender not verified, 3 for receiver not verified, 4 for insufficient balance, 5 for agent permission required, and 6 for transfer restricted. All permission factors are displayed with visual indicators to help users understand exactly why a transfer is allowed or blocked.

WHAT IT CANNOT SEE

This tool cannot verify off-chain identity credentials or ensure that the on-chain identity corresponds to a real person or entity. It cannot ensure that the transfer is legally valid or that the transaction complies with applicable securities laws. It cannot detect fraudulent identities or verify the authenticity of identity registry entries. It cannot validate agent decisions or ensure that the agent has properly approved the transfer. It cannot guarantee regulatory compliance in any jurisdiction. It cannot assure that the permissioned token contract is free from vulnerabilities, bugs, or malicious code. It cannot verify that the token contract address is correct or that the agent address is valid. It cannot detect front-running or other execution risks. It cannot provide legal or financial advice or guarantee that executing the transfer is safe. All data is provided as-is for informational purposes only; any reliance on the tool's output for transfer decisions is the sole responsibility of the user.

PLEASE NOTE

This tool supports EVM-compatible chains only: Ethereum Mainnet (1), Polygon (137), Optimism (10), Arbitrum One (42161), Base (8453), and Sepolia testnet (11155111). Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported. The tool requires a Web3 provider (MetaMask or WalletConnect) and access to an RPC endpoint for the selected chain. It does not store any wallet data, token addresses, or transfer records. All queries are performed directly against the blockchain in real time. The tool only provides read-only information and does not execute any transactions. Permission checks are based on the token contract's implementation and do not guarantee legal or regulatory compliance. Always verify critical data independently through a block explorer and consult with legal counsel before executing any permissioned token transfers.