feat: persist Freighter sessions#38
Conversation
|
@kaycke1337 is attempting to deploy a commit to the truthixify's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
The Freighter session persistence work in GitHub marks the PR mergeable, but a local test merge shows your branch (off pre-develop main) would silently revert the sponsored-withdrawal hooks from #29 in git fetch origin
git rebase origin/develop
git push --force-with-leaseKeep your context changes; drop the |
|
The Freighter session restore + network change listener + install detection + BroadcastChannel cross-tab sync are the right shape for issue #4. Conflicts now in just two files:
These came from #34 (payment link) and #35 (web worker) adding small touches to the same files since you opened this. git fetch origin
git rebase origin/develop
git push --force-with-leaseFor Thanks @kaycke1337. |
|
Closing as we wrap up this round of the Wraith × Drips × Stellar Wave program. Thanks for the contribution. The work and review history stays on this PR for reference. A new set of issues will go up shortly under the same If you specifically want to land the work that's already in this PR (post-wave), feel free to reopen and rebase against |
Summary
No wallet signatures or sensitive key material are cached; Stellar stealth keys are cleared on disconnect, address changes, and network changes.
Closes #4
Validation
Build completed successfully. Vite still reports existing dependency/chunk-size warnings from bundled wallet SDK dependencies.