

LogicAl
988 posts








@Justin_Bons My assessment of you and your $ICP knowledge. Meet your maker.......what ever you type further, I can technically counter with FACTS... Keep Jogging... The so called author understands some general blockchain concepts, but shows weak knowledge of how $ICP actually works. The repeated issue is comparing $ICP to Ethereum-style PoS and then claiming $ICP is broken because it does not use the same architecture. That is not analysis. That is category error. Examples: • Subnets are treated as if they are simple weak validator sets. • Chain-key ECDSA is compared to Ethereum contracts, which do not provide the same native protocol-level signing model. • HTTPS outcalls are dismissed because external data still needs trust, while ignoring that $ICP removes a separate oracle dependency layer. • Canisters, NNS, SNS and neurons are called “technobabble”, despite being defined technical components. • “Nothing at stake” is claimed, while ignoring node-provider economics, governance staking, NNS admission, subnet distribution and protocol-level consensus. There are fair criticisms to make about $ICP. Subnet security assumptions should be discussed. Node-provider governance should be discussed. Controller/admin risk should be discussed. Oracle data-source trust should be discussed. But this thread repeatedly mixes valid risk topics with inaccurate conclusions. My verdict He knows enough crypto terminology to sound technical. He does not appear to understand $ICP’s architecture deeply enough to fairly assess it. Different does not mean dishonest. Different does not mean insecure. Different does not mean fake. If you want to criticise $ICP, bring precise claims, evidence, and architecture-level comparisons. Not vibes dressed up as security analysis. @Marmightlite @EsselLeroy @ICPapprentice @BobbyO_
















