SMA-392: Session Keys V2 #180

ankurdubey521 · 2023-12-04T06:28:04Z

Introduction

Introduces a new SessionKeyManagerHybrid Module to support Session Keys infrastructure with the following enhancements:

Stores the SessionData(svm, validUntil, validAfter, data) on-chain. This removes any dependency on any off-chain DA solution such as Merkle tree storage, removing the need for synchronization between DApps using Session Keys infrastructure.
Once a Session has been enabled, allows referencing the Session simply by its bytes32 sessionDigest for subsequent session transactions, resulting in massive calldata savings for long-running sessions. This results in significantly cheaper transactions on L2s (amortized costs).
Optionally allows for the Session Enable Operation to be batched with the first Session Usage Operation, allowing for offline session creation, decreasing the cost and latency/first time to interact metric.
Improves transparency for which sessions are enabled since all enabled sessions are stored on-chain. It also opens up the possibility of Security Policies integration in the future.
Natively supports both execute and executeBatch flows, eliminating the need to separately integrate the Batched Session Router to support sessions while batching.
Natively supports the creation of multiple (potentially multi-chain) Sessions with a Single Signature, eliminating the need for separately integrating the MultiChain Validator Module for achieving the same.

Other notes:

Compatible with existing SVMs in both execute and executeBatch modes.
Densely packed signatures using abi.encodePacked to reduce calldata size to further the gas savings on L2s.

Usage

Definitions

struct SessionData {
    uint48 validUntil;
    uint48 validAfter;
    address sessionValidationModule;
    bytes sessionKeyData;
}

MODE_SESSION_KEY_PRE_ENABLED = 0
MODE_SESSION_KEY_ENABLE_AND_USE = 1

Enabling a Session Manually

/**
 * @dev creates a session for a smart account
 * @param sessionData session data
 */
function enableSession(SessionData calldata sessionData) external;

Disabling a Session Manually

Normally a session will expire automatically based on (validUntil, validAfter), however an option to disable the session manually is available.

/**
 * @notice Explicitly disable a session. Can be useful in situations where a session
 *         needs to be disabled before it expires.
 * @param _sessionDigest digest of session key data
 */
function disableSession(bytes32 _sessionDigest) external;

Single Execute

Enable And Use Session

Prepare a User Operation where op.calldata[0:4] is SmartAccount.execute.selector or SmartAccount.execute_ncC.selector.

Prepare one or more SessionData as described above. Calculate

Prepare bytes sessionEnableData as

 * Offset (in bytes)    | Length (in bytes) | Contents
 * 0x0                  | 0x1               | No of session keys enabled
 * 0x1                  | 0x8 x count       | Chain IDs
 * 0x1 + 0x8 x count    | 0x20 x count      | Session Data Hash

Sign sessionEnableData using EIP1271 to produce sessionEnableSignature

Prepare moduleSignature as

 * Offset (in bytes)    | Length (in bytes) | Contents
 * 0x0                  | 0x1               | MODE_SESSION_KEY_ENABLE_AND_USE
 * 0x1                  | 0x1               | Index of Session Key in Session Enable Data
 * 0x2                  | 0x6               | Valid Until
 * 0x8                  | 0x6               | Valid After
 * 0xe                  | 0x14              | Session Validation Module Address
 * 0x22                 | --                | abi.encode(sessionKeyData, sessionEnableData,
 *                      |                   |   sessionEnableSignature, sessionKeySignature)

Use Pre-Enabled Session

Prepare a User Operation where op.calldata[0:4] is SmartAccount.execute.selector or SmartAccount.execute_ncC.selector.

No sessionEnableData is needed in this case. Simply prepare moduleSignature as

 * Session Data Pre Enabled Signature Layout
 * Offset (in bytes)    | Length (in bytes) | Contents
 * 0x0                  | 0x1               | MODE_SESSION_KEY_PRE_ENABLED
 * 0x1                  | --                | abi.encode(bytes32 sessionDataDigest, sessionKeySignature)

Batch Execute

Prepare a User Operation where op.calldata[0:4] is SmartAccount.executeBatch.selector or SmartAccount.executeBatch_y6U.selector.

Here, for each item of the batch independently follow either the enable-and-use or the pre-enabled flow.
The global moduleSignature structure is as follows:

abi.encode(
	bytes[] sessionEnableDataList, 
	bytes[] sessionEnableSignatureList, 
	bytes[] sessionInfo, 
	bytes sessionKeySignature
)

First some invariants:

sessionInfo.length == executeBatch-operations.length
sessionEnableDataList.length == sessionEnableSignatureList.length >= 0

Each item in sessionInfo corresponds to an operation in the batch.
If any session wants to leverage the enable-and-use flow, it can refer to one of the enableData-signature pair. If no sessions use these flows, the first two lists are empty.

Session Enable and Signature List

Follows the same structure as described in the Single Execute Section. This is effectively a 2D array of (sessionDataHash, chainID). Assuming that batch operations A, B and C reference sessions SA, SB and SC, assuming the following Session Enable Data:

sessionEnableDataList = [
	SED1: [ (KECCAK(SA), 137), (KECCAK(SB), 137) ] ,
	SED2: [ (KECCAK(SC), 137)] 
]

sessionInfo[0] can refer to it's corresponding SED entry as [0, 0]
sessionInfo[1] can refer to it's corresponding SED entry as [0, 1]
sessionInfo[2] can refer to it's corresponding SED entry as [1, 0]

Session Info Structure - Enable And Use

* Offset (in bytes)    | Length (in bytes) | Contents
* 0x0                  | 0x1               | MODE_SESSION_KEY_ENABLE_AND_USE
* 0x1                  | 0x1               | Index of Session Enable Data in Session Enable Data List
* 0x2                  | 0x1               | Index of Session Key in Session Enable Data
* 0x3                  | 0x6               | Valid Until
* 0x9                  | 0x6               | Valid After
* 0xf                  | 0x14              | Session Validation Module Address
* 0x23                 | --                | abi.encode(sessionKeyData, callSpecificData)

Session Info Structure - Use Pre-Enabled Session

 * Session Data Pre Enabled Signature Layout
 * Offset (in bytes)    | Length (in bytes) | Contents
 * 0x0                  | 0x1               | MODE_SESSION_KEY_PRE_ENABLED
 * 0x1                  | 0x20              | bytes32 sessionDataDigest
 * 0x21                 | ---               | abi.encode(callSpecificData)

Change Type

Checklist

My code follows this project's style guidelines
I've reviewed my own code
I've added comments for any hard-to-understand areas
I've updated the documentation if necessary
My changes generate no new warnings
I've added tests that prove my fix is effective or my feature works
All unit tests pass locally with my changes
Any dependent changes have been merged and published

linear · 2023-12-04T06:28:06Z

SMA-392 Session Keys V2 - Onchain

…eyManagerBase

…ched Execution

livingrockrises · 2024-01-02T13:56:40Z

resolve conflicts

ankurdubey521 · 2024-01-03T00:41:12Z

PR is ready to be merged. I think we should merge this post the "all-encompassing audit"

AmanRaj1608 · 2024-01-03T10:09:42Z

...racts/smart-account/interfaces/modules/SessionKeyManagers/ISessionKeyManagerModuleHybrid.sol

+     *         needs to be disabled before it expires.
+     * @param _sessionDigest digest of session key data
+     */
+    function disableSession(bytes32 _sessionDigest) external;


Do you think adding a batch disableSession would be helpful. The users can definitely call execute batch multiple times to disableSession but having a method might be useful.

AmanRaj1608

Great work! LGTM

contracts/smart-account/modules/SessionKeyManagers/SessionKeyManagerHybrid.sol

Aboudjem · 2024-01-03T02:32:29Z

contracts/smart-account/modules/SessionKeyManagers/SessionKeyManagerHybrid.sol

+            sessionKeyIndex := shr(248, calldataload(offset))
+            offset := add(offset, 0x1)
+
+            validUntil := shr(208, calldataload(offset))
+            offset := add(offset, 0x6)
+
+            validAfter := shr(208, calldataload(offset))
+            offset := add(offset, 0x6)
+
+            sessionValidationModule := shr(96, calldataload(offset))
+            offset := add(offset, 0x14)


Suggested change

sessionKeyIndex := shr(248, calldataload(offset))

offset := add(offset, 0x1)

validUntil := shr(208, calldataload(offset))

offset := add(offset, 0x6)

validAfter := shr(208, calldataload(offset))

offset := add(offset, 0x6)

sessionValidationModule := shr(96, calldataload(offset))

offset := add(offset, 0x14)

// Extract the session key index

sessionKeyIndex := shr(248, calldataload(offset))

offset := add(offset, 0x1)

// Extract the 'valid until' timestamp

validUntil := shr(208, calldataload(offset))

offset := add(offset, 0x6)

// Extract the 'valid after' timestamp

validAfter := shr(208, calldataload(offset))

offset := add(offset, 0x6)

// Extract the session validation module address

sessionValidationModule := shr(96, calldataload(offset))

offset := add(offset, 0x14)

In general, I feel that the code is pretty self-explanatory and is self-documenting here.

However, given that I wrote it and am probably biased, I've added the comments in all parse* functions.

contracts/smart-account/modules/SessionKeyManagers/SessionKeyManagerHybrid.sol

Aboudjem · 2024-01-03T12:04:24Z

contracts/smart-account/modules/SessionKeyManagers/SessionKeyManagerHybrid.sol

+        // Also find the earliest validUntil and latest validAfter
+        uint48 earliestValidUntil = type(uint48).max;
+        uint48 latestValidAfter;
+        for (uint256 i = 0; i < length; ++i) {


uncheck ++i

https://soliditylang.org/blog/2023/10/25/solidity-0.8.22-release-announcement/
This is automatically done by the compiler post 0.8.22

contracts/smart-account/modules/SessionKeyManagers/SessionKeyManagerHybrid.sol

.vscode/settings.json

hardhat.config.ts

test/foundry/base/utils/EntrypointUtils.sol

...racts/smart-account/interfaces/modules/SessionKeyManagers/ISessionKeyManagerModuleHybrid.sol

tomarsachin2271 · 2024-01-05T07:20:40Z

...racts/smart-account/interfaces/modules/SessionKeyManagers/ISessionKeyManagerModuleHybrid.sol

+    /**
+     * @notice Returns session data for a given session digest and smart account
+     * @param _sessionDataDigest digest of session key data
+     * @param _sa smart account for which session key is being disabled


As per the description.. "smart account for which session key is being disabled"
Is this method specially called for disabling a session for smart account??

The description was incorrect, fixed it

tomarsachin2271 · 2024-01-05T07:50:39Z

contracts/smart-account/modules/SessionKeyManagers/SessionKeyManagerHybrid.sol

+            sessionDataDigest_ := calldataload(offset)
+            offset := add(offset, 0x20)
+
+            let dataPointer := add(baseOffset, calldataload(offset))


Didn't understand this line...

isn't calldataload(offset) returns the 32 bytes starting from sessionKeySignature here?

So first 32 bytes of session key signature is some offset value?

Consider the abi encoding of (bytes32 A, bytes B).

The length of A is fixed (32), therefore it is included as it is in the encoded byte array.
However, the length of B is "dynamic" in that it cannot be known at compile time, and can only be determined at runtime when the actual value of B is presented for encoding.

Therefore, it is not directly included in the encoding. Instead, the encoded bytes array includes a placeholder pointing to to B. Once all the parameters have either been encoded in place (fixed size) or their placeholders have been included, the variable length parameters are then appended to the end of the bytes array as <length><actual data>.

Therefore the actual encoding is
<32 bytes - A> <32 bytes - pointer to B> <32 bytes - len(B)> <len(B) bytes - B>
This placeholder/pointer is simply the offset at which B and its length are stored(by appending) in the final encoded bytes array. In the code, dataPointer represents this pointer.

The full specification of this encoding can be found here: https://docs.soliditylang.org/en/develop/abi-spec.html.

tomarsachin2271 · 2024-01-05T08:17:33Z

test/bundler-integration/module/HybridSessionKeyManager.Module.specs.ts

+
+      await environment.sendUserOperation(transferUserOp, entryPoint.address);
+
+      expect(await mockToken.balanceOf(charlie.address)).to.equal(


Should expect the event emitted for SessionCreated
After the transaction, query the contract to see if the session is actually enabled and cross check the count of sessions that are enabled.

The bundler integration tests only check for compatibility with the bundler, and similar positive scenario tests are implemented in foundry that verify all the conditions you've mentioned.
Please refer to

https://github.com/bcnmy/scw-contracts/blob/feat/sma-392-session-keys-v2/test/foundry/module/SessionKeyManager/SessionKeyManagerHybrid.BatchCall.t.sol#L87

https://github.com/bcnmy/scw-contracts/blob/feat/sma-392-session-keys-v2/test/foundry/module/SessionKeyManager/SessionKeyManagerHybrid.SingleCall.t.sol#L114

and other positive scenario tests in foundry, where event emissions and state checks have been thoroughly tested. You'll also find tests for enabling and disabling sessions there.

In general, I've implemented all positive and negative tests in foundry, and have only kept basic positive flow tests in bunder/hardhat to ensure bundler compatibility.

The full list of tests implemented in foundry:

Running 18 tests for test/foundry/module/SessionKeyManager/SessionKeyManagerHybrid.SingleCall.t.sol:SessionKeyManagerHybridSingleCallTest [PASS] testDisableSession() (gas: 208224) [PASS] testDisableSessions() (gas: 209324) [PASS] testEnableAndUseSessionInSameTransaction() (gas: 206419) [PASS] testEnableAndUseSessionMultiSessionEnable() (gas: 267433) [PASS] testEnableAndUseSessionPostSessionEnable() (gas: 243050) [PASS] testEnableSession() (gas: 165474) [PASS] testEnableSessions() (gas: 236559) [PASS] testExplicitEnableAndUseSessionDifferentOp() (gas: 216171) [PASS] testShouldNotSupportERC1271SignatureValidation(uint256) (runs: 256, μ: 12261, ~: 12261) [PASS] testShouldNotSupportERC1271SignatureValidationUnsafe(uint256) (runs: 256, μ: 12195, ~: 12195) [PASS] testShouldNotValidateTransactionFromNonEnabledSession() (gas: 170546) [PASS] testShouldNotValidateTransactionFromNonEnabledSessionWithPostCacheFlow() (gas: 119975) [PASS] testShouldNotValidateTransactionSignedFromInvalidSessionSigner() (gas: 210961) [PASS] testShouldNotValidateTransactionSignedFromInvalidSessionSignerPostSessionEnable() (gas: 270079) [PASS] testShouldNotValidateTransactionWithInvalidChainId() (gas: 153673) [PASS] testShouldNotValidateTransactionWithInvalidSessionIndex() (gas: 153168) [PASS] testShouldParseEnableSessionSignatureCorrectly(uint8,uint8,uint48,uint48,address,bytes,bytes,bytes,bytes) (runs: 256, μ: 61973, ~: 51556) [PASS] testShouldParsePreEnabledSignatureCorrectly(uint8,bytes32,bytes) (runs: 256, μ: 21042, ~: 18046) Test result: ok. 18 passed; 0 failed; 0 skipped; finished in 3.74s Running 21 tests for test/foundry/module/SessionKeyManager/SessionKeyManagerHybrid.BatchCall.t.sol:SessionKeyManagerHybridBatchCallTest [PASS] testEnableAndUseSessionSingleBatchItem() (gas: 227729) [PASS] testEnableAndUseSessionTwoBatchItems() (gas: 332589) [PASS] testShouldNotAllowInvalidChainIdInSessionEnableData() (gas: 166563) [PASS] testShouldNotAllowInvalidSessionEnableDataIndex() (gas: 166247) [PASS] testShouldNotAllowInvalidSessionEnableKeyIndex() (gas: 166860) [PASS] testShouldNotAllowSessionEnableWithEnableDataListLengthMismatch() (gas: 147112) [PASS] testShouldNotAllowSessionEnableWithInvalidSessionEnableSignature() (gas: 161367) [PASS] testShouldNotAllowSessionExecutionIfSVMReturnsDifferentSigner() (gas: 216672) [PASS] testShouldNotAllowSessionInfosLengthAndBatchItemsLengthMismatch() (gas: 168124) [PASS] testShouldNotAllowSessionWithDifferentDigestToBeExecuted() (gas: 169453) [PASS] testShouldNotAllowUsageOfExpiredSession() (gas: 298389) [PASS] testShouldNotAllowUsageOfNonEnabledSessionsInPreEnabledFlow() (gas: 132143) [PASS] testShouldNotAllowUsageOfSessionsNotValidYet() (gas: 298728) [PASS] testShouldNotSupportERC1271SignatureValidation(uint256) (runs: 256, μ: 12287, ~: 12287) [PASS] testShouldNotSupportERC1271SignatureValidationUnsafe(uint256) (runs: 256, μ: 12111, ~: 12111) [PASS] testShouldParseBatchCallDataCorrectly(address[],uint256[],bytes[]) (runs: 256, μ: 4337881, ~: 4337168) [PASS] testShouldParseSessionDataPreEnableSignatureBatchCall(uint8,bytes32,bytes) (runs: 256, μ: 20731, ~: 17927) [PASS] testShouldParseSessionEnableSignatureCorrectly(uint8,uint8,uint8,uint48,uint48,address,bytes,bytes) (runs: 256, μ: 35498, ~: 29535) [PASS] testShouldParseValidateUserBatchSignature(bytes[],bytes[],bytes[],bytes) (runs: 256, μ: 13238584, ~: 13069998) [PASS] testUseSessionTwoBatchItemsOneFreshAndOtherPostEnable() (gas: 389251) [PASS] testUseSessionTwoBatchItemsPostEnable() (gas: 387304) Test result: ok. 21 passed; 0 failed; 0 skipped; finished in 10.71s

tomarsachin2271 · 2024-01-05T08:21:22Z

test/bundler-integration/module/HybridSessionKeyManager.Module.specs.ts

+      );
+    });
+
+    it("Should process signed user operation from Session when session is pre-enabled", async () => {


Add negative test cases as well, that will test expired sessions should not allow executing any userOp signed by session key.

Invalid session key data format, should be reverted.

Add test cases for disableSession and disableSessions

All negative tests are implemented in foundry, please refer to tests starting from

https://github.com/bcnmy/scw-contracts/blob/feat/sma-392-session-keys-v2/test/foundry/module/SessionKeyManager/SessionKeyManagerHybrid.BatchCall.t.sol#L526

https://github.com/bcnmy/scw-contracts/blob/feat/sma-392-session-keys-v2/test/foundry/module/SessionKeyManager/SessionKeyManagerHybrid.SingleCall.t.sol#L563

tomarsachin2271 · 2024-01-05T09:37:42Z

Looks great 🚀 LGTM

livingrockrises · 2024-01-05T09:46:46Z

Should we merge this or Not?

ankurdubey521 · 2024-01-05T09:52:35Z

@Aboudjem please let us know when this can be safely merged.

Aboudjem · 2024-01-05T16:11:32Z

@Aboudjem please let us know when this can be safely merged.

Sure ! let's discuss it next week

ankurdubey521 · 2024-01-31T10:22:30Z

@Aboudjem Any update on this?

Aboudjem · 2024-01-31T13:47:36Z

@Aboudjem Any update on this?

I thought we had agreed to proceed with the merging after completing the audits, if I'm not wrong

github-actions · 2024-03-02T00:17:19Z

This PR has been inactive for 30 days. If it's waiting for a review, please reach out to the team. Otherwise, please update the PR or it will be closed due to inactivity.

ankurdubey521 · 2024-03-02T00:36:42Z

@Aboudjem Any update on this?

I thought we had agreed to proceed with the merging after completing the audits, if I'm not wrong

We have completed 1 audit for the module, I believe it can be safely merged now.

ankurdubey521 added 5 commits November 20, 2023 07:13

feat: Stateless Session Key Manager Module

5cdea88

feat: Statefull Session Key Manager Module + Bundler Compliance

f4b3772

feat: Hybrid Validation

ced1fc2

chore: add more console.logs

b6574b8

fix: dependencies and wallet utils

30da23c

ankurdubey521 added 23 commits December 4, 2023 12:03

chore: remove session comparision tests

5cc20b1

chore: move common stateful session functionality to StatefulSessionK…

6acc584

…eyManagerBase

Merge branch 'develop' into feat/sma-392-session-keys-v2

2e71194

test: Foundry Tests for Stateful Session Key Manager

6a84e57

test: Basic Foundry Tests for Hybrid Session Key Manager

089e7cb

test: Foundry Tests for Hybrid Session Key Manager

d6451d1

feat: SessionKeyManagerHybrid Gas Optimisation

edf5d3e

feat: SessionKeyManagerStateful Gas Optimisation

9166014

feat: Hybrid Session Key Manager Gas Optimisations + Refactor for Bat…

a75fa43

…ched Execution

feat: Hybrid Session Key Manager - Batched Execution

57ceed6

fix: Hybrid SKM: add callSpecificData

0575f17

test: Hyrbid SKM Single Call Parsers

8f5ea61

test: Stateful SKM Single Call Parsers

6ca3e6a

test: Hybrid SKM Batch Call Parsers

2dca0d4

test: Hybrid SKM Batch Call - Single Item and Tests Refactor

a5f0d22

test: Hybrid SKM Batch Call - All Positive Tests

3e2eb30

feat: Merge Stateful Session Key Manager into Hybrid Session Key Manager

08e5aff

chore: Refactor Test Utils

eb6f21a

test: Hybrid SKM Batch Call - Negative Cases

8d9db63

fix: Restore Session Key Manager Module and Batched Session Router

878d38e

fix: Bundler Integration Tests

5f3cfd5

chore: Bump Bundler version to accountabstraction/bundler:0.6.2

c5fd4ad

test: Bundler Integration Tests for Hybrid SKM in Single Mode

058f8dd

ankurdubey521 self-assigned this Dec 25, 2023

ankurdubey521 force-pushed the feat/sma-392-session-keys-v2 branch from baf58f7 to 58e7847 Compare January 3, 2024 00:40

ankurdubey521 force-pushed the feat/sma-392-session-keys-v2 branch from 58e7847 to 1755bb0 Compare January 3, 2024 00:41

Merge branch 'develop' into feat/sma-392-session-keys-v2

c5ca9de

ankurdubey521 force-pushed the feat/sma-392-session-keys-v2 branch from 1755bb0 to c5ca9de Compare January 3, 2024 00:47

AmanRaj1608 reviewed Jan 3, 2024

View reviewed changes

AmanRaj1608 approved these changes Jan 3, 2024

View reviewed changes

Aboudjem suggested changes Jan 3, 2024

View reviewed changes

ankurdubey521 added 2 commits January 5, 2024 10:59

fix: Feedback #180 by @AmanRaj1608

11cf3ad

fix: Feedback #180 by @Aboudjem

ac206f4

ankurdubey521 requested a review from Aboudjem January 5, 2024 05:44

feat: Solidity ^0.8.23 for SessionKeyManagerHybrid

3041d8f

tomarsachin2271 reviewed Jan 5, 2024

View reviewed changes

fix: Feedback #180 by @tomarsachin2271

f365630

tomarsachin2271 approved these changes Jan 5, 2024

View reviewed changes

Aboudjem approved these changes Jan 8, 2024

View reviewed changes

github-actions bot added the inactive-pr label Mar 2, 2024

Merge branch 'develop' into feat/sma-392-session-keys-v2

c3fe846

ankurdubey521 force-pushed the feat/sma-392-session-keys-v2 branch from 82abd25 to c3fe846 Compare March 2, 2024 00:39

feat: Kawach Audit for SKMv2

50ccc11

ankurdubey521 merged commit 3362262 into develop Mar 2, 2024
2 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

SMA-392: Session Keys V2 #180

SMA-392: Session Keys V2 #180

ankurdubey521 commented Dec 4, 2023 •

edited

Loading

linear bot commented Dec 4, 2023

livingrockrises commented Jan 2, 2024

ankurdubey521 commented Jan 3, 2024

AmanRaj1608 Jan 3, 2024

ankurdubey521 Jan 5, 2024

AmanRaj1608 left a comment

Aboudjem Jan 3, 2024

ankurdubey521 Jan 5, 2024

Aboudjem Jan 3, 2024

ankurdubey521 Jan 5, 2024

tomarsachin2271 Jan 5, 2024

ankurdubey521 Jan 5, 2024

tomarsachin2271 Jan 5, 2024

ankurdubey521 Jan 5, 2024 •

edited

Loading

tomarsachin2271 Jan 5, 2024

ankurdubey521 Jan 5, 2024

ankurdubey521 Jan 5, 2024

tomarsachin2271 Jan 5, 2024

ankurdubey521 Jan 5, 2024

tomarsachin2271 commented Jan 5, 2024

livingrockrises commented Jan 5, 2024

ankurdubey521 commented Jan 5, 2024

Aboudjem commented Jan 5, 2024

ankurdubey521 commented Jan 31, 2024

Aboudjem commented Jan 31, 2024

github-actions bot commented Mar 2, 2024

ankurdubey521 commented Mar 2, 2024


		await environment.sendUserOperation(transferUserOp, entryPoint.address);

		expect(await mockToken.balanceOf(charlie.address)).to.equal(

SMA-392: Session Keys V2 #180

SMA-392: Session Keys V2 #180

Conversation

ankurdubey521 commented Dec 4, 2023 • edited Loading

Introduction

Usage

Definitions

Enabling a Session Manually

Disabling a Session Manually

Single Execute

Enable And Use Session

Use Pre-Enabled Session

Batch Execute

Session Enable and Signature List

Session Info Structure - Enable And Use

Session Info Structure - Use Pre-Enabled Session

Change Type

Checklist

linear bot commented Dec 4, 2023

livingrockrises commented Jan 2, 2024

ankurdubey521 commented Jan 3, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

AmanRaj1608 left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

ankurdubey521 Jan 5, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tomarsachin2271 commented Jan 5, 2024

livingrockrises commented Jan 5, 2024

ankurdubey521 commented Jan 5, 2024

Aboudjem commented Jan 5, 2024

ankurdubey521 commented Jan 31, 2024

Aboudjem commented Jan 31, 2024

github-actions bot commented Mar 2, 2024

ankurdubey521 commented Mar 2, 2024

ankurdubey521 commented Dec 4, 2023 •

edited

Loading

ankurdubey521 Jan 5, 2024 •

edited

Loading