Tracer DAO is inviting new governors to join the DAO to govern the Tracer Protocol. Over the coming weeks, 200 new governors will be accepted into the DAO. Candidates are considered for selection from the following categories as per the Radar Article: Govern Tracer:
As a part of Lion’s Mane’s engagement to Tracer DAO, a recommended list of applicants was curated and presented to current DAO members for discussion and approval. The process used to create the recommended list can be found here Governor Applications: Lion’s Mane Recommendation.
Lion’s Mane has recommended that governors are accepted by Tracer DAO in batches of ~50. The reasons supporting this revised approach:
It is important to remember that this process is designed to cultivate the best possible group of decentralised Tracer DAO governors, who will lead Tracer to change the financial industry as we know it.
In line with this revised approach, Lion’s Mane will:
The following proposal, if engaged, will accept the first batch of new governors into Tracer DAO.
If this DAO Proposal is accepted, new governors will commit to ( Deliverables ):
The proposed first batch of 52 new governors can be found here:
Tracer >|< Governor Applications - Final LM Recommendation
Unless otherwise defined in this Proposal, all terms beginning with a capital letter which are defined in the Participation Agreement have the same meaning unless the context otherwise requires.
If this Proposal is accepted as a Proposal under the Participation Agreement, members may more formally document aspects of that Proposal.
Copyright and related rights are waived pursuant to CC0.
In order for the 52 governors to be engaged to provide the services described above, the following targets and relevant Proposal data must be passed to the DAO, via Proposal, by a current DAO member, in order to facilitate the execution of that Proposal. For each piece of Proposal data provided, the function encoded data that must be passed into the DAO is present, as well as the parameters and function calls used to generate this data. By utilising a package such as web3, any DAO member may verify this data using the web3.eth.abi.decodeParameters function (web3.eth.abi — web3.js 1.0.0 documentation).
The steps that the DAO must execute in order to appoint the new DAO members are as follows:
targets : [“0x9C4A4204B79dd291D6b6571C5BE8BbcD0622F050”, “0x9C4A4204B79dd291D6b6571C5BE8BbcD0622F050”]
proposalData : [“0xa9059cbb000000000000000000000000399257702f0f05ebec30c17b8888be1b2a321e3600000000000000000000000000000000000000000002268f76a7c51f08b00000”, “0xa9059cbb00000000000000000000000045eca81a5bfbdd58cafb225bd4c9c49c8db99754000000000000000000000000000000000000000000000002d1a51c7e00500000“]
name: Transfer 52 * 49999=2599948 TCR tokens to the new vesting contract
target: 0x9C4A4204B79dd291D6b6571C5BE8BbcD0622F050
proposalData:
0xa9059cbb000000000000000000000000399257702f0f05ebec30c17b8888be1b2a321e3600000000000000000000000000000000000000000002268f76a7c51f08b00000
raw data:
name: Transfer 52 TCR to the airdropper contract
target: 0x9C4A4204B79dd291D6b6571C5BE8BbcD0622F050
proposalData:
0xa9059cbb00000000000000000000000045eca81a5bfbdd58cafb225bd4c9c49c8db99754000000000000000000000000000000000000000000000002d1a51c7e00500000
raw data: