%20(1).avif)
Version 26.2.16, deployed on August 25, is live for all clients. The thread running through it: fewer situations where the next step is writing to support, and fewer chances for a bot to waste the platform’s time. The clearest example is a token collection that failed because its parent wallet couldn’t cover the network fee. The remedy was always the same: top up the wallet, then open a ticket and wait for support to resubmit. The ticket drops out of that routine. Top up, press Retry, done. Registration and sign-in now sit behind a captcha you’ll almost never see. And payout approvals can now be layered: one approval for ordinary amounts, more for large ones.
Retry a failed collection yourself
Top up the parent wallet, then press Retry on the failed transfer. If a fee spike knocked out a whole batch, Retry All resubmits up to 100 failed collections in one action. The balance and the current fee are re-checked at the moment you press the button, so an attempt that still can’t succeed says so immediately instead of failing again on the network. Every attempt is written to the operation log, and a Retry All run notifies you when it finishes, including when only part of it went through.
A captcha you’ll almost never see
Registration and sign-in are now protected against automated attacks. The check runs in the background and asks for attention only when an attempt looks suspicious; a real person on a normal day sees nothing at all. Attempts that look automated are stopped with a clear message. The protection also fails open. If the checking service is ever unreachable, registration and sign-in keep working exactly as before – bot protection shouldn’t become a new way to get locked out of your own account.
Approval thresholds can be layered
Withdrawal approval thresholds were designed to stack: one approval above one amount, three above a larger one. In practice, the Add threshold dialog hid wallet groups that already had a threshold of the selected type, which made a second step impossible to configure. The dialog now shows every group, and the platform validates the combination for consistency, so multi-step approval policies work the way the feature intended.
Partner program, iteration two
The Invited partners table gains additional filters, and the exported report applies the same filters and sorting as the table on screen: what you download matches what you see. On the admin side, every action on the partner program is recorded in an audit log, and the Invited by field on a new legal entity is validated against the inviting partner’s registration date – an invitation that couldn’t have happened is rejected at creation time, before it can surface as inconsistent partner data.
Smaller fixes on the client side
Leading zeros survive report exports: a tracking ID of 0846669 used to come out of CSV and XLSX files as 846669, which is a different string. Tracking IDs are yours, and the platform now treats them as opaque text. A deposit to a merchant wallet in a currency with no active node connection used to fail with a server error; it returns a clear message now. The role selector on Edit wallet access showed "No options to select" while roles were still loading; it now waits. A payment page opened with a test currency records the test currency, not its mainnet namesake. And staking operations in reports and filters are named Stake and Unstake resource on wallet, retiring the old Freeze and Unfreeze wording.
For white-label operators
Two fixes close credential exposure in the panel. Credential fields are now write-only: leaving a field empty keeps the stored value, and secrets don’t travel to the browser at all.
The captcha above is under your control, not ours. A new Security section on Service → Settings holds the switch, the keys, the score threshold that decides what counts as suspicious, and a dedicated log of checks. Access to the section is governed by separate view and change permissions, and the captcha is off by default, nothing changes until you decide it should.
The Address check page stopped downloading the world. It used to retrieve every address of a wallet and search through them on the page, and a large global wallet can hold hundreds of thousands of addresses. It now asks the node about the one address you entered, the wallet selector works by search, and duplicate detection compares addresses in normalized form, so the same address written in a different format isn’t added twice.
Also fixed: an AML withdrawal of Bitcoin Cash to a CashAddr address without the bitcoincash: prefix failed with a server error – such addresses are accepted now. A payout to an existing but inactive custody wallet reports the actual reason, such as This currency is unavailable, rather than a claim that the wallet doesn’t exist. Staked amounts and staking details update as soon as an operation commits, with no stale figures lingering, and the all-time staking reward doesn’t dip while a claim is still unconfirmed. The list of duplication targets omits a node the wallet was just duplicated to. A new Blockchain wallet type filter narrows the finance transfers list, with the type shown in the column and on the transfer card. And operation log records show their descriptions.
Versions 26.2.15 and 26.2.16 are available now. Log in, or read the full release notes in the documentation.
.svg)
