Skip to content

fix: UI-honesty + polish sweep (stake roadmap, drop fake buttons, resend, fee retry, spacing)#111

Merged
epicexcelsior merged 1 commit into
anonmesh:stagingfrom
epicexcelsior:night3/rampage-sweep
Jun 13, 2026
Merged

fix: UI-honesty + polish sweep (stake roadmap, drop fake buttons, resend, fee retry, spacing)#111
epicexcelsior merged 1 commit into
anonmesh:stagingfrom
epicexcelsior:night3/rampage-sweep

Conversation

@epicexcelsior

Copy link
Copy Markdown
Collaborator

What

The night3 rampage sweep — the app no longer has a button that lies, plus a few send/wallet papercuts.

  • nodes: beacon stake control now reads as a roadmap "SOON" pill instead of a broken-looking control; removed ~119 lines of unreachable stake-modal code (nothing opened it).
  • messages: dropped the fake file-save button on attachment rows (it did nothing); added resend-or-discard for a stuck outbound message.
  • send: retry the fee estimate when it falls back to unavailable; honest SPL/Token-2022 disabled-state copy (SOL-only on devnet, SPL view-only).
  • ui: tokenized the remaining hardcoded spacing in Settings/Wallet (zero-regression 1:1 value swaps).

Scope

BeaconRegistry, MessageBubble, ReviewCard, TokenPicker, MessagesScreen, SettingsScreen, WalletScreen.

Test

tsc clean · tier0 config/services clean · fake-money + lint clean.

- nodes: beacon stake control reads as a roadmap SOON pill, not broken; removed ~119 lines of unreachable stake-modal code (nothing opened it)
- messages: drop the fake file-save button on attachment rows; resend or discard a stuck outbound message
- send: retry the fee estimate when it falls back to unavailable; honest SPL/Token-2022 disabled-state copy
- ui: tokenize remaining hardcoded spacing in Settings/Wallet (1:1 value swaps)
@epicexcelsior epicexcelsior merged commit 3636905 into anonmesh:staging Jun 13, 2026
1 check 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