Lens Protocol Profile Viewer
Free to download on every platform. Comes pre-installed on BotFone, BotPad and BotFlip — with extra free apps included.
About this app
WHAT IT DOES
This tool provides a read-only interface to Lens Protocol's on-chain profile registry. Given a profile ID or an Ethereum wallet address, it queries the Lens Hub contract to retrieve profile information including the profile ID, handle, owner address, image URI, bio, follow count, and collect count. All data is pulled directly from the Lens Protocol contracts—no off-chain databases or third-party APIs are used (except for fetching optional metadata from IPFS via a public gateway). This is useful for developers, auditors, and users who want to verify on-chain Lens profile data without relying on off-chain services.
HOW TO USE
Connect your wallet (MetaMask or any Web3 wallet) to the desired EVM network (Polygon is the primary chain for Lens Protocol). Enter the Lens Hub contract address (the mainnet address is pre-filled), then enter either a profile ID or a wallet address to look up. Click "look up" or press Enter. The tool will query the contracts and display the user's profile ID, handle, owner address, image URI, bio, follow count, and collect count. If only a wallet address is provided, the tool attempts to find a profile owned by that address. The interface is intentionally minimal—it shows what the contract knows, nothing more and nothing less.
TECHNICAL MECHANISM
The tool uses the Lens Hub ABI to call tokenURI (to get the metadata URI), ownerOf (to get the profile owner), getFollowCount, and getCollectCount. It also attempts to fetch metadata from the tokenURI endpoint (supporting IPFS via a public gateway) to extract the handle, bio, and image URI. All reads are performed via the connected provider; no state is written. The tool also includes a simple fallback to find a profile ID by checking a range of token IDs for a given wallet address.
WHAT IT CANNOT SEE
This tool cannot read off-chain Lens data (posts, comments, mirrors, notifications) that is not stored on-chain. It cannot verify off-chain metadata or content. It cannot detect pending or unconfirmed transactions. It may not support all Lens contract versions or chain deployments. It cannot view non-public profiles or content without proper permissions. The data shown is exactly what is stored on-chain—nothing more.
PLEASE NOTE
This tool works on any EVM-compatible network where Lens Protocol is deployed, but is primarily designed for Polygon. It is intended for informational and monitoring purposes only. Always cross-reference with official sources and multiple explorers before making any decisions based on this data.