1. Context
The AMM market keeps expanding, with already 30+ players identified across Ethereum, Ethereum layers 2 and other blockchains.
Although not complete, the following visual provides a fair representation of the market: https://twitter.com/pironidi/status/1462435625383219200?s=20
AMMs compete for liquidity and best prices. Some innovative protocols stand out by their offering and / or approach to liquidity, creating very interesting use cases to study.
2. Proposal
To have a better understanding of those protocols and competitors, Ref’s dev team suggests the use of 5 ETH from the DAO in order to test and collect ‘data intelligence’ from direct and indirect competitors.
The main objective being the improvement of Ref solution, via the potential deployment of proven and market-approved features.
3. Scope
The scope of study would mainly include:
- AMMs
- Lending and Borrowing protocols
- Aggregators
- Payments
- Analytics
- Staking
- Insurance
- Derivatives and Margin trading
- Asset management tools
The underlying smart contract infrastructure is multi-chain and can include:
- Ethereum
- Ethereum L2 (Arbitrum, Fantom, Optimism, Polygon)
- Other blockchains (Algorand, Aurora, Avalanche, BSC, Cosmos, Elrond, Heco, Klaytn, Kyber, Near, OKEXChain, Polkadot, Secret, Stellar, Terra, Tron, xDAI, Zilliqa)
4. Testing approach
When the team targets a specific protocol, the following options MUST be considered, before any Mainnet interactions:
- Testnet environment: can the Testnet env and version offer a similar experience (both at the execution and functional levels)?
- Local fork: can the dev team deploy a local fork and simulate a similar production experience at a low dev cost AND below the opportunity cost of the current Roadmap?
In case the above alternatives to Mainnet testing can’t be achieved, the dev team will use Mainnet. Every test on mainnet will be rigorously documented.
In case the proposal fails, the above options will be followed.
5. Proposal execution
As ETH from the IDO is actually in the form of nWETH, which is not supported now, this 5 nWETH would first be sent to an existing nWETH NEAR account and then second, be sent through the Rainbow Bridge.
The ETH account would be in the hands of the dev team. The address will be public (available to the community) for transparency and monitoring purposes. Each event will be recorded in a public DEV-ETH-USE REPORT doc, updated on a monthly basis.