-
Notifications
You must be signed in to change notification settings - Fork 11
feat: ini v3 core #210
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
base: master
Are you sure you want to change the base?
feat: ini v3 core #210
Conversation
86d26f3
to
56c6f8a
Compare
This reverts commit 079c479.
- Removed unnecessary parameters from GetIntentConfigurationSignature, streamlining its functionality. - Cleaned up related test cases in intent_config_test.go to reflect the updated method signature. - Eliminated unused types and functions related to TrailsExecutionInfo, enhancing code clarity and maintainability.
…ionSignature for improved clarity
…configuration (#275) - Updated Factory, MainModule, MainModuleUpgradable, and Guest addresses in `network.go`. - Modified expected address in `TestIntentConfigurationAddress_RealWorldExample` in `intent_config_test.go`. - Adjusted expected wallet address and signature in `TestWalletSignMessageAndValidate` in `wallet_test.go`. - Updated contract artifacts for wallet contracts in JSON files.
…ests by removing unnecessary common.Address parameter
- Updated Factory, MainModule, MainModuleUpgradable, and Guest addresses in `network.go`. - Modified the creation code for V3 in `contracts/contracts.go` to reflect recent changes.
- Updated bytecode and deployed bytecode for various contracts including Estimator, Factory, Guest, Simulator, Stage1Module, Stage2Module, Wallet, and Passkeys. - Added new interfaces for IERC223Receiver, IERC721Receiver, and IERC1155Receiver. - Modified existing contracts to reflect changes in bytecode and structure. - Ensured consistency across all contract artifacts in the wallet-contracts-v3 directory.
- Updated Factory, MainModule, MainModuleUpgradable, Guest, and Utils addresses in `helpers.go` to reflect the latest deployment changes. - Ensured consistency with the recent updates in contract artifacts for V3.
- Introduced a new method `Approval` in the ImageHash struct to generate a digest that must be signed for subsequent ImageHash approvals. - Utilized a predefined salt for the hashing process to ensure consistency and security in the approval mechanism.
if err != nil { | ||
return common.Address{}, fmt.Errorf("sequence, AddressFromImageHash: %w", err) | ||
return common.Address{}, fmt.Errorf(`invalid creation code "%v": %w`, context.CreationCode, err) |
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.
return common.Address{}, fmt.Errorf(`invalid creation code "%v": %w`, context.CreationCode, err) | |
return common.Address{}, fmt.Errorf("invalid creation code %q: %w", context.CreationCode, err) |
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.
@shunkakinoki @attente before I go through the PR in detail, what's the high-level update on this PR? Did we stabilize the v3 contracts? Is this backward-compatible regarding v1/v2?
(+38,535 added lines makes me a bit nervous :D)
It looks like we're already using this branch in relayer -- https://github.com/0xsequence/relayer/blob/master/go.mod#L29.
And we're ready to use it in stack/api too: https://github.com/0xsequence/stack/pull/1187.
That makes me think we're close?
Do we need any more time to refactor/polish this PR? Or is this ready to go?
Co-authored-by: Shun Kakinoki <[email protected]>
…721cdd882f92521a2742d07
lib/forge-std
Outdated
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.
Are we adding a new git module into the repository? Do we need to?
Can we embed/vendor/use forge some other way?
Includes all required core
configuration
,imageHash
,signature
modules derived from sequence-core forv3
and ensures that all critical tests are passing.Steps to test
rpc
:Caveats
Some gas-estimation commands, etc. are commented out because of the scope of this PR. will follow up in a later PR. Also,
Permission
,SmartSession
,SessionManager
related modules will follow up later.