Lbrian
May 22, 2023, 4:41pm
327
ATTN: BIT Delegates and active BitDAO/Mantle governance participants:
Check out details on the migration of the BitDAO forum to a Mantle forum as part of new changes under BIP-21, which was passed last week.
This post outlines details about:
Archiving and comment access
Forum migration process (BitDAO forum → Mantle forum)
Launch of the Mantle Governance Forum
Curation of content
Privacy Policy
Dear forum users,
We would like to inform you about the migration process for our forum in accordance with BIP-21 . The migration involved cloning the forum from https://discourse.bitdao.io to https://forum.mantle.xyz . Please take note of the following important details:
Archiving and Read-only Status
The BitDAO forum was archived and set to read-only at approximately 2023 May 24, 1PM UTC.
The read-only forum will be retained for record-keeping purposes, particularly for situations where …
Lbrian
May 22, 2023, 6:28pm
328
Following BIP-21, A new soft proposal has been posted to the BitDAO forum for discussion:
Please read the proposal for full details. Share your comments, feedback directly on the proposal discussion:
[DISCUSSION] Mantle Token Design, Conversion Parameters, and Asset Handling
Unifying the ecosystem under the Mantle brand with a product focus will prevent fragmentation. The token conversion plan ensures a fair and convenient transition for all holders. Accelerating vesting schedules simplifies tokenomics and boosts transparency. Governance remains intact, empowering the community. Existing initiatives maintain their autonomy. Maintaining redirects from the old website ensures a smooth transition. Exciting times ahead for Mantle Network and BIT ecosystem!
1 Like
I support this progress, as this can unite the project as one and avoid confusions in the future.
1 Like
I support this proposal of ONE BRAND, ONE TOKEN.
The only challenge I think I have with this proposal is the conversion rate.
Je
May 24, 2023, 1:08pm
335
Dear forum user, due to the forum migration , this discussion has now been set to read-only.
Please continue the conversation here .