Skip to content

Enabling Policy creators to specify rules and parameters of Token Lifecycle #1697

@prernaadev01

Description

@prernaadev01

Problem description

All methodologies define rules, explicit or implicit, that govern the lifecycle of carbon units which includes rules for:

  • matching with other units
  • disposal
  • exchange and transfer
  • rectification
    This rules can be different for different tokens, and can change for tokens depending on the governing regulations and jurisdictions. Furthermore some other groups, e.g. industry associations or trading partnerships, can impose other (more strict) requirements and constraints on the lifecycle in addition to those specified by the minting Standard Registry (SR). The architecture needs to also support making this to be enforceable.

In Guardian ecosystem rules for tokens, representing such units, need to be enforced by technology.

Requirements

Using a combination of HTS and HSCS capabilities develop a consistent system which enable policy creators to specify rules and parameters of the minted token lifecycle such that:

  • rules are enforced regardless of whether Guardian is used or not for token management
  • rules and their parameters can be changed by the SR that originally minted the token
  • anyone can create additional sets of rules and any holder of the token can agree to follow them, thereby imposing on yourself these additional rules. Such rules cannot overwrite the original SR rules, the validation is effectively performed in a sequence:
    additional rules applied for validation of the attempted action
    SR rules applied

Definition of done

Guardian reference implementation of smart contracts contains provisions for SRs to switch on and parameterize (i.e. configure various rules thresholds etc) rules governing the most common aspects of carbon units lifecycle. These rules then become automatically enforced on-chain as described above.

Acceptance criteria

Guardian policy authors can create tokens on-chain lifecycle rules.

Metadata

Metadata

Assignees

No one assigned

    Labels

    ø Next PhaseWill be worked in Next Phase Propose to delete. Handled by milestones.ø documentationImprovements or additions to documentation Propose to delete. Handled by storymap columns.ø technical taskPropose to delete, handled by issue types

    Type

    No fields configured for Epic.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions