What
The inverse of authoring: point the studio at a set of live contract addresses, fetch verified ABIs/sources (Etherscan/Sourcify), and reverse-engineer a DeploymentSpec + graph from a system deployed by other means. Turns the studio into an onboarding tool for existing systems, not just new ones.
Scope sketch
- reader: an "adopt" module — given
{address, network} pairs, fetch ABI + constructor args (from verified source / tx input data), detect inter-contract references (constructor args or getter values that equal another imported address) to propose graph edges.
- studio: import wizard (paste addresses or upload JSON) → editable draft graph → export spec; unresolved refs flagged for manual wiring.
- Heuristics are best-effort v1: constructor-arg address matching only; storage scanning OUT of scope.
Why
Every prospective user already has a deployed system; adoption starts from "show me mine".
What
The inverse of authoring: point the studio at a set of live contract addresses, fetch verified ABIs/sources (Etherscan/Sourcify), and reverse-engineer a
DeploymentSpec+ graph from a system deployed by other means. Turns the studio into an onboarding tool for existing systems, not just new ones.Scope sketch
{address, network}pairs, fetch ABI + constructor args (from verified source / tx input data), detect inter-contract references (constructor args or getter values that equal another imported address) to propose graph edges.Why
Every prospective user already has a deployed system; adoption starts from "show me mine".