*** BETA SOFTWARE - USE AT YOUR OWN RISK ***

MUE 2.0 MonetaryUnit Core integration/staging repository

MonetaryUnit is a cutting edge cryptocurrency, with many features not available in most other cryptocurrencies.

• 100% Proof of Stake 3.0 Consensus protocol, allowing very low transaction fees and energy expenditure, and staking rewards to all participants in the network
• Masternode technology used to secure the network and provide the above features, each Masternode is secured with collateral of 500K MUE
• Decentralized blockchain voting utilizing Masternode technology to form a DAO. The blockchain will distribute monthly treasury funds based on successful proposals submitted by the community and voted on by the DAO.

139439504 MonetaryUnit was produced for swapping.

Coin Specs

Hash Type	SHA256
Block Time	40 Seconds
Difficulty Retargeting	Every 10 blocks
Max Coin Supply (PoS Phase)	4 billion

PoS Rewards Breakdown

Block Height	Reward	Masternodes	Stakers	Budget
1-96514012	36 MUE	18 MUE	18 MUE	4 MUE
96514013+	0 MUE	0 MUE	0 MUE	0 MUE

MUE resources

• Client & Source: Client Binaries Source Code
• Links: Homepage CoinBuy CryptoFeed

Nodes & ports

dns1.monetaryunit.org
dns2.monetaryunit.org
dns3.monetaryunit.org
192.99.217.102
164.132.151.109
p2p port :19687

Importing wallet balances from MUE 1.0.3 wallets into MUE 2.0 wallets

MUE has migrated to a completely new codebase, and as such, is no longer compatible with the previous network and blockchain used by the old 1.0.3 wallets. As part of the migration to the MUE 2.0 wallets and network, users can redeem their old wallet balances* into their new wallets. This process is simple, but if not done correctly could risk you losing all your coins.

NEVER UNDER ANY CIRCUMSTANCES GIVE AWAY YOUR PRIVATE KEYS TO ANYONE, THE ONE WHO HAS YOUR KEYS CONTROLS YOUR MUE

Please follow these simple steps

1. BACKUP your old MUE wallet, make multiple copies (most critical is your wallet.dat file!)
2. Copy that back up somewhere safe e.g USB drive, seperate computer.
3. Make a list of your wallet addresses (you may need to look in "coin control" for a full list). If coin control is not available in the send tab of your wallet, then activate this under śettings / Options / Wallet / Enable Coin Control Features
4. For each wallet address (that you know has a balance of MUE) in debug console run dumpprivkey 7enteryourmuewalletaddresshere
5. Record the private key (securely & safely) that is printed there
6. As per item 2) Backup your old MUE wallet (just to be sure). Again, critical is your wallet.dat file
7. Uninstall your old MUE wallet IF you are installing the 2.0 wallet on the same machine (to avoid any conflicts). For the sake of safety, you may also rename your MUE folder to say MUE-1.0.3-backup so it is preserved on your machine if things go wrong.
8. Install the new MUE 2.0 wallet
9. In debug console run importprivkey KenterYourPrivateKeyHere "comment"

You should now see your old MUE balance re-instated into the new MUE 2.0 wallet. For security, we strongly recommend you now send those coins to yourself to a newly generated receive address created in your own 2.0 wallet.

For support, please don't hesitate to join us in our chat platform at http://discord.gg/5PD3X7G

*Only transactions up to and including block 833658 will be processed

How to run the linux monetaryunit-qt executable under Windows Subsystem Linux

Please follow these steps

1. (Windows) Install VcXsrv
2. (Windows) Run XLaunch
   1. Display settings: Keep default settings (Multible Windows + Display number = -1)
   2. Client startup: Keep default settings (Start no client)
   3. Extra settings: Enable all checkboxes especially "Disable access control" or it will not work.
   4. (Optional) Save the settings for later use.
3. (WSL) Add export DISPLAY=$(grep -m 1 nameserver /etc/resolv.conf | awk '{print $2}'):0.0 to the end of your .bashrc
4. (WSL) Start monetaryunit-qt
5. (Optional) In case this did not work. Most likeley your windows firewall is blocking the connection. During the first start of XLaunch some rules will be set. Search for the blocking firewall rules "VcXsrv windows xserver" and disable them.