From 0651b80eb7a1353b5aa0ad97098f55f3266fb4c5 Mon Sep 17 00:00:00 2001 From: Satoshi Qazi Muhammed Date: Sun, 19 Jul 2026 01:48:13 -0700 Subject: [PATCH] fix: sync renewal topup with the live bridge config (10K -> 200K wUSDT) STANDARD_RENEWAL_TOPUP still had the bot's old built-in default (10,000). The live pezbridge_bot_config.json and the Android wallet's BridgeMultisigConstants both renew to 200,000 (threshold 40,000) - and all three signing channels must build the same call, or the hash differs and real pending renewals stop auto-matching in the /multisig/pending UI. --- shared/lib/usdt.ts | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/shared/lib/usdt.ts b/shared/lib/usdt.ts index 8250d3d3..3b3d7258 100644 --- a/shared/lib/usdt.ts +++ b/shared/lib/usdt.ts @@ -33,8 +33,13 @@ export const WUSDT_BRIDGE_CUSTODY_PEZKUWI = '5GvwxmCDp3PC33KHoeWSgj3S7ocE7nzk1ji export const WUSDT_AUTOMATION_KEY_ADDRESS = '5GQu4PFUb1f3MTJ7i7c1CtLgDk3TVvpSW1VbQCRmfkMoC8cM'; /** The standard top-up amount the multisig renews the automation key's allowance to (6 - * decimals) - used to reconstruct and auto-describe that one deterministic pending call. */ -export const STANDARD_RENEWAL_TOPUP = 10_000_000_000n; // 10,000 wUSDT + * decimals) - used to reconstruct and auto-describe that one deterministic pending call. + * MUST match pezbridge_bot_config.json's topup_amount AND the Android wallet's + * BridgeMultisigConstants.TOPUP_AMOUNT: all three signing channels build the SAME on-chain + * call, so a different amount here computes a different call hash - real renewals would + * show as "Unknown call" instead of auto-matching. 10,000 (the bot's old built-in default) + * was stale; the live config renews to 200,000 (renewal_threshold 40,000). */ +export const STANDARD_RENEWAL_TOPUP = 200_000_000_000n; // 200,000 wUSDT // Withdrawal limits and timeouts export const WITHDRAWAL_LIMITS = {