Skip to content

move id spec #21

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
forshtat merged 1 commit into from
Feb 3, 2025
Merged

move id spec #21

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
23 changes: 12 additions & 11 deletions EIPS/eip-5792.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,9 +62,18 @@ The wallet:
* MAY reject the request if one or more calls in the batch is expected to fail, when simulated sequentially
* MUST reject the request if it contains a `capability` (either top-level or call-level) that is not supported by the wallet and the `capability` is not explicitly marked as optional.
* Applications may mark a capability as optional by setting `optional` to `true`. See the RPC Specification section below for details.
* If provided, the wallet MUST respect the `id` field and return it in the response.
* App-provided `id`s MUST be unique per sender per app, where each "app" SHOULD be identified by their domain.
* Wallets MUST reject requests with duplicate `id`s.

If provided, the wallet MUST respect the `id` field and return it in the response.

Identifiers, whether provided by the app or generated by the wallet, MUST be a unique string up to 4096 bytes (8194 characters including leading `0x`).

App-provided `id`s MUST be unique per sender per app, where each "app" SHOULD be identified by their domain.

Wallets MUST reject requests with duplicate `id`s.

Within 24 hours from the corresponding `wallet_sendCalls`, wallets SHOULD return a call-batch status when `wallet_getCallsStatus` is called with the same `id`.

The `capabilities` response object allows the wallets to attach a capability-specific metadata to the response.


#### `wallet_sendCalls` RPC Specification
Expand Down Expand Up @@ -129,14 +138,6 @@ Note that since the `paymasterService` `capability` is marked as optional, walle

##### `wallet_sendCalls` Example Return Value

If the `id` field was provided by the app, the wallet MUST return the same value in the response.

The identifier MUST be a unique string up to 4096 bytes (8194 characters including leading `0x`).

Within 24 hours from the corresponding `wallet_sendCalls`, wallets SHOULD return a call-batch status when `wallet_getCallsStatus` is called with this value.

The `capabilities` object allows the wallets to attach a capability-specific metadata to the response.

```json
{
"id": "0x00000000000000000000000000000000000000000000000000000000000000000e670ec64341771606e55d6b4ca35a1a6b75ee3d5145a99d05921026d1527331",
Expand Down
Loading