Thanks for your proposal to The Sia Foundation Grants Program.
After review, the committee is requesting some additional information regarding your proposal:
You state in your initial proposal that all code will be open source, but then later in your update state that it will not be. Fully open-source code is a requirement for funding under the grants program.
Do you have any proof of past development work, like a completed project or Github repo?
In your latest comment, you mentioned that you will be working full-time on SecureSphere. Have you secured other funding to allow this?
We’ll keep this in the Proposed section while we await your response. Thanks again for your proposal.
Thank you for taking the time to review my proposal and for providing valuable feedback. I truly appreciate the opportunity to clarify and address the points raised.
Open Source Commitment
I would like to confirm that all the code for SecureSphere will be fully open source as per the grant program requirements. I apologize for any confusion caused by my previous update. I have consulted a legal expert to ensure that the project complies with GDPR and other relevant data protection regulations. Adjustments to the data collection policy will reflect this compliance while maintaining the transparency of the open-source commitment.
Proof of Development Work
While I do have a proof of concept to demonstrate my past development work, these projects are not open source. However, I am happy to share them privately with the committee for evaluation purposes. Please let me know the best way to proceed with this.
Full-Time Commitment and Funding
I am fortunate to have passive income that covers my personal expenses, allowing me to dedicate myself fully to SecureSphere. The grant funding will be specifically allocated to employee salaries and hiring freelancers to accelerate the development and delivery of the project.
Thank you once again for your consideration. I remain committed to creating a meaningful and impactful open-source solution and look forward to your guidance on the next steps.
Please send whatever you’re able to share to [email protected]. We’ll be re-reviewing the grant and your responses at the next meeting on January 21st.
Thanks for the update! I’ve already sent the email with the requested details. Let me know if you need anything else before the review meeting on January 21st. Looking forward to your feedback!
Thank you for your support and for approving my proposal! I truly appreciate the opportunity to build SecureSphere with the help of the Sia Foundation. I’m excited to move forward and demonstrate the impact of decentralized security solutions.
I look forward to the onboarding process and will adjust my timeline accordingly. Please let me know if there’s anything I need to prepare in advance.
What progress was made on your grant this month?
Over the past two weeks, we have focused on research and the creation of a system architecture diagram for our app. This includes defining how different programming languages will be used across the mobile app, browser extensions, and backend. Additionally, we have started working on the encryption feature and the Sia integration. We are currently testing two different integration models and will begin development on the most efficient one in the coming days.
Links to repositories worked on this month:
We will share them in a few days.
What will you be working on next?
Our next focus will be further development of the encryption feature and the implementation of the browser extensions.
What progress was made on your grant this month?
This month, we achieved significant milestones in developing the browser extension and mobile app, bringing us closer to MVP completion.
Browser Extension (80% Complete)
Finalized SIA integration for encrypted backups and password recovery.
Completed Password Manager core functionality.
Enhanced data encryption (local storage + backups) for security.
Improved UI/UX based on user feedback.
Added seed phrase authentication for decentralized access.
Mobile App (75% Complete)
Implemented all browser extension features (backups, password manager, encryption).
Added custom SIA node support: Users can now connect to their own rented SIA nodes or use ours via API/S3. (Note: This feature extends beyond the original grant scope.)
Hi @parox,
Our mobile app repository has been updated:
Integrated features: Password Manager core function, Signup with seedphrase, SIA backup upload, and all the main features of our app.
Apologies for the delay in publishing we wanted to ensure we share something with as many features as possible and as few bugs as we can. We will be sharing new features and the APK very soon.
Hi @Hani, thank you for updating the app repository, can you also provide a link to the code for the browser extension?
In the app repository I see an S5 integration, could you point me to the code for the renterd integration mentioned here:
Added custom SIA node support: Users can now connect to their own rented SIA nodes or use ours via API/S3. (Note: This feature extends beyond the original grant scope.)
Hi @parox browser extension will be available late today or tomorrow after finishing some modification, for the user custom node we will update it in few days after the testing
Our dev team has reviewed your progress report and was not able to find work related to your stated milestones or work referenced in your report for this month. Our developers attempted to review work related to:
The browser extension
As a result, we’ll withhold payment until they can review.
Please reference specific commits or branches and how they relate to your progress and milestones for this month. Thanks, and let us know if you have any questions.
We’ve slightly adjusted the timeline of our project due to the unexpected complexity of the mobile app. As a result, we advanced more on the mobile app this month and pushed the browser extension slightly behind. However, the extension is nearly complete we’re currently finalizing the authentication function, which required some additional time and rework.
The changes were made to ensure better overall integration between the extension and the app, but we’ll make sure everything is transparent and properly documented for your review.
Please let me know if you’d like further clarification. I’m happy to provide any additional information.
Thanks for the update. We’ll send your latest payment.
In the future, progress must be able to be easily evaluated by our development team. Please clearly cite work in PRs with clear descriptions and link them in your report. Work done in un-merged branches or locally pushed without version tracking can make it more difficult for our devs to sort through.
Hi @steve Thank you for the update and for processing the payment.
I completely understand the importance of clear tracking and visibility for the dev team. Going forward, I’ll make sure to include detailed PR descriptions, clearly reference relevant commits, and provide direct links in the progress reports to make the review process smoother.
