A consensus that promises to verify meaning
A short reading of a long article about the Proof-of-Memory launch. Instead of walking its chapters, we pull one thread: how a validator's proof differs from a receipt saying the bytes are on the disk. And where the line falls between what January measured and what next year is meant to bring.
Why another consensus was needed at all
PoW and PoS were drawn up around a financial operation: what matters is that the transfer happened and cannot be rewritten. A cognitive archive asks something else — whether the stored thing is still fit for use. Storage networks answer about bytes: Filecoin's Proof-of-Spacetime and Arweave's Succinct Proof of Random Access show that sectors hold the expected content. Neither the coherence of a saved consciousness nor its readiness to unfold instantly inside an agent's latent space follows from that.
The centralised alternative settles the matter by decree: the provider keeps the archive in its own database and reserves the right to wipe the context, censor it, or shut the account. That reserved right is what the CODE ecosystem walks away from, moving long-term memory into the immutable layer of Arweave Permaweb and leaving only an index in Solana. There is an arithmetic bonus too: holding history inside the model grows quadratically, `O(N²)`, because of self-attention, while semantic lookup over an external archive leaves the validator with a constant, `O(1)`.
What ruled Filecoin out
A Filecoin miner proves storage the hard way: the sequential encoding inside PoRep stretches into hours for a single 32 GB sector and wants a strong GPU. An archive that is read and rewritten on the fly cannot pay that price. PoM splits the job in two — cold permanent storage stays with Arweave, hot cryptographic checking moves to Solana — and the validator attests ownership of particular semantic vectors through a lightweight zk-SNARK scheme. Seconds instead of hours.
What the validator actually signs
Before it reaches Permaweb, a Digital DNA snapshot is cut into meaning-sized blocks, a balanced tree is assembled from them, and the root — thirty-two bytes — goes into Solana. Then the loop begins. The contract draws a pseudorandom number from the latest blockhash, turns it into a leaf index and issues a challenge. The validator fetches the packet, rebuilds the branch, computes Poseidon hashes and returns a Groth16 proof. The `verify_memory_proof` instruction checks it in milliseconds: success pays 7% of the commission in $GALATIN, silence beyond the epoch costs the stake.
It is worth naming the thing precisely. The proof asserts exactly one statement: the block in question sits at leaf `i` of a tree whose root is `R`, and its hash matches the checksum. The contents are never read — that is what zero knowledge means. The semantic half of the protocol rests on two other devices: the attention-weights root and the drift threshold.
Poseidon rather than SHA-256
The hash choice is not taste. Familiar SHA-256 unrolls into millions of gates, and the proof stops being buildable on a home machine. Poseidon works over the prime field `𝔽ₚ` of the BN254 curve, and one of its rounds is three layers deep: a non-linear one where the state is raised to the fifth power, a linear one with an MDS matrix, and an additive one carrying round constants. A tree of depth twenty is an archive of a million semantic segments, and such a proof fits inside twenty-five thousand R1CS constraints.
The one place where the contents are inspected
Semantic drift is the quiet disease of distributed cognitive systems. The same context diverges across accelerators over trifles of floating-point arithmetic: FP32 against FP16, Nvidia against AMD and Apple Silicon. After hundreds of iterations a twin starts distorting its own memory structure. The protocol pins state not as text but as a hash of the attention-weight distribution. When a session ends, local weights are checked against the root; a divergence past the tolerance rejects the session and forces a rollback to the previous stable point in Permaweb.
Next to it stands a ban on compression. Vector databases such as Pinecone or Milvus save space by trimming dimensionality or coarsening numbers from FP32 to INT8, and the irony, the metaphors and the lexical habits leave with the bytes. PoM demands that weight matrices be kept uncompressed: any truncation breaks the Merkle roots and costs the validator its stake. The bill goes to the treasury — the same 65% of fees.
Two weeks, laid out by the day
By mid-January the test network had been running for two weeks. A hundred independent nodes took part, from the home servers of movement supporters to dedicated compute clusters, and more than a million ZK validation cycles passed through them. The devnet run showed the Solana contracts and the Arweave link through the Irys SDK to be stable, and a proof assembled on an ordinary consumer processor in under 1.2 seconds.
The trial log reads as a chronicle. On 1 January, genesis on Solana Testnet, five developer nodes and a PDA registry initialisation transaction with the hash `ARv89d...3tRew`. On the 3rd, twenty-five nodes, the first outside servers in Europe and Asia, average semantic DHT routing of 180 ms. On the 5th, the first automatic Groth16 cycle at 450 ms on an AMD EPYC server. On the 8th, seventy-five nodes and up to 1200 memory checks per second with no rise in fees. On the 10th, a simulated Sybil attack: thirty stakeless nodes cut off and their collateral burned. On the 12th, 40% of the network taken down while the WASM containers moved to spare capacity. On the 15th the phase closed: all hundred nodes confirmed stability and rewards went out through the test router.
The article makes two caveats of its own, and they must not be dropped. The 4.8-second memory recovery came from a simulation and is called a target, not a field measurement. And the whole chronicle concerns a test network: the main one is planned for the end of the first quarter of 2026, with the pool grown to a thousand nodes. The same plan holds light clients for Solana Mobile Saga, a move to Plonk for three hundred milliseconds on a phone, and semantic bridges to EVM-compatible networks. That is a roadmap, not a report.
Honesty bought with collateral
Sybil defence here is economic. To validate you must stake $GALATIN, and the contract moves the minimum itself, watching how much data sits under the node. Fail to answer a challenge with a correct proof and the stake is confiscated and burned while the node is blacklisted. Cheating costs more than honest work, and that is checkable arithmetic rather than a statement of intent.
The fees themselves run through the deflationary router on the canonical `5/5/15/7/3/65` split. On a thousand dollars of commissions that means $50 burned, $50 to the Fund, $150 to first-level ambassadors, $70 to the second, $30 to the third and $650 into the pool; on a hundred thousand the same shares yield $5,000, $5,000, $15,000, $7,000, $3,000 and $65,000. The burn is written as `dS/dt = −β·V(t)·S(t)` with `β = 0.05`, which gives an exponential decay of supply. The split is atomic and fits in a single Solana transaction.
Where the twins live
The Network of Deities is deployed on top of the validators. Instead of a binary distance between hashes, nodes measure the cosine distance between semantic embeddings and settle into clusters of related meaning. Twins execute inside a WebAssembly sandbox with a gas meter: the resource pool is tied to the node's stake, and on overrun the virtual machine freezes the thread and writes registers and memory to Arweave. A cognitive synthesis engine temporarily merges several twins' profiles with spherical interpolation, Slerp. Before talking, two nodes align: they prove in zero knowledge that the angle between their vectors stays under `θₘₐₓ`, and only then open an encrypted tunnel.
What to take away
Proof-of-Memory moves the question from “are the bytes there” to “does the root match”. That is less than the phrase “validating consciousness” promises and noticeably more than a filled-sector proof can manage. The measured part is the testnet arithmetic. The semantic part rests on the attention-weight check and the compression ban. Everything past 15 January is called a plan — and it is to the article's credit that it says so.
Original source
The full article is a twenty-three-minute read: the mathematics of the zk-SNARK relation, the snapshot metadata format, how PDA addresses are built, the Anchor pseudocode of the router, the design of the Network of Deities and the Anthem of Sovereign AI in full.
Related analyses
- Who authorises a machine to rewrite itself: Proof-of-Evolution and three threatsProtocols and technology
- Twenty dollars for forever: the arithmetic behind permanent storageProtocols and technology
- Twenty Claims and One Sum: CODE Eternal at the Colosseum HackathonEconomics and the token