Wtf is Motoko

Dude, you sum up your kind. Rather than answer the points directly, you respond like the filthy money-gribber you are with ad hominem attacks on me, DFINITY and the ICP community. You even use how the ICP price, manipulated on FTX, dropped at launch in 2021, aligning yourself with, and promoting, the work of serious criminals who are in jail. Take a look in the mirror. You're sad.

I ran Bons thread through Gemini Argon on High. For those interested here is what Gemini says: Justin Bons gets the core numbers right, even if his framing is aggressive. His breakdown exposes a real gap between how DFINITY markets network activity and how the rest of the blockchain industry measures transactions. At the same time, parts of his critique overlook why the Internet Computer Protocol (ICP) records internal activity differently than monolithic chains like Ethereum or Solana. 1. The 6,000 TPS Headline Figure and Read Queries The Claim: DFINITY reports over 6,000 transactions per second (TPS) on its official dashboard, but roughly 4,000 of those are read only queries. The Reality: This claim is accurate. The headline counter on the ICP dashboard (which sits around 5,890 to 6,070 TX/s as of October 2026) combines state changing update calls with read only query calls. On ICP, a query call reads data from a single node without going through consensus or modifying the ledger state. Every other major blockchain handles read requests through off chain RPC nodes (such as an eth_call on Ethereum) and never counts them as transactions. Bundling read queries into a headline transaction metric inflates the number and makes direct comparisons with other networks misleading. 2. The 2,000 Update Calls vs. 0.4 User TPS The Claim: The remaining 2,000 TPS consists of internal application steps like contract to contract calls, replies, timers, and heartbeats. Once those are removed, actual user transactions sit between 0.4 and 0.7 TPS. The Reality: The math is accurate, and it highlights a fundamental architectural difference in how blockchains define a transaction. On Ethereum or Solana, a user transaction executes synchronously inside a single atomic block. If a user calls Contract A, and Contract A calls Contract B and receives a response, that entire chain of events counts as one transaction. ICP uses an asynchronous actor model where smart contracts (canisters) pass messages to each other across independent subnets. Because these steps happen asynchronously across different consensus rounds, ICP tracks each execution step as a separate update message: * Ingress messages: External transactions signed and submitted directly by users. This is the direct equivalent of a standard transaction on Ethereum or Solana. Filtering strictly for ingress messages and token ledger transfers brings ICP down to roughly 0.4 to 0.7 TPS. * Canister to canister calls: When one canister sends an instruction to another canister, the network processes it as a distinct consensus message. * Replies and callbacks: When a called canister finishes its work and sends data back to the first canister, that reply is also processed as a separate update message. That is why replies alone account for more than half of all update traffic on the network. * Timers and heartbeats: ICP canisters can execute scheduled code automatically on every block (heartbeats) or at set intervals (timers) without an external user triggering them. Bons is right that comparing 2,000 internal execution messages on ICP to 2,000 user signed transactions on Solana is an apples to oranges comparison. Calling those internal messages completely fake, however, misses a key technical detail. Every inter canister call and timer runs through subnet consensus, mutates state, and pays for compute cycles. On Ethereum, smart contracts cannot wake themselves up, so protocols rely on external keeper bots (such as Chainlink Automation) to submit transactions that poke the contract. Those bot pokes count as user TPS on Ethereum, whereas ICP handles them natively at the protocol level through timers. 3. The 2022 Developer Forum Incident The Claim: In 2022, a developer running less than one database upload per second generated 1,300 TPS on a subnet because each upload triggered 3,000 internal messages.

The cycles you are buying are created from ICP (i.e. when you pay using your cc, behind the scenes, you are buying ICP, that's being transformed to cycles). This is a convenience layer over the decentralized network that removes token processing friction for mainstream users.