일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | ||||||
2 | 3 | 4 | 5 | 6 | 7 | 8 |
9 | 10 | 11 | 12 | 13 | 14 | 15 |
16 | 17 | 18 | 19 | 20 | 21 | 22 |
23 | 24 | 25 | 26 | 27 | 28 | 29 |
30 |
- REACT
- built in object
- Redux
- express.js
- error
- API
- web
- middleware
- CLASS
- 삶
- concept
- 기준
- bitcoin
- SSR
- graphQL
- JavaScript
- blockchain
- Interface
- typeScript
- Ethereum
- node.js
- useState
- Props
- hardhat
- solidity
- CSS
- evm
- tailwindcss
- HTML
- nextJS
- Today
- Total
목록abstract (2)
ReasonJun
Abstract contracts and interfaces are both powerful features of Solidity that can be used to improve the quality, flexibility, and readability of your code. However, there are some key differences between the two. Abstract contracts Abstract contracts are contracts that cannot be deployed by themselves. They must be inherited by other contracts. Abstract contracts are used to define the common f..
An abstract contract in Solidity is a contract that cannot be deployed by itself. It must be inherited by other contracts. Abstract contracts are used to define the common functionality of a group of related contracts. To create an abstract contract, you use the abstract keyword. For example, the following contract is abstract: abstract contract Student { function major() public pure virtual ret..