Skip to content

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Mar 15, 2025
Merged

updated description of using session keys with Engine #6474

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2653254
updated description of using session keys with Engine
eabdelmoneim Mar 14, 2025
b2b63e0
Update apps/portal/src/app/engine/features/account-abstraction/page.mdx
joaquim-verges Mar 15, 2025
b8e8462
Update apps/portal/src/app/engine/features/account-abstraction/page.mdx
joaquim-verges Mar 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions apps/portal/src/app/engine/features/account-abstraction/page.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,12 +64,12 @@ Grant & revoke admins on an account with the `/contract/<chain>/<account_address

Grant & revoke sessions on an account which allow specific wallets to interact with specified contracts for a given period of time with the `/contract/<chain>/<account_address>/account/sessions` endpoints.

## Transact with an account
## Transact with an account using session keys

Make write calls with a smart account by calling a write endpoint and specify the `x-backend-wallet-address` and `x-account-address` headers.

The `x-backend-wallet-address` should be set to the engine backend wallet that is an admin over the account.
The `x-backend-wallet-address` should be set to the Engine backend wallet that has been granted signing permission by the smart account's admin through a [session key](https://portal.thirdweb.com/references/typescript/v5/erc4337/addSessionKey).

The `x-account-address` should be set to the deployed account address itself.
The `x-account-address` should be set to the deployed smart account address itself.

Write calls made using these headers will initiate a `UserOperation` sent from the specified account.