Privacy in blockchain and web3 is not a default setting. Because privacy must be designed in, decentralized applications (dApps), including decentralized finance (DeFi) solutions, often lack it. As a private, non-custodial DeFi interface, Privana aims to answer this\u00a0need.<\/p>\n
Built by the Oasis team, Privana runs on Sapphire\u2019s confidential EVM runtime inside hardware-secured enclaves, better known as Trusted Execution Environments (TEEs). This setup enables the features of privacy, automation, and self-custody to coexist without trade-offs.<\/p>\n
Before understanding in detail the core concepts behind Privana, it is useful to examine the privacy problem and how it is intended to be\u00a0solved.<\/p>\n
What users can do with Privana<\/a> underscores this application\u2019s privacy-first commitment: swap tokens, earn yield on stablecoins, and automate trading strategies. At the same time, users have self-custody, and none of their activities are revealed on-chain. This is in contrast to any standard decentralized exchange (DEX), where trades are always public; transactions are visible to anyone, including bots, who can also intervene with sandwich attacks and front-running; and full transparency dictates that user wallet history is always accessible. Privana is designed to solve these problems.<\/p>\n Privana and Oasis combine to deliver the application\u2019s multi-chain feature while maintaining the privacy\u00a0setup.<\/p>\n Each layer has to play only its own part. Oasis takes on the responsibility for privacy and security with Sapphire\u2019s confidential smart contracts and encrypted contract storage. The external chains just enjoy the benefits, and they only see what they need to\u200a\u2014\u200asigned transactions in final state. Privana\u2019s contribution is the user interface: wallet connection, asset deposit, execution of swaps, rule setup for automation, and portfolio management.<\/p>\n It is crucial that privacy and security guarantees come from Oasis rather than from Privana because the assurances are backed by core hardware and blockchain levels instead of merely the application level.<\/p>\n Privana\u2019s core functionality can be stated in a single sentence. It operates pooled, policy-governed vaults that hold assets inside hardware enclaves and execute DeFi actions privately. Let\u2019s see how this\u00a0tracks.<\/p>\n Pooled vault\u00a0model<\/strong><\/p>\n When users deposit tokens in Privana, the funds are kept in a vault, a smart contract on Oasis Sapphire inside an Intel SGX enclave (more on this, rather than in individual wallets as usual. This model moves away from the system of individual wallet users holding their private keys and instead uses a single vault per chain to hold assets for multiple users. The obvious next question is how individual token holdings are then managed. The answer lies in a confidential accounting layer<\/strong> tracking the user balances. This layer is a set of encrypted smart contracts that privately map and maintain individual token holdings.<\/p>\n This design choice is deliberate and comes with several benefits. The confidential accounting layer in Privana\u2019s pooled vault model is unique to DeFi solutions but follows the same logic as traditional institutions where, for example, users keeping their gold would all be stored in a single secure vault while the ledger records will maintain individual holdings. Privana\u2019s use of this accounting layer thus serves 4 purposes.<\/p>\n * When users deposit their tokens, this system verifies the deposit on the source chain and registers it to the balance in the user\u2019s name in the confidential ledger.<\/p>\n * When users initiate a trade or yield activity, the system does a quick balance check for fund sufficiency before processing any transactions.<\/p>\n * For every incoming deposit, the system runs Know Your Transaction (KYT) checks to verify that funds don\u2019t originate from sanctioned sources. This filter is a compliance mechanism adding another layer of security to the vault without compromising its privacy\u00a0mandate.<\/p>\n * After every successful trade execution, there is immediate balance reconciliation so that the latest state of the user\u2019s holdings remains updated in vault\u00a0records.<\/p>\n A great advantage of Privana\u2019s vaults is that they are chain-agnostic. The keys stay and run inside TEEs, while from the target blockchain\u2019s perspective, all logic is enforced off-chain. So, even a network like Bitcoin, without native smart contract support, can benefit from the\u00a0model.<\/p>\n TEEs, key encumbrance, and the non-custodial model encapsulate the core concepts behind Privana\u2019s build, so it is important to delve a little deeper into each of\u00a0them.<\/p>\n TEEs<\/strong><\/p>\n TEEs sit at the center of Privana\u2019s privacy and security architecture. It is hardware running code inside, like a locked room enforcing rules so that no one can view, access, or modify what\u2019s inside. It keeps everybody out, even the operating system and the server operator. As mentioned before, for Privana, this locked room is an Intel SGX enclave on Oasis Sapphire.<\/p>\n The TEE protects vault keys, user balances, policy rules, and transaction history. Everything stays encrypted within the TEE, only gets decrypted during the duration of processing, and is re-encrypted when processing is complete.<\/p>\n There is never any exposure to external systems. So, the TEE prevents access to or reading of private keys or any attempts to bypass user policies. Moreover, no unauthorized transactions can get through or get signed. Not even an engineer with full server access can extract or alter what is inside the\u00a0enclave.<\/p>\n Most users will be satisfied with guarantees, but anyone who is tech-savvy and wants to verify for themselves can use remote attestation to check that the code running inside the enclave is the one that was promised and whether it is really untampered.<\/p>\n From an applicability point of view, enterprise custody platforms often utilize TEEs for institutional users. Privana aims to provide the same security model for DeFi\u00a0users.<\/p>\n Key encumbrance<\/strong><\/p>\n In a standard wallet, users must manually approve every transaction by signing with their private keys, which increases the risk of exposure or compromise. With key encumbrance, users can pre-define rules and let automation take care of the rest. This is the practical application of the concept laid down in the Liquefaction research paper<\/a> by Austgen et al. at Cornell\u00a0Tech.<\/p>\n Key encumbrance thus lets the enclave execute on the user\u2019s behalf, bound or encumbered by user-defined policy that can be updated or revoked at any time at the user\u2019s discretion.<\/p>\n Take this\u00a0example.<\/p>\n \/\/ Example policy: delegate yield routing, keep direct swap control \/\/ The enclave enforces these limits in hardware. Privana takes key encumbrance utility forward by introducing the principle of asset-time segmentation<\/strong>. It means that at any given time, only a single entity can exclusively control any specific asset position, and this entity can either be the user themselves or the user\u2019s delegate. As a result, two policies cannot simultaneously claim the same asset, thereby preventing conflicts and ensuring user exit as and when they\u00a0want.<\/p>\n The benefit of key encumbrance is best understood from how it counteracts the SEAO assumption model. Single-Entity Address-Ownership, or SEAO, dictates that one address must mean one corresponding user controlling it absolutely. In contrast, key encumbrance espouses programmable access-control policies that can function with complex rules, multiple delegations, time bounds, and asset limits. Everything is enforceable inside hardware without custody transference. This is the essence of automated, private DeFi without having to give up\u00a0control.<\/p>\n Non-custodial model<\/strong><\/p>\n The term \u201ccustody\u201d is used often but not always clearly understood in DeFi. Let\u2019s compare Privana with other prevalent custody models regarding their attributes to understand the difference.<\/p>\n This redefines the concept of non-custodial. Before, in standard wallets, users had to either manually sign every transaction for safety or give up control to bots for automation, leading to potential security risks. Now, with Privana, automation and self-custody are simultaneous, with privacy ensured throughout the whole experience.<\/p>\n This does not mean that there are no trust assumptions in Privana; it only means that the trust requirements are as minimal as possible. As long as Intel SGX hardware works as designed and Sapphire\u2019s confidential smart contracts function as built and deployed, no one from Privana or Oasis\u2019s side can access or tamper with the vault\u2019s private key or override the user\u2019s policy rules. It may be useful to check out the Trust Model<\/a> page in Privana\u2019s docs for details on every assumption and its mitigation.<\/p>\n This concludes the deep dive into Privana\u2019s core concepts. Next time, I will discuss Privana\u2019s features in detail. In the meantime, let\u2019s continue the discussion in the comments section about what you think of these concepts that are the pillars of Privana\u2019s build.<\/p>\n Resources & references:<\/strong> Originally published at <\/em>https:\/\/dev.to<\/em><\/a> on September 21,\u00a02026.<\/em><\/p>\n Introducing Privana: A Deep Dive into Core Concepts<\/a> was originally published in Coinmonks<\/a> on Medium, where people are continuing the conversation by highlighting and responding to this story.<\/p>","protected":false},"excerpt":{"rendered":" Privacy in blockchain and web3 is not a default setting. Because privacy must be designed in, decentralized applications (dApps), including decentralized finance (DeFi) solutions, often lack it. As a private, non-custodial DeFi interface, Privana aims to answer this\u00a0need. Built by the Oasis team, Privana runs on Sapphire\u2019s confidential EVM runtime inside hardware-secured enclaves, better known […]<\/p>\n","protected":false},"author":0,"featured_media":230716,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-230715","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-interesting"],"_links":{"self":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts\/230715"}],"collection":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=230715"}],"version-history":[{"count":0,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts\/230715\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/media\/230716"}],"wp:attachment":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=230715"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=230715"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=230715"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}An overview of Privana\u2019s core functionality<\/h3>\n
* Privacy amplification<\/strong>\u200a\u2014\u200aEvery transaction originating from Privana has the same address\u200a\u2014\u200athat of its pooled vault. Since any user\u2019s personal wallet activity is not broadcast, no specific trade can be attributed to a specific person.
* Liquidity efficiency<\/strong>\u200a\u2014\u200aThe Privana vaults hold an inventory of commonly traded assets. As a result, internal liquidity can settle user trades instantly within the vault, eliminating the need for external transactions. This also augments privacy while being fast and cheap.
* Lower costs<\/strong>\u200a\u2014\u200aBeing a pooled model, there is no need for individual smart contracts for the users. This results in low complexity of the application, lower gas fees, and higher cost-efficiency.<\/p>\nThe three pillars of Privana\u2019s core\u00a0concepts<\/h3>\n
{
asset: “USDC”,
spend_limit: 1000 USDC\/day, \/\/ max automated spend
destination_lock: [“aave-v3”], \/\/ only this protocol
expires: 30 days, \/\/ time-bound \u2014 auto-expires
revocable: true \/\/ you can always cancel
}<\/p>\n
\/\/ No one \u2014 including Privana \u2014 can execute outside these rules.<\/p>\n
* Privana<\/a>
* Oasis<\/a>
* For specific questions or feedback, connect on the Oasis Discord\u2019s Privana\u00a0channel<\/a><\/p>\n