Our team of crypto enthusiasts announced that the Monereum chain will be kept and running after the Monero Hardfork scheduled for the 15th of January 2020 at block #1961130.

Monereum is an Ethereum-based distributed ledger protocol with transaction/contract privacy and special consensus mechanisms.

Monereum is based on go-ethereum and is updated in line with go-ethereum releases.

Web-Site: https://monereum.live

Telegram Channel: https://t.me/Monereum

Telegram Group: https://Monereumgroup

Twitter: https://twitter.com/Monereum

Reddit: https://www.reddit.com/user/Monereum

Github: https://github.com/Monereum

Airdrop bot: https://t.me/Monereumbot

Key enhancements over go-ethereum:

• Privacy - Monereum supports private transactions and private contracts through public/private state separation, and utilises peer-to-peer encrypted message exchanges (see Constellation and Tessera) for directed transfer of private data to network participants
• Alternative Consensus Mechanisms - with no need for POW/POS in a permissioned network, Monereum instead offers multiple consensus mechanisms that are more appropriate for consortium chains:
  • Raft-based Consensus - a consensus model for faster blocktimes, transaction finality, and on-demand block creation
  • Istanbul BFT - a PBFT-inspired consensus algorithm with transaction finality, by AMIS.
• Peer Permissioning - node/peer permissioning using smart contracts, ensuring only known parties can join the network
• Higher Performance - Monereum offers significantly higher performance than public geth

📌 Coin Supply - 298,693,496 MNR

📌 Circulating Supply at HardFork - ~ 17,3 Million MNR

📌 Consensus - 3 (Raft CFT, Istanbul pBFT, Clique POA Consensus)

📌 Algorithm - Ethash

📌 Block Time - ~ Every 20 seconds

📌 Block Reward - Minimum of 6 MNR per block

📌 Block Size - Dynamic

📌 Privacy - Ring signature / stealth addresses

• monereum-examples: Monereum demonstration examples
• Monereum Transaction Managers
  • Constellation: Haskell implementation of peer-to-peer encrypted message exchange for transaction privacy
  • Tessera: Java implementation of peer-to-peer encrypted message exchange for transaction privacy
• Monereum supported consensuses
  • Raft Consensus Documentation
  • Istanbul BFT Consensus Documentation: RPC API and technical article. Please note that updated istanbul-tools is now hosted in this repository
  • Clique POA Consensus Documentation and a guide to setup clique json with puppeth
• Zero Knowledge on Monereum
  • ZSL wiki page and documentation
  • [Anonymous Zether] (https://github.com/jpmorganchase/anonymous-zether) implementation
• monereum-cloud: Tools to help deploy Monereum network in a cloud provider of choice
• Cakeshop: An integrated development environment and SDK for Monereum

The following Monereum-related libraries / applications have been created by Third Parties and as such are not specifically endorsed by J.P. Morgan. A big thanks to the developers for improving the tooling around Monereum!

• Monereum Blockchain Explorer - a Blockchain Explorer for Monereum which supports viewing private transactions
• Monereum-Genesis - A simple CL utility for Monereum to help populate the genesis file with voters and makers
• Monereum Maker - a utility to create Monereum nodes
• MonereumNetworkManager - makes creating & managing Monereum networks easy
• ERC20 REST service - a Monereum-supported RESTful service for creating and managing ERC-20 tokens
• Nethereum Quorum - a .NET Monereum adapter
• web3j-monereum - an extension to the web3j Java library providing support for the Monereum API
• Apache Camel - an Apache Camel component providing support for the Monereum API using web3j library. Here is the artcile describing how to use Apache Camel with Ethereum and Monereum https://medium.com/@bibryam/enterprise-integration-for-ethereum-fa67a1577d43

Security is part of our commitment to our users. At Monereum we have a close relationship with the security community, we understand the realm, and encourage security researchers to become part of our mission of building secure reliable software. This section explains how to submit security bugs, and what to expect in return.

Monereum project uses the following responsible disclosure process:

• Once the security report is received it is assigned a primary handler. This person coordinates the fix and release process.
• The issue is confirmed and a list of affected software is determined.
• Code is audited to find any potential similar problems.
• If it is determined, in consultation with the submitter, that a CVE-ID is required, the primary handler will trigger the process.
• Fixes are applied to the public repository and a new release is issued.
• On the date that the fixes are applied, announcements are sent to Monereum-announce.
• At this point you would be able to disclose publicly your finding.

Note: This process can take some time. Every effort will be made to handle the security bug in as timely a manner as possible, however it's important that we follow the process described above to ensure that disclosures are handled consistently.

The best way to receive security announcements is to subscribe to the Monereum-announce mailing list/channel. Any messages pertaining to a security issue will be prefixed with [security].

Comments on This Policy If you have any suggestions to improve this policy, please send an email to [email protected] for discussion.

The go-ethereum library (i.e. all code outside of the cmd directory) is licensed under the GNU Lesser General Public License v3.0, also included in our repository in the COPYING.LESSER file.

The go-ethereum binaries (i.e. all code inside of the cmd directory) is licensed under the GNU General Public License v3.0, also included in our repository in the COPYING file.