Privacy and limitations
Public execution with a self-custodied wallet. No anonymity or shielding claims.
Public onchain execution
01What is visible
Swaps are public onchain transactions. Sender, target, value, calldata, transfers, approvals, outcomes and receipts can be observed through chain infrastructure. Public submission can expose intent before inclusion depending on propagation.
Addresses are pseudonymous, not anonymous. Funding, timing, interactions and external records can link identities. VEKTRA does not remove those links.
02Non-custodial does not mean trustless
The application holds no user private keys or pooled custody account. The wallet signs. The router can temporarily receive wrapped output before atomic unwrapping to the recipient. Contracts, wallet software, approvals and RPC remain trust dependencies.
New approvals are bounded to input. Older allowances are not automatically revoked. Disconnecting does not cancel onchain permissions.
03Execution bounds and MEV
Minimum output and deadlines constrain execution conditions. They do not hide order flow or establish comprehensive MEV protection. Transactions may be reordered, execute unfavorably within the bound or revert after spending gas.
No verified private relay, encrypted mempool, bundle submission or MEV-protected transport is configured. Protected execution does not mean private submission.
04Stealth and zero-knowledge shielding
Stealth-address derivation, scanning and recovery are not implemented. Shielded balances, nullifiers, anonymity pools, private swaps and zero-knowledge proofs are not implemented. No anonymity-set measurement exists.
Current public swaps are not anonymous or shielded. Future privacy features would require an explicit protocol, threat model, audit and end-to-end verification before such claims describe production.
05Offchain exposure
The quote API receives pair, amount and slippage. RPC operators can observe reads, including account balance requests when wallet functionality is enabled. Hosting/network providers process request metadata under their policies. No no-logging or retention guarantee is established.
Activity and slippage preferences use localStorage. Clearing storage removes local entries, not chain records. Documentation and market quotes require no wallet.