Instant Convert v6.0.5

Release Date: October 20, 2026 Tags: DELIVERY, WALLET, ECOSYSTEM, SEND

Overview

A user can now receive ETH, SOL and tokens that exist on several networks into their own wallet, from My balance. Until now these coins were only available as Send under My balance, and a Send refused the user's own address, so the only way to receive them was a Send to an address outside the platform. A client described it as a catch-22, and said that testers who could not get SOL from a faucet could not have swapped an easy-to-get token into it. A delivery closes the circle: the house pays the coins on-chain from its own address to the user's own deposit address, which the server picks, and the deposit scanner credits the wallet as it credits a deposit. The user chooses a network and nothing else.

Giving ETH or SOL on Ecosystem is still closed: a coin the house bought would stay on the seller's own deposit address and pay that user's next withdrawal, so the house could never collect it. TON and XMR cannot be delivered. A wallet's page now opens Convert with its currency chosen. Upgrade Notes lists what a delivery draws on.

Requires Ecosystem v6.6.1 for deliveries: with an older Ecosystem add-on these coins stay Send-only, as before. Requires Bicrypto 6.8.3 or newer for everything else, as before. The Convert button on a wallet's page is part of Bicrypto 6.8.7. The new text falls back to English on an older Core, except the asset dialog's new line, which an older Core does not show.

Update Instructions

pnpm updator

No schema change, no seeder, no .env change. Update Ecosystem v6.6.1 in the same window. Nothing needs switching on: a coin that already has a Send chain, with its Sends switch on and a funded house address, is offered under My balance as soon as both add-ons are updated, provided the background deposit scanner runs in this backend and can credit that chain (see Upgrade Notes). The new text is in English in all 90 languages until it is translated.

Upgrade Notes

Deliveries draw on the Send chains you already run

• A delivery has no switch of its own. A delivery of a coin on a chain is offered only where a Send of it is open (Convert & Send on in Settings, the currency's Send chain with its Sends switch on, and the house address funded above the floor) and where the deposit scanner can credit it. Turning a Send chain off closes its deliveries too. No setting closes deliveries alone: only switching the background scan off, or handing a chain's deposits to the Rust backend, does, and that affects every deposit.
• A delivery pays real coins from the same house holding, with the same reservation and the same floor, so a funding level that suited Sends alone now also serves every user who chooses My balance for these coins.
• The background deposit scanner has to run in this backend (ECOSYSTEM_BACKGROUND_SCAN not false, and the scan loop not handed to the Rust backend), the chain's deposits must not be on the Rust worker, the token must be enabled on a network this deployment runs, and the chain's monitor must be able to credit a deposit into the wallet. A chain that fails any of these is not offered, because coins paid to an address nothing credits are on a key with no ledger row. When a delivery quote is refused the log says why. Why the asset list leaves a chain out is logged only with LOG_LEVEL=debug.
• Added an alert to the admins who can act: every Super Admin, and users of the Admin role whose role holds view.convert.send or manage.convert.send (on a demo install, Super Admins only). Convert delivery not credited is sent once per delivery, when the chain confirmed it 30 minutes ago and no deposit credit carries its transaction. The coins are on the user's own address, so nothing is lost. Check the deposit scanner's log lines for that chain (DEPOSIT_SCAN) and its monitor. This console cannot credit a delivery by hand.

Added

Deliver to my wallet

A native EVM coin, SOL, an SPL token or a token enabled on several chains cannot be a ledger balance: only the user's own address can spend it, so a balance with no coins behind it could never be withdrawn. What the platform can do is what a deposit does, which is to put the real coins on the user's own deposit address. That is what a delivery does, using the Send machinery for the one destination a Send refuses. It goes one way only: nothing can be given on Ecosystem that could not be before, because the house may only buy what it can collect, and a native coin it bought would stay on the seller's own deposit address and be spent by the seller's next withdrawal. TON and XMR are not offered at all, because the house cannot pay either.

• Added the choice under My balance on an Ecosystem convert. The user picks the coin and the network, and the form reads Delivered to your ETH wallet. On a fresh form with several networks none is preselected, because the wallet holds the coin on the network chosen. There is no address to paste: the quote carries the chain, and the server opens the user's Ecosystem wallet in that coin (issuing the deposit addresses a deposit page would) and takes their address on it. An address from the browser is never read, and every other address is refused at the quote and again at the execute.
• Added the preview line Arrives in your wallet, with Your ETH wallet, its address and its network, the network fee, the convert fee and the rate. The button reads Convert (Verify and convert when the platform asks for a code on converts). The receipt, the History card, the History table and the detail sheet call the figure the same.
• Added a step to the delivery's progress. The payout is confirmed when the chain has it, but the balance moves when the scanner credits it, so the steps are Sending, Sent, Confirmed, and a last step that reads Waiting to be credited until the credit is seen and Credited to your wallet after. Until the chain confirms, the heading reads Your coins are on their way to your wallet; from the confirmation until the credit it reads Arrived on the network, waiting to be credited. The page keeps asking until about half an hour after it began following the payout; after that, History shows whether the delivery has been credited when its detail is opened. When the payout is signed and again when it is sent, the user's address is put on the scanner's fast lane and scanned, so the credit normally follows the confirmation by minutes.
• Added that a delivery asks for no withdrawal second factor, and applies no withdrawal KYC level, no withdrawal geography check and no per-account withdrawal freeze, because the value stays on the platform. The Trade KYC and Trade geography checks every convert runs still apply. A delivery also charges no ecosystem withdrawal fee. The network fee is in the quote. The optional Convert two-factor still applies. The quote route also accepts a Spot input, which runs the Spot withdrawal switches and the approval rule like a Send; the page offers a delivery from Ecosystem balances.
• Added to a Send's detail in Admin → Convert → Sends a line, Delivery to the user's wallet, that reads Not delivered yet (whenever the Send is not Confirmed), On the chain, not credited yet (in a warning tone) or Credited with the deposit's time. On each confirmation pass, every delivery confirmed in the last 48 hours (among the 200 most recently confirmed Sends) is looked for among the deposits of the user's wallet by its transaction hash, and stamped when found. A credit seen later than that is not stamped.
• Added to the asset dialog of a closed Ecosystem row a line saying that users can also receive the coin into their own wallet, and what that needs.

The Convert page opens on a wallet's currency

• Added the link from a wallet's page: /convert?type=eco&currency=ETH opens Convert on that kind of balance with that currency chosen as what is given, also when it cannot be given. An Ecosystem ETH then says Convert on Ecosystem is not available for ETH in the server's own words. A currency the asset list does not have for that wallet type is ignored.

Changed

A Send to the user's own address says what to do instead

• Changed the refusal. Where a delivery of the coin is open on the Send's network, a Send to the user's own deposit address now reads This is your own ETH wallet address. Choose My balance to have it delivered there. Where it is not (the Ecosystem add-on is too old, or that network cannot be credited), the old This address belongs to an account here. Convert to your balance and transfer instead. stands. Another account's address keeps the old sentence.

The asset list names the networks a delivery can use

• Changed GET /api/convert/asset: every asset carries deliverChains, the part of its sendChains a delivery can also use (empty unless a delivery is open for it, absent from an older server). A delivery quote is a Send quote with delivery wallet and twoFactorRequired false, and the order's send says delivery and whether it is credited.