FeedProjects
Developers
Settings
๐ŸŽ‰ A new chapter begins: Boardroom has joined Agora
Learn more
protocol logo
Explore / Projects
Blockzero Labs

Proposals

Members

Information

Create Proposal

Blockzero Labs

ProposalsMembersInformation
Proposal
Back to Proposals
closedEnded 5 years ago ยท Snapshot (Offchain)

Should we allow minter addresses for the Aqua token to be editable? (see additional info below)

By 0x1123...0e0000

Additional Information:

You can discuss here: https://discord.gg/vECzp2kc

After speaking with our senior blockchain engineer I have determined that the best course of action for the AquaFi protocol in regards to layer 2 support is as follows.

In order to support sidechains/L2, we need a L1-L2 token bridge. Due to the nature of the Aqua token (has mining ability), the token bridge must be able to mint and burn tokens at will.

For example, if you transfer 1000 Aqua to the L1 side of the bridge from L2, 1000 Aqua must be minted on L1/mainnet. This means tokens can be exchanged 1:1 between the Ethereum mainnet and the sidechain/L2 thus keeping the price of the Aqua token consistent over all chains where AquaFi is deployed. Unfortunately due to the permissionless nature of AquaFi (as it currently stands) it would be impossible to update the minters for the Aqua token.

I propose:

  1. we allow the Blockzero council to update (add or remove) the minters for the Aqua token via the council controlled multi-sig wallet.
  2. we implement a time-lock (duration to be determined) which means anytime the council wants to update the minter addresses, the council will need to submit a transaction to the ethereum network which will be publicly viewable. The council must then wait a period of time (duration to be determined) before the change is live and the minter addresses are then updated.
  3. we implement functionality that allows the council to permanently revoke this permission when executed

If we decide not to add this functionality, there is a very high chance that we will require a token migration each time we want to add or remove a new sidechain/L2 network. The alternatives are:

  1. Do not launch with sidechain/L2 support and require a rather large migration down the line if we want to support in the future
  2. Launch with support for predetermined sidechains/L2 networks - eg Arbitrum - this can never be updated (permissionless)
  3. Launch AquaFi independently onto sidechains/L2 - this effectively means Aqua on the other networks are completely independent from Aqua on the ethereum mainnet - so different prices, different tokens
Continue Reading
Connect Wallet to Add Note
0
Votes 30
VoterCast PowerVote & Rationale
0x5Da9...dC000A
662,389

Yes

0x9C86...0636B4
249,659

No

0xF44B...9E73c4
155,474

Yes

0xcdA2...721bb6
146,298

Yes

0xEB54...28F5AC
131,604

Yes

SHOW MORE
VOTE POWER
0
Connect Wallet
Proposal Status
  • Thu June 17 2021, 04:00 pmVoting Period Starts
  • Tue June 22 2021, 04:00 pmEnd Voting Period
Current Results

1-Yes

2.497M

90.23%

2-No

270,193.212

9.76%

3-I abstain

187.05

0.01%
DocumentationBrandingContact Us
Home
This Project is Currently Disabled

If you would like to enable it, please checkout below.

Boardroom Subscription

Sign up for an individual subscription (access all projects on the platform)

Subscribe
Enable Project

Enable the entire project for every user

Enable Project
Contact Us