Rizenet Blockchain Design Requirements
The Rizenet blockchain is purposely optimized for asset tokenization, designed to meet the rigorous security and compliance standards demanded by institutional players. It enables institutions to validate and manage interactions with counterparties while adhering to strict legal obligations and risk management protocols. A key feature is the controlled deployment of smart contracts, restricted to whitelisted addresses, ensuring safeguards for non-tech-savvy users.
The table below outlines the core requirements and their corresponding impact, demonstrating how Rizenet is optimized for high performance, security, and scalability in tokenized asset management.
R1: Permissioned Validators Set
Description: Only pre-selected validators process transactions into blocks.
Impact:Reduced third party risks.
R2: EVM Compatibility
Description: Smart contracts executed by the Ethereum Virtual Machine (EVM).
Impact: Facilitates interoperability and enables use of existing tools, standards, and applications.
R3: Native Gas Token
Description: Uses a custom gas token for network fees.
Impact: Driving network engagement and allocates network resources efficiently.
R4: Permissioned Smart Contract Deployment
Description: Limits smart contract deployment to authorized addresses.
Impact: Balances openness with control, ensuring network integrity while supporting community activity.
R5: High Throughput
Description: Supports computationally intensive applications.
Impact: Essential for business intelligence, workflow automation such as automated portfolio rebalancing and times of high volatility.
R6: Low-Cost Transactions
Description: Using the network and its applications is not expensive.
Impact: Encourages broader adoption, supports the Web3 communication protocol and enables oracles to commit up to date information more often.
R7: Auditability
Description: Allow auditors to inspect the chain data.
Impact: Builds institutional and public trust.
R8: Data Privacy
Description: Enable asset owners to conceal their identity and quantity of tokens to the public.
Impact: Allow pseudo-anonymity while developping more robust solutions using fully homomorphic encryption or Zero-Knowledge Proofs. Align with privacy laws for broader adoption.
R9: Interoperability with Other Networks
Description: Connects to other high-liquidity networks and applications.
Impact: Attracts investors by providing a seamless user experience and unified liquidity.
R10: BFT Consensus Mechanism
Description: Use Byzantine Fault Tolerance (BFT) to protect against faults or malicious actors.
Impact: Ensures robustness and security, maintaining operations even under adversarial conditions.
R11: High Availability
Description: Maintains constant network operation with minimal downtime.
Impact: Guarantees reliability and uninterrupted service for all network functions.
R12: Geographically Distributed Nodes
Description: Spreads nodes across various regions or specific regions for custom networks.
Impact: Improves network resilience, reducing risks associated with specific regional issues. Supports region-specific sub-networks.
R13: Fast Finality
Description: Quick transaction finalization without traditional delays.
Impact: Improves transaction efficiency and velocity of money, reducing counterparty risk.
R14: Self-Sovereignty
Description: Allows the network to function independently and make decisions autonomously.
Impact: Eliminates dependency on external systems, enhancing control and trust within the network.