Skip to content

[OpenRPC] Clarify wallet_prepareCalls response schema variants #1177

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

Closed
JackReacher0807 wants to merge 1 commit into from
+5 −4
Closed

[OpenRPC] Clarify wallet_prepareCalls response schema variants #1177

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
9 changes: 5 additions & 4 deletions src/openrpc/alchemy/wallet-api/wallet-api.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -760,6 +760,7 @@ methods:

result:
name: prepareCallsResponse
description: "The response type depends on your account type and request configuration. Check the `type` field to determine which variant you received."
schema:
allOf:
- anyOf:
Expand Down Expand Up @@ -1212,7 +1213,7 @@ methods:
errorMessage: "Must be a valid hex string starting with '0x'"
description: "Raw payload that can be signed if using a signer that supports signing raw bytes (such as an Alchemy Signer)"
description: "Prepared EIP-7702 Authorization"
description: "Array of prepared calls"
description: "Returned when the request requires multiple signatures — most commonly on the first transaction for an EIP-7702 account that hasn't been delegated yet. The array contains an `authorization` item (EIP-7702 delegation) and a `user-operation-v070` item, each with its own `signatureRequest`. Sign every item in the array and pass the full array to `wallet_sendPreparedCalls`. After the initial delegation, subsequent requests return a single user operation instead."
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot Apr 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Describe array variant as v060/v070, not only v070

This description says the multi-signature array always contains an authorization item and a user-operation-v070 item, but the schema for this same array explicitly allows user-operation-v060 as an item type (enum: "user-operation-v060" in the array item anyOf). That mismatch can lead integrators to hardcode v070 parsing and mishandle valid v060 responses; please make the guidance variant-agnostic or explicitly mention both versions.

Useful? React with 👍 / 👎.

- type: "object"
required:
- "type"
Expand Down Expand Up @@ -1406,7 +1407,7 @@ methods:
type: "string"
pattern: "^0x.*$"
errorMessage: "Must be a valid hex string starting with '0x'"
description: "Prepared User Operation (Entrypoint v0.6.0)"
description: "Returned for smart contract accounts (created via `wallet_requestAccount`) that use Entrypoint v0.6.0. Contains a single unsigned user operation. Sign the `signatureRequest` and pass the result to `wallet_sendPreparedCalls`."
- type: "object"
required:
- "type"
Expand Down Expand Up @@ -1602,7 +1603,7 @@ methods:
type: "string"
pattern: "^0x.*$"
errorMessage: "Must be a valid hex string starting with '0x'"
description: "Prepared User Operation (Entrypoint v0.7.0)"
description: "The most common response variant. Returned for EIP-7702 accounts that have already been delegated, or for smart contract accounts (created via `wallet_requestAccount`) that use Entrypoint v0.7.0 (the default for new accounts). Contains a single unsigned user operation. Sign the `signatureRequest` and pass the result to `wallet_sendPreparedCalls`."
- type: "object"
required:
- "type"
Expand Down Expand Up @@ -2264,7 +2265,7 @@ methods:
errorMessage: "Must be a valid hex string starting with '0x'"
description: "Raw payload that can be signed if using a signer that supports signing raw bytes (such as an Alchemy Signer)"
description: "Typed data"
description: "Prepared ERC-7597 Permit Signature Request for the paymaster"
description: "Returned when using ERC-20 gas payment and the token allowance is below the threshold specified in `paymasterService.erc20.preOpSettings.autoPermit.below`. The user must first sign the ERC-7597 Permit in `signatureRequest`, then resubmit the included `modifiedRequest` to `wallet_prepareCalls`. The second call will return a standard user operation variant with the permit signature baked in."
- type: "object"
properties:
details:
Expand Down
Loading