Git-Mirrors/blockchains-security-toolkit
1
0
Fork 0
mirror of https://github.com/autistic-symposium/blockchains-security-toolkit.git synced 2025-05-13 12:12:19 -04:00
Code Issues Projects Releases Packages Wiki Activity

Update proxies.md

Browse source
This commit is contained in:
steinkirch.eth, phd 2023-04-25 08:41:05 -07:00 • committed by GitHub
parent bb48e7b75d
commit 1644d317e3
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

17
advanced_expert/vulnerabilities/delegatecall/proxies.md
View file

@ -1,10 +1,14 @@
## proxies
<br>
### tl; dr
<br>
* here exists a special variant of a message call, named delegatecall which is identical to a message call apart from the fact that the code at the target address is executed in the context (i.e. at the address) of the calling contract and msg.sender and msg.value do not change their values. This means that a contract can dynamically load code from a different address at runtime. Storage, current address and balance still refer to the calling contract, only the code is taken from the called address.
* there exists a special variant of a message call, named delegatecall which is identical to a message call apart from the fact that the code at the target address is executed in the context (i.e. at the address) of the calling contract and `msg.sender` and `msg.value` do not change their values.
* this means that a contract can dynamically load code from a different address at runtime.
* storage, current address and balance still refer to the calling contract, only the code is taken from the called address.
<br>
@ -30,7 +34,7 @@
1. upgrade logic is stored in proxy itself.
2. gas-inefficient
<br>
#### universal upgradable proxy standard (UUPS)
@ -38,11 +42,11 @@
2. gas-efficient
<br>
#### diamond pattern
* diamond patterns differ from proxy patterns because the diamond proxy contract can delegates function calls to more than one logic contract.
* when a user makes a function call, the proxy contract checks the mapping to find the facet responsible for executing that function. Then it invokes delegatecall (using the fallback function) and redirects the call to the appropriate logic contract.
@ -52,6 +56,7 @@
### unitialized proxy bug
<br>
* Developers might leave proxies unitialized - this can be a problem when it leads to changes such as granting ownership to the caller
@ -64,11 +69,11 @@
### resources
<br>
* [proxy patterns](https://mirror.xyz/0xB38709B8198d147cc9Ff9C133838a044d78B064B/M7oTptQkBGXxox-tk9VJjL66E1V8BUF0GF79MMK4YG0)
* [how diamond upgrades work](https://dev.to/mudgen/how-diamond-upgrades-work-417j)
* [the state of smart contract updates](https://blog.openzeppelin.com/the-state-of-smart-contract-upgrades/)
* [multiple ways to update a contract](https://cryptomarketpool.com/multiple-ways-to-upgrade-a-solidity-smart-contract/)
* [Web3 Tutorial: write upgradeable smart contract (proxy) using OpenZeppelin](https://dev.to/yakult/tutorial-write-upgradeable-smart-contract-proxy-contract-with-openzeppelin-1916)
* [web3 Tutorial: write upgradeable smart contract (proxy) using OpenZeppelin](https://dev.to/yakult/tutorial-write-upgradeable-smart-contract-proxy-contract-with-openzeppelin-1916)
* [safe smart account & diamond proxies, by safe](https://safe.mirror.xyz/P83_rVQuUQJAM-SnMpWvsHlN8oLnCeSncD1txyMDqpE)