Live prices are currently unavailable — the exchange feed could not be reached and no recent cached reading is held.

Bitcoin Data GuideBitcoin Reference

Comparisons

A single chain and a network of subnets

Bitcoin is one ledger that every participant can verify. The Internet Computer is a set of independent blockchains that each hold a signing key and can act on other chains without a bridge. The architectures are shaped by what each network was built to do.

The subnet and canister model

The Internet Computer is not a single blockchain. Its documentation describes it as a network of independent blockchains called subnets, where each subnet is a group of nodes running its own instance of the consensus protocol, maintaining its own chain and executing canisters independently of the others. When a canister is deployed it lands on one subnet and is replicated across every node in that subnet, and that replication is what the documentation identifies as making canisters tamperproof: no single node can unilaterally change a canister's state.

The execution model is the part that differs most from Bitcoin. A canister is a program with its own state and its own cycles budget, and the documentation describes subnets producing one finalised block per round, approximately every second, with cryptographic rather than probabilistic finality. Query calls skip consensus entirely and are answered by a single node, which is why they are fast and why the documentation is explicit that they carry weaker authenticity guarantees than update calls. Bitcoin's model is the opposite in every respect: one chain, one block roughly every ten minutes, and settlement assurance that grows with confirmations rather than arriving at a defined moment.

The two designs also differ in what a program can do. A Bitcoin script is a predicate that decides whether an output may be spent, and it has no memory of its own beyond the unspent outputs it controls. A canister holds state, serves requests and can call other canisters, which makes it closer to a server process than to a script. That is a deliberate design choice, and it is why the Internet Computer is described as running at web speed rather than as settling a payment network.

Chain-key cryptography and what it enables

The feature that most clearly separates the two networks is chain-key cryptography. The Internet Computer's documentation describes it as a set of threshold cryptographic protocols in which no single node holds a private key: the key is split into shares distributed across the nodes of a subnet, and the nodes collaboratively sign without ever reconstructing the full key. Each subnet holds a threshold BLS key, so any sufficiently large subset of nodes can produce a valid signature and no smaller group can forge one.

Two consequences follow. The first is verification: because a response from a subnet is signed by one key, a client can verify it with a single signature check against a single public key, however many nodes produced it. The documentation describes certified data as the mechanism that lets a canister prove a query response reflects state committed through consensus, using a certificate that chains back to the network's root public key. The second is cross-chain signing: canisters can request threshold ECDSA and Schnorr signatures, which gives them the ability to control addresses and sign transactions on external chains. The documentation presents this as the foundation of Chain Fusion, and notes that canisters can sign Bitcoin, Ethereum and Solana transactions directly, without a bridge.

Bitcoin has no equivalent. A Bitcoin node verifies signatures and enforces script; it does not hold a share of a network key and it cannot sign on behalf of another chain. Moving bitcoin to another network therefore requires a separate mechanism, which is why the custody and bridge questions on the native and wrapped bitcoin page are specific to Bitcoin and do not arise in the same form on the Internet Computer.

What each network is structured to optimise for

Bitcoin optimises for verifiability and for a monetary policy that no one can change. Its block size is bounded so that validation stays cheap, its subsidy schedule is fixed so that supply is predictable, and its scripting language is deliberately limited so that the set of behaviours a node must reason about stays small. Every one of those choices costs throughput or expressiveness, and each is defended on the grounds that the base layer should be the most conservative component in the system.

The Internet Computer optimises for running applications. Subnets produce blocks about once a second, canisters hold state and serve requests, and the threshold cryptography lets a canister act as an autonomous agent that can hold and move assets on other chains. The documentation frames the platform's purpose around hosting software rather than settling payments, and the architecture follows: many subnets rather than one chain, fast finality rather than probabilistic settlement, and a signing capability that no single-chain network has.

The comparison is therefore not a contest. A reader who wants a monetary asset with a supply rule that cannot be revised is looking at Bitcoin, and a reader who wants to run a program that holds state and can sign for itself on other chains is looking at the Internet Computer. The two networks are not substitutes, and treating them as rivals on a single axis obscures the design intent on both sides.

Sources and references

The Internet Computer's architecture is described from DFINITY's official developer documentation; Bitcoin's from its reference documentation. No capability is asserted that the cited source does not describe.

  • Subnets, canisters and finality. ICP Developer Docs, Network overview: subnets are independent blockchains, canisters are replicated across a subnet's nodes, and blocks are finalised roughly every second.
  • Chain-key cryptography. ICP Developer Docs, Chain-key cryptography: keys are split into shares across a subnet's nodes, and threshold ECDSA and Schnorr signatures let canisters sign on external chains.
  • Certified responses. ICP Developer Docs, Certified data: a query response can be verified with a single signature check against the network's root public key.
  • Bitcoin's block structure and subsidy. Bitcoin Developer Reference, Block Chain: a block's serialised size is bounded by consensus, and the block reward is the subsidy plus transaction fees.

Related reading