일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
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 |
- 삶
- web
- typeScript
- Redux
- blockchain
- REACT
- useState
- middleware
- node.js
- evm
- hardhat
- HTML
- 기준
- CLASS
- express.js
- Interface
- nextJS
- SSR
- CSS
- built in object
- bitcoin
- concept
- Props
- solidity
- tailwindcss
- Ethereum
- API
- graphQL
- JavaScript
- error
- Today
- Total
목록delegatecall (2)
ReasonJun

The main difference between call() and delegatecall() in Solidity is that call() executes code in a new context, while delegatecall() executes code in the context of the caller. call() When you call a function using call(), the called function is executed in a new context, with its own stack and storage. This means that the called function does not have access to the caller's state, and any chan..
Delegatecall is a low-level Solidity opcode that allows a contract to execute code from another contract while using the state and storage of the calling contract. This can be used to implement a variety of features, such as: Upgrading contracts without losing data: Delegatecall can be used to upgrade a contract to a new version without losing any of the data stored in the contract. This is done..