it should probably endeavor to have most/all of the data on the transaction signing confirmation view where the user enters the password, in the same format.
it should probably endeavor to have most/all of the data on the transaction signing confirmation view where the user enters the password, in the same format.
clawbot
was assigned by sneak2026-02-28 20:27:24 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
it should probably endeavor to have most/all of the data on the transaction signing confirmation view where the user enters the password, in the same format.
PR #64 addresses this. The success-tx view now shows decoded calldata details (action name, description, token symbols, amounts, protocol info) matching the format used on the transaction signing confirmation view. Changes span approval.js (carry decoded data), txStatus.js (render decoded details), and index.html (container element).