Internet Computer Wiki - User contributions [en]

Internet Computer wiki

2022-10-17T21:11:08Z

Vusirikala:

==Welcome!==

This is a general source of information about 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>. Created for and by the IC community, topics vary from cryptography, network governance, user experience, tokenomics, developer tutorials and more.

==Introduction to the Internet Computer==
The Internet Computer is a general-purpose blockchain that hosts [[canister smart contract]]s. It is designed to [[Replace traditional IT with a World Computer|provide a World Computer that can replace traditional IT]] and host a new generation of [[Web3:_The_bull_case_for_the_Internet_Computer|Web3]] services and applications that run solely from the blockchain, without the need for traditional IT. It can also play the role of Web3 orchestrator, by interacting with traditional blockchains.

It has a completely unique design that reflects a ground-up rethink of blockchain architecture and the application of modern cryptography, [https://web.archive.org/web/20150914013643/http://dfinity.io/ which can be traced back to 2015]. It was built by the largest [https://dfinity.org/team ongoing R&D effort in crypto], which has employed many notable cryptographers, computer science researchers and engineers. The blockchain underwent genesis in May 2021 and became part of the public internet.

The Internet Computer blockchain's protocols leverage novel [[chain key cryptography]] to combine multiple [[Limitless_Scaling#Subnet Architecture|subnet blockchains]] into a single blockchain. This allows it to [https://en.wikipedia.org/wiki/Scalability#Horizontal_(scale_out)_and_vertical_scaling_(scale_up) horizontally scale] the total volume of hosted [[canister smart contract]], and their computations and data, without limit. These smart contracts run at web speed, and with web-levels of efficiency, and uniquely, thanks to the blockchain architecture enabled by chain key crypto, can process HTTP requests and directly and securely serve interactive web experiences to the end-users of web3 services, without need for trusted intermediaries (whereas on other blockchains, the web experience users interact with is generally built on centralized, insecure and trusted servers or cloud computing services).

Through these kinds of unique capabilities, the Internet Computer provides a platform that can be used to build mass market web3 services that run 100% on-chain, without any need for traditional IT, such as web servers and databases running on cloud computing services. The longer-term objective is that the Internet Computer will completely replace traditional IT, creating a ''blockchain singularity'', in which everything runs fully on-chain in powerful new forms where it is unstoppable and cannot be hacked.

The development of the Internet Computer has heralded numerous notable technological developments, such as [[chain key cryptography]] and programming languages such as [https://wiki.internetcomputer.org/wiki/Motoko Motoko]. In another notable advance, the Internet Computer hosts an advanced [https://en.wikipedia.org/wiki/Decentralized_autonomous_organization DAO] within its protocols, called the [[Network Nervous System]], which provides the community with direct control over network governance, and can upgrade the protocol running on its network nodes, without requiring the network to fork. The network's utility token is ICP (see [[Roles of the ICP utility token]]).

A recent new technological advance has extended the Internet Computer's [[chain key cryptography]] protocols. This has enabled smart contracts hosted on the Internet Computer to directly interact with other blockchains, without need for dangerous centrally-controlled bridges or wrapping (see [[trustless multi-chain web3 using the IC]], and [[Extend Bitcoin, Ethereum and other blockchains|extending Bitcoin, Ethereum and other blockchains]]).

For example, a canister smart contract hosted on the Internet Computer can create bitcoin addresses, and directly send and receive bitcoins on the Bitcoin ledger as though it were hosted by the Bitcoin network itself. This is possible because chain key crypto enables blockchains to create public "chain keys", for which their nodes can create corresponding signatures. Recent work has now made it possible to create ECDSA chain keys. Since [https://en.wikipedia.org/wiki/Elliptic_Curve_Digital_Signature_Algorithm ECDSA] is the signature scheme used by most other blockchains, this means the Internet Computer can create TX on other blockchains.

Future work will enable its smart contracts to directly interact with other important blockchains such as [https://ethereum.org/en/ Ethereum]. This also leverages other important features such as [[HTTPS outcalls]]. As a consequence, many believe that the Internet Computer will play the role of an orchestration layer that combines different blockchains in the web3 environment, and helps combine them with off-chain services and systems, such as Web 2.0 services and enterprise systems, in a trustless way.

===Popular places to start===
* [https://www.youtube.com/watch?v=IfM3I8pudFs&t=327s Internet Computer overview video from 2022 IC hackathon]
* [https://www.youtube.com/watch?v=IfM3I8pudFs June 2022 IC hackathon, full launch video]
* [https://dfinity.org/icig.pdf Internet Computer Infographic (PDF)]

* [[Glossary]]

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

===For a more technical audience===
* [https://eprint.iacr.org/2022/087 "Internet Computer for Geeks" paper]
* The [https://dfinity.org/howitworks "How it works" series] with videos and in-depth articles on various topics.
* [https://www.reddit.com/r/dfinity/comments/ozboyi/megathread_technical_amas/ Technical AMAs on Reddit by different IC and DFINITY teams]

== Internet Identity Introduction ==
One of the core benefits of building on the Internet Computer is that end users do not need to pay fees or use tokens to access and use dapps. As an alternative to authenticating from a wallet, users can authenticate with an Internet Identity. Learn more information about Internet Identity (II), a blockchain authentication framework supported by the Internet Computer:

* [[What is Internet Identity]]
* [[How to create an Internet Identity]]
* [[Internet Identity technical overview]]
* [https://identity.ic0.app/ Internet Identity dapp]

==IC 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]]

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

== IC for ICP Token-holders, Stakers, 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]]
* [[Tutorials for acquiring, managing, and staking ICP]]
* [[Staking, voting and rewards]]
* [[Governance of the Internet Computer]]
* [[Network Nervous System]]
* [[Total supply, circulating supply, and staked_ICP]]
* [[NNS neuron operations related to maturity]]

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

== IC for Smart Contract and Dapp Developers ==

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

Examples:
* [[Canisters (dapps/smart contracts)]]
* [https://smartcontracts.org/ Developer documentation on smartcontract.org]
* [https://forum.dfinity.org/ IC community developer forum]


* [[Bitcoin integration]]
* [[SNS Tokenization Considerations]]
* [[Web Speed]]
* [[Web Serving]]
* [[Limitless Scaling]]
* [[Users interact with dapps without tokens]]
* [[Parallelism]]
* [[Proof of Personhood]]

If you've been programming smart contracts on Ethereum before, you should read [[The Internet Computer for Ethereum Developers]].

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

== IC for the Curious, Researchers and Blockchain Enthusiasts ==

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

Examples:
* [https://dfinity.org/howitworks/ How the Internet Computer Works]
* [https://dashboard.internetcomputer.org/ Internet Computer dashboard]
* [[Internet Computer performance]]
* [[DFINITY Foundation]]
* [[Bitcoin integration]]
* [[Third-party security audits]]
* [[Networking]]
* [[ICP technical design documents]]

== For Node Providers ==
Node providers invest in and operate node hardware, which powers the Internet Computer with processing and storage capacity. Running these nodes in data centers provides the high performance and the cost-effectiveness of the Internet Computer. Every node provider is allowed a limited amount of nodes.
* [[Node Provider Onboarding]]
* [[IC OS Installation Runbook - Dell Poweredge]]
* [[IC OS Installation Runbook - Supermicro]]
* [[Storage Runbook]]
* [[Node rewards]]

== Technical Working Groups ==
* [[Identity & Authentication]]
* [[Developer Tooling]]
* [[Ledger & Tokenization]]
* [[Scalability & Performance]]

== 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]]

===Best Practices===
Example:
* [[Managing ICP holdings]]
* [[Managing Internet Identity]]
* [[Maximizing Voting and NNS Rewards]]
See more in [[Best Practices]]

=== Tutorials ===
Example:
* [[Tutorials for acquiring, managing, and staking ICP]]
* [[How-To: Claim neurons for seed participants]]
* [[How-To: Create an NNS motion proposal]]
* [[How-To: Set your neuron to follow another neuron]]
* [[How-To: Updating neuron following via quill]]

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==

test

Proof of Personhood

2022-10-12T19:27:31Z

Vusirikala: Created page with "= This page is still work in progress = == People Parties == People parties<ref>https://medium.com/dfinity/ultimate-decentralization-using-virtual-people-parties-that-deliver..."

= This page is still work in progress =

== People Parties ==
People parties<ref>https://medium.com/dfinity/ultimate-decentralization-using-virtual-people-parties-that-deliver-proof-of-personhood-at-de575522c80</ref> are a mechanism for obtaining proof of personhood (also referred to as proof of humanity) built on and for the Internet Computer.

Each people party takes place at one specific point in time. Prior to that time, each prospective participant commits to a location that they will visit for the time of the party. At the beginning of the party, participants are assigned to small, random subgroups, and meet in a real-time video call with other participants assigned to the same group. The video call, however, does not show the participants’ faces; instead, participants show their surroundings, proving that they are at the place they committed to. As locations chosen by different participants must have a certain minimum distance, and no participant can be physically present at two locations simultaneously, the proof of personhood even guarantees the uniqueness of the validated persons.

The main purpose of people parties is democratization. Each validated participant can designate a neuron in the network nervous system that receives increased voting power; this improves the relative voting power of the “many” vs. the “heavy”. It also provides additional voting rewards to all validated participants, which further motivates people to participate in the parties. The validated personhood also benefits the Internet Computer ecosystem more broadly: Open Internet Systems, which are dapps that are controlled by a decentralized governance system, will be able to profit from the improved decentralization similarly to the Internet Computer itself. And any dapp will be able to use the validation information in order to, e.g., differentiate between bots and actual human users.

== Party Flow ==

== Personhood Score ==
Each identity in the internet computer is assigned a personhood score. If an identity hasn’t participated in any people party, its personhood score is 0. As the identity participates in people parties, its personhood score increases. This personhood score can potentially be used to determine voting power of an identity in many elections/voting programs.

===== Requirement #1 =====
An Internet Computer user is naturally inclined to increase his voting power. He is therefore motivated to create many identities and attend a people party with each identity. This gives him control of many identities with a positive personhood score, and thereby a higher voting power. We would like to avoid this. We would like to design the personhood score in such a way that an IC user is motivated to attend each people party with the same identity rather than creating a new identity for each people party.

===== Requirement #2 =====
Suppose Alice attended many parties with her identity, and Bob attended only one recent party. Alice and Bob’s personhood scores should still be close. Alice should not have a significant advantage by attending many parties.

===== Failed Attempt #1 =====
Suppose personhood score of an identity = 1 if the identity is successfully validated in at least one party. This personhood score violates our Requirement #1.

===== Failed Attempt #2 =====
Suppose personhood score of an identity = number of parties in which the identity is successfully validated. This personhood score violates our Requirement #2.

===== Successful Attempt =====
After a party ends, the personhood score of an identity is composed of three components:
* Recent party result (RPR): This value is 1 if the identity is accepted to be a person in the recent party. The value is 0 if the identity did not participate or is rejected in the recent party.
* Decay function of previous personhood score: The decay function is a monotonically non-increasing function. It is computed on the old personhood score (the score before the recent party started). The decay lets us give more weightage to the validation in the recent party over the previous parties.
* Bonus reward function: If the identity is accepted in the most recent party and is successfully accepted in some parties before, a bonus reward is given to the identity. This bonus component is added to incentivize IC users to participate in all the parties using the same identity rather than creating a different identity for each party.

Suppose the personhood score of an identity is PSold before a party starts. The trust score PSnew of the identity after the party ends is calculated as follows.

PSnew = RPR * (1 + bonus(PSold)) + decay(PSold)

Where Recent Party Result (RPR) is 1 iff the identity is accepted in the party.

Through empirical evidence, we found that
* bonus(x) = log10(1 + 0.25 * x) and
* decay(x) = log10(1 + x)
work pretty well. That is,

PSnew = RPR * (1 + log10(1 + 0.25 * PSold)) + log10(1 + PSold)

===== Example =====
Consider 2 scenarios.
* Scenario A: The user enters each party with the same identity, and the user is accepted in each of the parties.
* Scenario B: The user enters each party with a new identity, and the user is accepted in each of the parties.

Let us compare the personhood scores of the user in each of the scenarios. In Scenario B, we sum up the personhood scores of all the identities controlled by the user.

{| class="wikitable"
|+ Comparison of personhood scores of a user in Scenarios A & B
|-
! !! Scenario A !! Scenario B
|-
| Initial Score || 0 || 0
|-
| After 1st party || 1 || 1
|-
| After 2nd party || 1.398 || 1.301
|-
| After 3rd party || 1.510 || 1.415
|-
| After 4th party || 1.539 || 1.462
|-
| After 5th party || 1.546 || 1.482
|-
| After 6th party || 1.548 || 1.491
|-
| After 7th party || 1.548 || 1.494
|-
| After 8th party || 1.548 || 1.496
|}