You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would suggest splitting this into addresses.roles and addresses.contracts keys, as shown below. This would then map nicely to the "roles" section of the docs. It also gives a similar structure to how inputs and outputs will be structured for the OP Stack Manager deployment scripts
I'm open to names other than "protocol" for the other section. I didn't want to use "contracts" as some roles are contracts, but protocol feels like it might be too broad of a term.
Right now I find the addresses section hard to read because it's a bit cluttered and there's nothing separating semantically different addresses:
superchain-registry/superchain/configs/mainnet/op.toml
Lines 31 to 53 in c92ef42
I would suggest splitting this into
addresses.roles
andaddresses.contracts
keys, as shown below. This would then map nicely to the "roles" section of the docs. It also gives a similar structure to how inputs and outputs will be structured for the OP Stack Manager deployment scriptsI'm open to names other than "protocol" for the other section. I didn't want to use "contracts" as some roles are contracts, but protocol feels like it might be too broad of a term.
The text was updated successfully, but these errors were encountered: