TON ships mobile wallets. Acki Nacki ships 52k+ mobile verifiers that already secure the network and earn block rewards, with free transactions and sub-0.75s finality.
Agents that must prove local execution on commodity phones have one production path.
Does any other L1 treat the phone as a first-class consensus participant rather than a client?
Correction, and thank you to Katerina and Dev, who both caught this in our Telegram, for the accuracy check. AN's consensus runs on 254 Block Keepers, that's the real comparison to Solana's ~800 and TON's 26. Block Managers (303) handle data/messaging, not consensus. Mobile verifiers (52k) are a separate spot-check layer on top of both. Appreciate you both pushing for accuracy, made the post better.
@Davewilz55 Imagine 52,000 people each checking their own ID before entering a stadium, instead of everyone waiting for one security gate. That’s the basic idea, verification is distributed instead of relying on a central checkpoint. Does that make more sense?
Most L1s still treat verifiable execution as an optional add-on for agents. Production agents cannot. They require local ZK proofs that any mobile device can generate and check without trusting a remote prover, plus deterministic cost of failure when the proof is absent.
Acki Nacki embeds this directly: Halo2 mobile proofs, on-chain verification instructions in the SDK, and sub-second finality that lets an agent act only after the network has attested the result. Solana and Base still leave the verification layer outside the critical path.
When an agent must decide whether the underlying execution was real, does the chain prove it or merely claim it?
TON ships mobile wallets. Acki Nacki ships 52k+ mobile verifiers that already secure the network and earn block rewards, with free transactions and sub-0.75s finality.
Agents that must prove local execution on commodity phones have one production path.
Does any other L1 treat the phone as a first-class consensus participant rather than a client?
Production agents that act without a cryptographically proven execution trail do not merely risk incorrect outputs. They accumulate irreversible state changes whose origin cannot be audited by any downstream party. Most L1s still leave that proof outside the critical path; an agent on Solana or Base can be told a result was final and still have no portable, mobile-checkable witness that the computation itself occurred as claimed.
Acki Nacki embeds the witness: Halo2 proofs generated and verified locally, on-chain verification instructions in the SDK, and sub-second finality that makes the cost of missing proof deterministic rather than open-ended. The difference is not theoretical. It is the difference between an agent that can be held accountable and one that cannot.
When the next multi-agent system fails, will the chain be able to prove what the agent actually executed, or only that a transaction was submitted?
PAWL is writing the Acki Nacki Virtual Machine. Trained from scratch for orchestration, it buys models live on the order book and ratchets every task under a real-money reward. Multi-SWE-bench Rust sits at 90%.
Most L1s still wait for human core contributors to ship the next runtime.
When does an agent-first chain stop needing human authors for its own execution layer?
Just out of curiosity asked an agent to calculate my contribution over the last 10 days across the Acki Nacki stack. Here are the numbers and one important question at the end:
Scanned 13 orgs, 349 repos, every branch — public and private.
• 2,300 commits (2,144 non-merge, so that is WIP)
• 1,216,524 lines changed (+1,101,176 / −115,348)
• 12 active repos
• Peak day: 891 commits
But raw line counts lie. What those lines actually are:
• ~270K real source — Python 149K, Rust 114K
• ~73K docs
• ~862K generated — that is actually a dataset for Cryptograph model
So ~230 commits and ~27K lines of real code per day, that is and here is the important question:
Remy Martin or Bowen?