How much does it cost to run a dapp on the Internet Computer?
Computation and Storage Costs
The Internet Computer requires computation operations and storage to be supported by cycles. Cycles are generated from the conversion of Internet Computer (ICP) utility tokens.
The Role of the Network Nervous System (NNS) in Defining Costs
The Internet Computer is a decentralized public utility, controlled by the NNS –– the network’s open, algorithmic governance system. The NNS fundamentally controls how many cycles are required for low-level computation actions for computation and storage. The number of cycles needed for individual computations will vary based on a number of factors considered by the NNS, including proposals from the community.
Details: Cost of Compute and Storage Transactions on the Internet Computer
Canisters (dapps/smart contracts) computations running on the Internet Computer blockchain are fueled by “cycles”, which play a similar role to “gas” on Ethereum. There are several major differences, however. One of the most fundamental differences is that Ethereum leverages “user pays” and the Internet Computer leverages “smart contract pays” (sometimes called “reverse gas”) model. Whereas the Ethereum blockchain requires end-users to send payments for the gas smart contracts consumed with every transaction, on the Internet Computer, canisters (dapps/smart contracts)are pre-charged with cycles, such that contracts effectively pay for their own computation - freeing users from the responsibility.
See below for details on the cost of compute and storage transactions[1] on the Internet Computer as of July 26, 2021.
| Transaction | Description | All Application Subnets |
|---|---|---|
| Canister Created | For creating canisters on a subnet | 100_000_000_000 |
| Compute Percent Allocated Per Second | For each percent of the reserved compute allocation (a scarce resource). | 100_000 |
| Update Message Execution | For every update message executed | 590,000 |
| Ten Update Instructions Execution | For every 10 instructions executed when executing update type messages | 4 |
| Xnet Call | For every inter-canister call performed (includes the cost for sending the request and receiving the response) | 260_000 |
| Xnet Byte Transmission | For every byte sent in an inter-canister call (for bytes sent in the request and response) | 1_000 |
| Ingress Message Reception | For every ingress message received | 1_200_000 |
| Ingress Byte Reception | For every byte received in an ingress message | 2_000 |
| GB Storage Per Second | For storing a GB of data per second | 127_000 |
The $USD cost for transactions below is based on the above cycle costs. 1 XDR is equal to 1 Trillion cycles. As of July 26, 2021, the exchange rate for 1 XDR = $1.42. The exchange rate for USD <> XDR may vary and it will impact the conversion rate. For XDR exchange rates please visit: https://www.imf.org/external/np/fin/data/rms_sdrv.aspx
| Transaction | Description | All Application Subnets |
|---|---|---|
| Canister Created | For creating canisters on a subnet | $0.142 |
| Compute Percent Allocated Per Second | For each percent of the reserved compute allocation (a scarce resource). | $0.000000142 |
| Update Message Execution | For every update message executed | $0.0000008378 |
| Ten Update Instructions Execution | For every 10 instructions executed when executing update type messages | $0.00000000000568 |
| Xnet Call | For every inter-canister call performed (includes the cost for sending the request and receiving the response) | $0.0000003692 |
| Xnet Byte Transmission | For every byte sent in an inter-canister call (for bytes sent in the request and response) | $0.00000000142 |
| Ingress Message Reception | For every ingress message received | $0.000001704 |
| Ingress Byte Reception | For every byte received in an ingress message | $0.00000000284 |
| GB Storage Per Second | For storing a GB of data per second | $0.00000018034 |