Onboard OP Labs Superchain data

[ccerv1]

What is it?

Playbook:

• Available on BQ
• dbt sources defined
• Staging and int models
• Updated docs
• Announcement on socials

[ryscheng]

Data is here

https://bit.ly/superchain-public-data

[ccerv1]

@ravenac95 I wanted to review the plan for this...

Sources

• Update superchain_sources.yml to point to new database
• [eventually] deprecate all sources for base, mode, etc.

Macros

• Update the relevant event data macro models (filtered_blockchain_events, contract_invocation_events_with_l1, etc)
• [eventually] deprecate the chain-specific int models for these
• Update the relevant address labeling macro models (factories, first_time_addresses, etc)
• [eventually] deprecate the chain-specific stg models for these

Events & Registries

• Swap out all the chain unions in int_events__blockchain and assign namespaces correctly
• Swap out all the chain unions in int_factories, int_deployers, etc and assign namespaces correctly
• Bump the event_source field to SUPERCHAIN where relevant

wdyt?

When this is done, we'll need to do a massive refresh of everything 😅

[ryscheng]

Couple comments from our chat today

• We still need Goldsky for non-Superchain chains (e.g. Arbitrum, etc).
• We probably want to keep the event_source specific to the underlying chain, so long as most of our metrics will be analyzing activity per-chain. Even in an interop world, I believe we'll still care about per-chain activity.
• We can always aggregate across Superchain chains in a downstream model

[ccerv1]

@ravenac95 Let's discuss this. I quickly realized that I don't have any of this data in the playground, so I we should resolve that first before I go and do any new modeling.