AELIP-40: Extra info for vouched direct deals
Author | |
---|---|
Status | Approved |
Implementor | TBD |
Release | TBD |
Created | 2022-10-14 |
Simple Summary
This AELIP proposes to let protocols and large holders creating direct deals to optionally share additional information:
- Twitter handle
- Website link
- Mirror post hash
- Discord username
The Aelin UI will only show this additional data in the verified pools section.
Abstract
As more investors participate in Aelin Pools and the upcoming deals, it is clear that more information is needed to help understand what protocol or large holder is raising funds or doing an OTC deal and why? Often this is because an early stage project is raising funds and there is no token trading yet.
Also, content for the mirror post hash that is shared must be tied to the sponsor's account (e.g. mirror.xyz/<sponsor address>/<mirror post hash>
). For direct deals the sponsor is always the account creating the deal initially.
Motivation
The goal is to simplify the experience for investors to provide them with more information about a direct deal. At the moment there is no way of verifying that information provided by sponsors is accurate so these fields will only be shown in the verified section.
In the near future an AELIP will be presented to allow anyone to vouch for deals and to update the UI to see which deals a specific ENS or address has vouched for. This information will be available for that future section as well, removing the need to rely on the Aelin Council for vouching.
Specification
Overview
A new struct will be created and stored in the smart contract for retrieval and display in the UI. This change will not affect the direct deal logic.
Rationale
Pushing this AELIP now to improve the investor experience and providing protection by only putting these fields in the verified section.
Technical Specification
Test Cases
Copyright
Copyright and related rights waived via CC0.