-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat!: add callee params to lsp20 & EXECUTE_RELAY_CALL permission & mapping reentrancyStatus #729
Conversation
👋 Hello ⛽📊 See Gas Benchmark report of Using UniversalProfile owned by an EOA🔀
|
execute scenarios - 👑 UP Owner |
⛽ Gas Usage |
---|---|
Transfer 1 LYX to an EOA without data | 37537 |
Transfer 1 LYX to a UP without data | 36639 |
Transfer 1 LYX to an EOA with 256 bytes of data | 42210 |
Transfer 1 LYX to a UP with 256 bytes of data | 44867 |
Transfer 0.1 LYX to 3x EOA without data | 70862 |
Transfer 0.1 LYX to 3x UP without data | 75680 |
Transfer 0.1 LYX to 3x EOA with 256 bytes of data | 84826 |
Transfer 0.1 LYX to 3x EOA with 256 bytes of data | 100357 |
🗄️ setData
scenarios
setData scenarios - 👑 UP Owner |
⛽ Gas Usage |
---|---|
Set a 20 bytes long value | 49971 |
Set a 60 bytes long value | 95293 |
Set a 160 bytes long value | 164465 |
Set a 300 bytes long value | 279700 |
Set a 600 bytes long value | 484136 |
Change the value of a data key already set | 32847 |
Remove the value of a data key already set | 27333 |
Set 2 data keys of 20 bytes long value | 78428 |
Set 2 data keys of 100 bytes long value | 260580 |
Set 3 data keys of 20 bytes long value | 105145 |
Change the value of three data keys already set of 20 bytes long value | 45445 |
Remove the value of three data keys already set | 41339 |
🗄️ Tokens
scenarios
Tokens scenarios - 👑 UP Owner |
⛽ Gas Usage |
---|---|
Minting a LSP7Token to a UP (No Delegate) from an EOA | 92016 |
Minting a LSP7Token to an EOA from an EOA | 59323 |
Transferring an LSP7Token from a UP to another UP (No Delegate) | 100102 |
Minting a LSP8Token to a UP (No Delegate) from an EOA | 158946 |
Minting a LSP8Token to an EOA from an EOA | 126253 |
Transferring an LSP8Token from a UP to another UP (No Delegate) | 148671 |
📝 Notes
- The
execute
andsetData
scenarios are executed on a fresh UniversalProfile smart contract, deployed as standard contracts (not as proxy behind a base contract implementation).
⛽📊 See Gas Benchmark report of Using UniversalProfile owned by an LSP6KeyManager
This document contains the gas usage for common interactions and scenarios when using UniversalProfile smart contracts.
🔀 execute
scenarios
👑 unrestricted controller
execute scenarios - 👑 main controller |
⛽ Gas Usage |
---|---|
transfer LYX to an EOA | 60386 |
transfer LYX to a UP | 61988 |
transfer tokens (LSP7) to an EOA (no data) | 107906 |
transfer tokens (LSP7) to a UP (no data) | 244229 |
transfer a NFT (LSP8) to a EOA (no data) | 171775 |
transfer a NFT (LSP8) to a UP (no data) | 291345 |
🛃 restricted controller
execute scenarios - 🛃 restricted controller |
⛽ Gas Usage |
---|---|
transfer some LYXes to an EOA - restricted to 1 x allowed address only (TRANSFERVALUE + 1x AllowedCalls) | 71578 |
transfers some tokens (LSP7) to an EOA - restricted to LSP7 + 2x allowed contracts only (CALL + 2x AllowedCalls) (no data) | 122597 |
transfers some tokens (LSP7) to an other UP - restricted to LSP7 + 2x allowed contracts only (CALL + 2x AllowedCalls) (no data) | 258920 |
transfers a NFT (LSP8) to an EOA - restricted to LSP8 + 2x allowed contracts only (CALL + 2x AllowedCalls) (no data) | 186431 |
transfers a NFT (LSP8) to an other UP - restricted to LSP8 + 2x allowed contracts only (CALL + 2x AllowedCalls) (no data) | 306001 |
🗄️ setData
scenarios
👑 unrestricted controller
setData scenarios - 👑 main controller |
⛽ Gas Usage |
---|---|
updates profile details (LSP3Profile metadata) | 136764 |
give permissions to a controller (AddressPermissions[] + AddressPermissions[index] + AddressPermissions:Permissions:) | 132900 |
restrict a controller to some specific ERC725Y Data Keys | 139171 |
restrict a controller to interact only with 3x specific addresses | 161875 |
remove a controller (its permissions + its address from the AddressPermissions[] array) | 67878 |
write 5x LSP12 Issued Assets | 233142 |
🛃 restricted controller
setData scenarios - 🛃 restricted controller |
⛽ Gas Usage |
---|---|
setData(bytes32,bytes) -> updates 1x data key |
102666 |
setData(bytes32[],bytes[]) -> updates 3x data keys (first x3) |
161405 |
setData(bytes32[],bytes[]) -> updates 3x data keys (middle x3) |
145559 |
setData(bytes32[],bytes[]) -> updates 3x data keys (last x3) |
170892 |
setData(bytes32[],bytes[]) -> updates 2x data keys + add 3x new controllers (including setting the array length + indexes under AddressPermissions[index]) |
250891 |
📝 Notes
- The
execute
andsetData
scenarios are executed on a fresh UniversalProfile and LSP6KeyManager smart contracts, deployed as standard contracts (not as proxy behind a base contract implementation).
6880b55
to
f5bfd09
Compare
Changes to gas cost
🧾 Summary (10% most significant diffs)
Full diff report 👇
|
…ions range Co-authored-by: Skima Harvey <skimaharvey@users.noreply.github.com>
ae51877
to
a0545ab
Compare
…contracts into feat/modify-lsp20
198361b
to
550b608
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added first round of review.
I suggest to check the difference in gas cost moving back from uint8
to uint256
inside the reentrancy mapping.
24848b6
to
d646d67
Compare
d646d67
to
685872c
Compare
…s into feat/modify-lsp20
@@ -33,6 +33,7 @@ abstract contract LSP20CallVerification { | |||
(bool success, bytes memory returnedData) = logicVerifier.call( | |||
abi.encodeWithSelector( | |||
ILSP20.lsp20VerifyCall.selector, | |||
address(this), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In order to make the LSP20 modules reusable, I would suggest to parameterize in _verifyCall
all the lsp20 functions parameter, because not in all scenarios the address(this) will be the target or msg.sender
is the one to verify permissions for.
But probably can be done in later PRs, just a note
f06483f
to
7ae6051
Compare
cf5182c
to
fc23072
Compare
fc23072
to
8e9963c
Compare
What does this PR introduce?
lsp20
interface with thecallee
paramslsp20
constant filelsp20
mocks contractsEXECUTE_RELAY_CALL
permissionreentrancyStatus
fromuint8
tomapping(address => uint8)
constant.ts
file