Every call the engine makes goes out to several machines at once. They work it out separately, and unless two thirds of them arrive at the same answer, nothing gets written at all.
Which means we cannot slip one in later, and we cannot take one out that aged badly. Anyone can go and read the whole thing, in order, including the parts we would rather you skipped.
What lands on the chain
A public record of what the engine decided is useful to everybody. A public record of what you did about it would be a liability with your name on it, so none of that goes anywhere near the chain.
Written down
The last one is a fingerprint, not the data. It proves what the engine was looking at without publishing it.
Never written down
Not held back, not encrypted, not stored somewhere safer. Never collected in the first place.
Why more than one
Any company can publish a list of its past calls. The list is worth exactly as much as your trust in whoever published it, which for a company selling you a trading product should be close to nothing.
So the writing does not go through us. The decision is sent out to staked machines we do not own, each works it out on its own, and their answers are compared. Two thirds have to match before anything is sealed. When they do not, nothing is written and the disagreement is the result.
That is slower than a database and more expensive than a database. It is also the only version of this where the record means anything, because it is the only version we cannot quietly correct later.
The rule is a fraction, not a count. Two thirds of whoever was assigned to the job have to agree. How many that is depends on how much of the network is available to put on it, so it might be two of three, or five of seven, or six of nine.
It has to work that way, because this network starts with two graphics cards on a desk. A rule that demanded nine machines would have been unenforceable on day one and would have quietly become a rule about something else. A fraction holds at any size and gets stronger as more capacity joins.
The number assigned is written into the entry alongside the number that agreed, so nobody has to take our word for how thin the verification was on any particular day. A receipt that only went to three machines says so.
market BTC/USDT
direction long
confidence 0.71
quant +0.62 v4.2.1
sentiment +0.31 v2.8.0
weights 60 / 40
inputs sha256:9f2c…41ab fingerprint only
time 2026-08-27T14:02:11Z
assigned 9 machines
agreement 7 of 9, needed 6
sealed 0xa73f…5d2eModel versions travel with the entry on purpose. When a model is replaced, old calls stay attached to the version that made them, so nobody can upgrade the engine and claim credit for what an earlier one got right.