Security of the bridge page

There are two ways to deposit. They trade convenience for what this page ever sees.

Two ways to deposit

Made here (the default): the page creates your secret in this tab and puts it in the claim file. Convenient, but the secret exists in the browser until you close the tab.
From your Logos wallet’s request: the wallet keeps the secret, and the page only sees public facts. The safer way, once the wallet’s bridge mini-app is out.

What can go wrong when the secret is made here

A tampered copy of this page could send the secret away and claim your deposit.
A browser extension allowed to read pages could read it too.

What protects you: the page’s Content-Security-Policy lets it talk to no site but its Sepolia read service (PublicNode); it loads no third-party code; it never stores or sends the secret; and every file is listed in a manifest you can check.

What the page checks before you sign

Your wallet is on Sepolia. Every other network, Ethereum mainnet included, is refused.
The vault is the known one and holds the configuration your deposit was made for.
The amount is one the vault accepts, deposits are open, the limit has room, and the commitment is new.
The deposit succeeds when simulated, checked again right before your wallet asks.

A token approval is for the exact amount, never unlimited.

Your wallet is the last check

It must show Sepolia and the demo vault, 0x8C8b2664De28e5287158db4DB65D448638871b74. That catches a page that sends you to another vault. It cannot show a swapped commitment, so that depends on the page being genuine.

Limits today

Only accounts on the team’s test chain can claim. A deposit to any other account, including your account on the public Logos testnet, cannot be claimed yet.
Tested with a scripted wallet and read-only checks against the Sepolia vault, not yet with a real deposit.
Phone wallets work inside their own browser. There is no WalletConnect.