Tronent - Decentralised Versioning and Secure Backup

[Varun_Kapoor]

@Chizz

Welcome to the hackathon session
By offering a decentralized approach to file storage and management, I am concerned on the following and will like your clarity on it;

1. Will users be able to encrypt their data to ensure that it remains private and secure, especially for sensitive files?
2. What file management features will be offered to enhance user’s experience. Example will users be able to create folder to store certain files together, will there be a search functionality to help in locating files easily, and file sharing among users?

Thank you for your questions!

Data Encryption: We’re exploring client-side encryption so files are encrypted before uploading to BTFS, ensuring only users can access decryption keys for privacy.

File Management Features:

• Folder Structure: Organize files easily with a folder-like system.
• Search: Quickly find files by name
• File Sharing: is currently in the planning stage. We are working towards implementing it in the future, ensuring secure, permission-based access for sharing files or specific versions.

[ines_valerie]

Thank you for you’re replying to me, please tell me as you grow very bigger how are you going to boost your operation to be able to handle a very big user base, thank you

[Chukseucharia]

Ok thank you for the clarification. I wish you the best in hackathon participation

[Okorie]

Base on your project value and goal please I have a question

• What approach will you take to ensure data integrity and also prevent dark force from tampering with or deleting user files.

[manfred_jr]

@Varun_Kapoor

Integrating multiple hardware wallets does come with some challenges, like making sure they work with different APIs and SDKs (like Ledger and Trezor), keeping the user experience smooth across all wallets, staying up-to-date with firmware updates, and ensuring everything stays secure. But with some careful planning and collaboration, we’re confident we can build a secure and easy-to-use solution for our platform in the future.

In case users lose access to their hardware wallet, do you have a recovery process in place that allows them to regain access to their platform account?

[Varun_Kapoor]

@ines_valerie

Thank you for you’re replying to me, please tell me as you grow very bigger how are you going to boost your operation to be able to handle a very big user base, thank you

Thank you for your question!

To handle a growing user base, we plan to:

• Use cloud-based infrastructure for dynamic scaling based on demand.
• Implement load balancing to ensure smooth traffic distribution.
• Continuously monitor and update the platform for efficiency as we scale.

These steps will help us maintain reliability and performance as we grow.

[Varun_Kapoor]

@Okorie

Base on your project value and goal please I have a question

• What approach will you take to ensure data integrity and also prevent dark force from tampering with or deleting user files.

Thank you for your question!

To protect user files from tampering or deletion, we plan to:

• Use BTFS for decentralized storage making it hard for any one person to alter or delete files
• Store file metadata on the TRON blockchain, ensuring it’s immutable and transparent
• Implement client-side encryption so only users have access to their decryption keys(Post Hackathon)
• Introduce version control to keep track of all file versions, preventing accidental deletions

[Okorie]

@Varun_Kapoor
Thanks for your response

[Varun_Kapoor]

@manfred_jr

In case users lose access to their hardware wallet, do you have a recovery process in place that allows them to regain access to their platform account?

Thank you for your question!

If users lose access to their hardware wallet, recovery will depend on the wallet’s seed phrase (12-24 words) provided by devices like Ledger and Trezor. We’ll remind users to store this securely, as it’s the only way to restore access.

We’re also exploring multi-signature solutions to offer more flexible recovery options, but our platform won’t store private keys, just guide users on these recovery methods.

[ines_valerie]

I must to confess that you are really doing very solid work, please tell me when you are doing your marketing campaign how are you going to be managing the spike in traffic, thank you

[manfred_jr]

This is really getting interesting further, exploring multi-signature solutions is a smart addition for added flexibility and your approach to user wallet recovery is thoughtful, particularly by relying on the hardware wallet’s built-in security features and seed phrase recovery.
There’s something that really bares to mind here, as users may use more than one device, how will you handle cases where one device is lost while others remain active? Will you support recovery from another authenticated device, or will users need to go through full seed phrase or multi-sig recovery?

[Varun_Kapoor]

@ines_valerie

I must to confess that you are really doing very solid work, please tell me when you are doing your marketing campaign how are you going to be managing the spike in traffic, thank you

Thank you for the kind words!
To manage a spike in traffic during our marketing campaign, we’ll ensure that our platform is scalable and prepared to handle high volumes of users. We’ll achieve this by:

1. Load Balancing: Implementing load balancers to distribute traffic across multiple servers, ensuring efficient resource usage and preventing server overload.
2. Performance Monitoring: Continuously monitoring our system to identify bottlenecks and resolve issues before they affect the user experience.
3. Caching: Utilizing caching mechanisms for frequently accessed data, which reduces load on the backend and improves performance.

[Varun_Kapoor]

@manfred_jr

This is really getting interesting further, exploring multi-signature solutions is a smart addition for added flexibility and your approach to user wallet recovery is thoughtful, particularly by relying on the hardware wallet’s built-in security features and seed phrase recovery.
There’s something that really bares to mind here, as users may use more than one device, how will you handle cases where one device is lost while others remain active? Will you support recovery from another authenticated device, or will users need to go through full seed phrase or multi-sig recovery?

Thank you for your insightful question!

Looking ahead, we plan to provide flexible recovery options for users who lose access to one device while still having others authenticated:

1. Recovery from Another Device: Users will be able to regain access through another authenticated device without needing their seed phrase, making the process quick and user-friendly.
2. Seed Phrase Recovery: If no other devices are available, users can always fall back on their seed phrase for recovery.
3. Multi-Signature Recovery: For those who set up multi-signature, recovery can be authorized with additional trusted accounts, adding an extra layer of security.

[ines_valerie]

Thank you for your reply to me and I really like how you reply, you put it line by line and make it easy for me to understand, please tell me in a case where you have a very serious problem about slow server responding or overloading issue how long works it take you to respond and to solve this problem, thank you

[manfred_jr]

Your plan of providing flexible recovery options is a significant step toward enhancing user experience and security.
How do you plan to raise user awareness about these recovery options?

[Varun_Kapoor]

To raise awareness about recovery options, we plan to:

1. In-App Guides: Provide clear, step-by-step instructions within the platform for recovery methods like hardware wallets, multi-signature, and seed phrases.
2. Tutorial Videos: Create videos to visually explain the recovery process.
3. Comprehensive Documentation: Offer detailed guides in the help section and on GitHub covering recovery options and security tips.
4. User Notifications: Send periodic reminders to encourage users to secure their accounts by enabling recovery options and backing up credentials.

[manfred_jr]

Way to go, thanks for the clarity.

[SaanviSeek]

@Varun_Kapoor

Project Website:

• [Coming soon]

This project is missing working MVP too. May I learn eligibility of this project too? @admin.hackathon @SimbadMarino

[adeel]

@SaanviSeek This project shows great potential. The team has put in a lot of thought and effort, and we’re excited about the concept. However, to be eligible for judging, we require a deployed application link so we can test and experience the project firsthand.

We really believe this idea has great potential, and once the app is ready to showcase, we’d love to welcome the team back in Season 8. We’re looking forward to seeing how this project grows!

[SaanviSeek]

Okay all clear @adeel thank you for explanation