| 일 | 월 | 화 | 수 | 목 | 금 | 토 |
|---|---|---|---|---|---|---|
| 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 | 31 |
- blockchain
- evm
- hardhat
- built in object
- JavaScript
- solidity
- node.js
- middleware
- HTML
- useState
- Ethereum
- Redux
- tailwindcss
- graphQL
- express.js
- typeScript
- REACT
- 삶
- 기준
- nextJS
- web
- CSS
- CLASS
- API
- concept
- error
- SSR
- Interface
- bitcoin
- Props
- Today
- Total
목록external (2)
ReasonJun
The main difference between fallback() and receive() in Solidity is that fallback() is called when a contract receives Ether without any calldata, while receive() is called when a contract receives Ether with empty calldata. In other words, fallback() is called when a user sends Ether to a contract directly, while receive() is called when a user calls a function on a contract without passing any..
Visibility in Solidity is used to control who can access and modify functions and state variables within a contract. There are four visibility levels in Solidity: Public: Public functions and state variables can be accessed by anyone, inside or outside of the contract. Internal: Internal functions and state variables can be accessed by any function within the contract, as well as any function wi..