-
Notifications
You must be signed in to change notification settings - Fork 542
updated description of using session keys with Engine #6474
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
Conversation
Signed-off-by: Eiman <eabdelmoneim@gmail.com>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
How to use the Graphite Merge QueueAdd either label to this PR to merge it via 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. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6474 +/- ##
=======================================
Coverage 54.80% 54.80%
=======================================
Files 875 875
Lines 54851 54851
Branches 3738 3738
=======================================
Hits 30062 30062
Misses 24695 24695
Partials 94 94
🚀 New features to boost your workflow:
|
size-limit report 📦
|
apps/portal/src/app/engine/features/account-abstraction/page.mdx
Outdated
Show resolved
Hide resolved
Co-authored-by: Jonas Daniels <jonas.daniels@outlook.com> Signed-off-by: Joaquim Verges <joaquim.verges@gmail.com>
apps/portal/src/app/engine/features/account-abstraction/page.mdx
Outdated
Show resolved
Hide resolved
Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com> Signed-off-by: Joaquim Verges <joaquim.verges@gmail.com>
Signed-off-by: AU_gdev_19 <64915515+Dargon789@users.noreply.github.com>
PR-Codex overview
This PR updates the documentation for account transactions, emphasizing the use of session keys for interacting with smart accounts. It clarifies the roles of the
x-backend-wallet-address
andx-account-address
headers.Detailed summary
Transact with an account using session keys
.x-backend-wallet-address
must be from a wallet granted signing permission via a session key.x-account-address
refers to the deployed smart account address.