Release v0.2.0 - #8
Merged
Merged
Conversation
- Add simulate_transaction MCP tool (generic eth_call with viem-decoded reverts) - Run eth_call on every prepared tx; refuse to forward reverting txs to Ledger - Fix Compound V3 dust rendering when base token decimals() read transiently fails Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
szhygulin
added a commit
that referenced
this pull request
Apr 27, 2026
The address-book PR (#284) and the pre-existing sign_message_btc / sign_message_ltc tools together expand the signing surface beyond sign-transaction flows. SECURITY.md previously covered only the contacts blob signing trade-off (path C) and did not describe the free-form public sign-message tools at all. This commit: - Updates the contacts "EVM signing trade-off" paragraph to point at skill v4 Invariant #7 as the agent-side defense (decoration, tamper warning, sign-message-during-prepare anomaly check, post- add_contact verify cross-check), correctly attributing the contacts JSON preimage as NOT subject to character-by-character matching (its user-side defense is the recognizable domain prefix + JSON shape, per the skill's own carve-out). - Adds a new "Free-form message signing" section describing the public sign_message_btc / sign_message_ltc tools, the substitution threat, and skill v4 Invariant #8's MESSAGE-PREVIEW block as the agent-side defense (the user verifies the previewed string against the device screen character-by-character). - Notes that EVM has no equivalent public free-form signer (personal_sign is restricted to the contacts signer) and eth_signTypedData_v4 remains excluded from the WC namespace. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This was referenced Apr 27, 2026
Closed
This was referenced Apr 28, 2026
This was referenced Jul 19, 2026
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
1 participant
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
Bump to v0.2.0. Merge this, then cut a GitHub release tagged
v0.2.0to trigger the npm publish workflow.Contents (merged on main since v0.1.1):
simulate_transactionMCP tool — genericeth_callwith viem-decoded revert reasonsenrichTxrunseth_callon every prepared tx and attaches the result to the previewsend_transactionre-simulates right before signing and refuses when the tx would revertdecimals()read transiently failsTest plan
npm test— 209 tests passingnpm run build— clean typecheckv0.2.0→ verifyPublish to npmworkflow succeedsrecon-crypto-mcp@0.2.0visible on npm registry🤖 Generated with Claude Code