Closed brenzi closed 3 years ago
I suggest including all fields into a new CommunityMetadata
struct, (maybe except for nominal_income
and demurrage_per_block
, as these are fetched regularly by the pallets. Doing so, we would save some decoding operations if we store them separately, which might be significant depending on the size of the icons
, theme
?).
Along this approach I would only offer the following sudo calls:
update_community_metadata
→ supply an updated struct. Saves some boilerplate code in the pallets compared to offering a sudo call to change each field, and is of almost the same effort on the client side.update_demmurage
update_nominal
Estimate concerns only tasks 1.-3., without integration in explorer/app
This was closed with #31
Currently, our chain spec only allows to set bootstrappers, but name is ignored:
Moving towards mainnet, we want to allow branding. The app shall no longer show the human-unfriendly
CommunityIdentifier
and we want to allow customizationname
: a long name, like "Züri Leu"symbol
abbreviation, like "LEU"icons
a multi-resolution resource for the community icontheme
an optional color scheme or other customizable styles to shape app appearanceurl
a optional link to a community sitedemurrage_per_block
: to override the defaultnominal_income
: the amount of UBI to be paid out for every attended ceremony. to override the defaultFor icons, we could use the favicon format, like manifest.json
TODO:
nominal_income
inpallet-encointer-ceremonies
anddemurrage_per_block
inpallet-encointer-balances
see
bazaar
for IPFS integration