Update session key documentation #88
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| - Create a normal transaction that transfers some ETH to the SK. The amount depends on how many "moves" the user is prepared to prepay for. | ||
| - Ask the user to sign this transaction with their normal wallet, and submit it to the network using the library of your choice. | ||
| - Once the receipt is received, call ``sessionkeys_Activate``. | ||
| - Call the RPC `eth_getStorageAt` with address `0x0000000000000000000000000000000000000003` (CreateSessionKeyCQMethod) - this will return the hex-encoded address of the SK. |
There was a problem hiding this comment.
I'm not sure "CreateSessionKeyCQMethod" means anything for an external dev
| - Create a normal transaction that transfers some ETH to the SK. The amount depends on how many "moves" the user is prepared to prepay for. | ||
| - Ask the user to sign this transaction with their normal wallet, and submit it to the network using the library of your choice. | ||
| - Once the receipt is received, call ``sessionkeys_Activate``. | ||
| - Call the RPC `eth_getStorageAt` with address `0x0000000000000000000000000000000000000003` (CreateSessionKeyCQMethod) - this will return the hex-encoded address of the SK. |
There was a problem hiding this comment.
mention that the dapp must store the sk address
|
|
||
| When a game ends, you have to move the remaining funds back to the main address and deactivate the key. | ||
| - Create a transaction that moves the funds back from the SK to the main address. Submit it unsigned using the SendUnsignedTxCQMethod, because the funds are controlled by the SK. | ||
| - Call `eth_getStorageAt` with address `0x0000000000000000000000000000000000000004` (DeleteSessionKeyCQMethod) to permanently remove the session key. |
There was a problem hiding this comment.
same for all these DeleteSessionKeyCQMethod and the others.
|
|
||
| ### Key Benefits | ||
|
|
||
| - **No Activation/Deactivation**: Session keys are implicitly active when created and remain active until deleted |
There was a problem hiding this comment.
this doesn't mean anything for a user who reads this for the first time
| - **Multiple Session Keys**: Users can have up to 100 session keys (one per dApp) | ||
| - **Simplified API**: Uses `eth_getStorageAt` with custom addresses instead of separate RPC methods | ||
| - **Secure Management**: Session keys are managed by TEEs, eliminating the risk of losing private keys | ||
| - **Base64 Transaction Encoding**: Unsigned transactions must be base64 encoded when sent via SendUnsignedTxCQMethod |
There was a problem hiding this comment.
not sure how these are benefits.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.