Skip to content

[Permissions Bount To “0th NFT”] & [Permission Transfer] #10

@matic0209

Description

@matic0209

Feature Background
Semios need to establish a permissions system for users, allowing them to separate management permissions based on their preferences. To achieve this, we have designed a permission management mechanism based on NFTs. The corresponding node's permissions are bound to the 0th NFT on the Nodes 721 contract to accomplish the respective objectives. The specific requirements are as follows:

When create a Seed Nodes in Semios, user will have the following 7 Permissions, which are:

  1. SubNodes Edit Information Permission
  2. Edit On-chain Parameters Permission
  3. Edit Strategies Permission
  4. Starter Reward Claim Permission
  5. Seed Nodes Edit Information Permission
  6. Treasury Permission
  7. Top-Up Governance Permission
    These permissions will be bound to the 0th NFT of the SubNodes ERC-721 contract. Whoever holds this NFT will have the above permissions. These permissions can also be bound to different NFTs (in My Permissions or on the details page of the corresponding NFT) allowing for more flexible management and customization of your Node's permissions.

When you create a SubNodes in Semios, you will have the following 4 Permissions, which are:

  1. SubNodes Edit Information Permission
  2. Edit On-chain Parameters Permission
  3. Edit Strategies Permission
  4. Starter Reward Claim Permission
    These permissions will be bound to the 0th NFT of the SubNodes ERC-721 contract. Whoever holds this NFT will have the above permissions. These permissions can also be bound to different NFTs (in My Permissions or on the details page of the corresponding NFT) allowing for more flexible management and customization of your Node's permissions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions