Skip to content

Fix: standardize on expires_at, drop duplicate funding_expires_at in WapuPay orders - #129

Draft
andycreed0x wants to merge 10 commits into
use-lbtc-on-wapupayfrom
fix/wapupay-use-expires-at
Draft

Fix: standardize on expires_at, drop duplicate funding_expires_at in WapuPay orders#129
andycreed0x wants to merge 10 commits into
use-lbtc-on-wapupayfrom
fix/wapupay-use-expires-at

Conversation

@andycreed0x

Copy link
Copy Markdown
Collaborator

Purpose

WapuPay's order responses only ever return expires_at; the codebase also carried a redundant funding_expires_at field that duplicated it. This drops the duplicate and standardizes on expires_at end-to-end.

Targets use-lbtc-on-wapupay (#122) instead of develop so it merges together with the L-BTC funding-rail work, since both touch WapuPayOrder/wapupay.py.

Main Changes

  • 🐛 Removed the redundant funding_expires_at field from WapuPayOrder and _TENTATIVE_RESP_FIELDSexpires_at is now the single source of truth
  • ♻️ WapuPayManager's funding-window display now reads order.expires_at
  • 📝 Updated docstrings and the MCP tool description (server.py, tools.py) to reference expires_at
  • ✅ Updated tests/test_wapupay.py and the manual test script (scripts/prompts/prompt_test_wapupay.md) to match

⚠️ Breaking Changes

funding_expires_at is removed from the wapupay_create_order / order-status response shape. Any caller reading that field directly (instead of expires_at) needs to switch.

Checklist

  • No hardcoded values (they should go in constants.py, .env, or our database)
  • Added/updated tests (if necessary)
  • Added/updated relevant documentation (if necessary)

andycreed0x and others added 10 commits July 20, 2026 11:12
The tool reference tables only covered the original wallet/BTC/Liquid/
Lightning tools; SideSwap, SideShift, Changelly, WapuPay, JAN3 account,
qr_generate, and doctor were all missing. Also trims a few stale
docstrings/comments left over from the doctor feature.
Bump the beta segment on every develop push via scripts/bump_beta.py,
commit it back, then build and publish to TestPyPI. main no longer
triggers the workflow; PyPI stays release-only. Move PUBLISHING.md to docs/.
develop's required-checks ruleset rejects GITHUB_TOKEN pushes since the bump
commit can never carry a passing "Run tests" run. Use a repo deploy key
(DEVELOP_DEPLOY_KEY secret), which is an explicit bypass actor on the ruleset.
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.

1 participant