refactor!: replace tuple value for LSP5/10 from bytes8 -> uint128
#486
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
👋 Hello ⛽📊 See Gas Benchmark reportThis document contains the gas usage for common interactions and scenarios when using UniversalProfile smart contracts. 🔀
|
execute scenarios - 👑 main controller |
⛽ Gas Usage |
|---|---|
| transfer LYX to an EOA | 55442 |
| transfer LYX to a UP | 57044 |
| transfer tokens (LSP7) to an EOA (no data) | 101718 |
| transfer tokens (LSP7) to a UP (no data) | 239674 |
| transfer a NFT (LSP8) to a EOA (no data) | 165594 |
| transfer a NFT (LSP8) to a UP (no data) | 287320 |
🛃 restricted controller
execute scenarios - 🛃 restricted controller |
⛽ Gas Usage |
|---|---|
| transfer some LYXes to an EOA - restricted to 1 x allowed address only (TRANSFERVALUE + 1x AllowedCalls) | 62197 |
| transfers some tokens (LSP7) to an EOA - restricted to LSP7 + 2x allowed contracts only (CALL + 2x AllowedCalls) (no data) | 114132 |
| transfers some tokens (LSP7) to an other UP - restricted to LSP7 + 2x allowed contracts only (CALL + 2x AllowedCalls) (no data) | 252088 |
| transfers a NFT (LSP8) to an EOA - restricted to LSP8 + 2x allowed contracts only (CALL + 2x AllowedCalls) (no data) | 178008 |
| transfers a NFT (LSP8) to an other UP - restricted to LSP8 + 2x allowed contracts only (CALL + 2x AllowedCalls) (no data) | 299734 |
🗄️ setData scenarios
👑 unrestricted controller
setData scenarios - 👑 main controller |
⛽ Gas Usage |
|---|---|
| updates profile details (LSP3Profile metadata) | 135582 |
| give permissions to a controller (AddressPermissions[] + AddressPermissions[index] + AddressPermissions:Permissions:) | 137920 |
| restrict a controller to some specific ERC725Y Data Keys | 140072 |
| restrict a controller to interact only with 3x specific addresses | 140016 |
| remove a controller (its permissions + its address from the AddressPermissions[] array) | 73278 |
| write 5x LSP12 Issued Assets | 230434 |
🛃 restricted controller
setData scenarios - 🛃 restricted controller |
⛽ Gas Usage |
|---|---|
setData(bytes32,bytes) -> updates 1x data key |
101339 |
setData(bytes32[],bytes[]) -> updates 3x data keys (first x3) |
159345 |
setData(bytes32[],bytes[]) -> updates 3x data keys (middle x3) |
143274 |
setData(bytes32[],bytes[]) -> updates 3x data keys (last x3) |
168307 |
setData(bytes32[],bytes[]) -> updates 2x data keys + add 3x new controllers (including setting the array length + indexes under AddressPermissions[index]) |
258255 |
📝 Notes
- The
executeandsetDatascenarios are executed on a fresh UniversalProfile and LSP6KeyManager smart contracts, deployed as standard contracts (not as proxy behind a base contract implementation).
Changes to gas cost
🧾 Summary (10% most significant diffs)
Full diff report 👇
|
CJ42
added
help wanted
|
not forget to remove the custom errors that are not used anymore from the |
b00ste
approved these changes
Mar 2, 2023
This was referenced Nov 30, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR introduce?
Change the value stored under the LSP5/10 tuples from
bytes4,bytes8)to -->(bytes4,uint128)add checks to test when the value under the
LSP5ReceivedAssets[]andLSP10Vaults[]array is the max possible index and introduce custom error to handle this case.This is to prevent a
Panic(uint256)error type with error code0x11due to arithmetic overflow withmax(uint128) + 1This PR follows the changes introduced in the LSP5 and LSP10 specs.
See this PR in the LIP repository for reference: lukso-network/LIPs#173