feat(#519): same-device WalletConnect mobile pairing #1053
No reviewers
Labels
No labels
agent:fix_bugfix
agent:fix_conflicts
agent:fix_security
agent:gap_analysis
agent:implement
agent:implement
agent:implement
agent:open_issues
agent:ready
agent:research
agent:security_audit
agent:verify
architecture
backend
blocker:hybrid
blocker:launch
blocker:limit-orders
blocker:v2
block:log_only
block:security
bug
ci
contracts
correctness
deploy
dev
devops
docs
documentation
duplicate
e2e
enhancement
epic
feature
frontend
functional-completion
gas
good first issue
governance
help wanted
high-risk
hooks
hybrid
indexer
infra
infrastructure
integrators
invalid
launch-blocker
limit-orders
localnet
localterra
low priority
missing-implementation
needs-design
ops
performance
priority
high
priority
medium
product
qa
QA
question
ready
ready
research
scripts
security
security-hardening
smartcontracts
tech-debt
testing
ux
UX
v2
verification
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
code/cl8y-dex-terraclassic!1053
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/519-walletconnect-mobile-deeplink"
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
wc:), and Copy pairing link instead of a QR the user cannot scan on the same phone.QRCodeModalstill shows Scan + canvas when the hook returns false).location.hrefs from the async session callback (not a user gesture on iOS/Android). Vanilla fallback still has Open + Copy if the React hook is missing.Closes #519
Test plan
make verify-issue-519(unit + docs/skills invariants WC-M1–WC-M7)wc:URI (paste into the wallet WalletConnect input)mentioned in issue #519
added 4 commits
main8bb0e6ab- Merge branch 'main' into feat/519-walletconnect-mobile-deeplinkCompare with previous version
mentioned in commit
417257b89ementioned in issue #521
mentioned in issue #554