Frequently asked questions

Privana is a private, non-custodial DeFi application for swapping tokens, earning yield on stablecoins, and automating trading strategies. All activity executes inside hardware-secured enclaves (TEEs) on Oasis Sapphire, a confidential blockchain. Transaction intent, balances, and trading history are private by default. Your keys never leave the hardware.

On a standard DEX like Uniswap, swaps enter a public mempool before settling, where bots running MEV strategies front-run them for a worse price. Privana routes swaps through a TEE, signing and submitting transactions directly from inside the enclave with no mempool exposure. Trades that do route externally originate from a shared vault address, not your personal wallet.

Custodial exchanges hold your private keys and can freeze funds, be hacked, or become insolvent. Privana keys are held inside a hardware enclave that the team cannot access, automation runs via programmable policies enforced in hardware, and trading activity is private by default.

Privana processes every swap inside a TEE, a hardware-isolated enclave that no one outside can read. Transactions are signed and submitted directly from inside the enclave, bypassing the public mempool. All users share a single pooled vault address per chain, so external observers cannot attribute any individual trade to a specific wallet.

No. Routing decisions happen inside the TEE before anything touches external infrastructure. When Privana sources liquidity from another chain, it does so from the shared vault address, not yours. Your wallet, your trade size, and your target are never visible to the external chain.

Oasis ROFL provides cryptographic attestation that the TEE is running the published code. The integrity of the enclave is verifiable independently. If the code running inside differed from what's published, attestation would fail.

No. Private keys are generated inside the TEE and have never existed outside it. Privana engineers cannot read them. Automation rules are enforced in hardware, not by policy, so no one at Privana can override them.

A smart contract on Ethereum monitors system liveness every 24 hours. If the enclave is unresponsive for seven days, a challenge period opens onchain and vault keys are reconstructed from distributed secret shares held by independent parties. The keys are released directly to you and you can sweep your funds without Privana's involvement. This is an onchain guarantee, not a service-level promise.

Privana routes swaps through a three-stage pipeline, trying each stage in sequence until the order is filled:

• Stage 1: Internal matching. Your intent is matched against other active intents inside the vault. If matched, balances update instantly with no external transaction.
• Stage 2: Vault inventory. If no internal match is found, the trade settles against vault inventory via the LiFi aggregator. Still no external transaction.
• Stage 3: External DEX routing. If internal liquidity is insufficient, the trade routes through external DEXes. Visible onchain, but originates from the shared vault address, not your wallet.

Privana's yield module routes idle stablecoin balances to vetted yield protocols automatically when you activate it. The module is opt-in: you define which assets participate, deposit thresholds, and maximum amounts. When you initiate a swap, any active yield position for that asset unwinds automatically before execution.

Privana maintains an instant liquidity reserve so withdrawals are not subject to lock-up periods.

Early waitlist members trade fee-free for 90 days. Full fee schedule will be published at launch.

Privana supports seven automation rule types at launch: trailing stop-loss, profit-take, price-triggered rebalancing, time-scheduled execution (DCA), Nightguard (overnight rebalance to stablecoins), profit-to-yield routing, and yield-to-trading. All rules are enforced in hardware with no manual signing required.

No. Once configured and funded, the enclave executes rules continuously without requiring your presence.

Yes, via a scoped sub-policy. The agent trades within limits you define: a daily spending limit, asset whitelist, trade direction, frequency cap, and maximum single trade size. Your private key stays inside the TEE and is never accessible to the agent. AI agents cannot initiate withdrawals or route funds to yield — those actions require direct user authorization.

Private keys on Privana are held inside the TEE on Oasis Sapphire. Privana does not hold your keys and engineers cannot access them. The vault's signing key is generated inside the enclave and has never existed outside it, enforced by Intel SGX hardware, not policy.

Your vault on Oasis Sapphire holds signing authority for each supported chain. The enclave derives a chain-specific key for each network and signs transactions directly on your behalf. Nothing moves through a bridge. The TEE acts as the signer across chains using keys that never leave the hardware.

Key encumbrance is a cryptographic mechanism that allows a private key inside a TEE to sign transactions automatically, but only within programmable rules you define: specific assets, actions, and conditions. You can update or revoke those rules at any time. This makes non-custodial automation possible without handing your key to a third party. The concept originates from the Liquefaction research paper by Austgen et al. at Cornell Tech (arXiv: 2412.02634, 2024).

Your account is your wallet, and your funds are governed on-chain by a smart contract on Oasis Sapphire, not by Privana. As long as you control your wallet, you can withdraw your funds directly on-chain at any time, even if Privana is offline, through the paths described in Fallback & Recovery. Privana never holds your keys, so keep your wallet's recovery phrase safe.