TL;DR:
The community is actively discussing 0xlide's proposal to add FXS to the Ethereum Aave v3 Liquidity Pool, with parameters like isolation mode, borrowable status, collateral enabled, and a supply cap of 800,000 FXS. Despite concerns from 0xlide about the snapshot for voting, Alice believes it's the right choice to gather community opinion and enable FXS listing before governance pause due to V3 migration.
The discussion revolves around the proposal by 0xlide to add FXS to the Ethereum Aave v3 Liquidity Pool1. The proposal includes specific parameters, such as an isolation mode, borrowable status, collateral enabled, and a supply cap of 800,000 FXS, which are supported by Gauntlet1. Alice and ChaosLabs have also contributed to the discussion, providing feedback and risk analysis respectively2,4,5.
The community is actively engaged in the discussion. Alice has provided feedback and initiated a snapshot for voting2,6. However, 0xlide has expressed concerns about the snapshot, suggesting that more thorough discussions should take place before proceeding with the vote7. Despite these concerns, Alice believes that going to snapshot now is the right choice as it would gather the community's opinion and allow a path for FXS to be listed before the pause in governance due to the migration to V38.
The proposal to add FXS to the Ethereum Aave v3 Liquidity Pool is a positive development as it expands the range of assets available in the pool1. The active engagement of the community, including the feedback and risk analysis provided by Alice and ChaosLabs, demonstrates a healthy and collaborative decision-making process2,4,5.
The concerns raised by 0xlide about the snapshot for voting indicate potential issues with the decision-making process7. The disagreement between Alice and 0xlide over the timing of the snapshot and the need for further discussion could lead to divisions within the community7,8.
Posted 2 months ago
Last reply 2 months ago
Summary updated a month ago
Last updated 06/12 00:43