Private Monetary Infrastructure / Testnet Phase
A trustless, private monetary network. Built by one developer. No venture capital. No compromise.
The Problem
Three decades of digital money experiments. Three fundamental failures nobody wanted to admit.
Making every transaction visible to everyone was called innovation. It was surveillance with a different logo. A public ledger means every employer, government, and stranger can trace exactly where your money came from and where it goes.
When the top 10 wallets control the majority of governance votes, you haven't removed central authority. You've just changed who holds it. Voting on protocol rules is not decentralization — it is politics by another name.
A monetary supply that can be changed by a vote is not a supply limit. It's a suggestion. The entire premise of sound money collapses the moment enough stakeholders can agree to change the rules that protect you.
A Different Approach
Four properties. Each one unbreakable. Not by design preference — by mathematical enforcement.
Every transaction is private — enforced cryptographically at the protocol level. There is no transparent mode, no optional disclosure setting, no "compliance mode" that can be enabled by a future governance vote. Private is the only mode.
No team, no multisig wallet, no governance committee, no emergency council can override the protocol. The rules are expressed in mathematics. Mathematics does not hold meetings or accept pressure.
The maximum supply is embedded in the protocol itself. It cannot be changed by vote, by emergency, by upgrade, or by any other mechanism. What is issued is what will ever exist. Full stop.
No oracle feeding external data. No bridge depending on a federation. No sequencer operated by a company. No ceremony. No assumption that someone, somewhere, did the right thing and deleted something they should not have kept
Scalar doesn't ask you to trust us. It was designed so that you never have to.
Truth by Mathematics, Not by Majority.
Governance by Genuine Operation, Not by Stakes.
Hardened by Determinism, Secured by Analysis.
Progress
No public testnet numbers yet — only a complete specification and a functional local implementation. The testnet is not a demo. It is a destruction test. We are actively trying to break the protocol so that no one else can. Nothing ships until this phase produces no surprises.
Live network metrics will be published here when a public testnet is running. Until then, no numbers are shown — because no honest numbers exist yet.
The Builder
Every project that has taken VC money has eventually made decisions in favour of its investors. This is not speculation — it is the mechanical consequence of capital with return expectations. Scalar was built alone because the only way to guarantee no one else's interests can shape the protocol is to ensure no one else has a financial claim on it.
Solo development means slower shipping. It also means no co-founder with a different vision, no investor board applying pressure on timelines, no marketing team adding "features" to make a pitch deck more compelling. Every design decision made on Scalar has been made for one reason: correctness.
I have no intention of introducing a team. When this ships, it will ship because the mathematics holds — not because a funding runway forced a launch.
The Full Journey
From a first-principles idea to an audited specification in under 60 days. Every version existed because the previous one had a flaw worth fixing.
Version numbers reflect specification revisions, not software releases. Each one represents a deliberate decision to get something right before moving forward.
Not a feature request. Not an improvement on an existing chain. The starting point was a question asked from scratch: what would a monetary network look like if you refused to inherit the fundamental assumptions that make every current network weak? The answer required building something 180 degrees different from the majority of existing decentralised projects.
The first version established the core monetary model. The challenge was designing a supply schedule that allowed large participants to accumulate value without monopolising the network against ordinary users. The answer was a psychologically calibrated supply ceiling and a decade-long maturation window to ensure early stability rather than early speculation.
A serious flaw emerged: if transaction fees were burned, rational participants would stop transacting and simply hold. A network where no one transacts is a dead network. The solution was a two-phase monetary evolution — an initial passive deflation phase followed by a permanent fixed supply phase — keeping the network alive by volume rather than by burning.
The initial asset distribution model was unfair. Free airdrops at launch reward speculators, not participants. The decision was made to distribute assets purely based on demonstrated participation — earned by doing, not by arriving early. At the same time, the maximum supply was locked permanently. And the founder allocation was eliminated entirely.
The hardware requirements were too high for true decentralisation. But reducing them naively creates a different problem: low-cost attackers. The resolution was elegant — make attacking the network require so much investment that rational attackers have more to lose by attacking than by participating honestly. Power is measured by demonstrated commitment to the network, not by computing power owned.
A critical vulnerability was discovered: the method by which nodes synchronised their view of the network contained an internal arithmetic contradiction. Under certain conditions, different nodes could reach different conclusions — not from an attack, but from the design itself. The entire synchronisation method was replaced with one that is locally computed, deterministically bounded, and mutually verifiable without any bias.
Any future application built on top of Scalar — wallets, tools, integrations — could, if carelessly designed, modify or weaken the core protocol layer. The protocol and the application layer were formally and permanently separated. Third-party developers can build on Scalar without ever being able to touch its foundation.
The key derivation system — how access credentials are generated from a passphrase was vulnerable to brute-force attacks using high-performance hardware at scale. The system was replaced with one where the cost of attacking scales with the attacker's ambition. The more attempts an adversary makes, the more it costs them in a way that cannot be parallelised or accelerated by throwing more hardware at the problem.
Using wall-clock time to determine network period transitions created an attack surface: an adversary with control over timestamps could manipulate the network's sense of when one period ends and another begins. Period transitions were redesigned around an internally verifiable reference that cannot be manipulated by any external party. The historical data storage system was also simplified, and a minimal emergency signal was added for nodes that become temporarily disconnected.
A large consolidation pass. Communication pathways between nodes were over-engineered and inefficient. The authentication method in use was consuming more space than the security requirements justified. The governance decision process had accumulated unnecessary complexity. Everything was stripped back to the minimum that still satisfies the security requirements — nothing more.
An independent cryptographic audit identified four vulnerabilities in the specification. Three were identified, reproduced, and closed at the implementation level before this version was finalised. The fourth requires live network conditions to evaluate and remains open pending public testnet deployment. The specification is now the single authoritative document for all further implementation.
The specification document was stripped of version numbers, release labels, historical change notes, and any language implying a previously active network or existing users. A procedure was established: audit findings are absorbed into the document text rather than appended as amendments, and the implementation follows the document — not the reverse. What remains is one clean document that serves as the genesis reference for the first implementation of Scalar.
A full audit of the repository against the consolidated specification identified nine points where the implementation had drifted from the document. All nine were corrected. Two annotation errors in the specification were also found and fixed. Every constant that the protocol treats as permanent now lives in a single authoritative location — no module may define its own copy. All 1,400+ unit tests pass against the aligned codebase.
A network-wide improvement plan was formalised targeting the three primary performance dimensions without altering the protocol's foundational constraints. Transaction data efficiency can be increased by up to 75%, finality latency reduced by over 99%, and total network throughput lifted by up to 100×. Selected supporting components are now entering a dedicated security‑research phase before integration approval.
A full-spectrum audit revealed that the specification contained statements it did not enforce and formulas it could not fully define. Principles were declared at the top of the document and silently violated lower down. Some symbols used in critical distribution calculations had never been assigned a definition — meaning two independent implementations could produce divergent results with no way to determine which was correct. The document has now been brought into alignment with itself. Every declared prohibition is enforced. Every symbol is defined. Every procedure handles its edge cases. The specification is no longer a document that mostly means what it says — it means exactly what it says, all the way through.
No calendar dates. It ships when it is right.
The specification is complete and the local implementation is functional. The current work is hardening: running the system under adversarial conditions, expanding the test suite, validating that every security property holds not just in theory but under real pressure. Nothing ships until this phase produces no surprises.
When the implementation is stable enough to withstand external scrutiny, a public testnet will be deployed. This is when live network metrics will appear on this page for the first time — because that will be the first time honest numbers exist.
Establishing the parameters for independent participants to operate network nodes. No central operator. No foundation-controlled majority. The network exists when others run it, not before.
User-facing software built on the isolated application layer — the one that cannot touch the core protocol by design. Privacy-first from the interface down.
Public launch when all prior phases pass their exit criteria. No date is set. No date will be set until the network has proven it can withstand what the real world will do to it. A premature launch is not a launch — it is a liability.
Support
No venture capital means no investor pressure on timelines, no governance rights sold to funds, and no obligation to deliver returns. It also means development depends entirely on people who believe this work matters.
Private by default. Every transaction untraceable by design. The most philosophically aligned way to support a project built around financial privacy.
Scan to send XMR
Questions
Direct answers. No spin.