Native storage layer
Store and index data directly on-chain with configurable costs for each PBaaS chain.
Store and retrieve data on-chain
A complete on-chain database system with encryption, indexing, and flexible storage options, secured by consensus.
Privacy-first storage
Store data publicly or privately with optional encryption, zk-SNARKs privacy, and controlled sharing.
Indexed queries
Query structured and unstructured data through globally unique VDXF keys across multiple chains.
Flexible key system
Define custom namespaces and data types with VDXF keys tied to clear application ownership.
Structured and unstructured
Store anything from simple key-value pairs to nested objects and larger data blobs.
Data sharding
Distribute data across PBaaS chains while preserving references, relationships, and access patterns.
Cross-chain access
Reference and retrieve data across any PBaaS chain through a unified data model.
Smart transactions
Store, update, and retrieve data with protocol-level commands instead of custom smart contracts.
Usage-based pricing
Pay for the storage you use with transparent fees that flow to the chain validators.
Blockchain-native storage for modern dApps
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. Verus makes data storage a core protocol feature rather than an external service.
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 and security
- Encryption support for stored data
- Private storage through zk-SNARKs transactions
- VerusID-based access control
- Selective data sharing capabilities
Cost structure for developers
Storage costs are transparent and chain-specific, so applications can choose the storage market that fits their access and permanence requirements.
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.
PBaaS chain storage
Each PBaaS chain can set its own storage fees based on capacity and validator costs, creating a competitive marketplace for blockchain storage.
Cost optimization
Applications can choose chains with appropriate fee structures and use cross-chain references to distribute data efficiently.
Store data with simple commands
Add structured data to your VerusID with a standard API call, creating a permanent on-chain data store.
Terminal - verus
# Storing 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
VDXF key for myId.vrsc::shop.
i4GC1...nCQv
A data descriptor key for the stored object.
label
VDXF key for myId.vrsc::shop.type.
objectdata
Contains the actual JSON content being stored.
Example use case
This example stores business location data in a structured format. Each data point has its own VDXF label for access and querying, while remaining cryptographically tied to the parent VerusID.
- Business name, such as Bookshop
- Location address, such as 15 Sea View, Miami, 132523
- Property value, such as $100,000
Standardized data exchange across chains
VDXF is a protocol-level system for defining, storing, and exchanging data across the Verus network.
Every VDXF key is tied to a namespace, typically a VerusID, and includes metadata about how the data should be handled. 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
Use VDXF keys as a universal reference layer across PBaaS chains, storage markets, and applications.
Data sharding
Distribute data across multiple PBaaS chains while maintaining atomic references and access patterns.
Storage markets
PBaaS chains can compete on capacity, cost, and features, with different chains optimizing for different storage needs.
Unified access
Query data across chains through VDXF keys while the protocol handles cross-chain references and retrieval.
Simple developer-first APIs
VDXF objects follow a standardized format that makes them easy to integrate into any application.
Applications can implement partial support for VDXF data types, using what they understand while safely ignoring the rest.
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
Store and retrieve on-chain data with familiar commands and predictable lookup patterns.
RESTful API
Use simple API commands for storing and retrieving data while the protocol manages blockchain interaction.
Query system
Find and retrieve data across multiple chains with lookups based on VDXF type and namespace.
Choose the right storage for your dApp
Compare on-chain storage with alternatives to make informed architectural decisions for your applications.
Feature
Verus on-chain storage
IPFS
Centralized servers
Data ownership
Strong
True user ownership through VerusID, with users maintaining control of their data.
Moderate
Content-addressed, but persistence depends on pinning services.
Limited
Provider controls the data and account relationship.
Persistence
Strong
Permanent by default after a one-time storage fee.
Moderate
Requires pinning services or active hosting.
Moderate
Depends on subscription, account status, or provider policy.
Privacy
Strong
Protocol-level privacy with zk-SNARKs, encryption, and selective disclosure.
Moderate
Public by default, with encryption handled outside the protocol.
Moderate
Depends on provider implementation and privacy policy.
Query capabilities
Strong
Direct key lookup through VDXF, multimap support, and built-in versioning.
Limited
Limited without additional indexing services.
Strong
Full database query capabilities.
Cost structure
Strong
One-time fee for permanent storage, with chain-dependent pricing.
Moderate
Free to use at the protocol layer, but persistence often requires pinning costs.
Limited
Ongoing subscription, storage, and bandwidth costs.
Identity integration
Strong
Native self-sovereign identity system through VerusID.
Limited
No native identity system.
Moderate
Account-based identity controlled by the provider.
Access control
Strong
Built in through VerusID permissions and encryption.
Limited
Limited without additional application layers.
Strong
Granular access control is familiar and available.
Cross-chain support
Strong
Native cross-chain data access across PBaaS chains.
Moderate
Network agnostic, but not chain-native.
Limited
No native blockchain support.
Data integrity
Strong
Cryptographically verified by consensus.
Strong
Content-addressed integrity.
Moderate
Depends on provider controls and backups.
StrongClear capability or advantage
ModerateUseful capability with tradeoffs
LimitedLimited capability or disadvantage