Monthly Initiative Update:
- Summary of Achievements:
- As part of Milestone 4, we integrated third-party Safe Account functionality with our modules by creating the Core SDK. This SDK allows JS/TS projects to utilize the 7579 module on existing Safe Accounts. The SDK is also available as an NPM Package.
- The Core SDK will be used by projects like QuestBook, as mentioned in previous reports, for module use cases in partnered projects.
- As part of Milestone 3, we organized a Modular Smart Account Expo aimed at the developer and Web3 communities. The expo will take place in three cities:
- Hyderabad, in partnership with Hyderabad DAO and Draper Startup House.
- Goa, in collaboration with HackVerse as part of Hacker House. (Close to 500 developers)
- Bangalore, in collaboration with Foundership (Details TBD).
- Each event will feature workshops on Safe Accounts, modules, standards, developer onboarding, and user onboarding using our apps. We have created exclusive demos and onboarding sessions for Safe using the Passkey module onboarding, along with a merchandise giveaway using the Smart Drop Module app. The module apps are deployed on testnets and the Base Mainnet. Event updates and outcomes can be tracked here.
- We are monitoring module activity and Safe user onboarding through on-chain events on Dune Analytics, which can be tracked here. Each event has an audience of approximately 100 attendees, who will be onboarded to Mainnet Accounts. We have already onboarded around 100 users on testnets.
- Milestones Reached:
- No new milestones completed this period.
- Milestone 2: Module auditing is still underway with a few final steps remaining before the Hats Finance audit competition
- Milestone 3: Good progress has been made in propagating module app usage through our apps, with two apps now on Mainnet. We are tracking Safe user onboarding and activity as we conduct offline events.
- Milestone 4: We developed an SDK leveraging the Safe {Core} SDK and 7579 modules to integrate existing Safes. We are collaborating with projects like QuestBook and Coinshift to utilize our modules using the SDK.
- Challenges/Blockers Faced:
- For Milestone 2, there have been some delays in finalizing the modules for audit, as we opted for audit competitions. Additionally, we focused on Milestones 3 and 4 to gain more clarity on module traction. We will resume our auditing efforts soon after the upcoming physical events.
- We needed additional refactoring for module templates and all our apps due to a new development involving the integration of module APIs by permissionless.js (Pimlico), which is officially promoted by Safe.
Milestone Progress Snapshot [%]:
Provide a snapshot of progress for each milestone as of end of reporting period; July 31, 2024.
|
Targeted %* |
Actual % |
Comments |
Milestone I |
100% |
100% |
|
Milestone II |
100% |
~60% |
Not a lot of updates as we focussed on M3 and M4. Please refer Challenges/ Blockers. |
Milestone III |
100% |
60% |
Onboarded users to testnet. Tracking new users on mainnet to be tracked post few physical events. |
Milestone IV |
80-90% |
80% |
Developed SDK leveraging the Safe {Core} SDK and 7579 modules. |
*Targeted completion % is derived from the proposal timeline, understanding that some milestones may have been blocked from progression for valid reasons. These blockers are reflected in our reporting sheets.
Month |
Amount Due |
Executed |
July |
$15,000 |
$15,000 |
Follow-Ups
Rationale on the decision of best auditing option…
- To make our decision on the module auditing process, we talked to several teams to get a sense of their module auditing (7579 modules and 4337 spec in general) expertise, how long it would take, their reporting methods, and the costs. From these chats, we realized audit competitions have a lot of perks: they attract more security researchers, provide clear issue reporting, and let us control the costs.
- We also monitored the audit competitions for the Palmera module and Safe last month. The results were impressive, with fair rewards and good-quality issue reports from researchers. Plus, the Hats Finance team previously guaranteed to come up with a method to facilitate on-chain security attestations for audit competitions. These points really helped us decide.
CES Comment:
- Note: this initiative is behind its projected timeline, although progress towards remaining milestones appears scheduled and reasonable.
- Have followed up for clearer rationale on decisions which have impacted delays and will copy responses above…
Safe Sign-Off:
- Approved - Amy (OBRA DAO Commission) August 7, 2024