Fireblocks
Understanding Fireblocks and Its Use
To understand what Fireblocks is and how it is used, you need to understand how blockchain technology works.
“Not your keys, not your cryptos”
This sentence highlights the importance of the difference between centralization and decentralization:
Decentralized Applications
A decentralized application (dApp) stores and manipulates data on a blockchain.
To interact with this type of application, the user must have a WALLET, provided along with their private key.
The user is the only one who knows this key and must not share it with anyone in order to:
Maintain the integrity of their assets (cryptos/NFTs).
Remain the sole person responsible for their wallet.
Centralized Web3 Applications
Examples: Coinbase or Revolut.
These are applications that interact with the blockchain but keep custody of their clients’ assets.
On these platforms:
The user has a wallet, but not the private key.
This is called custodial wallet management.
👉 These centralized applications are responsible for all assets.
Fireblocks in Action
Fireblocks allows you to create a centralized Web3 application. Just like Coinbase or Revolut, Authentify It will guarantee the certificates of authenticity of all its users through Fireblocks.
Benefits
No NFTs are sold on a secondary market.
No loss of access to Authentify It advantages in case of asset transfer to an external wallet (since this violates the terms of use).
Simplifies blockchain usage for the user:
They only need to log in with an email to access their assets.
Why is this an Advantage?
As explained on the blockchain section, Authentify It aims to provide a cross-chain solution.
Brands will be able to create products and put certificates on the blockchain of their choice (among those available).
If Authentify It were decentralized:
Users would need a wallet for each blockchain.
They would also need to manage multiple secret keys, which can quickly become overwhelming for beginners.
Learn More
📄 For more details, read: Authentify It x Fireblocks in this documentation
Last updated