Instant Convert 6.0.4
Latest13 October 2026
This release has upgrade notes. Read them before updating — they describe behaviour changes that need your attention.
Instant Convert v6.0.4
Release Date: October 13, 2026 Tags: INVENTORY, QUOTES, TESTNET
Overview
A native coin's house wallet can now be opened from the screen that promises it. The inventory says "Rescan deposits opens the house wallet for this currency", but the rescan only registered wallets the house already held. A native coin is funded on-chain only, and its converts stay closed while the house holds none, so for those coins the house wallet could never be created from there and every rescan answered that the house had no ECO wallet yet. The rescan now opens it.
A customer who types the amount they want to receive and is refused for size is now told what to type instead. A testnet coin spelled in two cases no longer shows "0 enabled chains". An Ecosystem asset that is Closed for balance converts now says why in its dialog. Upgrade Notes lists the assets to look at again.
Requires Bicrypto 6.8.3 or newer, as before. The Convert button on My Wallets is part of Bicrypto 6.8.6, and so are the two new texts of the asset dialog: on an older Core the dialog shows the rule from the wallet field and leaves the Send line out, and prints no key.
Update Instructions
pnpm updatorNo schema change, no seeder, no .env change. The two new texts are in English in all 90 languages until they are translated.
Upgrade Notes
Assets that showed "0 enabled chains"
- Fixed the console reading a BSC testnet token spelled
tBNBas no token at all. After the update such an asset (TBNB with atBNBtoken row, for example) shows its chains and can open for converts. Review the enabled state and the limits of every asset that used to show "0 enabled chains".
Added
Convert from My Wallets
- Added a Convert button in the wallet page's header and a fifth quick action, "Swap one balance for another", both opening Convert. They appear only while this add-on is enabled. They ship in Bicrypto 6.8.6.
Changed
A size refusal says what fits when the customer named what they receive
The per-convert limits are in US dollars and measured on what the customer gives. A customer who typed what they want to receive could be refused with only "The maximum convert is $50.00." and no way to tell what to type: with a 0.5% fee, a 1.5% spread and a $50 maximum, receiving 49 USDT takes 0.00060569 BTC, worth $50.07.
- Changed the refusal, for an amount typed on the receiving side, to say what that amount costs and the most (or least) that can be received. Above the maximum: "Receiving 49 USDT takes 0.00060569 BTC, worth $50.07 with fees included, and the maximum convert is $50.00. The most you can receive in one convert is N USDT." Below the minimum: "… and the minimum convert is $10.00. Receive at least N USDT." N is priced through the same route, so the next quote accepts it. It reads "about" when a Send's or a withdrawal's own fee is part of the route.
- The giving side keeps "The maximum convert is $50.00." and "The minimum convert is $10.00.", and so do the daily and hourly limits and any quote where the figure could not be worked out.
A closed Ecosystem asset says why
An Ecosystem asset can be switched on in Assets and still convert nothing: the code opens a currency only when it has exactly one enabled withdrawal chain, of a pooled family (UTXO coins, EVM tokens, TRC-20 tokens, TRX), and no switch on the row changes that. The asset's dialog said Closed for balance converts, a family and a chain count. The sentence a user is refused with was one page away, on the Inventory screen, so an operator who switched ETH on in both directions and asked why it still would not convert had nothing to read.
- Changed the asset's view dialog. For a closed Ecosystem row, Ecosystem eligibility now states the rule and the sentence a user is refused with on each side, in the words the quote answers with, for example "Convert on Ecosystem is not available for ETH" and "Convert to ETH is only available as Send". A sentence that is the same on both sides is printed once.
- For a currency that can still be received through Convert & Send (a native EVM coin, SOL, an SPL token or a multi-chain token), it adds what that takes: Convert & Send switched on in Settings, a Send chain for it in Inventory with the house's address funded on that chain, then the row enabled with Convert to on. A currency the house cannot pay out (TON, XMR) gets no such line.
- An open row shows nothing extra, and nothing about what converts has changed. The asset table keeps its badge and chain line as before; the reason is in the dialog.
Fixed
Rescan deposits opens a missing house wallet
- Fixed the rescan for a native coin. In Admin → Instant Convert → Inventory → Funding addresses, Rescan deposits for a currency now opens the house's ECO wallet for it first, when the currency is an ECO asset and the house holds none, and then registers the addresses with the deposit scanner. The click creates the wallet and its addresses, and needs the edit permission on the inventory.
- When the wallet cannot be opened the reason appears under "Skipped by the deposit watch", for example "Could not open the ECO ETH wallet: no enabled ecosystem token for ETH on a network this install can reach". A currency that is not an ECO asset keeps the old "the house has no ECO … wallet yet".
- A rescan sent for all currencies at once through the API opens nothing. The console always sends one.
A testnet coin spelled in two cases
- Fixed the console showing a BSC token spelled
tBNBas TBNB with "0 enabled chains". The token rows were matched without regard to case and then discarded by an exact comparison, so the asset found none.