Thank you so much for the feedback and ideas! It’s great to hear that there’s enthusiasm around a password manager with a focus on security and privacy.
Regarding your question about S5 vs Renterd, our plan is to offer both options to users during the setup process. This way, users can choose the storage solution that best fits their needs and preferences. For example, S5 (Sia) will be available for those who prioritize decentralization and full control over their data, while Renterd will provide a more streamlined, user-friendly option for those who prefer a simpler experience. We want to ensure that users have the flexibility to choose what works best for them.
As for the desktop/web app, I completely agree that it’s a key next step after our MVP. The mobile app and browser extension will be our first release, but we have plans to expand into desktop/web apps to offer a more comprehensive solution.
Regarding liso.dev and other competitors like Bitwarden/Vaultwarden, I’ve already analyzed these projects, and our approach will be focused more on privacy encryption and breach monitoring. After the LastPass breach, I was motivated to develop a more secure solution that goes beyond just password management. This project has been in my mind and research for over a year, and the MVP is just the beginning. I’ve worked extensively as an IT consultant for banks, so security is at the core of everything we’re building. Our ultimate goal is to bring Sia technology from individual users all the way to business-level banking solutions.
This is only the start, and we’re excited to offer a highly secure, privacy-focused product that leverages the power of Sia. We appreciate your support and feedback!
I think you got those inverted… lol. renterd requires you to run your own node, manage contracts/money etc, and S5 would enable cloud hosting (like Lume) and P2P syncing.
And I see the most value from this through S5 personally (and if integrated into Vup later, can possibly use its account system? idk). That is how I would be immediately using this once all legos are ready (I still have work to do myself).
And I moved to bitwarden after lastpass so I 100% get your POV.
Thank you for your feedback! I appreciate the clarification regarding Renterd and S5. You’re absolutely right—S5 offers cloud hosting and P2P syncing, making it a much more practical and user-friendly option for most users. Meanwhile, Renterd provides the control and customization needed for advanced users who want to manage their own nodes.
To address this, we plan to include both options in our setup. This way, individual users can benefit from the simplicity of S5, while businesses and enterprises with specific needs can leverage Renterd for maximum control. Our goal is to ensure flexibility while maintaining a seamless user experience.
I also had the chance to learn more about Lume, and it’s truly an inspiring project. Your vision of using P2P technology to tackle access issues and empower users with ownership of their data and content aligns closely with our philosophy. I’ll definitely explore if there’s a way we can leverage Lume within our solution. Integrating with platforms that share a commitment to privacy, decentralization, and user freedom is a priority for us.
As for your thoughts on Bitwarden, I completely understand its appeal after the LastPass breach—it’s a robust solution. However, our approach aims to build on this foundation by incorporating breach monitoring, enhanced encryption and decentralized storage (In the final product) to create a security-first tool that serves both individuals and businesses.
Thank you again for your insights—they’re invaluable as we continue to refine our approach and ensure that SecureSphere aligns with both user needs and the broader goals of the Sia ecosystem.
Thank you for the note! I double-checked the grant request template and couldn’t identify any missing information. If there’s something specific that I overlooked, I’d appreciate it if you could point it out.
We cannot provide grants to residents of jurisdictions under increased FATF monitoring, those that have active OFAC sanctions, or those that fail our bank compliance tests. We also cannot provide grants if your payment bank account is located in those same locations. Please review the following list.
Are you a resident of any jurisdiction on that list? Yes/No
Will your payment bank account be located in any jurisdiction on that list? Yes/No
Contact info
Email:
Any other preferred contact methods:
It may look like answering those two questions about the residency and/or the bank with a “yes” would automatically bring the proposal to a rejection. And, unfortunately, it will.
The thing is that, if both questions are deceivingly answered with a “no”, and even if the Committee approves the proposal, it will surely become clear at the onboarding stage, so it ultimately will be a waste of time for both the Committee and the author of the proposal.
Speaking from my personal point of view, I regret that we have to do this, but at the end of the day, it is the legal entity of the Foundation who pays the money, and they have to comply to the laws.
Thank you for the clarification. I can confirm that neither my residency nor my bank account is located in any of the listed countries, I added that to my proposal
Lume as a project has done several experiments in the past, but moving forward the project is more immediately focusing on hosting (long term goals are a long ways off). IPFS is already supported, S5 will be next. So, as long as a supported P2P protocol (these are actually plugins to the portal) is used for your app, a portal node can be used to host the data.
Thank you for the detailed explanation. It’s great to hear that Lume supports IPFS and is planning to integrate S5 next. This aligns perfectly with the flexibility we aim to provide in our app. We will ensure compatibility with supported P2P protocols, enabling users to take advantage of portal nodes for data hosting. This modular approach fits well with our vision for offering secure and decentralized options.
After extensive research and consultations with industry experts, I am excited to announce that SecureSphere will be my main and full-time project for 2025. Here are the latest updates on the project’s progress and future plans:
Formation and Team Expansion
I have begun the process of establishing a dedicated company for SecureSphere to ensure the project’s growth and sustainability.
I am actively seeking a UI/UX designer and developer to join the team and help bring our vision to life.
Expanded Vision Beyond the MVP
The initial idea has grown significantly, and we are working toward broader applications following the release of the MVP:
Hardware Password Manager for Individuals:
A physical device that securely stores passwords.
Fully synchronized and backed up using Sia S5 decentralized storage.
Enterprise Hardware Solutions:
Data storage and password management hardware tailored for businesses.
These devices will also leverage Sia’s decentralized network for synchronization and storage.
Advanced Data Breach Detection System:
We are developing a system to scan the dark web, hacking forums, Telegram channels, and other sources for data breaches.
This system will compare detected breaches against data saved in the password manager.
Open API: While the system itself may not be fully open-source (due to legal and security concerns), we plan to offer it as an API for developers to integrate into their solutions.
Key Differentiators
Data Ownership: The use of Sia’s decentralized storage network will remain at the core of SecureSphere, reinforcing our commitment to user-owned and private data.
Future-Proof Vision: By integrating hardware solutions and decentralized technology, SecureSphere aims to redefine the landscape of password management and data security.
We are confident that these developments will make SecureSphere a standout project in the data security space. I look forward to sharing more details about the technologies, hardware devices, and our roadmap as we finalize the MVP and move forward.
Together, we can build a more secure and privacy-focused digital future.
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.