VREM Token Distribution
10% of the tokens are allocated to the initial development team of VREM. This is to incentivize the initial team, which faced substantial costs in hardware, software, network, and operational personnel aspects to develop and launch the VREM network. Additional funding is needed from VREM investors, and 10% of the tokens will be allocated to them. However, the VREM Foundation will still allocate most of the VREM token supply to VREM community users and contributors, as detailed in the distribution chart below.
Before achieving complete decentralization and self-sustainability, the VREM Foundation will support the VREM ecosystem. As part of the Foundation's duties, it will distribute VREM tokens mainly for four clear purposes:
- VREM User Incentives
- VREM Network Operations
- VREM Ecosystem Developers
- Early Investment Institutions
(Note: The detailed distribution table is not provided but can be added based on the percentages and categories mentioned.)
Initial Development Team: 10%
This allocation is to incentivize the initial team responsible for developing and launching the VREM network, which requires significant costs in terms of hardware/software/network and operational personnel.
VREM Investors / Advisors: 10%
Early Investment Institutions and Additional funding is needed from VREM investors. For early backers and supporters of the VREM project
The VREM Foundation will oversee the distribution and ensure that the tokens are allocated as per the above structure. Before achieving full decentralization and self-sustainability, the VREM Foundation will support the VREM ecosystem.
User Incentives: 80%
A significant portion is allocated for user incentives to encourage adoption and active participation in the VREM ecosystem. To incentivize developers to build on and enhance the VREM platform.
| % | Category | Description |
|---|---|---|
| 80% | VREM Community | Most of these tokens will beallocated to users. some of the tokens will be used for the ecosystem fund.and for network operations |
| 10% | Initial Team | Initial contributor to VREM, lock-up for two years, linear release after 2 years |
| 10% | Investors / Advisors | VREM investors provided funding that enabled VREM to support the VREM project. Locked for two years, linear release after 2 years |
Technical Information
Contract Address (Pending Public Release):
VREM Token (VREM): [Not Yet Released]
Wallet Addresses (Pending Public Release):
VREM Foundation Wallet: [Not Yet Released]
User Incentive Distribution Wallet: [Not Yet Released]
Developer Incentive Wallet: [Not Yet Released]
The addresses above are placeholders and have not been made public yet. Always verify contract and wallet addresses from official sources before making any transactions. Be cautious about interacting with unofficial or suspicious addresses to prevent potential financial losses or fraud.
Ecosystem Partner Nodes
Partner nodes apply the SDK to wallets being deployed to expand the ecosystem and provide direct key management services to users. To qualify as a partner node, 1 million VREM tokens must be staked for one year, after which they can be unstaked. The staked VREM will be linearly released over two years. As a node reward, they will receive 10% of the VREM amount earned by users when they activate biometric recognition features + asset verification.
Security Audit
A comprehensive security audit was conducted on the protocol, encompassing both off-chain and on-chain components. The audit was particularly focused on evaluations related to the use of blockchain technology, cryptography, and smart contracts. The areas covered in the audit include:
Implementation Correctness
Ensuring the cryptographic structures and primitives are correctly implemented.
Proper use of smart contract structures.
Implementation Errors
Checking for common and specific case implementation mistakes.
Adversarial Behavior & Other Attacks
Evaluating the code for potential adversarial actions.
Identifying vulnerabilities that could lead to attacks.
Key Management
Secure storage of keys.
Proper cryptographic management.
Handling of signing keys.
Exposure of Critical Information
Ensuring no critical information is exposed during user interactions.
Resistance to DDoS Attacks
Evaluating the protocol's resilience against Distributed Denial of Service attacks and other similar threats.
Vulnerabilities Leading to Adversarial Actions
Identifying code vulnerabilities that could lead to adversarial operations and other attacks.
Prevention of Malicious Attacks
Evaluating the protocol's defenses against malicious attacks and other exploitation methods.
Performance Issues
Identifying any performance-related issues or other potential impacts on performance.
Data Privacy, Data Leaks, & Information Integrity
Ensuring data privacy is maintained.
Checking for potential data leaks.
Ensuring the integrity of information.
Improper Permissions, Privilege Escalation, & Overstepping
Evaluating the protocol for any instances of improper permissions.
Checking for potential privilege escalation vulnerabilities.
Ensuring no overstepping of boundaries.
The security audit was crucial in ensuring the safety and reliability of the protocol. It provided valuable insights into potential vulnerabilities and areas of improvement, ensuring that users can trust the protocol's integrity and security.