vRAM Guide for Experts

A Technical Deep-Dive Into The DAPP Network’s Decentralized Memory Solution

DAPP Network
Mar 10, 2019 · 12 min read

EOS — Home of dApps

RAM Isn’t Being Used Properly

Introducing The vRAM System

Provisioning Layer

DAPP Service Layer

IPFS Service Layer

vRAM Layer

vRAM under the hood


Client’s App (eosjs instance) sends a transaction through the DSP API node. The transaction fails when run locally by the DSP. This exception is a way to signal a service request.


The DSP fetches the requested file from local IPFS cluster and retrieves the cryptographic proof of the dataset’s integrity from EOS RAM. It then relays the file and proof to the dApp Smart Contract in what is known as a ‘Warm-Up Request”.

Load and Transact

After verifying the validity of the data, the DSP loads it into EOS RAM and sends the transaction to the blockchain. This time it succeeds since all the necessary data is available in RAM.


The dApp Smart Contract modifies data on EOS RAM by means of an inline action. DSPs listen to the modification event and write the new file on their local IPFS cluster node.

Clear Cache

The data is deleted from EOS RAM, leaving behind a cryptographic proof (Merkle root) that the action happened.

End-to-End Decentralized Memory

DAPP to the Future

Follow LiquidApps

The DAPP Network Blog

Designing tools for building and scaling the dApps of the…