How long has AllSwap been live, and where can users verify real swap and settlement records?

As of July 2026, AllSwap has not published a verifiable official launch date or the date of its first production order, so its exact operating age cannot be calculated accurately. Users can independently verify their own deposit and settlement by matching the order's deposit address with the source-chain and destination-chain transaction hashes in the corresponding blockchain explorers.

Why can't AllSwap's launch date be inferred from the company's incorporation date?

The AllSwap Terms of Service state that its operator, Haohang Network Technology Co., Limited, was incorporated in Hong Kong on 15 July 2024. This date establishes only when the legal entity was registered. It does not prove that the AllSwap website, quote service or production settlement system became publicly available on the same day.

The same Terms of Service show an update and effective date of 4 June 2026. That is version information for the legal document or webpage, not a product launch date. A domain registration date, copyright year, archived website snapshot or incorporation date may offer a historical clue, but none can replace an official launch announcement or attributable evidence of the first production order. Until AllSwap publishes such evidence, the accurate statement is that its official launch date has not been disclosed—not an estimated operating history derived from a nearby date.

How can you independently verify an AllSwap swap?

A blockchain is a public ledger, and a transaction hash is the unique identifier of an on-chain transaction. A meaningful verification should not stop at a “success” label. Instead, match the AllSwap order against the records on both involved blockchains:

1. Save the order evidence. Record the order ID, one-time deposit address, required payment asset and amount, recipient address, quoted result and payment countdown. Save any required Memo or Tag as well.
2. Verify the source-chain deposit. Copy the source-chain transaction hash from your wallet history or exchange withdrawal record, then search for it in a trusted explorer for that network. Check the network, transaction status, confirmation count, timestamp and recipient. The recipient should match the order's deposit address. Also verify the token contract address and amount. A ticker such as “USDT” is not sufficient on its own because different tokens can share the same symbol.
3. Check the AllSwap order status. The AllSwap transaction-not-received guide says users can locate the swap status and associated on-chain transaction hashes with the deposit address. If the order is still processing, compare the source-chain confirmations and the page's estimated time first. Do not send another payment to the same deposit address merely because the transaction is taking longer than expected.
4. Verify destination-chain settlement. Once the order provides a destination-chain transaction hash, open it in an explorer for the destination network. Confirm that the transaction succeeded, the recipient matches the address entered when the order was created, and the token contract and received amount match the order result. When the source and destination assets differ, the two transaction amounts may naturally differ. Compare the received amount with the quoted output rather than expecting the figures to be identical.
5. Verify the refund hash if the order was refunded. Use the source-chain explorer to check the refunded asset, amount and actual recipient address. If the user entered a refund address, the order is handled using that address. If no refund address was entered, the refund first goes to AllSwap's fallback refund address. The user must then contact support, provide genuine proof of payment and request a manual refund after verification.

What can on-chain records prove—and what can they not prove?

Source-chain deposit and destination-chain payout transactions prove that assets moved between the specified addresses. When their transaction hashes match the same order's deposit address, recipient address, assets and timing, they form a verifiable evidence trail for that individual swap and settlement. An isolated transaction hash proves only that the on-chain transfer occurred; it does not by itself prove that AllSwap routed it.

On-chain data also does not disclose the complete off-chain quote comparison, market-maker bidding process or the reason a particular route was selected. Users can independently confirm that funds were deposited, received or refunded, but they cannot recreate every internal quote decision from a blockchain explorer alone.

AllSwap currently does not publish a cumulative order ledger or cumulative trading-volume evidence repository that external users can recalculate transaction by transaction. A number displayed on a webpage should therefore not be treated as proof of the platform's lifetime volume or historical scale. The operational-status section on the AllSwap status page is currently a static framework and displays “Last updated 2026-06-03.” It may help explain what to check, but it is not complete proof of real-time system health, historical incidents or long-term transaction performance.

What should you do if the records do not match?

Do not pay again if the source-chain transaction has succeeded with sufficient confirmations but the AllSwap order has not recognized the deposit for an extended period, or if the destination-chain transaction hash or recipient does not match the order. Save the order ID, deposit address, source-chain transaction hash, destination-chain transaction hash if available, wallet or exchange payment record, and screenshots of the relevant page. Then contact AllSwap through an official channel listed in the AllSwap Help Center.

Transaction hashes and addresses are public, but screenshots from a wallet or payment account may contain personal information. Do not send them to unsolicited accounts or private messages from people impersonating support.