Difference between revisions of "Decentralized Applications (DApps)"

Latest revision as of 04:14, 7 November 2022

A decentralised application. So not an app. But a dapp. Now possible with blockchains and smart contracts. Unlike regular apps one uses on a mobile phone or a laptop, dApps are powered by multiple servers.
From Vitalik’s terminology guide:

"A decentralized application is similar to a smart contract, but different in two key ways. First of all, a decentralized application has an unbounded number of participants on all sides of the market. Second, a decentralized application need not be necessarily financial. Because of this second requirement, decentralized applications are actually some of the easiest things to write (or at least, were the easiest before generalized digital consensus platforms came along). For example, BitTorrent qualifies as a decentralized application, as do Popcorn Time, BitMessage, Tor and Maidsafe (note that Maidsafe is also itself a platform for other decentralized applications).

Generally, decentralized applications fall into two classes, likely with a substantial gray area between the two. The first class is a fully anonymous decentralized application. Here, it does not matter who the nodes are; every participant is essentially anonymous and the system is made up of a series of instant atomic interactions. BitTorrent and BitMessage are examples of this. The second class is a reputation-based decentralized application, where the system (or at least nodes in the system) keep track of nodes, and nodes maintain status inside of the application with a mechanism that is purely maintained for the purpose of ensuring trust. Status should not be transferable or have de-facto monetary value. Maidsafe is an example of this. Of course, purity is impossible – even a BitTorrent-like system needs to have peers maintain reputation-like statistics of other peers for anti-DDoS purposes; however, the role that these statistics play is purely in the background and very limited in scope."

@@ Line 1: / Line 1: @@
-* A decentralised application. So not an app. But a dapp. Now possible with [[Blockchain|blockchains]] and [[Smart Contract|smart contracts]].
+* A [[Decentralized|decentralised]] application. So not an app. But a dapp. Now possible with [[Blockchain|blockchains]] and [[Smart Contract|smart contracts]]. Unlike regular apps one uses on a mobile phone or a laptop, dApps are [https://thedefiant.io/what-is-a-dapp powered by multiple servers].
+*From [[Vitalik Buterin|Vitalik’s]] [https://blog.ethereum.org/2014/05/06/daos-dacs-das-and-more-an-incomplete-terminology-guide/ terminology guide]:
-* From [[Vitalik Buterin|Vitalik’s]] [https://blog.ethereum.org/2014/05/06/daos-dacs-das-and-more-an-incomplete-terminology-guide/ terminology guide]:
 ''"A decentralized application is similar to a smart contract, but different in two key ways. First of all, a decentralized application has an unbounded number of participants on all sides of the market. Second, a decentralized application need not be necessarily financial. Because of this second requirement, decentralized applications are actually some of the easiest things to write (or at least, were the easiest before generalized digital consensus platforms came along). For example, [[BitTorrent]] qualifies as a decentralized application, as do Popcorn Time, BitMessage, [[Tor]] and [[Maidsafe]] (note that Maidsafe is also itself a platform for other decentralized applications).''
-''Generally, decentralized applications fall into two classes, likely with a substantial gray area between the two. The first class is a fully anonymous decentralized application. Here, it does not matter who the [[Node|nodes]] are; every participant is essentially anonymous and the system is made up of a series of instant atomic interactions. BitTorrent and BitMessage are examples of this. The second class is a reputation-based decentralized application, where the system (or at least nodes in the system) keep track of nodes, and nodes maintain status inside of the application with a mechanism that is purely maintained for the purpose of ensuring trust. Status should not be transferable or have de-facto monetary value. Maidsafe is an example of this. Of course, purity is impossible – even a BitTorrent-like system needs to have peers maintain reputation-like statistics of other peers for anti-DDoS purposes; however, the role that these statistics play is purely in the background and very limited in scope."''[[Category:Jargon/Various]]
+''Generally, decentralized applications fall into two classes, likely with a substantial gray area between the two. The first class is a fully anonymous decentralized application. Here, it does not matter who the [[Node|nodes]] are; every participant is essentially anonymous and the system is made up of a series of instant atomic interactions. BitTorrent and BitMessage are examples of this. The second class is a reputation-based decentralized application, where the system (or at least nodes in the system) keep track of nodes, and nodes maintain status inside of the application with a mechanism that is purely maintained for the purpose of ensuring trust. Status should not be transferable or have de-facto monetary value. Maidsafe is an example of this. Of course, purity is impossible – even a BitTorrent-like system needs to have peers maintain reputation-like statistics of other peers for anti-[[Denial-of-Service attack (DoS attack)|DDoS]] purposes; however, the role that these statistics play is purely in the background and very limited in scope."''[[Category:Jargon/Various]]