Skip to content

script/Deploy.sol emits meta to the v1 MetaBoard; the org deployed a successor board on 2026-08-21 #264

Description

@thedavidmeister

Found while flipping rain.metadata.deploy's subgraph record to the new board (rain.metadata.deploy#4).

script/Deploy.sol:12 hardcodes the v1 board:

address constant METABOARD_ADDRESS = 0xfb8437AeFBB8031064E274527C5fc08e30Ac6928;

and run() emits the subparser's described-by meta to it at deploy time.

On 2026-08-21 a new MetaBoard was deployed to all seven supported networks at 0x8fD50fF9Db9835ba1B61394752A26F53D721D2a1 (rain.metadata.deploy sol-v0.1.0, frozen in src/generated/0_1_0/), and the metaboard subgraph record now indexes the new board. The v1 board keeps running, but nothing new indexes it once the subgraph moves.

Consequence: the next ERC4626Words deploy emits its meta to a board the org's subgraph no longer watches, so the meta is on-chain but invisible to anything reading the subgraph.

The current shape for this coupling is a pinned dependency on the deploy repo's released record (rain-metadata-deploy 0.1.0 on Soldeer publishes LibMetaBoardDeploy.METABOARD_DEPLOYED_ADDRESS) rather than a hand-written constant — that way the address moves when the record moves.

This repo is one of two remaining v1 references in the org; the other is a matchstick fixture in rain.metadata (subgraph/tests/address.ts:6), which is test scaffolding rather than a live coupling.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions