This feature will allow admins to mint and burn unique ID1 (Admin IDs) tied to their address, enabling streamlined management of admin privileges for community groups. Admins should only be able to add or remove IDs one at a time, with users required to sign a transaction for each action.
The functionality will be available on the Admin and Mods page until #9978
We want to allow for onchain features to be used by admins other than the namespace creator: see thread
Project Owner
@sachben91
Bucket ID
No response
User Stories / Acceptance Criteria
As an admin, I should be able to mint a new ID1 (Admin ID) by entering an address and signing the transaction.
As an admin, I should be able to burn an existing ID1 (Admin ID) associated with an address by selecting it and signing the transaction.
As an admin user, I must sign each transaction (mint or burn) to validate the action.
As an admin, I should know that I am able to mint and burn and what functionality it enables.
The system should restrict minting and burning to one address per transaction, or if feasible allow for a multicall.
Design Devlink
tk tk
Design Screenshot
tk tk
Additional Context
Admin IDs are minted and burned onchain for transparency and immutability.
Each admin action (mint or burn) must be signed via a transaction.
The feature will initially be limited to one ID addition/removal per transaction for simplicity and robustness.
This feature should be implemented within the Admin and Mods page.
We will follow up on the Mod ID Minting as these currently do not have any onchain action
Description
This feature will allow admins to mint and burn unique ID1 (Admin IDs) tied to their address, enabling streamlined management of admin privileges for community groups. Admins should only be able to add or remove IDs one at a time, with users required to sign a transaction for each action.
The functionality will be available on the Admin and Mods page until #9978
We want to allow for onchain features to be used by admins other than the namespace creator: see thread
Project Owner
@sachben91
Bucket ID
No response
User Stories / Acceptance Criteria
The system should restrict minting and burning to one address per transaction, or if feasible allow for a multicall.
Design Devlink
tk tk
Design Screenshot
tk tk
Additional Context