Hero background - light

Store & Retrieve Data On-Chain

A complete on-chain database system with encryption, indexing, and flexible storage options—secured by consensus.

Native Storage Layer

Store data directly on-chain with efficient indexing and retrieval. Each PBaaS chain offers protocol-level storage capabilities with configurable costs. Perfect for permanent, verifiable record keeping.

Privacy-First Storage

Store data publicly or privately with optional encryption. Leverage zk-SNARKs for private transactions and support for encrypted data storage. Control exactly what data is shared and with whom.

Indexed Queries

Query data through globally unique VDXF keys. Fast lookup of structured and unstructured data across multiple chains. Efficient retrieval through standardized data identifiers.

Flexible Key System

Define custom namespaces and data types through the VDXF key system. Organize data with unlimited nesting levels. Create application-specific data structures with clear ownership.

Structured & Unstructured

Support for both structured data with defined schemas and unstructured data blobs. Store anything from simple key-value pairs to complex nested objects with multiple data types.

Data Sharding

Distribute data across multiple PBaaS chains while maintaining atomic references. Scale storage horizontally while preserving data relationships and access patterns.

Cross-Chain Access

Access and reference data across any PBaaS chain in the network. Unified data model enables seamless integration between different chains and applications.

Smart Transactions

Interact with stored data through protocol-level smart transactions. No complex smart contracts needed - just simple commands to store, update and retrieve data.

Usage-Based Pricing

Pay only for the storage you use with transparent, predictable pricing. Storage costs are determined by data size and complexity. Fees flow directly to chain validators.

Build with Blockchain Native Storage—Beyond Traditional Databases

Integrate censorship-resistant storage directly in your application with blockchain-level security guarantees.

Every PBaaS chain includes a native storage layer that lets you store and index data directly on the blockchain. Unlike traditional systems that rely on external storage solutions, Verus makes data storage a core protocol feature.

Store up to 999,999 bytes per entry with encryption and indexing. Data can be stored publicly, privately through zk-SNARKs transactions, or attached to VerusIDs for fine-grained access control.

Developer API Features

  • Store up to 999,999 bytes per entry
  • Automatic indexing for fast retrieval
  • Support for structured and unstructured data
  • Cross-chain data references and queries

Privacy & Security

  • Default encryption for all stored data
  • Private storage through zk-SNARKs transactions
  • VerusID-based access control
  • Selective data sharing capabilities

Cost Structure for Developers

Verus Storage

On the Verus blockchain, storage costs approximately 0.01 VRSC per kilobyte. Fees are paid in VRSC and flow directly to miners and stakers who secure the network.

PBaaS Chain Storage

Each PBaaS chain can set its own storage fees based on capacity and validator costs. This creates a competitive marketplace for blockchain storage with different chains optimizing for different use cases.

Cost Optimization

Applications can optimize storage costs by choosing chains with appropriate fee structures and using cross-chain references to distribute data efficiently across the network.

Store Data With Simple Commands

Add structured data to your VerusID with a single API call, creating a permanent on-chain data store.

Terminal - verus

# Storing multiple data objects in a VerusID using contentmultimap

./verus updateidentity '{

"name": "yourid",

"contentmultimap": {

"iMvTg2HGhKKGYMqtapvRyfZNahbzmD9R3b": [

{

"i4GC1YGEVD21afWudGoFJVdnfjJ5XWnCQv":{

"version": 1,

"label": "i3esdByX2PKx5vJiuNrRb61KAKqsBEMxac",

"mimetype": "text/plain",

"objectdata": {

"message": "Bookshop"

}

},

}

// Additional data entries omitted for clarity

]

}

}'

Data Structure

  • contentmultimap - Maps namespaces to collections of data objects, enabling complex data structures
  • iMvTg...D9R3b - vdxfkey: myId.vrsc::shop
  • i4GC1...nCQv - This is a dataDescriptor key
  • label - vdxfkey: myId.vrsc::shop.type
  • objectdata - Contains the actual content being stored (any JSON structure)

Example Use Case

This example stores business location data in a structured format. The three entries contain:

  • Business name ("Bookshop")
  • Location address ("15 Sea View, Miami, 132523")
  • Property value ("$100,000")

Each data point has its own label (vdxfkey) for easy access and querying, while being cryptographically tied to the parent VerusID.

Standardized Data Exchange—Cross-Chain Compatible

Build applications with a universal data schema that works seamlessly across all Verus ecosystem chains.

VDXF is a protocol-level system for defining, storing, and exchanging data across the Verus network. It provides globally unique identifiers for data types and enables applications to handle data consistently across different chains and systems.

Every VDXF key is tied to a namespace (typically a VerusID) and includes metadata about how the data should be handled. This creates a permission system where only namespace controllers can create new data types.

Developer Integration

  • Globally unique 20-byte identifiers
  • Human-readable type names
  • Namespace-based permissions
  • Support for complex data structures

Use Cases for Builders

  • Identity profiles and credentials
  • Application states and settings
  • Digital asset metadata
  • Cross-chain references

Multi-Chain Architecture

Data Sharding

Distribute data across multiple PBaaS chains while maintaining atomic references. Scale horizontally by using different chains for different types of data or access patterns.

Storage Markets

Each PBaaS chain can compete in storage markets based on capacity, costs, and features. Some chains might optimize for large files, while others focus on fast access to frequently used data.

Unified Access

Query and access data seamlessly across all chains using VDXF keys. The protocol handles cross-chain references and data retrieval automatically.

Developer-First APIs—Simple Integration

Leverage blockchain storage with familiar APIs designed for rapid integration into any app architecture.

VDXF objects follow a standardized format that makes them easy to integrate into any application. Each object includes metadata about version, handling requirements, and content type.

Applications can implement partial support for VDXF data types, using what they understand while safely ignoring the rest. This enables gradual adoption and compatibility across different systems.

Data Object Structure

  • Version tracking for compatibility
  • Special handling flags
  • Data payload field
  • Human-readable labels

Content Management

  • MIME type specification
  • Encryption metadata
  • Custom type definitions
  • Schema validation rules

Developer Toolkit

RESTful API

Simple API commands for storing and retrieving data. No need to handle complex blockchain interactions—the protocol manages everything automatically.

Query System

Efficient querying through VDXF keys. Find and retrieve data across multiple chains with simple lookups based on type and namespace.

Access Control

Built-in permission system based on VerusIDs and namespaces. Control who can create, modify, and access different types of data.

Choose the Right Storage—For Your dApp Needs

Compare on-chain storage with alternatives to make informed architectural decisions for your applications.

Feature
Verus On-Chain Storage
IPFS
Centralized Servers
Data Ownership
🟢 True user ownership through VerusID - users maintain complete control of their data
🟡 Content-addressed but requires pinning services for persistence
🔴 Provider owns and controls data
Persistence
🟢 Permanent by default - one-time storage fee
🟡 Requires pinning services or must be actively hosted
🟡 Depends on subscription/payment
Privacy
🟢 Protocol-level privacy with zk-SNARKs, encrypted storage, and selective disclosure
🟡 Public by default, encryption possible but not native
🟡 Provider-dependent privacy policies
Query Capabilities
🟢 Direct key lookup via VDXF, multimap support, versioning built-in
🔴 Limited without additional indexing services
🟢 Full database query capabilities
Cost Structure
🟢 One-time fee for permanent storage (e.g., ~0.01 native coin per KB on the Verus blockchain, is chain dependent)
🟡 Free to use but requires pinning costs
🔴 Ongoing subscription costs
Identity Integration
🟢 Native self-sovereign identity system (VerusID)
🔴 No native identity system
🟡 Account-based identity
Data Validation
🟢 Protocol-level validation of data types and structures
🔴 No built-in validation
🟢 Server-side validation
Access Control
🟢 Built-in through VerusID permissions and encryption
🔴 Limited without additional layers
🟢 Granular access control
Scalability
🟢 Horizontal scaling through PBaaS chains
🟢 Highly scalable P2P network
🟢 Vertical and horizontal scaling
Availability
🟢 Blockchain-guaranteed availability
🟡 Depends on network participation
🟢 High availability (with cost)
Decentralization
🟢 Fully decentralized, validated by consensus
🟢 Fully decentralized
🔴 Centralized
Data Recovery
🟢 Built-in recovery mechanisms through VerusID
🟡 Depends on content availability
🟢 Provider backup systems
Development Complexity
🟢 Simple API commands, no special programming needed
🟡 Moderate complexity
🟢 Familiar development patterns
Cross-chain Support
🟢 Native cross-chain data access
🟡 Network agnostic but no native chain support
🔴 No native blockchain support
Data Integrity
🟢 Cryptographically verified by consensus
🟢 Content-addressed integrity
🟡 Provider-dependent
🟢Strong capability/advantage
🟡Moderate capability/tradeoffs
🔴Limited capability/disadvantage