Get MonaCoin price, charts, and other cryptocurrency info.

Just curious, I find the numbers on whattomine to not be accurate for me, on a single 1080TI I consistently was mining ~.33MONA in a 24 hours period. I'd really like to know what other people have accomplished on 1080TI on a per card basis and if I missing something in order to get to the numbers they have on the site which should be possible. Also, Ill point out that according to the miner software I was even ABOVE the hashrates that whattomine uses to figure their numbers. They use 64MH/sec and my mining software consistently reported me hashing at 68MH/sec so Im wondering what I am missing. Also, not sure if it matters but I was mining on the suprnova pool. Anyone have any input?

Id like to know everyone's opinion on this.

README.md Monacoin Core integration/staging tree What is Monacoin? Monacoin is an experimental digital currency that enables instant payments to anyone, anywhere in the world. Monacoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Monacoin Core is the name of open source software which enables the use of this currency. For more information, as well as an immediately useable, binary version of the Monacoin Core software, see.

License Monacoin Core is released under the terms of the MIT license. See for more information or see. Development Process The master branch is regularly built and tested, but is not guaranteed to be completely stable. Are created regularly to indicate new official, stable release versions of Monacoin Core. The contribution workflow is described in. The developer should be used to discuss complicated or controversial changes before working on a patch set. Developer IRC can be found on Freenode at #monacoin-dev.

Testing Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money. Automated Testing Developers are strongly encouraged to write for new code, and to submit new unit tests for old code. Unit tests can be compiled and run (assuming they weren't disabled in configure) with: make check. Synology Verge XVG Miner. DigiByte DGB Mining Hash Rate Calculator. Further details on running and extending unit tests can be found in. There are also of the RPC interface, written in Python, that are run automatically on the build server.

These tests can be run (if the are installed) with: qa/pull-tester/rpc-tests.py The Travis CI system makes sure that every pull request is built for Windows, Linux, and OS X, and that unit/sanity tests are run automatically. Manual Quality Assurance (QA) Testing Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.

Translations We only accept translation fixes that are submitted through. Translations are converted to Monacoin periodically. Translations are periodically pulled from Transifex and merged into the git repository.

See the for details on how this works. Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.