Web3 & Network Strategy

DataRume operates across multiple networks to balance the need for privacy, shareability, and public auditability.

🌐 Supported Networks

Network	Role	Chain ID	Type	URL
RumeNet	Primary Platform	600001	Private	RumeNet Explorer
Optimism	Public Provenance	10	Public	Optimism Explorer

Network Topology

🚰 Automated Faucet (RumeNet Only)

To enable a seamless experience for enterprise users on our private network, DataRume includes an automated funding mechanism:

How it triggers:

1. Wallet Connection: When a user connects a wallet address that has not been seen before, the WalletLinker component detects it.
2. On-the-Fly Funding: The system calls the /api/faucet endpoint which sends 0.2 ETH to the user's address immediately as welcome funds.
3. Network Addition: If a user adds RumeNet to their wallet for the first time via our UI, a specific funding trigger is fired to ensure they have gas for their first deployment.

Note: This faucet is only available on RumeNet (Chain ID: 600001).

🛡️ Wallet Integration & Reliability

Network Switching

We use a debounced network switching logic to prevent the common "Requests Exceeded" error in mobile and browser wallets. If a request is in flight, any redundant requests are locked until the first one is resolved.

Manual Network Addition

For custom networks like RumeNet, the application supports wallet_addEthereumChain. If a wallet doesn't recognize the chain, the dApp will automatically prompt the user to add the network with the correct RPC and Explorer configurations.

📦 Smart Contracts

The platform relies on a set of specialized smart contracts designed for secure data management:

• ERC721Factory: The master factory contract used to deploy new, unique Data Room Manager contracts. It ensures every Data Room is a distinct on-chain entity.
• DatarumeManagerContract: The core contract logic for each Data Room.
  • Access Control: Manages the minting, burning, and transfer of access tokens (ERC-20).
  • Room Configuration: Handles storage duration, access capacity, and file metadata hashes.
  • Room Upgrades: Functionality to extend storage duration, increase access slots, and update file storage limits post-deployment.
  • Usage Logic: Processes startOrder and executeOrder transactions to manage secure access sessions.
• Roles: Contracts use RBAC (Role-Based Access Control) to restrict critical operations (like Upgrades or Minting) to the Data Room Owner.