Veridium Network: Innovations and Challenges in Consensus Mechanisms

Hey all! Just diving into the world of crypto and wanted to share a bit about myself. I was a total Bitcoin nut back in 2010, spent hours learning everything I could. After some time, I sold my coins and moved on. Recently got into ETH and other coins, but nothing beats that rush of being there at the start.

Glad to see you back! Anyone from 2010 designing consensus in 2026 is in the right place. Just watch out for the jump from simulation to real-world mining; that gap can be a killer. There’s a ton of factors like network issues, implementation quality, and hardware quirks that can mess things up.

Thanks for the welcome! It really drives me to keep pushing forward. I get your point, security is tough. Cryptography is a whole other level. I know I need to explore networking privacy more, maybe look into a Dandelion++ setup like Monero.

Quick update: spent the day coding and working on some charts and policies. Just released version 3 of my whitepaper to match the binary ledger format. Some highlights: - Can now derive up to 256 sub-keys for multi-core CPU mining - Partially working aggregated STARK proofs over VDF and ledger state - Binary native ledger is live with HorizonTree - Switched over Probe is binary native - Identity DDA now focuses on lease density instead of entry speed.

So I finally picked a name for my project and registered domains everywhere. Introducing: Veridium Network by Anosic Systems! Veridium means "green mineral". Green is my fave color, and it kinda ties into mining too. Anosic stands for "healthy". My aim is to tackle the crazy incentives from PoW consensus.

I nailed the STARK field alignment today! It was tough getting everything to sync up, but I managed to unify VDF, Identity, and Ledger with a specialized witness index. Now Veridium has three proof segments within a single oracle setup.

Almost hit a wall today. Tried compressing the ledger using recursive STARK aggregation, but the size exploded from 10 KB to way too big. Found a workaround that cuts it down to about 20 KB, but miners would need tons of RAM for proofs. Thought about quitting but found a new dual-PCS strategy instead.

Back with updates on the dual-PCS compression! The gossip cert is stable at 20.70 KB. The breakthrough was separating security parameters from the proof system. Now the Master Verifier works with a 256x expansion factor with 12 queries, all set for speedy network sharing.

Not gonna happen. Competing with powerful hardware is impossible.

Maybe it can work. That’s why I’m here. Not just to spread negativity. Veridium is different. I’ll explain how soon, but right now I’m deep in R&D.

Previously mentioned the need to strengthen VDF, Identity, and Ledger arithmetics. I was worried about gate count inflation messing things up. Twenty days later, those concerns were valid. The last few weeks have been brutal; I’ve been on a cryptographic rollercoaster.

I've been swamped and tired lately, but I wanted to share an update. I really believe Veridium is onto something groundbreaking; it might end up being the most innovative blockchain since Bitcoin. So who knows, maybe these updates will matter to someone someday.

The struggle continues. Still tackling tough issues with subtle causes that are tricky to diagnose. Here’s a quick recap of what’s been up: Switched from Binius v0 (stale fork) to Binius v0 (HEAD) with 53 tests, all passing Picking up some Binius M3 primitives and focusing on formal verification Expanding circuit coverage with Kani Current status: gearing up for recursion assembly.