Bug: register-tokens incomplete — Anvil1 unregistered, Terra incoming missing, USTC missing #85
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#85
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?
Ran Verify All on Settings > Tokens page (v0.1.197/84cf7e4). Three systematic gaps in the token registration deploy:
Anvil1: 0/7 on every token. No tokens registered, no dest mappings, no incoming mappings. Entire chain skipped by register-tokens.
LocalTerra incoming mappings: missing for all CW20 tokens (TKNA/B/C, KDEC, SOL) from both Anvil and Anvil1. Only LUNC (uluna) has full 4/4 Terra registration. Outgoing dest mappings exist but incoming set_incoming_token_mapping was never called.
USTC (uusd): 0/7 everywhere. Not registered on any chain, no dest mappings, no incoming mappings.
What works: Anvil has 7/7 on all tokens. Solana Localnet has 5/5 on all SPL tokens except SOL/wSOL (#84). Terra outgoing dest mappings present for CW20s.
Separate from #84 which covers the wSOL mint-not-on-localnet issue.
Confirmed E2E impact: Anvil->LocalTerra 100 TKNA deposit succeeded (tokens locked) but HASH SUBMISSION FAILED on Terra side — 'Token not mapped for source chain: chain=0x00000001, token=terra17p9rzw...ydrqk7'. The missing Terra incoming mapping causes operator withdrawal to be rejected. 99.50 TKNA stuck in limbo. TransferStatusPage correctly shows the error at step 2/4 with resolved params.
Also: the retry/resubmit button on the HASH SUBMISSION FAILED screen doesn't work — clicking it just loops back to the deposit step instead of retrying the hash submission.
USTC (uusd) and QA scope
USTC showing 0/7 in Settings → Tokens → Verify All is expected for the current QA stack:
setup-bridge.shonly runsadd_tokenforuusdon Terra.register-tokens.ts/qa-full-token-setupdo not registeruusdon EVM TokenRegistries or full Terra↔EVM/Solana mappings.We do not need to test or fully register USTC in QA paths at this time. Full USTC parity can be a separate product-driven scope later.
(Tracked alongside #85 registration/verify gaps for Anvil1 / Terra incoming.)
Update (branch
feat/solana-integration, commitcda6bf7)Fixes in this push:
make deploy,start-qarunsscripts/qa/sync-local-env-from-forge-broadcast.shso.deploy/local.envEVM / EVM1 bridge, registry, and LockUnlock addresses match Foundryrun-latest.jsonon chains 31337 and 31338 (avoids stale proxy addresses beforeqa:full-token-setup).terraIncomingSrcTokenB64()(native denoms → keccak UTF-8; CW20 → canonical 32-byte bech32 as base64).register-tokens.tsuses it for incoming mappings; unit tests interraTokenEncoding.test.tsand chain checks intoken-registration.integration.test.ts.@brouie Please QA-verify on a host with Docker + this branch:
make start-qa(full stack: compose, migrate, deploy, broadcast sync,qa:full-token-setup, operator, canceler — seescripts/qa/README.md).uusdshowing 0/7 remains expected for local QA; no need to block on USTC registration.cd packages/frontend && npx vitest run src/services/terraTokenEncoding.test.tsand, with chains up,make test-frontend-integration-chains.Thanks!
Partial fix in
cda6bf7: Terra incoming mappings now 4/4 on all tokens (was broken yesterday). That item is resolved.Still open:
SOL Solana PDAs still 2/5 tracked separately in #84.
mentioned in issue #67
@brouie USTC (
uusd) 0/7 is expected with the current QA setup:qa:full-token-setup/register-tokens.tsdo not registeruusdon any chain (no dest/incoming mappings). That token can be dropped from the Settings → Tokens verification matrix (or marked skipped) so it does not look like a deploy regression.@brouie When comparing Settings → Tokens / Verify All to the QA server, the full laptop sequence in
scripts/qa/README.md(On your laptop) matters: SSH-Lforwards,scpthe server’s.deploy/local.envinto your clone, run./scripts/qa/write-frontend-env-local.sh, then restart Vite (npm run dev) soVITE_EVM1_*and token addresses match the latest deploy. Skippingscp/regenerate/restart often looks like “Anvil OK, Anvil1 0/7” even when the server registered correctly.register-tokens fix is working great -- pulled
74b5f3e, clean restart, 6/7 tokens now 23/23 verified. SOL route works too (#84 confirmed fixed). only USTC (uusd) is still completely unregistered: 0/7, no dest mappings, no incoming mappings, no Solana PDA on any chain. everything else is green.@Brouie uusd unregistered is expected, please close if remaining are passing
closing -- 6/7 tokens 23/23 verified. USTC (uusd) unregistered is expected per dev.