# Find3r

> A lightweight, static browser for apps, files, Art Blocks artworks and ABX items. BAMFS read-only recovery uses EVM JSON-RPC and never requires a Find3r server or BAMFS/ABX content gateway.

- [Agent recovery guide](./AGENTS.md): complete read path, commands, self-hosting, security boundaries, and supported scope.
- [Exact specification](./spec/site-v0.md): contract signatures, hash formulas, compression, and resource limits.
- [Deployment map](./deployments.json): original chain, collection, enumeration, history, directory, file, and content store addresses.
- [Standalone tool](./agent/recover.mjs): download once; Node 22.13+; no npm installation or gateway needed at recovery time. Use --help.
- [Human guide](./learn.html): browsing, recovery, self-hosting, and sandbox limitations.

Select or browse a BAMFS app or file and choose Open independently for a machine-readable find3r-recovery-v1 descriptor containing chainId, collection, tokenId, fixed version, rootCid, stores, and path. Descriptors and receipts exclude RPC URLs and credentials.

Wallets show relevant Apps, Art Blocks and ABX folders after checking supported holdings; failed checks remain retryable. Collection contracts open their own contents, with contract holdings as an explicit secondary view. Art Blocks project folders/search/counts use exact-owner queries on Ethereum, Arbitrum and Base (including indexed Engine collections); contract folders show projects without an owner filter. Recently collected sorts the full indexed token scope by last_transferred_at; newest minted uses minted_at. Pages are bounded to 40. ABX groups owned ERC-721 tokens/positive ERC-1155 holdings in registered public-resolver collections, then opens metadata images/live views/features. ABX sorts numerically because its projections lack consistent mint/transfer dates. Both discovery paths use hosted indexes and are not a complete or verified chain inventory. Generic token metadata is supported, but universal wallet discovery is not implemented.

Artwork pages offer image/live-view actions, without the BAMFS recovery or gateway buttons. Programmatic Art Blocks descriptors use find3r-artwork-v1; the standalone tool supports Ethereum artworks via the on-chain generator, with other chains requiring manual recovery. ABX descriptors use find3r-abx-v1; the bundled tool does not yet support them. Follow AGENTS.md#abx for tokenURI/uri, reader/field-renderer/generator reads, deployment discovery, external dependency checks and CLI/SDK recovery. Never copy full ABX project projections (service configuration) into a descriptor. Failed categories remain failures rather than proof of no holdings.

The token-style web3:// address is Find3r's BAMFS convention, not general ERC-4804 compatibility. The browser treats bare token and /latest/ links as the current BAMFS head and freezes the result into a fixed version. Explicit /v/N/ locators never follow latest. The low-level recovery tool expects fixed versions; its legacy abbreviated locator selects version 1.

The earlier Find3r build was published on Base at web3://0x10ddfcbcd62e784c522d0b466ed109fc65b2a855:8453/7/v/1/ with root 0xcbd02c188132d390c67a614f0b5cb61bb20daca34d37c63de036b0d31fb94a7f. This updated build needs its own publication and hash verification before claiming these exact files are on-chain.

Artwork links open artwork.html#chain=CHAIN&contract=CONTRACT&token=TOKEN. This static detail page shows the image, features and project information and offers separate live-view and full-screen image actions. Full Art Blocks metadata is fetched when a piece is opened; derived image/live links remain usable if metadata fails. ABX listing pages fetch standard metadata for up to 40 pieces; details retry it and only offer actions supplied by metadata.

- [Make a gateway](./gateway.html): copy-and-paste preparation of a bundled Cloudflare gateway, following latest or keeping a fixed BAMFS version.
- [Gateway setup guide](./gateway/README.md): owner-authorized CLI deployment, dedicated domains, RPC secrets, cache/read behavior, supported generations and costs. No automatic account deployment is included. Optional, explicitly configured read-only RPC sponsorship is described in the guide.

HTTPS find3r.app and www.find3r.app use same-origin sponsored RPC routes automatically. Other copies use replaceable public RPC defaults for Ethereum, Base, Arbitrum and Base Sepolia, with optional custom URLs in Settings. Embedded copies keep preferences for the current visit. User RPC overrides are local to a dedicated origin and never passed to opened apps. Shared gateway origins cannot save private keys.


Direct ABX recognition reads abxVersion and ERC-165 from the contract, without requiring resolver registration; this is compatibility detection, not factory authentication. Direct generic ERC-721/1155 tokens can follow JSON data URI, HTTPS, IPFS and Arweave metadata pointers on Ethereum/Base/Arbitrum/Base Sepolia. Non-enumerable collections without a supported ABX cursor offer exact token lookup. Universal wallet discovery remains unimplemented. Portable links use #collection=CHAIN:CONTRACT or artwork.html#chain=CHAIN&contract=CONTRACT&token=TOKEN&adapter=abx|nft|auto. Copy link actions do not include private settings or saved-folder IDs.

Wallet browsing defaults to All chains (network=0): Ethereum (1), Base (8453), Arbitrum One (42161), Base Sepolia (84532). The Network selector limits address detection and wallet/category discovery to the selected chain, and wallet links retain it. ENS resolution still uses Ethereum. Collection and app links pin their actual chain. BAMFS apps use only the published deployments in config/deployments.json (currently Base and Base Sepolia); All chains checks both, with at most 40 items per page split across deployments and deployment-qualified item IDs. No Arbitrum BAMFS stores are guessed. ABX wallet discovery remains limited to registered public-resolver collections. The Worker requires RPC_URL_42161 as a full Arbitrum One HTTPS RPC URL for sponsored reads. Independent copies have a replaceable public Arbitrum default.