-
Notifications
You must be signed in to change notification settings - Fork 142
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: eip-7702 support in aa-sdk/core, and sma7702 support in account-kit/smart-contracts #1287
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
How to use the Graphite Merge QueueAdd the label graphite-merge-queue to this PR to add it to the merge queue. You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. |
6797694
to
ed436d8
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.
this is looking good!
One thing missing is some client.test at a minimum (though would be great if we could extend it to installValidation.ts
and have unit tests for installValidation.test.ts
)
OOS for this PR is the naming I think, but calling it out here as @howydev and @linnall look at consolidating to the Prism naming as just looking at this PR it's clear that it'll be much better devex externally to have both a Prism account factory and Prism client factory for release
|
||
export type MAV2Account< | ||
TSigner extends SmartAccountSigner = SmartAccountSigner | ||
> = SmartContractAccountWithSigner<"MAV2Account", TSigner, "0.7.0"> & { |
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.
I think this base type should probably be generic on source
as well since source
should be unique per instance (ie. the first generic parameter in SmartContractAccountWithSigner
)
signer: TSigner; | ||
entryPoint?: EntryPointDef<"0.7.0", Chain>; | ||
signerEntity?: SignerEntity; |
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.
oh yea I remember seeing this during hackathon and thinking it odd. Why can't we merge signer
and signerEntity
?
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.
cc @howydev
account-kit/smart-contracts/src/ma-v2/account/semiModularAccount7702.ts
Outdated
Show resolved
Hide resolved
site/pages/reference/account-kit/infra/functions/alchemyGasManagerMiddleware.mdx
Outdated
Show resolved
Hide resolved
c0d52b7
to
847ab00
Compare
* feat: adds initial impl of signAuthorization * docs: adds signAuthorization documentation * fix: rename var
847ab00
to
7d20b9f
Compare
* feat: add unified ma v2 client * chore: update docs * chore: make account source unique
* feat: add unified ma v2 client * chore: make account source unique * feat: add ma v2 account to use smart contract client hook * chore: remove different type names * chore: rename mav2 to ModularAccountV2 * fix: review fix, add common type * fix: typo * fix: remove await * fix: narrow the type instead of doing non null assertion
Pull Request Checklist
yarn test
)site
folder, and guidelines for updating/adding docs can be found in the contribution guide)feat!: breaking change
)yarn lint:check
) and fix any issues? (yarn lint:write
)PR-Codex overview
This PR focuses on upgrading the
viem
package version across multiplepackage.json
files and introduces a newModularAccountV2
feature in the smart contract architecture, enhancing account management capabilities.Detailed summary
viem
version from^2.20.0
to^2.22.6
in multiplepackage.json
files.createSMAV2Account
withcreateModularAccountV2
in relevant files.ModularAccountV2
type and related functions.signAuthorization
method inLocalAccountSigner
.ModularAccountV2
.InvalidModularAccountV2Type
.createModularAccountV2
andsignAuthorization
.