Difference between revisions of "Daemon canisters"

From Internet Computer Wiki
Jump to: navigation, search
m
m
Line 1: Line 1:
 
'''On the Internet Computer blockchain, you can create canister smart contracts that run like daemon processes — that is, you can configure them so that they are automatically activated by the network itself at specified block intervals.'''
 
'''On the Internet Computer blockchain, you can create canister smart contracts that run like daemon processes — that is, you can configure them so that they are automatically activated by the network itself at specified block intervals.'''
  
When smart contracts are hosted on traditional blockchain networks, computations can be only be invoked by submitting a new transaction to their networks. This means that if, say, a DeFi smart contract needs to periodically perform some action, such as recording the latest asset prices published by [[DEX]]s (decentralized exchanges), a traditional off-chain system such as software running on a centralized [[cloud service]] must be configured to periodically submit transactions.
+
When smart contracts are hosted on traditional blockchain networks, computations can be only be invoked by submitting a new transaction to their networks. This means that if, say, a DeFi (decentralized finance) smart contract needs to periodically perform some action, such as recording the latest asset prices published by [[DEX]]s (decentralized exchanges), a traditional off-chain system such as software running on a centralized [[cloud service]] must be configured to periodically submit transactions.
  
The approach that must be used with traditional blockchains is complex, fault prone, and introduces several problems native to centralization. For example, who will be responsible for running the centralized infrastructure, and will that person become a de facto "controller" or "owner" of an otherwise decentralized DeFi framework in the eyes of financial regulator?
+
The approach that must be used with traditional blockchains is complex, fault prone, and introduces several problems native to centralization. For example, who will be responsible for running the centralized infrastructure, and will that person become a de facto "controller" or "owner" of an otherwise decentralized financial system in the eyes of financial regulator?
  
 
The Internet Computer provides a means to avoid such problems, by allowing canister smart contracts to be configured so that they aer invoked by the blockchain itself, at some specified block interval.
 
The Internet Computer provides a means to avoid such problems, by allowing canister smart contracts to be configured so that they aer invoked by the blockchain itself, at some specified block interval.

Revision as of 16:47, 19 August 2022

On the Internet Computer blockchain, you can create canister smart contracts that run like daemon processes — that is, you can configure them so that they are automatically activated by the network itself at specified block intervals.

When smart contracts are hosted on traditional blockchain networks, computations can be only be invoked by submitting a new transaction to their networks. This means that if, say, a DeFi (decentralized finance) smart contract needs to periodically perform some action, such as recording the latest asset prices published by DEXs (decentralized exchanges), a traditional off-chain system such as software running on a centralized cloud service must be configured to periodically submit transactions.

The approach that must be used with traditional blockchains is complex, fault prone, and introduces several problems native to centralization. For example, who will be responsible for running the centralized infrastructure, and will that person become a de facto "controller" or "owner" of an otherwise decentralized financial system in the eyes of financial regulator?

The Internet Computer provides a means to avoid such problems, by allowing canister smart contracts to be configured so that they aer invoked by the blockchain itself, at some specified block interval.