Our Validators Post a Bond Worth Nothing, Because the Token It Is Denominated In Does Not Trade

The stake requirement described here is real code, and the economic security people assume it provides does not exist yet.

What a bond is supposed to do

A validator proposes and votes on blocks. Nothing stops it voting dishonestly except the cost of being caught.

The bond is that cost. Lock value up front, lose it on provable misbehaviour, and dishonesty becomes an economic decision with a known price rather than a free option.

The entire security argument rests on the bond being worth more than the attack. Not on the code that holds it. On its value.

Ours, stated exactly

There is a stake minimum, and it is enforced in code. A participant must lock 1,000 base units of our token before it can join the validator set. That check runs in the staking path on every attempt, it is not a document, and it is not aspirational.

And the token has no public distribution and does not trade anywhere. So the bond is denominated in something with no market price, which means the economic cost of losing it is zero.

What the requirement actually does is order participation inside a test network. It answers "who may join" deterministically. It does not deter anything, because nothing of value is at risk.

We would rather write that sentence ourselves than have it read as an economic guarantee. A stake minimum in a specification and a bond that costs something to lose are different claims, and only the first is true here.

And the set is four, operated by us

The design targets a committee of 21-of-100 validators. That is a spec. The running network is four validators, operated by one party, which is us.

So the bond deters nobody, and the participants are all the same party anyway. Either fact alone would make the economic security argument unavailable. Together they make it unavailable twice.

The consensus mechanism is real and it is not the thing in question. What is missing is the population it was built to secure and the value it was built to put at risk.

Why publish this

Because "stake-secured" and "proof-of-stake" appear in a great deal of material where the token is untraded, the set is internal, or both, and the phrase does exactly the work of implying economic security that is not present.

The distinction a buyer needs is between a mechanism that exists and a mechanism that is doing anything. Ours exists. On this network, it is not doing anything, and we would rather you evaluate us on what runs than on what the vocabulary suggests.

What to ask any chain about its validators

"What is the bond worth in a currency I can price?" If the token does not trade, the answer is zero, whatever the number in the specification says. Ours is zero.

"Who operates the validators, and how many parties is that?" For us: one, and it is us.

"What misbehaviour is actually detectable and penalised?" A penalty only deters what it can detect, which we cover separately.

"How many of these are running versus specified?" For us: 4 running, 21-of-100 specified and not deployed.

Where this leaves a decision

If your requirement is economic security today, we do not have it, the bond is real code denominated in nothing, and no reading of our specification changes that.

If you are evaluating whether the engineering will hold when the economics arrive, the mechanism is built, tested and model-checked, the gap is a distributed token and an external validator set, and we would rather name that gap in our own words than let the word "staking" imply it is already closed.