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
Let's explore the possibility of encoding data in the community ID to identify and categorize them better. Later we can also use this information to enable/restrict parts of the system, e.g. some types of communities can be created permissionlessly paying different prices while others only by root.
typeRegion = u16;typeIndex = u16;typeMoniker = [u8;4];// a granular type that can also be represented as a number(e.g. u64) when neededenumCommunityId{GeneralCollective(Moniker),Local(Region,Option<Index>),Commercial(Industry,Index),Union(Index),Administrative(Index),OssProject(Index),}enumIndustry{ ... }
The text was updated successfully, but these errors were encountered:
An alternative to introducing categories as part of the CommunityId is to add the category as a field in the info of the community, this might create less issues to migrate and integrate with other pallets in the runtime.
Let's explore the possibility of encoding data in the community ID to identify and categorize them better. Later we can also use this information to enable/restrict parts of the system, e.g. some types of communities can be created permissionlessly paying different prices while others only by root.
The text was updated successfully, but these errors were encountered: