Joystream / Joystream/joystream

crt whitelist storage logic not defined yet

Open
#4,859 0 comments 0 reactions 1 assignee Claimed by @dobertRowneySr View on GitHub
crt-v2 project_token runtime
Dominant language
Rust
Stars
1.4k
Forks
116
PR merge metrics
No merged PRs in 30d

Description

When creating a permissioned CRT via the `issue_creator_token` extrinsic you have to specify the following parameters:

``` rust
pub struct TokenIssuanceParameters {
/// Initial allocation of the token
pub initial_allocation: BTreeMap,

/// Initial transfer policy:
pub transfer_policy: TransferPolicyParams,

/// Initial Patronage rate
pub patronage_rate: YearlyRate,

/// Revenue split rate
pub revenue_split_rate: Permill,
}

pub enum TransferPolicyParams {
/// Permissionless
Permissionless,

/// Permissioned transfer with whitelist
Permissioned(WhitelistParams),
}

pub struct WhitelistParams {
/// Whitelist merkle root
pub commitment: Hash,
/// Optional payload data to upload to storage
pub payload: Option,
}
```

The logic behind is that we should upload the whitelist to the storage.
But no logic is yet present in order to achieve that https://github.com/Joystream/joystream/blob/2826d5137dec295f9652ec4b2021ad1a60803460/runtime-modules/project-token/src/lib.rs#L2042

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.