Hacki
About the project
TreP2P is a peer-to-peer file and sensitive data transfer tool designed for situations where information should not pass through third-party applications, cloud storage services, or centralized servers.
The project focuses on enabling direct transfers between two users. The sender only needs to select the file or sensitive information they want to share. TreP2P then generates a unique code that the receiver uses to establish the "transfer channel" and obtain the information required to decrypt the transferred content.
This approach reduces the need to upload sensitive information to an intermediary platform before it reaches its destination. Instead, the transfer is designed around a direct peer-to-peer workflow, making it especially suitable for confidential files, credentials, secrets, tokens, internal documents, or other information that users may prefer not to store temporarily on third-party infrastructure.
From the user’s perspective, the workflow is intentionally simple:
- The sender selects the file(path).
- TreP2P generates a unique session code.
- The receiver enters that code.
- The code is used as part of the process for establishing the communication channel and securely recovering the transferred content.
- The data is transferred directly between peers rather than being uploaded to an intermediary cloud service.
How We Built It
The project was developed collaboratively by a three-person team with the support of AI coding agents. We first defined the core idea, technical scope, expected workflow, and responsibilities of each component. Once the architecture was established, the work was divided into parallel tasks so that different parts of the application could be implemented simultaneously.
The agents were used as development assistants to help us structure tasks, troubleshoot implementation issues, and accelerate the development of individual components. The final architecture, integration decisions, testing, and project scope were managed by the team.
During development, we encountered integration and merge conflicts while combining work through GitHub. To avoid introducing unstable changes into the main branch, we temporarily moved to a more controlled integration process: changes were reviewed and merged locally, the complete application was tested as a single working version, and only after validating the integration was the consolidated version pushed back to GitHub.
This development process allowed us to continue working in parallel while maintaining control over the final integrated build.
Only available on Windows: pear install pear://gtzdz48poxtdczfm9sihz7968suigmn61gw9b6uo1qgdskxhn7zy