# Daosquare Post Mortem ## RICE CCO CCO worked as expected. The CCO completed in less than 2 min. Hitting the cap and closing the raise. But there were issues: * user experience was not great. * The main feedback was there was too much complexity in withdrawing and canceling. * Proposals that came in after the cap was already met would have to go through this process. Then because it takes a few hours to process all proposals, some people where left not knowing if they got in in time or not. Although this was the expected behavior and was relayed to Daosquare before the CCO, the users did not like it and found it confusing. We did not anticipate the CCO filling so fast. Part of the issue was compounded by a user base that was not web3 native, so dealing with MM and blockchain in general was harder for them. ### Things we can iterate on We have now created a new proposal type ('CCO funding proposal') and smart contract that will fail once the cap is meet. Because of how transactions are procesed in blocks, there will still be a chance that some proposals will get in during the same block and after the CCO has filled, which is why the proposal processing bot and human oversight will still be necessary. We can continue to iterate on this process, potentially with a new DAO contract. The verification of join proposals and waiting period for those proposal to be accepted is actually more a feature than a bug. It is good to have some manual verification and lock up time, although is not instant enough for contributors. We can work on better UI messaging and community messaging to better inform users of the process before they participate. This, along with the fact that there would be fewer invalid proposals with the new 'CCO funding proposal' type, should help with overall UX. Daosquare gave UX a 5 out of 10. So definitely improvement space there ## Farms Several Issues: **Issue 1:** On the day of the launch there was a critical bug on the front-end that blocked many users from seeing the interface. Because the farm was launched in the middle of the night (US time) no one from the dev team was able to look at it until hours later. The core reason for this failure was a miscommunication regarding when the farm would be launched. The US dev team was informed the late on the night of the farm launch, and no one was online to see the notification or provide support. Furthermore, the farm UI contract was owned by a single dev, who was not reachable immediately because of a personal health issue. Once we were able to get a hold of the Farm UI dev the fix was very simple and took about 1hr to update the frontend code and deploy the new version. **Issue 2:** Initial testing was done on xdai with the RICE token and Daoquare felt this was unprofessional. During testing we found a issue with the smart contract where any funds sent to the farm and not claimed by the end of the farming round would be locked up. This requires no one to be in the farm at the time the reward period finishes. This bug locked up about 10-20 RICE in the test contract, forever. ### Things we can do better Schedualing coordination was the major flaw here. In the future we will need to have a 72hr lead before any launches. Single point of failure with single dev involved. We need to have backups and a way to handle or delay a launch when lead dev is not available. Time zone issues, the core dev team is in the US and Daosquare is in China; this makes for a lot more coordination effort to get meetings and launch times reasonable for both sides. ## Conclusion: * Client and User expectations where not managed correctly * Timezone coordination was not handled correctly * Launch day should have been delayed. Need 72hr lead time before any launch. And furthermore, we should operate with a launch checklist and ensure that the primary responsible dev and a backup dev are available on launch day in case of a bug. * Overall we rushed this, because Daosquare asked for an agressive timeline and we accommodated that timeline based on our friendship. We rushed through an amount of work in a month what should have been done over 2-4 months minimum. ### Relationship going forward: 7k retainer for the month of June will be waved and because future CCOs are not a priority, further engagement and retainers are closed. Hand off all current work to RaidGuild. Raidguild will create a spec for work going forward.