Skip to content

feat(offline): keep the last export across reloads - #213

Merged
mellowcroc merged 5 commits into
mainfrom
feat/persist-offline-export
Nov 5, 2026
Merged

mellowcroc merged 5 commits into
mainfrom
feat/persist-offline-export

Conversation

@mellowcroc

Copy link
Copy Markdown
Collaborator

On a proposal's page, the offline signing panel now keeps each action's exported filename and fee in sessionStorage (per network, vault and proposal hash), so step 2's command and the signed-fee check survive a reload or navigation. Start over clears it, and a broadcast removes it. The new-proposal page keeps nothing across reloads.

The new-proposal page's pending summary now comes from the last export instead of the live form.

Follow-up: the summary is matched by vault only, not by proposal hash.

🤖 Generated with Claude Code

The signing panel saves each action's exported filename and fee in
sessionStorage, keyed by network, vault and proposal, so a reload or a
visit to another page keeps step 2's command and the signed-fee check.
Start over clears it, and a broadcast stops saving it.
After a reload the form is empty, and reading it once the proposal was
broadcast could fail. The pending summary now comes from the last export
in this page load, and is left out when there is none.
A signed new proposal cannot be matched to an export, so a kept fee could
be applied to another proposal's file. Only the proposal page, keyed by
proposal hash, keeps its exports.
@mellowcroc
mellowcroc merged commit 70b7bb1 into main Nov 5, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant