Hey, maker here. I built LapseCoin because Bitcoin's proof-of-work ties reward directly and unboundedly to hash rate, which is what pushed mining from CPUs to GPUs to ASICs and drove a huge energy bill along with it. A Verifiable Delay Function ties block production to real elapsed sequential time instead, with a much smaller hardware-advantage gap: roughly 3-10x measured on real hardware (from Chia's own 2019 competition on the same VDF construction), not the 10,000x+ gap ASICs opened up. The approach changed a lot as I worked on it. I originally assumed a balance-weighted tie-break was needed to stop one operator running many builder addresses from gaining an unfair edge. Simulated it properly instead of assuming, and found it isn't needed: running many addresses at the same hardware tier already wins exactly proportionally, and splitting one machine's throughput across addresses is actively worse than running it as one. That's now written up in the whitepaper with the actual numbers, not just asserted. No premine, fair launch. I'd genuinely value people trying to break the consensus mechanism more than people trying to use the coin, tell me where it's wrong.

Lapsecoin

A cryptocurrency secured by a VDF instead of proof-of-work

A cryptocurrency secured by a VDF instead of proof-of-work