juanfranblanco
commented
3 years ago Who is the user here? The DAO? Are you describing the flow for a charity to manage their funds and get the yield? The only issue i have with this is that i would prefer a central pot to get the yield, as we will have specific countries provide more tax incentives to have those charities receive those funds, adding a level of inequality to the other charities / countries. Also as a charity you would not want to have to manage the yield either (which is good, etc).
Edit: But those are semantics on something needed anyway :) Edit2: But maybe im wrong let the charity manage their funds.. but also do that schedule screen.
jaerith
The below flow exists only to describe the flow for a prototype, not for any complete product.
Initial Screen: Fully describe the intentions of the project and ask to connect to the wallet of the user (i.e., charity).
Transfer Screen: Ask for amount to transfer to yield contract. Present information to the user based about amounts and interest (i.e., $2000 deposit of 15% APY means $25 of purchase per month), so that the user can decide on the amount to transfer. Upon confirmation, the chosen assets (like DAI) will be put into the yield contract.
Schedule Screen: Present limited list of vendors (Amazon, etc.), with each vendor screen listing a few commonly desired items by charities (women's deodorant, socks, etc.). Allow the users to pick the vendor and items for the monthly delivery that fits the budget of the monthly yield. Possibly add option for altered delivery schedule (i.e., a delivery for every 2 months, with amount accumulated from a 2-month yield).
Confirmation Screen: Present all information detailing the autopurchase of goods from a scheduled yield. Request any information about notifications (email, text, etc.) before the final commitment.