Product Spike: Upgradeable Contracts

[fainashalts]

Given the developer pain points here around upgradeable contracts in a multichain environment, we need to determine the product requirements for supporting developers in overcoming these pain points.

Definition of Done: A PRD is completed and shared with the team covering suggested solutions.

[fainashalts]

Hi @tremarkley @jakim929 just checking in on this one -- will you need some time in Q1 to work on this, and is a PRD still the best deliverable to aim for?

[tremarkley]

@fainashalts I think the deliverable depends on how this fits into our roadmap for H1. We had a productive meeting with @pharger to discuss the painpoints and added them to the doc listed in the description. Not sure we need a formal PRD or more work on this unless we want to prioritize this in Q1. Let me know what you think.

[fainashalts]

Cool I reached out to @pharger to see what he thinks. I think we have enough on our plate in Q1 but also want to assess whether this is more urgent, whether enough people need assistance with this that it should be prioritized.

[pharger]

Generally agree this will be an important point but given the focus on new L2 native deployments for interop compatibility this should probably fall right below it. That said if there are specific areas worth drilling in on with upgrades I'm all ears

[pharger]

Although - as we discussed updates (e.g., blocklist on a token on many chains) would be something that would be pretty important

[fainashalts]

@pharger by updates do you mean "I deployed a token that has functions that can be called which check a blocklist, and I want to set/update the blocklist on every chain at once"? That could fall under contract management but I don't think we have any direct product planned for this flow?