Fix Solana wallet connection for claim flow #4
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
symphony
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Borodutch/borodutch-tools!4
Loading…
Reference in a new issue
No description provided.
Delete branch "bdt-kaneo-4-solana-wallet-connect"
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
window.solanaduring renderwindow.phantom.solana,window.solana, Solflare/Backpack injected providers, delayed injection events, and Solana Wallet Standard registrationbun run testpathValidation
bun run checkbun run testbun run buildManual QA Handoff
Required after deploy to tools.borodutch.com: use a real browser profile with a real Solana wallet extension/account. Verify clicking Claim $testcoin -> Connect and check allocation opens the wallet connect/sign flow, the signed allocation check reaches
/api/claim/allocation-checkand updates the UI, a non-holder result witheligible:falseis acceptable, and the Lock $testcoin EVM wallet flow still connects and reads available/locked balances.Deployment note: the repo only documents Easypanel/Nixpacks production commands (
bun install,bun run build,bun run start); no repo-local deploy hook or Easypanel API credentials were present in this workspace.