Bridge routes and what each one guarantees

Two routes carry funds from another chain into your Cloak balance. They deliver the same asset to the same place, and that is where the similarity ends. This page is the honest comparison — read it before you pick, and especially before you send an amount you would mind losing. If you have not read Bridging in from another chain yet, start there; this page assumes it.

​

Side by side

​

Why the signature matters

Without one, a deposit address is a string a web page handed you. A substituted address and a real one look identical, and you would find out by having sent money to it. 1Click signs a payload that contains both the deposit address and the Solana recipient. Your browser verifies that signature against the route’s key before the address is displayed, and a route whose signature fails verification is not offered at all — it is moved aside with the routes that are unavailable. The property that buys you is unusual and worth stating precisely: Two limits on that, because a guarantee stated without its edges is not a guarantee:

• The signature covers amounts, the address and the recipient — not fee captions. Fee figures sit outside the signed payload, so they carry no such proof. The app ranks and displays on signed amounts.
• A compromised web page could lie about the result. The verification runs in the browser, so a bundle that had been tampered with could claim a check passed. This is why verified addresses matters: confirm you are on the real Cloak app first, and the check underneath is sound.

​

What the Jupiter route offers instead

Nothing is signed on this route, and the app says so in those words rather than hiding it behind the same badge the other route earns. What is available is weaker and worth understanding for what it is:

• The address it hands out is stable across repeated requests for your destination, and
• it is different for a destination Cloak does not control.

Those two checks falsify a broken or hostile interface — one address handed to everybody, or a new one every call. They do not attest that this address belongs to you. On this route you are trusting Cloak.

​

The trust nobody can remove

Both routes hold your funds between the origin transfer and the Solana payout. That is how every bridge that is not burn-and-mint works, it is not something Cloak introduced, and no part of Cloak’s design touches it. It can be bounded and disclosed, which is what this page is for; it cannot be removed on these routes. The honest framing is never “trustless or not” — it is which trust, how bounded, and how visible. Here:

• In transit: the route holds the funds, for the time its estimate quotes.
• At the address: the funds are yours the moment they land. The receiving key is derived from your own key material and no server has ever held it.
• After the shield: the pool’s guarantees take over, and the security model applies as it does to any other deposit.

​

The refund address, on the 1Click route

You supply an origin-chain address when you use this route. It is used for exactly one thing: receiving your funds back if the order cannot be filled.

• Give an address you control on the origin chain — the same wallet you are sending from is the normal choice.
• Leave it blank and the 1Click route is simply skipped for that chain. The Jupiter route needs nothing here.
• The address is screened against sanctions and high-risk lists before any route is asked for a quote, the same screening described in Compliance. A screening failure stops the request rather than letting it through.
• A smart-contract wallet address may be rejected by the route itself, so a plain wallet address is the safe choice.

​

Choosing

Where both routes serve your chain, the amounts they quote land about a tenth of a percent apart. The output number is not the interesting axis. What differs is everything above: one route lets you verify the address and returns an order it cannot fill; the other does neither.

​

Where next