Feat/simplex UI redesign - #1190
Merged
Merged
Conversation
…nto feat/simplex-ui-redesign # Conflicts: # sdk/packages/simplex/docs/ai/ChangeLog.md # sdk/packages/simplex/docs/ai/Decisions.md # sdk/packages/simplex/docs/ai/Flow.md
Member
|
We have simplex paymaster on bnb, this warning is not necessary |
Member
|
After configuration let's show the by and sell price on this list item, no need to show the maxOrderCap |
Member
|
Let this be uncapped by default |
Member
|
Add USDT/CNGN to this list by default also |
Member
|
Show current buy and sell price on this list item |
Member
|
Button is not aligned |
Member
|
Vault configuration currency should be in the token being configured not USD |
Member
|
Increase font size for wallet addresses on this panel |
Member
|
Show available balance of the selected token |
Member
|
Really great work |
Contributor
Author
|
@Wizdave97 Comments have been addressed |
Member
|
Editing and saving vaults does not work sometimes |
Member
|
this is wrong, filler does not need to be restarted |
Member
|
There's no notification when vaults are saved |
Member
|
The transaction hash should be a link to explorer |
…nto feat/simplex-ui-redesign # Conflicts: # sdk/packages/simplex/docs/ai/ChangeLog.md # sdk/packages/simplex/docs/ai/Decisions.md
Contributor
Author
|
@Wizdave97 Comments addressed |
…rt-needed vault saves The periodic sweep silently skipped a vault whose maxDeposit(solver) was 0 (a StreamingYieldVault mid-tranche), so a wallet far over its threshold never deposited and nothing in the log or dashboard said why. The manual Sweep now button reported "Sweep executed" on the same path. - sweepExcessToVault returns a VaultSweepResult: submitted batches with per-vault deposits, and every skipped vault with a reason (sweeping-disabled / below-threshold / deposits-closed) plus the wallet balance, threshold and maxDeposit it saw. - deposits-closed warns once per closure with those fields, debug on repeats until a deposit succeeds or the venue is reconfigured. - VaultLiquidityState reads maxDeposit on refresh; balance rows carry acceptsDeposits and the overview shows "Deposits closed" under In vault. - POST /api/vault/sweep returns the formatted pass; the vault panel renders one sentence saying what was deposited or which vault refused and why. - Vault saves show a warning notice and toast when the server answers restartNeeded: true (filler booted without a vault venue), and the hint copy names the restart again. The 2026-09-03 removal treated that advisory as incorrect; it is the only case where the saved rows do nothing. - InitChainMeta gains the optional `note` the setup API and terminal wizard already read, so the declaration build passes again.
Wizdave97
approved these changes
Sep 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Redesigns the Simplex onboarding flow and operator dashboard with a clearer visual hierarchy, consistent controls, and more focused workflows.
What changed
App.tsxBehavior
The underlying setup and operator behavior remains unchanged. This PR primarily improves presentation, navigation, validation clarity, and code organization.