DEV Community: DC

Guide To Deploying A Trustless Eliza Agent With Oasis ROFL

DC — Thu, 28 May 2026 06:53:48 +0000

Oasis introduced the framework for runtime off-chain logic (ROFL) to help build and run apps off-chain while ensuring privacy and maintaining trust with on-chain verifiability. For most people, this explainer video would be enough. But for developers and dApp builders, who want to try things out themselves, a deeper dive is worth it.

In this tutorial, I will demonstrate how to build and deploy a trustless Eliza agent with Oasis ROFL.

Objective

The objective is to have a working Eliza agent running inside a ROFL Trusted Execution Environment (TEE). I will also show how to get it registered and validated as a trustless agent in the ERC-8004 registry. The agent's code will be fully auditable, and anyone can verify the authenticity of the origin of the deployed instance, which is immutable and tamper-proof.

Prerequisites

Refer to the prerequisite section in the ROFL quickstart tutorial for setup details.
So, right now, we need these to get started.

Docker (or Podman) with credentials. It can be on docker.io, ghcr.io, or any other public OCI registry.
Oasis CLI and at least 120 TEST tokens in your wallet. Since we are building in the testnet environment, you can get these tokens for free from the official faucet.
Node.js 22+. It is for Eliza and helper scripts.
OpenAI API key
RPC URL. It is to access the ERC-8004 registry (e.g. Infura).
Pinata JWT. It is to store agent information in IPFS.
At least 2 GiB of memory and 10 GB of storage.

Eliza Agent Creation

The first step is to initialize a project using the ElizaOS CLI. Next, prepare it for ROFL.

# Install bun and ElizaOS CLI
bun --version || curl -fsSL https://bun.sh/install | bash
bun install -g @elizaos/cli

# Create and configure the agent
elizaos create -t project rofl-eliza
# 1) Select Pqlite database
# 2) Select the OpenAI model and enter your OpenAI key

# Test the agent locally
cd rofl-eliza
elizaos start
# Visiting http://localhost:3000 with your browser should open Eliza UI

Containerize

In this step, you will need to containerize both the app and the ERC-8004 wrapper.
You will notice that the Eliza agent startup wizard has already generated:

Dockerfile - this packs your agent into a container.
docker-compose.yaml - this automatically configures, connects, and manages the interdependent postgres and elizaos containers.

The next step is to make some changes to docker-compose.yaml.

In the PostgreSQL section, you need to replace relative image: ankane/pgvector:latest with image: docker.io/ankane/pgvector:latest.
You need to name the elizaos image with a corresponding absolute path, e.g. image: docker.io/YOUR_USERNAME/elizaos:latest.
You need to register the Eliza agent as a trustless agent in the ERC-8004 registry using the rofl-8004 snippet. Ensure that the environment variables are mapped as is.

docker-compose.yaml

  rofl-8004:
    image: ghcr.io/oasisprotocol/rofl-8004@sha256:f57373103814a0ca4c0a03608284451221b026e695b0b8ce9ca3d4153819a349
    platform: linux/amd64
    environment:
      - RPC_URL=${RPC_URL}
      - PINATA_JWT=${PINATA_JWT}
    volumes:
      - /run/rofl-appd.sock:/run/rofl-appd.sock

The validation flow looks something like this:

Once you have edited docker-compose.yaml, it is time to build and push.

docker compose build
docker compose push

If you are looking for full verifiability, you need to pin the digest by appending image: ...@sha256:... to all images in docker-compose.yaml.

Init & Create

Once all previous steps are complete, you will find that the agent is running in a container within a TEE. In this setup, ROFL handles the startup attestation of the container and the secrets in the form of environment variables. As a result, the TEE is completely transparent to the Eliza agent app.

oasis rofl init
oasis rofl create --network testnet

You can check out on-chain activity and app details in the Oasis Explorer.

Build ROFL bundle

This is where the memory and storage prerequisites come in handy.
First, you need to update the resources section.

rofl.yaml

resources:
  memory: 2048
  cpus: 1
  storage:
    kind: disk-persistent
    size: 10000

Now, you can build the ROFL bundle by invoking this command.

oasis rofl build

Secrets

In this step, we take care of encryption. It involves:

End-to-end encrypting of OPENAI_API_KEY and storing it on-chain.
Providing the RPC_URL and PINATA_JWT values for ERC-8004 registration.

echo -n "<your-openai-key-here>" | oasis rofl secret set OPENAI_API_KEY -
echo -n "https://sepolia.infura.io/v3/<YOUR_KEY>" | oasis rofl secret set RPC_URL -
echo -n "<your-pinata-key-here>" | oasis rofl secret set PINATA_JWT -

Then comes the important step of storing the secrets as well as the previously built enclave identities on-chain.

oasis rofl update

Deploy

This completes the building of the Eliza agent. Now, we need to deploy it to an ROFL provider.

oasis rofl deploy

The Oasis-maintained provider is selected on Testnet, which rents a node for 1 hour by default. You can extend the rental period for more hours, say for 6 hours, by invoking oasis rofl machine top-up --term hour --term-count 6 command.

Test

You have successfully built and deployed your very own Eliza agent. You can test if it is running properly with this CLI check.

# Show machine details (state, proxy URLs, expiration).
oasis rofl machine show

A successful agent boot means the Proxy: section will show the URL where the agent is accessible. So, for example if it shows:

Proxy:
  Domain: m1058.opf-testnet-rofl-25.rofl.app
  Ports from compose file:
    3000 (elizaos): https://p3000.m1058.opf-testnet-rofl-25.rofl.app

In this case, the app would be accessible at https://p3000.m1058.opf-testnet-rofl-25.rofl.app.

ERC-8004 Registration and Validation

This is not an automatic step and needs to be completed to get this Eliza agent registered and validated as a trustless agent in the ERC-8004 registry. When you are running the agent for the first time, the rofl-8004 service will derive the Ethereum address for registering it. To go ahead, you will need to fund that account with some ETH to pay for the gas fees.

Use this command to fetch your app logs.

oasis rofl machine logs

The Please top it up line will show the derived address. After funding it, your agent is registered and validated, and ready to go.

Please note: All logs here are accessible to the app admin, as they are stored unencrypted on the ROFL node. So, remember not to put any private information here.

Demo

This guide shows how you can build your own agent, but if you need to check out a full-fledged demo of how it looks and works, there is an example in the official Oasis repository.
Trustless Agent Demo

For a quick chat with the Oasis engineering team for help with specific issues, you can drop your comments in the dev-central channel in the official Discord.

Key Encumbrance: The Primitive That Makes Programmable Privacy Possible

DC — Wed, 27 May 2026 08:34:18 +0000

Over the years, blockchain technology has unlocked key primitives that drive utility and adoption. Multisigs, multi-party computation, ERC-4337 (account abstraction), smart wallets, etc., have all contributed to making it more accessible and user-friendly.

But problems persist. Public blockchains mean absolute transparency and on-chain visibility, leading to constant exposure and risk of exploitation. Then there is the need to always coordinate among people to enable the "multi" aspect for security. Most of the major chains are also siloed, and interoperability is still very limited in application. Moreover, key custody is binary, making private key management both challenging and often trust-dependent. And this does not inspire user confidence or mass adoption.

Key Encumbrance

Oasis has been at the forefront of privacy-first blockchain technology and utility, and has actively supported the development of primitives to advance this.
Last year the protocol collaborated with researchers at IC3 and Cornell Tech to explore practical implementations of Liquefaction on Sapphire.

Key encumbrance is a core benefit of Liquefaction that proposes an elegant solution for the pain points discussed earlier. Here, the private key is generated inside a TEE enclave and can only be interacted with through programmable policies.
As a result, the key is completely secure and tamper-proof, with neither the end users nor the delegates nor the operators and developers ever having access to the keys.

So, when users try to sign with their keys, that is only possible when the signature request satisfies the policy conditions. Simply stated, the key never leaves the secure enclave, and the policy enforcement is end-to-end encrypted and processed only inside the enclave. Therefore, the assets linked to the key enjoy complete security and privacy, and can be moved, traded, shared, or pooled without on-chain exposure or tracking.

How It Works

The major question now is whether this is actually implementable. Short answer, yes.

The USP is adding programmable policies that must be passed before the key inside the TEE encrypts and signs the transaction on the target chain. Interestingly, this does not need a multisig solution, and a single entity can operate under multiple policy scopes.
As a practical application of this concept, Oasis has developed encumbrance-powered vault infrastructure for DeFi, bringing privacy, security, and ease of use together.

The architecture is simple, with a user interface where the application interacts with the functionality via an SDK. Any request or intent passes into the enclave, consisting of:

A policy engine
The encumbered key
A transaction executor

In this setup, the request encounters the policy engine that stores the policies in a confidential smart contract. If and when the request satisfies the policy conditions, the key signs and authorizes the request. In case the policy conditions are not met, the request fails, and there is no further action. Simply put, instead of the user accessing and potentially exposing the private key, the key remains inaccessible within the enclave, and only meeting the policy criteria triggers the smart contract to sign the transaction.

This system becomes particularly powerful when other chains are involved. Even though Oasis has its own network, users do not need to deposit the assets to Oasis, which simplifies interoperability. The assets are stored in a confidential container where the users can generate wallets for target chains and sign with them over programmable policies. So, the user assets stay where they are, while Oasis functions as the ultimate security layer.

Why Encumbrance? Why Not Multisig?

Multisigs have been useful for a long time, but come with limitations.

Every action lives on-chain
Users are locked to a single chain
No action is possible without coordination and a quorum
Enforcement needs a dedicated contract
Delegation entails adding/removing signers, which also requires authorized signatures

Key encumbrance does away with these limitations.

Adding or revoking access can be done by updating a policy. As the keys are never shared and truly private, the rules are enforced only through the policy engine.

The programmable policies are the definitive point of difference, making encumbrance a groundbreaking and powerful primitive for future utility and user convenience. In practice, these policies come with tangible capabilities and benefits.

Non-custodial automatic execution. If an asset's price threshold is breached, the enclave verifies with the policy condition, and the key signs a trade/sell. Neither manual approval is needed, nor is there a need for a bot with private key access.
Composable policy chains. Multi-chain functionality is in-built. So, profit from a sale or trading into a stablecoin can be routed to a different chain where it can earn passive yield - the entire process is maintained by using the policy engine without manual intervention or signing.
Scoped bot access. By adding policies to an encumbered key - it can be anything, such as assigning a dollar value threshold, specifying transactional time windows, or assets whitelisted with pre-set criteria, bot usage can be streamlined. Here, the bot will access the signature via an API without ever having key access.
Delegation without quorum. Policy access can be programmed to have an expiry date of 30 days. With no key sharing, and keys managed and enforced inside TEEs, no human coordination or quorum criteria are needed.
Session-based gaming. Application in gaming and related use cases where policy can pre-determine a threshold and time window, and handle signatures accordingly without needing to leave the game to approve transactions.

Final Takeaway

Current user experience in the blockchain and web3 space is riddled with poor key management and compromised access control. Encumbered keys make it possible for the next generation of applications to integrate programmability, privacy, and permissionless utility.
The proof of concept is already under development by Oasis using its own tech stack and primitives - private DeFi with Privana.

Further reading: Primitives by Oasis

How To Enhance Your App With Oasis ROFL: A QuickStart Tutorial

DC — Wed, 22 Apr 2026 14:34:03 +0000

I have mentioned the Oasis ROFL (runtime off-chain logic) framework on several occasions. For most people, this explainer video would be enough. But for developers and dApp builders, who want to try things out themselves, a deeper dive is worth it. In this guide, I will give a quick introduction to ROFL and then share a QuickStart tutorial to help build a ROFL-powered app.

ROFL in a nutshell

The ROFL architecture consists of these distinct components: the hardware, the application, the remote attestation, the blockchain layers, and user interaction.

Further, this 5-part process lays out how ROFL works.

From a developer's perspective, ROFL-powered apps run on Oasis nodes inside a Trusted Execution Environment (TEE), managed through the protocol's unique production-ready EVM runtime - Sapphire.

When you use ROFL, you get the following support:

Docker-like containers or single executable apps, based on what Trusted Compute Base (TCB) you are using, and what your threat model is
Intel SGX/TDX ensures privacy and integrity, and also provides a full update history and auditability
Your app is registered, managed, and deployed on a permissionless pool of ROFL nodes, which means it is not censorable
There is a built-in Key Management Service (KMS) that stores your app's secrets as well as secures key derivation inside the TEE
Verifiable ROFL transactions originating from integration with Oasis Sapphire that enable EVM-compatible confidential smart contracts

Moreover, you don't need to build from scratch - you can just wrap your existing app into a ROFL-powered app. Let's see how.

QuickStart

There are 5 steps to enhance an app with ROFL power:

Initialize the ROFL manifest
Create a new app on blockchain
Build a ROFL bundle
Encrypt secrets and store them on-chain
Deploy your app on a ROFL node

Prerequisites

Containerized App
First thing you need is a containerized app with a downloadable Docker-like image. Any public Open Container Initiative (OCI) repository works; however, you might like to choose from Docker or GitHub container registry.

If your app is not already running inside a container and you don't know how, follow this step-by-step mini tutorial.

Oasis CLI
Next, you need the latest version of the Oasis Command Line Interface (CLI). Install it from here.

Tokens
Lastly, you will need about 150 tokens to cover ROFL registration, renting a machine, and paying for the gas fees.

Now, you can either create a new account or import an existing one. Let's check out both processes.

Create a new account ->

oasis wallet create my_account --file.algorithm secp256k1-bip44

Later, you can choose to import this account to Metamask or other Ethereum-compatible tooling, e.g. Hardhat.

Import an existing account ->
You need to export the secp256k1 private key or mnemonic from your existing wallet before running this command:

oasis wallet import my_account

Note: If you are working in a test environment, you can get free testnet tokens from the official faucet.
If you are building on the mainnet, you will need to buy ROSE tokens.

Initialize

This is the first step. You start by running oasis rofl init using compose.yaml inside your app folder. This will generate the ROFL manifest in the form of rofl.yaml.

oasis rofl init

Now, based on your requirement, you can change the memory, specify the number of cpus, and the root filesystem storage section that comes under resources.
rofl.yaml

name: my-app
version: 0.1.0
tee: tdx
kind: container
resources:
  memory: 512 # in megabytes
  cpus: 1
  storage:
    kind: disk-persistent
    size: 512 # in megabytes
artifacts:
  firmware: https://github.com/oasisprotocol/oasis-boot/releases/download/v0.6.2/ovmf.tdx.fd#db47100a7d6a0c1f6983be224137c3f8d7cb09b63bb1c7a5ee7829d8e994a42f
  kernel: https://github.com/oasisprotocol/oasis-boot/releases/download/v0.6.2/stage1.bin#e5d4d654ca1fa2c388bf64b23fc6e67815893fc7cb8b7cfee253d87963f54973
  stage2: https://github.com/oasisprotocol/oasis-boot/releases/download/v0.6.2/stage2-podman.tar.bz2#b2ea2a0ca769b6b2d64e3f0c577ee9c08f0bb81a6e33ed5b15b2a7e50ef9a09f
  container:
    runtime: https://github.com/oasisprotocol/oasis-sdk/releases/download/rofl-containers%2Fv0.8.0/rofl-containers#08eb5bbe5df26af276d9a72e9fd7353b3a90b7d27e1cf33e276a82dfd551eec6
    compose: compose.yaml

Create

The next step is to create a new app on-chain. You can use the oasis rofl create command for this.
Please note that any newly created app in this process is registered by default on the Sapphire mainnet. If you are using a test environment, you will need to change the setting. So, you will be required to pass --network testnet parameter.

oasis rofl create --network testnet

The check whether this transaction was successful is to find your app on the Oasis Explorer.

Build

In this step, we will build the ROFL bundle.

oasis rofl build

This command results in the generation of a new .orc file inside your project folder.

Secrets

This is the step where privacy is enforced. So, if there are environment variables that your app is using, you can store them on-chain privately using the oasis rofl secret command. It would look like this:

echo -n "my-secret-token" | oasis rofl secret set TOKEN -

This command populates the TOKEN secret. You can now use it in your compose file like this:
compose.yaml

services:
  python-telegram-bot:
    build: .
    image: "ghcr.io/oasisprotocol/demo-rofl-tgbot:ollama"
    platform: linux/amd64
    environment:
      - TOKEN=${TOKEN}

If you want to submit the secrets and the ROFL bundle information on-chain, you can do so with the oasis rofl update command.

oasis rofl update

Deploy

This is the final step of the process. Here, you use the oasis rofl deploy command so that your app gets deployed to a ROFL provider.

oasis rofl deploy

The command triggers the bootstrapping of a new machine that fits the required resources provided by Oasis. You can check the status of the machine using the oasis rofl machine show command.

Oasis rofl machine show

You can now also check your application logs to verify how everything works. You will need the oasis rofl machine logs command for this.

oasis rofl machine logs

Parting words

If you are a developer who likes the hands-on approach, I hope you had a good time trying out this tutorial and successfully deploying your first ROFL-powered app.
You will note that in this guide, I have provided several links to the Oasis documentation instead of elaborating on them.

containerize your app
latest Oasis CLI release
oasis rofl init
oasis rofl create
oasis rofl secret
oasis rofl update
oasis rofl deploy
oasis rofl machine show
oasis rofl machine logs

That's because I wanted to focus on the topic here without going into details on these commands, which require separate attention, and I will prepare other tutorials explaining them later on.

For a quick chat with the Oasis engineering team for help with specific issues, you can drop your comments in the dev-central channel in the official Discord.

Need Truly Secure Digital Storage? The Answer Is Decentralized Storage + Privacy Layer

DC — Mon, 20 Apr 2026 10:42:08 +0000

As our digital footprints expand, our data floats around the internet, unsupervised and unprotected. Cloud storage is a practical solution, but it does not focus on data security. Moreover, you no longer truly own your data. This is the pain point that decentralized storage tries to tackle. But privacy is not automatic, even in decentralized systems. An intentional architecture with privacy-by-design is the only answer.

Defining Decentralized Storage

Traditional cloud storage uses location addressing. Here, the uploaded files, when they need to be accessed, can be retrieved from specific server URLs. In case of server outage or authorities implementing a takedown, the links stop working, and data becomes inaccessible, maybe lost forever. Now, some context: almost two-thirds of the global cloud infrastructure is currently handled by the Big 3 - AWS, Azure, and Google Cloud.

This data concentration is what decentralized storage evolved to solve. Here, the content of the files is identified by cryptographic hash generation. This is a unique digital identifier and, being decentralized, there is no dependence on a single server. All nodes in the system will always produce the same content, thereby securing the data and its integrity.

Top Decentralized Storage Protocols

All the protocols dealing with decentralized solutions have different approaches to digital storage. Let's take a look at the top 5 - IPFS (InterPlanetary File System), Filecoin, Arweave, Storj, and Sia.

IPFS - This is the earliest solution in the form of peer-to-peer (P2P) protocol. Every uploaded file is broken into blocks, cryptographically hashed, and organized into a Merkle DAG. These generate a unique Content Identifier (CID) for the file, which can be accessed thanks to any of the 20k+ active peers in the IPFS public network. However, this does not guarantee data perpetuity, as none of the nodes may commit to storing the file over time.
Filecoin - This tries to solve the problem of persisting data by rewarding the nodes. It adds an economic incentive layer to IPFS. Two cryptographic proofs enhance the system. Proof-of-Replication verifies the storage provider has created a unique physical copy of the data, while Proof-of-Spacetime then continuously audits the provider to verify that they still hold the data over time. Filecoin stores almost 1,110 PiB of data, with clients that include the Smithsonian Institution and the Internet Archive.
Arweave - This is the next-level solution. One-time payment funds a storage endowment that pays out to the storage providers gradually over 200 or more years, assuming a declining storage cost of at least 0.5% annually. Here, a "blockweave" structure links each new block to both the previous block and a randomly selected older block, incentivizing historical data storage. Arweave processes over 30 million transactions daily out of approximately 300 million data requests per day.
Storj and Sia - These specifically cater to privacy-oriented decentralized solutions. Storj encrypts all data with AES-256-GCM. It is then sharded into 80 pieces and distributed among independent nodes. Any 29 out of 80 pieces coming together retrieves the data. For Sia, the sharding is in 30 pieces, and reconstruction needs only 10 pieces, with on-chain smart contracts enforcing the model, and performance review maintaining host standards.

Centralized Systems Lack Privacy

Privacy failure is a constant threat in traditional cloud solutions, as the data handled in centralized data centres is huge and unwieldy, making it vulnerable to hackers and ripe for government tracking.

According to an IBM report, the global average breach cost, especially in cloud environments, is close to the $5 million mark. It slightly improved in the 2025 report, but healthcare continues to remain the top vulnerable sector, and breaches originating in the US alone crossed the $10 million mark.

Legally authorised surveillance, typically without users' knowledge, combined with the ease with which providers can censor or erase data, makes true ownership an illusion.

5 Layers of Privacy In Current Decentralized Systems

Decentralized storage that includes privacy mechanisms offers a solution to the problems posed by centralized systems.

Client-Side Encryption - Here, the data is encrypted in the user's device before being uploaded to the network. Storj and Sia do this automatically, but users of IPFS, Filecoin, or Arweave need to do it themselves. Centralized systems like AWS also encrypt data, but they own and hold the keys. Decentralized solutions give the key to the data owner upon encryption, which translates into no key, no data. But it also eliminates data loss through backdoor access.
Sharding - Here, the information in the encrypted files is split and shared across nodes in multiple locations. Individual hosts can view only the encrypted fragment stored with them. The data owner has sole access to the information, which is reconstructed together with the decryption key and the minimum number of fragments.
Erasure Coding - Here, the user data is secured through resilience and redundancy without storing complete copies. So, in the case of the Storj model, 51 nodes (63% of the shards) can go offline simultaneously, and still, data can be retrieved. It is more efficient than three-copy replication without adding to the storage overhead.
Encryption in Transit and at Rest - Here, Transport Layer Security (TLS) is used to protect the encrypted data as it moves between user devices and storage hosts. Encryption at rest also enhances data protection, so even if the physical device is stolen, the information remains unreadable. It is often combined with client-side encryption to ensure maximum data security.
Zero-Knowledge Proofs (ZKP) - ZKP enables the storage providers to prove data storage without revealing the data itself. For example, Filecoin uses Zero-Knowledge Succinct Non-Interactive Arguments of Knowledge (zk-SNARKs) to cryptographically prove the presence of information without exposing the content.

Privacy Gaps That Privacy-Preserving Blockchains Solve

Decentralized storage without privacy-by-design is not truly secure, despite its advantages.

For example, IPFS, being the foundational protocol, is most at risk. Anyone who knows a CID can access the associated file. Besides, the CIDs, being deterministic, can be tracked.
Same problem with Filecoin, which also uses the IPFS model. In addition to the risk run by unencrypted files, it is vulnerable to traffic pattern analysis due to publicly available metadata.

Arweave's perpetual data storage has its own risk - immutability. Unencrypted data is exposed forever; encrypted data is only secure with current encryption standards and is breakable with future advancements in cryptography and quantum computing.

The answer lies in adding a privacy layer to the decentralized storage concept.
Result: users can enjoy cheap, persistent, censorship-resistant data hosting services, with the privacy layer managing encryption keys and authorization logic, and also providing access control in a confidential environment.

Oasis provides a unique and substantive solution, adding programmable privacy and access control policies to traditional decentralized storage.

Trusted Execution Environments (TEEs) ensure data is encrypted at both input and output states, and any decryption and processing happens only inside the protection of hardware-isolated secure enclaves. So, a confidential smart contract is applied to the storage and runs on Oasis Sapphire. The TEEs hold encryption keys and access policies in a private state. The decryption key is accessible only for authorized users who have been verified inside the enclave. This effectively rules out any interference from node operators, storage providers, or validators.

The access issue is handled by implementing the Liquefaction primitive. It is a level up from standard access control. Anyone can thus see access being granted or denied, but they will not know why. As a result, it is impossible to game the conditions and manipulate access.

Oasis is, however, not the only protocol that is working on a privacy-focused infrastructure. Lit Protocol also provides decentralized key management through threshold multi-party computation.

Here is how plugging the privacy gaps works.
First, implement client-side encryption using keys managed by a privacy layer.
Next, upload the encrypted data to a decentralized storage protocol.
Then, register the CID and key metadata inside a confidential smart contract with clearly defined access policies.
Finally, the result is a system where the privacy layer verifies and authorizes access requests inside a TEE or multi-party computation network.
Bottom line: Data is encrypted, on-chain but confidential, and access is controlled, so no data exposure even if anyone somehow procures the CID, thus mitigating the risk of a single point of failure.

Real-World Use Cases

NFT metadata - One of the first mainstream utilities. Solved broken hosting issues common to centralized servers. Case in point, in 2025, over 12k NFTs were delisted. Now, Solana’s Metaplex framework uses Arweave as the default storage option, benefiting over 10k NFTs. Also, Yuga Labs migrated Bored Ape Yacht Club (BAYC) metadata away from centralized cloud to IPFS.
AI and data infrastructure - The fastest growing segment. Filecoin’s Onchain Cloud launched as an official alternative to AWS for AI workloads. Also, Arweave’s AO hyper-parallel computing layer handles permanent data storage and computation of decentralized AI agents.
Healthcare - One of the highest stakes for private digital data storage. Examples include projects like BurstIQ, Medicalchain, and Patientory using IPFS for encrypted patient data storage and blockchains for access and audit purposes. Also, Estonia’s national healthcare system uses blockchain-based infrastructure for record integrity.
Financial data - Another high-stakes private digital data storage. Decentralized finance uses confidential computation and encrypted data for better privacy without needing a complete overhaul of existing architecture.

Final Takeaway

IPFS, Filecoin, and Arweave are better than traditional cloud systems in terms of censorship resistance, redundancy, and data integrity, and still, they are too public. Client-side encryption and sharding (Storj and Sia), ZKPs (Filecoin), and confidential access control (Oasis and Lit Protocol) provide viable privacy solutions for the future decentralized storage systems.

Decentralized storage holds the key to secure digital storage of the future. The solution is production-ready, and awareness is the only missing piece of the puzzle. So, next time you go looking for truly secure digital storage, you know which door to knock.

Agentic Economy With x402 Gets A Boost From ROFL's Verifiable, Private Compute Layer

DC — Mon, 23 Mar 2026 06:15:16 +0000

Autonomous AI agents can do a lot of things, but for a long time, internet-native payments were out of their purview. So, when I first learned about x402, I was intrigued by the possibilities. But the privacy-first blockchain, Oasis, raises an important question: Is the agentic economy adequately addressing verifiable privacy?

In this piece, I will explore x402, the value added by ERC-8004 in this context, as the standard for agent discovery, and the role Oasis's expertise in offering verifiable privacy with off-chain compute and on-chain trust can play.

x402 101

Let's start with some context. x402 is not a recent discovery related to web3 or AI. It pre-dates even the privacy narrative, going back to those days when the internet (also known as web2 in web3 terminology) was still using "HTTP" rather than "HTTPS". The code 402 simply designated 'payment required'.

The code was a stepping stone to internet-native payments, heralding a future in which servers could charge per request. But as long as online payment was not viable beyond theoretical discourse, this remained practically unused.

How does web3 fit in this conversation? The answer lies in what web3 made possible. Stablecoins, sub-second settlement, no chargebacks, and scalable blockchain protocols have become quite the norm. This is when HTTP 402 can evolve into x402. This ensures an open standard, enabling web2's request-response loop and allowing any service to charge for API or content access over HTTP.
Result: zero dependency on traditional accounts, sessions, or credentials.

It is interesting to note how awareness of x402 emerged in the cryptoAI space. It was triggered as a ERC-8004 utility. There is a close correlation between x402 and ERC-8004, enabling autonomous agents to trustlessly discover and transact. I will revisit this later.

x402 Functionality

So, how does x402 work? You start with a human/agent client, a server with the desired resource, and a facilitator (infra for payments). The following steps then unfold.

A request is made to a server, which could be anything, such as an API call or a piece of content
This resource needs to be paid for
The server responds with an HTTP 402 code
The code comes with payment instructions, specifying the token type, the amount, the network, and the destination address
The client-side wallet reads the 402 response and generates a signature authorizing the payment

The variation in this process would depend on whether the client is human or an agent.

If human, a pre-programmed policy in the wallet's smart contract can eliminate the need for manual signature steps.
If an agent, a pre-programmed policy in the wallet's smart contract can ensure that pre-set limits and rules are obeyed.

An overview of the process flow (source: https://docs.cdp.coinbase.com/x402/core-concepts/how-it-works):

Key Takeaways

Signature uses the transferWithAuthorization function (EIP-3009). This means the client doesn't need to manage gas and private keys. This permission transaction, combined with a facilitator, enables seamless client sign-off on the transfer. Since anyone can submit it to the blockchain, the facilitator plays that role here.
The client's signed payment goes back to the server. There are a few steps before trust is established. First, the signature is forwarded to the facilitator's /verify endpoint. Then, the signature's legitimacy is authenticated. Next, the facilitator's /settle endpoint executes payment transfer. Finally, with all these steps complete, the server responds to the client's resource request.
This entire sequence of events occurs within a second or less with x402, ensuring smooth, composable payments. For the client, it is a simple HTTP code; for the agent, it is another API call.

x402 In Practice

Universal design -> seamless UI/UX. x402 uses HTTP's standard operating procedure (SOP). So, there is no need to add additional tools or software development kits (SDKs) when integrating with existing infrastructure.
Web2-native. Since x402 uses HTTP's SOP, it is also compatible with every major programming language, framework, and hosting platform on the internet. The seamlessness of web2 is thus replicated in web3.
Lightning-fast settlements. Payment authorization only involves a single request-response and is completed in sub-seconds. The settlement is asynchronous and has instant finality, with the server trusting the facilitator for on-chain execution.
Micropayments. Pricing granularity and tiny charges are made possible thanks to the zero-fee protocol and extremely low-cost transactions that only comprise of gas fees for the facilitator.

Traditional solutions are closed systems, needing constant customization every time the platforms or API providers change. This is exactly the pain point x402 solves.
Additionally, x402 enables micropayments, which were problematic earlier when everything would be bundled, by default, with subscriptions. Live example of the benefit includes pay-per-crawl APIs, where agents pay nano-payments to scrape content.

Another crucial advantage of x402 is understood when we consider how this protocol can logically extend its functionality with agents on both sides of the request-response pairing.
All this leads to setting up a new agentic future involving an autonomous agent economy. Consider this:

Agent 1 queries the data API, then hires Agent 2 to process the output, while paying a compute node to run simulations.
Zero human intervention needed at any stage of the process.
No restrictions by traditional payment rails.
Result: All transactions conditional (payment only when valid response) and composable, running at thousands of fractional payments per minute/hour.

x402 x ERC-8004 x ROFL

The potential of x402 grows when integrated with other crypto primitives.

As I mentioned earlier, x402 and ERC-8004 share a connection. X402 standardizes agentic payment, and ERC-8004 standardizes agentic discovery and introduces the need-for-trust factor. This is a critical factor we need to examine, as the data is exposed no matter what, whenever there is API access or inference.

The agentic trust gap is solvable.

We know that ERC-8004 gives us the agent coordination/discovery layer, involving on-chain registries for identity, reputation, and validation, but it is neutral about establishing trust. The solution comes from the Oasis ROFL (runtime off-chain logic) framework for trustless compute, providing data privacy, decentralized key management, and verifiable, tamper-proof execution.
Together, the setup ensures code verification, key isolation, and end-to-end confidentiality.

As we have seen in this x402 discussion, the facilitators play an important role. ROFL offers the opportunity to move away from highly centralized and opaque facilitators to a decentralized trustless TEE cloud for running the x402 facilitator. This can ensure that the payment layer is decentralized and verifiable even as the entire stack operates without extra, unnecessary trust assumptions.

Check out this example of a live public testnet deployment of a trustless and verifiable facilitator. There is also a sample implementation including a document summarization service that runs Ollama inference inside an ROFL container. And then there is a demo using multiple LLM models with cross-validation for oracle consensus. All of these being open-source, anyone can replicate or tweak for further developments.

So, what is the final takeaway? x402, ERC-8004, and Oasis ROFL each solve a distinct layer of the agentic stack. Together, they make a trustless, private, composable agent economy not just conceivable but ready to be developed.

The Flashback Labs Case Study On Privacy-first AI Training

DC — Fri, 20 Mar 2026 07:27:08 +0000

Our interactions with AI and our shared experiences are growing exponentially. We know AI needs extensive training for all this, but how much thought or effort is put into ensuring data privacy?

Oasis, as a privacy-first blockchain, has taken essential steps in bringing confidentiality to decentralized AI (DeAI). So, no wonder that Flashback Labs adopted the game-changing technology of runtime off-chain logic (ROFL) to integrate verifiable privacy into their AI training setup. The result of that collaboration is the basis of this case study.

Decoding Flashback

Flashback Labs helps train AI to understand people through lived human experiences. On their platform, a conversational AI app, people can interact with the AI to talk about their lives and preserve memories.

How this works is: say you type in a prompt with a personal piece of conversation, or run a stream-of-consciousness with a voice assistant. The chatbot, like any other conversational AI model, will pick up the cue and ask follow-up personal questions. The data that flows as a result is structured around you personally - places, emotions, and timelines.

The Flashback app can then generate a short animated video from your inputs, using photos, text, and voice narration like a call-back memory. As you go through multiple sessions, a sort of graph forms in the AI database, and the more you use it, the more enriching your personal experience becomes.

Flashback x Oasis

Flashback's platform deals with extremely sensitive information, from personal memories to relationships, even health-related or finance-related conversations, as a personalized experience is directly dependent on personal shares with the app. It is, therefore, critical that there is implicit trust.

Opaque systems or even fully transparent decentralized solutions are ill-equipped to handle this.
Oasis enters the equation here by becoming the encryption layer and plugging the trust gaps.

The result is both elegant and crucial. Now, all the inputs ever made into the platform - photos, videos, stories, etc, are wallet-owned, processed and secured by TEEs (trusted execution environments), and stored on-chain after being consented to by the user.

Now, let's look at the AI training aspect. It entails dealing with massive datasets and processing them. Flashback uses 0G, BNB Greenfield as storage networks, but they do not offer data privacy. Oasis provides the ideal confidentiality solution to encrypt the data files before storing them. Users can verify on-chain that their encrypted data is safe and secure.
Interestingly, Oasis has also been developing a dedicated solution for privacy-enabled decentralized storage with programmable access control, which the ecosystem urgently needs.

Scaling Progress

Flashback Labs has focused little on marketing hype or gimmick. Still, their initiative has struck a chord and fuelled a wide response and active participation. Some of the key milestones achieved include:

more than 1k users with close to 1k early contributions
3k+ on-chain, encrypted files at the rate of almost 200 per day
almost 10k on-chain transactions generated at the rate of almost 700 per day

The metrics, growing as more users come in, tell a clear story - private AI is getting scaled.

Flash Forward: What Future Promises

The case study of Flashback Labs and its success is a huge step forward for DeAI, as its target is the mainstream audience, and its use cases are not part of traditional crypto utility.

At the moment, as Flashback goes through its roadmap for 2026, the team has multiple products underway. One is related to Alzheimer's care, while another is a product developed in collaboration with notable bereavement non-profits in the US to help people cope with the process of loss of a family member.

There are also plans to develop an agentic framework that empowers Flashback's AI rendering to proactively reach out to users for memory collection and preservation. Hardware integration, like in robotic companion devices, to assist in hospice and elder care settings, is another promising development.

The bottom line: personalized AI is going to be more and more an integral part of our memorable experiences, and the data confidentiality that this undertaking must assure is non-negotiable, both during training and in storing the processed data. And, Oasis is the industry expert for this solution - verifiable privacy.

Do You Vibe Code? A DeAI Primer By Oasis

DC — Wed, 18 Mar 2026 07:40:56 +0000

AI integration is moving fast, and the accessibility to develop AI is becoming easier by the day. The decentralized AI (DeAI) space has also picked up momentum as the new-gen web3 solutions all come with an AI edge. So, if you are a web3 developer, it is no longer imperative that you be a Solidity expert or know the ins and outs of building on-chain applications. Vibe coding is your friend.

In this guide, I will show you new tools and help you learn how to build with AI on Oasis, with privacy by default. We will be using an llms.txt file, a Context7 MCP integration, for the purpose of this tutorial.

AI context

AI is prone to forgetting, and its way of remembering needs some understanding. To understand AI memory and context, check out this Oasis Academy course.

Suffice it to say, large language models (LLMs) need context to respond to any prompts, especially when you are asking them to build something. So, patchy memory or outdated context might result in a code that looks correct on a quick review but fails in practice. There are two possible solutions so that the AI tool can directly access Oasis docs to correctly consult instead of hallucinating, and I will outline them both.

llms.txt
Model context protocol (MCP)

llms.txt

For anyone familiar with AI, this is a standardized file format. It functions like a sitemap and is specifically designed for AI so that it can access a project's documentation as a structured index. It provides a brief description of the documentation and links to detailed markdown files for the AI to find and read.

For our purpose, we will be referring to these files:

https://docs.oasis.io/llms.txt — a curated index with page titles, descriptions, and URLs
https://docs.oasis.io/llms-full.txt — the complete documentation content consolidated in one file

If the AI supports project context, such as Cursor's docs feature or a CLAUDE.md file, good. Alternatively, copy-pasting the URLs in the LLM chat directly works too.

The usefulness of having two versions is dictated by AI memory and context limits. llms.txt is designed for a quick overview, and llms-full.txt is when you need the AI to know everything, unabridged.

MCP

MCP is an open standard. If you don't use MCP, then AI will only read the prompt submitted at face value. Using MCP not only gives AI structured access to all external context - documentation, codebases, tools, and runtime information- but also enables the AI to refer to them on demand and query external tools if and when needed.

As mentioned earlier, Oasis documentation is indexed on Context7, an MCP server that serves docs to AI coding assistants. The library ID is llmstxt/oasis_io_llms_txt.

Setting Up

I will show here Cursor and Claude as primary tools, as they are the most popular among vibe coders.

Using Cursor

The first step is to add the following snippet to your .cursor/mcp.json:
json

{
  "mcpServers": {
    "context7": {
      "url": "https://mcp.context7.com/mcp"
    }
  }
}

This will prompt Cursor to connect to Context7. So, now when you generate code, you will have full access to the Oasis documentation.
Pro tip: It is advisable to add a rule to your Cursor settings so that the AI always consults the Oasis docs. It can be phrased like this - Always use Context7 MCP with library ID llmstxt/oasis_io_llms_txt for Oasis documentation reference.

Using Claude

Run:
bash

claude mcp add --transport http context7 https://mcp.context7.com/mcp

The next step is to verify configuration is correctly done:
bash

claude mcp list

When you see context7 listed, you are good to go.
Pro tip: The same rule applies for your project's CLAUDE.md - Always use Context7 MCP with library ID llmstxt/oasis_io_llms_txt for Oasis documentation reference.

Other AI tools

Even though Cursor and Claude are popular choices, you may be using other AI tools such as VS Code, JetBrains, Windsurf, Zed, etc. Context7 supports 40+ clients, and you can refer to the full list here to check the setup instructions specific to your tool of choice.

Before We Start

If you are set up, there are still a few things you will need before starting to vibe code.

Node.js: This is required for Hardhat. You can check if your terminal has it installed by running node -v. It will show a version number, if it is already available. If not, download the LTS version from https://nodejs.org/en, install it, then reopen your terminal and recheck to confirm successful installation.
Wallet: Since we are working with DeAI, you will need a wallet with its private key.
If using CLI, refer to this: https://docs.oasis.io/build/tools/cli/wallet. The best approach is to create a new MetaMask wallet.
Testnet tokens: You will need testnet tokens, too, in the wallet to proceed with your vibe coding. First, you need to add the Sapphire testnet to your MetaMask wallet. You can then request free TEST tokens from https://faucet.testnet.oasis.io/. Remember to select Sapphire from the network dropdown and provide the wallet address created above.

Example: Deploying a Confidential Smart Contract

I will use a basic example here to demonstrate how this will all work. Once you have connected your Integrated Development Environment (IDE) with the Oasis MCP, start a fresh project. Let's use this prompt:

Create a confidential smart contract on Sapphire with Hardhat. It should store a secret message that only the owner can set. Anyone can submit a guess, but the actual secret should never be visible on-chain.

Your chosen AI tool will immediately pull the documentation and perform the following steps seamlessly:

Identify the correct Hardhat config.
Infer that the contract state on Sapphire is private by default.
Generate a working contract with a full project structure, including a deploy script, interaction examples, and tests.

Note that Claude will ask for permission before running commands. So, you might want to select "don't ask again" if you prefer.
There will also be a .env.example file generated in the process. You need to copy it to .env and add your wallet's private key.

cp .env.example .env

For those developers who are new to the decentralized setup, the private key can be found on your MetaMask wallet account with these steps: click the three dots next to the account name → account details → reveal private keys → enter password.
This private key will have to be added to the .env file as PRIVATE_KEY=0x..., and then deployed:
bash

npm run deploy:testnet

When you see a contract address returned in your terminal, it confirms the successful deployment of a confidential smart contract live on the testnet, using just the prompt mentioned at the start of this segment.

You can further test the confidentiality of the contract when you try calling eth_getStorageAt on your contract at Oasis Explorer.

As Oasis enables verifiable privacy and confidential computation, this is the gateway to developing private applications. You can start exploring the possibilities at https://oasis.net/ and start vibe coding to build the next-gen dApps. With your AI coding tool connected to the docs, it will be the model doing all the work.

Sources referred: https://docs.oasis.io/build/tools/llms/
Help needed? Ask the dev team: https://oasis.io/discord

AI Has a Memory Problem. Decentralization and Privacy Might Have a Solution. Part 3

DC — Mon, 23 Feb 2026 11:26:51 +0000

In the first part of this 3-part series, I covered AI memory and its classification, while in the second part, I discussed in detail the types of AI memory and security risks associated with the architectures.
Here, I will refer to Oasis technology for a potential solution to AI memory pain points through the decentralization and privacy approach. I will also talk about some working use cases for portable AI memory.

Zero-Trust and DeAI Solutions

There are two distinct pain points of the AI memory architectures: security threats, and data silos and redundancy.

As a believer in decentralized AI (DeAI), I think the solution to attack risks is best addressed by security-first architectures that adopt a Zero-Trust model.
How does this work? Basically, all data is monitored at the ingestion stage, and any sensitive information is identified and redacted before it moves to the vector storage phase. Role-Based Access Control (RBAC) and Attribute-Based Access Control (ABAC) are enforced at the retrieval layer. Result: the system only considers document subsets that the specific user is authorized to see.

Now, what about the other pain point - information silos and redundant work? Simple answer: it is preventable. Let's understand how, with reference to the multi-agent collaboration we discussed regarding stateful memory loops.
DeAI ensures a shared workspace allowing different agents (for example, an Architecture Agent and an Implementation Agent) to work in tandem, querying and updating the same memory instance. This is also the seed for AI context flow, where data silos do not result in context loss.

Role of Confidential Computing and Oasis Tech

A serious bottleneck in ensuring secure AI memory is protecting the data being computed. Traditional encryption can handle data at rest and in transit. But what about the information that is decrypted during the actual retrieval and inference processes?

Hardware-Backed Privacy via TEEs

Confidential Computing is the answer to this security gap, utilizing hardware-backed Trusted Execution Environments (TEEs). The secure enclaves isolate memory as the content is made cryptographically inaccessible to any unauthorized access, even by the infrastructure operators. For the AI systems, the prompts and embeddings are only decrypted inside the enclave's black box. As a result, the vector searches and inference building can occur smoothly without exposing any raw data.

The reason to use Oasis technology as a reference to a potential solution for secure AI memory is how it combines and optimizes on-chain and off-chain components - the first production-ready confidential Ethereum Virtual Machine (EVM), Sapphire, and the Runtime Off-chain Logic (ROFL) framework. By utilizing hardware isolation (Intel SGX/TDX), it is ensured that transaction inputs, return values, or the internal state of the smart contract remain confidential at all times.

For complex AI memory systems requiring computation-heavy processing, Oasis utilizes the ROFL framework instead of wholesale on-chain logic. So, model training and inference can be done securely off-chain while verifiable settlement can happen on-chain. This combination is the foundation for trustless AI agents that can manage private keys and sensitive user context within a secure enclave. The personal information and sensitive data consequently become a portable, secure asset.

Industry-Specific Implementations of AI Memory

What AI memory architectures need vary across regulated industries needing dynamic blueprints for solutions. Let's talk about healthcare and finance as the two most highly impacted areas.

Healthcare

Here, AI systems must adhere to strict standards like the Health Insurance Portability and Accountability Act (HIPAA) and Health Information Trust Alliance (HITRUST) to protect electronic Protected Health Information (ePHI). Such a memory architecture must include:

Zero-Retention Architectures: Data is isolated and cannot be reused for any other training purpose. A volatile memory approach is ideal where data is processed in-memory and immediately discarded.
FHIR-First Data Foundations:The Fast Healthcare Interoperability Resources (FHIR) standard helps create a standardized operational data layer. This eliminates schema chaos and enables AI assistants to retrieve clinical facts using a shared, consistent language.
Auditability and Explainability: Verifiable audit trails for agentic workflows ensure that we know which medical databases were accessed and why. This is critical for regulatory compliance.

Finance

Here, there needs to be a fine balance between collaborative analytics and exposure to private and proprietary data through transparency.

Secure Multi-Party Computation (SMPC): An example would be where multiple banks are analysing transaction data for fraud detection, but no single institution can access another’s private customer records.
Homomorphic Encryption: Financial institutions use this to perform computations directly on encrypted data, ensuring that sensitive financial parameters are never exposed during processing.

Working Use Cases

There are already a few companies that are working on solutions for AI memory problems and tackling how to implement portable memory systems.

Plurality is developing the Open Context Layer. It allows users to autonomously store their data and chats in specific memory buckets for better context management, and also for sharing.
MemSync is building the Unified Memory Layer. It allows users to create a persistent “digital twin” based on personalized conversation and knowledge. This enables the AI system to know the user, track their evolving ideas, and serve as a private sounding board for reflection and decision-making.
Ekai is offering a developer-focused solution. It allows users to switch among various AI models via smart model routing without context loss.

Final Takeaway

The future of AI memory? A portable context model. This means that you, as a user, are not obligated to commit to a single model or AI assistant, or have your digital history trapped in large platforms like OpenAI or Anthropic. When you move and switch as you need and choose, the memory travels with you, encrypted and under control, working like a neutral, interoperable memory layer.

Realizing this vision requires a fundamental reimagining of memory as infrastructure. We can combine stateful memory loops, DeAI, and confidential computing technologies like Oasis ROFL and Sapphire to build AI systems that are smarter and personalized while also being fundamentally secure and user-owned. Result: Private, portable AI memory that is a sovereign asset, free from data privacy liability.

Resources referred:

AI Has a Memory Problem. Decentralization and Privacy Might Have a Solution. Part 2

DC — Mon, 23 Feb 2026 09:11:35 +0000

In the first part of this 3-part series, I covered AI memory and its classification.
Here, I will start with a deep dive into the types of AI memory, and then discuss the pain points in AI memory architectures.

A Deep Dive Into AI Memory Classification

As I mentioned in the first part, how human and AI memory work is different. The broad classification of short-term and long-term AI memory requires further analysis.

Short-Term Memory: Managing Ephemeral Context

This spans a single conversation session. The memory is preserved temporarily across a few prompts and responses. The context window, thus, encompasses the whole chat in the session, utilizing sliding windows or token-based buffers.

Short-term memory can be hence defined as the system’s ability to maintain continuity within a specific session or task. Working memory is a subset of short-term memory. While working memory only deals with tokens being processed immediately, short-term memory can strategically manage continuity to a certain extent as the conversation grows.

Implementation Strategies

Let's start by understanding why short-term memory fails. Simply because it outgrows the context window and hence cannot remember beyond the model's token limit. To counter this, the system can delete and overwrite earlier information or, because it is full, fail to add new information, leading to memory failure and possible hallucination.
There are three techniques to manage this:

Conversation Buffers: These maintain a list of recent messages. There are two types of buffers - full, which remembers everything, and windowed, which retains the last few turns, ensuring the model works within its limits and the earlier context is not totally lost.
Summarization: This technique compresses the conversation history into a concise summary of essential facts by forgetting redundant details. While this can extend the session limits, nuances from earlier context might get filtered out.
Token Budgeting: This optimization technique is a variation of summarization where only the system prompt and the latest five turns are preserved, pruning the rest. Research suggests this middle data is often ignored by models anyway, and hence discarding that portion of the context is an acceptable approach.

The Key-Value (KV) cache plays a vital role in short-term memory. It preserves the exact attention patterns of recent turns and can sometimes perform better than standard Retrieval-Augmented Generation (RAG). There is, however, a trade-off between speed and memory capacity.

Long-Term Memory: Shift to Persistent and Adaptive Knowledge

This spans multiple conversation sessions. The memory is preserved for longer periods, resulting in better context. External databases (vector databases, key-value stores) help to refer to persistent data outside the model.

Long-term memory can be hence defined as the system’s ability to maintain continuity across sessions and days, sometimes even weeks, months, or years. It builds relationships rather than transactions, as external databases synchronize with the model’s built-in knowledge, and RAG is the single-most critical technology to achieve this.

RAG Pipeline and Role of Vector Databases

A typical RAG architecture computes information only one-way. Documents are converted into high-dimensional vector embeddings and stored in a vector database. The advantage of the RAG system is that the data is organized based on semantic meaning instead of literal matches.

So, when a user submits a prompt, the system embeds the query and retrieves a chunk of data that is most similar. This information is pulled into the context window, and the AI can generate answers based on private, proprietary, or real-time data, not necessarily part of its original training. Research suggests this can cut down factual errors and increase efficiency.

From Stateless RAG to Stateful Memory Loops

An essential point to note here, if it has not been apparent, is that RAG is fundamentally stateless. What does this mean? It means that every query is independent, and its significance lies in the fact that the system does not learn anything from interacting with the user. The next logical step is, therefore, moving towards stateful AI memory architectures that can operate as a continuous loop of learning.

There are 4 critical components of a truly stateful memory system.

Extraction: First, the LLM evaluates user interactions to identify and filter salient facts or user preferences.
Synthesis and Learning: Next, synchronization between new information and existing knowledge takes place. The system determines whether new information is a new addition entirely or an overwriting of older, redundant data.
Conflict Resolution: Next, any contradiction arising from the new data addition is resolved by the intelligent agentic system so that consistency and continuity are maintained.
Consolidation: Finally, all knowledge deemed as significant is moved from the short-term context to a long-term Memory Graph or relational store.

It stands to reason that such a stateful loop needs multi-agent collaboration.

Since we are discussing the various types of AI memory, there is another that deserves mention - User Profile Memory. It is usually a subset of the long-term memory with particular emphasis on the user and their preferred language, time zone, conversational and response style, etc. These structured user profiles are stored in databases and injected into prompts, giving the appearance of personalized conversations.

Security and Privacy Risks in AI Memory Architectures

AI memory is built over time, processing through huge and complex datasets that can encompass critical and sensitive information. As vector databases and RAG pipelines become live memory, there is an inevitable vulnerability to severe, crippling security threats.

Data Leakage and Unauthorized Access

This is related to the exposure of Personal Identifiable Information (PII) or proprietary content. RAG systems pull context from a vast range of documents and sources. All the data needs to be properly cleaned, classified, and scoped so that the AI models do not reveal sensitive facts by mistake. This type of context leakage is common when prompts by one user retrieve another user’s private embeddings due to misconfigured access controls.

Embedding Inversion and Data Poisoning

Embedding Inversion occurs when embeddings in the vectors, which are essentially high-dimensional semantic relationships, are inverted, leading to the reconstruction of the original source text, compromising anonymity.
Data Poisoning occurs when malicious actors inject false or adversarial data through subliminal texts hidden in documents into a knowledge base accessed by the model, leading to erroneous or harmful responses.

In the concluding part of the series, I will discuss a potential solution in decentralized and privacy-first AI, along with a mention of working use cases of portable AI memory.

AI Has a Memory Problem. Decentralization and Privacy Might Have a Solution. Part 1

DC — Mon, 23 Feb 2026 06:21:45 +0000

We are on the cusp of an AI revolution. AI agents today are building social networks, negotiating contracts, and even contributing to creativity, like making music. All aspects of our lives are affected every day, as we can choose from a range of AI models and assistants for our interactions and experiences. But there is a chronic problem with AI that often flows under the radar. AI has a memory problem.

Anyone who uses an AI solution has faced it. It does not matter whether you are using Claude, GPT, or anything else; it does not matter whether you are a developer or an end user. If we ever need to switch models, we have to start again from scratch, rebuilding the context of our conversations every time. The same forgetfulness can also happen across different sessions or between different chats in the same model.

Here in this 3-part series, I will discuss what AI memory is, how it works, what types there are, the pain points regarding its architecture, and a potential solution through decentralization and privacy, with Oasis technology as a reference. I will also mention a few working use cases tackling the AI memory problem.
In the first part, I will cover AI memory and its classification.

What is AI memory?

AI memory is the ability of an AI system to retain, recall, and use information from past interactions. While human memory is associative due to being organic, AI associations come from data engineering and code-based architecture. In other words, Large Language Models (LLMs) do not and cannot remember anything. Every interaction is processed fresh. So, what appears to be memory is basically an association achieved through engineering and algorithms.

Human brain: a biological organ where memory is always on, where learning, remembering, and forgetting happen organically.
LLM: a codebase that learns and forgets, but can be made to remember by being given contextual refreshers manually or by smart engineering on a short-term basis.

The Context Window

Before expanding on the different types, it is useful to note that the context window is the most basic form of AI memory. This is quantifiable and measured in tokens or the amount of text that any given model can process in a single interaction. Approximately 150 tokens can constitute about 100 words. And every word in an interaction, those you send and those the AI responds with, together make up the context window limit.

How Context Works

Most conversations with an AI model consist of multiple prompts. What we do not know as an end user is that the system does not remember previous messages. So, what happens? The system typically resends the entire conversation history as part of each new request. Take this example.

You send “Hello” -> AI sees: [Hello]
You send “How are you?” -> AI sees: [Hello, AI reply, How are you?]
You send “Tell me about crypto” -> AI sees: [Hello, AI reply, How are you?, AI reply, Tell me about crypto]

As the conversation carries on, the token count also increases. On reaching the context window limit, the older messages get dropped. This is where AI forgetfulness and hallucination begin.

Context Window Sizes (Typical in 2025)

Any long, detailed conversation can thus stretch and exhaust even high token capacity models. That is why we need more advanced memory systems.

In 2026, the trends indicate that 1M+ token capacity is going to become common, with more focus on scale and performance. For example, top-tier models (e.g., potential Llama 4 iterations) can reach up to 10 million tokens.

Active Models:

Qwen3-Coder-480B: Designed for coding with a 256K to 1M token range.
Gemini 2.5 Pro: Offers 1M+ token windows, with 2M+ expected.
GPT-4.1 Turbo: 128K–1M tokens with advanced "Context Compression" to manage efficiency.

The context window size increase without "smarter" context management is, however, also problematic, as it can lead to "needle in a haystack" failures where models struggle while searching for specific information within a vast context.

The Taxonomy of AI Memory

The analysis of AI memory architecture reveals the various components according to their temporal duration and functional purpose. All modern systems use a multi-tiered memory hierarchy that can balance real-time processing speed with the need for vast, durable storage.

Working memory is at the vanguard of this architecture. Its capacity is limited and critical for achieving coherence through raw token processing and immediate inference building.
Short-term memory is the next stage that strings together working memory. It builds and maintains context across a specific session through sliding windows or summarization techniques.
Long-term memory is the embodiment of continuity. It can be externalized into durable storage systems, acting as an unbounded index of knowledge.
Interesting to note that long-term memory can encompass and go beyond procedural memory, which is fixed within learned logic and inference.

In the next part of the series, I will discuss at length the short-term and long-term AI memory, and also the security and privacy risks associated with AI memory architecture.

Guide To Cross-Chain Key Generation (EVM / Base) With Oasis ROFL

DC — Fri, 20 Feb 2026 12:26:19 +0000

Oasis introduced the framework for runtime off-chain logic (ROFL) to help build and run apps off-chain while ensuring privacy and maintaining trust with on-chain verifiability. There are many moving parts to building with ROFL.
In this tutorial, I will demonstrate how to build a tiny TypeScript app, generating a secp256k1 key inside ROFL. It will be using the @oasisprotocol/rofl-client TypeScript SDK, which talks to the appd REST API under the hood. The TypeScript app will also:

derive an EVM address
sign messages
deploy a contract
send EIP-1559 transactions on Base Sepolia

There will be a simple smoke test that prints to logs.

Prerequisites

To do the steps described in this guide, you will need:

Node.js 20+ and Docker (or Podman)
Oasis CLI and a minimum of 120 TEST tokens in your wallet (Oasis Testnet faucet)
Some Base Sepiola test ETH (Base Sepiola faucet)

For the setup details, please refer to the documentation on Quickstart Prerequisites.

Init App

The first step is to initialize a new app using the Oasis CLI.

oasis rofl init rofl-keygen
cd rofl-keygen

Create App

At the time of creating the app on the Testnet, you will be required to deposit tokens. Assign 100 TEST tokens at this point.

oasis rofl create --network testnet

As output, the CLI will produce the App ID, denoted by rofl1....

Init a Hardhat (TypeScript) project

Now, you are ready to kickstart the project.

npx hardhat init

Since we are showcasing a TypeScript app, choose TypeScript when prompted, and then accept the defaults.
Next step would be to add the small runtime deps for use outside of Hardhat.

npm i @oasisprotocol/rofl-client ethers dotenv @types/node
npm i -D tsx

Hardhat’s TypeScript template automatically creates a tsconfig.json. We need to add a small script so that the app code can compile to dist/.

// tsconfig.json
{
  "compilerOptions": {
    "rootDir": "./src",
    "outDir": "./dist"
  },
  "include": ["src"]
}

App structure

In this section, we will add a few small TS files and one Solidity contract.

src/
├── appd.ts               # thin wrapper over @oasisprotocol/rofl-client
├── evm.ts                # ethers helpers (provider, wallet, tx, deploy)
├── keys.ts               # tiny helpers (checksum)
└── scripts/
    ├── deploy-contract.ts  # generic deploy script for compiled artifacts
    └── smoke-test.ts       # end-to-end demo (logs)
contracts/
└── Counter.sol           # sample contract

src/appd.ts — thin wrapper over the SDK
Here, you will need to use the official client to talk to appd (UNIX socket). We will also need to keep an explicit local‑dev fallback when running outside ROFL.

import {existsSync} from 'node:fs';
import {
  RoflClient,
  KeyKind,
  ROFL_SOCKET_PATH
} from '@oasisprotocol/rofl-client';

const client = new RoflClient(); // UDS: /run/rofl-appd.sock

export async function getAppId(): Promise<string> {
  return client.getAppId();
}

/**
 * Generates (or deterministically re-derives) a secp256k1 key inside ROFL and
 * returns it as a 0x-prefixed hex string (for ethers.js Wallet).
 *
 * Local development ONLY (outside ROFL): If the socket is missing and you set
 * ALLOW_LOCAL_DEV=true and LOCAL_DEV_SK=0x<64-hex>, that value is used.
 */
export async function getEvmSecretKey(keyId: string): Promise<string> {
  if (existsSync(ROFL_SOCKET_PATH)) {
    const hex = await client.generateKey(keyId, KeyKind.SECP256K1);
    return hex.startsWith('0x') ? hex : `0x${hex}`;
  }
  const allow = process.env.ALLOW_LOCAL_DEV === 'true';
  const pk = process.env.LOCAL_DEV_SK;
  if (allow && pk && /^0x[0-9a-fA-F]{64}$/.test(pk)) return pk;
  throw new Error(
    'rofl-appd socket not found and no LOCAL_DEV_SK provided (dev only).'
  );
}

src/evm.ts — ethers helpers

import {
  JsonRpcProvider,
  Wallet,
  parseEther,
  type TransactionReceipt,
  ContractFactory
} from "ethers";

export function makeProvider(rpcUrl: string, chainId: number) {
  return new JsonRpcProvider(rpcUrl, chainId);
}

export function connectWallet(
  skHex: string,
  rpcUrl: string,
  chainId: number
): Wallet {
  const w = new Wallet(skHex);
  return w.connect(makeProvider(rpcUrl, chainId));
}

export async function signPersonalMessage(wallet: Wallet, msg: string) {
  return wallet.signMessage(msg);
}

export async function sendEth(
  wallet: Wallet,
  to: string,
  amountEth: string
): Promise<TransactionReceipt> {
  const tx = await wallet.sendTransaction({
    to,
    value: parseEther(amountEth)
  });
  const receipt = await tx.wait();
  if (receipt == null) {
    throw new Error("Transaction dropped or replaced before confirmation");
  }
  return receipt;
}

export async function deployContract(
  wallet: Wallet,
  abi: any[],
  bytecode: string,
  args: unknown[] = []
): Promise<{ address: string; receipt: TransactionReceipt }> {
  const factory = new ContractFactory(abi, bytecode, wallet);
  const contract = await factory.deploy(...args);
  const deployTx = contract.deploymentTransaction();
  const receipt = await deployTx?.wait();
  await contract.waitForDeployment();
  if (!receipt) {
    throw new Error("Deployment TX not mined");
  }
  return { address: contract.target as string, receipt };
}

src/keys.ts — tiny helpers

import { Wallet, getAddress } from "ethers";

export function secretKeyToWallet(skHex: string): Wallet {
  return new Wallet(skHex);
}

export function checksumAddress(addr: string): string {
  return getAddress(addr);
}

src/scripts/smoke-test.ts — single end‑to‑end flow
This is an important step as this script has multiple functions:

print the App ID (inside ROFL), address, and a signed message
waits for funding
deploy the counter contract

import "dotenv/config";
import { readFileSync } from "node:fs";
import { join } from "node:path";
import { getAppId, getEvmSecretKey } from "../appd.js";
import { secretKeyToWallet, checksumAddress } from "../keys.js";
import { makeProvider, signPersonalMessage, sendEth, deployContract } from "../evm.js";
import { formatEther, JsonRpcProvider } from "ethers";

const RPC_URL = process.env.BASE_RPC_URL ?? "https://sepolia.base.org";
const CHAIN_ID = Number(process.env.BASE_CHAIN_ID ?? "84532");
const KEY_ID = process.env.KEY_ID ?? "evm:base:sepolia";

function sleep(ms: number): Promise<void> {
  return new Promise((r) => setTimeout(r, ms));
}

async function waitForFunding(
  provider: JsonRpcProvider,
  addr: string,
  minWei: bigint = 1n,
  timeoutMs = 15 * 60 * 1000,
  pollMs = 5_000
): Promise<bigint> {
  const start = Date.now();
  while (Date.now() - start < timeoutMs) {
    const bal = await provider.getBalance(addr);
    if (bal >= minWei) return bal;
    console.log(`Waiting for funding... current balance=${formatEther(bal)} ETH`);
    await sleep(pollMs);
  }
  throw new Error("Timed out waiting for funding.");
}

async function main() {
  const appId = await getAppId().catch(() => null);
  console.log(`ROFL App ID: ${appId ?? "(unavailable outside ROFL)"}`);

  const sk = await getEvmSecretKey(KEY_ID);
  // NOTE: This demo trusts the configured RPC provider. For production, prefer a
  // light client (for example, Helios) so you can verify remote chain state.
  const wallet = secretKeyToWallet(sk).connect(makeProvider(RPC_URL, CHAIN_ID));
  const addr = checksumAddress(await wallet.getAddress());
  console.log(`EVM address (Base Sepolia): ${addr}`);

  const msg = "hello from rofl";
  const sig = await signPersonalMessage(wallet, msg);
  console.log(`Signed message: "${msg}"`);
  console.log(`Signature: ${sig}`);

  const provider = wallet.provider as JsonRpcProvider;

  let bal = await provider.getBalance(addr);
  if (bal === 0n) {
    console.log("Please fund the above address with Base Sepolia ETH to continue.");
    bal = await waitForFunding(provider, addr);
  }
  console.log(`Balance detected: ${formatEther(bal)} ETH`);

  const artifactPath = join(process.cwd(), "artifacts", "contracts", "Counter.sol", "Counter.json");
  const artifact = JSON.parse(readFileSync(artifactPath, "utf8"));
  if (!artifact?.abi || !artifact?.bytecode) {
    throw new Error("Counter artifact missing abi/bytecode");
  }
  const { address: contractAddress, receipt: deployRcpt } =
    await deployContract(wallet, artifact.abi, artifact.bytecode, []);
  console.log(`Deployed Counter at ${contractAddress} (tx=${deployRcpt.hash})`);

  console.log("Smoke test completed successfully!");
}

main().catch((e) => {
  console.error(e);
  process.exit(1);
});

contracts/Counter.sol — minimal sample

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.24;

contract Counter {
    uint256 private _value;
    event Incremented(uint256 v);
    event Set(uint256 v);

    function current() external view returns (uint256) { return _value; }
    function inc() external { unchecked { _value += 1; } emit Incremented(_value); }
    function set(uint256 v) external { _value = v; emit Set(v); }
}

src/scripts/deploy-contract.ts — generic deployer

import "dotenv/config";
import { readFileSync } from "node:fs";
import { getEvmSecretKey } from "../appd.js";
import { secretKeyToWallet } from "../keys.js";
import { makeProvider, deployContract } from "../evm.js";

const KEY_ID = process.env.KEY_ID ?? "evm:base:sepolia";
const RPC_URL = process.env.BASE_RPC_URL ?? "https://sepolia.base.org";
const CHAIN_ID = Number(process.env.BASE_CHAIN_ID ?? "84532");

/**
 * Usage:
 *   npm run deploy-contract -- ./artifacts/MyContract.json '[arg0, arg1]'
 * The artifact must contain { abi, bytecode }.
 */
async function main() {
  const [artifactPath, ctorJson = "[]"] = process.argv.slice(2);
  if (!artifactPath) {
    console.error("Usage: npm run deploy-contract -- <artifact.json> '[constructorArgsJson]'");
    process.exit(2);
  }

  const artifactRaw = readFileSync(artifactPath, "utf8");
  const artifact = JSON.parse(artifactRaw);
  const { abi, bytecode } = artifact ?? {};
  if (!abi || !bytecode) {
    throw new Error("Artifact must contain { abi, bytecode }");
  }

  let args: unknown[];
  try {
    args = JSON.parse(ctorJson);
    if (!Array.isArray(args)) throw new Error("constructor args must be a JSON array");
  } catch (e) {
    throw new Error(`Failed to parse constructor args JSON: ${String(e)}`);
  }

  const sk = await getEvmSecretKey(KEY_ID);
  // NOTE: This demo trusts the configured RPC provider. For production, prefer a
  // light client (for example, Helios) so you can verify remote chain state.
  const wallet = secretKeyToWallet(sk).connect(makeProvider(RPC_URL, CHAIN_ID));
  const { address, receipt } = await deployContract(wallet, abi, bytecode, args);

  console.log(JSON.stringify({ contractAddress: address, txHash: receipt.hash, status: receipt.status }, null, 2));
}

main().catch((e) => {
  console.error(e);
  process.exit(1);
});

Hardhat (contracts only)

At this stage, we will need minimal config to compile Counter.sol

hardhat.config.ts

import type { HardhatUserConfig } from "hardhat/config";

const config: HardhatUserConfig = {
  solidity: {
    version: "0.8.24",
    settings: {
      optimizer: { enabled: true, runs: 200 }
    }
  },
  paths: {
    sources: "./contracts",
    artifacts: "./artifacts",
    cache: "./cache"
  }
};

export default config;

Point to note is that local compilation is optional, so you can skip it if you want. Next step is a choice - either delete the existing contracts/Lock.sol file or you can update it to Solidity version 0.8.24.

npx hardhat compile

Containerize

This is an essential step. Here, you need to a Dockerfile that builds TS and compiles the contract. The file will also run the smoke test once, and then stand idle while you inspect logs.

Dockerfile

FROM node:20-alpine
WORKDIR /app

COPY package.json package-lock.json* ./
RUN npm ci

COPY tsconfig.json ./
COPY src ./src
COPY contracts ./contracts
COPY hardhat.config.ts ./
RUN npm run build && npx hardhat compile && npm prune --omit=dev

ENV NODE_ENV=production
CMD ["sh", "-c", "node dist/scripts/smoke-test.js || true; tail -f /dev/null"]

Next, you must mount appd socket provided by ROFL. Rest assured that no public ports are exposed in the process.

compose.yaml

services:
  demo:
    image: docker.io/YOURUSER/rofl-keygen:0.1.0
    platform: linux/amd64
    environment:
      - KEY_ID=${KEY_ID:-evm:base:sepolia}
      - BASE_RPC_URL=${BASE_RPC_URL:-https://sepolia.base.org}
      - BASE_CHAIN_ID=${BASE_CHAIN_ID:-84532}
    volumes:
      - /run/rofl-appd.sock:/run/rofl-appd.sock

Build the image

It is important to remember that ROFL only runs on Intel TDX-enabled hardware. So, if you're compiling images on a different host, such as macOS, then passing the --platform linux/amd64 parameter is an essential extra step.

docker buildx build --platform linux/amd64 \
  -t docker.io/YOURUSER/rofl-keygen:0.1.0 --push .

An interesting point to note here is that you can opt for extra security and verifiability. You just need to pin the digest and use image: ...@sha256:... in compose.yaml.

Build ROFL bundle

There is a step that you must take before running the oasis rofl build command. Since building the image segment comes after containerization, you will need to update the services.demo.image in compose.yaml to the image you built.
For simple TypeScript projects, like this one, there is sometimes a possibility that the image size is larger than anticipated. It is thus advisable to update the rofl.yaml resources section to at least: memory: 1024 and storage.size: 4096.
Now, you are ready.

oasis rofl build

You can next publish the enclave identities and config.

oasis rofl update

Deploy

This is an easy enough step where you deploy to a Testnet provider.

oasis rofl deploy

End‑to‑end (Base Sepolia)

This is a 2-step process, although the second step is optional.
First, you view smoke‑test logs.

oasis rofl machine logs

If you have completed all the steps till now correctly, you will see in the output:

App ID
EVM address and a signed message
A prompt to fund the address
Once funding is done, a Counter.sol deployment

Next, local dev. Here, you need to run npm run build:all command to compile the TypeScript code and the Solidity contract. Skip this step if not needed.

 export ALLOW_LOCAL_DEV=true
 export LOCAL_DEV_SK=0x<64-hex-dev-secret-key>   # DO NOT USE IN PROD
 npm run smoke-test

Security & notes to remember

Provider logs are not encrypted at rest. So, **never **log secret keys.
The appd socket /run/rofl-appd.sock exists only inside ROFL.
There may be rate limits in public RPCs. So, it is advisable to opt for a dedicated Base RPC URL.

There is a key generation demo in the Oasis GitHub, which you can refer to as an example of this tutorial. https://github.com/oasisprotocol/demo-rofl-keygen

Now that you have successfully generated a key in ROFL with appd, signed messages, deployed a contract, and moved ETH on Base Sepolia, let us know in the comments section your feedback. For a quick chat with the Oasis engineering team for help with specific issues, you can drop your comments in the dev-central channel in the official Discord.

Developing in Web3: Deploying Privacy-First dApps with Sapphire + ROFL

DC — Tue, 20 Jan 2026 06:28:08 +0000

TL;DR

Sapphire provides confidential EVM smart contracts. OPL lets existing dApps add privacy without migrating chains.
ROFL enables verifiable, privacy-preserving off-chain computation.
Together, Sapphire + ROFL form a full stack for building private, AI-ready web3 applications.

The crypto landscape today is flooded with web3 and AI dApps (decentralized applications). You need to choose the right chain and the right tools to develop and deploy your dApp, as it can make all the difference in attracting the right attention from the end-users. The choices are too many, and they often distract more than add value. It is also hard to come by solid, reliable information to make a decision.

I believe in Oasis as a pioneer of smart privacy for web3 and AI. Let me tell you point by point why I became a believer.

The Tech Stack: Sapphire EVM

In the blockchain trilemma scene, privacy has always taken the backseat, as most protocols emphasize decentralization and scalability. And then there is the debate and confusion of how to frame the rising privacy narrative - is it privacy coin or privacy blockchain?

Oasis has emerged as a pioneer in the field of smart privacy. It is a modular L1 blockchain that aims to finally complete the blockchain picture - decentralization, scalability, and privacy (and security) together.

Privacy-preserving techniques have garnered much attention in recent times. Long before zero-knowledge proofs (ZKPs), fully homomorphic encryption (FHE), and secure multiparty computation (sMPC) became trending, Oasis had adopted trusted execution environments (TEEs) for end-to-end encryption and confidential computation.

In Oasis Sapphire, you get the world's first and only production-ready confidential EVM. Its key features help you build better dApps that are privacy-first.

EVM compatibility
Private storage
Encryption precompiles
Free view calls
Web2 authentication
ROFL (runtime off-chain logic)

So, as a web3 developer, you get to work with smart privacy, cross-chain simplicity, and low technical overhead. How it differs from most other projects also offering privacy solutions is that you get the best of both worlds here - transparent when you need it, confidentiality when it matters. Further, you can build with full spectrum of confidentiality customization - 100% public to 100% private or anywhere in between.

Deployed already? Use the OPL hack

But what happens if you have already built your dApp on another EVM chain? It is unfeasible to dismantle everything there and start rebuilding from scratch for the sake of privacy. Acknowledging this dilemma, Oasis offers the services of the Oasis Privacy Layer (OPL).

OPL is simple to use - a few hundred lines of code, practically a plug-and-play solution. Behind the scenes, it uses a message passing bridge and a gas relayer.

It gives the flexibility to leverage Sapphire's features and functionalities for your dApp right from your home network, paying transaction fees with your chain's native token. What you assuredly get from this setup:

Customizable privacy
Cross-chain convenience
Productive transparency
Low complexity
Access to cryptographic primitives

Learn more about OPL's technical advantage and utility here, and start building.

The Framework: ROFL

Now, Sapphire is the runtime on-chain logic, but computation-heavy dApps, with end-to-end encryption and/or powered by AI, are a huge challenge. When you add the criteria that the privacy you get and the computations you process should be verifiable and trustless, the feasibility of doing everything on-chain plummets.

The challenges mount when dealing with cryptoAI, as it has two main problems - crypto's limited application layer and AI's trust issues. Off-chain computation is a viable answer in this situation. Oasis has thus developed the ROFL framework, essentially working like a decentralized TEE cloud with on-chain privacy and verifiability.

ROFL's 5-part architecture involves a hardware layer, an application layer, a remote attestation layer, a blockchain layer, and a user interaction layer. Key features include:

Uncapped computational power
Tamper-proof processing
Verifiable execution
Decentralized key management solution
Direct access to confidential virtual machines

The reason ROFL is so crucial and pivotal to the next-gen private and trustless web3 and AI dApps can be simply summed up by what it doesn't need, which you will definitely appreciate.

No chain dependency
No coding language dependency
No prior TEE experience

Start exploring the scope of ROFL with these resources:

Real-World Integrations

The applicability of the Sapphire + ROFL solution, with its impact and scope, is limitless. The features and primitives that ROFL unlocks are also significant.

Already, multiple live collaborations have transpired.

Zeph - developing AI companions empowered by DeAI and DeCC
Tamarin - empowering secure and private cross-border healthcare data analysis
Tradable - trading with privacy-preserving AI insights
Flashback - privacy-first AI training that lets users own and monetize their data
Plurality - confidential reputation scoring and AI context flow
Talos - combining DAO 2.0 and DeFAI in the form of a new model for on-chain sovereign intelligence
zkAGI - building PawPad, a privacy-preserving platform for trustless trading agents
Heurist - enabling privacy-first MCP servers for AI agents
Huralya - building private AI wellness assistants
Carrotfunding - servicing on-chain prop trading, introducing a new model for parallel verification of the risk and evaluation engine

Talos and Carrotfunding here deserve special focus, standing out as pathbreaking case studies redefining DeFi.

Final words

The takeaway from all this is that what Oasis offers to blockchain and web3 developers is not just some concept - it's something real and tangible.
In a space where half-baked or well-intentioned ideas sound promising but often don't deliver in their execution, a working blueprint for next-gen dApp builders stands out.

So, if you want to deploy your dApp in a web3 universe where privacy, scalability, trustlessness, and AI-ready performance all matter equally, take a moment to explore Oasis - and help shape what comes next.