https://wiki.internetcomputer.org/w/api.php?action=feedcontributions&feedformat=atom&user=Dominic.woerner 2026-04-30T16:06:14Z User contributions MediaWiki 1.39.17 https://wiki.internetcomputer.org/w/index.php?title=L1_comparison&diff=6556 2023-11-03T08:35:26Z

<p>Dominic.woerner: Updated value of available stable memory</p> <hr /> <div>The promise of a [[World Computer]] and the emergence of a Blockchain Singularity has far reaching consequences in technology, sociology, economics, politics, communication, entertainment, and most aspects of our digital lives. As the industry is one of rapid innovation and progress, and as projects constantly and dynamically change, it's important to take stock, every now and then, to note how the industry is doing, and to check if the Internet Computer is on track to achieve the goals of decentralization, scalability, usability, and functionality. <br /> <br /> The industry is now moving out of its infancy, which is seen by the increasing number of smart contract developers, rather than core protocol developers, and users wanting to fully engage with a platform, rather than simply sending transactions back and forth. The shift away from simple payment systems, towards Web3 is well on its way, and it's within this scope that this page attempts to map the blockchain landscape.<br /> <br /> Top performing blockchain projects are compared across a number of metrics that are expected to yield a 'good' Web3 experience under the categories of core protocol, developer experience, and user experience.<br /> <br /> Unless otherwise stated, all data is correct as of December 9th 2022. Metrics are explained and references are given below.<br /> <br /> == Base comparisons == <br /> This section compares standard metrics that are used to measure performance of the core protocol of popular blockchain projects. Note that these metrics should not always be taken at face value. While references are listed below to note where the figures can be found, it's not always clear how these figures are computed. Additionally, parts of different projects may have the same name, but often are constructed differently (most notably, transactions), and so should not be compared blindly like-for-like. The [https://a16zcrypto.com/why-blockchain-performance-is-hard-to-measure/ a16z blog] has a nice article describing how the industry should think about metrics.<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Metrics / L1 !! Average MIEPs !! Average TPS !! Average finality !! Average block time (seconds) !! Average tx Cost !! Average energy consumption per transaction (wh/tx) !! Average energy consumption per million instructions (wh/mi) !! Size of network (nodes) !! On-Chain storage cost (1GB p/a)<br /> |-<br /> | ICP ||20000||5382 (update calls)||1.4secs||0.936||$0.0000022||0.008||0.0012||823||$5 (3.95T cycles x 1XDR)<br /> |-<br /> | Algorand || ||15.5||3.5secs||3.5||$0.00025||2.7|| ||1530|| <br /> |-<br /> | Avalanche || ||49.52||2.3secs||2.3||$0.0066 (C-Chain only)||4.76|| ||1195||$206,875 (15,62 5AVAX)<br /> |-<br /> | Cardano || ||2.37|| ||20||$0.1|| 51.59 || || 1050 || $17,035 - $113,507 (53,236 – 354708ADA) <br /> |-<br /> | Ethereum || 1.25 || 11.1 || 15mins || 12.08 || $2.39 || 6.29 || 75.480|| 6562 || $15,494,409 (12,643.75 ETH) <br /> |-<br /> | Near || || 8.25 || 3.3secs || 1.11 || $0.0031 || 0.036 || || 798 || <br /> |-<br /> | Solana || || 286 (non-voting calls) || 5-12secs || 0.542 || $0.000026 || 0.166 || || 1872 || $48,625 (3,477.69 SOL)<br /> |}<br /> <br /> * ''' Average MIEPs''' measures millions of executed instructions per second which is an approximation of useful work performed. Further explanation can be found here: [[Not all transactions are equal|&quot;Not all transactions are equal&quot;]]. Note that the figure for ETH is an upper bound of what is possible, while the figure for ICP is the actual count of executed instructions. <br /> * '''Average TPS''' measures the transactions processed per second - note that the interval over which these are measured does vary across chains. The dollar amounts are computed by converting the native token cost cycles/gas/fee needed per transaction, to USD given the exchange rate on December 9th 2022.<br /> * '''Average finality''' refers to the amount of time that passes between the proposal of a new valid block containing transactions until the block has been finalized and its content is guaranteed to not be reversed or modified (for some blockchains, e.g., Bitcoin, this guarantee can only be probabilistic).<br /> *''' Average block time''' refers to the amount of time between blocks (per subnet on the IC)<br /> * '''Average tx Cost''' measures the cost of a transaction. Note that the definition of 'transaction' varies widely across chains, where some are described below. The dollar amounts are computed by converting the native token cost cycles/gas/fee needed per transaction, to USD given the exchange rate on December 9th 2022. (Cardano and Ethereum figures found in [https://messari.io/asset/cardano/chart/txn-fee-avg Messari dashboard].) <br /> * '''Average energy consumption per transaction''' measures the network energy consumption to process a transaction (measured in watt hours)<br /> * '''Average energy consumption per million instructions''' measures the network energy consumption to process 1 million instructions (measured in watt hours). Note this considered that Etheruem executes 0.083333 million instructions per transaction while ICP executes 6.66 million instructions per transaction. Figures true as of March 2023 and discussed [[Not all transactions are equal|here]].<br /> * '''Size of network (nodes)''' notes the number of nodes currently making up the network<br /> * '''On-chain storage cost''' gives the dollar cost and the native token cost of storing 1GB of data per year on chain.<br /> <br /> == Comparing developer experience ==<br /> Whether they were writing games, operating systems or text editing applications, in the 70s, 80s and early 90s, developers always had to face limitations imposed by hardware. Applications were constrained to accessing a few kilobytes of memory through small stacks and heaps, using limited (and constantly changing) instruction sets, and using significant amounts of power to run instructions. The history repeats itself in the blockchain landscape these days. Application developers are limited to stack sizes of a few kilobytes to several megabytes at best. Persistent storage is expensive and limited. Programmers are bound to using cumbersome APIs that make hidden assumptions in terms of numbers of executed instructions. And, moreover, most chains operate inefficiently, burning too much power per executed transaction. This not only limits the types of applications that can be deployed on chain, but also increases development and testing time (and cost).<br /> <br /> As opposed to all existing blockchains, the IC brings modern programming to on-chain developers, allowing them to use time for creativity rather than fixing memory packing issues or spreading computation in small iterations that do not hit instruction limits. The IC programming model offers orthogonal persistence, large stack and heap spaces (4 GiB), stable storage of 96 GiB (with plans for increase) in mainstream languages, such as Rust, JavaScript, or even Python.<br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> ! Metrics / L1 !! Stable tx cost !! HTTPs outcalls !! Smart contract language support !! Max stack size !! Max persisted memory (per smart-contract) !! Active developers (full-time / monthly) !! Active repositories <br /> |-<br /> | ICP || ✅ || ✅ || Motoko (native), Rust, TypeScript, Python ||data-sort-value=&quot;4294967296&quot;| 4 GiB ||data-sort-value=&quot;55834574848&quot;| 96 GiB || 121 / 406 || 3973 <br /> |-<br /> | Algorand || ❌ || ❌ || Teal (native), Python ||data-sort-value=&quot;4194304&quot;| 4 MB ||data-sort-value=&quot;1048576&quot;| 1 MB || 52 / 192 || 438 <br /> |-<br /> | Avalanche || ❌ || ❌ || Solidity || || || 95 / 332 || 1901 <br /> |-<br /> | Cardano || ❌ || ❌ || Plutus (native), Haskell || || || 163 / 465 || 1252 <br /> |-<br /> | Ethereum || ❌ || ❌ || Solidity (native), Vyper, Yul, FE ||data-sort-value=&quot;32768&quot;| 32 KiB ||data-sort-value=&quot;3705346855594118253554271520278013051304639509300498049262642688253220148477952&quot;| 2^261 B (however, 15,494,409$ per GiB) || 1873 / 5734 || 29117 <br /> |-<br /> | Near || ❌ || ❌ || Rust, Javascript ||data-sort-value=&quot;262144&quot;| 256 KiB ||data-sort-value=&quot;32768&quot;| 32 KiB || 205 / 781 || 5352 <br /> |-<br /> | Solana || ❌ || ❌ || Rust C, C++ || || || 383 / 2082 || 6137<br /> |-<br /> |}<br /> <br /> <br /> * ''' Stable tx cost''' provides the ability to have predictable costs for computation <br /> * ''' HTTPs outcalls''' is the ability to communicate directly with Web2 services (outside of the network)<br /> * '''Max stack size''' is the maximum size the stack can grow for smart contracts and serves as a measure for the complexity of code that is supported by each platform<br /> * '''Max persisted memory''' is the maximum size of persisted memory supported by each platform. Persisted memory is preserved across individual function calls<br /> * '''Active developers''' counts the number of developers who made commits on more than 10 days in a month (full-time) or original code authors who made commits in a given month. Source [https://www.electriccapital.com/ Electric Capital]. Figures true as of 15/12/22<br /> * '''Active repositories''' are sourced from the [https://www.electriccapital.com/ Electric Capital] [https://github.com/electric-capital/crypto-ecosystems crypto ecosystems list]. Figures true as of 15/12/22<br /> <br /> <br /> == Comparing user experience == <br /> It is widely accepted that the Web3 user experience needs massive development before mainstream adoption is likely. This sections starts to map out key metrics for Web3 usability. First and foremost is privacy, identity management and authentication. On many projects, every interaction that a user ever makes can be traced and monitored. While transparency is good for some things, it's argued that this is a severe hindrance to adoption. Financial privacy and the freedom to interact should be paramount. <br /> The tools needed to interact with a project are also noted. These can be seen as a measure of accessibility and openness to onboarding. <br /> Finally, metrics about participation in the network are included. A large draw of Web3 is the fact that users can become owners and drivers of the platform. Here the percentage of native tokens staked as a measure of user confidence and participation in the project are included. <br /> <br /> {| class=&quot;wikitable sortable&quot;<br /> |-<br /> ! Metrics / L1 !! Privacy-preserving authentication !! Prerequisites to use !! Staking ratio !! Monthly active wallets<br /> |- <br /> | ICP || ✅ || Browser || 73.89% || 93k<br /> |-<br /> | Cardano || ❌ || Browser, browser extension, tokens || 71.58%||<br /> |-<br /> |Avalanche || ❌ || Browser, browser extension, tokens || 61.78% || [https://stats.avax.network/dashboard/overview/ 390k]<br /> |-<br /> | Algorand || ❌ || Browser, browser extension, tokens || 51.17% ||<br /> |-<br /> | Ethereum || ❌ || Browser, browser extension, tokens || 13.57% || [https://www.theblock.co/data/on-chain-metrics/ethereum/number-of-active-addresses-on-the-ethereum-network-monthly 15m]<br /> |- <br /> | Near || ❌ || Browser, browser extension, tokens || 43.19% ||<br /> |-<br /> | Solana || ❌ || Browser, browser extension, tokens || 68.59% || [https://dune.com/queries/829800 655k]<br /> |}<br /> <br /> * '''Privacy-preserving authentication''' notes whether a project allows privacy-preserving interactions with the blockchain.<br /> * '''Prerequisites to use''' lists what is needed to interact with the project<br /> * '''Staking ratio''' gives the percentage of native tokens that are staked in the protocol. The staking ratio metrics are from [https://www.stakingrewards.com/cryptoassets/ Staking Rewards] and are correct as of 19.12.2022<br /> * ''' Monthly active wallets''' counts the wallet addresses that sent or received native currency in a given month (December 2022) <br /> <br /> === A note about average transactions cost === <br /> * Algorand: https://metrics.algorand.org/#/protocol/, explanation: Average transaction fee of all transactions in the selected time period. [https://developer.algorand.org/docs/get-details/transactions/#fees Algorand fees]<br /> * Cardano: [https://docs.cardano.org/explore-cardano/fee-structure Cardano fees] Fees are constructed around two constants (a and b). The formula for calculating minimal fees for a transaction (tx) is '''a''' times '''size(tx) + b''', where:<br /> ** a/b are protocol parameters<br /> ** size(tx) is the transaction size in bytes<br /> * Solana: [https://docs.solana.com/transaction_fees Solana fees]<br /> <br /> === A note about finality === <br /> It is sometimes unclear what exactly different projects mean by finality, so references are noted here and describe how the above figures are computed. <br /> * For ICP, finality calculated as described in the [https://internetcomputer.org/whitepaper.pdf whitepaper] in section 5.11.6. <br /> * For Near, the fact finalization occurs after 3 blocks is leveraged (as stated in the [https://docs.near.org/concepts/advanced/near-indexer-framework#limitations docs]) as well as the current block time of 1.1 seconds from the [https://explorer.near.org/ explorer].<br /> * All other finality figures for now come from the finality section [https://newsbtc.com/all/assessing-the-top-performing-layer-1-blockchain-protocols/ here].<br /> <br /> === A note about decentralization ===<br /> Decentralization is key to make web3 dapps run in a trustless manner. However, decentralization has many dimensions and cannot be understood and quantified using a single number or coefficient. One can distinguish between a) the decentralization of the entities running the machines on top of which a protocol runs, b) the decentralization of the consensus and sharding mechanism, c) the governance system, the owners of liquid tokens etc. In this case, the whole is greater than the sum of its parts and one cannot understand decentralization as a single discussion on each of these topics.<br /> <br /> See [[Decentralization|Decentralization Wiki Page]] for more details.<br /> <br /> <br /> == References == <br /> * '''ICP''' : [https://dashboard.internetcomputer.org IC Dashboard]<br /> * '''ADA''' : [https://explorer.cardano.org/en Cardano explorer] and [https://cexplorer.io/ cexplorer]<br /> * '''AVAX''' : [https://snowtrace.io/ Snowtrace] and [https://subnets.avax.network/ Avalanche explorer]<br /> * '''ALGO''' : [https://www.algorand.com/ Algorand website] and [https://metrics.algorand.org/ Algorand metrics site]<br /> * '''ETH''' : [https://etherscan.io/ Etherscan]<br /> * '''NEAR''' : [https://explorer.near.org/ Near explorer] and [https://docs.near.org/ Near docs]<br /> * '''SOL''' : [https://solana.com/ Solana website] and [https://solanabeach.io/ Solana beach]</div>

Dominic.woerner https://wiki.internetcomputer.org/w/index.php?title=Scalability_%26_Performance&diff=4586 2023-03-14T20:44:03Z

<p>Dominic.woerner: </p> <hr /> <div>== Working Group Topic: Scalability &amp; Performance ==<br /> <br /> * DFINITY lead: [https://forum.dfinity.org/u/abk Adam Bratschi-Kaye]<br /> * Cadence: Monthly on the third Thursday of every month at 5:30pm CET<br /> * Discord Channel: [https://discord.com/channels/748416164832608337/994942091463512175 Scalability]<br /> * [https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265 Forum Thread]<br /> * [https://docs.google.com/document/d/11L9_MvoW12JTWH71T6i3ULskjj9b3Gec0oBPVR83ZsE Meeting Notes with links to Recordings]<br /> <br /> First meeting: July 21, 2022 at 5:30pm CET<br /> <br /> ==== Calendar ====<br /> [https://calendar.google.com/calendar/u/0?cid=Y19jazBncjc5YmtnY29vaWNuMXA4N21vMWVyb0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t Calender link (all working groups)]<br /> [https://calendar.google.com/calendar/u/0/embed?src=c_ck0gr79bkgcooicn1p87mo1ero@group.calendar.google.com&amp;ctz=Europe/Zurich Public Calendar Link]<br /> <br /> ==== Zoom Meeting Details ====<br /> https://dfinity.zoom.us/j/98492107298?pwd=QlJQNnU5SmhKY01vbTRkYlEyZ2Rzdz09<br /> <br /> Meeting ID: 984 9210 7298&lt;br&gt;<br /> <br /> Passcode: 806912<br /> <br /> ==== Description ====<br /> <br /> The Internet Computer provides a unique blockchain platform for decentralized applications. The actor model allows parallel execution of code in a given subnet and the IC can scale horizontally by adding more subnets. Already today, this allows the building of decentralized applications using smart contracts that aren't possible on other blockchains. However, these are still early days for the Internet Computer, and design patterns for building decentralized applications on a global scale are only starting to emerge. The Internet Computer itself is also continuously maturing with performance improvements, new features, and better tooling. The goal of this working group is to foster a regular exchange between R&amp;D at DFINITY and application developers with the following focus:<br /> <br /> * Updates on the relevant R&amp;D roadmap and presentation of ideas<br /> * Collecting and discussing pain points of application developers<br /> * Identification and sharing of best practices and design patterns for building applications on the IC</div>

Dominic.woerner https://wiki.internetcomputer.org/w/index.php?title=Developer_Tooling&diff=3851 2022-11-30T12:35:52Z

<p>Dominic.woerner: </p> <hr /> <div>== Working Group Topic: Developer Tooling ==<br /> <br /> * DFINITY lead: [https://forum.dfinity.org/u/dfx-json Jason Ibrahim]<br /> * Coordinator: [https://forum.dfinity.org/u/domwoe Dominic Wörner]<br /> * Cadence: Monthly on the first Thursday of every month at 7pm CET<br /> * Discord Channel: [https://discord.com/channels/748416164832608337/976871731245490237 Developer Tooling]<br /> * [https://forum.dfinity.org/t/technical-working-group-developer-tooling/11941 Forum Thread]<br /> * [https://docs.google.com/document/d/1IRfsi3ojNuoctFvZEmLOsYUAH5E2CBSuctxuJvA5M1U Meeting Notes with Link to Recording]<br /> <br /> * First meeting: April 5, 2022 at 7:00pm CET<br /> <br /> ==== Calendar ====<br /> <br /> [https://calendar.google.com/calendar/u/0?cid=Y19jazBncjc5YmtnY29vaWNuMXA4N21vMWVyb0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t Calender link (all working groups)]<br /> <br /> [https://calendar.google.com/calendar/u/0/embed?src=c_ck0gr79bkgcooicn1p87mo1ero@group.calendar.google.com&amp;ctz=Europe/Zurich Public Calendar Link]<br /> <br /> ==== Zoom Meeting Details ====<br /> <br /> https://dfinity.zoom.us/j/98865672859?pwd=UXorcDNQQzl3Tk5rVTVmRW5lYXdEQT09<br /> <br /> Meeting ID: 988 6567 2859&lt;br&gt;<br /> <br /> Passcode: 075319</div>

Dominic.woerner https://wiki.internetcomputer.org/w/index.php?title=Scalability_%26_Performance&diff=3850 2022-11-30T12:31:55Z

<p>Dominic.woerner: </p> <hr /> <div>== Working Group Topic: Scalability &amp; Performance ==<br /> <br /> * DFINITY lead: [https://forum.dfinity.org/u/johan Johan Granström]<br /> * Coordinator: [https://forum.dfinity.org/u/domwoe Dominic Wörner]<br /> * Cadence: Monthly on the third Thursday of every month at 5:30pm CET<br /> * Discord Channel: [https://discord.com/channels/748416164832608337/994942091463512175 Scalability]<br /> * [https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265 Forum Thread]<br /> * [https://docs.google.com/document/d/11L9_MvoW12JTWH71T6i3ULskjj9b3Gec0oBPVR83ZsE Meeting Notes with links to Recordings]<br /> <br /> First meeting: July 21, 2022 at 5:30pm CET<br /> <br /> ==== Calendar ====<br /> [https://calendar.google.com/calendar/u/0?cid=Y19jazBncjc5YmtnY29vaWNuMXA4N21vMWVyb0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t Calender link (all working groups)]<br /> [https://calendar.google.com/calendar/u/0/embed?src=c_ck0gr79bkgcooicn1p87mo1ero@group.calendar.google.com&amp;ctz=Europe/Zurich Public Calendar Link]<br /> <br /> ==== Zoom Meeting Details ====<br /> https://dfinity.zoom.us/j/98492107298?pwd=QlJQNnU5SmhKY01vbTRkYlEyZ2Rzdz09<br /> <br /> Meeting ID: 984 9210 7298&lt;br&gt;<br /> <br /> Passcode: 806912<br /> <br /> ==== Description ====<br /> <br /> The Internet Computer provides a unique blockchain platform for decentralized applications. The actor model allows parallel execution of code in a given subnet and the IC can scale horizontally by adding more subnets. Already today, this allows the building of decentralized applications using smart contracts that aren't possible on other blockchains. However, these are still early days for the Internet Computer, and design patterns for building decentralized applications on a global scale are only starting to emerge. The Internet Computer itself is also continuously maturing with performance improvements, new features, and better tooling. The goal of this working group is to foster a regular exchange between R&amp;D at DFINITY and application developers with the following focus:<br /> <br /> * Updates on the relevant R&amp;D roadmap and presentation of ideas<br /> * Collecting and discussing pain points of application developers<br /> * Identification and sharing of best practices and design patterns for building applications on the IC</div>

Dominic.woerner https://wiki.internetcomputer.org/w/index.php?title=Scalability_%26_Performance&diff=3849 2022-11-30T12:31:01Z

<p>Dominic.woerner: </p> <hr /> <div>== Working Group Topic: Scalability &amp; Performance ==<br /> <br /> * DFINITY lead: [https://forum.dfinity.org/u/johan Johan Granström]<br /> * Coordinator: [https://forum.dfinity.org/u/domwoe Dominic Wörner]<br /> * Cadence: Monthly on the third Thursday of every month at 5:30pm CET<br /> * Discord Channel: [https://discord.com/channels/748416164832608337/994942091463512175 Scalability]<br /> * [https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265 Forum Thread]<br /> * [Meeting Notes with links to Recordings s://docs.google.com/document/d/11L9_MvoW12JTWH71T6i3ULskjj9b3Gec0oBPVR83ZsE]<br /> <br /> First meeting: July 21, 2022 at 5:30pm CET<br /> <br /> ==== Calendar ====<br /> [https://calendar.google.com/calendar/u/0?cid=Y19jazBncjc5YmtnY29vaWNuMXA4N21vMWVyb0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t Calender link (all working groups)]<br /> [https://calendar.google.com/calendar/u/0/embed?src=c_ck0gr79bkgcooicn1p87mo1ero@group.calendar.google.com&amp;ctz=Europe/Zurich Public Calendar Link]<br /> <br /> ==== Zoom Meeting Details ====<br /> https://dfinity.zoom.us/j/98492107298?pwd=QlJQNnU5SmhKY01vbTRkYlEyZ2Rzdz09<br /> <br /> Meeting ID: 984 9210 7298&lt;br&gt;<br /> <br /> Passcode: 806912<br /> <br /> ==== Description ====<br /> <br /> The Internet Computer provides a unique blockchain platform for decentralized applications. The actor model allows parallel execution of code in a given subnet and the IC can scale horizontally by adding more subnets. Already today, this allows the building of decentralized applications using smart contracts that aren't possible on other blockchains. However, these are still early days for the Internet Computer, and design patterns for building decentralized applications on a global scale are only starting to emerge. The Internet Computer itself is also continuously maturing with performance improvements, new features, and better tooling. The goal of this working group is to foster a regular exchange between R&amp;D at DFINITY and application developers with the following focus:<br /> <br /> * Updates on the relevant R&amp;D roadmap and presentation of ideas<br /> * Collecting and discussing pain points of application developers<br /> * Identification and sharing of best practices and design patterns for building applications on the IC</div>

Dominic.woerner https://wiki.internetcomputer.org/w/index.php?title=Developer_Tooling&diff=3848 2022-11-30T12:24:15Z

<p>Dominic.woerner: </p> <hr /> <div>== Working Group Topic: Developer Tooling ==<br /> <br /> * DFINITY lead: [https://forum.dfinity.org/u/dfx-json Jason Ibrahim]<br /> * Coordinator: [https://forum.dfinity.org/u/domwoe Dominic Wörner]<br /> * Cadence: Monthly on the first Thursday of every month at 7pm CET<br /> * Discord Channel: [https://discord.com/channels/748416164832608337/976871731245490237 Developer Tooling]<br /> * [https://forum.dfinity.org/t/technical-working-group-developer-tooling/11941 Forum Thread]<br /> * [https://docs.google.com/document/d/1IRfsi3ojNuoctFvZEmLOsYUAH5E2CBSuctxuJvA5M1U/edit# Meeting Notes with Link to Recording]<br /> <br /> * First meeting: April 5, 2022 at 7:00pm CET<br /> <br /> ==== Calendar ====<br /> <br /> [https://calendar.google.com/calendar/u/0?cid=Y19jazBncjc5YmtnY29vaWNuMXA4N21vMWVyb0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t Calender link (all working groups)]<br /> <br /> [https://calendar.google.com/calendar/u/0/embed?src=c_ck0gr79bkgcooicn1p87mo1ero@group.calendar.google.com&amp;ctz=Europe/Zurich Public Calendar Link]<br /> <br /> ==== Zoom Meeting Details ====<br /> <br /> https://dfinity.zoom.us/j/98865672859?pwd=UXorcDNQQzl3Tk5rVTVmRW5lYXdEQT09<br /> <br /> Meeting ID: 988 6567 2859&lt;br&gt;<br /> <br /> Passcode: 075319</div>

Dominic.woerner https://wiki.internetcomputer.org/w/index.php?title=Developer_Tooling&diff=3847 2022-11-30T12:19:48Z

<p>Dominic.woerner: </p> <hr /> <div>== Working Group Topic: Developer Tooling ==<br /> <br /> * DFINITY lead: [https://forum.dfinity.org/u/dfx-json Jason Ibrahim]<br /> * Coordinator: [https://forum.dfinity.org/u/domwoe Dominic Wörner]<br /> * Cadence: Monthly on the first Thursday of every month at 7pm CET<br /> * Discord Channel: [https://discord.com/channels/748416164832608337/976871731245490237 Developer Tooling]<br /> * [https://forum.dfinity.org/t/technical-working-group-developer-tooling/11941 Forum Thread]<br /> * [https://docs.google.com/document/d/1IRfsi3ojNuoctFvZEmLOsYUAH5E2CBSuctxuJvA5M1U/edit# Meeting Notes with Link to Recording]<br /> <br /> * First meeting: April 5, 2022 at 7:00pm CET<br /> <br /> [https://calendar.google.com/calendar/u/0?cid=Y19jazBncjc5YmtnY29vaWNuMXA4N21vMWVyb0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t Calender link (all working groups)]<br /> <br /> ==== Zoom Meeting Details ====<br /> <br /> https://dfinity.zoom.us/j/98865672859?pwd=UXorcDNQQzl3Tk5rVTVmRW5lYXdEQT09<br /> <br /> Meeting ID: 988 6567 2859&lt;br&gt;<br /> <br /> Passcode: 075319</div>

Dominic.woerner https://wiki.internetcomputer.org/w/index.php?title=Developer_Tooling&diff=3846 2022-11-30T12:18:22Z

<p>Dominic.woerner: </p> <hr /> <div>== Working Group Topic: Developer Tooling ==<br /> <br /> * DFINITY lead: [https://forum.dfinity.org/u/dfx-json Jason Ibrahim]<br /> * Coordinator: [https://forum.dfinity.org/u/domwoe Dominic Wörner]<br /> * Cadence: Monthly on the first Thursday of every month at 7pm CET<br /> * Discord Channel: [https://discord.com/channels/748416164832608337/976871731245490237 Developer Tooling]<br /> * [https://forum.dfinity.org/t/technical-working-group-developer-tooling/11941 Forum Thread]<br /> * [Meeting Notes with Link to Recording](https://docs.google.com/document/d/1IRfsi3ojNuoctFvZEmLOsYUAH5E2CBSuctxuJvA5M1U/edit#)<br /> <br /> * First meeting: April 5, 2022 at 7:00pm CET<br /> <br /> [https://calendar.google.com/calendar/u/0?cid=Y19jazBncjc5YmtnY29vaWNuMXA4N21vMWVyb0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t Calender link (all working groups)]<br /> <br /> ===+ Zoom Meeting Details ====<br /> <br /> https://dfinity.zoom.us/j/98865672859?pwd=UXorcDNQQzl3Tk5rVTVmRW5lYXdEQT09<br /> <br /> Meeting ID: 988 6567 2859<br /> Passcode: 075319</div>

Dominic.woerner https://wiki.internetcomputer.org/w/index.php?title=Scalability_%26_Performance&diff=2956 2022-08-30T12:32:49Z

<p>Dominic.woerner: </p> <hr /> <div>== Working Group Topic: Scalability &amp; Performance ==<br /> <br /> * DFINITY lead: [https://forum.dfinity.org/u/johan Johan Granström]<br /> * Coordinator: [https://forum.dfinity.org/u/domwoe Dominic Wörner]<br /> * Cadence: Monthly on the third Thursday of every month at 5:30pm CET<br /> * Discord Channel: [https://discord.com/channels/748416164832608337/994942091463512175 Scalability]<br /> * [https://forum.dfinity.org/t/technical-working-group-scalability-performance/14265 Forum Thread]<br /> <br /> First meeting: July 21, 2022 at 5:30pm CET<br /> <br /> [https://calendar.google.com/calendar/u/0?cid=Y19jazBncjc5YmtnY29vaWNuMXA4N21vMWVyb0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t Calender link (all working groups)]<br /> <br /> The Internet Computer provides a unique blockchain platform for decentralized applications. The actor model allows parallel execution of code in a given subnet and the IC can scale horizontally by adding more subnets. Already today, this allows the building of decentralized applications using smart contracts that aren't possible on other blockchains. However, these are still early days for the Internet Computer, and design patterns for building decentralized applications on a global scale are only starting to emerge. The Internet Computer itself is also continuously maturing with performance improvements, new features, and better tooling. The goal of this working group is to foster a regular exchange between R&amp;D at DFINITY and application developers with the following focus:<br /> <br /> * Updates on the relevant R&amp;D roadmap and presentation of ideas<br /> * Collecting and discussing pain points of application developers<br /> * Identification and sharing of best practices and design patterns for building applications on the IC<br /> <br /> <br /> &lt;!-- <br /> Working Group Discussion Thread on the Forum<br /> <br /> All notes and presentation decks will be saved [https://drive.google.com/drive/folders/1JkUkZelJdN0DwNtHfVxl94Ke2lCcMxpe here].<br /> --&gt;</div>

Dominic.woerner https://wiki.internetcomputer.org/w/index.php?title=Developer_Tooling&diff=2955 2022-08-30T12:31:14Z

<p>Dominic.woerner: </p> <hr /> <div>== Working Group Topic: Developer Tooling ==<br /> <br /> * DFINITY lead: [https://forum.dfinity.org/u/dfx-json Jason Ibrahim]<br /> * Coordinator: [https://forum.dfinity.org/u/domwoe Dominic Wörner]<br /> * Cadence: Monthly on the first Thursday of every month at 7pm CET<br /> * Discord Channel: [https://discord.com/channels/748416164832608337/976871731245490237 Developer Tooling]<br /> * [https://forum.dfinity.org/t/technical-working-group-developer-tooling/11941 Forum Thread]<br /> <br /> * First meeting: April 5, 2022 at 7:00pm CET<br /> <br /> [https://calendar.google.com/calendar/u/0?cid=Y19jazBncjc5YmtnY29vaWNuMXA4N21vMWVyb0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t Calender link (all working groups)]</div>

Dominic.woerner https://wiki.internetcomputer.org/w/index.php?title=Scalability_%26_Performance&diff=2649 2022-07-11T07:10:42Z

<p>Dominic.woerner: </p> <hr /> <div>== Working Group Topic: Scalability &amp; Performance ==<br /> <br /> * DFINITY lead: [https://forum.dfinity.org/u/johan Johan Granström]<br /> * Coordinator: [https://forum.dfinity.org/u/domwoe Dominic Wörner]<br /> * Cadence: Monthly on the third Thursday of every month at 5:30pm CET<br /> * Discord Channel: [https://discord.com/channels/748416164832608337/994942091463512175 Scalability]<br /> <br /> First meeting: July 21, 2022 at 5:30pm CET<br /> <br /> [https://calendar.google.com/calendar/u/0?cid=Y19jazBncjc5YmtnY29vaWNuMXA4N21vMWVyb0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t Calender link (all working groups)]<br /> <br /> [https://forum.dfinity.org/t/announcing-technical-working-groups/11781/9 Announcing Technical Working Groups]<br /> <br /> The Internet Computer provides a unique blockchain platform for decentralized applications. The actor model allows parallel execution of code in a given subnet and the IC can scale horizontally by adding more subnets. Already today, this allows the building of decentralized applications using smart contracts that aren't possible on other blockchains. However, these are still early days for the Internet Computer, and design patterns for building decentralized applications on a global scale are only starting to emerge. The Internet Computer itself is also continuously maturing with performance improvements, new features, and better tooling. The goal of this working group is to foster a regular exchange between R&amp;D at DFINITY and application developers with the following focus:<br /> <br /> * Updates on the relevant R&amp;D roadmap and presentation of ideas<br /> * Collecting and discussing pain points of application developers<br /> * Identification and sharing of best practices and design patterns for building applications on the IC<br /> <br /> <br /> &lt;!-- <br /> Working Group Discussion Thread on the Forum<br /> <br /> All notes and presentation decks will be saved [https://drive.google.com/drive/folders/1JkUkZelJdN0DwNtHfVxl94Ke2lCcMxpe here].<br /> --&gt;</div>

Dominic.woerner https://wiki.internetcomputer.org/w/index.php?title=Scalability_%26_Performance&diff=2648 2022-07-11T07:04:57Z

<p>Dominic.woerner: </p> <hr /> <div>== Working Group Topic: Scalability &amp; Performance ==<br /> <br /> * DFINITY lead: [https://forum.dfinity.org/u/johan Johan Granström]<br /> * Coordinator: [https://forum.dfinity.org/u/domwoe Dominic Wörner]<br /> * Cadence: Monthly on the third Thursday of every month at 5:30pm CET<br /> * Discord Channel: [https://discord.com/channels/748416164832608337/994942091463512175 Scalability]<br /> <br /> First meeting: July 21, 2022 at 5:30pm CET<br /> <br /> [https://calendar.google.com/event?action=TEMPLATE&amp;tmeid=NGptNXJubTI5Ym1kMWtnb2RvbHFvbGdibjFfMjAyMjA0MDVUMTUwMDAwWiBjX2NrMGdyNzlia2djb29pY24xcDg3bW8xZXJvQGc&amp;tmsrc=c_ck0gr79bkgcooicn1p87mo1ero%40group.calendar.google.com&amp;scp=ALL Event link]<br /> <br /> [https://forum.dfinity.org/t/announcing-technical-working-groups/11781/9 Announcing Technical Working Groups]<br /> <br /> The Internet Computer provides a unique blockchain platform for decentralized applications. The actor model allows parallel execution of code in a given subnet and the IC can scale horizontally by adding more subnets. Already today, this allows the building of decentralized applications using smart contracts that aren't possible on other blockchains. However, these are still early days for the Internet Computer, and design patterns for building decentralized applications on a global scale are only starting to emerge. The Internet Computer itself is also continuously maturing with performance improvements, new features, and better tooling. The goal of this working group is to foster a regular exchange between R&amp;D at DFINITY and application developers with the following focus:<br /> <br /> * Updates on the relevant R&amp;D roadmap and presentation of ideas<br /> * Collecting and discussing pain points of application developers<br /> * Identification and sharing of best practices and design patterns for building applications on the IC<br /> <br /> <br /> &lt;!-- <br /> Working Group Discussion Thread on the Forum<br /> <br /> All notes and presentation decks will be saved [https://drive.google.com/drive/folders/1JkUkZelJdN0DwNtHfVxl94Ke2lCcMxpe here].<br /> --&gt;</div>

Dominic.woerner https://wiki.internetcomputer.org/w/index.php?title=Scalability_%26_Performance&diff=2647 2022-07-11T07:04:33Z

<p>Dominic.woerner: </p> <hr /> <div>== Working Group Topic: Scalability &amp; Performance ==<br /> <br /> * DFINITY lead: [https://forum.dfinity.org/u/johan Johan Granström]<br /> * Coordinator: [https://forum.dfinity.org/u/domwoe Dominic Wörner]<br /> * Cadence: Monthly on the third Thursday of every month at 5:30pm CET<br /> * Discord Channel: [Scalability https://discord.com/channels/748416164832608337/994942091463512175]<br /> <br /> First meeting: July 21, 2022 at 5:30pm CET<br /> <br /> [https://calendar.google.com/event?action=TEMPLATE&amp;tmeid=NGptNXJubTI5Ym1kMWtnb2RvbHFvbGdibjFfMjAyMjA0MDVUMTUwMDAwWiBjX2NrMGdyNzlia2djb29pY24xcDg3bW8xZXJvQGc&amp;tmsrc=c_ck0gr79bkgcooicn1p87mo1ero%40group.calendar.google.com&amp;scp=ALL Event link]<br /> <br /> [https://forum.dfinity.org/t/announcing-technical-working-groups/11781/9 Announcing Technical Working Groups]<br /> <br /> The Internet Computer provides a unique blockchain platform for decentralized applications. The actor model allows parallel execution of code in a given subnet and the IC can scale horizontally by adding more subnets. Already today, this allows the building of decentralized applications using smart contracts that aren't possible on other blockchains. However, these are still early days for the Internet Computer, and design patterns for building decentralized applications on a global scale are only starting to emerge. The Internet Computer itself is also continuously maturing with performance improvements, new features, and better tooling. The goal of this working group is to foster a regular exchange between R&amp;D at DFINITY and application developers with the following focus:<br /> <br /> * Updates on the relevant R&amp;D roadmap and presentation of ideas<br /> * Collecting and discussing pain points of application developers<br /> * Identification and sharing of best practices and design patterns for building applications on the IC<br /> <br /> <br /> &lt;!-- <br /> Working Group Discussion Thread on the Forum<br /> <br /> All notes and presentation decks will be saved [https://drive.google.com/drive/folders/1JkUkZelJdN0DwNtHfVxl94Ke2lCcMxpe here].<br /> --&gt;</div>

Dominic.woerner https://wiki.internetcomputer.org/w/index.php?title=Scalability_%26_Performance&diff=2644 2022-07-08T08:45:44Z

<p>Dominic.woerner: </p> <hr /> <div>== Working Group Topic: Scalability &amp; Performance ==<br /> <br /> * DFINITY lead: [https://forum.dfinity.org/u/johan Johan Granström]<br /> * Coordinator: [https://forum.dfinity.org/u/domwoe Dominic Wörner]<br /> * Cadence: Monthly on the third Thursday of every month at 5:30pm CET<br /> <br /> First meeting: July 21, 2022 at 5:30pm CET<br /> <br /> [https://calendar.google.com/event?action=TEMPLATE&amp;tmeid=NGptNXJubTI5Ym1kMWtnb2RvbHFvbGdibjFfMjAyMjA0MDVUMTUwMDAwWiBjX2NrMGdyNzlia2djb29pY24xcDg3bW8xZXJvQGc&amp;tmsrc=c_ck0gr79bkgcooicn1p87mo1ero%40group.calendar.google.com&amp;scp=ALL Event link]<br /> <br /> [https://forum.dfinity.org/t/announcing-technical-working-groups/11781/9 Announcing Technical Working Groups]<br /> <br /> The Internet Computer provides a unique blockchain platform for decentralized applications. The actor model allows parallel execution of code in a given subnet and the IC can scale horizontally by adding more subnets. Already today, this allows the building of decentralized applications using smart contracts that aren't possible on other blockchains. However, these are still early days for the Internet Computer, and design patterns for building decentralized applications on a global scale are only starting to emerge. The Internet Computer itself is also continuously maturing with performance improvements, new features, and better tooling. The goal of this working group is to foster a regular exchange between R&amp;D at DFINITY and application developers with the following focus:<br /> <br /> * Updates on the relevant R&amp;D roadmap and presentation of ideas<br /> * Collecting and discussing pain points of application developers<br /> * Identification and sharing of best practices and design patterns for building applications on the IC<br /> <br /> <br /> &lt;!-- <br /> Working Group Discussion Thread on the Forum<br /> <br /> All notes and presentation decks will be saved [https://drive.google.com/drive/folders/1JkUkZelJdN0DwNtHfVxl94Ke2lCcMxpe here].<br /> --&gt;</div>

Dominic.woerner https://wiki.internetcomputer.org/w/index.php?title=Scalability_%26_Performance&diff=2643 2022-07-08T08:03:35Z

<p>Dominic.woerner: Created page with &quot;== Working Group Topic: Scalability &amp; Performance == * DFINITY lead: Johan Granström * Coordinator: [https://forum.dfinity.org/u/domwoe Dominic Wörner] * Cadence: Monthly o...&quot;</p> <hr /> <div>== Working Group Topic: Scalability &amp; Performance ==<br /> <br /> * DFINITY lead: Johan Granström<br /> * Coordinator: [https://forum.dfinity.org/u/domwoe Dominic Wörner]<br /> * Cadence: Monthly on the third Thursday of every month at 5:30pm CET<br /> <br /> First meeting: July 21, 2022 at 5:30pm CET<br /> <br /> [https://calendar.google.com/event?action=TEMPLATE&amp;tmeid=NGptNXJubTI5Ym1kMWtnb2RvbHFvbGdibjFfMjAyMjA0MDVUMTUwMDAwWiBjX2NrMGdyNzlia2djb29pY24xcDg3bW8xZXJvQGc&amp;tmsrc=c_ck0gr79bkgcooicn1p87mo1ero%40group.calendar.google.com&amp;scp=ALL Event link]<br /> <br /> [https://forum.dfinity.org/t/announcing-technical-working-groups/11781/9 Announcing Technical Working Groups]<br /> <br /> The Internet Computer provides a unique blockchain platform for decentralized applications. The actor model allows parallel execution of code in a given subnet and the IC can scale horizontally by adding more subnets. Already today, this allows the building of decentralized applications using smart contracts that aren't possible on other blockchains. However, these are still early days for the Internet Computer, and design patterns for building decentralized applications on a global scale are only starting to emerge. The Internet Computer itself is also continuously maturing with performance improvements, new features, and better tooling. The goal of this working group is to foster a regular exchange between R&amp;D at DFINITY and application developers with the following focus:<br /> <br /> * Updates on the relevant R&amp;D roadmap and presentation of ideas<br /> * Collecting and discussing pain points of application developers<br /> * Identification and sharing of best practices and design patterns for building applications on the IC<br /> <br /> <br /> &lt;!-- <br /> Working Group Discussion Thread on the Forum<br /> <br /> All notes and presentation decks will be saved [https://drive.google.com/drive/folders/1JkUkZelJdN0DwNtHfVxl94Ke2lCcMxpe here].<br /> --&gt;</div>

Dominic.woerner https://wiki.internetcomputer.org/w/index.php?title=Internet_Computer_wiki&diff=2642 2022-07-08T07:57:10Z

<p>Dominic.woerner: </p> <hr /> <div>==Welcome!==<br /> <br /> This is a general source of information about the '''Internet Computer (IC)''', the world's fastest and most powerful blockchain network&lt;ref&gt;https://medium.com/dfinity/the-internet-computers-transaction-speed-and-finality-outpace-other-l1-blockchains-8e7d25e4b2ef&lt;/ref&gt;. Created for and by the IC community, topics vary from cryptography, network governance, user experience, tokenomics, developer tutorials and more.<br /> <br /> ==Introduction to the Internet Computer==<br /> The Internet computer is the fastest and most scalable general-purpose blockchain. It was launched as an open source project by [https://dfinity.org/ DFINITY] in May 2021 with the aim of realising a blockchain singularity through hosting dapps, content, and performing computation for billions of users. In building the Internet Computer there have been a number of notable technological developments in cryptography ([https://medium.com/dfinity/chain-key-technology-one-public-key-for-the-internet-computer-6a3644901e28 chain-key cryptography]), programming languages such as [https://wiki.internetcomputer.org/wiki/Motoko Motoko] and others. <br /> <br /> ===Most common place to start===<br /> * [https://dfinity.org/icig.pdf Internet Computer: Infographic]<br /> &lt;!-- Link is going to nowhere. Should be updated if target is clear. Uncommented for now.<br /> * [https://internetcomputer.org/education#online-courses/ Internet Computer: Online Courses]<br /> --&gt;<br /> * [[Glossary]]<br /> <br /> ===For a general audience===<br /> * [[Internet Computer overview]]<br /> * [[Internet Computer vision]]<br /> * [https://dfinity.org/roadmap/ Internet Computer roadmap]<br /> <br /> ===For a more technical audience===<br /> * [https://eprint.iacr.org/2022/087 &quot;Internet Computer for Geeks&quot; paper]<br /> * The [https://dfinity.org/howitworks &quot;How it works&quot; series] with videos and in-depth articles on various topics.<br /> * [https://www.reddit.com/r/dfinity/comments/ozboyi/megathread_technical_amas/ Technical AMAs on Reddit by different IC and DFINITY teams]<br /> <br /> == Internet Identity Introduction == <br /> One of the core benefits of building on the Internet Computer is that end users do not need to pay fees or use tokens to access and use dapps. As an alternative to authenticating from a wallet, users can authenticate with an Internet Identity. Learn more information about Internet Identity (II), a blockchain authentication framework supported by the Internet Computer:<br /> <br /> * [[What is Internet Identity]]<br /> * [[How to create an Internet Identity]]<br /> * [[Internet Identity technical overview]]<br /> * [https://identity.ic0.app/ Create an Internet Identity]<br /> <br /> ==IC for Dapp Users ==<br /> <br /> If you use or are interested in using dapps on the Internet Computer, this section will help you understand the user experience benefits of the IC, how to use Internet Identity, or find more IC dapps.<br /> <br /> Examples:<br /> * [[Introduction to the Internet Computer for dapp users]]<br /> * [[Index of dapps on the Internet Computer]]<br /> <br /> See more in [[Internet Computer for dapp users]]<br /> <br /> == IC for ICP Token-holders, Stakers, and Neuron Holders==<br /> <br /> The Internet Computer is governed by on-chain governance system called the Network Nervous System (NNS). To participate on governance, users need to stake ICP tokens. This section will explain how the NNS works, ICP tokens, staking, voting, rewards, and options for managing one's ICP.<br /> <br /> Examples:<br /> * [[ICP token]]<br /> * [[Tutorials for acquiring, managing, and staking ICP]]<br /> * [[Staking, voting and rewards]]<br /> * [[Governance of the Internet Computer]]<br /> * [[Network Nervous System]]<br /> * [[Total supply, circulating supply, and staked_ICP]]<br /> <br /> See more in [[Internet Computer token-holders, investors, and neuron holders]].<br /> <br /> == IC for Smart Contract and Dapp Developers ==<br /> <br /> The Internet Computer (IC) is a new platform for executing smart contracts. This section contains information for developers, including links to documentation, developer forums, and relevant dashboards.<br /> <br /> Examples:<br /> * [[Canisters (dapps/smart contracts)]]<br /> * [https://smartcontracts.org/ Developer documentation on smartcontract.org]<br /> * [https://forum.dfinity.org/ IC community developer forum]<br /> &lt;!--* [[Index of libraries for Internet Computer development]]--&gt;<br /> &lt;!--* [[Best practices for a high traffic dapp launch]]--&gt;<br /> * [[Bitcoin integration]]<br /> <br /> If you've been programming smart contracts on Ethereum before, you should read [[The Internet Computer for Ethereum Developers]].<br /> <br /> See more in [[Internet Computer for smart contract and dapp developers]].<br /> <br /> == IC for the Curious, Researchers and Blockchain Enthusiasts ==<br /> <br /> This section is for those interested in how the Internet Computer works under the hood. It touches many different subject areas from cryptography, consensus protocols, virtual machines, operating systems, networking, distributed systems, etc.<br /> <br /> Examples:<br /> * [https://dfinity.org/howitworks/ How the Internet Computer Works]<br /> * [https://dashboard.internetcomputer.org/ Internet Computer dashboard] <br /> * [[Internet Computer performance]]<br /> * [[DFINITY Foundation]]<br /> * [[Bitcoin integration]]<br /> * [[Third-party security audits]]<br /> <br /> See more in [[Internet Computer for researchers and blockchain enthusiasts]].<br /> <br /> == For Node Providers == <br /> Node providers invest in and operate node hardware, which powers the Internet Computer with processing and storage capacity. Running these nodes in data centers provides the high performance and the cost-effectiveness of the Internet Computer. Every node provider is allowed a limited amount of nodes.<br /> * [[Node Provider Onboarding]]<br /> * [[IC OS Installation Runbook - Dell Poweredge]]<br /> * [[IC OS Installation Runbook - Supermicro]]<br /> * [[Storage Runbook]]<br /> * [[Node rewards]]<br /> <br /> == Technical Working Groups == <br /> * [[Identity &amp; Authentication]]<br /> * [[Developer Tooling]]<br /> * [[Ledger &amp; Tokenization]]<br /> * [[Scalability &amp; Performance]]<br /> <br /> == FAQs, Tutorials, and How-tos==<br /> Tutorials are guided introductions to user stories, intended for first-time users and characterized by a shallow learning curve. How-Tos are step-by-step instructions for specific, narrow goals.<br /> <br /> ===FAQs===<br /> * [[FAQ]]<br /> <br /> ===Best Practices===<br /> Example:<br /> * [[Managing ICP holdings]]<br /> * [[Managing Internet Identity]]<br /> * [[Maximizing Voting and NNS Rewards]] <br /> See more in [[Best Practices]]<br /> <br /> === Tutorials ===<br /> Example:<br /> * [[Tutorials for acquiring, managing, and staking ICP]]<br /> * [[How-To: Claim neurons for seed participants]]<br /> * [[How-To: Create an NNS motion proposal]]<br /> * [[How-To: Set your neuron to follow another neuron]]<br /> <br /> <br /> See more in [[How-Tos]].<br /> <br /> ==Contributing to the Wiki==<br /> <br /> === How to contribute ===<br /> Anyone can read the wiki. You can also edit pages, all you need to do is [https://wiki.internetcomputer.org/wiki/Special:CreateAccount create an account]. See more in [[Contributing to the wiki]].<br /> <br /> ==References==</div>

Dominic.woerner https://wiki.internetcomputer.org/w/index.php?title=The_Internet_Computer_for_Ethereum_Developers&diff=2391 2022-05-25T08:44:09Z

<p>Dominic.woerner: Created page with &quot;&lt;br&gt; For many developers, the first contact with a smart contract platform is through Ethereum. Hence, when developers later encounter the Internet Computer (IC) they have man...&quot;</p> <hr /> <div>&lt;br&gt;<br /> For many developers, the first contact with a smart contract platform is through Ethereum. Hence, when developers later encounter the Internet Computer (IC) they have many preconceptions about how things ought to work and this does not always map to the way the Internet Computer works.<br /> <br /> In this article, we’ll try to explain the differences that most developers will encounter and present the differentiating capabilities. Since the language of Ethereum and the Internet Computer slightly differ, we mostly talk in terms common to Ethereum developers and provide a little dictionary in the end. We hope that this is a living article which gets updated by the community over time to provide a comprehensive reference for new developers coming across the IC.<br /> <br /> ===A very brief introduction to the Internet Computer===<br /> <br /> Before diving into a list of specific differences, we’ll give a brief description of the IC as a whole. The IC is a network of mostly independent subnet blockchains, but contracts can interact transparently across subnets. This allows horizontal scaling of the IC by continuously adding subnets. The subnets are managed by the [https://dfinity.org/howitworks/network-nervous-system-nns Network Nervous System (NNS)], essentially a Decentralized Autonomous Organization (DAO), running on the first subnet itself. The IC has a main utility token - ICP - which can be staked in the NNS to participate in governance and has to be converted to cycles in order to pay for resource consumption on the IC. Contracts on the IC are called canisters and contain [https://webassembly.org/ WASM] byte code. This allows to create contracts in a range of programming languages. In addition, there’s [https://dfinity.org/howitworks/motoko Motoko], a programming language that has been purposefully designed to write canisters in the actor model for the IC.<br /> <br /> If you want to dig deeper into mechanics of the Internet Computer have a look at the following resources:<br /> <br /> * [https://dfinity.org/whitepaper.pdf The Internet Computer for Geeks]<br /> * The Internet Computer [https://dfinity.org/howitworks/ “How it works”] series with many in depth articles and videos<br /> * The official [https://smartcontracts.org/ Developer Documentation]<br /> * [https://smartcontracts.org/docs/current/references/ic-interface-spec The Internet Computer Interface Specification]<br /> * The [https://forum.dfinity.org/ Developer Forum] and [https://discord.com/invite/cA7y6ezyE2 Discord]<br /> <br /> ===Differences between Ethereum and the Internet Computer===<br /> <br /> So without further ado, we’ll dive into some of notable differences between Ethereum and the IC. <br /> &lt;br&gt;<br /> &lt;br&gt;<br /> ====User Experience====<br /> &lt;br&gt;<br /> =====External accounts don’t have to pay for gas=====<br /> <br /> The IC implements a “reverse gas” model, where contracts have to pay for their resources in cycles. Hence, a user of a dapp doesn’t need a wallet or tokens to interact with the dapp. Nevertheless, users can still be strongly authenticated to dapps using [https://medium.com/dfinity/internet-identity-the-end-of-usernames-and-passwords-ff45e4861bf7#:~:text=Internet%20Identity%20builds%20on%20the,ID%2C%20or%20fingerprint%20scanner. Internet Identity which is based on the [https://www.w3.org/TR/webauthn-2/ Web Authentication] standard.<br /> <br /> If you wonder how canisters pay for their resources. Every canister has a cycle balance and the balance can be topped up by any other canister. Of course, you can also require users to pay a fee in ICP and then let your canister convert the ICP to cycles, essentially imitating the gas model of Ethereum. Hence, the IC allows for much more flexibility.<br /> &lt;br&gt;<br /> <br /> =====Users can interact with the IC safely from their browsers=====<br /> <br /> The interaction between a user and an application on Ethereum usually looks like the following:<br /> # A user points her browser to the domain of the application.<br /> # The front end of the application is served by a traditional hosting provider.<br /> # Dynamic data from the blockchain is typically proxied by either a centralized backend provided by the application provider or by a service provider like [https://infura.io/ Infura].<br /> # The user connects to the application with her wallet.<br /> # The front end drafts a transaction and asks the wallet to sign and submit the transaction. Even in the case of a non-financial application the user needs to have ETH in her wallet to pay for gas fees.<br /> # The user approves using the wallet and the wallet submits the signed transaction.<br /> # The user waits - depending on the current usage of the network and the provided fees - from 10s of seconds to minutes until the transaction is confirmed. (See [https://ethgasstation.info/ ETH Gas Station] for current costs and waiting times)<br /> <br /> The synergy of a few key innovations allows a user to safely interact with an application on the IC without setting up a wallet, without buying cryptocurrency, and without having to rely on any intermediaries.<br /> <br /> # Chain-key technology and subnets allow for lightweight verification and lower costs because of lower replication and horizontal scaling.<br /> # The reverse gas model allows contracts to be pre-loaded with gas to simplify user onboarding<br /> # Internet Identity allows privacy-preserving authentication to services on the IC using [https://webauthn.guide/ WebAuthentication] and a delegation mechanism. Cryptographic secrets are managed with secure hardware.<br /> # Boundary nodes and [https://dfinity.org/howitworks/response-certification certified asset] contracts allow serving the front end directly from a contract.<br /> <br /> So how does interaction with a dapp on the IC look like?<br /> <br /> # A user points her browser to the domain of the application which is either a ''ic0.app'' domain directly or the browser will be redirected to a ''ic0.app'' domain.<br /> # The user will see that a service worker gets installed which uses the [https://www.npmjs.com/package/@dfinity/agent Java Script agent] to verify the [https://dfinity.org/howitworks/response-certification certified assets] originating from a contract on the IC. The service worker mechanism is workaround until browsers support the IC, either natively or via an extension.<br /> # The user is asked to login with Internet Identity or another authentication method. <br /> # The user can interact with the dapp without paying fees. State-changing updates take seconds and can mostly be hidden from the user by utilizing optimistic ui patterns.<br /> <br /> The best is to try it yourself. Head over to [http://icapps.xyz/ http://icapps.xyz] for example and try a few of the popular apps on the IC.<br /> <br /> &lt;br&gt;<br /> &lt;br&gt;<br /> ====Developer Experience====<br /> &lt;br&gt;<br /> <br /> =====Contracts are upgradable by default=====<br /> <br /> On Ethereum, contracts are immutable. If there is a bug in a contract, there is little a developer can do. This led to clever workarounds like [https://docs.openzeppelin.com/learn/upgrading-smart-contracts proxy contracts] which lead to additional complexity and risks for users. On the IC, contracts are mutable by default. Each contract has an associated list of controllers, which are authorized to upgrade contracts. By setting the controllers an empty list or a black hole contract, you can make your contract immutable. But in the IC community, there is the vision that most contracts will be governed by Decentralized Autonomous Organizations (DAOs) just like the IC itself. The DFINITY foundation is working on the [https://medium.com/dfinity/how-the-service-nervous-system-sns-will-bring-tokenized-governance-to-on-chain-dapps-b74fb8364a5c#:~:text=An%20SNS%20would%20derive%20from,%2C%20permissionless%2C%20and%20decentralized%20manner. Service Nervous System], a customizable turn-key solution to govern services on the IC, inspired by [https://dfinity.org/howitworks/network-nervous-system-nns Network Nervous System] which governs the IC.<br /> &lt;br&gt;<br /> <br /> =====Inter-contract calls are asynchronous and not atomic=====<br /> <br /> The EVM is synchronous and transactions are atomic. This means if a user sends a transaction the transaction is either executed completely or the state is rolled back - only consuming the gas attached to the transaction. This is true independently of the number of contracts involved in the transaction. This property has led to interesting innovations such as Flashloans but severely limits scalability since the entire Ethereum network acts as a single process. On the IC inter-contract calls are asynchronous. Every time you use `await` the state is committed. In case a function traps, the state is only rolled back to the last occurrence of await. You can read more about this [https://smartcontracts.org/docs/current/developer-docs/build/languages/motoko/actors-async/#traps-and-commit-points here] in the documentation. There’s also a [https://forum.dfinity.org/t/we-need-a-defi-subnet/11388/32#world-computers-and-real-world-computers-for-defi-1 great forum post about the different models concerning DeFi].<br /> &lt;br&gt;<br /> <br /> ===== Contracts will be deleted when they are running out of gas =====<br /> <br /> On Ethereum contracts are permanent. While this has some advantages (peace of mind for developers and users), it also has considerable disadvantages (limited scalability). The state of Ethereum is growing without bounds, and there is little incentive for developers to free space in the state. Hence, there are still all those ICO tokens from 2017 in the Ethereum state, although many projects have long been abandoned. On the IC, contracts consume cycles according to their actual resource consumption. Even if contracts won’t be called they consume some cycles, although very little. This is important for the sustainability of the platform. When coming from Ethereum to the IC, developers often are anxious about the cycle consumption and that their contracts will be deleted suddenly. However, there are two effective guards built into the IC.<br /> <br /> # There’s an [https://smartcontracts.org/docs/current/references/ic-interface-spec/#system-api-inspect-message ''inspect_message'' functionality] that lets contracts introspect ingress messages (i.e. messages originating from outside the IC) and decide if they want to process the message. This introspection is not charged.<br /> # The IC can freeze a canister such that it automatically rejects all calls and only the base maintenance has to be paid for. Each canister has a [https://smartcontracts.org/docs/current/references/ic-interface-spec/#ic-create_canister ''freezing_threshold''] which can be set as a period in seconds and essentially guarantees that the IC will freeze the canister such that the canister has a balance to afford the maintenance cost for this period. The default ''freezing_threshold'' is approximately 30 days and should give developers or users ample time to top up the canister before it is garbage collected.<br /> &lt;br&gt;<br /> <br /> =====Gas fees are predictable=====<br /> <br /> In the Ethereum Virtual Machine (EVM), specific operations (Opcodes) have a defined cost in gas, but the exchange rate between ETH and gas is entirely defined by the market. The user can define a ''maxFeePerGas'' that she is willing to pay in a transaction and the individual miner decides if it deems this offer acceptable or not. Since the throughput of Ethereum is highly limited, the price of gas can fluctuate wildly with demand. In addition, the actual price in USD or EUR is even more unpredictable due to the current market price of ETH.<br /> <br /> Similar (but more extensive) to gas in Ethereum, the IC has a set of [https://smartcontracts.org/docs/current/developer-docs/updates/computation-and-storage-costs fixed prices in cycles for various resources]. The main difference however is that the price of cycles is pegged to the XDR, which is based on a basket of the world’s main currencies.<br /> <br /> &lt;br&gt;<br /> ''1 XDR = 1 Trillion cycles''<br /> &lt;br&gt;<br /> <br /> <br /> The exchange rate between XDR and ICP is managed by the NNS. Hence, the actual cost of running a canister is relatively stable and predictable, and independent of the current market price of ICP.<br /> &lt;br&gt;<br /> =====The ICP Token is not part of the system but is implemented as a contract=====<br /> The ICP token has two important roles in the IC:<br /> <br /> # It can be burned to create cycles that are needed to pay for resources on the IC<br /> # It can be locked in neurons to participate in the governance of the IC<br /> <br /> However, ICP does not appear in the system state but is built as a contract running on the NNS subnet. You can find more information about the Ledger canister [https://smartcontracts.org/docs/current/references/ledger here] or [https://www.youtube.com/watch?v=im5HBRd3mqo here].<br /> &lt;br&gt;<br /> &lt;br&gt;<br /> ====Scalability and Costs====<br /> &lt;br&gt;<br /> =====48-bytes are enough to verify the state of the IC=====<br /> <br /> Verifying the EVM state is a resource-intensive process by which a node has to verify the whole blockchain from genesis. It is possible to have light nodes, that verify only the header chain (which is nevertheless growing forever), in addition to relevant parts of the current state, but the infrastructure is not built yet. Hence, most users rely on centralized APIs to access the Ethereum state, most notably [https://infura.io/ Infura]. The Internet Computer in contrast allows clients to verify the state with a constant 48-byte public key. This public key could be hardcoded into software such as browsers or even hardware like Internet of Things devices to let them interact securely with contracts on the IC.<br /> &lt;br&gt;<br /> =====The Internet Computer can scale horizontally=====<br /> <br /> The IC is a network of subnets where contracts can interact transparently across subnets. With increasing demand of the Internet Computer additional subnets can be added by proposals to the NNS.<br /> &lt;br&gt;<br /> =====Contract storage is orders of magnitudes cheaper=====<br /> <br /> Ethereum does not yet implement sharding and every node in the network needs to store and execute every contract and every transaction. On the IC only the nodes in a particular subnet replicate execution and state. While this might decrease security in contrast to Ethereum, it is still much more secure than traditional web services with comparable costs. While storing 1 GB on Ethereum is on the order of hundreds of millions of dollars, it is only a few dollars per year on the IC. This allows hosting entire web applications, music, and even videos on the IC, instead of only stripped backend logic. For an overview of common costs on the IC have look at the [https://smartcontracts.org/docs/current/developer-docs/updates/computation-and-storage-costs Computation and Storage Cost documentation].<br /> &lt;br&gt;<br /> =====There is in general no need to keep track of old blocks=====<br /> <br /> Chain-key technology allows a new (validator) node to quickly sync the state and join the validator set using [https://eprint.iacr.org/2021/339 non-interactive distributed key resharing] instead of syncing and validating the blockchain from genesis. Hence, nodes can safely prune the chain every few minutes. For some applications, however, it’s not enough to only be sure that all state transitions have been authorized by at least 2/3 of the nodes, but an audit trail is required. Examples are the ICP ledger and the NNS. In this case, the audit trail is implemented on the application i.e. contract layer. Thereby, in contrast to Ethereum, contracts have access to the audit trails, and not only outside observers.<br /> <br /> However, in the future there will be two types of subnets. Private and public subnets. For public subnets, it will be possible for an observer to get the raw block data. The first public subnet will be Nervous Network System subnet itself.<br /> &lt;br&gt;<br /> &lt;br&gt;<br /> ====Privacy====<br /> &lt;br&gt;<br /> =====External accounts are not (directly) part of the global state=====<br /> <br /> The world state of Ethereum consists of external accounts (users) and internal accounts (contracts). Each account has an associated ether balance. On the IC only canister principals are part of the state. Each canister principal has an associated cycle balance which is not public by default. This has privacy advantages since a user can interact with canisters on the IC in an authenticated manner without disclosing its principal in the public state. The disadvantage is that user principals can’t hold cycles directly, but need a canister like the cycles wallet.<br /> &lt;br&gt;<br /> =====The global state is not public, but only parts=====<br /> <br /> On Ethereum, everyone can run a full node, and therefore everything is public. Privacy can only be achieved by keeping data off-chain or by using cryptography. On the IC, nodes are permissioned by the NNS and only parts of the IC are public. Besides the API a contract developer defines for the contract itself, the following data is public<br /> <br /> * The subnet of the contract<br /> * The name of the contract<br /> * The hash of the [https://webassembly.org/ WASM] module of the contract<br /> * The controllers of the contract<br /> <br /> In particular, neither the actual byte code nor the (cycles) balance of a contract is public. However, as mentioned earlier, the IC will support public subnets in the future. These subnets will make the raw IC block data available.<br /> &lt;br&gt;<br /> &lt;br&gt;<br /> ====Differentiating Capabilities====<br /> &lt;br&gt;<br /> =====Contracts can trigger themselves=====<br /> <br /> On Ethereum, every state change has to be triggered by an external account. On the IC, however, a canister can use the [https://smartcontracts.org/docs/current/developer-docs/build/languages/motoko/heartbeats ''heartbeat'' functionality] to be triggered by the IC. This opens up a lot of new possibilities. A simple example would be a cron service, which allows other canisters to register themselves to be called.<br /> &lt;br&gt;<br /> =====Contracts have access to cryptographic randomness=====<br /> <br /> The unique consensus algorithm of the IC can be used as a source of cryptographic randomness. This randomness is [https://smartcontracts.org/docs/current/references/motoko-ref/random/ accessible to contracts] and can be used in applications like lotteries or games.<br /> &lt;br&gt;<br /> =====Contracts can hold private keys and sign messages (Soon)=====<br /> <br /> On Ethereum every contract is public. This means a contract can’t hold private information and hence can’t sign messages because there’s no way to securely store a private key. The consensus mechanism of the IC uses a mechanism known as threshold signing where the validator nodes collaborate to create a (BLS) signature without the entire private key existing at all. In an upcoming [https://dfinity.org/howitworks/threshold-ecdsa-signing feature] a similar mechanism will be available for contracts to order the IC to generate threshold ECDSA signatures. These signatures will be verifiable outside the IC just like regular ECDSA signatures. This means you can sign Ethereum or Bitcoin transactions with a contract on the IC or you can create JWTs, verifiable credentials or x.509 certificates.<br /> &lt;br&gt;<br /> =====Contracts can call web services (Soon)=====<br /> <br /> If you need data from the outside world on Ethereum you need oracles that feed this information into a contract on Ethereum. On the IC it will soon be possible to call web services from inside a contract. You can read more about this feature on the [https://forum.dfinity.org/t/enable-canisters-to-make-http-s-requests/9670 forum] or watch the [https://www.youtube.com/watch?v=n_LFCc0ws6o community conversations].<br /> &lt;br&gt;<br /> &lt;br&gt;<br /> ===Dictionary===<br /> contract → canister<br /> <br /> gas → cycles<br /> <br /> shard → subnet (Not entirely true, since Ethereum currently only considers data shards)<br /> <br /> (validator) nodes → replicas</div>

Dominic.woerner https://wiki.internetcomputer.org/w/index.php?title=Internet_Computer_wiki&diff=2390 2022-05-25T08:02:27Z

<p>Dominic.woerner: </p> <hr /> <div>==Welcome!==<br /> <br /> This is a general source of information about the '''Internet Computer (IC)''', the world's fastest and most powerful blockchain network&lt;ref&gt;https://medium.com/dfinity/the-internet-computers-transaction-speed-and-finality-outpace-other-l1-blockchains-8e7d25e4b2ef&lt;/ref&gt;. Created for and by the IC community, topics vary from cryptography, network governance, user experience, tokenomics, developer tutorials and more.<br /> <br /> ==Introduction to the Internet Computer==<br /> The Internet computer is the fastest and most scalable general-purpose blockchain. It was launched as an open source project by [https://dfinity.org/ DFINITY] in May 2021 with the aim of realising a blockchain singularity through hosting dapps, content, and performing computation for billions of users. In building the Internet Computer there have been a number of notable technological developments in cryptography ([https://medium.com/dfinity/chain-key-technology-one-public-key-for-the-internet-computer-6a3644901e28 chain-key cryptography]), programming languages such as [https://wiki.internetcomputer.org/wiki/Motoko Motoko] and others. <br /> <br /> ===Most common place to start===<br /> * [https://dfinity.org/icig.pdf Internet Computer: Infographic]<br /> &lt;!-- Link is going to nowhere. Should be updated if target is clear. Uncommented for now.<br /> * [https://internetcomputer.org/education#online-courses/ Internet Computer: Online Courses]<br /> --&gt;<br /> * [[Glossary]]<br /> <br /> ===For a general audience===<br /> * [[Internet Computer overview]]<br /> * [[Internet Computer vision]]<br /> * [https://dfinity.org/roadmap/ Internet Computer roadmap]<br /> <br /> ===For a more technical audience===<br /> * [https://eprint.iacr.org/2022/087 &quot;Internet Computer for Geeks&quot; paper]<br /> * The [https://dfinity.org/howitworks &quot;How it works&quot; series] with videos and in-depth articles on various topics.<br /> * [https://www.reddit.com/r/dfinity/comments/ozboyi/megathread_technical_amas/ Technical AMAs on Reddit by different IC and DFINITY teams]<br /> <br /> == Internet Identity Introduction == <br /> One of the core benefits of building on the Internet Computer is that end users do not need to pay fees or use tokens to access and use dapps. As an alternative to authenticating from a wallet, users can authenticate with an Internet Identity. Learn more information about Internet Identity (II), a blockchain authentication framework supported by the Internet Computer:<br /> <br /> * [[What is Internet Identity]]<br /> * [[How to create an Internet Identity]]<br /> * [[Internet Identity technical overview]]<br /> * [https://identity.ic0.app/ Create an Internet Identity]<br /> <br /> ==IC for Dapp Users ==<br /> <br /> If you use or are interested in using dapps on the Internet Computer, this section will help you understand the user experience benefits of the IC, how to use Internet Identity, or find more IC dapps.<br /> <br /> Examples:<br /> * [[Introduction to the Internet Computer for dapp users]]<br /> * [[Index of dapps on the Internet Computer]]<br /> <br /> See more in [[Internet Computer for dapp users]]<br /> <br /> == IC for ICP Token-holders, Stakers, and Neuron Holders==<br /> <br /> The Internet Computer is governed by on-chain governance system called the Network Nervous System (NNS). To participate on governance, users need to stake ICP tokens. This section will explain how the NNS works, ICP tokens, staking, voting, rewards, and options for managing one's ICP.<br /> <br /> Examples:<br /> * [[ICP token]]<br /> * [[Tutorials for acquiring, managing, and staking ICP]]<br /> * [[Staking, voting and rewards]]<br /> * [[Governance of the Internet Computer]]<br /> * [[Network Nervous System]]<br /> * [[Total supply, circulating supply, and staked_ICP]]<br /> <br /> See more in [[Internet Computer token-holders, investors, and neuron holders]].<br /> <br /> == IC for Smart Contract and Dapp Developers ==<br /> <br /> The Internet Computer (IC) is a new platform for executing smart contracts. This section contains information for developers, including links to documentation, developer forums, and relevant dashboards.<br /> <br /> Examples:<br /> * [[Canisters (dapps/smart contracts)]]<br /> * [https://smartcontracts.org/ Developer documentation on smartcontract.org]<br /> * [https://forum.dfinity.org/ IC community developer forum]<br /> &lt;!--* [[Index of libraries for Internet Computer development]]--&gt;<br /> &lt;!--* [[Best practices for a high traffic dapp launch]]--&gt;<br /> * [[Bitcoin integration]]<br /> <br /> If you've been programming smart contracts on Ethereum before, you should read [[The Internet Computer for Ethereum Developers]].<br /> <br /> See more in [[Internet Computer for smart contract and dapp developers]].<br /> <br /> == IC for the Curious, Researchers and Blockchain Enthusiasts ==<br /> <br /> This section is for those interested in how the Internet Computer works under the hood. It touches many different subject areas from cryptography, consensus protocols, virtual machines, operating systems, networking, distributed systems, etc.<br /> <br /> Examples:<br /> * [https://dfinity.org/howitworks/ How the Internet Computer Works]<br /> * [https://dashboard.internetcomputer.org/ Internet Computer dashboard] <br /> * [[Internet Computer performance]]<br /> * [[DFINITY Foundation]]<br /> * [[Bitcoin integration]]<br /> <br /> See more in [[Internet Computer for researchers and blockchain enthusiasts]].<br /> <br /> == For Node Providers == <br /> Node providers invest in and operate node hardware, which powers the Internet Computer with processing and storage capacity. Running these nodes in data centers provides the high performance and the cost-effectiveness of the Internet Computer. Every node provider is allowed a limited amount of nodes.<br /> * [[Node Provider Onboarding]]<br /> * [[IC OS Installation Runbook - Supermicro]]<br /> * [[IC OS Installation Runbook - Dell Poweredge]]<br /> * [[Node rewards]]<br /> <br /> == Technical Working Groups == <br /> * [[Identity &amp; Authentication]]<br /> * [[Developer Tooling]]<br /> * [[Ledger &amp; Tokenization]]<br /> <br /> == FAQs, Tutorials, and How-tos==<br /> Tutorials are guided introductions to user stories, intended for first-time users and characterized by a shallow learning curve. How-Tos are step-by-step instructions for specific, narrow goals.<br /> <br /> ===FAQs===<br /> * [[FAQ]]<br /> <br /> ===Best Practices===<br /> Example:<br /> * [[Managing ICP holdings]]<br /> * [[Managing Internet Identity]]<br /> * [[Maximizing Voting and NNS Rewards]] <br /> See more in [[Best Practices]]<br /> <br /> === Tutorials ===<br /> Example:<br /> * [[Tutorials for acquiring, managing, and staking ICP]]<br /> * [[How-To: Claim neurons for seed participants]]<br /> * [[How-To: Create an NNS motion proposal]]<br /> * [[How-To: Set your neuron to follow another neuron]]<br /> <br /> <br /> See more in [[How-Tos]].<br /> <br /> ==Contributing to the Wiki==<br /> <br /> === How to contribute ===<br /> Anyone can read the wiki. You can also edit pages, all you need to do is [https://wiki.internetcomputer.org/wiki/Special:CreateAccount create an account]. See more in [[Contributing to the wiki]].<br /> <br /> ==References==</div>

Dominic.woerner https://wiki.internetcomputer.org/w/index.php?title=Internet_Computer_for_smart_contract_and_dapp_developers&diff=2389 2022-05-25T07:57:21Z

<p>Dominic.woerner: </p> <hr /> <div><br /> <br /> ==Intended Audience==<br /> <br /> This article is an entry point for developers interested in building smart contracts and dapps on the IC.<br /> <br /> ==Developer Documentation==<br /> <br /> ===Key Concepts===<br /> <br /> * [[Canisters (dapps/smart contracts)]]<br /> * [[Internet Identity technical overview]]<br /> * [[Neuron attributes and commands]]<br /> <br /> ===Building Dapps=== <br /> * [[Index of libraries for Internet Computer development]]<br /> * [[Best practices for a high traffic dapp launch]]<br /> * [[Current limitations of the Internet Computer]]<br /> * [[Bitcoin integration]]<br /> * [https://dfinity.frontify.com/d/XzkdhhDptijE/dfinity-brand-guide#/internet-computer/powered-by-badges-1 &quot;Powered by the IC&quot; badges]<br /> * [[Dealing with cycles limit exceeded errors]]<br /> * [[Comparing Canister Cycles vs Performance Counter]]<br /> <br /> ==Developer Community==<br /> <br /> * A common resource for developers unblocking each other is the [https://forum.dfinity.org/ developer forum]. Topics there include things such as help with SDK installation, Motoko, canister troubleshooting, and designs.<br /> <br /> * [https://smartcontracts.org/ Developer documentation on smartcontract.org]<br /> * [https://forum.dfinity.org/ IC community developer forum]<br /> * [https://discord.com/invite/cA7y6ezyE2 IC community developer Discord]</div>

Dominic.woerner https://wiki.internetcomputer.org/w/index.php?title=Internet_Computer_wiki&diff=2357 2022-05-24T10:13:21Z

<p>Dominic.woerner: </p> <hr /> <div>==Welcome!==<br /> <br /> This is a general source of information about the '''Internet Computer (IC)''', the world's fastest and most powerful blockchain network&lt;ref&gt;https://medium.com/dfinity/the-internet-computers-transaction-speed-and-finality-outpace-other-l1-blockchains-8e7d25e4b2ef&lt;/ref&gt;. Created for and by the IC community, topics vary from cryptography, network governance, user experience, tokenomics, developer tutorials and more.<br /> <br /> ==Introduction to the Internet Computer==<br /> The Internet computer is the fastest and most scalable general-purpose blockchain. It was launched as an open source project by [https://dfinity.org/ DFINITY] in May 2021 with the aim of realising a blockchain singularity through hosting dapps, content, and performing computation for billions of users. In building the Internet Computer there have been a number of notable technological developments in cryptography ([https://medium.com/dfinity/chain-key-technology-one-public-key-for-the-internet-computer-6a3644901e28 chain-key cryptography]), programming languages such as [https://wiki.internetcomputer.org/wiki/Motoko Motoko] and others. <br /> <br /> ===Most common place to start===<br /> * [https://dfinity.org/icig.pdf Internet Computer: Infographic]<br /> &lt;!-- Link is going to nowhere. Should be updated if target is clear. Uncommented for now.<br /> * [https://internetcomputer.org/education#online-courses/ Internet Computer: Online Courses]<br /> --&gt;<br /> * [[Glossary]]<br /> <br /> ===For a general audience===<br /> * [[Internet Computer overview]]<br /> * [[Internet Computer vision]]<br /> * [https://dfinity.org/roadmap/ Internet Computer roadmap]<br /> <br /> ===For a more technical audience===<br /> * [https://eprint.iacr.org/2022/087 &quot;Internet Computer for Geeks&quot; paper]<br /> * The [https://dfinity.org/howitworks &quot;How it works&quot; series] with videos and in-depth articles on various topics.<br /> * [https://www.reddit.com/r/dfinity/comments/ozboyi/megathread_technical_amas/ Technical AMAs on Reddit by different IC and DFINITY teams]<br /> <br /> == Internet Identity Introduction == <br /> One of the core benefits of building on the Internet Computer is that end users do not need to pay fees or use tokens to access and use dapps. As an alternative to authenticating from a wallet, users can authenticate with an Internet Identity. Learn more information about Internet Identity (II), a blockchain authentication framework supported by the Internet Computer:<br /> <br /> * [[What is Internet Identity]]<br /> * [[How to create an Internet Identity]]<br /> * [[Internet Identity technical overview]]<br /> * [https://identity.ic0.app/ Create an Internet Identity]<br /> <br /> ==IC for Dapp Users ==<br /> <br /> If you use or are interested in using dapps on the Internet Computer, this section will help you understand the user experience benefits of the IC, how to use Internet Identity, or find more IC dapps.<br /> <br /> Examples:<br /> * [[Introduction to the Internet Computer for dapp users]]<br /> * [[Index of dapps on the Internet Computer]]<br /> <br /> See more in [[Internet Computer for dapp users]]<br /> <br /> == IC for ICP Token-holders, Stakers, and Neuron Holders==<br /> <br /> The Internet Computer is governed by on-chain governance system called the Network Nervous System (NNS). To participate on governance, users need to stake ICP tokens. This section will explain how the NNS works, ICP tokens, staking, voting, rewards, and options for managing one's ICP.<br /> <br /> Examples:<br /> * [[ICP token]]<br /> * [[Tutorials for acquiring, managing, and staking ICP]]<br /> * [[Staking, voting and rewards]]<br /> * [[Governance of the Internet Computer]]<br /> * [[Network Nervous System]]<br /> * [[Total supply, circulating supply, and staked_ICP]]<br /> <br /> See more in [[Internet Computer token-holders, investors, and neuron holders]].<br /> <br /> == IC for Smart Contract and Dapp Developers ==<br /> <br /> The Internet Computer (IC) is a new platform for executing smart contracts. This section contains information for developers, including links to documentation, developer forums, and relevant dashboards.<br /> <br /> Examples:<br /> * [[Canisters (dapps/smart contracts)]]<br /> * [https://smartcontracts.org/ Developer documentation on smartcontract.org]<br /> * [https://forum.dfinity.org/ IC community developer forum]<br /> &lt;!--* [[Index of libraries for Internet Computer development]]--&gt;<br /> &lt;!--* [[Best practices for a high traffic dapp launch]]--&gt;<br /> * [[Bitcoin integration]]<br /> <br /> See more in [[Internet Computer for smart contract and dapp developers]].<br /> <br /> == IC for the Curious, Researchers and Blockchain Enthusiasts ==<br /> <br /> This section is for those interested in how the Internet Computer works under the hood. It touches many different subject areas from cryptography, consensus protocols, virtual machines, operating systems, networking, distributed systems, etc.<br /> <br /> Examples:<br /> * [https://dfinity.org/howitworks/ How the Internet Computer Works]<br /> * [https://dashboard.internetcomputer.org/ Internet Computer dashboard] <br /> * [[Internet Computer performance]]<br /> * [[DFINITY Foundation]]<br /> * [[Bitcoin integration]]<br /> <br /> See more in [[Internet Computer for researchers and blockchain enthusiasts]].<br /> <br /> == For Node Providers == <br /> Node providers invest in and operate node hardware, which powers the Internet Computer with processing and storage capacity. Running these nodes in data centers provides the high performance and the cost-effectiveness of the Internet Computer. Every node provider is allowed a limited amount of nodes.<br /> * [[Node Provider Onboarding]]<br /> * [[IC OS Installation Runbook - Supermicro]]<br /> * [[IC OS Installation Runbook - Dell Poweredge]]<br /> * [[Node rewards]]<br /> <br /> == Technical Working Groups == <br /> * [[Identity &amp; Authentication]]<br /> * [[Developer Tooling]]<br /> * [[Ledger &amp; Tokenization]]<br /> <br /> == FAQs, Tutorials, and How-tos==<br /> Tutorials are guided introductions to user stories, intended for first-time users and characterized by a shallow learning curve. How-Tos are step-by-step instructions for specific, narrow goals.<br /> <br /> ===FAQs===<br /> * [[FAQ]]<br /> <br /> ===Best Practices===<br /> Example:<br /> * [[Managing ICP holdings]]<br /> * [[Managing Internet Identity]]<br /> * [[Maximizing Voting and NNS Rewards]] <br /> See more in [[Best Practices]]<br /> <br /> === Tutorials ===<br /> Example:<br /> * [[Tutorials for acquiring, managing, and staking ICP]]<br /> * [[How-To: Claim neurons for seed participants]]<br /> * [[How-To: Create an NNS motion proposal]]<br /> * [[How-To: Set your neuron to follow another neuron]]<br /> <br /> <br /> See more in [[How-Tos]].<br /> <br /> ==Contributing to the Wiki==<br /> <br /> === How to contribute ===<br /> Anyone can read the wiki. You can also edit pages, all you need to do is [https://wiki.internetcomputer.org/wiki/Special:CreateAccount create an account]. See more in [[Contributing to the wiki]].<br /> <br /> ==References==</div>

Dominic.woerner https://wiki.internetcomputer.org/w/index.php?title=Internet_Computer_wiki&diff=2356 2022-05-24T07:31:35Z

<p>Dominic.woerner: </p> <hr /> <div>==Welcome!==<br /> <br /> This is a general source of information about the '''Internet Computer (IC)''', the world's fastest and most powerful blockchain network&lt;ref&gt;https://medium.com/dfinity/the-internet-computers-transaction-speed-and-finality-outpace-other-l1-blockchains-8e7d25e4b2ef&lt;/ref&gt;. Created for and by the IC community, topics vary from cryptography, network governance, user experience, tokenomics, developer tutorials and more.<br /> <br /> ==Introduction to the Internet Computer==<br /> The Internet computer is the fastest and most scalable general-purpose blockchain. It was launched as an open source project by [https://dfinity.org/ DFINITY] in May 2021 with the aim of realising a blockchain singularity through hosting dapps, content, and performing computation for billions of users. In building the Internet Computer there have been a number of notable technological developments in cryptography ([https://medium.com/dfinity/chain-key-technology-one-public-key-for-the-internet-computer-6a3644901e28 chain-key cryptography]), programming languages such as [https://wiki.internetcomputer.org/wiki/Motoko Motoko] and others. <br /> <br /> ===Most common place to start===<br /> * [https://dfinity.org/icig.pdf Internet Computer: Infographic]<br /> &lt;!-- Link is going to nowhere. Should be updated if target is clear. Uncommented for now.<br /> * [https://internetcomputer.org/education#online-courses/ Internet Computer: Online Courses]<br /> --&gt;<br /> * [[Glossary]]<br /> <br /> ===For a general audience===<br /> * [[Internet Computer overview]]<br /> * [[Internet Computer vision]]<br /> * [https://dfinity.org/roadmap/ Internet Computer roadmap]<br /> <br /> ===For a more technical audience===<br /> * [https://eprint.iacr.org/2022/087 &quot;Internet Computer for Geeks&quot; paper]<br /> * [https://www.reddit.com/r/dfinity/comments/ozboyi/megathread_technical_amas/ Technical AMAs on Reddit by different IC and DFINITY teams]<br /> <br /> == Internet Identity Introduction == <br /> One of the core benefits of building on the Internet Computer is that end users do not need to pay fees or use tokens to access and use dapps. As an alternative to authenticating from a wallet, users can authenticate with an Internet Identity. Learn more information about Internet Identity (II), a blockchain authentication framework supported by the Internet Computer:<br /> <br /> * [[What is Internet Identity]]<br /> * [[How to create an Internet Identity]]<br /> * [[Internet Identity technical overview]]<br /> * [https://identity.ic0.app/ Create an Internet Identity]<br /> <br /> ==IC for Dapp Users ==<br /> <br /> If you use or are interested in using dapps on the Internet Computer, this section will help you understand the user experience benefits of the IC, how to use Internet Identity, or find more IC dapps.<br /> <br /> Examples:<br /> * [[Introduction to the Internet Computer for dapp users]]<br /> * [[Index of dapps on the Internet Computer]]<br /> <br /> See more in [[Internet Computer for dapp users]]<br /> <br /> == IC for ICP Token-holders, Stakers, and Neuron Holders==<br /> <br /> The Internet Computer is governed by on-chain governance system called the Network Nervous System (NNS). To participate on governance, users need to stake ICP tokens. This section will explain how the NNS works, ICP tokens, staking, voting, rewards, and options for managing one's ICP.<br /> <br /> Examples:<br /> * [[ICP token]]<br /> * [[Tutorials for acquiring, managing, and staking ICP]]<br /> * [[Staking, voting and rewards]]<br /> * [[Governance of the Internet Computer]]<br /> * [[Network Nervous System]]<br /> * [[Total supply, circulating supply, and staked_ICP]]<br /> <br /> See more in [[Internet Computer token-holders, investors, and neuron holders]].<br /> <br /> == IC for Smart Contract and Dapp Developers ==<br /> <br /> The Internet Computer (IC) is a new platform for executing smart contracts. This section contains information for developers, including links to documentation, developer forums, and relevant dashboards.<br /> <br /> Examples:<br /> * [[Canisters (dapps/smart contracts)]]<br /> * [https://smartcontracts.org/ Developer documentation on smartcontract.org]<br /> * [https://forum.dfinity.org/ IC community developer forum]<br /> &lt;!--* [[Index of libraries for Internet Computer development]]--&gt;<br /> &lt;!--* [[Best practices for a high traffic dapp launch]]--&gt;<br /> * [[Bitcoin integration]]<br /> <br /> See more in [[Internet Computer for smart contract and dapp developers]].<br /> <br /> == IC for the Curious, Researchers and Blockchain Enthusiasts ==<br /> <br /> This section is for those interested in how the Internet Computer works under the hood. It touches many different subject areas from cryptography, consensus protocols, virtual machines, operating systems, networking, distributed systems, etc.<br /> <br /> Examples:<br /> * [https://dfinity.org/howitworks/ How the Internet Computer Works]<br /> * [https://dashboard.internetcomputer.org/ Internet Computer dashboard] <br /> * [[Internet Computer performance]]<br /> * [[DFINITY Foundation]]<br /> * [[Bitcoin integration]]<br /> <br /> See more in [[Internet Computer for researchers and blockchain enthusiasts]].<br /> <br /> == For Node Providers == <br /> Node providers invest in and operate node hardware, which powers the Internet Computer with processing and storage capacity. Running these nodes in data centers provides the high performance and the cost-effectiveness of the Internet Computer. Every node provider is allowed a limited amount of nodes.<br /> * [[Node Provider Onboarding]]<br /> * [[IC OS Installation Runbook - Supermicro]]<br /> * [[IC OS Installation Runbook - Dell Poweredge]]<br /> * [[Node rewards]]<br /> <br /> == Technical Working Groups == <br /> * [[Identity &amp; Authentication]]<br /> * [[Developer Tooling]]<br /> * [[Ledger &amp; Tokenization]]<br /> <br /> == FAQs, Tutorials, and How-tos==<br /> Tutorials are guided introductions to user stories, intended for first-time users and characterized by a shallow learning curve. How-Tos are step-by-step instructions for specific, narrow goals.<br /> <br /> ===FAQs===<br /> * [[FAQ]]<br /> <br /> ===Best Practices===<br /> Example:<br /> * [[Managing ICP holdings]]<br /> * [[Managing Internet Identity]]<br /> * [[Maximizing Voting and NNS Rewards]] <br /> See more in [[Best Practices]]<br /> <br /> === Tutorials ===<br /> Example:<br /> * [[Tutorials for acquiring, managing, and staking ICP]]<br /> * [[How-To: Claim neurons for seed participants]]<br /> * [[How-To: Create an NNS motion proposal]]<br /> * [[How-To: Set your neuron to follow another neuron]]<br /> <br /> <br /> See more in [[How-Tos]].<br /> <br /> ==Contributing to the Wiki==<br /> <br /> === How to contribute ===<br /> Anyone can read the wiki. You can also edit pages, all you need to do is [https://wiki.internetcomputer.org/wiki/Special:CreateAccount create an account]. See more in [[Contributing to the wiki]].<br /> <br /> ==References==</div>

Dominic.woerner