Motion 29-34: cancel legacy and approve new bounties

Motion 29: re-add the second new Gatekeeper

This is a follow-up of and fix to motion #23. It removes the wrongly added pRuntime hash, and register the second Gatekeeper again.

Motion 30: close bounty “Phala Network Demand-End Tokenomic Design”

Bounty #4 was incorrect because it doesn’t include the curation fee. This motion closes Bounty #4.

The new bounty #6 is the total amount including the curation fee. However we’d like to split it to two milestones. So I suggest to vote Nay to the motion to accept bounty #6 (Motion #33)

Motion 31: close bounty “Miner monitor robot on telegram”

This bounty was a test. Nobody is backing up it.

Motion 32: approve bounty “Phala Darkpool Exchange”

Bounty #5 is proposed by an ecosystem team to build a Darkpool on Phala. More details can be found in Phala Bounty Tracker PR.

:warning: Please vote Nay to this motion because the requester wants to change the amount of the bounty. We are also waiting for the feedback to our PR comment.

Motion 33: approve bounty “Phala Demand-End Tokenomic Design w/ curator fee”

:warning: Please vote Nay to this motion because we are going to create another bounty.

Motion 34: approve bounty “Phala Demand-End Tokenomic Design M1”

This is the updated bounty request for the tokenomic design. Instead of requesting the total number, this bounty request for its Milestone 1. According to the bounty request, the breakdown is:

  1. M1: Pre-implementation
    • Deliver the full conclusion of the tokenomic design, the parameters, and the paper to describe the design
    • 65% of the total amount, or 117000 PHA, including the 33% curation fee
  2. M2: Post-implementation
    • Help the dev team to implement and launch the new tokenomic on Khala and Phala if applicable
    • 35% of the total amount, or 63000 PHA, including the 33% curation fee
1 Like