Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Treasury for Hashed Network budgets #369

Open
mgravitt opened this issue Feb 23, 2023 · 0 comments
Open

Treasury for Hashed Network budgets #369

mgravitt opened this issue Feb 23, 2023 · 0 comments
Assignees

Comments

@mgravitt
Copy link
Contributor

The HN genesis token budgets are broken out into percentages of the total token supply

image

Over the long term, each of these budgets will have their own council to approve spends. For example, there may be a Marketing team that spends the 2.6% allocation.

These allocations are NOT available all at genesis though. They will vest into the treasury over time.

On Polkadot, the Treasury pallet is funded by inflation rather than the genesis budget. So, the initial task is to figure out if we can use the concept of vesting and/or vesting pallet to make funds available to a specific Treasury over time. For example, perhaps the Marketing budget vests to the Marketing Treasury over 2 years at x per block, and the owners of that particular treasury are Alice, Bob, and Charlie.

Then, anyone can post proposals on that particular Treasury and Alice, Bob, and Charlie will review and decide to approve or not.

The initial task is to do a POC that shows this is possible and begin to configure it on Hashed Network. We can have Sudo assign the multisig treasury approvers for each budgeted bucket.

Over the long term, these budgets may have additional functionality:

  1. The approvers would be elected rather than assigned by sudo.
  2. The treasuries will be funded by inflation rather than genesis allocations.
  3. The treasuries will be assigned burn rates, so something like 0.25% of the treasury is burned each week to avoid stockpiling of accrued funds.

But for now, the basic functionality needed is multisig over the separate 11 budgeted allocations with vesting.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants