Blog
Full blog post view.
Skalacoin
Posted: Apr 9, 2026 3:47 PM (UTC)
A bit of an odd one here.
Basically, as a bit of a challenge to myself, I wanted to reimplement the Bitcoin Client/Node in pure C, but it quickly went off the rails.
Whar?
It started like most of my projects. Just an idea that I got and thought to myself: "Hey, that sounds fun!". Unfortunately, like most of my ideas, it quickly turned into something way more complicated. Essentially, I started reimplementing the basic protocol of Bitcoin at the conceptual level in C. It started with small things like "Hm, I should change the Proof-of-Work difficulty system", then "Hm, I should change the block sizes", spiraling into me changing the entire Proof-of-Work system from SHA-256 into Autolykos2 with some weird-ass DAG scaling system and a completely redefined economic system.
Concept?
Basically, I decided to try and devise a "Public/Private, Balance-based, ASIC-resistant, Inflationary cryptocurrency". Let me try to explain these.
Public/Private
The system supports both public and private transfers, crossing them included. So your transactions can be both public or private, depending on what you want.
Balance-based
Address balances are stored as numbers directly, not UTXOs, meaning that your balance can be fetched instantly.
ASIC-resistant
The Autolykos2 hashing algorithm for Proof-of-Work essentially means that it's economically illogical for people to develop ASICs for it, leaving the ability for anyone with a GPU (provided enough VRAM) to mine coins.
Inflationary
Before you get scared, this basically means that the economic system prints a bunch of coins at the start of the chain (Monero-style emission). In about ~6.5 years (off the top of my head, I should recalculate this), about ~18.4 million coins will have been printed, and from that point, the reward will be set each year to target a 1.5% yearly inflation rate. This should provide a constant rising incentive for miners. Also compared to fiat, this rate is tiny (USD is like ~2.8%/year), and it's static, meaning it's hardcoded as the rate, no adjustments.
So yeah. I'm like 80% there with the actual implementation in C (just as God intended) and then I need to write a whitepaper for it.
Also I already registered domain for it, website (in progress) accessible here.