QA: Validate below-min block behavior against live TokenMapping PDA limits (Solana) #112
Labels
No labels
agent:implement
agent:ready
backend
bug
cannot-reproduce
confirmed
desktop
docs
documentation
duplicate
enhancement
feature
frontend
good first issue
help wanted
high-risk
in-review
invalid
mobile
needs-triage
P0-critical
P1-high
P2-medium
P3-low
qa
QA
question
ready
report
responsive
security
security-escalate
smart-contract
solana
tablet
test-pass
ux
wallet-issue
wallet:keplr
wallet:metamask
wallet:station
wallet:walletconnect
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
code/cl8y-bridge-monorepo#112
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
Follow-up from bridge UI verification on v0.1.82 (
2a127e66, mainnet). Primary fix is confirmed: MIN label on Solana destination,destTokenDecimalsloading via TokenMapping PDA (findTokenMappingPda+resolveWithdrawSrcTokenBytesForSolana), net "You will receive" line, MIN preset + CTA flows (route tested: BSC → Solana, token testa).What still needs validation
Below-min block behavior should be exercised against live PDA limits, not only the happy path. Today testa has a 1.0 minimum, which makes the below-min edge case hard to trigger without sub-1 testa transfers (or another asset / configuration with a more testable floor).
Scope / acceptance
cc @Brouie
assigned to @Brouie
mentioned in issue #108
@PlasticDigits verified on v0.1.82 -
2a127e6.Route: BSC → Solana
Token: tdec (18 decimals on BSC, MIN PDA 3Af1LkQo2g9xasGhCcofVnRPWJxPjSyBHnMiFdzVNRm5)
Live MIN displayed: 1.005251256281407037 tdec
Test amount: 0.0005 tdec (~2000x below MIN)
Result: BRIDGE button disabled, blocked cursor on hover. UI correctly prevents submission below MIN.
Minor UX note: button is silently disabled with no explicit error text or tooltip explaining "below MIN" — not blocking, just an observation. MIN value is shown in the header row so user has the reference.
Screenshot attached on request.
@Brouie Open an issue for the minor ux note to add tooltip and explicit error text below button explaining the reason the button is disabled, then close this issue
mentioned in issue #113
mentioned in issue #111