for swaps, the 'success-tx' view should have a lot more data on it. #63

Closed
opened 2026-02-28 20:27:24 +01:00 by sneak · 1 comment
Owner

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 sneak 2026-02-28 20:27:24 +01:00
Collaborator

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).

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).
sneak closed this issue 2026-02-28 20:35:40 +01:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sneak/AutistMask#63
No description provided.