Wallets Overview
Interacting with the Brixs Network requires a highly secure wallet. Brixs supports a wide variety of wallet architectures to suit both institutional treasuries and retail Web3 users.
Custody Models Explained
Custodial Wallets
Your keys are managed by a trusted third party. Best for enterprise applications focusing on user experience.
Non-Custodial Wallets
You hold your own private keys. Maximum security and autonomy.
Security Warning
"Not your keys, not your coins." If using a non-custodial wallet, you must back up your seed phrase securely. Loss of a seed phrase means permanent loss of assets.
Integration Pathways
Phase 1: Engine Initialization
The first phase requires a comprehensive setup of the execution environment. The Brixs Native EVM initializes the state and establishes secure connections with the P2P network. This ensures that when the DPoS Sequencer begins proposing blocks, there are no bottlenecks in transaction ingestion.
Transactions are ordered securely by the Encrypted Mempool to prevent MEV. The Native EVM processes transactions while the ZK-SNARK Prover Engine generates validity proofs. Once processed, the Sequencer commits the block to the Ethereum L1, achieving Rollup Finality and inheriting Ethereum's cryptographic security.