Justin is arguing from a ledger-chain maximalist frame. ICP is a decentralized cloud / world-computer architecture. If he evaluates ICP only by whether it looks like Solana, Sui, or a conventional shared-security L1, he will keep missing the thing that makes ICP important.
That is not a small mistake. That is the entire failure of his critique.
At this point, there are only two explanations: either Justin does not understand the value of ICP’s architecture, or he does understand it and is choosing to frame it in the most damaging way possible because ICP threatens the narratives behind the chains he prefers.
Neither option makes his critique trustworthy.
ICP is not trying to be Solana with different branding. It is not trying to be Sui with canisters. It is not trying to win the narrow race of “fast token ledger with smart contracts.” ICP is trying to replace major parts of the traditional cloud stack with decentralized compute, storage, web serving, governance, threshold cryptography, cross-chain signing, and full-stack on-chain applications.
That is the big picture Justin avoids.
Instead, he zooms in on ICP’s design choices, strips away the reason they exist, compares them to the assumptions of ledger chains he already likes, and then presents the result as if ICP has been exposed.
That is not technical honesty. That is either ignorance or selective framing.
His “ICP should switch to sharding” point is a perfect example. ICP already scales horizontally through subnets. A subnet is an independent blockchain within the Internet Computer that runs consensus, executes canisters, stores state, communicates with other subnets, and helps the network scale. So the real complaint is not that ICP lacks sharding. The real complaint is that ICP does not use Justin’s preferred shared-security model.
Fine. Say that.
But do not pretend a different engineering tradeoff means ICP is centralized, insecure, or scammy.
The node-count argument is even worse. Node count is not decentralization. Independent control is decentralization. In proof-of-stake systems, voting power comes from stake, not from the number of machines. One actor or aligned group can split stake across many validators and create the appearance of decentralization while still controlling the real voting power.
This is basic. Yet it is constantly ignored because “look how many validators we have” is useful marketing.
ICP takes a more serious approach. Node providers are not just anonymous stake hiding behind machine count. Node providers are approved through NNS governance, and subnets can be composed based on operator independence, data centers, geography, jurisdiction, and infrastructure diversity.
That is deterministic decentralization.
So when Justin acts like “13 nodes” automatically means weak security, he is either missing the point or hoping his audience misses it. A 13-node ICP application subnet is not 13 random machines. It is a deliberately composed Byzantine-fault-tolerant subnet where canister state is replicated across every node, and the subnet continues operating as long as fewer than one third are faulty.
For higher-security workloads, ICP can and does use larger subnets.
That is not a flaw. That is how a decentralized cloud should work.
A real cloud architecture needs a security/cost curve. You do not replicate every application across every node in the world just to satisfy a simplistic talking point. That would be economically absurd. ICP uses the amount of replication and independence appropriate to the workload, while scaling horizontally through additional subnets.
That is engineering.
The reason critics do not want to engage this honestly is obvious: once ICP is evaluated as a decentralized cloud, not just another ledger chain, most of crypto starts looking primitive.
Solana and Sui may be fast. They may have interesting technology. But they are still primarily ledger-chain architectures. ICP is designed to host full-stack applications, serve web content directly from canisters, maintain persistent state, use reverse gas, perform threshold signing, communicate across subnets, and integrate with other chains.
That is a different class of technology.
And that is why the critique has to stay small. It has to obsess over narrow details, terminology, and preferred security models, because if the discussion zooms out to what ICP can actually do, the comparison becomes uncomfortable for the coins Justin supports.
The terminology complaint is especially revealing. Calling ICP’s language “scammy” because it has its own terms is ridiculous. Solana has Proof of History, Tower BFT, Turbine, Sealevel, Gulf Stream, slots, and leaders. Sui has objects, Mysticeti, epochs, shared objects, owned objects, programmable transaction blocks, and delegated proof-of-stake validators.
Every meaningfully different architecture develops its own vocabulary.
ICP has canisters, cycles, subnets, NNS, SNS, XNet, and chain-key cryptography because it is not another EVM clone or high-throughput token chain. The terms exist because the system is different.
Pretending that new terminology is suspicious only when ICP uses it is not a standard. It is bias.
The honest version of Justin’s critique would be this: “ICP does not replicate every application across every node in the network. It uses subnet-based replication, deterministic decentralization, and NNS-governed subnet composition. I personally prefer a different security model.”
That would be accurate.
But it would not sound nearly as damaging.
So instead, the critique uses words like “centralized,” “insecure,” “scammy,” and “dishonest,” because the emotional framing has to do the work the technical argument cannot.
ICP is not perfect. The launch and token-distribution questions can be debated separately. Communication can always improve. But none of that invalidates the architecture.
The subnet model is real. The canister model is real. Chain-key cryptography is real. Threshold signatures are real. Reverse gas is real. Cross-subnet communication is real. Web-serving on-chain applications are real. The decentralized cloud vision is real.
This is the part Justin’s critique cannot afford to face directly.
If ICP is judged by what it can actually host, compute, serve, automate, and integrate, then it is not just another L1 in the pile. It is the project that makes most of the ledger-chain race look small.
Justin can prefer Solana. He can prefer Sui. He can prefer conventional PoS assumptions. That is his choice.
But criticizing ICP because it does not fit the worldview of the coins he already likes is not intellectual honesty. It is motivated maximalism dressed up as technical critique.
His proposed solution is basically: make ICP more like the chains he already understands.
That is exactly why he is missing the value.
ICP does not need to become another ledger chain.
Crypto has enough of those.
ICP is building the decentralized cloud.
$JBBJ sits at just a $35,124 market cap today.
If $ICP becomes a major piece of internet infrastructure. & Jerry Banfield gets the redemption arc many are writing off today.
Then a 100x+ from here isn't hard to imagine.
Fun fact:
Out of 10,000+ Crypto's, only 3 have made higher highs across 3 full cycles:
→ Bitcoin $BTC [$ 78.741,00]
→ Ethereum $ETH [$ 2.400,00]
"Most Altcoins Will Never See Another Real Bull Market..
.. Except $ICP."
Internet Computer Protocol → ∞
pi-network:native Network: A Centralized Mobile App Wrapped in a Crypto Narrative
Tap your screen daily, mine hopes, harvest disappointment.
Pi’s doing cardio on your thumb.
Meanwhile internet-computer:native Internet Computer Protocol, is out here reinventing the internet. (Sitting at a lower market cap)
Wild.
Hey @TeamYouTube, I need help reclaiming my original handle https://t.co/JdvnOFBvlV and https://t.co/B0vTC2Jobr. I deleted the old channel in June 2025 (well over the 60-day window), but it’s still showing as "unavailable."
My current channel https://t.co/dVJaAAsVon is on the same email/AdSense. I suspect a Legacy URL lock is preventing the release. Can a specialist manually clear this? 🙏
I reached out to the support chat already but they were unable to help