Ecosystem v6.5.7

Release Date: October 1, 2026 Tags: WITHDRAWALS, TRANSFERS, ACCOUNTS, FEES

Overview

Ecosystem withdrawals and transfers now obey Core's money restrictions. Core 6.8.3 lets an admin stop withdrawals, transfers or both on one account without blocking it. This release is what makes that apply to on-chain withdrawals, Ecosystem wallet transfers and withdrawals already in the queue. Without it, those stay open on a restricted account and nothing warns you.

Requires Core v6.8.3. On an older Core this release's withdrawal and transfer routes, its withdrawal queue and its scheduled jobs, deposit verification included, do not load.

Update Instructions

pnpm updator

Update Core 6.8.3 first, then this add-on in the same window. No schema change of this add-on's own, no seeder, no .env change.

Added

Withdrawals and transfers obey an account's money restrictions

• Added the refusal of an Ecosystem withdrawal on an account with Withdrawals disabled: "Withdrawals are disabled on your account. Please contact support.", before the KYC, location and 2FA checks.
• Added the refusal of an Ecosystem wallet transfer on an account with Transfers disabled: "Transfers are disabled on your account. Please contact support.", before the Transfer PIN.
• Added the same refusal for a withdrawal to an address that belongs to another customer, which is a transfer in substance: "Failed to withdraw: Transfers are disabled on your account. Please contact support." On this one route, with only Transfers disabled on, the customer's withdrawal 2FA code is used up before the refusal.
• Added a hold on withdrawals already queued when the account is restricted. They stay pending: not sent, not failed, not refunded, and the customer is not told. They go out within about five minutes of the restriction being lifted. To return the money instead, reject the withdrawal.
• A withdrawal already being sent is not recalled, and a restriction set after the queue has picked a withdrawal up does not stop it.