Control starts with clear boundaries.
Wallet keys, transaction review and recovery.
Keys stay with your wallet
veilink never stores a wallet private key. Connecting requests public accounts; signing requires a separate action. Privacy sessions use two matching fixed-message signatures to derive keys inside a dedicated worker.
Decode and preflight before signing
Short-lived reviews bind the exact transaction, owner, assets, recipients and bounds. Solana signatures must match the reviewed message. Chain preflight is retained to detect failure before a real transaction is sent.
Unknown is not successful
Execution records and duplicate guards are persisted before submission. Unknown outcomes are queried by hash, never automatically resent. Read-only recovery tokens cannot authorize a payment.
Verification has limits
Automated checks and public endpoint reads do not establish funded settlement or a third-party security audit. Every financial flow needs human-wallet acceptance.