Skip to content

Pallet-level CDM contract registry address storage & extrinsic #12237

@charlesHetterich

Description

@charlesHetterich

Is there an existing issue?

  • I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

  • This is not a support question.

Motivation

Pretty soon, CDM is going to be a more relied on piece of infra. tl;dr of CDM is that it is a contract registry which maps human readable @org/foo style packages to the contract's Address, ABI, & peripheral metadata like README's. This means contracts can update to new versions with new ABI, and consumers can instantly interact with the latest contract by running cdm install, without changing any of their code.

Occasionally when the CDM contract is updated, the address changes, and consumers have to update the root CDM registry address. Since the point of CDM is to avoid dealing with contract addresses, it would be ideal to avoid this issue with some governance controlled storage that sets the cdm_registry_address. Then consumers can point always point here for the cdm registry address and not have to worry about the address changing.

Request

Add a storage value to PalletRevive (or some other appropriate pallet) with cdm_registry_address constant.

I'm not sure if other peripheral work also has to be done in order to make testing functionally work on testnets? I haven't needed to manage governance controlled variables yet, so any further guidance would be super helpful 🙏

Solution

No response

Are you willing to help with this request?

Yes!

Metadata

Metadata

Assignees

No one assigned

    Labels

    I5-enhancementAn additional feature request.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions