A fork of find3r with faster loading, ENS v2 names and more. What changed · The original is find3r.app.
find3r.Apps, art, and a little exploring.Back to your folders ↗
HOW FIND3R WORKS

A file browser for
the things people own onchain.

Enter a wallet address or a name like snowfro.eth. Find3r shows its apps, artworks, and files in folders you can explore. You can look inside anyone’s collection. No sign-in or wallet connection needed.

Looking at a wallet doesn’t give Find3r access to it. You don’t need to approve a transaction, share a password, or prove that the wallet is yours.

Start with an address

  1. Paste an address, an ENS name, a collection’s contract address, or a Find3r app link into Go to.
  2. Leave Network on All chains, or choose Ethereum, Base, Arbitrum, or Base Sepolia. This checks the address you entered, not other people’s wallets.
  3. Choose Apps, Art Blocks, or ABX, or Artworks to see that part of the collection.
  4. Open something that catches your eye. Choose ☆ Save wallet to keep the wallet handy, or use Save a wallet in the sidebar to add one by name or address.

Simple mode is the default: click an app and its start page opens. Explorer mode lets you look at the files inside and choose older versions. You can switch between a list and icons, sort items, and use the back button or folder trail to move around.

A collection or app belongs to one network, so its network is shown while you’re inside it. Go back to the address or Home to choose a different network. Shared links keep the selected network. Apps from different networks have their own labels.

Your saved wallets appear under Bookmarks → Wallets and on Home. You can give them a name, keep anyone’s wallet, and return with one click. Wallets added from the sidebar start with All chains. Collection bookmarks still use Add address. Remove bookmarks in Settings → Wallets & address bookmarks.

Bookmarks and connection settings stay in this browser on this device, including after a reload. If you open Find3r inside another app or on a shared BAMFS website, bookmarks only last for that visit. Clearing browser storage removes them.

What’s in the folders?

A BAMFS app is also an NFT. Under Apps, you open the app itself through Find3r’s connection. In its ABX view, you see the token’s image, details, and live-view link. The same item can have both views. BAMFS groups apps into collections called orgs. Inside a wallet’s Apps folder, open an org folder to see the apps held there. You can paste an org’s address to see all of its apps, too. Older shared BAMFS collections are hidden from wallet browsing; their original links still open.

NFT support follows shared formats, so a collection does not need to be added by name before you can open it. Unique items (ERC-721) and editions (ERC-1155) use the same reader across many creators and platforms. The named collections are a small fallback list for discovering holdings without an artwork index; they are not a list of everything Find3r can open. App orgs are discovered from onchain ownership. Find3r also checks collections found in a wallet’s Artworks list for ABX support onchain. Recognized collections appear in both ABX and Artworks, even without ABX directory registration. The directory provides another way to discover holdings. A collection contract or specific artwork can also be read directly, even when the ABX directory hasn’t listed it. Direct connections currently cover Ethereum, Base, Arbitrum, and Base Sepolia.

Wallets show Apps, Art Blocks, ABX, and Artworks folders when supported holdings are found. Empty categories are hidden after a successful check; a failed check stays available to retry. Use the address in the breadcrumb trail above the files to go back and choose another folder. Large collections use small pages. Search Art Blocks and ABX for a project or artist, or search for a token number inside a collection. Next and Previous move through the results. Search app folders by name. Inside an org, app search and sorting apply to the page you’re viewing.

Collections, artwork links, and sharing

Paste a collection’s contract address to go straight to its contents. Art Blocks collections open into projects; BAMFS collections open into apps; ABX and other supported NFT collections show artworks. They don’t show wallet category folders. View holdings separately shows what the contract address owns.

You can paste an OpenSea artwork link too, along with supported Foundation, SuperRare, KnownOrigin, CryptoPunks, and Async Classic links. Older links may need the original marketplace to identify a contract; if it is gone, paste the contract address and open the token number. Find3r uses the network, contract, and token number from the link to open the artwork here. Copy link shares a folder or selected item; Copy artwork link shares the piece you’re viewing. These links don’t require your saved addresses or settings.

Async Classic: these artworks are made of layers that their owners can change. You can see the saved preview, inspect a layer’s current settings, or choose View current image to assemble a supported artwork here. Find3r reads the settings from Ethereum and loads the image layers from IPFS or the artist’s storage, without using Async’s website. This is a snapshot when you open it; close and reopen to refresh. Some works use sound, daily randomness, outside prices, or special colour effects that this lightweight viewer cannot recreate yet. It tells you when a current image cannot be assembled, and keeps the saved preview available. Find3r cannot change layers. Other Async collections can still open through standard NFT metadata when available.

Autoglyphs: Find3r reads the original drawing instructions from Ethereum and draws the artwork here. You can also save the original text. No image website is needed for this view.

More collections: Meebits, Checks, Opepen, Credits, Statements, PXL DEX, PXL POD, The Vessel Crafts and Sequences, and other compatible collections use the same artwork folders. Meebits currently offers a picture and details, rather than a built-in 3D viewer. Some large onchain artworks need more computing time than the shared connection allows. If Find3r uses saved details instead, the page says so; a saved preview may be older.

The Vessel: choose Explore Vessel contents on a Craft or Sequence. You can view a Craft’s contents as pixels, save its original bytes, read text when available, and browse a Vault’s saved entries. Viewing an entry here does not change the Craft. Relics are special registered contents; some are registered before their Craft has been claimed, and Find3r labels those as unclaimed. The Machines view shows registered generators and lets you preview their output for a Craft number. A Machine preview does not attach it to the Craft. Refresh to read the latest output.

You can paste a published Relics, Machine, or renderer contract address in Find3r to explore it directly. Craft, Vault-entry, Machine-preview and Sequence views have ordinary shareable URLs; they work without your saved folders. Contents are read through your current Ethereum connection, without using The Vessel website or its indexer. The artwork metadata view can still use a labelled saved preview. Pixel previews interpret one byte as one pixel; the byte download preserves exactly what the contract returned. HTML bytes can be opened explicitly in the same isolated viewer used for live artworks. Find3r does not mint, write, delegate, or change a Machine or entry selection.

Live artwork included in the NFT: some collections, such as Checks and PXL DEX/POD, include a complete animated webpage in their artwork details. Open live view opens that page inside Find3r in its own isolated frame. It can use the same read-only connection as other Find3r apps, without seeing your private connection settings. This does not connect a wallet or let the artwork sign or send transactions. Works that need separate websites or files still depend on those sources.

While an app is open, Copy app link shares its onchain address, selected version, page, and URL options. Anyone can type or share that URL. It reads the app directly from the chain, including in a fresh browser. The address bar shows the same kind of portable URL.

An app’s address follows web3://ORG:CHAIN/TOKEN/latest/, or /v/NUMBER/ for a fixed version. A page such as index.html names a file inside the onchain package. The normal web URL is https://find3r.app/app/CHAIN/ORG/TOKEN/. Add options at the end, just like any website: ?time=1. For a fixed version, use /app/CHAIN/ORG/TOKEN/v/NUMBER/. They configure the app; they don’t change where its files come from.

For large wallets, the optional artwork index finds collections and lets you search their names before opening one. It can also list items from collections that don’t provide their own list. Recently collected is available where the index supports it; other order comes from the collection or index. The index is a browsing helper, and may lag behind transfers. Opening a piece reads its contract directly. Without an index, familiar collections are checked through the blockchain. When an original metadata call or storage service is unavailable, the optional index may have a saved copy of the details. Find3r labels these saved details clearly. Ownership checks still happen first; saved details may be older, and do not prove the original files remain available. Some collections don’t provide a complete list of their artworks. Find3r explains that and offers Open an artwork by number. Enter its token number, such as 0. An unrecognized contract is shown as a contract rather than being mistaken for a wallet. If the address exists on several networks, choose which one to browse.

Artwork details can come from the blockchain, IPFS, Arweave, or a website. The image and live view may use a different source. More about this piece shows those sources when Find3r reads the token directly. Storage locations aren’t separate collection types. Artwork can also include its SVG image directly in its details, and collections can provide traits in several common formats. Editions show copy counts when available. A website link is kept separate from a live artwork link; 3D attachments offer an Open 3D file action for a compatible viewer. CryptoPunks images and traits come directly from their onchain data contract. Audio and video files have play controls; documents have a preview or an Open file link. Find3r tries another IPFS or Arweave gateway when the first one is busy. In Settings → Images & files you can choose your own.

Choose how apps load

An app opens in a new tab. Find3r checks that its files match the published version before using them. In Settings → Opening apps, choose:

Both choices use the same published files and the same checks. Recent copies can be reused on your device for up to one day, so reopening is often faster. Settings → Clear local copies removes Find3r’s saved copies. An app’s own outside services still need a working connection.

Choose Open full screen to open a fresh view of the same published app in another tab, without the Find3r header or border. It fills the space below your browser’s own toolbar. Your original tab stays open; close the new tab when you’re done. Changes you made inside the original app aren’t copied into the new view.

Apps open in a protected view so they can’t read Find3r’s saved connection keys or folders. This first version doesn’t pass your wallet into that view or keep an app’s own saved state. Apps that need those features, or other browser features this viewer doesn’t support, may work better when you download and open a separate copy.

What is an RPC, and do I need one?

An RPC is a connection that lets an app read the blockchain. The name sounds technical; using Find3r doesn’t have to be.

Your own URL takes priority over the default. The connection can be changed without changing the app’s onchain address or files. On a shared BAMFS website, private connection fields are disabled; use Find3r on its own domain or your computer to save them.

Some onchain artworks need extra work to open. Their contracts build the picture, live page, and details when you request them. Find3r tries a larger computing budget for standard NFT details if the normal read fails. These reads need no blockchain transaction or wallet gas payment. The connection provider still has to do the work and may limit or charge for it.

If a provider reports a computing limit, Find3r says so. If the cause is unclear, it says the renderer may have failed or reached a connection limit. Choose Choose another connection on the artwork to enter your own network RPC and retry, or try the offered free public connection. A different provider may allow more, but it is not a guarantee. A saved preview can still be shown while the original read is unavailable; the explanation stays visible.

With Settings → Let apps use my browsing connection switched on, compatible apps can read blockchain data through your Find3r connection. Your private connection URL stays outside the app. This includes a copy of Find3r opened inside Find3r; its folders and custom settings last for that visit. Apps with their own built-in connection still use that connection. You can turn sharing off at any time and reopen an app for the change to take effect. This covers reads, not gas fees, signatures, or transactions. A private RPC saved in your wallet cannot be read by Find3r; you can paste that URL into Find3r Settings instead.

Which version opens?

Opening an app normally selects its latest published version. BAMFS records that choice on the blockchain. If there’s an index.html or index.htm start page, Find3r opens it for you. Otherwise, you can browse the files.

A link to a specific version keeps opening that version. Once an app opens, Find3r keeps its file reads on that same version so an update won’t change files halfway through your visit. Open it again to pick up the latest publication. Explorer mode lets you choose an older version.

What lives onchain?

Find3r’s website files are published on BAMFS. The find3r.app address gives ordinary browsers a convenient way to reach them. A small Cloudflare Worker reads those files from the blockchain and keeps copies for faster delivery.

The BAMFS apps you browse work the same way: their published files can be read without the original creator’s website or BAMFS’s website. The domain, gateway, and RPC provider are replaceable ways to reach those files.

Some parts still use outside services. Art Blocks, ABX, and an optional NFT index help Find3r find owned artworks. The NFT index can be configured in Settings → Find more artworks; an Alchemy RPC URL can supply its matching index automatically. Art Blocks previews and some ABX previews use their hosted services. Other artwork details are read from the collection contract and any storage address it provides. Individual apps or artworks may use outside images, libraries, or APIs too. Storing the website files onchain doesn’t make every service it uses permanent.

A new ABX contract is not automatically in every directory. A resolver lists the projects registered with that service. Deployment and directory registration are separate steps; waiting alone may not add it. A wallet’s artwork index can find an unregistered collection; Find3r checks its ABX support onchain and shows it in both categories. Direct contract or artwork links can also read onchain metadata without that directory. The ABX hosted-services guide explains registration and indexing status.

The promise is that someone with access to the chain and compatible software can recover the published files. It depends on the chain remaining available, its data being readable, and the app’s required outside dependencies being available or included with it.

Keep a copy, or ask your agent to help

Download file keeps the selected original file. Download app keeps the app’s complete published folder as a ZIP. These downloads preserve the original files.

Open independently gives you a prompt for your coding agent. It appears while browsing a BAMFS app or its files, and includes where the app lives and which version to read, so the agent can retrieve it using a connection you choose and help open it on your computer.

For supported BAMFS apps, the included recovery tool checks and reconstructs the complete folder directly from the chain. Artwork pages offer images, details, and live views instead. The technical agent guide separately explains how to investigate Art Blocks and ABX content and its outside dependencies.

Use Find3r without find3r.app

You can recover Find3r’s published files and run your own copy on your computer or a static website host. Public connections are included, and you can replace them in Settings. You don’t need a Find3r account or application server.

The package includes a tiny local server: node agent/serve.mjs .. It opens Find3r at http://127.0.0.1:8787 and supports the same app URLs. Your agent can handle that step. Keep unfamiliar downloaded apps separate from places where you store private connection keys.

Give an onchain app a normal web address

Put this app online appears when you select or browse a BAMFS app. It fills in the selected app’s link and prepares a small Cloudflare Worker for a compatible BAMFS app. Think of it as a front door: visitors use a normal website address, and the Worker gets the app’s files from the chain.

  1. Check the filled-in app link and choose whether to follow updates or keep a specific version. A selected app starts with “follow updates”; when you’re browsing a particular version, that version is selected instead.
  2. Copy the prepared code into a Hello World Worker in your own Cloudflare account and deploy it.
  3. Add the connection URL under Secrets with the name RPC_URL. Then use the Worker’s web address or connect your own domain.

Your website files stay on BAMFS. You upload the small gateway code to Cloudflare. Find3r prepares it; it doesn’t deploy into your account automatically.

Follow updates keeps looking for the latest version of the same BAMFS app, so you can publish a new revision without editing the pointer. A move to a different token or contract needs a new pointer. Choose a specific version when you want a gateway that always serves the same copy.

For developers and coding agents

These resources describe the exact reads, file checks, supported deployments, and recovery limitations.

Find3r’s current publication is on Base Sepolia (chain 84532), BAMFS org 0x1e55775e148ae8839677134f46d6937442817e58, token 1. Save a fixed-version recovery descriptor for the exact copy you want to preserve.

export FIND3R_RPC='https://YOUR_RPC'
node recover.mjs --descriptor find3r-recovery.json restored-site
python3 -m http.server 8787 --directory restored-site --bind 127.0.0.1

The viewer uses an opaque sandbox, adapted local assets and modules, and a file-only bridge. Wallet injection, persistent rendered-app storage, XHR, workers, computed imports, import.meta resource URLs, and some navigation patterns are not supported. Serve original files separately for broader browser compatibility.

Find3r checks recovered files against their published fingerprints. Keep the original app address and a verified copy with your recovery records. Older BAMFS collections and newer orgs use different readers; the recovery tool keeps that distinction.

BAMFS deployments · BAMFS read interfaces · Ethereum public connection · Base public connection