Two weeks ago, the anticipated beta version of DMDv4 was made available for public testing, with supportive guides on maximizing Open Beta experiences. The level of participation in the Open Beta testing amazes us—thanks to all community members who make it a priority to test-run the use cases on top of DMDv4. With these community efforts, the beta network has also continued to scale up to accommodate more testers for meaningful network improvements and stability prior to the mainnet release.
With Open Beta testing, community members are now conversant with how to set up the DMDv4 and validator nodes, how to set up their Web 3 wallet (e.g., MetaMask) for DMD Diamond Network, how to claim their existing DMDv3 coins as DMDv4 coins (testnet coins for Open Beta), and, importantly, how to navigate Diamond-UI for creating a pool (as a validator candidate) and being a delegated staker on top of a validator.
They have started experiencing the dynamic block-times feature of DMDv4 – how our network creates stable blocks (heartbeat all in 10 minutes) and reacts to incoming transactions in a super fast 1-2 seconds. They are now experiencing how epoch switches and active validator nodes (25 nodes per epoch) are randomly selected (based on staked coins, trust scores, etc., as designed on our network) to participate in the active set. They have also started understanding how reward mechanisms work via running a validator node and being a delegated staker on top of a validator.
In subsequent testing weeks, we look forward to community members testing and running the DAO by initiating and executing proposals for the ecosystem’s improvements and progress. Based on Open Beta testing feedback from community members, we recently released a newer version (1.1) of Diamond-UI – which remains the central point of interaction between our users and the DMD diamond ecosystem. Its interface is user-friendly and more robust with newer updates. There’s an FAQ section on the Diamond-UI website’s footer page. You can also learn more on GitHub to maximize your experience interacting with the DMD diamond ecosystem. DMDv4 Open Beta is open for all to join testing. For big DMD Diamond Coin owners, you can test validator node setup and operations (a minimum of 10,000 DMD is required to run a validator node). Small coin owners can test delegated staking (minimum of 100 DMD), and owners of all sizes who hold DMDv3 in private wallets can test claiming.
Check the GitHub guides to set up a DMDv4 beta and validator nodes and configure your wallet custom network. Delegated stakes can use Diamond-UI to stake on any validators of choice after connecting their wallet and ultimately sharing epoch rewards with them. If you had coins on DMDv3, you would first need to request some testnet DMD Diamond coins from the faucet to your MetaMask DMDv4 address, then test claiming DMDv4 Coins here (although testnet coins! You would claim your main coins on the mainnet!). There’s also a comprehensive guide on claiming DMDv4 coins.
For every node operator, it’s expected you update your validator_node.toml configuration by following the guides below:
In the mining block, after the gas floor, add the following:
# Parity will keep/relay at most 10240 transactions in the queue.
tx_queue_size = 10240
# Maximum amount of memory that the transaction queue can use. Setting this parameter to 0 turns off limiting. (default: 4)
tx_queue_mem_limit = 128
# Maximum number of transactions per sender in the queue. By default, it’s 1% of the entire queue, but not less than 16.
tx_queue_per_sender = 256
# Disables transaction queue optimization to early reject transactions below the minimal effective gas price. This allows local transactions to always enter the pool despite being full but requires additional coverage for every transaction.
tx_queue_no_early_reject = true
In the network block, update these changes:
max_peers = 148
min_peers = 64
In the footprint block, update the cache_size to this value (ensure to remove the # in front of the cache_size parameter):
cache_size = 5120
Then, save the changes and rerun your node!
Furthermore, if your node version is lower than “OpenEthereum/v3.3.5-hbbft-0.9.7”, stop the node and run the following commands to update your node:
1. cd ~/dmdmdv4-testnet
2. git pull && ./build-from-source.sh
Allow it to build. Once it finishes building, start the node again (you now have an updated node running!).
Join us on our Beta Discord Channel for subsequent updates on how to have a seamless Open Beta testing experience! We look forward to your continuous informed feedback on the ideal DMDv4 mainnet launch!
