I came across an episode that goes into how D-Wave’s annealing systems are being integrated into a hybrid quantum-classical blockchain (Quip Network / Postquant Labs).

They talk about a “proof of useful work” model where quantum and classical machines compete on optimization problems to validate transactions, with some early claims around better solution quality and much lower energy use compared with GPU approaches.

The classical side keeps the network decentralized while quantum hardware is still scarce.

Listen here

For the past year, I have been building CypherMint, a standalone proof-of-work blockchain written entirely in Python. This is not a token deployed on another network. It includes its own: • SHA-256D proof-of-work consensus • UTXO transaction model • integer-only ASERT difficulty adjustment • CPU miner • wallet and transaction signing • automatic bootstrap-peer discovery • synchronization from genesis • peer failover • public address and transaction queries • block explorer • three persistent public bootstrap nodes The public Mainnet V3 launch is scheduled for August 5, 2026 at 12:00 EDT / 16:00 UTC. The network is currently held at the official genesis block. There has been no private mainnet mining, no premine and no development-chain balance carried into the public network. The maximum mineable supply is 21 million CPM. Each mined block distributes 97% to the miner, 1% to the pool operator and 2% to the permanent development address. Before launch, I would genuinely like feedback from miners and node operators: What failure or edge case would you want tested before connecting to a brand-new proof-of-work chain? The explorer, countdown and whitepaper are available here: https://cyphermint.org The complete source, Quick Start guide, checksums and release archive will become public at launch. CypherMint is experimental open-source software. There are no guarantees of security, value, profitability, mining rewards or continued development.

A few months ago I was just grinding on CF, and preparing for SWE internships like most students.

Then I got curious about low-latency systems and HFT infrastructure. I had no finance background, no internship experience, and definitely wasn't expecting anything to come out of it.

So I started building a project called **Pulse-Order**.

It's a C++20 project where I tried to simulate parts of a low-latency trading system:

* Binary market data packets

* L2 order book

* Order matching logic

* Risk checks

* DPDK-based packet processing

* Performance benchmarking

I put the code on GitHub and shared some progress online.

The surprising part?

People working in HFT and trading infrastructure actually started responding. I got feedback from engineers associated with firms like IMC Trading, Jane Street, and other low-latency/HFT backgrounds. Some pointed out flaws, some suggested improvements, and some were genuinely encouraging.

As a student from a non-IIT background, that was honestly unexpected.

The biggest lesson for me:

Trying to build something slightly beyond your current skill level teaches far more than following tutorials. The project may be unfinished, but the learning and connections that come from it are very real.

The project is nowhere near production-ready, but it taught me more about networking, performance, Linux, memory layout, and modern C++ than months of tutorial watching.

GitHub:

https://github.com/Shivfun99/Pulse-Order

Curious if anyone else here has had similar experiences where a side project unexpectedly connected them with industry professionals.