> For the complete documentation index, see [llms.txt](https://monobridge.gitbook.io/monobridge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://monobridge.gitbook.io/monobridge/ecosystems-and-dapps/1.2-history-and-prospects-of-dapps/1.2.1-history-of-dapps.md).

# 1.2.1 History of Dapps

As the application environment evolves, the ways in which Dapps are deployed and run have changed as well, as shown in Figure 1.

<figure><img src="/files/xz5QQVyGwQ2pyzTK8qsL" alt=""><figcaption></figcaption></figure>

Stage I: Blockchain as Dapp. The blockchain system itself is a Dapp. All public chains are such Dapps.&#x20;

Stage II: Single-chain deployment and single-chain running. The contract that is part of a Dapp needs to be deployed and run on the chain where it is located according to the technological system of the chain, using the corresponding development language. It executes the business logic based on the on-chain data, the results of which are also stored on the chain.&#x20;

Stage III: Multi-chain deployment and single-chain running. Dapps can be deployed on multiple EVM-compatible chains without an extensive effort for code modification, but each Dapp runs independently on the chain it is located. The above reflects the evolution of ways in which Dapps are deployed and run at different stages of the decentralized application environment powered by blockchain, and also illustrates how the application environment drives the change of ways in which Dapps are deployed and run.