hook: GlueHook (monad)

[lalilulel0x]

Chain

monad

Hook Address

0xb216070c3509047ea597e2e626a29cea427a60c8

Hook Name

GlueHook

[github-actions]

Analyzing hook submission... this may take a few minutes. Follow along

[github-actions]

ERROR: Invalid address format:
ERROR: Unsupported chain: . Must be one of: arbitrum, avalanche, base, blast, bnb, celo, ethereum, ink, linea, megaeth, monad, optimism, polygon, robinhood, soneium, tempo, unichain, worldchain, xlayer, zksync, zora

[github-actions]

Analysis failed. See workflow run for details.

[lalilulel0x]

Holding this submission until source verification resolves, and correcting the record on the earlier failure.

The earlier failure was a format problem, not a hook problem. The body listed the fields as markdown bullets, while scripts/prefilter.py splits on ### headings and reads the Chain / Hook Address sections — so both parsed as empty and produced Invalid address format / Unsupported chain. The body is now the exact issue-form shape and passes prefilter.py locally. The same hook was analyzed successfully from a correctly-shaped submission in #1283 and merged as hooks/ethereum/0xb216070c3509047ea597e2e626a29cea427a60c8.json.

Why this chain still needs work: the hook is deployed here (eth_getCode returns the same runtime bytecode as the verified deployments — every chain is the same CREATE deployment at the same address), but the lookup fetch_source.py performs for this chain does not return verified source yet, so Step 2: Fetch source would fail and label this unverified. I will complete verification against the explorer this chain resolves to in chains.json and then submit through the issue form so the analysis runs cleanly, rather than asking for a re-run that is expected to fail.

[lalilulel0x]

Update: source verification for this chain is now complete, so this submission is ready to analyze.

GlueHook and its DELEGATECALL-linked GlueLiquidity library are both verified on the explorer this chain resolves to in chains.json, and running the registry's own scripts/fetch_source.py against this chain on current main now returns verified=True with the contract name resolving to GlueHook.

The body was also corrected earlier to the issue-form shape (### Chain / ### Hook Address / ### Hook Name) that scripts/prefilter.py parses. The original body listed the fields as markdown bullets, so chain and address both parsed as empty strings — that, and not anything about the hook, is what produced Invalid address format / Unsupported chain. The same hook was analyzed successfully from a correctly-shaped submission in #1283 and merged as hooks/ethereum/0xb216070c3509047ea597e2e626a29cea427a60c8.json.

Since the analysis workflow only triggers on issues: [labeled] and GitHub drops label changes made through the API by a non-collaborator, could a maintainer remove and re-add the submission label to re-run it? Happy to file a fresh submission through the form instead if that is preferred.

[github-actions]

Analyzing hook submission... this may take a few minutes. Follow along