Internet Computer (ICP)

@jp_dawg As promised, here are the 4 additional errors (it would be 5 including the last one you made in the meantime).

1) HTTP Gateway is not the same as a Cloudflare Worker. ICP serves certified responses, meaning the canister output is organized in a Merkle tree, signed with threshold BLS by the subnet, and verified on the client side against the NNS root key. The gateway cannot tamper with the payload. A Cloudflare Worker is simply a proxy with no certification and must be fully trusted.

2) Trust topology... NEAR's path goes through an RPC provider, then Worker code, and finally the Cloudflare edge, which means three trusted off chain hops. ICP boundary nodes are governed by the NNS, are multiple, and run on hardware provided by different providers, as stated on the very page you shared.

3) "Fully on-chain" got used in two senses.
On ICP execution + state + asset serving all live in the canister, gateway is transport. On Flappy Bird the 60fps authoritative game loop runs in browser JS, the contract is

will double https://t.co/YTeK7uSVZl