# 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.
- [Org generation](./orgs.json): authenticated BAMFS org factory and content-v2 stores, with dynamic wallet-owned org discovery.
- [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, ABX and Artworks 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, and optional indexed discovery now groups other NFT collections.

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.

Wallet bookmarks: Save wallet while browsing a wallet, or Save a wallet in the sidebar to enter an address/ENS name and optional label. Wallets and collections are grouped separately under Bookmarks and appear on Home. Remove them in Settings. This reuses local find3r.preferences.v1 folders; kind=wallet, holdings=true explicitly opens owned items. New manually added wallets default to All chains; the current-wallet action retains its network filter. No wallet connection, server account, or transaction is involved. Embedded/shared-origin copies remain temporary.


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. Optional indexed wallet discovery groups other NFT collections; familiar collections also have a direct-RPC fallback. 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. Wallet → Apps shows current factory-verified org folders on all four networks, then owned tokens inside an org. Old shared BAMFS apps are omitted from automatic wallet browsing; direct original links still work. No store addresses are guessed. ABX wallet discovery includes owned BAMFS orgs, registered collections, and NFT-index wallet collections recognized through abxVersion plus ERC-165 NFT support. Recognized collections remain visible in Artworks too; ABX registration is not required. 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.

Portable app URL: https://find3r.app/app/CHAIN/ORG/TOKEN/?time=1 . Default follows latest; /v/N/ pins a version. App options are ordinary query parameters at the end. The address bar and Copy app link retain path/options without local session IDs. /app-full/... removes the frame. A fresh browser retrieves files directly via RPC. Recovered Find3r can serve these paths with `node agent/serve.mjs . 8787`; HTTP gateways map them to onchain viewer.html.

Expanded artwork access: wallet Artworks folders use optional Alchemy-compatible NFT indexing, with RPC fallback for CryptoPunks, BAYC, Pudgy Penguins, Foundation, SuperRare and KnownOrigin. Images have configurable IPFS/Arweave gateway fallback. Audio, video, PDF, and text previews are supported. CryptoPunks ownership, SVG, and traits read from the original market/data contracts. Supported legacy marketplace links preserve contract/token identity; unavailable or ambiguous links require an exact identity. See AGENTS.md → Broader NFT access.

Compatible apps can use window.find3r.rpc.request({chainId,method,params}), find3r.rpc.provider, or local POST /rpc/CHAIN. This bridge keeps private endpoint URLs outside the sandbox, honors parent Find3r settings, and only allows bounded reads. It never exposes wallet accounts, signs, or submits transactions. Find3r nested inside Find3r can use this bridge when enabled. Hard-coded external RPC URLs are unchanged. See AGENTS.md → App read connection.

Release: publish the dist folder and update the prepared Cloudflare Worker module to enable expanded read methods, /nfts/CHAIN, and /resolve-nft. Keep existing SITE_URL, RPC_URL_CHAIN, domains and SPONSORED_HOSTS. Matching Alchemy RPC URLs enable private NFT API derivation; optional NFT_API_URL_CHAIN overrides it. Neither publication nor deployment is automatic.

Shared NFT compatibility: the generic ERC-721/1155 reader now normalizes inline image_data SVG, trait dictionaries/properties, date traits, JSON utf8/base64 data URIs, ERC-1155 media {id} templates, metadata-relative URLs, bare CIDs and IPFS subdomains. Editions display available quantities/supply, and unnamed collections can use contractURI. External websites are separate from interactive views; 3D files open externally without a bundled renderer. Familiar collection discovery includes Loot, Nouns, ENS; this registry does not restrict direct NFT support.

Optional getNFTMetadata fallback restores cached details when original reads fail, after chain checks. Cached details are visibly labelled and never substitute for failed ownership checks. It requires updated Worker /nfts/CHAIN metadata mode and the existing NFT API connection. Nouns and ENS may use this cache rather than successful original metadata reads. See AGENTS.md → Shared metadata compatibility.

Async Classic V1/V2 has read-only controls and supported current-image reconstruction. Autoglyphs reads ownerOf/draw/symbolScheme directly from Ethereum and interprets the exact drawing grid locally; the original text can be saved. See AGENTS.md for canonical addresses and recovery calls. Familiar discovery also includes Meebits, Checks, Opepen, Credits, Statements, PXL DEX/POD, Machine in the Ghost and The Vessel Crafts/Sequences. NFT metadata can use labelled index fallback when original reads fail or exceed provider limits. Meebits is an image/details view.

The Vessel components have a dedicated RPC-only read view: artwork.html?view=vessel&chain=1&contract=CONTRACT&token=ID (token optional for component hubs). It reads Capsule payloads, main/Relic Vault saved entries, canonical Machine outputs, Relic registry pages, Machine router registration and explicit previews, and Sequence configuration/issuance/renderer links. entry=N views a saved Vault entry without changing chain state. Main Vault ABI indexes are zero-based; Relic Vault ABI indexes are one-based. Mutable runtime output is pinned per view; Refresh selects a new block. Raw bytes can be saved exactly, rendered as pixels, or viewed as inert text. Explicit HTML rendering remains sandboxed. Mainnet core contracts are documented in AGENTS.md. No Vessel website/indexer is required for contents. Do not claim an unclaimed registered Relic is minted. No writes or wallet transactions are supported.

Vessel reads start at 5M gas. Exact mainnet Vessel/Hyperportal craftToPayload calls for valid Craft IDs may retry at 20M, with no generic cap increase; see AGENTS.md for address/ABI restrictions. Publish dist and update the prepared Worker for Hyperportal's heavier reads. Existing SITE_URL and RPC variables stay unchanged. Nested connections preserve sanitized contract-revert codes for this bounded retry.

Embedded text/html animation data URIs open inside an opaque sandbox at artwork.html?chain=CHAIN&contract=CONTRACT&token=ID&adapter=nft&view=live. The normal artwork page remains the preview/details view. Self-contained blob/data workers and bounded read-only RPC sharing are supported; parent storage, credentials, wallet accounts and signing are unavailable. Update the prepared Worker for complete bounded HTML fallback, then publish dist. No new RPC variables are needed. See AGENTS.md → Autoglyphs and embedded live artworks for limits and primary sources.

Standard NFT metadata can retry once at the same block with 30M gas after a revert or confirmed computation-limit error. Only exact tokenURI(uint256), uri(uint256), and contractURI() calldata qualify; ordinary calls retain 5M and Vessel payload reads retain their separate 20M exception. A failed expanded read is explained without claiming all contract reverts are out-of-gas. Cached previews retain failure context. Artwork details let the user choose a network-specific RPC and Save & retry. Publish dist and update the prepared Worker, keeping current variables. Mio on Base was verified through this path without an index/cache. See AGENTS.md → Heavy onchain metadata and connection failures.

New ABX deployments are not automatically registered with each hosted resolver. Public not_registered is distinct from delayed/backfilling. Account/control-plane registration is at services.abx.io; public token data remains resolver.abx.io. Registration is optional for direct onchain metadata reads. See the ABX hosted-service docs and use the correct Base chain/service account when explicitly authorized to register a project.

ABX wallet classification batches up to 32 abxVersion reads in one read-only Multicall3 call, then checks ERC-721/1155 support for positive versions. It caches results for a minute; Refresh clears them. Candidate requests are shared with Artworks. Incomplete initial category probes keep ABX available for further discovery. Unregistered collection folders use normal wallet token indexing and direct metadata fallback; existing registered legacy collections retain their public projection fallback. Interface recognition is compatibility, not canonical-factory authentication, and wallet discovery is not a complete chain scan. This UI update needs only a new dist publication, with no additional Worker changes.