After a full review of the project deliverables record and feedback exchanges. Here is the summary of the exchanges for more clarity:
| June 13 | Milestones deliverables agreed | 3 milestones defined |
| July 10 | start date | after KYC being completed. |
| July 28 | DA reminder about program end | “The pilot of The Sandbox DAO Grant Program ends on August 31st. Please submit your final milestone at least 5 days before that date.” |
| August 2nd | Grantee submission | Team declares all 3 milestones “completed” and requests review. |
| August 11 | DA review #1 | Feedback provided after review, Milestone 1 not validated due to technical issues (converter not importing correctly into Unity/Roblox). |
| August 18 | Correction #1 submitted | Grantee sends revised files. |
| August 25 | DA review #2 | Milestone 1 rejected again. DA warns: “This is the second time M1 has been rejected. Please address all feedback; otherwise, I will cancel the grant.” |
| August 26 | Grantee follow-up | Team sends additional information to fix M1. |
| September 6 | DA review #3 | Still not working. DA says: “I will give you a last chance, guys.” |
| September 6 | Grantee request | Team asks for a call to discuss issues. |
| September 18 | DA validates M1 | Milestone 1 validated. But, Milestone 2 not validated due to texture issues caused by size reduction. |
| September 22 | Grantee correction #2 | Grantee reports issue fixed for M2 and submits final report. |
| September 26 | DA review #4 and cancellation | DA notes textures fixed but animations removed, invalidating performance results. Grant canceled for missed extented deadlines and unvalidated deliverables. |
| October 11 | Grantee follow-up | Reports that the issue is now fixed, after the project’s cancellation and program closure. |
DA holds the discretion to review and validate milestones based on their technical expertise. The admin team does not override or influence these evaluations. The DA’s decision to cancel the grant was made in accordance with standard grant procedures and within the scope of their delegated authority.
–
The corrections requested by the DA were not “add-ons” or optional improvements, they directly concerned the core deliverables (e.g., successful import of .glTF/.glb files into Unity and Roblox, accurate texture and animation handling). These were explicitly listed as part of the milestone deliverables.
–
A milestone is considered “completed” only once it has been reviewed and validated by the DA. Submitting files does not constitute completion if the deliverables fail to meet the agreed requirements.
Hope this clarify.
Best