Data Storage

Details about the native Lynx Blockchain data storage RPC functions and associated security model.

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 fetchAsset() function. For detailed documentation on each function, the respective arguments, examples and syntax, please reference the built-in Lynx Core daemon help commands.

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

Copy an asset 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

Copy an asset 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 authenticate by providing appropriate credentials.

Data storage functions are enabled on the Lynx Core help documentation after authentication. Otherwise, the fetchAsset() will be the only listed RPC data storage function.

RPC Data Storage Functions

fetchAsset()

Lynx version supported: Professional and Enterprise

Retrieve an asset from the Lynx blockchain. Their are no fees to retrieve an asset. No authentication is required to use this function.

storeAsset()

Lynx version supported: Enterprise

Permanently store an asset on the Lynx Blockchain. Fees are deducted from the local daemon wallet. It is highly recommended that staking functions be disabled for more efficient processing. The use of this function requires tenant specific authorization.

authenticateTenant()

Lynx version supported: Enterprise

As authorization roles apply, once a user has authenticated themselves, they will unlock associated data storage functions for 12 hours. Tenants are required to authenticate every 12 hours.

listTenants() [to be removed from Doc]

Lynx version supported: Enterprise

View a list of all active tenants who have rights to authenticate. This list of pubic keys does not reveal a relationship to the assets stored by a respective tenant nor the identity of the tenant. The use of this function requires tenant specific authorization.

authorizeTenant() [to be removed from Doc]

Lynx version supported: Enterprise

Add a new tenant that will be able to authenticate with the authenticateTenant() function. After two blocks, they will appear in listTenants(). The use of this function requires tenant specific authorization.

deauthorizeTenant() [to be removed from Doc]

Lynx version supported: Enterprise

Deny a tenant from being able to authenticate by deleting the tenant from listTenants(). The use of this function requires tenant specific authorization.

getState()

Lynx version supported: Enterprise

Return the most recent job and storage thread state for the local daemon. The use of this function requires tenant specific authorization.