Repository navigation
require transaction_data in Express sign/data docs and recipes - #136
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
Oct 22, 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.
Summary
Express
sign/datanow rejects an ETHraw_data_hashthat isn't sent with matchingtransaction_data(400 INVALID_SIGNING_PARAMS). Fridge recomputes the hash from it and screens the content for sanctions. Every EVM example here sent a bare hash, so this updates them before enforcement ships. Part of WAL-165Changes
express-api/wallet-operations.mdx:transaction_datais required for ETH, with the fields and hash for eachmethod, a workingeth_signexample and the 400 behavior.express-api/data-preparation/evm.mdx: every signing example sendstransaction_data; adds aneth_signexample and a note on unsupported transaction types (access list, blobs, authorization list).express-api/policy/transaction-data.mdx: no longer says the field is only required under policy evaluation; corrects the method list and documentsaddressfor 7702.Testing
chainIdand no domain) through fridge's validator: all accepted under enforcement, with viem 2.21.55 and 2.55.19.mint broken-links: no new broken links (the 18 existing ones are in unrelated embedded-wallet pages).Not changed