Hi fam, we’re happy to have you here for the next (semi-)weekly update. Expo Week took over most of our attention, but we’ve got something to show for it!
The Last Two Weeks
Work continued on our MVP while we also prepared a demo and slide deck for the KERNEL Midway Expo Week. During Expo Week we got the opportunity to showcase our vision, business case, and the CommitPool app to mentors Sandeep Nailwal (Matic), Devin Walsh (Coinfund), and other KERNEL fellows. We are thankful for their input and are looking forward to follow-up conversations!
The slide deck - including demo video - is made available here.
The demo session really pushed us to mature the MVP and move from proof-of-concept towards a fleshed out application.
In addition to preparing for Expo Week, we:
Successfully integrated Tasit SDK for wallet creation/management in our mobile app
Began exploring database integrations for managing refresh tokens. A database is the intermediate solution while we further refine our solution to our oracle problem
Continued deliberating on the trade-offs between the oracle problem, centralization, and protecting user privacy. In the short term, we’re testing a solution that compromises slightly on centralization while letting us iterate faster elsewhere without leaking user data
Improved on the smart contract code with some tests
Next Week (Week 6)
Next week our goal is to progress our demo application into a testnet MVP that we can distribute to early users for testing, feedback, and of course helping them meet their commitments!
To meet this goal we are focusing on:
Implementing the short term user privacy solution
Polishing the mobile apps for iOS and Android based on our Figma designs
Improving documentation within our repositories
Getting our apps in TestFlight and Play Store early access
Continuing to mature our smart contract testing suite
Asks
We are looking for input on our architecture, especially regarding the trade-off between user privacy and decentralization. For our MVP we are using a database for maintaining users’ Strava OAuth refresh tokens that our Chainlink adapter needs to bring their exercise activity data on-chain. We would welcome any input that helps us remove our dependency on a database without putting user privacy at risk.
In commitment,
Ken and the CommitPool team