|
32 | 32 | //! |
33 | 33 | //! ## Comparative Table |
34 | 34 | //! |
35 | | -//! | Aspect | Runtime | Smart Contracts | |
| 35 | +//! | Aspect | Runtime |
| 36 | +//! | Smart Contracts | |
36 | 37 | //! |-----------------------|-------------------------------------------------------------------------|----------------------------------------------------------------------| |
37 | | -//! | **Design Philosophy** | Core logic of a blockchain, allowing broad and deep customization. | Designed for DApps deployed on the blockchain runtime.| |
38 | | -//! | **Development Complexity** | Requires in-depth knowledge of Rust and Substrate. Suitable for complex blockchain architectures. | Easier to develop with knowledge of Smart Contract languages like Solidity or [ink!](https://use.ink/). | |
39 | | -//! | **Upgradeability and Flexibility** | Offers comprehensive upgradeability with migration logic and on-chain governance, allowing modifications to the entire blockchain logic without hard forks. | Less flexible in upgrade migrations but offers more straightforward deployment and iteration. | |
40 | | -//! | **Performance and Efficiency** | More efficient, optimized for specific needs of the blockchain. | Can be less efficient due to its generic nature (e.g. the overhead of a virtual machine). | |
41 | | -//! | **Security Considerations** | Security flaws can affect the entire blockchain. | Security risks usually localized to the individual contract. | |
42 | | -//! | **Weighing and Metering** | Operations can be weighed, allowing for precise benchmarking. | Execution is metered, allowing for measurement of resource consumption. | |
| 38 | +//! | **Design Philosophy** | Core logic of a blockchain, allowing broad and deep customization. |
| 39 | +//! | Designed for DApps deployed on the blockchain runtime.| | **Development Complexity** | Requires in-depth knowledge of Rust and Substrate. Suitable for complex blockchain architectures. | Easier to develop with knowledge of Smart Contract languages like Solidity or [ink!](https://use.ink/). | |
| 40 | +//! | **Upgradeability and Flexibility** | Offers comprehensive upgradeability with migration logic |
| 41 | +//! and on-chain governance, allowing modifications to the entire blockchain logic without hard |
| 42 | +//! forks. | Less flexible in upgrade migrations but offers more straightforward deployment and |
| 43 | +//! iteration. | | **Performance and Efficiency** | More efficient, optimized for specific needs of |
| 44 | +//! the blockchain. | Can be less efficient due to its generic nature (e.g. the overhead of a |
| 45 | +//! virtual machine). | | **Security Considerations** | Security flaws can affect the entire |
| 46 | +//! blockchain. | Security risks usually localized to the individual |
| 47 | +//! contract. | | **Weighing and Metering** | Operations can be weighed, allowing for precise |
| 48 | +//! benchmarking. | Execution is metered, allowing for measurement of resource |
| 49 | +//! consumption. | |
43 | 50 | //! |
44 | 51 | //! We will now explore these differences in more detail. |
45 | 52 | //! |
|
0 commit comments