ANTARA is now open source. A wallet that asks you to trust its security should let you verify it, so we published the whole thing under Apache 2.0. You can read exactly how it works now. The vault isn’t an ANTARA contract you have to trust. It’s each chain’s standard multisig: a @multisig v4 2-of-2 on @solana, and a Safe on @ethereum, @base, @BNBCHAIN and @RobinhoodCrypto, checked against @safe’s published bytecode before it’s trusted. The guardian that holds the second key can do one thing: vote on a release. It can’t start one, it can’t execute one, and it never touches your keys. The logic that decides whether it signs is all in the repo. Every protection layer (biometrics, MFA, Safe Zones, Wi-Fi, Bluetooth, limits) is verified at approval time, tied to the exact transaction, and fails closed. If a check can’t be verified, it counts the same as one that failed. Releases only go to your own linked wallets. Before every deposit, proposal, approval and execution, the vault gets read from the chain again. Your private keys and biometric data never reach our servers. Read it, audit it, try to break it, and tell us what you find. Security you can inspect beats security you’re asked to believe. github.com/Antara-Wallet/ant… antara.tech

Bluetooth as requirement for vault txn. Your trusted Bluetooth device can become another condition for a vault release. Save a device, then have ANTARA check for a match when you approve. Desktop checks a connected device; the browser uses its device chooser. It checks device presence, not a distance in meters. The saved device must also match the app surface where you enrolled it.