feat(frontend): add vFDUSD token logo for bridge UI #133
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#133
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?
Summary
Venus vFDUSD is now registered on the CL8Y bridge (BSC LockUnlock ↔ Terra mint_burn). The bridge frontend resolves logos via symbol match against
packages/frontend/public/tokens/*.pngandLOGO_SYMBOLSinpackages/frontend/src/utils/tokenLogos.ts— vFDUSD is not in that set yet, so the UI will show a missing/fallback icon.Related: ust1-window#19 (Phase 2 UST1↔vFDUSD window deploy).
Live token addresses
0xC4eF4229FEc74Ccfe17B2bdeF7715fAC740BA0baterra1mnl9azefrqpmu888ar2u6zrcwr80hxlt3avf4300r576cw5ar7esvxsvj3Acceptance criteria
packages/frontend/public/tokens/VFDUSD.png(same style/size convention as existing token logos, e.g.CL8Y.png/SPACEUSD.png).'VFDUSD'toLOGO_SYMBOLSinpackages/frontend/src/utils/tokenLogos.ts.vFDUSD/VFDUSD).Notes
VFDUSD.png.mentioned in commit
87061927dbmentioned in merge request !151
mentioned in merge request !152
Implementation update (!152)
Branch:
feat/gl-133-vfdusd-token-logo— MR: https://gitlab.com/PlasticDigits/cl8y-bridge-monorepo/-/merge_requests/12Acceptance criteria
packages/frontend/public/tokens/VFDUSD.png(256×256, Venus Protocol branding from this issue’s attachment)'VFDUSD'toLOGO_SYMBOLSinpackages/frontend/src/utils/tokenLogos.tsvFDUSD/VFDUSD→/tokens/VFDUSD.png(unit-tested twice vianpm run test:run -- src/utils/tokenLogos.test.ts)Also documented INV-FE-TOKEN-LOGO-1 +
skills/agent-frontend-token-logos.md(cross-linked fromdocs/FRONTEND_BRIDGE_INVARIANTS.md,docs/frontend.md, README,skills/agent-frontend-bridge-chains.md).Final verification — per-tx + rolling rate limits (2026-07-30T04:16:17Z UTC)
Queried live mainnet; values below are as configured on-chain, not changed by this frontend MR.
BSC — TokenRegistry
0x3d8820EC93748fd4df8eee6B763834a23938B207isTokenRegisteredtruerateLimitBridge0xb2A22c74dA8E3642e0EffC107d3Ac362ce885369(wired)getRateLimitConfig[0])865586527getRateLimitConfig[1])86558652777getRateLimitConfig[2])86558652777Token:
0xC4eF4229FEc74Ccfe17B2bdeF7715fAC740BA0baBSC — Guard
TokenRateLimit0xD72b2fe3012a2896aef7E3cA561aD11B1542a88cdepositLimitPerToken0(unset / no guard deposit cap)withdrawLimitPerToken0(unset / no guard withdraw cap)Terra Classic — bridge
terra18m02l2f43c2dagqnz3kfccpgz9pzzz5hk9l5mh5wvr6dcvv47zfqdfs7laenabled: true, 6 decimals)rate_limitconfignull(not inall_rate_limits)total_supply00); per-period:100e18when supply is zero (DEFAULT_RATE_LIMIT_IF_ZERO_SUPPLY)period_usage.used_amount0period_usage.remaining_amount2^128-1(no configured period cap stored)Terra CW20:
terra1mnl9azefrqpmu888ar2u6zrcwr80hxlt3avf4300r576cw5ar7esvxsvj3Not done / follow-ups (out of #133 frontend scope)
set_rate_limitfor vFDUSD (currently relying on zero-supply default) — operational, not a logo task.TokenRateLimitdeposit/withdraw caps for vFDUSD — optional defense-in-depth; TokenRegistry withdraw caps are already set andrateLimitBridgeis wired.Verified: vFDUSD rate limits set to 500 / tx and 5 000 / 24h
On-chain readback matches the intended policy (BSC 8 decimals, Terra 6 decimals).
BSC TokenRegistry
setRateLimit— ✅0500000000005000000000000xC4eF4229FEc74Ccfe17B2bdeF7715fAC740BA0ba0x3d8820EC93748fd4df8eee6B763834a23938B2070x59f86cda47aa58bff1f830cab6ededa2f50926136351b4a7cb3281ce2be77b81(block112947574, status success)0xCd4Eb82CFC16d5785b4f7E3bFC255E735e79F39cBSC Guard
TokenRateLimit.setLimitsBatch— ✅depositLimitPerToken(24h)500000000000withdrawLimitPerToken(24h)5000000000000xD72b2fe3012a2896aef7E3cA561aD11B1542a88c0x50eadf2f87eae60ee3f818c275ea6d7c0de39331533e68b0c391e04282e9fc(block112947516, status success)Terra Classic
set_rate_limit— ✅max_per_transaction500000000max_per_period5000000000terra1mnl9azefrqpmu888ar2u6zrcwr80hxlt3avf4300r576cw5ar7esvxsvj3terra18m02l2f43c2dagqnz3kfccpgz9pzzz5hk9l5mh5wvr6dcvv47zfqdfs7laAll three surfaces now agree on 500 / tx and 5 000 / 24h.
Correction: Guard tx hash
Previous note’s Guard tx link may have been corrupted by HTML entity encoding. Canonical hash from block
112947516:setLimitsBatch:0x50eadf2f87e692e60ee3f818c275ea6d7c0de39331533e68b0c391e04282e9fc(status success)On-chain readbacks from the prior verification comment remain correct (500 / tx, 5 000 / 24h on TokenRegistry + Guard + Terra).
mentioned in commit
c4bebecefbmentioned in commit
c7139fddc6mentioned in merge request !153
mentioned in commit
d5f053cb9amentioned in commit
5e1c3ecdc0mentioned in merge request !154
mentioned in commit
f62203b50a