-
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
refactor: mark relay call signature as used #670
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 | 42198 |
Transfer 1 LYX to a UP with 256 bytes of data | 44738 |
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 | 100006 |
🗄️ 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 | 164453 |
Set a 300 bytes long value | 279700 |
Set a 600 bytes long value | 484124 |
Change the value of a data key already set | 32859 |
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 | 260592 |
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 | 91241 |
Minting a LSP7Token to an EOA from an EOA | 59206 |
Transferring an LSP7Token from a UP to another UP (No Delegate) | 98689 |
Minting a LSP8Token to a UP (No Delegate) from an EOA | 158192 |
Minting a LSP8Token to an EOA from an EOA | 126157 |
Transferring an LSP8Token from a UP to another UP (No Delegate) | 147236 |
📝 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 | 60395 |
transfer LYX to a UP | 61997 |
transfer tokens (LSP7) to an EOA (no data) | 107118 |
transfer tokens (LSP7) to a UP (no data) | 242646 |
transfer a NFT (LSP8) to a EOA (no data) | 170965 |
transfer a NFT (LSP8) to a UP (no data) | 289821 |
🛃 restricted controller
execute scenarios - 🛃 restricted controller |
⛽ Gas Usage |
---|---|
transfer some LYXes to an EOA - restricted to 1 x allowed address only (TRANSFERVALUE + 1x AllowedCalls) | 72604 |
transfers some tokens (LSP7) to an EOA - restricted to LSP7 + 2x allowed contracts only (CALL + 2x AllowedCalls) (no data) | 122897 |
transfers some tokens (LSP7) to an other UP - restricted to LSP7 + 2x allowed contracts only (CALL + 2x AllowedCalls) (no data) | 258425 |
transfers a NFT (LSP8) to an EOA - restricted to LSP8 + 2x allowed contracts only (CALL + 2x AllowedCalls) (no data) | 186732 |
transfers a NFT (LSP8) to an other UP - restricted to LSP8 + 2x allowed contracts only (CALL + 2x AllowedCalls) (no data) | 305588 |
🗄️ setData
scenarios
👑 unrestricted controller
setData scenarios - 👑 main controller |
⛽ Gas Usage |
---|---|
updates profile details (LSP3Profile metadata) | 136831 |
give permissions to a controller (AddressPermissions[] + AddressPermissions[index] + AddressPermissions:Permissions:) | 132862 |
restrict a controller to some specific ERC725Y Data Keys | 139238 |
restrict a controller to interact only with 3x specific addresses | 161942 |
remove a controller (its permissions + its address from the AddressPermissions[] array) | 67827 |
write 5x LSP12 Issued Assets | 233209 |
🛃 restricted controller
setData scenarios - 🛃 restricted controller |
⛽ Gas Usage |
---|---|
setData(bytes32,bytes) -> updates 1x data key |
102582 |
setData(bytes32[],bytes[]) -> updates 3x data keys (first x3) |
161396 |
setData(bytes32[],bytes[]) -> updates 3x data keys (middle x3) |
145475 |
setData(bytes32[],bytes[]) -> updates 3x data keys (last x3) |
170708 |
setData(bytes32[],bytes[]) -> updates 2x data keys + add 3x new controllers (including setting the array length + indexes under AddressPermissions[index]) |
249828 |
📝 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).
Changes to gas cost
🧾 Summary (10% most significant diffs)
Full diff report 👇
|
1dc2dc3
to
413ca43
Compare
Few things I had in mind:
|
1b5c793
to
650b25d
Compare
LGTM.
|
a9daf90
to
fb9c199
Compare
I suggest we put this PR as draft. (Looks like the gas diff for Foundry does not show this) |
I will close the PR as hash collisions need more investigation. |
What does this PR introduce?
♻️ Refactor
After investigating the way signatures are stored in
Safe.sol
, it turns out that they have asignMessage(...)
function which marks a signature as approved signature. That further is checked inisValidSignature(...)
which requires that a signature to be approved.With this said, they don't quite have the same purpose as in our case. We need to store signatures in order to not allow double use while they store signatures that are approved. In our case we cannot use
signMessage(...)
as it will block gas-less execution and will require for someone to have gas in order to approve a signature. We need an approach that does not break the ux behind relay calls.I took the liberty to implement it in the following way:
signedMessages
mapping.signedMessages
mapping.That would 100% not allow any signature to be used twice.
PR Checklist
npm run lint
&&npm run lint:solidity
(solhint)npm run format
(prettier)npm run build
npm run test