Internet Computer Wiki - User contributions [en]

Node Deployment Guide

2023-08-07T13:13:41Z

Jens:

This runbook covers all steps necessary to install the Internet Computer Operating System (IC-OS).

The physical machine is expected to be racked and stacked according to its respective manual.

If you encounter issues through any of these steps, check the [[Node Provider Troubleshooting]] page. If that does not solve your problem, you are encouraged to ask for assistance in the [[Node Provider Matrix channel]].

❗️❗️❗️DFINITY does ''not'' offer live support for Node Providers attempting to onboard nodes.

== 1. Choose onboarding path (HSM vs no HSM) ==
If you chose the [[Node Provider Onboarding#6. Choose onboarding path .28HSM vs no HSM.29|HSM Node Provider Onboarding Path]], follow the [[NitroKey HSM installation runbook]] to onboard your nodes.

If you chose to onboard '''without''' a Nitrokey HSM, '''continue to the next step.'''

== 2. Obtain requirements ==
* A USB (3.0 speed that can hold at least 4GB) to put the image file on.
** Faster USBs will allow the process to go much faster.
* The <code>node_operator_private_key.pem</code> for your data center (Acquired from [[Node Provider Onboarding#7. Setup the Node Operator keys|Node Provider Onboarding step 7]])
* It is recommended that each server have a label with the BMC's MAC address for ease of identification in future dashboard upgrades.

== 3. Download installation image ==
Download the latest release of the '''IC-OS USB Installer Image''' and the '''corresponding checksum''' from the [https://dashboard.internetcomputer.org/releases Internet Computer Dashboard Releases].

* Note that you should always use a release that is less than 6 weeks old in order to ensure that your node can keep up with the blockchain.

== 4. Verify checksum and unarchive file ==
=== Mac OS X ===
# Open the Terminal and type:
#: <syntaxhighlight lang="shell">shasum -a 256 ~/Downloads/disk-img.tar.gz</syntaxhighlight>
# Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#: Open the Terminal and type: <syntaxhighlight lang="shell">tar xzvf ~/Downloads/disk-img.tar.gz</syntaxhighlight>

=== Linux / Ubuntu ===
# Open the Terminal and type:
#: <syntaxhighlight lang="shell">sha256sum ~/Downloads/disk-img.tar.gz</syntaxhighlight>
# Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#: Open the Terminal and type: <syntaxhighlight lang="shell">tar xzvf ~/Downloads/disk-img.tar.gz</syntaxhighlight>

=== Windows ===
# Open PowerShell and type:
#: <syntaxhighlight lang="shell">Get-FileHash -Algorithm SHA256 .\Downloads\disk-img.tar.gz</syntaxhighlight>
# Compare the calculated checksum with the '''IC-OS installation image checksum''' file downloaded in the previous step. '''Warning:''' Only continue if they are identical, otherwise please post your issue in the [[Node Provider Matrix channel]].
#: Open PowerShell and type: <syntaxhighlight lang="shell">tar xzvf .\Downloads\disk-img.tar.gz</syntaxhighlight>

== 5. Create Bootable USB Stick ==
=== Mac OS X ===
# Open the Terminal and type:
#:<syntaxhighlight lang="shell">diskutil list</syntaxhighlight>
# All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive:
#:<syntaxhighlight lang="shell">sudo diskutil unmount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/disk4s1</syntaxhighlight>
# The file path is an example. Use the absolute path to the downloaded image. '''Warning:''' You risk losing your own data if you specify a wrong device.
#:<syntaxhighlight lang="shell">sudo dd if=/Users/YOUR_USER_NAME/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M</syntaxhighlight>If you get a “device is busy” error from the dd command, you can try running the following command to unmount all of the partitions on the disk, then re-run the dd command:
#:<syntaxhighlight lang="shell">sudo diskutil unmountDisk /dev/YOUR_USB_DEVICE # E.g. /dev/disk4</syntaxhighlight>

=== Linux / Ubuntu ===
# Open the Terminal and type
#:<syntaxhighlight lang="shell">blkid</syntaxhighlight>
# All available drives should be shown. Identify which device corresponds to your USB stick. You may need to unmount the USB drive:
#:<syntaxhighlight lang="shell">sudo diskutil unmount /dev/YOUR_USB_DEVICE_MOUNTED_PARTITION # E.g. /dev/sdb1</syntaxhighlight>
# Replace ''/dev/YOUR_USB_DEVICE'' with the device that corresponds to your USB stick. '''Warning:''' You risk losing your own data if you specify a wrong drive.
#:<syntaxhighlight lang="shell">sudo dd if=~/Downloads/disk.img of=/dev/YOUR_USB_DEVICE bs=1M</syntaxhighlight>

=== Windows ===
# Download and install [https://rufus.ie/en/ Rufus Portable]
# Start Rufus
# Select the USB stick under device and select the previously downloaded IC-OS disk image and press start
#: [[File:05.png|480px|screenshot]]
# You may see some warnings. Make sure you don't have any other USBs in your computer and chose OK
#: [[File:06.png|480px|screenshot]]
#: [[File:07.png|480px|screenshot]]
# The "Ready" bar will go from left to right as it completes.

== 6. Add configuration ==

=== A. Open Config.ini in a text editor ===

==== '''Mac OS X''' ====

# Open Finder. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again.
#:[[File:mac_01.png|580px|screenshot]]
# Double-click <code>config.ini</code> to open it in TextEdit.

===='''Linux'''====

# Open the File Manager. You should now be able to see the CONFIG partition. If it's not visible, remove the USB and insert it again.
#:[[File:linux_01.png|580px|screenshot]]
# Double-click <code>config.ini</code> to open it in KWrite.

==== '''Windows''' ====

# Open the Disk Management utility with a right click on the Start menu
#:[[File:09-b.png|300px|screenshot]]#:
# Right click the CONFIG partition
# Select Change drive letter or paths...
#:[[File:10-b.png|780px|screenshot]]
# Select any letter from the drop-down list
#:[[File:11-b.png|480px|screenshot]]
# Click OK.
# You should now be able to see the CONFIG partition in your Windows Explorer. Select the <code>config.ini</code> configuration file
#:[[File:12-b.png|780px|screenshot]]
# Click on Edit to open it.

=== B. Edit Config.ini ===

# Insert your IPv6 prefix, subnet and gateway.
#:[[File:Edit config ini.png|580px|screenshot]]
#:* The IPv6 prefix should consist of four groups of hexadecimal digits, separated by colons (':'). Each group can contain up to four hex digits.
#:* For example, a valid prefix could look like this: <code>2a00:fb01:400:100</code>
#:*'''Important:'''
#:** The prefix should not have a trailing ':'
#:** IPv6 CIDR notation allows for a double colon ('::') to represent consecutive groups of zeroes in an address. However, the prefix configuration in this context does '''not''' support '::'. The '::' shorthand should '''not''' be used. Even if some groups are all zeros, they must be explicitly written out.
# Save the changes.
#:* If you have trouble saving this file directly, you may need to save to a known location first, then copy the file into place.
#:* If you need help, please do not hesitate to post your issue in the [[Node Provider Matrix channel]].
#:*:[[File:mac_03.png|580px|screenshot]]

=== C. Copy Node Operator private key to config partition ===

# Copy <code>node_operator_private_key.pem</code> (created in [[Node Provider Onboarding#7. Setup the Node Operator keys|Node Provider Onboarding step 7]]) to the <code>CONFIG</code> partition. This file should have the name <code>node_operator_private_key.pem</code>, and sit next to <code>config.ini</code>, NOT inside the <code>ssh_authorized_keys</code> folder.

== 7. Connect Crash Cart ==
# In order to configure the UEFI and initiate the installation of the IC-OS, please connect a crash cart to the physical machine.
# Plug-in the VGA/Video, keyboard and IC-OS USB stick
#: [[File:08.png|580px|screenshot]]

== 8. UEFI Setup and Boot Menu ==
Use the related page below to set up the BIOS/UEFI according to your hardware vendor.

* [[Node Provider Machine Hardware Guide#Gen 2 Node Machine requirements|Gen2 hardware]]
**[[IC-OS Installation - UEFI Configuration - Gen2 Dell]]
** [[IC-OS Installation - UEFI Configuration - Gen2 Supermicro]]
** [[IC-OS Installation - UEFI Configuration - Gen2 Gigabyte]]
** 
* [[Node Provider Machine Hardware Guide#Gen 1 Node Machine requirements|Gen1 hardware]]
**[[IC-OS Installation - UEFI Configuration - Gen1 Dell|IC-OS Installation - UEFI Configuration - Gen1 Dell (Poweredge R6525)]]
** [[IC-OS Installation - UEFI Configuration - Gen1 Supermicro]]
***
'''Important:''' Do NOT enable the RAID bios setting. Doing so will cause issues with the IC-OS installation.

Resume from this point when you are finished configuring the BIOS.

== 9. IC-OS Installation ==
# Please wait while the USB Installer is booting up. This process can take up to 3 minutes.
#: [[File:35-sm.png|580px|screenshot]]
# The IC-OS installation starts. Please keep an eye on the progress. This part can take up to 10 minutes. Please remember to check the [[Possible Node Onboarding Errors]] page if you encounter any errors.
#:[[File:36-sm.png|580px|screenshot]]
# If the installation finished successfully, it will initiate a reboot.
#:[[File:38-sm.png|580px|screenshot]] 
== 10. First Boot ==
Please remember to check the [[Possible Node Onboarding Errors]] page if you encounter any errors onboarding.

'''🚨 Do NOT re-try the IC-OS installation after completing this section, as this can cause duplication within the registry.'''
# Once you see this message, you may unplug the USB stick and VGA/Video.
#:[[File:Node join message.png|580px|screenshot]]

Congratulations! Your machine successfully joined the Internet Computer! The machine has joined the IC and the Node Provider will start receiving rewards!

🚨 Again: Once you reach this stage and see this message, '''do not attempt to restart the onboarding process.''' Doing so may cause duplicate entries in the registry.

== 11. Verify node onboarding ==

# Verify that your node was successfully onboarded by checking its status on the [https://dashboard.internetcomputer.org/ dashboard] is set to either “Awaiting Subnet” or “Active in Subnet”.
#* The dashboard can be searched by your Node Provider principal. There, you should see the Node ID of your node (Node ID outputted in step 10).
#* If the status of your node is not either “Awaiting Subnet” or “Active in Subnet”, or if it is not listed under your Node Provider principal, you should contact the [[Node Provider Matrix channel]] for assistance.
#*:[[File:Dashboard-node-verification.png|thumb|998x998px]]

Node Provider Networking Guide

2023-08-07T13:12:08Z

Jens:

This guide is designed to provide an overview of the networking requirements and guide Node Providers through setting up their servers into a rack with functioning networking.

Configuring networks is not trivial. You should be familiar with IP networking, network equipment and network cabling.

Resources to learn about networking:

* [https://learningnetwork.cisco.com/s/article/200-301-ccna-study-materials CCNA Study Materials]
* Kevin Wallace [https://www.youtube.com/@kwallaceccie YouTube Training Videos]

'''DFINITY does not provide support for network configuration.'''

If a situation arises where you need technical assistance, keep decentralization and security in mind. Use a local technician you personally know and carefully monitor their work.

== Requirements ==
To join your servers to the Internet Computer (IC) you will need:

* 10G Network equipment
** [[wikipedia:Small_Form-factor_Pluggable|SFP+]] or [[wikipedia:10_Gigabit_Ethernet|Ethernet]]
** Switch(es)
** Cabling
** Quantity determined by number of nodes deployed
* Rackspace in a data center
* Internet connection
** Bandwidth
*** ~300Mbps per node
*** Ingress/egress ratio is currently 1:1. We expect egress (serving responses to client queries) to increase faster than ingress in the future.
*** This should guide how many servers to deploy and the appropriate ISP connection speed
*** E.g. a 1Gbps connection will support up to 3 IC nodes.
** One IPv6 /64 subnet - each node gets multiple IPv6 addresses
** One IPv4 address for every 4 nodes in a given data center per node provider (IPv4 addresses cannot be shared between node providers). See [[Node Provider Networking Guide#Appendix 1: Number of IPv4 Addresses Required|Appendix 1]] for table.
** '''All IP addresses are assigned statically''' and automatically by IC-OS
*** This is configured in the [[IC-OS Installation Runbook#6. Add configuration|IC-OS Installation Runbook]]

== Network Cabling ==
When racking and stacking your servers, ensure the '''first two 10G network ports''' on each server are connected to the 10G switch.

[[File:Supermicro 1124US-TNRP 1U server rear photo diagram.png]]

For example, on a Supermicro 1U server, the bottom two ports are considered ports 1 and 2 and will be enumerated by Linux in this order. Connect the bottom two ports to the switch.

Servers from other vendors will differ! See the server documentation for guidance.

This is subject to change - the IC-OS network configuration logic is undergoing improvements to make it more flexible.

Connect the 10G switch to the ISP endpoint - this could be the Top Of Rack (TOR) switch or other box.

== Network Configuration ==
Node machines require:

* The ability to acquire a public static IPv6 address on a /64 subnet
* An IPv6 gateway to communicate with other nodes on the broad internet
* Unfiltered internet access

One of every four nodes requires:

* The ability to acquire a public static IPv4 address
* An IPv4 gateway to communicate with other nodes on the broad internet
* Unfiltered internet access

There are many many ways to configure the network and some details depend on the ISP and data center. Here are some [[Example Network Configuration Scenarios]].

== BMC Setup Recommendations ==

=== What’s a BMC? ===
The [[wikipedia:Intelligent_Platform_Management_Interface#Baseboard_management_controller|Baseboard Management Controller (BMC)]] grants control of the underlying server hardware.

BMC’s have notoriously poor security. Vendors may name their implementation differently (Dell -> iDRAC, HPE -> iLO, etc.).

=== Recommendations ===

==== Change the password ====
BMC’s usually come with a common password. Log in via crash cart, KVM or the web interface and change it to something [https://krebsonsecurity.com/password-dos-and-donts/ strong].

==== No broad internet access ====
It is highly recommended: '''do not expose your BMC''' to the broad internet. This is a safety precaution against attackers.

Options:

* Don’t connect the BMC to the internet.
** Maintenance or node recovery will require physical access in this case.
** Any BMC activities occur via SSH on the host (unreliable on many mainboard vendors) or via crash cart.
* Connect the BMC to a separate dumb switch, and the dumb switch connects to a Rack Mounted Unit (RMU).
* Connect the BMC to a managed switch, and create a separate VLAN

This can get complicated. It’s outside the scope of this document to explain how to do this.

Resources:

* [https://security.stackexchange.com/questions/46351/best-practice-for-accessing-management-port-of-firewall StackExchange - Best practice for accessing management port of firewall]
* [https://www.supermicro.com/products/nfo/files/IPMI/Best_Practices_BMC_Security.pdf Supermicro Guidance]
* [https://www.unicomengineering.com/blog/ipmi-best-practices/ Unicom Guidance]

== What NOT to do ==

=== Don’t use external firewalls, packet filters, rate limiters ===
Don’t block or interfere with any traffic to the node machines. This can disrupt node machine functionality. Occasionally ports are opened for incoming (and outgoing) connections when new versions of node software are deployed.

==== What about network security? ====
IC-OS manages its own firewall(s) and rate limiters very strictly and is designed with security as a primary principle.

== How DFINITY manages its servers ==
See reference DFINITY [[Gen-2 Data Center runbook|data center runbook]].

== Final Checklist ==

* Did you deploy a 10G switch?
* Do the '''first and second 10G ports''' on each server plug into the 10G switch?
* Do you have '''one IPv6 /64 prefix''' allocated from your ISP?
* Do you have at least '''one IPv4 address for every four nodes''' allocated?
* Does each node have ~300Mbps bandwidth?
* Is your '''BMC inaccessible''' from the broad internet?

== References ==

* [[Gen-2 Network Requirements|Gen2 Network Requirements]] - more detailed, possibly out of date.

== Appendix 1: Number of IPv4 Addresses Required ==
{| class="wikitable"
|# Nodes
|# IPv4 Addresses
|-
|1
|1
|-
|2
|1
|-
|3
|1
|-
|4
|1
|-
|5
|2
|-
|6
|2
|-
|7
|2
|-
|8
|2
|-
|9
|3
|-
|10
|3
|-
|11
|3
|-
|12
|3
|-
|13
|4
|-
|14
|4
|-
|15
|4
|-
|16
|4
|-
|17
|5
|-
|18
|5
|-
|19
|5
|-
|20
|5
|-
|21
|6
|-
|22
|6
|-
|23
|6
|-
|24
|6
|-
|25
|7
|-
|26
|7
|-
|27
|7
|-
|28
|7
|}

Node Provider Onboarding

2023-08-07T13:03:00Z

Jens:

Learn how to be accepted by the NNS as a Node Provider and onboard your nodes to the IC.

Please allocate at least 0.5 day for going through the Node Provider NNS registration (steps 1-11). It may even take a couple of days, depending on how quickly the community votes on your NNS proposals.

Once the Node Provider NNS registration is complete, you can move on to '''step 12: Onboard nodes'''. This step involves you going to the DC and onboarding your nodes. It is much quicker than the Node Provider NNS registration (estimate to spend ~15 minutes per machine). Also, multiple machines can be brought up in parallel. Then return to this guide to complete step 13: Setting the reward configuration for your nodes.

'''Note that the following steps do not need to be performed on the node machine itself.''' You can complete them on your personal laptop.

If you encounter issues through any of these steps, check the [[Node Provider Troubleshooting]] page. If that does not solve your problem, you are encouraged to ask for assistance in the [[Node Provider Matrix channel]].

❗️❗️❗️DFINITY does ''not'' offer live support for Node Providers attempting to onboard nodes.

== Requirements ==

* [[Node Provider Machine Hardware Guide]]
* [[Node Provider Networking Guide]]
* [https://www.ledger.com/ Hardware wallet]
* [https://shop.nitrokey.com/shop/product/nkhs2-nitrokey-hsm-2-7/ NitroKey HSM] (Optional, legacy—not recommended)
* 11 ICP (10 of which are to be staked for the NNS proposal deposit)
* Basic understanding of [[Neurons 101|neurons]], [https://internetcomputer.org/docs/current/tokenomics/nns/nns-staking-voting-rewards staking], and [[Governance of the Internet Computer|governance]] proposals. For instance, understanding what it means to stake a neuron for 8 years.

== 1. Install the required tools ==
===''' A. Install ic-admin '''===

<code>ic-admin</code> is the tool used to create and submit NNS proposals.

==== MacOS ====
# Retrieve the file <syntaxhighlight lang="shell">
$ curl "https://download.dfinity.systems/ic/7445081734e6d896d090295967d50710975c4f25/openssl-static-binaries/x86_64-darwin/ic-admin.gz" -o - | gunzip > ./ic-admin
$ chmod +x ./ic-admin
</syntaxhighlight>
# Verify the binary <syntaxhighlight lang="shell">
$ diff <(shasum -a 256 ./ic-admin | cut -d' ' -f1) <(echo 3f75026d2f28f171068e332a42c82a2795c93fbf5ab351baef30b30eb901cdba) && echo "ic-admin checksum matches" || echo "***ERROR***: ic-admin checksum does not match"
</syntaxhighlight>

==== Linux ====
NOTE: The instructions below have been tested with the Ubuntu 20.04 release.
# Retrieve the file <syntaxhighlight lang="shell">
$ curl "https://download.dfinity.systems/ic/7445081734e6d896d090295967d50710975c4f25/openssl-static-binaries/x86_64-linux/ic-admin.gz" -o - | gunzip > ./ic-admin
$ chmod +x ./ic-admin
</syntaxhighlight>
# Verify the binary <syntaxhighlight lang="shell">
$ diff <(shasum -a 256 ./ic-admin | cut -d' ' -f1) <(echo e29bb9cc462e800b8b960ad49c412e5f5fdbb5ae2ae9fde0c13058422ba32802) && echo "ic-admin checksum matches" || echo "***ERROR***: ic-admin checksum does not match"
</syntaxhighlight>

===''' B. Install dfx '''===

#<code>dfx</code> is used to generate neuron hotkeys, among other things <syntaxhighlight lang="shell">
$ sh -ci "$(curl -fsSL https://smartcontracts.org/install.sh)"

</syntaxhighlight>
#Verify that dfx is up to date. <syntaxhighlight lang="shell">
$ export PATH=$HOME/bin:$PATH
$ dfx upgrade
$ dfx --version
</syntaxhighlight>

==2. Create Node Provider hotkey ==

#Create an identity for the Node Provider '''Hotkey''' <syntaxhighlight lang="shell">
$ dfx identity new --storage-mode=plaintext node-provider-hotkey

Created identity: "node-provider-hotkey".

$ dfx --identity node-provider-hotkey identity get-principal

xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
# example node-provider-hotkey: wuyst-x5tpn-g5wri-mp3ps-vjtba-de3xs-w5xgb-crvek-tucbe-o5rqi-mae

</syntaxhighlight>'''You will need the Node Provider hotkey in the next steps.''' Note: you may be prompted to enter a passphrase when creating your identity and accessing your identity principal. Take note of the passphrase you choose.

'''Note:''' The Node Provider hotkey is NOT the Node Provider principal. This is the hotkey that is used for the NNS proposal submissions only.

== 3. Setup your hardware wallet==

# Setup your hardware wallet: https://medium.com/dfinity/integrating-ledger-nano-with-the-nns-front-end-dapp-user-manual-9c5600925e16

==4. Create and Manage Neuron via NNS Frontend Dapp and Internet Identity==

#Send at least 11 ICPs to your hardware wallet address.
#Navigate to Neurons tab and create a Neuron by staking at least 10 ICP from your hardware wallet. Staking more ICP works as well, but 10 is the minimum.
#IMPORTANT! Confirm the transaction on your hardware wallet.
#:[[File:-docs-stake_neuron_1.png|1024px|stake neuron]]
#After the Neuron has been created successfully, confirm to "Add NNS Dapp as hotkey" in the dialogue and on your hardware wallet, and close the dialog after the action completes.
#:[[File:-docs-stake_neuron_2.png|1024px|neuron id]]
#Set the dissolve delay to at least 6 months, and confirm the choice in the dialogue and on your hardware wallet. After the action completes, you can close the "Follow Neurons".
#:[[File:dissolve_delay.png|480px|neuron id]]
#You will now see a Neuron listed with its ID. Copy the Neuron ID, since you will need it in the next steps to place the necessary proposals.
#:[[File:Neuron id.png|1024px]]

==5. Add hotkeys==

#Select the Neuron you just created to open Neuron management view and press “Add hotkey” button.
#:[[File:Hotkey 1.png|873x873px]]
# A dialog will pop up where you can enter the hotkey you generated in step 2.1 (output from command <code>dfx --identity node-provider-hotkey identity get-principal</code>). This will allow you to submit NNS proposals using <code>ic-admin</code> and will not be used for anything else. 
#:Press the '''confirm''' button and confirm the transactions on your hardware wallet. 
#:[[File:Hotkey 2.png|899x899px]]
#Get the Ledger Hardware Wallet Principal Id: Navigate back to ICP page and select your Ledger hardware wallet account. You will need to use this Ledger Hardware Wallet principal as the Node Provider principal in order to get the rewards directly into the secure hardware wallet.
#:[[File:Node provider principal 1.png|1024px]]
#:[[File:Node provider principal 2.png|800px]]
#Copy and save this Node Provider principal by clicking on the copy icon after the principal id. You'll need it in the next steps. <syntaxhighlight lang="shell">
$ NODE_PROVIDER_PRINCIPAL=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
# Input ledger Hardware Wallet principal, from the NNS FrontEnd dapp https://nns.ic0.app/

# example: $ NODE_PROVIDER_PRINCIPAL=fharn-5vyi2-4xb4a-64yyi-3jpmj-pga23-mxy25-d5uim-fqcro-eoefh-tae
</syntaxhighlight>

==6. Choose onboarding path (HSM vs no HSM)==
Onboarding '''without''' a NitroKey HSM is the recommended onboarding path. If you will not be using a NitroKey HSM, continue to the next step.

If the legacy procedure is necessary, follow the [[NitroKey HSM onboarding instructions]] and '''return to step 9.'''

==7. Setup the Node Operator keys ==
#'''''Ensure dfx is at least version 0.14.''''' Node Operator keys created with older versions of dfx '''will fail to join the IC'''. Run:<syntaxhighlight lang="bash">
$ dfx upgrade
$ dfx --version
</syntaxhighlight>
#Create a new principal with dfx:<syntaxhighlight lang="shell">
$ dfx identity new --storage-mode=plaintext node_operator
</syntaxhighlight>
#Confirm <code>node_operator</code> identity was created successfully:<syntaxhighlight lang="shell">
$ dfx identity list
</syntaxhighlight>This list ''should'' contain <code>node_operator</code>.
#Copy new key to a known location:<syntaxhighlight lang="shell">
$ cp ~/.config/dfx/identity/node_operator/identity.pem ./node_operator_private_key.pem
</syntaxhighlight>
#Check the contents of the <code>node_operator_private_key.pem</code> file and double check that it contains the following contents. It is imperative that the first line has <code>-----BEGIN EC PRIVATE KEY-----</code>. If it does not, make sure you use the latest <code>dfx</code> version and that you followed the instructions precisely.<syntaxhighlight lang="shell">
❯ cat ./node_operator_private_key.pem
-----BEGIN EC PRIVATE KEY-----
[3 lines of base64 encoded private key, e.g. n2Nhp68YcQpuS0u96r...]
-----END EC PRIVATE KEY-----
</syntaxhighlight>

==8. Get the node operator principal==

#Get the principal:<syntaxhighlight lang="shell">
$ NODE_OPERATOR_PRINCIPAL=$(dfx --identity node_operator identity get-principal)
$ echo $NODE_OPERATOR_PRINCIPAL

uqquy-76uhn-2mys5-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
</syntaxhighlight>
'''You will need the node operator principal in the next steps.'''

==9. Register your Node Provider principal to the network==
In the next codeblock:
*Replace the <code>NODE_PROVIDER_NAME</code> value with the name of the entity that will provide the nodes.
*Replace the <code>NODE_PROVIDER_PRINCIPAL</code> value with the Ledger Hardware Wallet principal that you got from the NNS Frontend DAPP (step 5.4)
*Replace the <code>NEURON_ID</code> value with your neuron ID from the NNS Frontend Dapp (step 4.6)

*'''''IMPORTANT:''''' Please make sure that you also update the <code>--summary</code> and include a link to the forum discussion, your company's web page, and/or to another place that can convince the voting community that you are making a legitimate request. You must also include the file hash for the self declaration and proof of identity documents, or the proposal will be rejected. This way you will avoid the community voting NO to your proposal and you losing your staked ICPs.

#Create the Proposal <syntaxhighlight lang="shell">
$ NODE_PROVIDER_NAME="My Company"
$ NODE_PROVIDER_PRINCIPAL=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
$ NEURON_ID=XXXXXXXXXXXXXXXXXXXX
$ ./ic-admin \
--nns-url https://ic0.app \
-s ~/.config/dfx/identity/node-provider-hotkey/identity.pem \
propose-to-add-or-remove-node-provider add \
--proposer $NEURON_ID \
--proposal-title "Register a node provider '${NODE_PROVIDER_NAME}'" \
--summary "Register a node provider '${NODE_PROVIDER_NAME}', in line with the announcement and discussion at <https://forum.dfinity.org/t/...>. The self-declaration documentation is available at <https://wiki.internetcomputer.org/wiki/...> with SHA256 hash <SHA256>." \
--node-provider-pid "$NODE_PROVIDER_PRINCIPAL"
</syntaxhighlight>
#Find the proposal on https://dashboard.internetcomputer.org/governance and '''wait until it is executed before proceeding to next step.'''

==10. Register your datacenter to the network (if necessary)==
#Search for your data center on https://dashboard.internetcomputer.org/centers.
#*If you found the datacenter that is hosting your nodes, remember its ID, and skip the following section. Otherwise, proceed with the registration of a new DC record.
#:[[File:dc_id.png|1041x1041px|alt=]]
===Create a data center record for a new DC===
In the next block of code:
*Replace the <code>NEURON_ID</code> value with your neuron ID from the NNS Frontend Dapp (step 4.6)
*Replace the JSON fields from the <code>–data-centers-to-add</code> argument and their corresponding values in <code>--summary</code>:
**<code>"id"</code> represents the city that your datacenter is in and is formulated as a combination of two letters representing the city and an incrementing number. Search data center IDs on https://dashboard.internetcomputer.org, and find a combination of two letters and a number that’s not yet registered. Examples:
***dl1 (Dallas, no IDs with “dl” prefix)
***zh10 (Zurich, numbers 0-9 are already registered)
**:[[File:dc_id.png|1024px]]
**<code>"region"</code> represents the local region of a datacenter and is formulated as a three-part string divided by commas. The three parts making the string are continent, country code, and region, in the given order. Examples:
***North America,US,Florida
***Europe,DE,Bavaria
***Asia,SG,Singapore
**:[[File:datacenter_region.png|1024px]]
**<code>"owner"</code> The entity that provides your datacenter facilities.
***Search https://dashboard.internetcomputer.org for existing data center providers.
*** If there’s match, make sure you use the same exact some name for your datacenter.
***Otherwise, name the data center owner to your best knowledge.
**:[[File:datacenter_owner.png|1024px]]
**<code>"gps"</code> GPS coordinates.
***Find your datacenter on https://www.google.com/maps/.
***Right click on location, and select the GPS coordinates (first item in the menu) in order to copy them.
**:[[File:maps.png|310x310px|alt=Getting GPS coordinates|Getting GPS coordinates]]

#Create the proposal: <syntaxhighlight lang="shell">
$ NEURON_ID=XXXXXXXXXXXXXXXXXXXX
$ ./ic-admin \
--nns-url https://ic0.app \
-s ~/.config/dfx/identity/node-provider-hotkey/identity.pem \
propose-to-add-or-remove-data-centers \
--summary "Register a Flexential datacenter as dl1 in North America,US,Texas" \
--skip-confirmation \
--proposer $NEURON_ID \
--data-centers-to-add '{
"id": "dl1",
"region": "North America,US,Texas",
"owner": "Flexential",
"gps": [
33.00803, -96.66614
]
}'
</syntaxhighlight>'''Remember to replace all the values of both the arguments <code>–data-centers-to-add</code> and <code>--summary</code>'''
#Find the proposal on https://dashboard.internetcomputer.org/governance and wait until it's executed before proceeding to next step.

==11. Create a node operator record==
In the next codeblock:
*Replace the <code>NEURON_ID</code> value with your neuron ID from the NNS Frontend Dapp (step 4.6).
*Replace the <code>NODE_PROVIDER_PRINCIPAL</code> value with the Ledger Hardware Wallet principal that you got from the NNS Frontend DAPP (step 5.4).
*Replace the <code>NODE_OPERATOR_PRINCIPAL</code> value with your node operator principal (step 8.1).
*Replace the <code>NODE_PROVIDER_NAME</code> value with the name of the entity that will provide the nodes.
*Replace the <code>NODE_ALLOWANCE</code> variable value with number of nodes you are providing.
* Replace the <code>DC_ID</code> variable value with id of your datacenter.

# Create the proposal: <syntaxhighlight lang="shell">
$ NEURON_ID=XXXXXXXXXXXXXXXXXXXX
$ NODE_PROVIDER_PRINCIPAL=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
$ NODE_OPERATOR_PRINCIPAL=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
$ NODE_PROVIDER_NAME="My Company"
$ NODE_ALLOWANCE=8
$ DC_ID=dl1

$ ./ic-admin \
--nns-url https://ic0.app \
-s ~/.config/dfx/identity/node-provider-hotkey/identity.pem \
propose-to-add-node-operator \
$NODE_PROVIDER_PRINCIPAL \
--summary "Node provider '$NODE_PROVIDER_NAME' is adding $NODE_ALLOWANCE nodes in the $DC_ID data center" \
--proposer $NEURON_ID \
--node-operator-principal-id $NODE_OPERATOR_PRINCIPAL \
--node-allowance $NODE_ALLOWANCE \
--dc-id $DC_ID
</syntaxhighlight>
#Find the proposal on https://dashboard.internetcomputer.org/governance and wait until it's executed before proceeding to next step.

==12. Onboard nodes==

# Follow the instructions to onboard new nodes:
#*[[IC-OS Installation Runbook]]

==13. Reward configuration proposal==
After you have completed all previous steps and the node machines have been onboarded, you must submit a reward configuration proposal in order to start receiving node rewards. If you do not do this, you will not receive node rewards.

In the next code block:

*Replace the <code>NEURON_ID</code> value with your neuron ID from the NNS Frontend Dapp (step 4.6).
*Replace the <code>NODE_OPERATOR_PRINCIPAL</code> value with your node operator principal (step 8.1).
*Replace <code>NODE_1_MACHINE_ID</code>, <code>NODE_2_MACHINE_ID</code> ... <code>NODE_N_MACHINE_ID</code> with the node machine IDs for all N of your node machines (found on the [https://dashboard.internetcomputer.org/ dashboard])
*Replace <code>NODE_COUNT</code> with the number of nodes you are setting a reward configuration for.

1. Create the proposal<syntaxhighlight lang="shell">
$ NEURON_ID = XXXXXXXXXXXXXXXXXXXX
$ NODE_OPERATOR_PRINCIPAL = xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxxxx-xxx
$ ./ic-admin \
--nns-url https://ic0.app \
-s ~/.config/dfx/identity/node-provider-hotkey/identity.pem \
propose-to-update-node-operator-config \
--proposer $NEURON_ID \
--summary "Set rewards for the following nodes:

* NODE_1_MACHINE_ID
* NODE_2_MACHINE_ID
* ...
* NODE_N_MACHINE_ID
" \
--node-operator-id $NODE_OPERATOR_PRINCIPAL \
--rewardable-nodes '{"type3.1": NODE_COUNT}'
</syntaxhighlight>

The default reward configuration for gen2 nodes is <code>type3.1</code>. If a different node configuration is applicable to your node models, replace this value.

Example reward configuration proposal for 3 gen2 nodes:
<syntaxhighlight lang="shell">
$ NEURON_ID = 13419667327548602649
$ NODE_OPERATOR_PRINCIPAL = uqquy-76uhn-2mys5-dh54e-85ntr-sr953-redif-zkte3-94ndi-st2i1-93t
$ ./ic-admin \
--nns-url https://ic0.app \
-s ~/.config/dfx/identity/node-provider-hotkey/identity.pem \
propose-to-update-node-operator-config \
--proposer $NEURON_ID \
--summary "Set rewards for the following nodes:

* sed94-atzdo-rltqy-tmnhr-fvspg-fat3p-sdbjp-7q3jg-dgfcq-zrlap-cqe
* uq4uy-76uhn-2mys5-dh54e-85ntr-sr953-redif-zkte3-94ndi-st2i1-93t-sdjsl-vjlfn-6duch-vskdu-26pf5-cwibg-zooqk-sdn2e-cgugm-tae
* 39esy-hmrb2-nfvao-t42co-tqfed-y3i7c-xqxyp-idt2w-wgmgr-l4x7l-gae
" \
--node-operator-id $NODE_OPERATOR_PRINCIPAL \
--rewardable-nodes '{"type3.1": 3}'
</syntaxhighlight>

2. Find the proposal on <nowiki>https://dashboard.internetcomputer.org/governance</nowiki> and wait until it's executed

Node Provider Machine Hardware Guide

2023-08-07T12:52:33Z

Jens:

Node Providers operate one or more node machines than run in the Internet Computer network.

Gen1 hardware requirements have been used by Node Providers to set up node machines during the Genesis launch.

The Gen2 hardware requirements have been defined for the further growth of the Internet Computer network. The specifications for the Gen2 node machines are generic (instead of vendor specific) and support VM memory encryption and attestation, which will be needed in future features on the Internet Computer.

While Gen2 Node Providers are only strictly required to follow the generic specifications '''(the IC-OS installation will fail if the generic specifications are not met)''', it is strongly recommended for Node Providers to purchase one of the validated configurations listed below.
== Gen 2 Node Machine requirements ==
==== Generic specification ====
{| class="wikitable"
|-
| Dual Socket AMD EPYC Milan CPU - Recommended: [https://en.wikichip.org/wiki/amd/epyc/7313 7313] (16C/32T 3 Ghz)
[https://en.wikichip.org/wiki/amd/epyc#7003_Series_.28Zen_3.29 optionally] 7343, 7373, 73F3
|-
| 16x 32GB RDIMM, 3200MT/s, Dual Rank
|-
| 5x 6.4TB NVMe Mixed Mode (DWPD >= 3)
|-
| Dual Port 10G SFP or BASE-T
|-
| TPM 2.0
|}
'''Important:''' Do NOT order a RAID controller for your node machine. If a RAID controller is included in your setup, it will cause issues with the installation of IC-OS on your machine.

=== Dfinity-validated configurations ===
DFINITY has [https://forum.dfinity.org/t/draft-motion-proposal-new-hardware-specification-and-remuneration-for-ic-nodes/14202/14?u=garym validated] the following Gen2 hardware configurations.
==== Dell ====
{| class="wikitable"
|-
| 2 || AMD EPYC 7343 3.2GHz, 16C/32T, 128M Cache (190W)
|-
| 16 || 32GB RDIMM, 3200MT/s, Dual Rank 16Gb BASE x8
|-
| 5 || 6.4TB Enterprise NVMe Mixed Use AG Drive U.2 Gen4 with carrier
|-
| 1 || PowerEdge R6525 Motherboard, with 2 x 1Gb Onboard LOM (BCM5720)MLK V2
|-
| 2 || Dual, Hot-plug, Redundant Power Supply (1+1) 1100W, Mixed Mode Titanium
|-
| 1 || Intel X710 Dual Port 10GbE SFP+, OCP NIC 3.0
|-
| 1 || Trusted Platform Module 2.0 V3
|}

==== ASUS ====
{| class="wikitable"
|-
| 2 || AMD EPYC 7313 (3,00 GHz, 16-Core, 128 MB)
|-
| 16 || 32GB ECC Reg ATP DDR4 3200 RAM
|-
| 5 || 6.4 TB NVMe Kioxia SSD 3D-NAND TLC U.3 (Kioxia CM6-V)
|-
| 1 || Asus Mainboard KMPP-D32 Series (without OCP 3.0, without Pike)
|-
| 2 || 1600 Watt redundant PSU
|-
| 1 || Broadcom 25 Gigabit P225P SFP28 Dual Port Network Card
|-
|0
|TPM 2.0*
|}
<nowiki>*</nowiki> Note Gen2 machines require TPM 2.0 hardware but this specific test machine did not include it.

==== Supermicro ====
{| class="wikitable"
|-
| 2 || AMD EPYC 7313 (3,00 GHz, 16-Core, 128 MB)
|-
| 16 || 32GB ECC Reg DDR4 3200 RAM
|-
| 5 || 6.4 TB NVMe TLC SSD, PCIe 4.0 x4, U.3 2.5", 3 DWPD
|-
| 1 || SuperMicro H12DSU-iN
|-
| 2 || 1200 Watt redundant PSU
|-
| 1 || Dual Port 10GBase-T Network Adapter Intel® X710-TM4*
|-
|1
|Dual Port 10GbE Network Adapter Intel® X710-TM4, SFP+*
|-
| 1 || Trusted Platform Module 2.0
|}
<nowiki>*</nowiki> Only one dual port network adaptor is required.

==== Gigabyte ====
{| class="wikitable"
|-
| 2 || AMD EPYC 7313 (3,00 GHz, 16-Core, 128 MB)
|-
| 16 || 32GB ECC Reg DDR4 3200 RAM
|-
| 5 || 6.4 TB NVMe TLC SSD, PCIe 4.0 x4, U.3 2.5", 3 DWPD
|-
| 1 || Gigabyte MZ92-FS1 Rev. 3.0
|-
| 2 || 1200 Watt redundant PSU
|-
| 1 || Dual Port 1000Base-T Network Adapter Intel® I350-AM2*
|-
|1
|Dual Port 10GbE Network Adapter, Broadcom NetXtreme E-Series*
|-
| 1 || Trusted Platform Module 2.0
|}
<nowiki>*</nowiki> Only one dual port network adaptor is required.

=== Community-validated configurations ===
Node Providers have validated the following Gen2 hardware configurations:

==== Dell PowerEdge R7525 ====
{| class="wikitable"
|2
|AMD 7313 3.0GHz,16C/32T,128M,155W,3200
|-
|16
|32GB RDIMM, 3200MT/s, Dual Rank 16Gb BASE x8
|-
|5
|6.4TB Enterprise NVMe Mixed Use AG Drive U.2 Gen4 with carrier
|-
|1
|PowerEdge R7525 Motherboard, with 2 x 1Gb Onboard LOM (BCM5720)MLK V2
|-
|2
|Dual, Hot-plug, Power Supply Redundant (1+1), 800W, Mixed Mode, NAF
|-
|1
|Intel X710 Dual Port 10GbE SFP+, OCP NIC 3.0
|-
|1
|Trusted Platform Module 2.0 V3
|}

== Gen 1 Node Machine requirements ==
If you're a Node Provider acquiring machines to join the IC, use the Gen2 specifications listed above. This section is for Gen1 Node Providers who joined before 2022.

==== SuperMicro ====
{| class="wikitable"
|-
| 1 || AS - 1023US - TR4
|-
| 2 || Rome 7302 DP/UP 16C/32T 3.0
|-
| 16 || 32GB DDR4-3200 2Rx4 ECC REG DIMM
|-
| 5 || Samsung PM983 3.2TB NVMe PCIE/SATA Hybrid M.2 & 1 PCIE
|-
| 2 || 800W Power Supply
|-
| 1 || Std LP 2-port 10G RJ45, Intel x540
|-
| 5 || Micron 5300 PRO 7.4TB, SATA, 2.5', 3D TLC, .6DWPD (with Caddie)
|-
| 1 || C13/C14 13A Power Cord
|}

==== Dell - type 1 ====
{| class="wikitable"
|-
| 1 || R6525
|-
| 1 || Chassis - Supports Up to 10 NVMe drives, 12 drives total
|-
| 1 || Dual 1 GB on Motherboard
|-
| 3 || Low Profile PCIe Slots
|-
| - || 3 Year Basic NBD Support
|-
| - || iDrac Enterprise
|-
| 1 || Dual port 10GbE Base - T Adapter Broadcom, PCIe Low Profile
|-
| 10 || 3.2TB NVMe, Mixed Use, 2.5" with Carrier
|-
| 16 || 32GB RDIMM (3200MT/s)
|-
| 2 || AMD 7302 3GHz, 16C/32T, 128M, 155W, 3200
|-
| 1 || Single Power Supply (800W)
|-
| 1 || C13-C14, 3M, 125V 15A Power Cored
|-
|}

==== Dell - type 2 ====
{| class="wikitable"
|-
| 1 || R6515
|-
| 1 || 3.5" Chassis with up to 4 Hot-Plug Hard Drives and OS RAID
|-
| 1 || Dual 1 Gb on Motherboard
|-
| 3 || Low Profile PCIe Slots
|-
| 1 || Standard Fan
|-
| - || 3 Year Basic NBD Support
|-
| - || iDrac Enterprise
|-
| 2 || Dual Port 10GbE Base - T Adapter Broadcom, PCIe LOw Profile
|-
| 2 || 480GB SSD SATA Mix Use 6Gbps 512 2.5in Hot-Plug AG Drive, 3.5in
|-
| 4 || 8GB RDIMM, 3200 MT/s, Single Rank
|-
| 1 || AMD EPYC 7232P 3.10GHz, 8C/16T, 64M Cache (120W) DDR4-3200
|-
| 1 || Dual Hot-Plug Redundant Power Supply (1+1), 550W
|-
| 2 || Jumper Cord - C13/C14, .6M, 250V, 13A
|}

== Purchasing Hardware ==
# '''Choose your node machine configuration'''
#* Stick with the configurations above. Anything else is unsupported.
# '''Use local and trusted supply chains'''
#* If possible, purchase hardware locally from a trusted vendor to avoid global single points of failure and to reduce the risk that somebody tampers with your hardware during delivery
# '''Where to buy?'''
#*[https://www.supermicro.com/en/wheretobuy Supermicro]
#*[https://www.dell.com/en-us/shop/dell-poweredge-servers/sc/servers Dell]
#*[https://www.gigabyte.com/WheretoBuy/Enterprise Gigabyte]
#*[https://servers.asus.com/support/wheretobuy/117 ASUS]
# '''Place your order'''
#* Double check the components meet the generic specs above.

Lead times can be weeks to months. Plan accordingly with respect to [[Node Provider Onboarding|onboarding]].

Node Provider Self-declaration

2023-08-07T12:37:36Z

Jens:

''This page is work in progress''

This page describes the Node Provider self-declaration process and provides templates. This process and templates are currently in a draft state and discussed by the community (see forum post). Once the NNS has decided on the expected format, the post and this page will be updated to reflect the NNS decision.

== Motivation ==

In a fully decentralized network, onboarding of a Node Provider is managed entirely by the Network Nervous Systems (NNS). This means that anybody who wants to become a Node Provider needs to submit a proposal that will be voted upon by the community. The main question for the community is: how to decide whether to accept or reject a new Node Provider into the network?

Ultimately, it’s the Node Provider's responsibility to convince the community to adopt their proposal to be added as a new Node Provider. With the self-declaration, the Node Provider shall:

* Establish their identity
* Make a statement of good intent

This way, the community will have sufficient information to vote on the Node Provider's onboarding proposal.

== Documents and Templates ==

Before submitting a proposal to become a new Node Provider, the Node Provider shall prepare two kinds of documents. The documents should be delivered as a pdf document, digitally signed.

=== (1) Self-declaration ===

(A) Statement of identity

Entity name: __________________________________________________

Official address and location: _____________________________________

Country: ______________________________________________________

Chamber of Commerce Nr: _______________________________________

(B) Statement of provision of node machines

I hereby guarantee that I shall provide node machines in accordance with the required Hardware Configuration for running the IC Network, as described on the IC wiki (see [[Node Provider Machine Hardware Guide]]).

(C) Statement of good intent

I guarantee to the world that I shall honestly operate the node machines I provide, and that should I behave dishonestly, for example by deliberately interfering with my node machine(s) to prevent them correctly processing ICP protocol messages, in collusion with others or alone, that I will be liable to users of the network, and to other node providers, for any damages caused.

I further declare I am aware that any deliberate interference with a node machine, which causes it to incorrectly process ICP protocol messages, represents a misuse of that hardware, and of any hardware it interacts with, and that in some jurisdictions, that may constitute a crime.

Signature of representatives

___________________

___________________

___________________

=== (2) Identity Proof ===

The Node Provider shall provide proof that the identity(ies) listed in the self-declaration exist in the real world. The proof can be any document that sufficiently proves the identity of the signers of the self-declaration to the community.

== Process ==

Initially, the process is quite manual. Over time, it shall be automated and for convenience be incorporated into dApps running on the IC. For now:

<ol style="list-style-type: decimal;">
<li><blockquote>'''Preparation:''' The Node Provider prepares

* The two kinds of documents listed above in a format that is widely available, e.g. PDF</blockquote>
<ul>
<li><blockquote>Creates a compressed file, e.g. zip file, including these documents and computes the hash.</blockquote></li></ul>
</li>
<li><blockquote>'''Publication:''' The Node Provider uploads the documents to the wikipage [[Node Provider Self Declarations]].</blockquote></li>
<li><blockquote>'''Proposal submission:''' The Node Provider submits a proposal to the NNS asking to be accepted to the network.</blockquote>
<ul>
<li><blockquote>The technical instructions are provided on the [[Node Provider Onboarding]] page.</blockquote></li>
<li><blockquote>The summary of the proposal shall point to the published file (step 2) and list the hash (step 1).</blockquote></li></ul>
</li>
<li><blockquote>'''NNS vote:''' It’s now up to the NNS community to check whether the provided information matches the community’s expectations and to vote on the proposal.</blockquote></li></ol>

Node Provider Matrix channel

2023-08-07T07:08:12Z

Jens:

There is an open Matrix channel that is intended to be a forum for potential and existing Node Providers as well as anybody else who would like to follow the node provider discussion: https://app.element.io/#/room/#ic-node-providers:matrix.org

The channel runs on the open Matrix network. Matrix [https://matrix.org/clients/ has many clients] you can use. One of the clients is element.io, which is very similar to Slack, and offers a web UI, a [https://element.io/download desktop app], and a mobile app.

We recommend that you add [https://ems-docs.element.io/books/element-cloud-documentation/page/element-settings an email address in the Element Profile settings] and to [https://element.io/help#settings3 enable notifications for missed messages].

Node Provider Roadmap

2023-07-24T09:30:43Z

Jens:

The roadmap outlines what is required of Node Providers, the reward model of the Internet Computer, guidance on hardware acquisition and data center contracts, in-depth best practices, node onboarding procedures, and much more.

There are five Node Provider milestones to go from scratch to being a node provider. Finally, the sixth milestone covers node management and maintenance once you're a node provider.

* [[Node Provider Milestone One: Education|Milestone One: Education]]
** Here, you will learn more about the Internet Computer and the rewards/obligations of being a Node Provider.
* [[Node Provider Milestone Two: Requirements|Milestone Two: Requirements]]
** Here, you will learn more about the specific skill, hardware, networking, and data center requirements, as well as some best practices regarding decentralization and security.
* [[Node Provider Milestone Three: Node Provider Onboarding|Milestone Three: Node Provider Onboarding]]
** Here, you will gain approval by the NNS DAO to be a Node Provider.
* [[Node Provider Milestone Four: Node Onboarding Preparation Checklist|Milestone Four: Node Onboarding Preparation Checklist]]
** Here, you will be guided on how to obtain the necessary requirements necessary to onboard nodes.
* [[Node Provider Milestone Five: Node Onboarding|Milestone Five: Node Onboarding]]
** Here, you will onboard your nodes to the Internet Computer.
* [[Node Provider Milestone Six: Node Management|Milestone Six: Node Management]]
** Here, you will find important guidance and resources on managing and troubleshooting your nodes.

Replace traditional IT with a World Computer

2022-11-10T13:09:24Z

Jens:

'''The Internet Computer aims to realize the [[World Computer]] vision first mooted within the [[Ethereum]] community in 2014. It is an open and decentralized platform that provides an alternative to the traditional IT stack, which is comprised of things such as [[cloud computing]] services, server computers, database servers, web servers, middleware, backup systems, and security infrastructure such as firewalls. The Internet Computer network provides an alternative platform that can be used to build and run almost any online system or service.'''

How, you might ask, can a public network provide an alternative to the $5-trillion-dollar-a-year IT industry (according to Gartner). The answer is that the Internet Computer is a radical new form of blockchain made possible by [[chain key cryptography|novel cryptography]] and math. Unlike traditional blockchains, it does not need to indefinitely store old blocks of transactions, does not need [[local node]]s in its network, and can scale its capacity to host compute, with orders of magnitude more efficiency.

On the Internet Computer, developers can build almost any online system or service desired, just by writing [[canister smart contract]] code. Canisters are [[smart contract]]s with breakthrough levels of efficiency, have the speed to process HTTP requests and serve interactive web experiences directly to end users, and can be composed to ''build almost any system or service''. Furthermore, their data is weakly private, with stronger privacy options in the works. Yet, while they work differently, for example running in parallel, they also have the key magical properties of traditional [[smart contract]]s.

For example, [[canister]]s are unstoppable, and also tamperproof, which means that when their code is invoked, the Internet Computer is guaranteed to run the correct logic against the correct data. Furthermore, they can be made to run autonomously if required, and can process tokens.

===No firewalls or security infrastructure necessary===

One obvious advantage that the Internet Computer provides over traditional IT is security.

Systems and services running from the Internet Computer, which have been built using canister smart contracts, don't need to be protected by firewalls. This is similar to how DeFi smart contracts on [[Ethereum]] don't need to be protected by firewalls. Instead, they are secure by default, which is the exact opposite of systems built using traditional software that run on traditional IT, which have no security by default, and must be protected by teams of security administrators, special configurations, and special security tech such as [https://en.wikipedia.org/wiki/Firewall_(computing) firewalls] and [https://en.wikipedia.org/wiki/Security_information_and_event_management SIEM logging].

[https://www.vox.com/recode/22428774/ransomeware-pipeline-colonial-darkside-gas-prices When systems and services are built using traditional IT, just one simple mistake can allow a hacker can steal data, or encrypt systems using ransomware, with catastrophic results], and it happens all the time. In 2022, worldwide expenditure on IT security will be $172 billion dollars (according to Gartner), but the intangible costs of constant hacks and potential business disruption is much higher.

Traditional IT is in the midst of a security meltdown, and the Internet Computer provides a way out. Because systems built on the Internet Computer using canisters are secure by default, the costs involved with security tech and its operation can be avoided, as can the vast majority of the intangible costs of hacks, and the damage they cause.

''Where Web3 services and applications are concerned, which involve token assets that can be stolen, security is even more critical. Here it's possible to go one step further, by placing the canisters behind the service or application under the full control of a [[DAO]], so that if a developer goes rogue and wishes to hack the system, they are unable to do so because they cannot change its code in an unmoderated manner.''

===Build on a public network, not on a Big Tech fly trap===

The game-changing advantages of the Internet Computer go far beyond security. In the 1990s, there was an ongoing debate regarding whether the public internet, or walled-garden networks, such as AOL, Compuserve and the [https://www.microsoft.com/en-us/research/publication/on-ramp-prospects-for-the-information-superhighway-dream/ "Information Superhighway" Microsoft imagined], would prevail. Eventually the internet easily won out because it was permissionless, and provided a free market, and nobody wanted to be fed content that was carefully curated for them by mega corporations.

It was a free market because, if Alice and Bob created profitable but competing websites, say, then Alice could not call up the owner of the internet and say "if you slow down the public's access to Bob's website, I will give you stock in my company." The permissionless free market provided the foundations for social impact and freedoms, innovation and massive economic growth.

''The internet provided decentralized, permissionless and global network connectivity that now connects almost everyone and everything. We now need to go one step further and do the same for computation using a [[World Computer]].''

The lives of the nearly 8 billion people on this planet could not be supported without the massive computing power that automates our global society's infrastructure. For example, it automates markets and supply chains that facilitate farming through the manufacture of fertilizer and tractors, and then the efficient transport of farm produce to supermarkets. Meanwhile, online interactions have created a social and business fabric that is an indispensable part of our personal and work lives.

Given how pivotal society's information infrastructure has become to human existence, it makes no sense to build it out on the back of a few anointed Big Tech services, such as [[Amazon Web Services]], who will then make us all captive. Moreover, when compared to what the Internet Computer can provide as a blockchain, these platforms have serious disadvantages.

To use traditional IT, we must combine and integrate a veritable menagerie of components — such as servers or cloud instances, cloud orchestration layers, databases, web servers, memcached, backup systems, content distribution networks, middleware, security tools and much more — creating systems and services that resemble [https://en.wikipedia.org/wiki/Rube_Goldberg_machine Rube Goldberg machines] that are fragile and unnecessarily complex.

Managing this complexity is the source of the biggest cost of all. Of the $5 trillion dollar global IT spend, 80% of that is spent on IT operations, which is comprised from human beings spending much of their time managing complexity. Organizations operating an important but simple website, say, will often hire systems administrators, database administrators and security administrators just to keep it running. This costs crazy amounts of money. These complex systems also cannot be updated quickly, creating opportunity costs.

Meanwhile, when building on traditional IT, the reward is typically to become a captive customer of a [[cloud computing]] service provider and other vendors. Those building using the proprietary and complex stack provided by [[Amazon Web Services]], for example, often eventually find themselves in a similar predicament to those building using the Microsoft software stack twenty years ago, and get stuck there because the re-engineering costs involved with moving are too great. Cloud computing services keep releasing new platform features, and a large part of the reason, is to better trap those lured into building there.

The Internet Computer now provides a clear alternative in the form of a public network. On this open platform, you build using canister smart contract code that is unstoppable and secure without firewalls, and which greatly simplifies the construction and maintenance of systems and services.

===Build on the internet to emit less CO2===

Traditional IT evolved in a time when computers were vastly less powerful, and the internet vastly slower, embedding architectural decisions that are no longer relevant at the root of an evolutionary branch of technology that is increasingly wrong-headed in the modern world.

Even though the Internet Computer is an advanced blockchain, it may come as a surprise that when used as an alternative to traditional IT, it can reduce CO2 emissions. That is because its architecture, cryptography and network governance, is able to configure the replication of computation and data within its network (a key source of inefficiency within traditional blockchain networks), in a ways that constrain the order of replication to the minimum needed to provide the strong liveness (unstoppability) and security guarantees expected of a blockchain.

Very deliberately, the Internet Computer's architecture and math embraces the replication of computation and data, using it to provide a platform for unstoppable and secure tamperproof code, while also scaling certain kinds of computation, such as data queries and web serving.

By contrast, traditional IT is replete with accidental, tacked-on replication. When you create a system or service, very often data is replicated across several database nodes, backup systems, middleware, and more copies are kept handy by the code producing web pages, for example using memcached. Then the web pages and other content served are further replicated by [[Content Distribution Network (CDN)|CDNs (content distribution networks)]].

When systems and services built using traditional IT components are considered as a whole, this accidental hidden replication is often very substantial. However, despite all the hidden replication involved, when systems and services are built using traditional IT, they are not unstoppable or secure and tamperproof.

The Internet Computer challenges deeply held misconceptions about blockchain science. In the popular imagination, it is defined by computationally expensive [https://en.wikipedia.org/wiki/Proof_of_work proof-of-work networks], which Satoshi introduced in his 2008 paper. These sometimes use as much power as a small country, yet can only process a handful of transactions a second.

The Internet Computer flips this narrative. It is a blockchain that can play the role of an end-to-end platform, which provides an alternative to traditional IT that will arguably be more efficient with respect to electricity consumption.

===Web3 and cloud are incompatible===

Today, if you ask much of the public and journalists what Web3 is, they will mostly propose that it is something to do with [[NFT]]s. But those working at the forefront of the field understand it as something much more profound and impactful. Web3 is about replacing today's Web 2.0 services, which are mostly run by big corporations, with an infrastructure that engages users through the tokenization of assets and participation rights, and by assigning full control over these services to [[DAO]]s (decentralized autonomous organizations), so they can be run by their communities.

In the future, Web3 online services will run rather like open economies. They will be controlled by DAOs, which in turn will be controlled by voting using [[governance tokens]]. These tokens will be held by founders, core developers, investors and, most importantly, the end users of the services themselves. Algorithms will be give them out to users who contribute, perhaps because they are prolific creators of popular content, refer other users to the service, or help with content moderation. Users will be the owners of services, and also part of the team that runs them — which will enable them to scale fast, and make them more viral and sticky.

Entire metaverse world's will run entirely from the blockchain. For example, one metaverse project being built on the Internet Computer today enables users to create their own 3D island, in the style of Minecraft, which they can share via a URL on their social media profiles. That world is itself an NFT, but they can also import ready-crafted objects into their metaverse islands, such as a castle or art gallery, by acquiring NFTs, then use the space to sell art NFTs. Island owners can create gateways to other islands, as a means to share traffic, and then sell the gateways as NFTs. This only scratches the surface of what is being done: The metaverse is an economy.

Meanwhile, in Web3, everything blends with DeFi. For example, social media can blend with DeFi to become [[SocialFi]]. Open Chat ([https://oc.app oc.app]) is a messaging service that runs entirely from the Internet Computer blockchain, where smart contracts process and store text messages and media messages such as video. But this is no normal messaging service. A user account can also play the role of a crypto wallet, which maintains bitcoin, [[Roles of the ICP utility token|ICP]] and other tokens that can be sent along with chat messages. On top, it is being integrated by other Web3 developers, and special group chats now provide users with easy ways to vote on DAO governance proposals, among other things.

The question of how security and regulation are handled by these new services is critical. Users do not want to lose their NFTs in a hack, especially if they confer ownership of a valuable and highly trafficked metaverse they created, say, and they also do not want to have their cryptocurrency and other tokens stolen. Furthermore, the developers of such services, do not want to find themselves classified as [https://en.wikipedia.org/wiki/Money_transmitter money transmitters], say, because they were constructed using centralized traditional IT.

Any reasonable analysis shows that the only practical way to solve these problems is to run Web3 services in the mode of protocols, just like blockchains themselves. This can be done by building them exclusively using smart contracts that are then placed under the ''full and exclusive control of community DAOs''. Once control has been transferred to a community DAO, and the service runs 100% from the blockchain without the use of traditional IT, the developers cannot arbitrarily change the code in an unmoderated way to steal crypto balances. Nor can anyone else steal the crypto balances unless their code is flawed.

Moreover, when a Web3 service truly runs autonomously in cyberspace, under the exclusive control of a community DAO, then its management and ownership is no longer rooted in a jurisdiction and it runs in the manner of a decentralized protocol. There is no centralized entity such as a person, group of developers, or corporation that is responsible for its ongoing operations. This is very different to a Web3 service built using a cloud computing service, or other traditional IT, which roots it in a jurisdiction and directly transfers legal responsibility to those who control and own the cloud account. This responsibility is also transitively transferred to any shadow controllers.

The Internet Computer provides for any Web3 service or application to be built entirely on chain using smart contracts, without need for cloud computing, server computers, or any other traditional IT. Furthermore, services and applications can be placed under the full control of DAOs, either using the built-in [[Service Nervous System]] DAO framework, or third party DAO frameworks.

===Web3 TL;DR===

However you plan to build a Web3 service or application, you need to ditch the cloud and traditional IT. You can either build exclusively on the Internet Computer, or [[Extend_Bitcoin,_Ethereum_and_other_blockchains|combine smart contract code on the Internet Computer with smart contract code on other chains such as Ethereum]].

Today, finally, thanks to years of work by engineers, computers science researchers and cryptographers, ''blockchain is the stack''.

[https://internetcomputer.org/developers Get started building systems, applications and services using canister smart contracts running on a real World Computer].

How much does it cost to run a dapp on the Internet Computer?

2022-08-17T04:59:02Z

Jens:

==Computation and Storage Costs==

The Internet Computer requires computation operations and storage to be supported by [[cycles]]. Cycles are generated from the conversion of Internet Computer (ICP) utility tokens.

==The Role of the Network Nervous System (NNS) in Defining Costs==

The Internet Computer is a decentralized public utility, controlled by the NNS –– the network’s open, algorithmic governance system. The NNS fundamentally controls how many cycles are required for low-level computation actions for computation and storage. The number of cycles needed for individual computations will vary based on a number of factors considered by the NNS, including proposals from the community.

==Details: Cost of Compute and Storage Transactions on the Internet Computer==
Canisters (dapps/smart contracts) computations running on the Internet Computer blockchain are fueled by “cycles”, which play a similar role to “gas” on Ethereum. There are several major differences, however. One of the most fundamental differences is that Ethereum leverages “user pays” and the Internet Computer leverages “smart contract pays” (sometimes called “reverse gas”) model. Whereas the Ethereum blockchain requires end-users to send payments for the gas smart contracts consumed with every transaction, on the Internet Computer, canisters (dapps/smart contracts)are pre-charged with cycles, such that contracts effectively pay for their own computation - freeing users from the responsibility.

See below for details on the cost of compute and storage transactions<ref>https://sdk.dfinity.org/docs/developers-guide/computation-and-storage-costs.html</ref> on the Internet Computer as of July 26, 2021.

{| class="wikitable"
|+ Table 1. Cycles Cost per Transaction (as of July 26, 2021)
|-
! Transaction !! Description !! All Application Subnets
|-
| Canister Created || For creating canisters on a subnet || 100_000_000_000
|-
| Compute Percent Allocated Per Second || For each percent of the reserved compute allocation (a scarce resource). || 100_000
|-
| Update Message Execution || For every update message executed || 590,000
|-
| Ten Update Instructions Execution || For every 10 instructions executed when executing update type messages || 4
|-
| Xnet Call || For every inter-canister call performed (includes the cost for sending the request and receiving the response) || 260_000
|-
| Xnet Byte Transmission || For every byte sent in an inter-canister call (for bytes sent in the request and response) || 1_000
|-
| Ingress Message Reception || For every ingress message received || 1_200_000
|-
| Ingress Byte Reception || For every byte received in an ingress message || 2_000
|-
| GB Storage Per Second || For storing a GB of data per second || 127_000
|}

The $USD cost for transactions below is based on the above cycle costs. 1 XDR is equal to 1 Trillion cycles. As of July 26, 2021, the exchange rate for 1 XDR = $1.42. The exchange rate for USD <> XDR may vary and it will impact the conversion rate. For XDR exchange rates please visit: https://www.imf.org/external/np/fin/data/rms_sdrv.aspx

{| class="wikitable"
|+ Table 2. Cost per Transaction in $USD (as of July 26, 2021)
|-
! Transaction !! Description !! All Application Subnets
|-
| Canister Created || For creating canisters on a subnet || $0.142
|-
| Compute Percent Allocated Per Second || For each percent of the reserved compute allocation (a scarce resource). || $0.000000142
|-
| Update Message Execution || For every update message executed || $0.0000008378
|-
| Ten Update Instructions Execution || For every 10 instructions executed when executing update type messages || $0.00000000000568
|-
| Xnet Call || For every inter-canister call performed (includes the cost for sending the request and receiving the response) || $0.0000003692
|-
| Xnet Byte Transmission || For every byte sent in an inter-canister call (for bytes sent in the request and response) || $0.00000000142
|-
| Ingress Message Reception || For every ingress message received || $0.000001704
|-
| Ingress Byte Reception || For every byte received in an ingress message || $0.00000000284
|-
| GB Storage Per Second || For storing a GB of data per second || $0.00000018034
|}

==References==

{{reflist}}

HTTP asset certification

2022-07-01T11:06:52Z

Jens:

HTTP asset certification is a protocol that allows canisters to certify bodies of responses to GET HTTP requests.
The receiver of such responses can use the IC public key to authenticate the body of the response.
The protocol relies on [https://smartcontracts.org/docs/interface-spec/index.html#system-api-certified-data Certified data] feature of the IC.

== Canister protocol ==

A canister must follow the following protocol to certify assets:

<ul>
<li>
Construct a [https://smartcontracts.org/docs/interface-spec/index.html#_certificate hash tree] that maps paths of HTTP resources to SHA-256 hashes of their bodies.
An example of such a tree:
<pre>
*root*
└── http_assets
├── index.html -> SHA256(body)
├── ...
└── /css/styles.css -> SHA256(body)
</pre>
</li>
<li>
Compute the root hash of the tree and call [https://smartcontracts.org/docs/interface-spec/index.html#system-api-imports <code>ic0.certified_data_set</code>] with the bytes of the hash as the argument.
</li>
<li>
Add a [[#IC-Certificate header]] to each certified HTTP response.
</li>
</ul>

== Validator protocol ==

The validator follows the following steps to validate the certificate of resource at path <code>PATH</code> served by canister <code>CANISTER_ID</code>:

* Hash the body of the HTTP response, obtaining hash <code>DATA_HASH</code>.
* Check that the response contains the <code>IC-Certificate</code> header.
* Decode the <code>certificate</code> and the <code>tree</code> from the value of the <code>IC-Certificate</code> header.
* Check the validity of the certificate as described in the [https://smartcontracts.org/docs/interface-spec/index.html#certification Interface Specification: Certification]. This step requires knowing the IC root key.
* Check that <code>lookup(/http_assets/PATH, tree) = Found(DATA_HASH)</code>
* Check that <code>lookup(/canister/CANISTER_ID/certified_data, certificate.tree) = Found(reconstruct(tree))</code>.

== IC-Certificate header ==

The <code>IC-Certificate</code> header is a Structure Header (as per [https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-header-structure RFC proposal]) with is a dictionary with with members <code>certificate</code> and <code>tree</code>, both of which are Byte Sequences:

<pre>
IC-Certificate: certificate=:<base64(c)>:, tree=:<base64(t)>:
</pre>

where

* <code>c</code> is the a CBOR-encoded certificate (see [https://smartcontracts.org/docs/interface-spec/index.html#certification-encoding Interface Specification: Encoding of certificates]).
* <code>t</code> is a Hash Tree, CBOR-encoded according the CDDL <code>#6.55799(hash-tree)</code> where <code>hash-tree</code> is the corresponding [https://smartcontracts.org/docs/interface-spec/index.html#api-cddl CDDL production in the Interface Specification].

The <code>certificate</code> must be a valid [https://smartcontracts.org/docs/interface-spec/index.html#_certificate Internet Specification: Certificate] with

<pre>
lookup(/canister/<canister_id>/certified_data, certificate.tree)
= Found (reconstruct(tree))
</pre>

The <code>tree</code> exposes the relevant nodes in the <code>/http_assets</code> subtree to allow the client to lookup the request path to get the expected body hash.

=== Example ===

For this example, we fetched <code>/index.html</code> resource of the Internet Identity canister (canister id <code>rdmx6-jaaaa-aaaaa-aaadq-cai</code>) available at https://rdmx6-jaaaa-aaaaa-aaadq-cai.raw.ic0.app/index.html.
The SHA-256 hash of the resource at the moment of fetching is <code>478afb8206ca0b566a7f138e623accd169fa822602d2f6d717fb67d1045f4f0d</code>.
The response contained the following header:

<pre>
IC-Certificate: certificate=:2dn3omR0cmVlgwGDAYMBgwJIY2FuaXN0ZXKDAYMBggRYIIudikoDwH1gRK637olblUhMUX3HlE0Dihj8MTACxGzHgwGCBFggyCRYc8M/ugt8G7C8RPYayn+l4sdBj8gvFotzJELnQ32DAYIEWCA1/+UHZ9SF67w4ssjOi+Jv3ch7WQNzezGmhtuvB+RDpYMCSgAAAAAAAAAHAQGDAYMBgwJOY2VydGlmaWVkX2RhdGGCA1ggWUt10wjWinx0aAWyrNEi/0R7VeuhalDMjGDErzIbZzqCBFgg/VtZRZdYyK/sr3KF2jWeS1rblF+4ajwfDv2ZbCGpaTiCBFggSoI5JS0pCusHP4nh6h780ebr961E0lVnFkFwzF5pZaeCBFggcKidPEGiPoFMPYfEyNGsDRYWmry1iGX0HNUEoKhIATeCBFggR0zdKUZOMcm5EHNl5Tee3XWqbq1gArwUGzZ2FH4rWtmCBFggTkwJcNrh0eJ9FutJcn6th9eCbM2KXnloxed0acxmQNeDAYIEWCA6SNH8IT1JMHEDEE99csK1kw7bqHh7kGMfNDs6popfCoMCRHRpbWWCA0nFnbXrts/65xZpc2lnbmF0dXJlWDCkXN2tcvH5b+xFCzfkuJMqrZDcplfW8vDziJwzx08WOPI4rh2TIGYZ3R6dgQTF0CA=:, tree=:2dn3gwGDAktodHRwX2Fzc2V0c4MBggRYIDgtAGcz5VvevwiEwwZB9zpkt17C9LE6o/O37bEwQUawgwGDAksvaW5kZXguaHRtbIIDWCBHivuCBsoLVmp/E45iOszRafqCJgLS9tcX+2fRBF9PDYIEWCCx2L8SfJwOydBkUxjc8tKXDVUeoiw8qEYI+8b+HRWIWYIEWCAqZ+3yoFSA9s+jbLFbtcVz+wi0HF9x51Kx38qPcBhiDA==:
</pre>

We can extract the following data from the header value:

<pre>
ROOT HASH: 0b2d843df534ac8ed2331fe2782deb71d23a08d9b4019a8fa695ec7fde93de36
TREE HASH: 594b75d308d68a7c746805b2acd122ff447b55eba16a50cc8c60c4af321b673a
SIGNATURE: a45cddad72f1f96fec450b37e4b8932aad90dca657d6f2f0f3889c33c74f1638f238ae1d93206619dd1e9d8104c5d020
CERTIFICATE TIME: 2022-02-02T08:23:24.851277509+00:00
CERTIFICATE TREE:
HashTree {
root: Fork(
Fork(
Fork(
Label("canister", Fork(
Fork(
Pruned(8b9d8a4a03c07d6044aeb7ee895b95484c517dc7944d038a18fc313002c46cc7),
Fork(
Pruned(c8245873c33fba0b7c1bb0bc44f61aca7fa5e2c7418fc82f168b732442e7437d),
Fork(
Pruned(35ffe50767d485ebbc38b2c8ce8be26fddc87b5903737b31a686dbaf07e443a5),
Label(0x00000000000000070101, Fork(
Fork(
Label("certified_data", Leaf(0x594b75d308d68a7c746805b2acd122ff447b55eba16a50cc8c60c4af321b673a)),
Pruned(fd5b59459758c8afecaf7285da359e4b5adb945fb86a3c1f0efd996c21a96938),
),
Pruned(4a8239252d290aeb073f89e1ea1efcd1e6ebf7ad44d25567164170cc5e6965a7),
)),
),
),
),
Pruned(70a89d3c41a23e814c3d87c4c8d1ac0d16169abcb58865f41cd504a0a8480137),
)),
Pruned(474cdd29464e31c9b9107365e5379edd75aa6ead6002bc141b3676147e2b5ad9),
),
Pruned(4e4c0970dae1d1e27d16eb49727ead87d7826ccd8a5e7968c5e77469cc6640d7),
),
Fork(
Pruned(3a48d1fc213d49307103104f7d72c2b5930edba8787b90631f343b3aa68a5f0a),
Label("time", Leaf(0xc59db5ebb6cffae716)),
),
),
}
TREE:
HashTree {
root: Fork(
Label("http_assets", Fork(
Pruned(382d006733e55bdebf0884c30641f73a64b75ec2f4b13aa3f3b7edb1304146b0),
Fork(
Label("/index.html", Leaf(0x478afb8206ca0b566a7f138e623accd169fa822602d2f6d717fb67d1045f4f0d)),
Pruned(b1d8bf127c9c0ec9d0645318dcf2d2970d551ea22c3ca84608fbc6fe1d158859),
),
)),
Pruned(2a67edf2a05480f6cfa36cb15bb5c573fb08b41c5f71e752b1dfca8f7018620c),
),
}
</pre>

== Limitations ==

* The protocol supports only one resource per path. This does not work well with content negotiation protocol.
* The protocol does not support certification of HTTP statuses and headers. Only resource bodies can be certified.

== Canisters using HTTP asset certification ==

* [https://github.com/dfinity/internet-identity/blob/7ff3dd51dd98c7b1b43d83950c9f31ea7159103d/src/internet_identity/src/main.rs#L775 Internet Identity canister]
* [https://github.com/dfinity/nns-dapp/blob/49126394df77b9583e508277fc736eda51de47be/rs/src/assets.rs#L123 NNS frontend]
* [https://github.com/dfinity/certified-assets Certified assets canister]

== Validators ==

* [https://github.com/dfinity/ic/tree/master/typescript/service-worker Certifying Service Worker]
* [https://github.com/dfinity/icx-proxy/blob/b0de0437fe6806a96d942465e5ee284c23b812e8/src/main.rs#L470 ICX proxy]

HTTP asset certification

2022-07-01T11:00:45Z

Jens:

HTTP asset certification is a protocol that allows canisters to certify bodies of responses to GET HTTP requests.
The receiver of such responses can use the IC public key to authenticate the body of the response.
The protocol relies on [https://smartcontracts.org/docs/interface-spec/index.html#system-api-certified-data Certified data] feature of the IC.

== Canister protocol ==

A canister must follow the following protocol to certify assets:

<ul>
<li>
Construct a [https://smartcontracts.org/docs/interface-spec/index.html#_certificate hash tree] that maps paths of HTTP resources to SHA-256 hashes of their bodies.
An example of such a tree:
<pre>
*root*
└── http_assets
├── index.html -> SHA256(body)
├── ...
└── /css/styles.css -> SHA256(body)
</pre>
</li>
<li>
Compute the root hash of the tree and call [https://smartcontracts.org/docs/interface-spec/index.html#system-api-imports <code>ic0.certified_data_set</code>] with the bytes of the hash as the argument.
</li>
<li>
Add a [[#IC-Certificate header]] to each certified HTTP response.
</li>
</ul>

== Validator protocol ==

The validator follows the following steps to validate the certificate of resource at path <code>PATH</code> served by canister <code>CANISTER_ID</code>:

* Hash the body of the HTTP response, obtaining hash <code>DATA_HASH</code>.
* Check that the response contains the <code>IC-Certificate</code> header.
* Decode the <code>certificate</code> and the <code>tree</code> from the value of the <code>IC-Certificate</code> header.
* Check the validity of the certificate as described in the [https://smartcontracts.org/docs/interface-spec/index.html#certification Interface Specification: Certification]. This step requires knowing the IC root key.
* Check that <code>lookup(/http_assets/PATH, tree) = Found(DATA_HASH)</code>
* Check that <code>lookup(/canister/CANISTER_ID/certified_data, certificate.tree) = Found(reconstruct(tree))</code>.

== IC-Certificate header ==

The <code>IC-Certificate</code> header is a Structure Header (as per [https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-header-structure RFC proposal]) with is a dictionary with with members <code>certificate</code> and <code>tree</code>, both of which are Byte Sequences:

<pre>
IC-Certificate: certificate=:<base64(c)>:, tree=:<base64(t)>:
</pre>

where

* <code>c</code> is the a CBOR-encoded certificate (see [https://smartcontracts.org/docs/interface-spec/index.html#certification-encoding Interface Specification: Encoding of certificates]).
* <code>t</code> is a Hash Tree, CBOR-encoded according the CDDL <code>#6.55799(hash-tree)</code> where <code>hash-tree</code> is the corresponding [https://smartcontracts.org/docs/interface-spec/index.html#api-cddl CDDL production in the Interface Specification].

The <code>certificate</code> must be a valid [https://smartcontracts.org/docs/interface-spec/index.html#_certificate Internet Specification: Certificate] with

<pre>
lookup(/canister/<canister_id>/certified_data, certificate.tree)
= Found (reconstruct(tree))
</pre>

The <code>tree</code> exposes the relevant nodes in the <code>/http_assets</code> subtree to allow the client to lookup the request path to get the expected body hash.

=== Example ===

For this example, we fetched <code>/index.html</code> resource of the Internet Identity canister (canister id <code>rdmx6-jaaaa-aaaaa-aaadq-cai</code>) available at https://rdmx6-jaaaa-aaaaa-aaadq-cai.raw.ic0.app/index.html.
The SHA-256 hash of the resource at the moment of fetching is <code>478afb8206ca0b566a7f138e623accd169fa822602d2f6d717fb67d1045f4f0d</code>.
The response contained the following header:

<pre>
IC-Certificate: certificate=:2dn3omR0cmVlgwGDAYMBgwJIY2FuaXN0ZXKDAYMBggRYIIudikoDwH1gRK637olblUhMUX3HlE0Dihj8MTACxGzHgwGCBFggyCRYc8M/ugt8G7C8RPYayn+l4sdBj8gvFotzJELnQ32DAYIEWCA1/+UHZ9SF67w4ssjOi+Jv3ch7WQNzezGmhtuvB+RDpYMCSgAAAAAAAAAHAQGDAYMBgwJOY2VydGlmaWVkX2RhdGGCA1ggWUt10wjWinx0aAWyrNEi/0R7VeuhalDMjGDErzIbZzqCBFgg/VtZRZdYyK/sr3KF2jWeS1rblF+4ajwfDv2ZbCGpaTiCBFggSoI5JS0pCusHP4nh6h780ebr961E0lVnFkFwzF5pZaeCBFggcKidPEGiPoFMPYfEyNGsDRYWmry1iGX0HNUEoKhIATeCBFggR0zdKUZOMcm5EHNl5Tee3XWqbq1gArwUGzZ2FH4rWtmCBFggTkwJcNrh0eJ9FutJcn6th9eCbM2KXnloxed0acxmQNeDAYIEWCA6SNH8IT1JMHEDEE99csK1kw7bqHh7kGMfNDs6popfCoMCRHRpbWWCA0nFnbXrts/65xZpc2lnbmF0dXJlWDCkXN2tcvH5b+xFCzfkuJMqrZDcplfW8vDziJwzx08WOPI4rh2TIGYZ3R6dgQTF0CA=:, tree=:2dn3gwGDAktodHRwX2Fzc2V0c4MBggRYIDgtAGcz5VvevwiEwwZB9zpkt17C9LE6o/O37bEwQUawgwGDAksvaW5kZXguaHRtbIIDWCBHivuCBsoLVmp/E45iOszRafqCJgLS9tcX+2fRBF9PDYIEWCCx2L8SfJwOydBkUxjc8tKXDVUeoiw8qEYI+8b+HRWIWYIEWCAqZ+3yoFSA9s+jbLFbtcVz+wi0HF9x51Kx38qPcBhiDA==:
</pre>

We can extract the following data from the header value:

<pre>
ROOT HASH: 0b2d843df534ac8ed2331fe2782deb71d23a08d9b4019a8fa695ec7fde93de36
TREE HASH: 594b75d308d68a7c746805b2acd122ff447b55eba16a50cc8c60c4af321b673a
SIGNATURE: a45cddad72f1f96fec450b37e4b8932aad90dca657d6f2f0f3889c33c74f1638f238ae1d93206619dd1e9d8104c5d020
CERTIFICATE TIME: 2022-02-02T08:23:24.851277509+00:00
CERTIFICATE TREE:
HashTree {
root: Fork(
Fork(
Fork(
Label("canister", Fork(
Fork(
Pruned(8b9d8a4a03c07d6044aeb7ee895b95484c517dc7944d038a18fc313002c46cc7),
Fork(
Pruned(c8245873c33fba0b7c1bb0bc44f61aca7fa5e2c7418fc82f168b732442e7437d),
Fork(
Pruned(35ffe50767d485ebbc38b2c8ce8be26fddc87b5903737b31a686dbaf07e443a5),
Label(0x00000000000000070101, Fork(
Fork(
Label("certified_data", Leaf(0x594b75d308d68a7c746805b2acd122ff447b55eba16a50cc8c60c4af321b673a)),
Pruned(fd5b59459758c8afecaf7285da359e4b5adb945fb86a3c1f0efd996c21a96938),
),
Pruned(4a8239252d290aeb073f89e1ea1efcd1e6ebf7ad44d25567164170cc5e6965a7),
)),
),
),
),
Pruned(70a89d3c41a23e814c3d87c4c8d1ac0d16169abcb58865f41cd504a0a8480137),
)),
Pruned(474cdd29464e31c9b9107365e5379edd75aa6ead6002bc141b3676147e2b5ad9),
),
Pruned(4e4c0970dae1d1e27d16eb49727ead87d7826ccd8a5e7968c5e77469cc6640d7),
),
Fork(
Pruned(3a48d1fc213d49307103104f7d72c2b5930edba8787b90631f343b3aa68a5f0a),
Label("time", Leaf(0xc59db5ebb6cffae716)),
),
),
}
TREE:
HashTree {
root: Fork(
Label("http_assets", Fork(
Pruned(382d006733e55bdebf0884c30641f73a64b75ec2f4b13aa3f3b7edb1304146b0),
Fork(
Label("/index.html", Leaf(0x478afb8206ca0b566a7f138e623accd169fa822602d2f6d717fb67d1045f4f0d)),
Pruned(b1d8bf127c9c0ec9d0645318dcf2d2970d551ea22c3ca84608fbc6fe1d158859),
),
)),
Pruned(2a67edf2a05480f6cfa36cb15bb5c573fb08b41c5f71e752b1dfca8f7018620c),
),
}
</pre>

== Limitations ==

* The protocol supports only one resource per path. This does not work well with content negotiation protocol.
* The protocol does not support certification of HTTP statuses and headers. Only resource bodies can be certified.

== Canisters using HTTP asset certification ==

* [https://github.com/dfinity/internet-identity/blob/7ff3dd51dd98c7b1b43d83950c9f31ea7159103d/src/internet_identity/src/main.rs#L775 Internet Identity canister]
* [https://github.com/dfinity/nns-dapp/blob/49126394df77b9583e508277fc736eda51de47be/rs/src/assets.rs#L123 NNS frontend]
* [https://githug.com/dfinity/certified-assets Certified assets canister]

== Validators ==

* [https://github.com/dfinity/ic/tree/master/typescript/service-worker Certifying Service Worker]
* [https://github.com/dfinity/icx-proxy/blob/b0de0437fe6806a96d942465e5ee284c23b812e8/src/main.rs#L470 ICX proxy]

Canister smart contract

2022-02-08T09:43:28Z

Jens:

Canisters are smart contracts that scale — interoperable compute units designed for internet-scale services. Software built on the Internet computer is composed of canisters. In addition to being composable, canisters support tokenization.

Some key design features of canisters include:
* '''Higher throughput and lower latency''' for processing smart contract transactions.
* '''Cost effectiveness''' allowing applications to compute and store data at a fraction of the cost of other platforms.
* '''Scalability''' to process unbounded volumes of smart contract data and computation natively because it can grow in capacity by adding more nodes to the network.

==From smart contracts to canisters==
A smart contract is a piece of software or a computer program that acts on cryptography verified inputs and produces cryptography certified results while maintaining the integrity of its internal state. For a smart contract to be trusted, it has to be run on a decentralized blockchain like Ethereum or, since its launch in May 2021, on the Internet Computer blockchain network.

Smart contracts have huge advantages over traditional software in that they maintain a chain of trust from inputs to outputs and cannot be tampered with.

Canisters are first and foremost smart contracts. However, there are also other ways of looking them which may be easier to understand from different perspectives.
* A canister is similar to a process, as in an operating system.
* A canister is similar to a container, as used by docker and the open container initiative.
* A canister is a WebAssembly module instance.
* A canister is an actor, as in the actor model.

==Canisters as smart contracts==
As mentioned above, a canister deployed on a subnetwork is tamper-proof in the sense that its state can only be modified by messages included in the subnet blockchain, and the subnet blockchain follows the Internet Computer Protocol.

One key difference between smart contracts deployed on the Internet Computer and on a traditional blockchain is how data from smart contracts can be verified. The Internet Computer is powered by Chain Key Cryptography which enables any artifact certified by any smart contract running on any subnet blockchain to be verified using a single 48-byte public key for the whole Internet Computer. This is in contrast to traditional blockchains, where you need the entire blockchain from Genesis to verify the current state of affairs. For example, to validate the outcome of a smart contract on Ethereum, an open Ethereum client needs to download 400 gigabytes and this only increases in time.

A useful analogy is that between a traditional database and its transaction log. A subnet blockchain is the transaction log of the cryptographically certified subnet state. In a traditional blockchain, the whole transaction log needs to be replayed to certify the state of smart contracts running on the blockchain. On a subnet blockchain, the subnetwork state, i.e., the state of all smart contracts running on the blockchain, is periodically recertified (currently every 100 blocks) so the whole subnet blockchain doesn't need to be kept around forever, or, if need be, it can be stored away as a backup. This gives smart contracts running on the Internet Computer clear scalability advantages over smart contracts running on traditional blockchains.

For example, on the Internet Computer, the current cost in cycles, the equivalent of "gas" on Ethereum, is around $5 per year to store 1 Gigabyte of data. Storing 1 Gigabyte of data will cost millions of dollars, but then it is of course stored indefinitely, or, as long as Ethereum exists, as it is burned into the blockchain.

==Canisters as processes==
A canister is much like a process in an operating system like Linux, MacOS, or Windows. The operating system keeps track of valid memory ranges for a process, while a canister has a boundary on its linear memory that’s enforced by the subnetwork.
The operating system scheduler wakes up a process when there is work to be done, while the subnetwork schedules the execution of canisters.
The operating system maintains state on behalf of a process, like open file descriptors and the parent process. Similarly, the Internet Computer maintains state on behalf of a canister, but instead of things like file descriptors, it keeps track of the canister's balance of cycles, outstanding calls, permissions, and more.
Just as a process cannot directly modify its table of file descriptors, a canister cannot directly modify its balances of cycles.

The operating system provides functionality to processes that allow them to perform special operations, like manipulating files and communicating with peripheral devices. Similarly, the Internet Computer provides APIs to canisters so that they can:
* make payments;
* call out to other canisters;
* create and manage canisters;
* manage permissions; and
* get the system time - a non-trivial function in a distributed system.

A unique feature of the Internet Computer is that it provides access to secure randomness. In the future, canisters will also be able to sign Bitcoin and Ethereum transactions through such APIs.

Behind the scenes, the biggest difference between a process and a canister is that a canister is replicated over all nodes in a subnetwork.
When a process malfunctions it crashes, but when a canister malfunctions, caused by a trap in WebAssembly, it does not crash. Instead its state is rolled back to what it was before the current message started executing, so that the canister can continue executing new messages.
Of course, this is of little help if the canister crashes on all of the messages it receives, but it is a very useful safeguard against accidentally missed cases in the logic of a canister.
In fact, a canister cannot terminate in the same way a process can terminate — because there is no exit() or abort() system call. A canister can only be removed from the Internet Computer by a controller through an administrative command. A controller of a canister is a user or another canister that is allowed to perform administrative commands, such as removing or updating the canister.
A canister controlling another canister is a key ingredient when building autonomous or self-governing services on the Internet Computer.

==Canisters as containers==
The meaning of the word canister is similar to the word container, in fact, a canister is typically understood as a cylindrical container. And, indeed, the canister concept has several things in common with the container concept.

Docker provides the following definition: "A container is a standard unit of software that packages up code and all its dependencies so the application runs quickly and reliably from one computing environment to another."

Containers and canisters are also similar in that they can be running and paused (container) or stopped (canisters). They can be moved around while stopped.
Containers run a process inside them so they also have to deal with the process exiting.

Thus, the main difference between containers and canisters is that a canister is a smart contract, i.e., it provides cryptographic guarantees, and it runs in a decentralized and thus trusted environment, namely on a subnet blockchain.

==Canisters as WebAssembly instances==
A canister is much like a [https://webassembly.org/ WebAssembly] module instance. This is more than just an analogy — this is how canisters are actually implemented on the Internet Computer.

Technically, the code part of a canister is a WebAssembly module that imports the System API; that is, the functionality provided to the canister by the Internet Computer. Moreover, a canister can export an API of its own, which can be called by users and other canisters.

According to the WebAssembly specification: “A module instance is the dynamic representation of a module, complete with its own state and execution stack.” Therefore, a canister deployed on a subnet blockchain is a WebAssembly module instance, not just a WebAssembly module — an important distinction - since there could be many canisters running the same WebAssembly module.

Canisters use orthogonal persistence to make it seem like the module instance lives forever, rendering databases or file I/O obsolete. To persistently store a variable, developers can just write the variable to memory. The operation of persisting the data is completely transparent to the developer, and orthogonal in the sense that the developer doesn't have to do anything special to persist the data.

All “writes” to a canister’s linear memory are tracked, for two reasons. First, so that failed computations or WebAssembly traps can be rolled back. Next, if one replica in a subnetwork crashes due to unforeseen events such as power outages, when the replica comes back online, it will request modified pages from other replicas, so it can resume operation.
This is how the Internet Computer maintains the illusion of providing WebAssembly module instances with indefinite lifetime.

Embracing WebAssembly gives the Internet Computer several benefits:
* Canisters can be written in any language that can compile to WebAssembly (e.g. Motoko, Rust), and canisters written in different languages are fully interoperable.
* WebAssembly is deterministic, except for a few edge cases that are easy to rule out.
* WebAssembly has formal semantics. Over a longer time horizon, we expect to see end-to-end formally verified WebAssembly execution environments, for additional security.

Moreover, the Internet Computer will evolve with the WebAssembly specification, adding support for new features as they become mature enough.

==Canisters as actors==
The actor model is a mathematical model of concurrent computation, where, in response to a message, an actor can modify its state, send messages, and create more actors.

* A canister is like an actor in many respects. For example, an actor has:
* a private state that can only be modified by the canister itself;
* a single thread of execution, so it does not need lock-based synchronization;
* the ability to communicate with other canisters through asynchronous messages; and
* the ability to create new canisters.

An important difference between traditional actors and canisters is that canisters on the Internet Computer have bidirectional message passing. Messages are divided into requests and responses, where requests can be replied to and the Internet Computer keeps track of the callback for responses.

In actor terminology, each actor has a mailing address that is used to receive messages. A canister also has a mailing address, which happens to look similar to an IPv6 address.

A single canister has only one thread of execution for updates, but the Internet Computer executes a potentially massive number of canisters in parallel. In addition, we make a distinction between requests that need to update the state of a canister, and queries, which cannot modify the state of a canister.

While a canister's update throughput is limited by consensus of the blockchain and the single thread of execution, a canister can serve hundreds of queries concurrently, achieving throughput in the order of thousands of queries per second, and latency measured in milliseconds.

To complete this picture, it should be added that end users also participate as actors in the model. This means that browsers and mobile apps can directly perform update and query operations on canisters.

In addition, the Motoko programming language, which is tailored to the Internet Computer, is inspired by the actor model.

==Advantages over other types of smart contracts==
Canisters have all the features of smart contracts on other blockchains (such as Ethereum). "In contrast to smart contracts, however, canisters have performance characteristics that makes it possible to use them to build software services that scale<ref>https://medium.com/dfinity/software-canisters-an-evolution-of-smart-contracts-internet-computer-f1f92f1bfffb</ref>. Canisters are better suited for distributed systems and concurrency because of their embracing of the [https://en.wikipedia.org/wiki/Actor_model Actor model].

==Statistics==
The number of canisters on the IC are represented in the [https://dashboard.internetcomputer.org/ IC dashboard].

==See Also==
* Developer documentation on [https://smartcontracts.org/docs/quickstart/quickstart-intro.html Building smart contracts]
* [[Trust in canisters]]

==References==

Internet Computer wiki

2022-02-08T08:48:33Z

Jens:

==Welcome!==

This is the wiki for the Internet Computer (IC), the world's fastest and most powerful blockchain network<ref>https://medium.com/dfinity/the-internet-computers-transaction-speed-and-finality-outpace-other-l1-blockchains-8e7d25e4b2ef</ref>. The goal of the wiki is to be a general source of information for and by the IC community. Topics can range as varied as cryptography, governance of the network, user experience, tokenomics, or developer-facing tutorials.

==Introduction to the Internet Computer==
The Internet computer is the fastest and most scalable general-purpose blockchain. It was launched by DFINITY in May 2021 and works towards realising a blockchain singularity by 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 (chain-key cryptography), programming languages (Motoko) and others.

===Most common place to start===
* [https://dfinity.org/icig.pdf Internet Computer: Infographic]

===For general audience===
* [[Internet Computer overview]]
* [[Internet Computer vision]]
* [https://dfinity.org/roadmap/ Internet Computer roadmap]

===For more technical audience===
* [https://eprint.iacr.org/2022/087 "Internet Computer for Geeks" paper]

==For Dapp Users ==

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.

Examples:
* [[Introduction to the Internet Computer for dapp users]]
* [[Index of dapps on the Internet Computer]]
* [[Internet Identity for dapp users]]

See more in [[Internet Computer for dapp users]]

== For ICP Token-holders, Investors and Neuron Holders==

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.

Examples:
* [[ICP token]]
* [[Managing ICP holdings]]
* [[Staking, voting and rewards]]
* [[Governance of the Internet Computer]]
* [[Network Nervous System]]

See more in [[Internet Computer token-holders, investors and neuron holders]].

== For Smart Contract and Dapp Developers ==

The Internet Computer (IC) is a new platform for executing smart contracts. This section contains information for developers such as links to documentation, developer forums, and relevant dashboards.

Examples:
* [[Canisters (dapps/smart contracts)]]
* [[Internet Identity technical overview]]
* [https://smartcontracts.org/ Developer documentation on smartcontract.org]
* [https://forum.dfinity.org/ IC community developer forum]
* [[Index of libraries for Internet Computer development]]
* [[Best practices for a high traffic dapp launch]]
* [[Bitcoin integration]]

See more in [[Internet Computer for smart contract and dapp developers]].

== For the Curious, Researchers and Blockchain Enthusiasts ==

This section is for those interested on how the Internet Computer works under the hood. This section touches many different subject areas from cryptography, consensus protocols, virtual machines, operating systems, networking, distributed systems, etc.

Examples:
* [https://dfinity.org/howitworks/ How the Internet Computer Works]
* [https://dashboard.internetcomputer.org/ Internet Computer dashboard]
* [[Internet Computer performance]]
* [[DFINITY Foundation]]
* [[Bitcoin integration]]

See more in [[Internet Computer for researchers and blockchain enthusiasts]].

== FAQs, Tutorials, and How-tos==
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.

===FAQs===
* [[FAQ]]

===Tutorials===
Example:
* [[Managing ICP holdings]]

See more in [[Tutorials]].

=== How-tos ===
Example:
* [[How-To: Claim neurons for seed participants]]
* [[How-To: Create an NNS motion proposal]]

See more in [[How-Tos]].

==Contributing to the Wiki==

=== How to contribute ===
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]].

==References==

Internet Computer wiki

2022-02-08T08:47:05Z

Jens: Undo revision 1795 by Jens (talk)

==Welcome!==

This is the wiki for the Internet Computer (IC), the world's fastest and most powerful blockchain network<ref>https://medium.com/dfinity/the-internet-computers-transaction-speed-and-finality-outpace-other-l1-blockchains-8e7d25e4b2ef</ref>. The goal of the wiki is to be a general source of information for and by the IC community. Topics can range as varied as cryptography, governance of the network, user experience, tokenomics, or developer-facing tutorials.

==Introduction to the Internet Computer==
The Internet computer is the fastest and most scalable general-purpose blockchain. It was launched by DFINITY in May 2021 and works towards realising a blockchain singularity by 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 (chain-key cryptography), programming languages (Motoko) and others.

===Most common place to start===
* [https://dfinity.org/icig.pdf Internet Computer: Infographic]

===For general audience===
* [[Internet Computer overview]]
* [[Internet Computer vision]]
* [https://dfinity.org/roadmap/ Internet Computer roadmap]

===For more technical audience===
* [https://eprint.iacr.org/2022/087 "Internet Computer for Geeks" paper]

==For Dapp Users ==

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.

Examples:
* [[Introduction to the Internet Computer for dapp users]]
* [[Index of dapps on the Internet Computer]]
* [[Internet Identity for dapp users]]

See more in [[Internet Computer for dapp users]]

== For ICP Token-holders, Investors and Neuron Holders==

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.

Examples:
* [[ICP token]]
* [[Managing ICP holdings]]
* [[Staking and voting]]
* [[Governance of the Internet Computer]]
* [[Network Nervous System]]

See more in [[Internet Computer token-holders, investors and neuron holders]].

== For Smart Contract and Dapp Developers ==

The Internet Computer (IC) is a new platform for executing smart contracts. This section contains information for developers such as links to documentation, developer forums, and relevant dashboards.

Examples:
* [[Canisters (dapps/smart contracts)]]
* [[Internet Identity technical overview]]
* [https://smartcontracts.org/ Developer documentation on smartcontract.org]
* [https://forum.dfinity.org/ IC community developer forum]
* [[Index of libraries for Internet Computer development]]
* [[Best practices for a high traffic dapp launch]]
* [[Bitcoin integration]]

See more in [[Internet Computer for smart contract and dapp developers]].

== For the Curious, Researchers and Blockchain Enthusiasts ==

This section is for those interested on how the Internet Computer works under the hood. This section touches many different subject areas from cryptography, consensus protocols, virtual machines, operating systems, networking, distributed systems, etc.

Examples:
* [https://dfinity.org/howitworks/ How the Internet Computer Works]
* [https://dashboard.internetcomputer.org/ Internet Computer dashboard]
* [[Internet Computer performance]]
* [[DFINITY Foundation]]
* [[Bitcoin integration]]

See more in [[Internet Computer for researchers and blockchain enthusiasts]].

== FAQs, Tutorials, and How-tos==
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.

===FAQs===
* [[FAQ]]

===Tutorials===
Example:
* [[Managing ICP holdings]]

See more in [[Tutorials]].

=== How-tos ===
Example:
* [[How-To: Claim neurons for seed participants]]
* [[How-To: Create an NNS motion proposal]]

See more in [[How-Tos]].

==Contributing to the Wiki==

=== How to contribute ===
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]].

==References==

Internet Computer wiki

2022-02-08T08:42:57Z

Jens: Removed superfluous word "examples"

==Welcome!==

This is the wiki for the Internet Computer (IC), the world's fastest and most powerful blockchain network<ref>https://medium.com/dfinity/the-internet-computers-transaction-speed-and-finality-outpace-other-l1-blockchains-8e7d25e4b2ef</ref>. The goal of the wiki is to be a general source of information for and by the IC community. Topics can range as varied as cryptography, governance of the network, user experience, tokenomics, or developer-facing tutorials.

==Introduction to the Internet Computer==
The Internet computer is the fastest and most scalable general-purpose blockchain. It was launched by DFINITY in May 2021 and works towards realising a blockchain singularity by 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 (chain-key cryptography), programming languages (Motoko) and others.

===Most common place to start===
* [https://dfinity.org/icig.pdf Internet Computer: Infographic]

===For general audience===
* [[Internet Computer overview]]
* [[Internet Computer vision]]
* [https://dfinity.org/roadmap/ Internet Computer roadmap]

===For more technical audience===
* [https://eprint.iacr.org/2022/087 "Internet Computer for Geeks" paper]

==For Dapp Users ==

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.

* [[Introduction to the Internet Computer for dapp users]]
* [[Index of dapps on the Internet Computer]]
* [[Internet Identity for dapp users]]

See more in [[Internet Computer for dapp users]]

== For ICP Token-holders, Investors and Neuron Holders==

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.

* [[ICP token]]
* [[Managing ICP holdings]]
* [[Staking, voting and rewards]]
* [[Governance of the Internet Computer]]
* [[Network Nervous System]]

See more in [[Internet Computer token-holders, investors and neuron holders]].

== For Smart Contract and Dapp Developers ==

The Internet Computer (IC) is a new platform for executing smart contracts. This section contains information for developers such as links to documentation, developer forums, and relevant dashboards.

* [[Canisters (dapps/smart contracts)]]
* [[Internet Identity technical overview]]
* [https://smartcontracts.org/ Developer documentation on smartcontract.org]
* [https://forum.dfinity.org/ IC community developer forum]
* [[Index of libraries for Internet Computer development]]
* [[Best practices for a high traffic dapp launch]]
* [[Bitcoin integration]]

See more in [[Internet Computer for smart contract and dapp developers]].

== For the Curious, Researchers and Blockchain Enthusiasts ==

This section is for those interested on how the Internet Computer works under the hood. This section touches many different subject areas from cryptography, consensus protocols, virtual machines, operating systems, networking, distributed systems, etc.

* [https://dfinity.org/howitworks/ How the Internet Computer Works]
* [https://dashboard.internetcomputer.org/ Internet Computer dashboard]
* [[Internet Computer performance]]
* [[DFINITY Foundation]]
* [[Bitcoin integration]]

See more in [[Internet Computer for researchers and blockchain enthusiasts]].

== FAQs, Tutorials, and How-tos==
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.

===FAQs===
* [[FAQ]]

===Tutorials===

* [[Managing ICP holdings]]

See more in [[Tutorials]].

=== How-tos ===

* [[How-To: Claim neurons for seed participants]]
* [[How-To: Create an NNS motion proposal]]

See more in [[How-Tos]].

==Contributing to the Wiki==

=== How to contribute ===
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]].

==References==

Staking, voting and rewards

2022-02-07T18:28:40Z

Jens:

== Staking & Voting Rewards ==

Stakeholders can earn significant returns on their staked ICP tokens in
the form of voting rewards.

The Internet Computer is a decentralized
platform whose evolution is decided by its
stakeholders through voting. This means decision impacting
the future of the Internet Computer are made by people vested in the
outcome. In return for participation in governance, the Internet Computer gives out voting rewards. Voters can vote actively, or they can use the liquid democracy on the
Internet Computer to automatically follow other voters.

== Key Concepts ==

=== Neurons ===

In order to become vested and obtain voting power, ICP tokens must first
be staked, and then locked up for a length of time greater than 6
months, to at most 8 years.

Just as tokens are held in a user's account, stake is held in a special
account called a "neuron". Each neuron has its own identifier, and
several attributes relating to its stake. These include:

* the length of time it is locked for (the "dissolve delay");
* whether it is currently dissolving toward liquidity;
* and how much reward it has accrued as a result of voting on proposals (the "maturity").

Once a neuron is locked for more than six months, it gains the ability
both to submit proposals and to vote on them. Voting in turn generates
voting rewards, based on how active a neuron is in voting on proposals.
If you vote on every open proposal, you gain the maximum reward.

A neuron can also "follow" other neurons, which causes it to
automatically vote the same as the majority of the neurons that it
follows. All new neurons by default follow neuron 27 held by the ICA, so
any newly staked neuron will generate voting rewards as soon as it is
locked for more than six months. The default following is applied to
most proposal topics, except for proposals with topic Governance, where
neuron holders have to explicitly vote to earn rewards.

=== Voting Power ===

The voting power of a locked neuron is determined by several factors:

* Principally, by its stake. 1 ICP = the power of 1 vote.
* Next, by its lock up duration, or dissolve delay. 6 months grants a 1.06x voting power bonus, and 8 years grants 2x. All other durations scale linearly between.
* Lastly, by its age, or length of time spent locked up without dissolving. 4 years grants a 1.25x bonus, multiplicative with any other bonuses. All other durations between 0 seconds and 4 years scale linearly between.

This means that the maximum voting power, of 2.5 votes per ICP staked,
is only achievable by locking up your neuron for 8 years, and leaving it
in that locked up state for 4 years. At that time you will have the most
voting power for the stake committed.

=== Maturity ===

Maturity represents the voting rewards accumulated in a neuron. Each day
the network rewards participants by allocating to every voting neuron a
portion of the total reward, based both on its voting power at the time
proposals were made, and the number of proposals it voted on.

Some look at maturity as similar to a "dividend" or "interest", but
please note that different tax authorities may take different views on the
subject. ICP stake holders should consult appropriate professionals before deciding on
an interpretation of when maturity becomes income.

For those who wish to compound the gains in their neuron, the most
natural activity is to "merge maturity" at intervals, which has the
effect of minting the neuron's maturity and adding that minted amount
back into the neuron's stake. If you wish to harvest income from the
neuron, you "spawn" maturity into a reward neuron, which mints the
parent neuron's, and moves this maturity into the stake of a new neuron.
It should be noted that if you do neither, and leave those gains in the
form of maturity, it will not add to the minted total of ICP, nor
contribute to your voting power.

== Why Staking Matters ==

To some, staking is seen as an income generator, a way to perform "yield
farming" by locking up ICP and enjoying the benefits of the accrued
maturity. However, staking is not intended solely as an income vehicle.
It is a way of allowing those who invest in the Internet Computer to
decide what happens next with the platform.

When the Internet Computer first launched, all proposals required a
majority vote to pass. Gradually, however, this is changing. After a
recent update it is now possible for proposals to pass with only a
majority among 3% of the total voting power, meaning that proposals
stand a chance even if large entities abstain and the majority of the
network does not vote.

== Voting Rewards ==

Even if you stake only for the purpose of being able to participate in governance and vote on proposals, voting
rewards are an important aspect of neurons. At the very least,
such returns can be compounded to increase your total voting power. So
to better understand staking and reward, it may be helpful to look at
staking from two perspectives:

=== Short-term: voting rewards each day ===

Every day, rewards are granted by the network to each voting neuron. The
percentage of those rewards received by each neuron depend on the
following factors:

* Amount of ICP staked
* Length of dissolve delay
* "Age" of the neuron (time spent in a non-dissolving state)
* Number of eligible proposals the neuron has voted on

For example, if on a single day the NNS has generated 1000 ICP in total
rewards (see below for more on how this is computed), and there were 10
proposals submitted which only two neurons voted on, and:

* Neuron A has a voting power of 20, and voted on all 10 proposals
* Neuron B has a voting power of 80, and voted on all 10 proposals

Then the 1000 ICP would be divided between these two neurons by their
proportional voting power:

* Neuron A with voting power of 20, gets 20% of the total = 200 ICP
* Neuron B with voting power of 80, gets 80% of the total = 800 ICP

If either neuron had only voted for X% of those 10 proposals, it's
reward would be decreased to X% of its maximum eligibility, with the
remainder distributed among the other neurons.

=== Long-term: voting rewards over years ===

As of December 2021, here is the long-term voting rewards curve: https://dashboard.internetcomputer.org/circulation

In the first year, the NNS allocates 10% of the total supply to generate
voting rewards. Note the term "allocates" rather than "mints", because
rewards are not minted until they are spawn, merged or the neuron is
disbursed, so total supply is not automatically increased by rewards
alone. This allocation rate drops linearly until it reaches 5% by year
8. Like all parameters in the NNS, the minting rate can be changed via
NNS proposals, but this is the current rate schedule.

Because the total supply of ICP is a dynamic system with deflation and
inflation, it is impossible to predict what voting rewards will be on any
given day or year in the future. It is relatively easy to predict what
the percentage allocation rate will be months from now, but it is much
harder to predict what the total supply will be both because of
potential changes to the rate, and how often stakeholders will mint
their maturity.

=== Inflationary and Deflationary Mechanisms ===

Deflationary mechanisms for ICP:

* Minting cycles to pay for compute and storage burns ICP to create cycles
* Burning of transaction fees
* Burning of the 1 ICP deposit for failed proposals; note that this only happens at disbursement or merging of neurons, so accumulated fees can persist for a while before finally contributing to deflation.

Inflationary mechanisms for ICP:

* Node providers are paid by minting ICP
* Voting rewards are paid by minting ICP, although this minting only happens at the moment rewards are spawned, maturity is merged, or the neuron is disbursed.

=== Network Factors Affecting Annual Percentage Yield ===

When considering potential Annual Percentage Yield (APY) for ICP staked
in a voting neuron, in addition to the primary factors of the dissolve
delay, neuron age, and amount of stake, there are also network factors
that can affect potential yield. Chief among them are:

* The amount of supply allocated each year to pay rewards;
* The total voting power across all neurons, since rewards are divided equally among neurons according to their voting power;
* Inflationary and deflationary pressures: primarily, minting to pay node providers and spawn rewards, burning to fuel canister cycles, and the other factors mentioned in the previous section.

These factors can affect future returns significantly. Firstly, the
amount of supply began at 10% at genesis, but will fall to 5% after the
first eight years. Secondly, as staking becomes more common and there
are better user interfaces to do it, there will naturally be more
competition. If no one else were staking, returns would be astronomical;
but if nearly everyone is staking, returns will be lower.

Economics are always at play, however. If staking is very popular, it
means the amount of liquid supply would reduce, which would drive up
demand and hence prices. So although returns would drop significantly,
price appreciation should offset the loss in income. Conversely, if most
people dissolve their neurons to trade on the open market, price would
likely drop while returns increase. It is reasonable to assume that over
time an equilibrium will be established, where rates and prices
fluctuate in sympathy based on the macro factors driving demand for ICP
tokens.

DFINITY Foundation

2022-02-07T17:40:41Z

Jens:

'''DFINITY''' is a name for the '''DFINITY Foundation''', or more correctly '''“DFINITY Stiftung”''', a not-for-profit organization headquartered in [[Zürich]], Switzerland, that was originally founded in Zug in October 2016.

==Mission==
DFINITY contributes technology to the [[Internet Computer]] blockchain, provides support for its ecosystem, and advocates for its application as a technology stack. DFINITY holds an endowment of [[ICP token]] that are currently worth billions of dollars, which it sells as needed to fund its operations. While DFINITY has no shareholders or members, DFINITY has one mission: foster the advancement and adoption of the Internet Computer.

A stated objective of DFINITY is to create a blockchain singularity, in which over time, the majority of humanity’s systems and services are rebuilt, and reimagined, upon the [[Internet Computer]] blockchain using a new form of smart contracts called [[canisters]]. DFINITY is held to its mission, which is defined in its notarial deed, by a regulatory framework operated by the Central Switzerland BVG and Foundation Supervisory Authority (ZBSA).

==Organization==
The organization can be described as Blockchain Maximalist and decentralization-forward. DFINITY runs what is arguably blockchain's largest R&D operation, which employs many famous [[cryptographers]], computer science researchers and senior engineers. It currently employs around 200 full-time personnel, with many working from dedicated research centers in locations including Zürich, Switzerland, and California, and from numerous remote teams. DFINITY is constantly integrating new talent into its team and scaling its R&D effort. By its own estimates, it will grow to employ thousands of R&D and operations staff in the coming years.

==History==
The name DFINITY derives from '''D'''ecentralized in'''FINITY''', which was first used by its founder Dominic Williams in 2015 to refer to technical research he had performed with the hope of enabling Ethereum to become a true [[world computer]] blockchain. Once it became apparent that a large and highly specialized team would need to perform years of blue sky R&D to realize the [[world computer]] vision, DFINITY became a standalone project. Today, the [[Internet Computer]] incorporates a blockchain architecture that has been totally rethought from the ground up in order to provide world computer capabilities.

DFINITY has become a go-to organization for talented individuals interested in working at the leading edge of blockchain, computer science and cryptography.

After several years of R&D, which effort continues today, the Internet Computer blockchain underwent [[Genesis]] on the 10th of May 2021.

==See Also==
* [https://dfinity.org DFINITY homepage]
* [https://twitter.com/dfinity DFINITY Twitter]
* [https://medium.com/dfinity DFINITY technical blog]
* [https://forum.dfinity.org/ DFINITY developer forum]
* [https://www.reddit.com/r/dfinity/ DFINITY subreddit]

How to create an Internet Identity

2022-02-07T17:07:12Z

Jens:

It has long been known that usernames and passwords have been a weak point of an individual's security on the web. In order to combat this and provide increased security to users on the Internet Computer (IC), the Internet Identity (II) blockchain authentication system was developed.
Internet Identity enables you to use your devices to authenticate and sign in pseudonymously to dapps on the Internet Computer. Anyone with a traditional HSM device, such as a YubiKey, or mobile devices that contain a TPM chip, such as a laptop or phone can generate Internet Identities and start using dapps on the IC.

==Getting Started==
[[File:Welcome.png|right|200px|Internet Identity welcome page]]Suppose you want to interact with dapps running on the Internet Computer. It's often the case that you will need to authenticate or login to access and use the features of the dapp. Currently, the easiest way to authenticate is by using an identity anchor obtained from Internet Identity.

Internet Identity associates each identity anchor with a unique user number. Dapps the user logs in to do not learn this user number. Instead, Internet Identity creates a pseudonymous identifier on a per user, per dapp basis. The dapp can see it is the same user that logged in before, but does not know user it is or whether the user also uses other dapps.

[https://www.youtube.com/watch?v=oxEr8UzGeBo Click here] to see a demo video of Internet Identity, while below the steps to get started with your own internet identity are described.

The quickest way to get started and generate an identity anchor, is to navigate directly to the Internet Identity dapp: https://identity.ic0.app/
Here, you will be welcomed with a screen prompting you to enter your identity anchor. If you are just getting started, then you need to create an identity anchor by selecting '''Create an Internet Identity Anchor'''.

Alternatively, if you are trying to access a dapp, for example the NNS frontend dapp, you will see that you are prompted to login. When clicking the login button, you will be redirected to the Internet Identity screen (as seen on the right) where you can either login if you have an identity anchor, or create a new one if you don't.

==Creating an Anchor==
[[File:ii_anchor_created.png|right|200px|Internet Identity welcome page]]When you select that you would like to create an Internet identity anchor on the II homepage, you will be directed to a screen where you are prompted to provide the name of the device on which you are generating the anchor, e.g. iPhone, Laptop, Yubikey.
Upon entering the device name, your device will prompt you to allow "identity.ic0.app" to use either a dedicated security key, or with an authentication method of the device you are using, if that option is available.
For example, if your device has biometrics enabled to unlock it, you might see the option to use those as your authentication method. You can also use the password that unlocks your computer or a pin that unlocks your phone, depending on the device you’re using.

Once you grant access, you will be redirected to solve a captcha. After solving this, you will be prompted to choose an account to sign in to "identity.ic0.app". If you are registering for the first time you can select to ''sign in with the Passkey'' (which was generated and is stored on your device) otherwise you can choose to sign in with an external security key.
After that, you will be redirected to a screen which displays your newly created identity anchor! Note that on this screen there is a suggestion to record your identity anchor number. This is the number that you will need to enter to authenticate to dapps running on the IC.

==Establishing recovery methods==
After creating your identity anchor, you will be directed to a page that allows to add a recovery mechanism, or to skip this step. There is a warning here, which notes that if your browser history is cleared, your authentication keys will be deleted from this device. For this reason, it's highly recommended to assign multiple devices or to use a security key or a seed phrase as a recovery mechanism. When you select to add a recovery mechanism, you are given two choices; either generate a seed phrase which you should store securely, or to use an extra security key. [[File:ii_setup_recovery.png|right|200px|Internet Identity recovery setup]]
===Seed phrase===
If you have used digital wallets before, perhaps you are used to securely maintaining seed phrases, if not, it is never too late to learn. Selecting this option generates a cryptographically-secure seed phrase that you can use to recover an identity anchor. Make sure you store this phrase somewhere safe and it is known only to you, as anyone who knows the seed phrase will be able to take full control of this identity anchor. Note that the first string in your seed phrase is the identity anchor. You will need this number to begin the recovery process.
===Security key===
If you choose not to use a seed phrase as a recovery method, you can use a dedicated security key to recover an identity anchor in the event that you lose access to your authorized devices. This key must be different from the ones you actively use to authenticate to Internet Identity using the given identity anchor. Keep this key somewhere safe and ensure it is available only to you. As above, anyone in possession of this security key will be able to take full control of your identity anchor. You will need to know the identity anchor to begin recovery.
===Skip this step===
It is not advisable to skip this step, unless you are sure that you will not need to remember this anchor.

==Adding a Second Device==
[[File:ii_newdevice.png|right|200px|Internet Identity adding a new device]]It is good practice to add a second device for a number of reasons.
* It is often the case that you will want to login to dapps from more than one device, eg. from a mobile phone, and later from a laptop.
* Adding a second device allows to more easily recover your anchor or account should it get lost from one device.
The most straight forward way to add a second device is to navigate to https://identity.ic0.app/ on the device that you would like to add. Once there, you can select the option "Already have an Anchor '''but using a new device'''". After clicking this, you will be directed to a page where you can enter your existing identity anchor.
Upon entering your anchor number and clicking continue, you will be prompted to allow access to either a security key, or your current device. Choose your preference (e.g. Yubikey or fingerprint scan), and then you will be directed to a screen displaying a url (and its equivalent QR code).

[[File:ii_newdeviceQR.png|right|200px|Internet Identity adding a new device link]]To add the new device, you need to enter the url or scan the QR code on the original device with which you first authenticated. For example, if you originally generated your identity anchor on a mobile phone, and now are attempting to add your laptop as a second device, you should scan the QR code generated on the laptop with your phone.
Upon scanning the QR code with the original device, you will be directed to the app where you can confirm that you are attempting to add a new device. One you confirm, you will be asked to name the new device (In the example above, an appropriate name would be 'Laptop').
After this, both devices should appear in the Anchor Management page of identity.ic0.app.

==Authenticating==
When you have created an identity anchor and added devices, logging into dapps is a simple process. When you navigate to a dapp that supports authenticating with Internet Identity, simply click on the login button to be directed to the II frontend where you can enter your anchor number and authenticate.

After this, you will be directed to a page requiring you to authorize the authentication. After selecting '''Proceed''' you will finalize the authentication process and be redirected and logged in to the dapp.
[[File:ii_recover.png|right|200px|Recover a lost identity]]
==Recovering a lost identity==
If you have lost your anchor number and no longer have access to your authorized devices, you can recover your lost identity using either the seed phrase or the security key used during the initial setup process.
[[File:ii_seedphrase.png|right|200px|Recover a lost identity with seed phrase]]
To recover your lost identity, first navigate to https://identity.ic0.app/ and select the '''Lost access and want to recover?''' link at the bottom of the page.
After this, you will be directed to a page asking to enter the anchor number for the lost identity. Note that the first string of the seed phrase is the anchor number, so you can always find it there. Once you enter the anchor number for the identity you are trying to recover, you will be directed to a page that requires you to enter your seed phrase. Once you copy your seed phrase and click continue, your identity will be recovered.

Note that the recovery page on the II dapp is the only page in which you should ever enter your seed phrase.
==Key Features==

===Ease of Use===
Internet Identity provides a secure way for users to generate identity anchors and authenticate to applications running on the Internet Computer without the need to remember and manage passwords.

===Privacy===
No personal identifying information is needed to generate an anchor and as Internet Identity generates different pseudonyms for different applications, privacy is provided for users as interactions across dapps cannot be tracked.

===Availability===
Since an anchor's key material is generated and stored on the user's device, it is not the case that a particular service or application can hinder the availability of an individual's anchor as a method of authentication.

==Quick Links==
* For a more technical overview check the [[Internet_Identity_technical_overview|II technical overview]] page.
* [https://medium.com/dfinity/internet-identity-the-end-of-usernames-and-passwords-ff45e4861bf7 Internet Identity Medium post] which gives an overview of Internet Identity and how to get started.
* [https://medium.com/dfinity/web-authentication-and-identity-on-the-internet-computer-a9bd5754c547 Web authentication medium post] where Björn Tackmann gives an overview of the core ideas of web authentication and describes how Internet Identity came to be the way it is.
* [https://www.youtube.com/watch?v=oxEr8UzGeBo Video Demo] showcasing Internet Identity and showing how to generate an anchor.
* [https://smartcontracts.org/docs/ic-identity-guide/what-is-ic-identity.html Developer Centre] introduction to Internet Identity.

==FAQ==

===Do I need to use Internet Identity to use all dapps on the IC?===
No, II is an authentication ''option'' that can be used by the developers of the dapps. Developers may choose they do not need authentication, or if they do want authentication, they may opt for another solution. II is very popular because building authentication systems is very hard to do securely so it is helpful for developers but they have freedom of choice.

Examples:
* [https://m7sm4-2iaaa-aaaab-qabra-cai.raw.ic0.app/ Motoko Playground] is an example of a dapp on the IC that does not require II and instead allows direct anonymous usage.

===How do I get an identity anchor from Internet Identity?===
The one and only place to generate an identity anchor is to visit https://identity.ic0.app/.

Detailed instructions can be found by visiting https://smartcontracts.org/docs/ic-identity-guide/auth-how-to.html

===Do I really need to link another device or save the seed-phrase?===
Although it is not necessary, it is really useful to link another device or to save the seed-phrase in case you lose access to your identity anchor on a particular device. Further, as your identity anchor may be used to generate accounts for wallets or dapps, access to these may also be lost if you lose access to your identity anchor.

===What happens if I lose my device?===
If you lose your device and want to recover, you can click on the 'Lost access and want to recover' link at https://identity.ic0.app/.

If you have an identity anchor tied to only one device and you lose that one device, you will be locked out. As a best practice, we recommend adding multiple devices and recovery mechanisms to every identity anchor.

===How can I add more devices?===
If you want to add another device, you can click on the 'Already have an anchor but using a new device?' link at https://identity.ic0.app/

Detailed instructions can be found here: https://smartcontracts.org/docs/ic-identity-guide/auth-how-to.html#_add_a_device

===Does Internet Identity share my personal information with dapps when I authenticate?===
No. Internet Identity uses a different principal (a "pseudonym") for each dapp that you authenticate to using Internet Identity. Since the pseudonyms Internet Identity generates for you are different for each dapp, dapps cannot use them to track you outside of their realm.

===Does Internet Identity support Windows Hello?===
Yes! Internet Identity supports authenticating via Windows Hello. If Windows Hello is set up on your PC then Internet Identity will offer you to authenticate through Windows Hello.

Detailed instructions can be found here: https://smartcontracts.org/docs/ic-identity-guide/hello-guide.html

===Why can't I log in with a new device?===
If you can't log in with an existing identity anchor, it may be the case that the anchor hasn't been added to the new device. If this is the case, simply visit https://identity.ic0.app/ , click on the 'Already have an anchor but using a new device?' link, add the device and try again.

It may also be the case that the face ID or the fingerprint system is not enabled on the device. Ensure that these are enabled, and try to log in again.

=== Is there a way to revoke a dapp's access to my identity anchor?===
There is no explicit revocation method, but privilege delegation to Internet Identity is limited in time, so will expire. Alternatively, simply once the browser tab is closed, the delegation is gone.

Internet Computer vision

2022-02-07T16:42:11Z

Jens:

'''The Internet Computer''' blockchain is a real "world computer" that removes the traditional limitations of smart contracts using advanced new cryptography and distributed protocols.

==Vision and Value Propositions==

===Web speed===

Smart Contracts are fast and performant to allow developers to build anything. The design goal is that developers can build consumer-facing experiences that are as fast as they would expect from centralized servers. Dapp developers do not need to choose between "smart contracts" and "fast." In short, dapp users experience is so fast that users should not notice if their web experience is running on a blockchain or centralized provider.

From a blockchain POV, [[Internet Computer Performance]] performance tests shows the IC latency at 200 milliseconds for query calls (reads) and 2 seconds for update calls (writes). As of December 1, 2021, The Internet Computer can handle 250,000 queries per second and 11,500 update calls per second.

===Environment and cost===

====Low direct costs====
Unlike most blockchains, the efficiency and costs of the Internet Computer approaches the traditional IT stack so its is economically feasible to host dapps with lots of data and content.

For comparison:

{| class="wikitable"
|-
! Blockchain !! Storage Costs
|-
| Ethereum || $350,000,000 USD per GB per year
|-
| Internet Computer || $5 USD per GB per year
|}

====Low indirect costs====

Smart contracts as "secure-by-default" that comes with data replication removes a lot of software complexity that developers do not need to build. The design intent of the IC is to make development and deployment simple to reduce the time necessary to build and maintain software compared to traditional systems.

===Network scales without limit===

Most blockchains have transactions limits baked into the protocol (e.g. adding more servers to Bitcoin does not increase its transaction volume) and need cumbersome workarounds to address scaling. The Internet Computer can process unbounded volumes of smart contract data and computation natively because it can grow in capacity by adding more nodes. That is how the network went from 19 blocks per second in July 2021 to 30 blocks per second by December 2021.

See Internet Computer Dashboard: https://dashboard.internetcomputer.org/

===Network scaling is transparent to systems===

Network scaling is transparent to smart contract code which means that dapp developers do not need to worry about details about the network in order for their dapps to operate or scale. For example:

<blockquote>
Although subnets are the fundamental building blocks of the overall Internet Computer network, they’re transparent to users and software. Users and canister software only need to know the identity of a canister to call the functions that it offers.
</blockquote>

Source: https://medium.com/dfinity/a-technical-overview-of-the-internet-computer-f57c62abc20f

===Web serving===

====Dapp code hosted and executed on-chain====
Smart contracts on the Internet Computer serve web content directly to users. This is a distinguishing feature, on other blockchains a small part of the dapp logic runs in a smart contract, but the actual consumer-facing web or interface is hosted on a centralized cloud provider (e.g. AWS) instead of being served directly from the blockchain.

The Internet Computer serving dapps whose code is hosted and executed entirely on-chain unlocks the Web3 potential of smart contracts.

====Reverse Gas Model (AKA "canister pays")====
In dapps built on Ethereum (as an example), users require a wallet or tokens to use it. This slows down adoption of dapps because using a dapp is not as simple as clicking on a website link; it requires users to buy tokens, install browser plugins, etc. Internet Computer dapps have he "Reverse Gas model" where users can interact with a dapp without having to pay in tokens since the canister can store a certain amount of [[cycles]] and pay for the user.

As an example, the Motoko Playground dapp is hosted and executed entirely on-chain and it does not require visitors to pay for the computation: https://m7sm4-2iaaa-aaaab-qabra-cai.raw.ic0.app/

====Internet Identity====

[[Internet_Identity_technical_overview|Internet Identity]] is a blockchain authentication system that enables you to sign in securely and pseudonymously to dapps on the Internet Computer. This makes logging into dapps easy and safe for consumers.

===Network Nervous System===

The [[Network Nervous System]] (NNS) is the control center where the Internet Computer’s nodes and subnets are organized, tracked, and managed. The NNS is an automated in-protocol governance system that makes the network self-directed. Unlike Bitcoin or Ethereum, this means the Internet Computer blockchain can update itself via community-led proposals so the community controls the network.

Advantages of the NNS:
* Seamless community-driven evolution and governance without disruptive hard forks
* Gives control of the network to token holders as well as node providers (in Bitcoin or Ethereum, only nodes affect the upgrades of the network)
* Accelerates the number of improvements or updates to the network. In 2021, the Internet Computer had dozens of updates, giving the IC very fast development iterations while also being decentralized.

===Novel “canister” smart contract framework===

Smart contracts have proven to be powerful new types of software programs because of their tamperproof nature. They can host financial contracts and systems with billions of dollars in value. However, as the scope of smart contracts increase, performance really matters. Building an "airbnb clone" entirely with Ethereum smart contracts would be impractical due to performance bottlenecks on individual smart contracts, but it is easy with the Internet Computer's canisters (dapps/smart contracts). A rough but helpful analogy may be "you can build complex calculations and logic with an excel spreadsheet, but you would not build Twitter by cobbling up many spreadsheets."

Attributes that make Internet Computer smart contracts powerful ways of building dapps:
* Orthogonal persistence (data lives in persistent memory pages) making managing data much easier
* [[Actor model]] gives dapps a time-tested model for concurrency that scales (deterministic parallelism, internally and externally)
* Dapps get access to system APIs uncommon in Ethereum smart contracts (but common tools in centralized solutions) such as public randomness
* Integration with other blockchains e.g. canisters will be able to have Bitcoin addresses in the future

===Service Nervous System (SNS) economic framework for dapps===

The Internet Computer’s SNS feature will allow developers to create decentralized, token-based governance systems for their dapps.

This unlocks a few possibilities:
* An advanced DAO can take control of a dapp
* Dapps run under the control of a community (full decentralization)
* Dapps run as extensions of the blockchain (microeconomy with macroeconomy)
* Dapps can raise funds into the SNS; funds controlled by community

Staking and voting

2022-02-07T16:02:03Z

Jens: Jens moved page Staking and voting to Staking, voting and rewards: Earning rewards is important to investors, so the page name should reflect that

#REDIRECT [[Staking, voting and rewards]]

Staking, voting and rewards

2022-02-07T16:02:03Z

Jens: Jens moved page Staking and voting to Staking, voting and rewards: Earning rewards is important to investors, so the page name should reflect that

== Staking & Voting Rewards ==

Stakeholders can earn significant returns on their staked ICP tokens in
the form of voting rewards. The Internet Computer is a decentralized
platform whose evolution is decided by the voting power of its
stakeholders. This scheme ensures that those making decisions impacting
the future of the Internet Computer are personally vested in the
outcome. In return the Internet Computer gives out voting rewards.
Voters can vote actively, or they can use the liquid democracy on the
Internet Computer to automatically follow other voters.

== Key Concepts ==

=== Neurons ===

In order to become vested and obtain voting power, ICP tokens must first
be staked, and then locked up for a length of time greater than 6
months, to at most 8 years.

Just as tokens are held in a user's account, stake is held in a special
account called a "neuron". Each neuron has its own identifier, and
several attributes relating to its stake. These include:

* the length of time it is locked for (the "dissolve delay");
* whether it is currently dissolving toward liquidity;
* and how much reward it has accrued as a result of voting on proposals (the "maturity").

Once a neuron is locked for more than six months, it gains the ability
both to submit proposals and to vote on them. Voting in turn generates
voting rewards, based on how active a neuron is in voting on proposals.
If you vote on every open proposal, you gain the maximum reward.

A neuron can also "follow" other neurons, which causes it to
automatically vote the same as the majority of the neurons that it
follows. All new neurons by default follow neuron 27 held by the ICA, so
any newly staked neuron will generate voting rewards as soon as it is
locked for more than six months. The default following is applied to
most proposal topics, except for proposals with topic Governance, where
neuron holders have to explicitly vote to earn rewards.

=== Voting Power ===

The voting power of a locked neuron is determined by several factors:

* Principally, by its stake. 1 ICP = the power of 1 vote.
* Next, by its lock up duration, or dissolve delay. 6 months grants a 1.06x voting power bonus, and 8 years grants 2x. All other durations scale linearly between.
* Lastly, by its age, or length of time spent locked up without dissolving. 4 years grants a 1.25x bonus, multiplicative with any other bonuses. All other durations between 0 seconds and 4 years scale linearly between.

This means that the maximum voting power, of 2.5 votes per ICP staked,
is only achievable by locking up your neuron for 8 years, and leaving it
in that locked up state for 4 years. At that time you will have the most
voting power for the stake committed.

=== Maturity ===

Maturity represents the voting rewards accumulated in a neuron. Each day
the network rewards participants by allocating to every voting neuron a
portion of the total reward, based both on its voting power at the time
proposals were made, and the number of proposals it voted on.

Some look at maturity as similar to a "dividend" or "interest", but
please note that your tax authority may take a different view on the
subject. Please consult the appropriate professionals before deciding on
an interpretation of when maturity becomes income.

For those who wish to compound the gains in their neuron, the most
natural activity is to "merge maturity" at intervals, which has the
effect of minting the neuron's maturity and adding that minted amount
back into the neuron's stake. If you wish to harvest income from the
neuron, you "spawn" maturity into a reward neuron, which mints the
parent neuron's, and moves this maturity into the stake of a new neuron.
It should be noted that if you do neither, and leave those gains in the
form of maturity, it will not add to the minted total of ICP, nor
contribute to your voting power.

== Why Staking Matters ==

To some, staking is seen as an income generator, a way to perform "yield
farming" by locking up ICP and enjoying the benefits of the accrued
maturity. However, staking is not intended solely as an income vehicle.
It is a way of allowing those who invest in the Internet Computer to
decide what happens next with the platform.

When the Internet Computer first launched, all proposals required a
majority vote to pass. Gradually, however, this is changing. After a
recent update it is now possible for proposals to pass with only a
majority among 3% of the total voting power, meaning that proposals
stand a chance even if large entities abstain and the majority of the
network does not vote.

== Staking Rewards ==

Even if you stake only for the purpose of voting on proposals, voting
rewards are an important aspect of neurons. At the very least,
such returns can be compounded to increase your total voting power. So
to better understand staking and reward, it may be helpful to look at
staking from two perspectives:

=== Short-term: NNS rewards each day ===

Every day, rewards are granted by the network to each voting neuron. The
percentage of those rewards received by each neuron depend on the
following factors:

* Amount of ICP staked
* Length of dissolve delay
* "Age" of the neuron (time spent in a non-dissolving state)
* Number of eligible proposals the neuron has voted on

For example, if on a single day the NNS has generated 1000 ICP in total
rewards (see below for more on how this is computed), and there were 10
proposals submitted which only two neurons voted on, and:

* Neuron A has a voting power of 20, and voted on all 10 proposals
* Neuron B has a voting power of 80, and voted on all 10 proposals

Then the 1000 ICP would be divided between these two neurons by their
proportional voting power:

* Neuron A with voting power of 20, gets 20% of the total = 200 ICP
* Neuron B with voting power of 80, gets 80% of the total = 800 ICP

If either neuron had only voted for X% of those 10 proposals, it's
reward would be decreased to X% of its maximum eligibility, with the
remainder distributed among the other neurons.

=== Long-term: NNS rewards over years ===

As of December 2021, here is the long-term NNS rewards curve: https://dashboard.internetcomputer.org/circulation

In the first year, the NNS allocates 10% of the total supply to generate
voting rewards. Note the term "allocates" rather than "mints", because
rewards are not minted until they are spawn, merged or the neuron is
disbursed, so total supply is not automatically increased by rewards
alone. This allocation rate drops linearly until it reaches 5% by year
8. Like all parameters in the NNS, the minting rate can be changed via
NNS proposals, but this is the current rate schedule.

Because the total supply of ICP is a dynamic system with deflation and
inflation, it is impossible to predict what voting rewards will be on any
given day or year in the future. It is relatively easy to predict what
the percentage allocation rate will be months from now, but it is much
harder to predict what the total supply will be both because of
potential changes to the rate, and how often stakeholders will mint
their maturity.

=== Inflationary and Deflationary Mechanisms ===

Deflationary mechanisms for ICP:

* Minting cycles to pay for compute and storage burns ICP to create cycles
* Burning of transaction fees
* Burning of the 1 ICP deposit for failed proposals; note that this only happens at disbursement or merging of neurons, so accumulated fees can persist for a while before finally contributing to deflation.

Inflationary mechanisms for ICP:

* Node providers are paid by minting ICP
* Voting rewards are paid by minting ICP, although this minting only happens at the moment rewards are spawned, maturity is merged, or the neuron is disbursed.

=== Network Factors Affecting Annual Percentage Yield ===

When considering potential Annual Percentage Yield (APY) for ICP staked
in a voting neuron, in addition to the primary factors of the dissolve
delay, neuron age, and amount of stake, there are also network factors
that can affect potential yield. Chief among them are:

* The amount of supply allocated each year to pay rewards;
* The total voting power across all neurons, since rewards are divided equally among neurons according to their voting power;
* Inflationary and deflationary pressures: primarily, minting to pay node providers and spawn rewards, burning to fuel canister cycles, and the other factors mentioned in the previous section.

These factors can affect future returns significantly. Firstly, the
amount of supply began at 10% at genesis, but will fall to 5% after the
first eight years. Secondly, as staking becomes more common and there
are better user interfaces to do it, there will naturally be more
competition. If no one else were staking, returns would be astronomical;
but if nearly everyone is staking, returns will be lower.

Economics are always at play, however. If staking is very popular, it
means the amount of liquid supply would reduce, which would drive up
demand and hence prices. So although returns would drop significantly,
price appreciation should offset the loss in income. Conversely, if most
people dissolve their neurons to trade on the open market, price would
likely drop while returns increase. It is reasonable to assume that over
time an equilibrium will be established, where rates and prices
fluctuate in sympathy based on the macro factors driving demand for ICP
tokens.

Internet Computer wiki

2022-02-07T15:57:22Z

Jens:

==Welcome!==

This is the wiki for the Internet Computer (IC), the world's fastest and most powerful blockchain network<ref>https://medium.com/dfinity/the-internet-computers-transaction-speed-and-finality-outpace-other-l1-blockchains-8e7d25e4b2ef</ref>. The goal of the wiki is to be a general source of information for and by the IC community. Topics can range as varied as cryptography, governance of the network, user experience, tokenomics, or developer-facing tutorials.

==Introduction to the Internet Computer==
The Internet computer is the fastest and most scalable general-purpose blockchain. It was launched by DFINITY in May 2021 and works towards realising a blockchain singularity by 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 (chain-key cryptography), programming languages (Motoko) and others.

===Most common place to start===
* [https://dfinity.org/icig.pdf Internet Computer: Infographic]

===For general audience===
* [[Internet Computer overview]]
* [[Internet Computer vision]]
* [https://dfinity.org/roadmap/ Internet Computer roadmap]

===For more technical audience===
* [https://eprint.iacr.org/2022/087 "Internet Computer for Geeks" paper]

==For Dapp Users ==

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.

Examples:
* [[Introduction to the Internet Computer for dapp users]]
* [[Index of dapps on the Internet Computer]]
* [[Internet Identity for dapp users]]

See more in [[Internet Computer for dapp users]]

== For ICP Token-holders, Investors and Neuron Holders==

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.

Examples:
* [[ICP token]]
* [[Managing ICP holdings]]
* [[Staking and voting]]
* [[Governance of the Internet Computer]]
* [[Network Nervous System]]

See more in [[Internet Computer token-holders, investors and neuron holders]].

== For Smart Contract and Dapp Developers ==

The Internet Computer (IC) is a new platform for executing smart contracts. This section contains information for developers such as links to documentation, developer forums, and relevant dashboards.

Examples:
* [[Canisters (dapps/smart contracts)]]
* [[Internet Identity technical overview]]
* [https://smartcontracts.org/ Developer documentation on smartcontract.org]
* [https://forum.dfinity.org/ IC community developer forum]
* [[Index of libraries for Internet Computer development]]
* [[Best practices for a high traffic dapp launch]]
* [[Bitcoin integration]]

See more in [[Internet Computer for smart contract and dapp developers]].

== For the Curious, Researchers and Blockchain Enthusiasts ==

This section is for those interested on how the Internet Computer works under the hood. This section touches many different subject areas from cryptography, consensus protocols, virtual machines, operating systems, networking, distributed systems, etc.

Examples:
* [https://dfinity.org/howitworks/ How the Internet Computer Works]
* [https://dashboard.internetcomputer.org/ Internet Computer dashboard]
* [[Internet Computer performance]]
* [[DFINITY Foundation]]
* [[Bitcoin integration]]

See more in [[Internet Computer for researchers and blockchain enthusiasts]].

== FAQs, Tutorials, and How-tos==
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.

===FAQs===
* [[FAQ]]

===Tutorials===
Example:
* [[Managing ICP holdings]]

See more in [[Tutorials]].

=== How-tos ===
Example:
* [[How-To: Claim neurons for seed participants]]
* [[How-To: Create an NNS motion proposal]]

See more in [[How-Tos]].

==Contributing to the Wiki==

=== How to contribute ===
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]].

==References==

Internet Computer overview

2022-02-07T14:40:18Z

Jens:

The Internet Computer is a “general-purpose” blockchain that provides a public platform for hosting tokens and decentralized applications (dapps). It acts as a complete technology stack, such that systems and services can be built that run entirely from the blockchain.

==What is the Internet Computer?==

Conceptually, the Internet Computer is an extension of the existing internet that enables a global network of computers to provide the computing power for running application software.

In much the same way that the adoption of the transmission control protocol (TCP) and Internet protocol (IP) provided ''rules'' for transferring data between endpoints that helped to establish the “network of networks” that we know as the internet of today, the Internet Computer relies on a ''decentralization protocol'' called the '''Internet Computer protocol''' to define the software components that enable a global network of computers to combine their resources to read, replicate, modify, and return application state.

The keys to Internet Computer infrastructure are:

* A '''secure protocol''' that enables general-purpose computations to run transparently directly on the internet.
* A '''network''' that runs the protocol to provide computing capacity—for example, the hardware, CPU, and memory required to run programs—through '''independently-operated data centers.'''
* A '''globally-accessible and scalable platform''' for running software applications.

==Why build the Internet Computer?==

For end-users, accessing Internet Computer-based services is largely transparent, the experience of interacting with a decentralized application is the same as it is on a public or private cloud.

For the people creating and managing those Internet Computer-based services, however, the Internet Computer eliminates many of the costs, risks, and complexities associated with developing and deploying modern applications and microservices. In addition, its secure protocol guarantees reliable message delivery, transparent accountability, and resilience without relying on firewalls, backup facilities, load balancing services, or failover orchestration.

In some ways, building the Internet Computer is about restoring the Internet to its open, innovative, and creative roots. To focus on a few specific examples, the Internet Computer does the following:

* Supports interoperability, shared functions, permanent APIs, and ownerless applications which reduces platform risk and encourages innovation and collaboration.
* Persists data automatically in memory which eliminates the need for database servers and storage management, improves computational efficiency, and simplifies software development.
* Simplifies the technology stack that IT organizations need to integrate and manage which improves operational efficiency.

==Canisters (dapps/smart contracts)==
The Internet Computer hosts powerful smart contracts called canisters. Canisters are tamperproof, autonomous, hosted on-chain, and can be run concurrently and interact with each other. Canisters can service HTTP requests created by end-users, which allows them to directly serve interactive web experiences. This means that blockchain dapps, systems and services can be created without incorporating websites running on corporate cloud hosting services and private servers into their architecture, which provides true end-to-end Web 3.0 decentralization, censorship resistance, and superior security.

More information about canisters can be found at:
* [[Canisters (dapps/smart contracts)|The canister wiki page]].
* This [https://medium.com/dfinity/software-canisters-an-evolution-of-smart-contracts-internet-computer-f1f92f1bfffb Medium post] about canisters.
* The [https://smartcontracts.org/docs/developers-guide/concepts/canisters-code.html developer documentation] for canisters.

==Dapps==
The Internet Computer was designed to improve the user experience of interacting with smart contracts and dapps running on a blockchain. Dapps on the IC are able to serve web content, allowing users to interact with the dapps through their browser. Dapps themselves are run by canisters (dapps/smart contracts) on the IC with the robustness and security guarantees it affords.
Developers create dapps in programming languages such as Rust or Motoko, compile them to WebAssembly byte code, and deploy the WebAssembly modules into canisters on the Internet Computer. A canister comprises a WebAssembly module and persisted memory.
For more information or to start using dapps on the IC see:
* [[Index of dapps on the Internet Computer ecosystem|Index of dapps on the IC]]
* This [https://medium.com/dfinity/internet-computer-pioneers-early-adopters-describe-launching-dapps-on-the-blockchain-e979281f19b8 Medium post] where early adopters describe their experience of launching dapps on the IC.

==Internet Identity==

Internet Identity is an anonymous blockchain authentication framework supported by the Internet Computer. Users can create identity "anchors" to which they assign compatible cryptographically enabled devices, such as the fingerprint sensor on a laptop, the face ID system on a phone, or a portable HSM, such as a YubiKey or Ledger wallet. Thereafter, they can signup and authenticate to any dapp running on the Internet Computer using any of the devices they have assigned to their anchor. This provides a high level of convenience, allowing users to authenticate to dapps they are interested in with a very low level of friction, while benefiting from the highest level of cryptographic security, but without the need to directly manage or handle cryptographic key material themselves, which prevents mistakes and the theft of their key material. The system is anonymizing towards dapps, and whenever an anchor is used to interact with a dapp, the dapp sees a specially generated pseudonym, which prevents users being tracked across the various dapps they use. A user can create as many identity anchors as they wish.

Unlike most authentication methods, Internet Identity does not require users to set and manage passwords or provide any personal identifying information to dapps or to Internet Identity.

To read more about Internet Identity, or to generate an anchor, see:
* The [https://identity.ic0.app/ Internet Identity dapp].
* [[Internet_Identity_for_dapp_users|Internet Identity for dapp users]].
* [[Internet_Identity_technical_overview|Internet Identity technical overview]].
* The Internet Identity [https://smartcontracts.org/docs/ic-identity-guide/what-is-ic-identity.html developer documentation].

==NNS==
The Internet Computer is governed and managed in realtime by a governance system, which is integrated into its blockchain protocols, called the Network Nervous System (or NNS). Anybody can submit proposals to the NNS, and they are either rejected, or adopted, and then automatically executed. Proposals can add additional nodes to run the Internet Computer, upgrade the Internet Computer protocol by updating the replica software running on node machines, tweak economic parameters, perform general configurations, and many other things. This provides an advantage over traditional blockchains, which must be upgraded manually by those operating nodes via a "hard fork". The decentralized Internet Computer network is thus designed to be self-directed.

==Tokens==
The Internet Computer uses a utility token ICP. Holders can stake ICP, allowing them to participate in the governance of the Internet Computer and earn voting rewards. ICP can also be converted into cycles and used to power computation, communication and storage costs of canisters. The blockchain incorporates a "reverse gas" model, in which smart contracts pay for their own computation, and must be pre-charged with cycles to run in much the same way an electric car must be pre-charged with electricity to drive. This ensures that end-users of dapps, systems and services can interact with them over the web without needing tokens to pay for the computations that they initiate. The Internet Computer maintains a floating conversion rate so that 1 Trillion cycles costs approximately 1 IMF SDR in ICP.

==Internal Building Blocks==
Internally, the Internet Computer's network is comprised from individual subnet blockchains. New subnet blockchains (often simply called "subnets") are formed by combining node machines to increase its capacity for hosting smart contract data and computation. Its protocols leverage chain key cryptography to have subnets function as a single blockchain, such that they are completely transparent to smart contract code, and every smart contract on the blockchain can directly call any other smart contract. Any number of subnets can be added, with each additional subnet linearly increasing the network's overall capacity.

The Internet Computer runs on a sovereign network of special node machines that are dedicated to the task. They are run by independent node providers (node owner/operators), from independent data centers, in different geographies and jurisdictions around the world, without any need for corporate cloud services. New subnets are formed by combining node machines that are calculated to be independent according to a decentralization hierarchy comprising node provider, data center, geography and jurisdiction, which makes it possible to produce the desired security and resilience properties with both higher certainty and lower levels of replication, thus driving efficiency.

For a more in depth view of the technical building blocks [https://dfinity.org/whitepaper.pdf The Internet Computer for Geeks whitepaper] gives a comprehensive coverage.

The Internet Computer was developed by the DFINITY Foundation, which now continues as its lead contributor. The network underwent Genesis on 10th May 2021.

==See Also==
* [https://www.youtube.com/watch?v=XgsOKP224Zw Overview of the Internet Computer] video on YouTube.
* The [https://dfinity.org/howitworks/ How it Works] page where you can get an overview of different building blocks and features of the internet computer.

Internet Computer wiki

2022-02-07T13:57:58Z

Jens:

==Welcome!==

This is the wiki for the Internet Computer (IC), the world's fastest and most powerful blockchain network<ref>https://medium.com/dfinity/the-internet-computers-transaction-speed-and-finality-outpace-other-l1-blockchains-8e7d25e4b2ef</ref>. The goal of the wiki is to be a general source of information for and by the IC community. Topics can range as varied as cryptography, governance of the network, user experience, tokenomics, or developer-facing tutorials.

== Introduction to the Internet Computer==
The Internet computer is the fastest and most scalable general-purpose blockchain. It was launched by DFINITY in May 2021 and works towards realising a blockchain singularity by 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 (chain-key cryptography), programming languages (Motoko) and others.

===Most common place to start===
* [https://dfinity.org/icig.pdf Internet Computer: Infographic]

===For general audience===
* [[Internet Computer overview]]
* [[Internet Computer vision]]
* [https://dfinity.org/roadmap/ Internet Computer roadmap]

===For more technical audience===
* [https://eprint.iacr.org/2022/087 "Internet Computer for Geeks" paper]

== For dapp users ==

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.

Examples:
* [[Introduction to the Internet Computer for dapp users]]
* [[Index of dapps on the Internet Computer]]
* [[Internet Identity for dapp users]]

See more in [[Internet Computer for dapp users]]

== For ICP token-holders, investors and neuron holders ==

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, and options for managing one's ICP.

Examples:
* [[ICP token]]
* [[Managing ICP holdings]]
* [[Staking and voting]]
* [[Governance of the Internet Computer]]
* [[Network Nervous System]]

See more in [[Internet Computer token-holders, investors and neuron holders]].

== For smart contract and dapp developers ==

The Internet Computer (IC) is a new platform for executing smart contracts. This section contains information for developers such as links to documentation, developer forums, and relevant dashboards.

Examples:
* [[Canisters (dapps/smart contracts)]]
* [[Internet Identity technical overview]]
* [https://smartcontracts.org/ Developer documentation on smartcontract.org]
* [https://forum.dfinity.org/ IC community developer forum]
* [[Index of libraries for Internet Computer development]]
* [[Best practices for a high traffic dapp launch]]
* [[Bitcoin integration]]

See more in [[Internet Computer for smart contract and dapp developers]].

== For the curious, researchers and blockchain enthusiasts ==

This section is for those interested on how the Internet Computer works under the hood. This section touches many different subject areas from cryptography, consensus protocols, virtual machines, operating systems, networking, distributed systems, etc.

Examples:
* [https://dfinity.org/howitworks/ How the Internet Computer Works]
* [https://dashboard.internetcomputer.org/ Internet Computer dashboard]
* [[Internet Computer performance]]
* [[DFINITY Foundation]]
* [[Bitcoin integration]]

See more in [[Internet Computer for researchers and blockchain enthusiasts]].

== FAQs, Tutorials, and How To's==
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.

===FAQs===
* [[FAQ]]

=== Tutorials ===
Example:
* [[Managing ICP holdings]]

See more in [[Tutorials]].

=== How-Tos ===
Example:
* [[How-To: Claim neurons for seed participants]]
* [[How-To: Create an NNS motion proposal]]

See more in [[How-Tos]].

== Contributing to the wiki ==

=== How to Contribute ===
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]].

==References==

Index of dapps on the Internet Computer ecosystem

2022-02-06T20:26:14Z

Jens:

= Index of dapps on the Internet Computer =

==List of IC ecosystem aggregators==
* [https://n7ib3-4qaaa-aaaai-qagnq-cai.raw.ic0.app/?locale=en#/ ICApps]
* [https://dfinity.org/showcase/ DFINITY Showcase]
* [https://zire.github.io/awesome-IC/ The Awesome IC Repository]

==List of dapps ==

This Wiki Page is a mirror of [https://zire.github.io/awesome-IC/ The Awesome IC Repository]

[[File:Logo.jpg|thumb]]

* Essential (<code>3</code>)
* Wallet (<code>5</code>)
* Tools (<code>26</code>)
* Motoko (<code>4</code>)
* DeFi (<code>13</code>)
* NFT (<code>42</code>)
* Social (<code>11</code>)
* Games (<code>10</code>)
* Metaverse (<code>3</code>)
* Productivity (<code>12</code>)
* Communities (<code>3</code>)
* Enterprise (<code>9</code>)

===Criteria===

This article tries to capture key info for each project, including its tag line, IC URL, Twitter, Discord, Telegram, Github repo and the team behind. For those projects with Twitter handles, they can also be found at:

<blockquote>[https://twitter.com/i/lists/1443165233510436868 IC Projects - All@Twitter]
</blockquote>
This list includes all the projects from [https://dfinity.org/showcase/ DFINITY Showcase] but is a lot more than that. It tries to index all the known IC dApps. Some of those projects have received [https://dfinity.org/grants/ developer grants from the DFINITY Foundation]. Some of them may not have been deployed on IC yet - though the expectation is that they are working toward that. It does not include IC communities, media or development teams per se (though they'll be included under the "project" section). All info is obtained from public channels.

The projects indexed on this list cover a wide spectrum on quality, maturity and tech deployment. Some of them have already received venture funding from established crypto funds; some of them are taking full advantage of Internet Computer (IC)'s unique technical strengths; some of them are using IC as a backend infrastructure in liew of AWS/GCP, and some of them are porting an existing Polkadot/Filecoin application to IC. The inclusion of a project (or lack of) does not speak to the quality of it. That judgment is left to the community and all IC advocates. This is just a directory that helps everyone do scavenger hunt on IC.

This is merely an index/directory, and does not represent official endorsement in any fashion. Nothing from this site shall be treated as financial advice. Please do your own research if you need to use any services listed below.

=== Essential (3) ===

'''ICA Network Status'''

* What: Real-time dashboard of key metrics on the Internet Computer
* Where: https://dashboard.internetcomputer.org/
* Who: [https://internetcomputer.org/ Internet Computer Association]

'''Internet Identity'''

* What: Internet Identity guarantees that your data isn’t visible, tracked, or mined. The blockchain authentication system enables users to sign in to dapps on the Internet Computer and sites across the web anonymously and securely.
* Where: https://identity.ic0.app/
* Who: [https://dfinity.org DFINITY Foundation]

'''NNS Frontend Dapp'''

* What: The NNS frontend dapp allows anyone to interact with the Internet Computer's Network Nervous System with a user-friendly UI. Served completely end-to-end through blockchain, this dapp allows you to manage ICP, stake neurons, participate in voting, and earn rewards.
* Where: https://nns.ic0.app/
* Who: [https://dfinity.org DFINITY Foundation]

=== Wallet (5) ===

'''ICWallet'''

* What: Your gateway to Dfinity ecosystem
* Where: https://icwallet.org/
* Twitter: https://twitter.com/icwallet
* Who: https://icwallet.gitbook.io/icwallet/team
* Discord: https://discord.com/invite/DqCeHU8rem

'''DFWallet'''

* What: a decentralized smart wallet on Internet Computer
* Where: https://dfwallet.ooo/
* Twitter: https://twitter.com/DFWallet
* Telegram: https://t.me/df_wallet

'''Plug'''

* What: A browser extension that allows you to access your ICP, Cycles and other tokens
* Where: https://plugwallet.ooo/
* Who: [https://fleek.co/ fleek]
* Twitter: https://twitter.com/plug_wallet
* Discord: https://discord.gg/yVEcEzmrgm

'''Stoic Wallet'''

* What: It allows anyone to create a digital wallet, authenticating users through a variety of methods.
* Where: https://www.stoicwallet.com/
* Who: [https://igpeu-waaaa-aaaad-qaava-cai.raw.ic0.app/ Toniq Labs]
* Github: https://github.com/Toniq-Labs/stoic-wallet

'''Earth Wallet'''

* What: The open-source wallet allows users to participate in DeFi, Governance, and Treasury (DAO) protocols with negligible fees and faster transaction settlement than legacy wallets.
* Where: https://www.earthwallet.io/
* Twitter: https://twitter.com/earthwallet
* Discord: https://discord.gg/B8G75XZ92K
* Telegram: https://t.me/earthwallet
* Github: https://github.com/earth-association

=== Tools (26) ===

'''AstroX'''

* What: AstroX is a blockchain development group focused on building tools for the Web3.0 ecosystem. AstroX has developed a Dart agent and other tools to help support mobile application development on the Internet Computer blockchain.
* Where: https://astrox.medium.com/
* Who: FireStack Labs
* Twitter: https://twitter.com/Astrox_Network
* Discord: https://discord.com/invite/Ky78nq4Nag
* Github: https://github.com/AstroxNetwork

'''Axon'''

* What: A community-built neuron management solution for the Internet Computer. Multiple users can own an Axon that manages multiple neurons within the Network Nervous System, as well as delegate votes to other neurons to vote on proposals. Axon is a multi-user, multi-neuron management canister.
* Where: https://axon.ooo/
* Twitter: https://twitter.com/axon_ooo
* Github: https://github.com/FloorLamp/axon

'''B9 Labs'''

* What: Better developer onboarding and documentation on IC
* Where: https://b9lab.com/
* Twitter: https://twitter.com/b9lab
* DFINITY Grant: received in August 2021

'''Canlista'''

* What: The Internet Computer community canister registry. Find, publish and extend applications and services built on the Internet Computer. Log in with Internet Identity.
* Where: https://k7gat-daaaa-aaaae-qaahq-cai.ic0.app/
* Twitter: https://twitter.com/canlista_io

'''Canistore'''

* What: Next-gen #SocialStore powered by @DFINITY, empowered by community
* Where: https://canistore.io/
* Twitter: https://twitter.com/canistore
* Telegram: https://t.me/canistore
* Medium: [https://medium.com/@canistore](https://medium.com/@canistore)

'''CAP'''

* What: an open internet service providing transaction history & asset provenance for NFT’s & Tokens on the Internet Computer
* Where: https://cap.ooo/
* Twitter: https://twitter.com/cap_ois
* Discord: https://discord.gg/psychedelic

'''ChainIDE'''

* What: a cloud-based multi-chain IDE
* Where: https://chainide.com/
* Who: [https://whitematrix.io/ White Matrix] and https://twitter.com/MatrixDapp
* Twitter: https://twitter.com/ChainIde
* Medium: https://t.co/ODqRqGNUoG?amp=1
* Github: https://github.com/WhiteMatrixTech
* DFINITY Grant: received in May 2021

'''Cover'''

* What: an open internet service that can be used by developers to verify and prove that a canister's code matches the open source code. Reducing the risk of malicious apps & increasing transparency and trust.
* Where: https://covercode.ooo/
* Twitter: https://twitter.com/cover_ois
* Discord: https://discord.gg/yVEcEzmrgm
* Github: https://github.com/psychedelic/cover

'''Create IC'''

* What: Modern frontend templates for the Internet Computer with everything working out of the box. Powered by ViteJS
* Where: https://create-ic.app/
* Who: [https://twitter.com/miamaruq Mio Q]
* Github: https://github.com/MioQuispe/create-ic-app/

'''DAB'''

* What: DAB provides seamless access to #InternetComputer data that many apps/UI's need to surface. Such as lists of NFT's, tokens, canister/Dapp metadata, and more.
* Where: https://dab.ooo/
* Twitter: https://twitter.com/dab_ooo
* Doc: https://docs.dab.ooo/

'''DFINITY Explorer'''

* What: DFINITY Explorer, a project started in 2018, is an open-source, community-built dashboard and explorer for the Internet Computer, providing live information and statistics about the network, governance, and the ICP utility token, including account and transaction information.
* Where: https://www.dfinityexplorer.org/#/
* Who: [https://github.com/dylancm4 Dylan Miller]
* Twitter: https://twitter.com/dfinityexplorer
* Github: https://github.com/dfinityexplorer/dfinityexplorer-dashboard

'''DFINITY Java Agent'''

* What: Dfinity Java Agent is a set of native Java libriaries to connect remotely to the Internet Computer applications
* Github: https://github.com/rdobrik/dfinity-agent
* Who: [https://github.com/rdobrik Roman]

'''DFT - Dfinity Fungible Token Standard'''

* What: Token standard will help Dfinity ecological developers adopt the same standard and promote the prosperity of the Dfinity ecosystem
* Where: https://dft.delandlabs.com/
* Who: [https://twitter.com/DelandLabs Deland Labs]

'''Dfinity Tutorials'''

* What: Chinese tutorials that teach you how to build on IC
* Where: https://icplabs.gitbook.io/dfinitytutorials/
* Who: [https://twitter.com/ICP_Labs ICP Labs]

'''Dstar'''

* What: a marketplace that facilitates listing, buying and selling of your Internet Identity ("II") accounts
* Where:
** https://ii.dstar.app
** https://yunqk-aqaaa-aaaai-qawva-cai.ic0.app/
* Github: https://github.com/ic-dstar/

'''EXT Token Tool'''

* What: EXT is a token standard that we built on the IC, modelled after Ethereum's ERC1155 standard
* Where: https://k6exx-uqaaa-aaaah-qadba-cai.raw.ic0.app/
* Who:[https://twitter.com/toniqlabs Toniq Labs]

'''Fleek'''

* What: Fleek brings decentralized web-hosting to the Internet Computer. With thousands of webpages deployed, Fleek enables anyone to deploy their content on Web3.0
* Where: https://fleek.ooo/
* Twitter: https://twitter.com/fleek_ois
* Discord: https://discord.gg/yVEcEzmrgm
* Github: https://github.com/FleekHQ

'''ICLight.house'''

* What: A standard interface for Dfinity tokens. The standard complies with ERC20 interface specification, and has some improvements to match IC network features
* Where: https://iclight.house/login
* Twitter: https://twitter.com/ICLighthouse
* Github: https://github.com/iclighthouse/DRC_standards

'''ICME'''

* What: ICME is a no-code tool that makes it easy for anyone to build and deploy beautiful websites on the Internet Computer. Launch your blog or business's website on the Internet Computer today.
* Where: https://sygsn-caaaa-aaaaf-qaahq-cai.raw.ic0.app/
* Twitter: https://twitter.com/icme_app

'''ICP Neuron Calculator'''

* What: The Network Nervous System Calculator is a calculator that allows anyone to edit variables and estimate voting rewards based on number of proposals voted on, length of stake, accumulated maturity, and more.
* Where: https://networknervoussystem.com/
* Twitter: https://twitter.com/NNSystem
* Newsletter: https://allthingsinternetcomputer.substack.com/

'''ICP Scan'''

* What: A scanner and dashboard tool for IC ecosystem to discover ICP projects and track key statistics
* Where: https://sznps-4aaaa-aaaah-qab2a-cai.ic0.app/project
* Who: [https://twitter.com/NnsDaos NnsDAO]

'''IC Rocks'''

* What: IC.Rocks is a complete "block explorer" for the Internet Computer – built by the community. Tracking everything from transactions, to network upgrades, to cycles, IC.Rocks enables anyone to explore the inner-workings of the Internet Computer.
* Where: https://ic.rocks/
* Who: [https://twitter.com/floatfloatboat Norton Wang]
* Twitter: https://twitter.com/ic_rocks

'''Pocket 4D'''

* What: A framework container runs Mini-Apps or Mini-Programs, using enhanced Canister of cross-platform.
* Who: [https://twitter.com/ghostcorn Michael So] and the team
* Github: https://github.com/Pocket4D/Pocket4D-Wiki

'''Sudograph'''

* What: Sudograph is a GraphQL database for the Internet Computer. Its goal is to become the simplest way to develop applications for the IC by providing flexibility and out-of-the-box data management.
* Where: https://i67uk-hiaaa-aaaae-qaaka-cai.raw.ic0.app/
* Twitter: https://twitter.com/lastmjs
* Github: https://github.com/sudograph/sudograph

'''Usergeek'''

* What: the first decentralised product analytics tool built on the DFINITY Internet Computer
* Where: https://fbbjb-oyaaa-aaaah-qaojq-cai.raw.ic0.app/#/
* Twitter: https://twitter.com/theUSERGEEK
* Discord: https://discord.gg/CvTpv2TeKs

'''The Wall'''

* What: The Wall is a dapp built on the Internet Computer blockchain, which blends Ethereum's MetaMask authentication with the Internet Computer's native Internet Identity blockchain authentication system. This first example of ETH x ICP allows users to leave any message on the wall for all eternity.
* Where: https://rivyl-6aaaa-aaaaf-qaapq-cai.raw.ic0.app/
* Github: https://github.com/kristoferlund/ic-wall
* Who: [https://twitter.com/kristoferlund Kristofer Lund]

=== Motoko (4) ===

'''Block.'''

* What: A virtual editor for Motoko

'''Motoko Playground'''

* What: The Motoko Playground is an IDE for developers to learn Motoko – the native language for the Internet Computer blockchain. Deploy canister smart contracts for free, directly within a browser, without needing to download an SDK or set up a wallet.
* Where: https://m7sm4-2iaaa-aaaab-qabra-cai.raw.ic0.app/
* Who: [https://forum.dfinity.org/u/chenyan/ Chen Yan]

'''Motoko School'''

* What: Motoko School is the first public school for the Metaverse, only on the Internet Computer
* Where: [https://www.youtube.com/channel/UCS2Y9oRMpBfVqAnChFoXepg Motoko School on Youtube]
* Twitter: https://twitter.com/MotokoSchool

'''Motoko Library'''

* What: An awesome list of Motoko code and resources curated by the community.
* Where: https://github.com/motoko-unofficial/awesome-motoko

=== DeFi (13) ===

'''Bauction'''

* What: Bauction will empower the online auction and tender for retail as well as enterprises customer is decentralized and transparent manner. By leveraging technology stack of ICP, we want it to be self governed self driven auction platform.
* Where: https://bauction.org/
* Twitter: https://twitter.com/bauctionorg
* DFINITY Grant: received in July 2021

'''CetoSwap'''

* What: CetoSwap ∞ is a fungible and non-fungible asset management platform base on #Dfinity
* Where: https://ijnlb-jiaaa-aaaah-qaesa-cai.ic0.app/
* Twitter: https://twitter.com/CetoSwap
* Medium: https://cetoswap.medium.com/

'''Dank'''

* What: Dank is the first Decentralized Bank built on the Internet Computer, developed by Fleek. Through a collection of Open Internet Services for users and developers, Dank makes cycles management seamless.
* Where: https://dank.ooo/
* Twitter: https://twitter.com/dank_ois
* Discord: https://discord.gg/yVEcEzmrgm

'''EnsoFinance'''

* What: Discover and create open DeFi metastrategies
* Where: https://www.enso.finance/
* Twitter: https://twitter.com/EnsoFinance
* Discord: https://discord.gg/y48Yp6Y4QX

'''iBridge'''

* What: #DeFi Protocol for #Crosschain Assets Based on #Dfinity
* Where: https://www.ibridge.pro/
* Twitter: https://twitter.com/iBridge_Labs
* Github: https://github.com/iBridge-up
* Medium: [https://medium.com/@ibridge_labs](https://medium.com/@ibridge_labs)

'''ICPSwap'''

* What: ICPSwap is decentralized exchange (DEX) built completely end-to-end on-chain. By building the ability for anyone to swap tokens through ICPSwap leveraging the Internet Computer blockchain as the high-speed, scalable, low-cost infrastructure makes ICPSwap a first-to-market in the growing Internet Computer DeFi ecosystem.
* Where:
** https://3pbcj-viaaa-aaaah-qaajq-cai.raw.ic0.app/
** https://twitter.com/ICPSwap
* Twitter: https://twitter.com/ICPSwap
* Telegram: https://t.me/ICPSwap_Official
* Medium: https://icpswap.medium.com/
* DSCVR: https://h5aet-waaaa-aaaab-qaamq-cai.raw.ic0.app/p/icpswap
* Github:https://iloveics.gitbook.io/icpswap/

'''InfinitySwap'''

* What: A platform to create, stake and swap Dfinity Tokens
* Where: https://infinityswap.one/
* Twitter: https://twitter.com/infinity_swap
* Telegram: https://t.me/infinityswapofficial

'''Liquid ICP'''

* What: Liquid ICP is world's first s-Bridge where bridged and staked assets remain liquid. Fractional reserve is governed by Liquid ICP community and ensures immediate withdrawal of ICP coins at any given time.
* Where: https://www.icp-20.com/
* Twitter: https://twitter.com/LiquidICP
* Discord: https://discord.com/invite/3F8CYyPpHq
* Github: https://docs.icp-20.com/

'''RFL'''

* What: Random Fair Lottery on IC
* Twitter: https://twitter.com/RFL_app

'''Sailfish'''

* What: The gateway to open financial services on the Internet Computer
* Where: https://sailfish.app/
* Twitter: https://twitter.com/Sailfishapp
* Discord: https://discord.com/invite/7Wbqucc

'''Sonic'''

* What: Swap tokens, earn fees as a liquidity provider, & build on the Internet Computer’s AMM
* Where: https://sonic.ooo/
* Twitter: https://twitter.com/sonic_ooo
* Discord: https://discord.com/invite/EkmnRd99h6

'''SupraOracles'''

* What: Bridging real-world data to automate, simplify, and secure the #smartcontracts of financial markets
* Where: https://www.supraoracles.com/
* Twitter: https://twitter.com/SupraOracles
* Telegram: https://t.me/supraoracles

'''Uniswap Front End on the IC'''

* What: Uniswap front end hosted on the Internet Computer through Fleek. Showing how traditional DeFi solutions can now be hosted completely on-chain by using the Internet Computer blockchain. Another use case of completely decentralizing a service which currently has a centralized front end.
* Where: https://lqku6-wqaaa-aaaad-qalmq-cai.ic.fleek.co/#/swap
* Who: [https://fleek.co/ fleek]

=== NFT (42) ===

'''Crowd Created Canvas (CCC)'''*

* What: CCC is the first-ever collectible, collaborative pixel artwork created by the #Dfinity community, sharing bonus pool and getting NFT.
* Where: https://sdnoa-fiaaa-aaaah-aaubq-cai.ic0.app/
* Twitter: https://twitter.com/CCCProtocol

'''Cronic NFTs'''

* What: Cronics play-to-earn ecosystem on the $ICP blockchain. Trade Cronic Critters and accessories on @EntrepotApp
* Where: https://cronic.toniqlabs.com/
* Who: [https://igpeu-waaaa-aaaad-qaava-cai.raw.ic0.app/ Toniq Labs]
* Twitter: https://twitter.com/CronicsP2E
* Telegram: https://t.me/cronic_talk

'''cubic'''

* What: Cubic is a generative art project. Data such as ownership history and transaction history are used in different ways to generate unique canvases in a variety of styles.
* Where: https://cubic.place/
* Github: https://github.com/FloorLamp/cubic
* Telegram: https://t.me/cubicplace

'''CYMAN'''

* What: 10,000 Randomly generated cybernetic humanoid's from 550,000,000 BCE built on the Internet Computer
* Where: https://www.cyman.live/
* Twitter: https://twitter.com/cyman_live
* Discord: https://discord.com/invite/cyman

'''IC Ape Ventures'''

* What: 10,000 Unique Apes are getting ready to take their first steps in to the #ICP ecosystem
* Where: https://icapeventures.com/
* Twitter: https://twitter.com/ICApeVentures
* Discord: https://discord.com/invite/icapeventures

'''ICKitties'''

* What: 10,000 8-bit kitties on IC
* Twitter: https://twitter.com/ICKitties
* Discord: https://discord.com/invite/r2c4TTr4un

'''ICPets | Infinity Pets'''

* What: 11,111 of Infinity Pets 🐧 | Community Gain Focused NFT collection living on #ICP Blockchain
* Where: https://icpets.io/
* Twitter: https://twitter.com/icpets_nft
* Discord: https://discord.com/invite/nD9HqPQ7

'''IC Photographers'''

* What: At IC photographers, the aim is to bring both creator and collector together. We endeavour to show talented artists to the collectors of photography NFT’s.
* Where: https://www.icphotographers.com/
* Who: [https://twitter.com/olisav Oli]

'''ICPics'''

* What: An NFT collection of 1,000 pieces of trival artwork on IC
* Twitter: https://twitter.com/ethnICPic
* Discord: https://discord.com/invite/gauQWrV2b4

'''ICPrime8s'''

* What: 5 releases of Prime8 focused, randomly generated NFTs on the Internet Computer
* Twitter: https://twitter.com/ICPrime8s

'''ICPumpkin NFT'''

* What: NFT pumpkins for Halloween on IC
* Twitter: https://twitter.com/ICPumpkin

'''Dfinity Bulls NFT'''

* What: 8,888 Awesome Badass Bulls will ever be minted! Exclusively on ICP!
* Twitter: https://twitter.com/DBulls_NFT
* Discord: https://discord.com/invite/GBSNhYeGxh

'''DfinityNFT'''

* What: The Cryptogarden of The Internet Computer. NFT cross-chain aggregator of The Internet Computer.
* Where: http://dfinitynft.com/
* Twitter: https://twitter.com/DfinityNFT
* DFINITY Grant: received in July 2021

'''Exponent'''

* What: The Exponent Platform is a complete Layer1 DeFi solution running on DFINITY's Internet Computer. Our platform is made from a number of our token standard, SDK and protocols.
* Who: [https://igpeu-waaaa-aaaad-qaava-cai.raw.ic0.app/ Toniq Labs]
* Discord: https://t.co/9iDZBX35mg?amp=1
* Github: https://github.com/Toniq-Labs/exponent

'''Entrepot NFT Marketplace'''

* What: Entrepot is a decentralized NFT marketplace developed by ToniqLabs, the creators behind Rise of the Magni, Stoic Wallet, Cronic NFTs, and Exponent. Entrepot (through Exponent) provides users with tools and on-chain services to design, deploy, and manage NFTs and traditional tokens.
* Where: https://entrepot.app/
* Who: [https://igpeu-waaaa-aaaad-qaava-cai.raw.ic0.app/ Toniq Labs]
* Twitter: https://twitter.com/EntrepotApp
* Discord: https://discord.gg/toniqlabs
* Github: https://github.com/Toniq-Labs/exponent

'''Fantosaurs'''

* What: Raptors from Isla NOOblar, currently on Eth, but hosted on IC
* Where:
** https://fantosaur.io/
** https://j5h4x-gyaaa-aaaad-qayjq-cai.raw.ic0.app/
* Twitter: https://twitter.com/fantosaurs
* Discord: https://discord.com/invite/e7bec4rm

'''Fungible Token Standard by Deland'''

* What: Fungible token standard by Deland
* Where: https://github.com/Deland-Labs/dfinity-fungible-token-standard
* Who: [https://deland.one/ Deland Labs]
* Medium: [https://medium.com/@DelandLabs](https://medium.com/@DelandLabs)
* Discord: https://discord.gg/CdzzUaFUXq
* DFINITY Grant: received in August, 2021

'''Haunted Hamsters'''

* What: NFT set of 6,666 haunted hamsters, spooking on DFINITY ICP
* Where: http://www.hauntedhamsters.io/
* Twitter: https://twitter.com/HauntedHamsters
* Discord: https://discord.com/invite/DtSF7SGK

'''IC3D'''

* What: Cool 3D NFTs on the Internet Computer - IC 3D NFT
* Twitter: https://twitter.com/IC3DNFT
* Discord: https://discord.com/invite/ic3dnft

'''IC Canvas'''

* What: a collaborative NFT
* Where: https://rdbii-uiaaa-aaaab-qadva-cai.raw.ic0.app/
* Who: [https://twitter.com/kylpeacock Kyle Peacock]

'''IC Cards'''

* What: IC Cards is an NFT-based game on the IC Protocol. Gather, craft, level, and prepare yourself for a world full of monsters and villains.
* Where:
** [[ic.cards|ic.cards]]
** https://tbhsl-lqaaa-aaaaj-qagzq-cai.ic0.app/
* Twitter: https://twitter.com/ic_cards

'''ICelebrity'''

* What: 100 Uniquely Minted handmade artistic representation of the people we know and love!
* Twitter: https://twitter.com/ICelebrityNFT
* Discord: [[discord.gg/AZFq4QMYBx|discord.gg/AZFq4QMYBx]]

'''IC Gallery'''

* What: Home of the Metaverse. 9999 unique 3D Moonwalker NFTs
* Where: https://gan2q-ciaaa-aaaai-aanoq-cai.raw.ic0.app/
* Who: [https://twitter.com/CipherProxyLLC Cipher Proxy]
* Twitter: https://twitter.com/ic_gallery
* Discord: https://discord.com/invite/6VWZNzskPA

'''ICircle NFT'''

* What: 8888 Generative Art NFTs Launch Soon in #InternetComputer | Math + Art = Beautiful
* Twitter: https://twitter.com/icircle_nft
* Discord: https://discord.io/ICircle_NFT

'''ICP Art'''

* What: Exclusive Hand-Crafted Art Collections
* Where: https://linktr.ee/ICPArt
* Twitter: https://twitter.com/ICP_Art

'''ICP Squad'''

* What: First Engage To Earn #NFTs Game. Powered by @dfinity
* Where: https://upf6d-saaaa-aaaah-aauwa-cai.ic0.app/#/
* Twitter: https://twitter.com/ICPSquadNFT
* Discord: https://discord.com/invite/icpsquad

'''ICPunks'''

* What: 10,000 randomly generated, unique collectible clowns with proof of ownership stored on the Internet Computer blockchain. Created as a reference to a meme comparing the Internet Computer token (ICP) with the Insane Clown Posse - an American hip hop duo founded in 1989.
* Where: https://icpunks.com/
* Twitter: https://twitter.com/ICPunks
* Who: [https://github.com/stopak stopak] and [https://github.com/przchojecki Przemyslaw Chojecki]
* Github: https://github.com/stopak/ICPunks/tree/dev
* Discord: https://discord.gg/m8QWD7m62h

'''ICPuppies'''

* What: ICPuppies is an NFT project hosted completely on the Internet Computer. In October, 10,000 randomly generated NFTs will be available for members of the Internet Computer community to claim through the Entrepot.app marketplace. A portion of the proceeds will be donated to organizations that support puppies.
* Where: https://icpuppies.io/
* Twitter: https://twitter.com/ICPuppies
* Discord: http://discord.gg/A3rmDSjBaJ

'''ICSnakes'''

* What: A collection of 10,000 randomly generated NFTs on #ICP blockchain hunting for food.
* Where: https://xn--4n8h7h.ws/
* Twitter: https://twitter.com/ICSnakes
* Discord: https://discord.com/invite/H9YUpwVrkQ

'''IC Turtles'''

* What: Customizable and breedable NFTS, powered by GameFi and P2E, dropping with accessories included
* Twitter:https://twitter.com/ic_turtles
* Discord:https://discord.com/invite/n77xjyspDR

'''Inferval Vampire Colony'''

* What: 666 randomly generated Vampires on the Internet Computer
* Where: https://www.infernalvampires.com/
* Twitter: https://twitter.com/IVCNFT
* Discord: https://discord.com/invite/mA5cXdAtwe

'''Infinite Charity Project'''

* What: A nonprofit corporation and charitable org providing non-commercial fundraising for 501(c)3 charities
* Where: https://chimps.icproject.org/
* Twitter: https://twitter.com/icproject_nft

'''Internet Astronauts'''

* What: Internet Astronauts are a set of 10,000 limited edition, uniquely minted astronaut-themed NFTs. These end-to-end on-chain NFTs will be up for grabs to the community through the Entrepot.app marketplace. They are only possible through the Internet Computer blockchain.
* Where: https://interastrosc.com/
* Twitter: https://twitter.com/interastrosc

'''Meme Cake'''

* What: The Cake Club is a collection of 7777 Dick NFTs unique digital collectible living on the Internet computer, made by Meme Cake, which claims to be the world's first decentralized comedy platform. Think of it as a 9GAG but decentralized.
* Where: https://memecake.io/
* Twitter: https://twitter.com/realmemecake
* Discord: https://discord.com/invite/vr2ATGMdug

'''Newsie'''

* What: Comic Book and NFT Collection On The Internet Computer
* Where: https://gh2ig-jqaaa-aaaai-aaslq-cai.raw.ic0.app/
* Twitter: https://twitter.com/NewsieCartoon

'''NFT Studio'''

* What: NFT Studio allows users to Mint, Buy, Sell and Stake 3DWASM NFTs on the Internet Computer
* Where: https://7xw5z-uqaaa-aaaad-qaqcq-cai.raw.ic0.app/
* Twitter: https://twitter.com/NFTStudioPoland
* Discord: https://discord.com/invite/65P4NzzSQx

'''NFT Village'''

* What: Look up the attributes, NRI %, rarity, and other information about Internet Computer NFTs. Simply input the URL of your ICPunks and Cronics NFTs or any other NFT minted on the Internet Computer blockchain and learn all of the details that make the NFT unique.
* Where:
** http://nftvillage.ai/
** https://nntkg-vqaaa-aaaad-qamfa-cai.ic.fleek.co/
* Twitter: https://twitter.com/NFT_Village

'''Pokded Studio BOTS'''

* What: A collection of 10,000 individual ROBOTS
* Twitter: https://twitter.com/pokedstudiouk
* Discord: https://discord.com/invite/PokedStudioNFT

'''PORTAL'''

* What: A Streamers Marketplace Powered by the #InternetComputer
* Where: https://ja7sy-daaaa-aaaai-qaguq-cai.raw.ic0.app/
* Twitter: https://twitter.com/PortalDapp
* Discord: https://discord.com/invite/FSSauMNrbS

'''The Sword NFT'''

* What: #ICP exclusive. Follow for updates and airdrop information. Series 1: Little Ninjas. Only 10K Unique Ninjas will be Minted, ever.
* Where: https://theswordnft.com/
* Twitter: https://twitter.com/TheSwordNft
* Discord: https://discord.com/invite/Xgc5zTrdSb

'''Wild and West NFT'''

* What: A wild west themed NFT project
* Where: https://wildandwest.com/
* Twitter: https://twitter.com/WildandWestNFT
* Discord: https://discord.com/invite/wildandwest

'''Yolo Octopus'''

* What: a collection of 8888 intelligently generated NFTs on the Internet Computer blockchain
* Where: http://www.enteryoloclub.com/
* Twitter: https://twitter.com/EnterYoloClub

=== Social (11) ===

'''crowdEats'''

* What: Yelp on IC, owned by users
* Where: https://www.crowdeats.io/
* Twitter: https://twitter.com/crowdeats_io
* Discord: https://discord.gg/Cmm7N9pqsK

'''DSCVR'''

* What: DSCVR is a decentralized version of Reddit, where users are the owners. Decentralized end-to-end, built on the Internet Computer, and accessible from any browser.
* Where: https://h5aet-waaaa-aaaab-qaamq-cai.raw.ic0.app/
* Twitter: https://twitter.com/DscvrO

'''Distrikt'''

* What: Distrikt is a completely decentralized, community-owned professional network. Users of the platform will vote on upgrades, and no user data will ever be mined or sold. Create your account, secured by Internet Identity today.
* Team:
** https://distrikt.io
** https://c7fao-laaaa-aaaae-aaa4q-cai.ic0.app/
* Dapp:
** https://distrikt.app
** https://az5sd-cqaaa-aaaae-aaarq-cai.ic0.app/
* Twitter: https://twitter.com/DistriktApp
* Telegram: https://t.me/DistriktApp
* Newsletter: https://medium.com/distrikt

'''DSocial'''

* What: Decentralized Youtube on IC
* Twitter: https://twitter.com/DSocialApp

'''ICPMeet'''

* What: a Tinder on ICP
* Where: https://www.icpmeet.com/
* Who: [https://github.com/HelloRickey Rickey]
* Twitter: https://twitter.com/icpmeet
* DFINITY Grant: received in July 2021

'''Go Bazzinga'''

* What: World's first decentralised "Short-Video X Draft Kings" Social Speculation Platform
* Where: https://gobazzinga.io/
* Twitter: https://twitter.com/GoBazzingainc

'''Learned'''

* What: LEARND is a community driven educationnal platform running on Internet Computer. We want to provide a new kind of learning and incentives using crypto assets, community vote using SNS, reward learners AND teachers.
* Where: https://learnd.dedn.eu/
* Twitter: https://twitter.com/LEARNDTEAM
* Who: [https://twitter.com/WaffCharlie Charlie Waff]

'''ModClub'''

* What: MODCLUB is a decentralized content moderation platform, it simplifies the moderation process by connecting our community to dApps that need UGC moderation. It has a reputation token economics model.
* Where: https://ljyte-qiaaa-aaaah-qaiva-cai.raw.ic0.app/
* Who: [https://twitter.com/RaheelGovindji Raheel Govindji]
* Twitter: https://twitter.com/ModclubApp
* Discord: http://discord.gg/8zUrHd46Tf
* Medium: [https://medium.com/@modclub](https://medium.com/@modclub)

'''OpenChat'''

* What: Decentralized messaging has been a pipe-dream for decades. With the advent of the Internet Computer, real-time messaging is now possible on a blockchain.
* Where: https://oc.app
* Twitter: https://twitter.com/OpenChat

'''Overchute'''

* What: A decentralized smart-contract application for crowdfunding the release of intellectual property under open licences
* Where: https://overchute.com/
* Twitter: https://twitter.com/OverchuteApp
* Github: https://github.com/Overchute

'''Party Board'''

* What: Multi-chain metaverse social network
* Twitter: https://twitter.com/party_board
* Telegram: https://t.me/partyboard_en
* Discord: https://discord.com/invite/kewhcJM4uf

=== Games (10) ===

'''Cube Run'''

* What: The classic game, "Cube Run" gets an update by having a new graphic interface and being hosted completely on-chain. The decentralized version of this game lets you keep your high-score running in your browser through persistent memory.
* Where: https://7qx3n-ziaaa-aaaad-qaqca-cai.raw.ic0.app/

'''HEXGL'''

* What: HexGL is a futuristic racing game using HTML5, Javascript, WebGL and hosted on the Internet Computer blockchain in order to run instantly on your browser from anywhere in the world.
* Where: https://neqb2-dyaaa-aaaad-qameq-cai.raw.ic0.app/

'''ICMoji Origins'''

* What: ICMoji Origins is an NFT-based multiplayer game built end-to-end on-chain on the Internet Computer.
* Where:
** https://icmojis.com/
** https://graci-aaaaa-aaaah-aaqjq-cai.raw.ic0.app/
* Twitter: https://twitter.com/icmoji
* Who: [https://twitter.com/Visions_GFX Visions]

'''Lo-Fi Player'''

* What: Lo-Fi Player is a dapp hosted on the Internet Computer that lets users listen to relaxing beats delivered by blockchain. The back-end is using machine learning to build and develop the AI produced tunes, and users can interact within the player to change the sound to their liking.
* Where: https://hl2zz-gyaaa-aaaad-qas3a-cai.raw.ic0.app/

'''Mission Is Possible'''

* What: A PVP third person shooter hosted on the Internet Computer blockchain. The John Wick inspired game is built using the Unity 3D Game Engine, and hosted on the IC enabling decentralized login with Internet Identity.
* Where: https://to3ja-iyaaa-aaaai-qapsq-cai.raw.ic0.app/
* Twitter: https://twitter.com/MiP_the_Game

'''Reversi'''

* What: Reversi is one of the first canister smart contracts deployed to the Internet Computer and is a completely decentralized multiplayer game. Play against a friend (or foe) in real-time, from any browser, anywhere in the world.
* Where: https://ivg37-qiaaa-aaaab-aaaga-cai.ic0.app/#!/play
* Who: [https://forum.dfinity.org/u/paulliu/ Paul Liu]

'''Rise of the Magni'''

* What: Rise of the Magni, winner of the DSCVR hackathon for games on the Internet Computer. Buy, earn, and trade collectibles, compete in tactical battles online to earn in-game tokens, and venture through story mode to experience one of the first games built on the Internet Computer.
* Where: https://riseofthemagni.com/
* Who: [https://igpeu-waaaa-aaaad-qaava-cai.raw.ic0.app/ Toniq Labs]
* Twitter: https://twitter.com/ToniqGames

'''Saga'''

* What: Have your fortune told on the Internet Computer. Saga Tarot gives you a tarot reading in one click. The user-friendly dapp is built completely on the Internet Computer, accessible from any browser. What will the future hold for you?
* Twitter: https://twitter.com/SagaCards
* Where:
** https://legends.saga.cards/
** https://5nl7c-zqaaa-aaaah-qaa7a-cai.raw.ic0.app/

'''Texas Hold'em'''

* What: IC Texas Hold'em is a dapp hosted completely on-chain on the Internet Computer. 2nd place winner of the DSCVR Hackathon Season 2
* Where: https://lm5fh-ayaaa-aaaah-aafua-cai.ic0.app/
* Who: [https://twitter.com/NnsDaos NNSDao]
* Github: https://github.com/NnsDao/ICTexas-UI

'''Welcome Into the Metaverse'''

* What: Prize winner of the DSCVR hackathon for the Internet Computer – this game brings digital community into a unified virtual space. Find anecdotes from founding ecosystem members, and go through a series of quests.
* Where: https://lc7ip-3iaaa-aaaah-aafva-cai.ic0.app/
* Who: https://twitter.com/ThuillierSbast3

=== Metaverse (3) ===

'''Drip.Land'''

* What: Open project, liquid democracy/community. Metaverse building on the #IC
* Where: https://drip.land/info
* Twitter: https://twitter.com/ICdripland
* Telegram: https://t.me/icdrip
* Discord: https://discord.com/invite/U8YppXuU2x
* Github: https://github.com/FloorLamp/drip-land

'''Metaverse AI'''

* What: Digital human and virtual idol on IC
* Where: https://www.metaverseai.org/
* Who: [https://www.linkedin.com/in/henryonline/ Henry Yan]
* Twitter: https://twitter.com/metaverseOrg
* Github: https://github.com/Vera-AI-Technology
* DFINITY Grant: received in October 2021

'''XR Foundation'''

* What: an open source zero-profit collective building metaverse technologies.
* Where: https://www.xrfoundation.io/
* Github: https://github.com/XRFoundation/XREngine

=== Productivity (12) ===

'''Aedile'''

* What: Aedile brings your team’s work together in one shared space, completely built on-chain. Manage your boards, columns & cards to transform your projects, serving web experiences directly from the Internet Computer blockchain.
* Where: https://eemeo-taaaa-aaaad-qakjq-cai.ic.fleek.co/
* Who: [https://www.esensconsulting.com/ Esens Consulting]
* Twitter: https://twitter.com/aedile_ic

'''Bunchd'''

* What: Create, Collaborate, and Earn on the Subscription Platform controlled by Creators.
* Twitter: https://twitter.com/GetBunchd

'''Dbox'''

* What: decentralized inbox built on Internet Computer
* Where: https://www.dbox.foundation/
* Twitter: https://twitter.com/DBOXFoundation

'''DeckDeckGo'''

* What: An open source web editor for presentations built completely on-chain. This dapp is like a decentralized version of Google Slides built on the Internet Computer.
* Where: https://deckdeckgo.com
* Who: https://twitter.com/daviddalbusco, https://twitter.com/nasmattia
* Twitter: https://twitter.com/deckdeckgo
* Github: https://github.com/deckgo/deckdeckgo

'''Dmail.ai'''

* What: Use Web3, not Gmail. Dmail makes it safe and private for you to communicate storage and transfer token & NFTs on DFINITY
* Where: https://dmail.ai/
* Twitter: https://twitter.com/dmailofficial
* Telegram: https://t.me/dmailofficial
* Medium: [https://medium.com/@dmail_official](https://medium.com/@dmail_official)
* Github: https://github.com/dmailofficial

'''IC Contacts'''

* What: A social media management tool build on ICP, helping users manage relations in Web3 networks
* Who: [https://twitter.com/relationlabs Relation Labs]
* Twitter: https://twitter.com/relationlabs
* Other: [https://twitter.com/herbertyang/status/1454780835379384326 Grand Slam winner of 7th Wanxiang Blockchain Hackathon]

'''IC Drive'''

* What: A decentralized private file storage dapp built on the Internet Computer. Store and securely share any type from anywhere in the world with this decentralized version of Box, or Google Drive.
* Where: https://icdrive.co
* Who: https://twitter.com/nanditmehra
* Twitter: https://twitter.com/icDrive

'''ICEvent'''

* What: an open event service built on IC
* Where:
** https://icevent.vercel.app
** https://znisf-eqaaa-aaaaj-aabta-cai.raw.ic0.app/
* Twitter: https://twitter.com/vansdaynet

'''Nuance'''

* What: Nuance is a Web3.0 blogging platform that is hosted on-chain end-to-end on the Internet Computer. Developed by Aikin Dapps, the alpha of the world’s first blogging platform to be hosted entirely on a blockchain has now launched. Nuance aims to bring NFTs into the world of editorial content ownership.
* Where: https://fxnaj-yaaaa-aaaaf-qad3q-cai.ic0.app
* Who: [https://www.aikin.io/ AIKIN]
* Twitter: https://twitter.com/AikinDApps
* Discord: https://discord.gg/2dPCPu6zxz

'''Photos by Functionland'''

* What: Photos is a react-native(expo)+typescript application to replace Google Photos/Apple Photos, and give freedom in hosting your photos on any platform, either centralized servers like Amazon or Microsoft, or decentralized solutions such as Dfinity or IPFS-based "box"
* Where: https://fx.land/
* Twitter: https://twitter.com/functionland
* Telegram: https://t.me/functionlanders
* Github: https://github.com/functionland/photos

'''Quark'''

* What: Quark is an open internet service facilitating payments on the Internet Computer like Stripe or Paypal
* Where: https://ebgyc-nqaaa-aaaaf-qad6q-cai.ic0.app/
* Github: https://github.com/SuddenlyHazel

'''Waterslide.app'''

* What: Frontend to interact with the @LiquityProtocol
* Where: https://waterslide.app/
* Twitter: https://twitter.com/waterslide_app

=== Communities (3) ===

'''ICP123'''

* What: Find Awesome Dfinity Projects
* Where: https://icp123.xyz/
* Twitter: https://twitter.com/icp123xyz
* Github: https://github.com/icpfans-xyz
* Who: [https://github.com/includeleec Lee] of [https://twitter.com/nebulasio https://www.nebulas.io/]
* DFINITY Grant: received in June 2021

'''Internet Computer Education'''

* What: very helpful Github-based education resources with elaborate and step-by-step online classes and cirriculum to teach developers Internet Computer
* Where: https://github.com/DFINITY-Education
* Who: [https://github.com/nzoghb nico], [https://github.com/csolimano csolimano] and [https://github.com/crusso Claudio Russo]

'''THUBA Education'''

* What: THUBA Education is an education platform supported by Tsinghua University student Blockchain Association. The goal is to be a solid bridge between students and blockchain world. The students can use this platform to learn blockchain courses, join Hackthon and do some research.
* Where: https://thublockchain.org/
* Who: Tsinghua University Students Blockchain Association

=== Enterprise (9) ===

'''Agryo'''

* What: Agryo is the global risk intelligence provider that enables financial institutions to assess and manage financial risks in the crop field level for underwriting agriculture insurance, loans, and trade finance globally; as well as meet sustainability goals.
* Where: [[www.agryo.com|www.agryo.com]]
* Twitter: https://twitter.com/agryo_

'''ContentFly'''

* What: Marketplace app connecting high quality Content Creators to Brands, running on Dfinity Internet Computer
* Where: https://contentfly.app/
* Twitter: https://twitter.com/ContentFlyApp

'''dFlow'''

* What: "decentralized Workflow"- an innovative and simple way for defining and executing cross-organisational business flows
* Where: https://www.dcentra.io/

'''dService'''

* What: A next-generation decentralized Service Management Application running on the Internet Computer. The Application is primarily focused on IT Service Management.
* Where:
** https://agnoo-nqaaa-aaaah-aaq4q-cai.ic0.app/
** https://dservice.app
* Twitter: https://twitter.com/dServiceApp

'''Get Impact Now'''

* What: The politics platform that enables you to change the world
* Where: https://getimpactnow.org/
* Twitter: https://twitter.com/getimpactnow
* Github: https://github.com/getimpactnow/getimpactnow/

'''Optex'''

* What: Optex is a powerful data visualisation tool designed to provide seamless insights into complex data. Optex is out-of-the-box solution that will allows users to combine data in a single analysis and get a holistic view of the same with interactive customisable visualisations.
* Where: https://www.clinicaltrialsintelligence.org/
* Twitter: https://twitter.com/ClinTexCTi

'''Origyn'''

* What: The Origyn Foundation is blending luxury goods, with NFTs by providing digital verifications for physical objects. Only possible on the Internet Computer.
* Where: https://www.origyn.ch/
* Twitter: https://twitter.com/ORIGYNTech
* Telegram: https://t.me/origynfoundation

'''Triip'''

* What: Triip is a blockchain-enabled travel platform allows for direct interactions between service providers and clients. Using a propriety token, Triip Miles or TIIM, Triip is a network that enables greater transparency, security and lower cost transactions between those who travel and those who serve them.
* Where: https://www.triip.me/
* Twitter: https://twitter.com/triipme
* Telegram: https://t.me/TriipMilesICO
* Github: https://github.com/triipme
* Who: [https://www.triip.me/pages/about_us Triip Pte Ltd]
* DFINITY Grant: received in Aug 2021

'''WeAct.chat'''

* What: The app made for groups of advocates, activists, and change makers working to better the world
* Where: https://www.weact.chat/dfinity
* Twitter: https://twitter.com/WeAct_Chat

Governance of the Internet Computer

2022-01-24T14:31:44Z

Jens:

The Internet Computer blockchain is governed by the Network Nervous System<ref>https://medium.com/dfinity/the-network-nervous-system-governing-the-internet-computer-1d176605d66a</ref>. The NNS is an algorithmic governance system that oversees the network and the token economics that make it possible to build DeFi dapps, open internet services and enterprise systems.

Holders of the Internet Computer’s ICP utility tokens can lock their tokens in ''neurons'' to participate in governance and contribute to decision-making, such as voting to determine whether or not a new collection of nodes (also called a subnet) should be added to the network.

=== Why the Internet Computer needs a Network Nervous System<ref>https://medium.com/dfinity/the-network-nervous-system-governing-the-internet-computer-1d176605d66a</ref> ===
The Internet Computer is a distributed protocol run by a network of node machines, which are hosted in different data centers. The nodes communicate with one another over the internet to achieve a consensus on what the Internet Computer’s state should be. A collection of nodes engaging in consensus is called a subnet. On top of this underlying communication and consensus protocol, the Internet Computer hosts ''canisters'', which are stateful programs that can also communicate with each other. The state of all of the canisters has to be replicated across all of the nodes. Therefore, to allow the Internet Computer to scale indefinitely, the network is made up of not just one subnet, but multiple subnets.

Different subnets can communicate with one another, enabling canisters that are hosted on different subnets to also communicate with each other. For the Internet Computer to scale on-demand, the network must be able to add new subnets over time to increase compute capacity. Moreover, the robustness of the subnets can be improved by adding new nodes to them over time. Eventually, the Internet Computer will run millions of nodes at scale. This means that there needs to be a mechanism by which the nodes and subnets are organized, tracked, and managed. For example, decisions must be made about when subnets and nodes should be added or removed. In addition, the Internet Computer was launched with an initial feature set, which evolves over time. Therefore, the Internet Computer needs to be able to make decisions on how to evolve the protocol in a distributed manner.

=Network Nervous System overview=

The NNS is a tokenized open governance system that is responsible for managing the Internet Computer. For example, the NNS stores information about what nodes belong to which subnet and the code each replica runs. The NNS also makes decisions about how to update this information and evolve the IC.

The NNS is realized by a set of ''[[canisters|canister smart contracts]]''.

=== NNS canister smart contracts ===

# '''Ledger canister:''' The ledger canister stores the ICP utility ''token balance'' of each principal and the history of ICP ''transactions''.
# '''Governance canister:''' The governance canister receives and stores ''Proposals'', which are suggestions for how the Internet Computer should be changed. These proposals can then be voted on. The governance canister also tracks ''Neurons'', which determine who is allowed to participate in governance.
# '''Registry canister:''' The registry canister stores the configuration of the whole Internet Computer, e.g., which nodes belong to a certain subnet and the software each node should run.
# '''Cycles minting canister''': This canister is responsible for minting ''cycles'', the fuel for canisters for computation, communication and storage. New cycles can be minted when a new canister is newly created or when an existing canister is topped up with additional cycles.
# '''Root canister''': The root canister is the controller of all other NNS canisters and responsible for upgrading them.
# '''Lifeline canister''': The lifeline canister is the controller of the root canister and responsible for upgrading it.
# '''Archive canisters''': The canisters that store the history of the ledger transactions once there are too many transactions to keep in a single canister.
#'''Genesis token canister:''' This is the canister that was used to initialize the neurons that already existed during genesis.

The canisters that users of the Internet Computer are interacting with the most are the first two: the ledger canister for making transactions, and the governance canister for staking tokens and submitting and voting on proposals.

= Ledger canister & ICP utility tokens in the NNS =
[[ICP token|ICP utility tokens]] are managed by the ledger canister, which stores two things: accounts and transactions. An account record keeps track of how many tokens are in the possession of a given [[principal]] (i.e., an identity by which a user is authenticated on the Internet Computer). Tokens can then be sent from one account to another, and this is recorded in the transactions of the ledger canister.

In the NNS, ICP utility tokens are used for three different things:

# ICP tokens facilitate '''participation in governance''' (more below on how the neurons are connected with the tokens).
# Those who participate in governance and those who provide compute capacity by operating note machines are '''rewarded''' in ICP tokens.
# ICP tokens are used for '''conversion into cycles''', which are fuel for canisters for computation, communication and storage.

=Governance Canister=

The governance canister is responsible for holding ''neurons'', determining who is allowed to participate in governance. Moreover, it stores proposals, which are suggestions for changes to the Internet Computer, and the information associated with proposals that decides if these suggestions should be implemented. If a proposal is adopted, the governance canister automatically executes the decision. Finally, the governance canister distributes rewards to those neurons who participated in voting and contributed to the decision making.

== Neurons ==
Neurons contain ''locked'' ICP utility tokens. These staked tokens are not liquid and cannot be transferred freely to others.

=== Neuron Attributes ===
Each neuron stores a number of neuron attributes. Some of the most important ones are the following:

* How many ICP tokens are ''locked'' in the neuron. This information is accessible both by a neuron referencing an account on the ledger canister that stores the neuron's balance and by a cached stake on the governance canister.
* A ''controller'' principal, which identifies who manages the neuron's actions.
* A unique ''neuron ID''
*The neuron's ''dissolve delay.'' Intuitively, the dissolve delay defines the earliest time when the locked ICP tokens can be unlocked. This time can be increased to up to 8 years but it can only be decreased by waiting for time to pass. A neuron can either be ''non-dissolving'', ''dissolving'', or ''dissolved.'' If a neuron is non-dissolving, its set dissolve delay is kept stable and the timer is not running down. The neuron can then be set to dissolving, which means that the dissolve delay is decreasing with the time. Finally, if a the dissolve delay reaches 0, the neuron is dissolved and the locked tokens can be transferred out of the neuron.
*The ''age'', which is between 0 and 4 years. A neuron's age determines the time since when then neuron has last entered the non-dissolving state.
A neuron's dissolve delay determines a neuron's ''eligibility'' to participate in voting. Namely, only those neurons with tokens locked for at least six months are eligible to participate in governance. This incentivizes neuron holders to vote such that the value of their tokens is maximized for a future date. Assuming the value of the tokens is a rough proxy for the network’s success, this incentivizes neuron holders to vote in the long-term interest of the Internet Computer.

A neuron's ''voting power'' depends on how many tokens a neuron has locked, as well as the neuron's dissolve delay and age. Intuitively, those who are more committed to the Internet Computer, as they have locked their tokens for longer or have already staked them for a long time, have more voting power. The voting power increases with the dissolve delay and the age.

Finally, the number of rewards that each neuron receives depends on the number of votes that the neuron participated in as well as the neuron's voting power.

===How to lock tokens in a neuron<ref>https://medium.com/dfinity/the-network-nervous-system-governing-the-internet-computer-1d176605d66a</ref>===

As a user, there are different [[ICP staking options]] to stake ICP utility tokens in a neuron. The effect of such an operation is that these ICP tokens are transferred to a ledger account that is associated with a newly created neuron. The tokens are thus locked and cannot be used freely by the neuron holder.

'''Example.''' ''Let’s assume that User B, who has an account (A1) on the ledger canister, would like to lock a hundred tokens in a neuron. To do so, User B sends a command to the NNS specifying the number of tokens and User B’s corresponding principal ID.''

''A transaction is then recorded on the ledger, which specifies that some tokens are sent from the original account (A1) of the user to a new account (A2), which also creates the new account (A2) that holds the locked tokens. A new neuron is created in the governance canister that specifies that User B is the one controlling this neuron and that specifies that the amount of locked tokens is defined by the new ledger account A2.''

''Externally, it’s not visible that the new account (A2) holds locked tokens or is in any way related to the original account (A1). Nevertheless, this account is in fact controlled by the neuron, which means that the tokens are not liquid and that User B cannot transfer the tokens or convert the tokens into cycles.''

The main reason for a user to lock tokens in a neuron is to be able to participate in voting and get voting rewards. Both are described in more detail below.
== Proposals ==
A proposal is a suggestion for a change to the Internet Computer. More technically, a proposal describes a ''method'' in a canister that is called if the proposal is accepted. Moreover, it describes the ''parameters'' with which the method will be called.

The Internet Computer supports a variety of different proposal ''topics''. Here are some examples of topics that are supported in the NNS governance canister:
* #SubnetManagement Proposals: This considers topology changes. The example proposal above about whether a node should be added to a subnet falls into this category.
* #NodeAdmin Proposals: This concerns the administration of node machines. An example of a proposal could specify that all of the nodes in a subnet should be updated.
* #NetworkEconomics Proposals: This concerns the administration of network economics. For example: what rewards should be paid to the node machine providers?
*#Motion Proposals: These proposals do not have a direct execution of a method as a consequence but are merely there to record the opinion of the community on a specified matter.

== Voting and proposal lifecycle ==

=== Submitting a proposal ===
Any eligible neuron can make and [https://wiki.internetcomputer.org/index.php?title=Neuron_Attributes_and_Commands#Make_Proposal submit a proposal]. To avoid being inundated by useless proposals, a user submitting a proposal has to pay a fee of 1 ICP when submitting a proposal, that they will receive back if the proposal is adopted (but that they will not receive back if the proposal is rejected).

'''Example.''' ''Let’s consider a User C who would like to suggest that a new subnet is created that initially consists of two nodes: Node 1 and Node 2. Once User C controls a neuron, they can submit a proposal by specifying their neuron ID, the type of proposal that they would like to submit, and the proposal’s parameters. In our example, the proposal specifies that a new subnet should be created and the proposal's parameters consist of the initial nodes Node 1 and Node 2. Upon the receipt of this proposal, the governance canister first checks that this user is indeed the one controlling the neuron with the given ID and that this neuron is eligible to vote. If the requirements are met, the proposal is added to the governance canister.''

After a proposal is submitted by an eligible neuron, the proposal is created and stored in the governance canister. Moreover, the governance canister computes and stores additional information with each proposal. First, the [[voting power]] of each neuron is computed and stored together with the proposal. The sum of all of these voting powers also determines the ''total voting power'' associated with a given proposal.

When a new proposal is created, the number of “yes” votes associated with the proposal is already increased by the proposer’s voting power. This reflects that the proposal already has the support of the user submitting it.

Moreover, each proposal has an associated ''voting period,'' which determines the period of time over which votes for this proposal are accepted.

=== Viewing NNS Proposals ===
You can see all the NNS proposals on the Internet Computer dashboard: https://dashboard.internetcomputer.org/governance

===Discussing NNS Proposals===

Voters can freely discuss proposal anywhere they like. A lot of NNS proposals are discussed on the developer forum: https://forum.dfinity.org/c/roadmap/29.

===Voting on a proposal===
After a proposal is submitted and added to the governance canister, other users who control neurons can [[ICP voting options|vote on the proposal]]. Currently, the most user-friendly way to vote on NNS proposals is via the NNS Frontend dapp: https://nns.ic0.app/. For voting, users would first learn which are the open proposals on the governance canister that they can actually vote on. This information is available, for example on Internet Computer dashboard: https://dashboard.internetcomputer.org/governance or in the [[NNS frontend dapp]].

If a neuron votes in favor of a proposal, the governance canister adds this neuron’s voting power, as stored with the proposal, to the “Yes”-votes associated with the proposal. Likewise, if a neuron votes against a proposal, the governance canister adds the neuron’s voting power to the “No”-votes of the proposal.

'''Example.''' ''Assume that a given User D would like to reject the proposal that was just added by User C. To do so, User D would send their neuron ID and a “no” vote to the governance canister. The governance canister would check that the vote is coming from the correct user who controls the neuron and confirm that the neuron is eligible to vote. If the conditions are met, the governance canister would then add the voting power of User D to the “no” votes.''

====Neuron following and liquid democracy====

Users may not have the time or knowledge to participate in all voting decisions. Therefore, instead of directly voting on proposals, neuron holders may choose to delegate their vote to other neurons that they trust with certain decisions. This concept of delegating the right to vote to other voters who then effectively vote with more voting power is called ''liquid democracy.''

Concretely, for each proposal topic a neuron can [[How to follow neurons|specify a set of other neurons that it would like to ''follow'']] ''(so-called followees)''. In addition, a neuron can specify a set of followees for "all other topics" that are not covered by specific rules. The governance canister keeps track of this relation of follower and followee neurons. It then automatically casts a vote for a follower neuron based on the decision of the followees. In particular, if more than 50% of the followees vote "yes", then a "yes" vote is cast for the follower and if at least 50% of the followees vote "no", then a "no" vote is cast for the follower.

'''Example'''. ''Consider neuron N1 that follows the set of neurons {N2, N3, N4, N5} on all proposal topics. Consider now that a proposal is submitted by another neuron N6. Assume in a first scenario that first N2 votes "No" and then N3 votes "No" on the proposal. In that case, the governance canister will also send a "No" vote for N1 two out of four followees voted "No" (which also means that it is not possible anymore to get more than 50% "Yes" votes). Assume a second scenario where N2 votes "Yes" and then N3 votes "Yes" on the proposal. In that case, no vote is sent yet for N1. However, if either N4 and N5 also send a "Yes" vote, a "Yes" vote is also cast for N1.''

This liquid democracy has great advantages. First, it allows even neurons that do not have enough knowledge of a certain topic to nevertheless participate in governance by choosing the neurons that they trust with certain decisions and by delegating their vote to them. In particular, a neuron can choose a different set of followees for different topics. Moreover, this mechanism allows neuron holders to get voting rewards from voting participation even if they do not have time to actively participate in all voting decision.

=== Proposal decision and wait-for-quiet ===
A proposal can be ''decided'' in two ways:
# '''Absolute Majority before the voting period ends''': At any point, even before the voting period ends, if an absolute majority (more than half of the total voting power stored in the proposal) has voted Yes, then the proposal is adopted and if an absolute majority has voted No, then the proposal is rejected.
# '''Simple Majority at the voting period’s end''': When the voting period ends, if a simple majority (more than half of the cast votes) has voted Yes and the number of these Yes-votes constitute at least 3% of the total voting power, then the proposal is adopted. Otherwise, the proposal is rejected.

What also plays into this is the fact that the governance voting algorithm also applies ''wait-for-quiet''. The idea of wait-for-quiet is to decide proposals quickly when all voters agree, but increase the time that neurons can vote for proposals that are controversial. That means that the voting period can be dynamically increased, depending on the neurons’ votes. In particular, each time a proposal’s outcome is turned (either a Yes-majority is turned to a No-majority or vice versa), the proposal’s deadline is increased. Currently, a proposal's initial voting period is 4 days and can be increased by at most another 4 days. That is, the voting period that is taken into account for the above rules can be between 4 and 8 days, depending on the voting activity.

=== Proposal execution ===
Recall that a proposal defines a method, a canister, and some parameters. As soon as a proposal is adopted, the defined method on the specified canister is called with the given parameters. This is done fully automatically by the governance canister.

== Voting Rewards ==
Contributing to decision-making is one incentive for voters to lock their neurons, but they are also ''rewarded'' for participating in network governance.

Specifically, each day the governance canister considers which proposal can be settled. It is then considered for each neuron in how many proposals they participated and with which voting power. Depending on this, the neurons get rewarded. Concretely, rewards are added to the neuron's attribute that is called ''maturity.'' Maturity represents ICP utility token that are not yet minted.

A neuron holder can then profit from the maturity in two ways:

# '''Spawn maturity:''' A neuron holder can choose to [[How to spawn a neuron|spawn a new neuron]] to get liquid ICP utility tokens worth the voting rewards. Spawning a new neuron has the effect that a new neuron with a new associated account on the ledger will be created, which contains the amount of staked ICP utility token equivalent to the maturity of the original neuron. In fact, the new tokens are minted and transferred to the new account, which is also recorded in the ledger canister. The new neuron has a small dissolve delay of 7 days. This means that users only need to wait a short amount of time to be able to unlock the tokens and use them freely, no matter what dissolve delay the original neuron has.
# '''Merge maturity''': A neuron holder can choose to [[merge maturity]] to reinvest the voting rewards in the existing neuron. This neuron operation adds the ICP utility token equivalent of the maturity to the neuron's stake and adjusts the neuron's age accordingly. Effectively this means that the maturity is reinvested in the neuron and contributes to the neuron's voting power.

= Cycles Minting Canister and Cycles<ref>https://medium.com/dfinity/the-network-nervous-system-governing-the-internet-computer-1d176605d66a</ref> =
Besides governance participation and voting rewards, tokens can also be converted into cycles, which fuel computation and storage on the Internet Computer. Each canister on the Internet Computer, except for those on the NNS, uses cycles for computations and has some cycles stored within it. While the token price may vary over time, the goal of the cycles is to keep the price of computation roughly consistent over time.

The canister responsible for converting ICP utility tokens into cycles is the ''Cycles Minting Canister.'' To convert cycles for creating or topping-up a canister, a user needs to send ICP utility tokens to the Cycles Minting Canister. This canister then burns the tokens and mints the cycles.

The Cycles Minting Canister only facilitates the conversion of ICP utility tokens to cycles but not the other way around. Cycles are burned in canisters when they use computation and storage over time.

'''Example.''' ''Consider User E who runs a canister on the Internet Computer and would like to top up the cycles of this canister so that it can perform even more computations. Also assume that this canister currently has 700 trillion cycles and User E would like to increase this number by 200 trillion. To do so, the user would send a command to the NNS that specifies the action of topping up their canister. Upon receiving this command, a transaction is made from the user’s account to the Cycles Minting Canister. As a result of this transaction, the Cycles Minting Canister would burn the tokens, mint new cycles, and send these freshly minted cycles to the user’s canister, meaning the canister balance is now 900 trillion cycles.''

=References=