Skip to content

fix: use match_address when locking exclusive wallets#219

Merged
v03413 merged 1 commit into
v03413:mainfrom
long2ice:fix/lock-trade-match-address
Jul 14, 2026
Merged

fix: use match_address when locking exclusive wallets#219
v03413 merged 1 commit into
v03413:mainfrom
long2ice:fix/lock-trade-match-address

Conversation

@long2ice

Copy link
Copy Markdown
Contributor

Summary

  • LockTradeAddress queried bep_order with column match_addr (wallet table name), but the order model column is match_address.
  • This caused MySQL Error 1054: Unknown column 'match_addr' and made exclusive (address_locked) address checks always treat addresses as free.

Test plan

  • Create a zero-amount / address-locked order and confirm no Unknown column 'match_addr' in logs
  • Create a second exclusive order against the same wallet+trade_type while the first is waiting/confirming and confirm it returns「暂无可用钱包地址」
  • Shared (non-locked) amount-based orders still allocate addresses as before

LockTradeAddress queried bep_order with match_addr (wallet column),
causing Error 1054 and breaking exclusive address checks.
@v03413
v03413 merged commit 62fc694 into v03413:main Jul 14, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants