Skip to main content


These are the building blocks to help you learn about various Arcana Network terms and usage.

💠 Authentication

Authentication is the first step for onboarding users on any application. In the Web3 ecosystem, it is typically not that straightforward. Users are required to have their secret private keys to interact with any blockchain and cryptographic system. Generating and managing private keys is cumbersome and losing them is worse as there is no handy recovery path. There is no central authority. Wallets provide some relief but they are a new paradigm for Web2 users to get used to. Managing secrets for the wallet is an additional overhead that a user has to deal with. All of this makes it very hard for new users to onboard Web3 dApps and the user onboarding experience is very different from the familiar Web2 applications.

💠 Gateway nodes

The gateway node is one of the key internal components of the Arcana Network storage protocol implementation. It handles data storage and access requests made by the dApps through the integrated . Once authenticated, each data access transaction from the SDK that is submitted to the gateway node in response to a dApp user action is first parsed and then relayed to the Arcana blockchain as a meta-transaction. The gateway server initiates a meta-transaction. A meta-transaction is an EVM-compatible transaction that contains the actual initial transaction within it. In using this meta-transaction style architecture the signers themselves do not have to pay the transaction fees and the management of payments is handled by the gateway node itself.

💠 Ownership Transfer

Arcana allows dApp users to upload, and share data in the Arcana Store. This data is of the type file blob. Users have full control over their data and they can choose who they share it with and for how long. Besides data sharing, the data owners can change the data owner as well. They can transfer ownership of a data file to another user by specifying the user's Web3 wallet address. The user need not be on the same dApp to transfer ownership. The ownership transfer is possible even if the recipient user is on a different blockchain.