The files should outlive
the place you found them.

Enter an address and Find3r turns it into a folder of apps, files, Art Blocks artworks and ABX items. No sign-in or wallet connection needed. Simple mode opens apps with one click. Switch to Explorer when you want to look at their files and older versions.

This build is ready to publish to BAMFS. It does not claim to be published until its own chain, contract, token, fixed version, and verified root are recorded.

Which copy opens?

Apps open their latest published copy automatically. BAMFS keeps that information on the chain; Find3r doesn’t choose it from a private database. A link to a specific version always opens that version. A folder without a start page shows its files instead.

Recover an item without this website

1. Select a published version or file in Find3r and choose Open independently.
2. Download its recovery descriptor, the standalone recovery tool, and the guide. These files are sufficient for the supported BAMFS read path after this website goes away.
3. Choose an RPC for the descriptor’s chain. Supply credentials through an environment variable so they stay out of receipts.
4. Recover the complete original file tree. The tool verifies file, directory, chunk, and decompressed-output commitments.

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

Open http://127.0.0.1:8787/ in a separate browser profile for an unfamiliar application. Recovery itself is read-only and never signs or submits transactions. A recovered app may contain external runtime dependencies or transaction features of its own.

Run Find3r yourself

Find3r has no application server. Copy the complete published file tree, serve it on localhost or any static host, and set your own RPCs in Settings. Once Find3r itself has been published, use its recorded fixed-version descriptor with the same recovery tool.

python3 -m http.server 8787 --directory find3r-files --bind 127.0.0.1

The app’s links are relative, so it can live under a directory or BAMFS gateway prefix. Use a normal HTTP(S) or localhost origin for browser storage. No service worker is required. A static copy includes the reader, viewer, guides, and recovery tool; there are no required CDN assets or remote font files.

Opening a website

Find3r reconstructs and verifies the package through RPC, then opens a local copy in a sandboxed iframe in a new tab. Local assets are embedded, ESM imports use a generated import map, and a package-only bridge serves relative fetches and navigation. Original downloads are unchanged; the viewer makes a separate copy with resource URLs adapted to its virtual filesystem.

Opened content has an opaque origin and cannot read Find3r’s local storage, RPC credentials, or extension privileges. Wallet injection and persistent site storage are not supported in this first sandbox. Explicit window.location, import.meta resource URLs, XHR, workers, computed imports, and other browser behavior may require local hosting. External dependencies still require their external services.

A big collection, a few little folders

Start with Apps, Art Blocks, or ABX. Art Blocks opens into project folders; ABX groups pieces by collection. Search for a project or artist, or enter a token number inside a project. Next and Previous keep each page small. You can paste a collection’s contract address to see its projects or pieces, then save it as a folder.

Art Blocks can sort by recently collected or newest minted inside a project. ABX currently sorts by token number. Apps search finds names on the page you’re viewing. This isn’t a complete list of every NFT: Art Blocks uses its public ownership index, and ABX shows collections registered with its public reader. These services also supply previews and live views. BAMFS apps are read directly from the chain. An unavailable category won’t prevent you from opening another one.

ENS resolves to the Ethereum address. Direct onchain ASCII .eth records are supported; other resolvers need an explicit wallet address.

Keep an artwork too

Select an artwork and choose Open independently for instructions your agent can follow. The artwork’s chain, contract and token number identify it outside Find3r. Many Art Blocks pieces can be rebuilt from the chain using its On-Chain Generator. Some need additional libraries or assets. The agent guide explains how to tell and recover them.

Art Blocks browsing uses hosted services for finding artworks and showing previews today. BAMFS app files are read directly from the chain. Moving Find3r to BAMFS makes its own files on-chain; it doesn’t remove these Art Blocks preview dependencies.

Keep an ABX piece

ABX items have the same image, features, and live-view choices when available. Choose Open independently to give your agent its chain, collection and token number, with instructions for public ABX reads. Some works contain everything on the chain; others reference external files. The guide helps your agent check and keep original bytes. ABX recovery currently uses its CLI, SDK or direct reads rather than the bundled BAMFS recovery command.

What is—and isn’t—permanent

A public RPC is replaceable transport. A gateway is a convenient entry point. A fixed version and its root CID identify the bytes, and the recovery descriptor records the original store addresses so a contract migration does not silently replace them.

The current BAMFS deployment documentation describes prerelease contracts with administrative configuration. Find3r’s checks verify content against a selected root; its RPC is trusted for chain state. This is not a consensus-verifying light client or a guarantee about the chain’s future. Preserve descriptors and verified local copies.

BAMFS deployments · BAMFS read interfaces · ENS resolver interfaces