-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Settlement Report for version 0.5.1. #113
Comments
Project at OpenDAN DAO Page is here: |
I'm confirmed. |
The score of story maker is too small. This was a very complicated logic at the time. The workflow and agent logic were not perfect at the time. I think the difficulty of this should be considered A level. At the same time, the working hours are far more than 2. Considering txt2voice and voice2txt It is the basis of story maker. Their evaluation time is on the high side. A3 is more suitable for story maker work. |
I confirmed. My address: 0xad82A5fb394a525835A3a6DC34C1843e19160CFA |
confirmed. Thank you to @waterflier and all contributors for their contributions and look forward to seeing our AIOS put into use! |
Follow your information, I update the repot~ |
Confirmed |
Confirmed. |
Confirmed. |
Confirmed. |
Confirmed. |
Final Confirm~ I will create the settlement purposal~ 0.5.1 total token is 35,000,000
|
After the launch of version 0.5.1 at the end of September, early users did not report any serious issues and are looking forward to our swift progression to the next version. Therefore, I request the settlement for version 0.5.1.
According to the rules of SourceDAO and the updated information at #46 , I have created the following contribution table. The basic logic is that for Category A tasks, 3 points are awarded per week, and for Category S tasks, 2 points are awarded per week.
If there are any omissions, all contributors are welcome to provide feedback! If there are no major changes, I plan to submit the official settlement proposal to the OpenDAN DAO Committee for approval in 3 days.
The text was updated successfully, but these errors were encountered: