DataRumeDocs

Terminologies ​

This glossary defines the key terms, concepts, and components used across the DataRume platform.

Core Concepts ​

Data Room ​

A secure, token-gated digital environment where sensitive files are stored. On the blockchain, each Data Room is represented by a unique Data NFT (ERC-721) that governs its ownership and configuration settings.

Data Token (ERC-20) ​

A fungible access token minted specifically for a single Data Room.

  • Function: Acts as a "pass" or "ticket." Holding at least one Data Token allows a user to verify access.
  • Usage: To view the secured files, a user must "burn" (spend) one Data Token used for that session.
  • Symbol: DRUME.

Data NFT (ERC-721) ​

A non-fungible token that represents the ownership and existence of a Data Room on the blockchain. The wallet holding this NFT is recognized as the Data Room Owner and has administrative rights to upgrade, share access, or manage the room.

TokenURI ​

The metadata URI attached to the Data NFT.

  • Format: It resolves to <url>/room/<dataNFTAddress>.
  • Usage:
    • Browser: Users can navigate directly to this URL to access the Data Room UI.
    • API: Developers use the dataNFTAddress extracted from this URI to perform startOrder and executeOrder transactions programmatically.

RumeNet ​

The specific Private Network name for DataRume's Layer 2 blockchain infrastructure.

  • Type: Private Permissioned Layer 2.
  • Purpose: processing high-volume, sensitive logistics transactions with near-zero latency and enhanced privacy compared to public mainnets.
  • Role: Serves as the primary execution environment where Data Rooms are deployed and Access Tokens are minted.

Gas Token (ETH) ​

The native currency used to pay for transaction fees (gas) on the RumeNet blockchain.

  • Ticker: ETH (on RumeNet).
  • Functionality: Every interaction that writes data to the blockchain (creating a room, transferring tokens, starting an order) requires a small amount of Gas Token to execute.
  • Acquisition: Users receive this token for free via the Faucet to subsidize enterprise usage costs.

Access & Security Flow ​

Start Order ​

The first step in the secure access flow. It is an on-chain transaction where the user validates their intent to access a file by burning 1 Data Token.

  • Outcome: Generates a unique serviceIndex on-chain.

Service Index ​

A unique, incrementing session identifier generated during a startOrder transaction. It prevents replay attacks and binds a specific access session to a specific user and timestamp.

Execute Order ​

The second step in the secure access flow. After a startOrder is confirmed, the user must cryptographically sign a message containing the serviceIndex.

  • Purpose: Proves that the entity requesting the file is the same entity that paid for the access token.

Consumer Signature ​

The cryptographic signature produced by the user's wallet during the Execute Order phase. This signature is verified by the backend and the smart contract against the on-chain order before releasing any data.

Pre-signed URL ​

A secure, temporary URL generated by the DataRume backend (AWS S3) that allows a user to download or view a file.

  • Expiry: These links automatically expire after 15 minutes to prevent unauthorized sharing.

Account & Infrastructure ​

A passwordless authentication method. Users enter their email address and receive a unique, one-time-use link (or 6-digit code) to log in securely without managing passwords.

WalletLinker ​

A system component that links an authenticated Web2 identity (email) with a Web3 identity (wallet address). It ensures that enterprise users can operate on-chain while maintaining a traditional user profile.

Faucet (RumeNet) ​

An automated service on the RumeNet network that distributes small amounts of RumeNet ETH (testnet gas ~50 USD) to new wallets. This ensures users can perform transactions (like deploying rooms or signing orders) without needing to acquire funds manually.

Access Slots ​

A configuration setting that defines the total supply of Data Tokens available for a room.

  • Example: If a room has 5 Access Slots, only 5 access tokens can ever be minted and distributed.

Access Duration ​

The validity period (in days) during which the files in a Data Room remain accessible on the storage network. Once expired, the files may be purged or become inaccessible.

Smart Contracts ​

ERC721Factory ​

The "Factory" contract responsible for deploying new Data Rooms. When a user clicks "Deploy," this contract creates a new instance of a Data Room Manager and mints the corresponding Data NFT to the creator.

DatarumeManagerContract ​

The "Manager" contract deployed for each specific Data Room. It contains the logic for:

  • Minting/Burning Access Tokens.
  • Validating startOrder and executeOrder transactions.
  • Managing upgrades and configurations.

Roles ​

Data Room Owner ​

The creator of the Data Room.

  • Rights: Can mint tokens, transfer access, upgrade room capacity, and add files (within the storage slots).
  • Identification: The wallet address that holds the Data NFT.

Consumer / Visitor ​

A user who has been granted access to a Data Room.

  • Rights: Can verify access, initiate startOrder, and view secured files after successful executeOrder.
  • Requirement: Must hold a valid balance (>0) of the specific Data Token for that room.
Previous Chapter
Architecture
 Next Chapter
API Access