Repository navigation
document typed data signing on /wallet/sign - #141
Merged
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
pws-kj
approved these changes
Nov 10, 2026
1 of 4 tasks
This branch was successfully deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Note to Reviewers
This goes with the uoa-server change on
WAL-366-wallet-sign-typed-data. Merge it when that deploys, or the docs will describe behavior that isn't live yet./wallet/signused to sign only a plainmessage. It now also accepts EIP-712 typed data astransaction_data, which partners use to sign Polymarket orders and similar payloads. The Sign Data section only documentedmessage.Changes Made
uoa/api-reference/wallet-operations.mdxtransaction_dataandraw_data_hashrequest parameters, and makesmessageone of two options instead of requiredraw_data_hashresponse field to cover both message and typed-data signingTesting: How do you know it works?
Manual Testing Guide
I tested the new example:
raw_data_hashin it is the correct EIP-712 digest of its typed data.verifyTypedData, onceEIP712Domainis left out oftypes, as the page notes.The same request shape returns 200 against the uoa-server branch locally.