Before the chain reads, carry over three small fixes and one change of direction from job 2's delivery, all defined by mockup/index.html and SPEC.md. (1) The brand mark: replace the ʃ character in the top bar with the drawn pixel fishing hook from the mockup, because VT323 has no glyph for ʃ and the character falls back to a different system font on every machine (SPEC 3.0 and 14.11).

First refresh the repo's SPEC.md and mockup/index.html from https://raw.githubusercontent.com/the-hook-store/hooks-store-spec/main/SPEC.md and https://raw.githubusercontent.com/the-hook-store/hooks-store-spec/main/mockup/index.html (the copies in the repo are spec 1.9; the current spec is 1.12).

The mark is this inline SVG, placed where the ʃ span was, with the same 10 px gap and the wordmark unchanged: Keep every font self-hosted.

(2) The empty pond panel's line must read exactly: Hooks launched through this store appear here. Be the first to cast. (3) When the featured strip holds only the open-slot card it must not scroll and must show that card once; the seamless marquee runs only when there are placements.

(4) No test network, by the owner's decision (SPEC 6.1, 14.12 and the 1.13 changes): remove Sepolia everywhere. public/site-config.json enables deploy chains 4663 and 1 and lists only those two chains. The Builder's Deploy on select offers Robinhood Chain and Ethereum behind an empty Choose a chain option, with no default; Continue stays disabled until a chain is chosen, like the pool share.

The top bar's chain pill shows the chosen chain's name and reads ETHEREUM · ROBINHOOD before a choice. The catalog's chain filter has two boxes. The Connect button offers a switch only when the wallet is on neither chain, and switches to Ethereum.

The Learn question Why Sepolia first becomes Which chains, with the answer from the mockup. The tested marks read proven in a live launch and not yet proven in a live launch. CHAIN_NAMES and the PoolManager map in src/lib/compose.ts drop Sepolia, the compose-A, compose-B and compose-C fixtures are regenerated with Robinhood Chain, the payment notice on the Launch page reads as the mockup's, and the README and the tests follow.

Everything else from job 2 stays as delivered. The Hooks Store, phase 1 job 3 of 6: chain reads, search by address, the Hook page with its Manage and Anyone-can panels, and My hooks. Implement SPEC.md sections 3.1 (address search and on-chain resolution), 3.4, 3.5, 4.11, 7.2 and 7.3.

Copy the Intake ABI from https://github.com/identity-md-launches/launch-1811-build-technical-foundation-hooks/blob/46e17ea70534e8a7ac2c4ff78501a3c183d32da8/docs/checks/consolidated/sources/intake-abi.json into src/abi/intake.json.

With viem public clients over https://ethereum-rpc.publicnode.com and https://rpc.mainnet.chain.robinhood.com, read Requested logs from the Intake 0xa43e6f75ee006411f79ac1c84120606c2330de82 filtered to the launch.open@launch-1 action id in 10,000-block ranges walking backwards with an in-memory and localStorage cache; decode the body JSON; keep only univ4_hook and evm_contracts bodies whose objective ends with the fixed last sentence from SPEC 5.1, which marks a launch made through this site, and ignore every other launch (SPEC 14.9); read Completed logs for those ids; status 0 with an ipfs uri fetches https://ipfs.imd.fun/ipfs//result.json for the launch addresses; status 1 or 2 is Failed with the bytes32 reason decoded as ASCII.

For every payer address, try an ENS reverse lookup on Ethereum mainnet (cached in localStorage for a day) and keep the name for the featured strip and the hook page. Every card is a launch made through this site, so no Built here mark is needed; derive block labels by matching numbered rules against the catalog sentence templates, falling back to Custom.

Search: a 40-hex query matches hook, token, distributor or pool currencies of known launches; a 64-hex query matches request ids and transaction hashes; an unmatched address is resolved on the two chains as in 3.1.

Hook page at #hook// per 3.4 with the Owner controls panel (rows from the owner functions of the hook's matched blocks, enabled only when the connected wallet equals owner(), OPEN FORM for functions with arguments, one field per argument, address validation) and the Traders, anyone, and readings panel (public and user functions as buttons, views read on load and every 20 seconds); build the minimal ABI from the 4.11 signatures.

My hooks per 3.5 with a MANAGE link for live hooks (connected wallet from job 4 may be absent: accept the address from a query param for now).

Pond trigger: poll both chains every 20 seconds for new Requested logs with the launch action whose objective ends with that fixed sentence, and call the cast function with the name parsed from the first line of the objective, else A new hook was requested on ; other launches never move the pond or the ticker. When the chain read returns no launches, the catalog keeps the empty pond panel from job 2.

Tests: decoding fixtures captured from at least two real Requested and two Completed logs on each chain saved under tests/fixtures, one Live case with a real result.json fixture, one Failed case, address resolution against a known hook and a known token on a fork, a Manage panel test on a fork with a mock hook exposing pause() and paused(); Playwright for the Hook page at three widths. Deliver source, dist/ and test results.

When a matched block has a risk field (SPEC 4.13), show the same small warning sign with its tooltip next to the block label on the hook page.