Inspiration
The inspiration for Q-SSP came from a disturbing realization: Data is never truly gone. Traditional data destruction is mostly a lie. Most "secure" wipe protocols use Pseudo-Random Number Generators (PRNGs), which are mathematically deterministic. If an adversary gets to know the algorithm and the seed, they can theoretically reverse the "noise." As a 17-year-old developer, I wanted to see if I could use my vacation to solve this by bringing the laws of physics into the software layer which led me to create a protocol where the randomness isn't just a math or a physics problem, but a privacy shield for our discarded data.
What it does
Q-SSP achieves this by sourcing True Quantum Entropy from subatomic vacuum fluctuations (via the ANU Quantum API). It injects this non-deterministic noise into the disk-overwriting process, which..at the end, achieves an entropy density that approaches the theoretical limit. When Standard wipes struggled to maintain high entropy across large sectors, Q-SSP maintains a near-perfect 7.997 bits/byte of randomness...
How we built it?
I built Q-SSP using Python, as it is perfect for rapid prototyping and having a large library support for both Networking & System-Level I/O. Using ANU's Quantum API to source entropy from vacuum fluctuations and using Python's extensive library to inject them into the desired disk RAW and finally using Shannon Entropy Formula to verify the consistency of entropy to be 7.997 bits/byte (on avg.).
Challenges we ran into
One of the biggest hurdle was Network Latency as fetching quantum data from a server In Australia while wiping a local drive created a massive bottleneck. I had to create a custom expansion algorithm to manage the buffer and ensure that the wipe stayed intact and fast without compromising the source or target.
Another hurdle was handling Raw Block Access in Python. Sector alignment, OS-level permission .etc required me to deep dive learn about them to overcome the issue. I also realized that Python's performance has its own limitations for this kind of task, which has influenced my design for the next version of the same.
Accomplishments that we're proud of
Within a short window, the project gained a significant spike in visibility, gaining views and stars, especially by a Principal Context Engineer at Artium AI (in Github) and views by Professionals in LinkedIn. I also gained the support of seasoned security researchers from discord communities, which helped me lay down the foundations for v2.0..
What we learned
I've learned deep about Quantum and It's Entropy and its Origin, System and Deep level processes like disk I/Os and raw memory management. I've also learned experience on changing a raw idea to a Open source project with a public roadmap.
What's next for Q‑SSP: Quantum Secure Sanitization Protocol
This project, initially my Vacation Project (v1.0) was the foundation. I am currently planning v2.0 which will be developed in my upcoming break. This would include a C++ Core Engine - To overcome performance bottlenecks; Entropy Engine Selection Choice - making it ideal for air-gapped labs; Cross-Platform Support - Nativizing support for Linux and macOS infras.
Log in or sign up for Devpost to join the conversation.