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
As part of the upcoming asset classification system scopes will need to be able to have attributes assigned to them. In order for this to work the allowed bech32 address prefixes will need to be extended to allow scope in addition to tp and pb used for normal accounts.
Problem Definition
The asset classification program uses controlled names owned by the Provenance foundation and delegated representatives to create classifications. sample.provenance.asset could be assigned to a some specific scope or account with an appropriate value. In order for this to work on metadata scopes the validation logic of the attribute module must be extended to allow this alternate address prefix. The rest of the scope MetadataAddress is already compliant with the required AccAddress expected format.
Proposal
Update the attribute module to allow the scope prefixed addresses to be used for attribute assignment.
For Admin Use
Not duplicate issue
Appropriate labels applied
Appropriate contributors tagged
Contributor assigned/self-assigned
The text was updated successfully, but these errors were encountered:
Summary
As part of the upcoming asset classification system scopes will need to be able to have attributes assigned to them. In order for this to work the allowed bech32 address prefixes will need to be extended to allow
scope
in addition totp
andpb
used for normal accounts.Problem Definition
The asset classification program uses controlled names owned by the Provenance foundation and delegated representatives to create classifications.
sample.provenance.asset
could be assigned to a some specific scope or account with an appropriate value. In order for this to work on metadata scopes the validation logic of the attribute module must be extended to allow this alternate address prefix. The rest of the scope MetadataAddress is already compliant with the required AccAddress expected format.Proposal
Update the attribute module to allow the
scope
prefixed addresses to be used for attribute assignment.For Admin Use
The text was updated successfully, but these errors were encountered: