One of the main features of blockchains is the decentralization: each transaction sent is verified by multiple nodes and its validation process does not rely on a single trusted third party.
In the beginning, the idea of decentralization by using Blockchains only applied to currency transfers. Over time, the scope of decentralization extended beyond just the currency transfers, through innovation in smart contracts: applications could run directly on blockchains, opening the way for more use-cases: making the decentralization of applications a reality.
Such applications are called Dapps for Decentralized applications.
They solve the same issues for applications that blockchains solved about banks:
- decentralization: the Dapp logic runs on a distributed computing system (using smart contracts), as opposed to the overwhelming majority of applications that run on centralized private servers (or backend).
- transparency: Dapps are usually open source, meaning that everyone can read and check the source code of the app. Every action performed by its admins can be checked by anyone. Thus, users can more easily trust those applications. In the case of Tezos, everyone can read the Michelson code deployed onto the network.
- history: everyone can read the history of all the transactions.
Dapps are usually composed of two parts:
- Smart contracts deployed onto the Tezos network, containing the Dapp logic (acting as backend). They are the decentralized part of the application.
- An off-chain part: most of the time, it is a UI interacting with the deployed smart contracts. This UI can be a web application, a desktop application, a mobile application, a CLI, etc. The UI can be served from a private server or from a decentralized hosting service like IPFS.
Dapps are first and foremost applications, and should to this end be designed with great care regarding the user experience, performance and scalability. These are the cornerstones necessary for the massive adoption of Dapps.
In other modules, the interactions with deployed smart contracts have been performed with CLIs (Octez client for instance) or libraries (Pytezos). However, these tools are meant for developers and not for the users, who need more user-friendly interfaces. Thus, for each smart contract, a frontend and possibily a backend (containing parts of the business logic) has to be developed to display information from the contract, make contract calls and to interact with off-chain services.
- Discover an in-browser Tezos wallet; Temple; that allows users to manage Tezos addresses and interact with the Tezos blockchain safely.
- Learn how to make deployments easier during the Dapp development phase using Taquito.