Lynx Blockchain
  • Welcome
  • Technical Evolution and Architecture Overview
  • History of Lynx
    • Evolution of a Blockchain
    • Hybrid Proof of Work (HPoW) Protocol
    • Pioneering Blockchain Data Storage
    • Evolution to Proof of Stake
    • Next Generation Data Storage Architecture
    • Preserving Knowledge
  • Lynx Core
    • Hardware and System Requirements
    • Lynx Dynamics
    • Open Source
    • Core Parameters and Strategy
    • Sustainability
    • Circulating Supply Analysis
    • Locked Addresses
    • Data Storage
      • auth
      • fetch
      • fetchall
      • store
      • status
      • list
    • Understanding the Encryption Option
    • Understanding Lynx Staking Wait Times
    • Understanding Asset Retrieval Times
    • Understanding Block Time Targeting in the Lynx Blockchain
    • Understanding the Lynx Blockchain Statistics Report
  • Lynx Administration
    • Public Peer Nodes
    • Understanding Blockchain Bootstrap Files
      • Bootstrap Extraction Script
      • Bootstrap Creation Script
    • How to Sweep a Lynx Wallet
    • Enable/Disable Staking
  • Clevver
    • Revolutionizing Digital Preservation
    • Permanent Storage for Digital Assets
    • Permanent Digital Archives for Journalism
    • How did Clevver originate?
    • Shortened URL Support
    • Assigning Tags to Assets
    • How to delete content
    • Clevver Terms of Service Agreement
  • Clevver API
    • Public Methods
      • Batches
      • Files
      • User
  • ElectrumX
    • Lynx ElectrumX nodes
    • Build Script Details
  • External Links
    • Lynx Explorer
    • Lynx Github
    • Lynx Uptime Report
    • Clevver Website
  • Lynx Bootstraps
  • Wallet Links
    • Komodo Wallet
    • Wally.id Wallet
    • Lynx Paper Wallet
  • Social Links
    • Lynx Discord
    • Lynx on Bluesky
    • Clevver on Bluesky
  • Exchange Links
    • FreiXLite (LYNX/LTC)
  • FreiExchange (LYNX/BTC)
  • Komodo Wallet (SWAP)
  • XredX (LYNX/LTC)
  • XredX (LYNX/DOGE)
  • XredX (LYNX/IL8P)
Powered by GitBook
On this page
  1. Lynx Core

Data Storage

Published: September 2024 | Last updated: March 2025

PreviousLocked AddressesNextauth

Last updated 1 month ago

The following built-in RPC functions are used to interact with the data storage mechanism of Lynx Core. These functions are built into the daemon and don't require any third party software or modules. All functions listed are supported by the Enterprise version of Lynx. The Professional version of Lynx will only support the fetch() function.

For convenience, when interacting with the Lynx daemon, the help() command will provide additional detailed documentation for each storage related function. The included documentation is respective to the version of Lynx running.

Definitions

Tenant

A user of data storage routines. In most cases, a tenant can be thought of as a traditional user account.

Asset

A digital file. While there may be file size, type, content, and format constraints on an asset, an asset is no more and no less than a digital file.

Store

to the Lynx blockchain. Storage is permanent. The file can not be edited or deleted after it has been placed. If uploading encrypted assets, the tenant is responsible for the retention of decryption keys.

Fetch

from the Lynx blockchain to the hard drive. Their is no fee to copy an asset from the blockchain. A unique identifier is required to find the requested asset.

Authorize

Make it such that a tenant, when authenticated, can perform operations allowed for that tenant.

Authenticate

Authorized tenants by providing appropriate credentials.

authenticate
Copy an asset
Copy an asset
Page cover image