Frequently Asked Questions

Glossary

The Transactions DAG is a Directed Acyclic Graph that works like IOTA's. Transactions define inputs and outputs, and new transactions use old transactions as inputs.

The Consensus DAG is a Directed Acyclic Graph that works like Nano's. Every Merit Holder has their own blockchain of Difficulty Updates and Gas Price sets. It also keeps track of, and staples, Verifications.

Merit Caching is a Consensus Mechanism. All transactions are published to a DAG. Merit Holders submit verifications that are valid as soon as they are received. A transaction is confirmed when it gets 50.1% of the weight. The blockchain archives these verifications. Mining the blockchain earns weight.

General

We aimed to launch the mainnet in Q2 of 2019. Due to delays with growing our team and building a quality GUI, this has been pushed back.

We have already launched multiple Developer Testnets, which were open to anyone who can compile their own node. When the software is more user-friendly, we will launch Public Testnets, where anyone can download the node software and partake.

There is no total supply. Meros will always have a block reward, yet it will decrease significantly over time. For more info, please see the Mining tab.

We cannot state the premine as a percent due to the lack of a total supply. That said, the premine is equivalent to seven weeks of generated coins. Two weeks will be released at launch, with one more week every six months thereafter.

Mining

The Block Reward is variable from Block to Block, based on the hash rate. If there are more miners, indicating a higher mining profitability, the Block Reward decreases. If there are less miners, indicating a lower mining profitably, the Block Reward increases. The Block Reward ranges from 50 MR to 0.0000001000 MR.

No. Meros uses a pool resistant mining algorithm to encourage further decentralization.

Trading

Not yet, though we are in talks with multiple exchanges.

Development

Meros can be improved and we plan to do so. We won’t hard fork if there isn’t enough of a reason to, but the plan is to do a hard fork every 6 months. Every commit is reviewed when it’s submitted, and the full difference between the two codebases will also be reviewed before we fork to it. We’ll also thoroughly test new codebases on a testnet.

You can check out our GitHub and go over the TODO list or the issues.