Skip to main content
How it worksIngress Message Lifecycle

Ingress Message Lifecycle

When a user sends an update call to a canister smart contract on the Internet Computer, it traverses several components before it is actually executed. In a first step, P2P ensures that it is broadcast to a sufficiently large set of other nodes. At some point, consensus forms a block that contains the message and passes it in a batch to message routing, which in turn inserts it into its destination canister’s queue, where it waits for the scheduler to select the next message to be executed. A message is subject to several checks, and a number of conditions must be satisfied for it to make it into the Induction Pool for execution to ensure that the right parties are charged and rewarded for its processing.

More academy sessions

Internet Computer Blockchain Overview

Internet Computer Blockchain Overview

Learn more
Chain Key Cryptography

Chain Key Cryptography

Learn more
Motoko Smart Contract Language

Motoko Smart Contract Language

Learn more
Network Nervous System: Internet Computer Blockchain Governance

Network Nervous System: Internet Computer Blockchain Governance

Learn more
Noninteractive Distributed Key Generation

Noninteractive Distributed Key Generation

Learn more
Internet Identity: Anonymizing Blockchain Authentication System

Internet Identity: Anonymizing Blockchain Authentication System

Learn more
Internet Computer Consensus

Internet Computer Consensus

Learn more
Peer-to-Peer Layer

Peer-to-Peer Layer

Learn more
Resumption

Resumption

Learn more
Blockchain Protocol Upgrade

Blockchain Protocol Upgrade

Learn more
Message Routing

Message Routing

Learn more
Canister smart contract lifecycle

Canister smart contract lifecycle

Learn more
Certified Variables

Certified Variables

Learn more
Direct Integration with Bitcoin

Direct Integration with Bitcoin

Learn more
Threshold ECDSA Signing

Threshold ECDSA Signing

Learn more
State Synchronization

State Synchronization

Learn more