monacoinproject / monacoin Goto Github PK

License: MIT License

QMake 0.01% Python 16.44% Makefile 1.00% Shell 1.26% C++ 65.77% C 12.26% HTML 0.20% Objective-C++ 0.05% Assembly 0.26% Java 0.28% M4 1.88% Sage 0.28% Scheme 0.05% CMake 0.26%

monacoin's Introduction

Monacoin Core integration/staging tree

https://monacoin.org

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 https://monacoin.org.

License

Monacoin Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

Development Process

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of Monacoin Core.

The contribution workflow is described in CONTRIBUTING.md and useful hints for developers can be found in doc/developer-notes.md.

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 unit tests 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. Further details on running and extending unit tests can be found in /src/test/README.md.

There are also regression and integration tests, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: test/functional/test_runner.py

The Travis CI system makes sure that every pull request is built for Windows, Linux, and macOS, 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 Bitcoin Core's Transifex page. Translations are converted to Monacoin periodically.

Translations are periodically pulled from Transifex and merged into the git repository. See the translation process 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.

Translators should also subscribe to the mailing list.

monacoin's People

Stargazers

Watchers

monacoin's Issues

Build Wallet From QT 4.8

Hello to everyone!
So i want to make a different version of this wallet but when i try to build with QT 4.8.7 i get the follow error

Using the QT 4.8.7 MSVC2008 32 bit
10:34:48: Configuration is faulty. Check the Issues view for details.
Error while building/deploying project bitcoin-qt (kit: Desktop Qt 4.8.7 MSVC2008 32bit)
When executing step "Make"

Windows 10 64bit
AMD FX9590 5.3Ghz
16 GB ram
GTX1080
M.2 512GB

Upgrading from 0.8 to 0.15

plz delete

Failed to build on Ubuntu Hirsute 21.04

I tried to build Monacoin on Ubuntu Hirsute 21.04 (PPA), but I got the following error.

g++ -std=c++11 -DHAVE_CONFIG_H -I. -I../src/config   -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -I.  -DBOOST_SP_USE_STD_ATOMIC -DBOOST_AC_USE_STD_ATOMIC -pthread -I/usr/include -I./leveldb/include -I./leveldb/helpers/memenv   -I./secp256k1/include -I./univalue/include   -pthread -DHAVE_BUILD_INFO -D__STDC_FORMAT_MACROS  -Wstack-protector -fstack-protector-all -Wall -Wextra -Wformat -Wvla -Wformat-security -Wno-unused-parameter -Wno-implicit-fallthrough    -fPIE -g -O2 -MT libbitcoin_server_a-httpserver.o -MD -MP -MF .deps/libbitcoin_server_a-httpserver.Tpo -c -o libbitcoin_server_a-httpserver.o `test -f 'httpserver.cpp' || echo './'`httpserver.cpp
In file included from /usr/include/boost/smart_ptr/detail/sp_thread_sleep.hpp:22,
                 from /usr/include/boost/smart_ptr/detail/yield_k.hpp:23,
                 from /usr/include/boost/smart_ptr/detail/spinlock_std_atomic.hpp:18,
                 from /usr/include/boost/smart_ptr/detail/spinlock.hpp:36,
                 from /usr/include/boost/smart_ptr/detail/spinlock_pool.hpp:25,
                 from /usr/include/boost/smart_ptr/shared_ptr.hpp:29,
                 from /usr/include/boost/shared_ptr.hpp:17,
                 from /usr/include/boost/signals2/signal.hpp:21,
                 from ./util.h:34,
                 from httpserver.cpp:9:
/usr/include/boost/function_output_iterator.hpp:14:1: note: ‘#pragma message: This header is deprecated. Use <boost/iterator/function_output_iterator.hpp> instead.’
   14 | BOOST_HEADER_DEPRECATED("<boost/iterator/function_output_iterator.hpp>")
      | ^~~~~~~~~~~~~~~~~~~~~~~
httpserver.cpp:74:10: error: ‘deque’ in namespace ‘std’ does not name a template type
   74 |     std::deque<std::unique_ptr<WorkItem>> queue;
      |          ^~~~~
httpserver.cpp:33:1: note: ‘std::deque’ is defined in header ‘<deque>’; did you forget to ‘#include <deque>’?
   32 | #include <support/events.h>
  +++ |+#include <deque>
   33 | 
httpserver.cpp: In member function ‘bool WorkQueue<WorkItem>::Enqueue(WorkItem*)’:
httpserver.cpp:92:13: error: ‘queue’ was not declared in this scope; did you mean ‘Enqueue’?
   92 |         if (queue.size() >= maxDepth) {
      |             ^~~~~
      |             Enqueue
httpserver.cpp:95:9: error: ‘queue’ was not declared in this scope; did you mean ‘Enqueue’?
   95 |         queue.emplace_back(std::unique_ptr<WorkItem>(item));
      |         ^~~~~
      |         Enqueue
httpserver.cpp: In member function ‘void WorkQueue<WorkItem>::Run()’:
httpserver.cpp:106:35: error: ‘queue’ was not declared in this scope; did you mean ‘Enqueue’?
  106 |                 while (running && queue.empty())
      |                                   ^~~~~
      |                                   Enqueue
httpserver.cpp:110:31: error: ‘queue’ was not declared in this scope; did you mean ‘Enqueue’?
  110 |                 i = std::move(queue.front());
      |                               ^~~~~
      |                               Enqueue

The complete build log can be found at here.

The error message says the std::deque is declared in <deque>, but this header file is not included in the source file.
It can be solved by just adding the "#include <deque>" directive.

This issue is also reported in the Litecoin repo litecoin-project/litecoin#632 and was solved by the PR litecoin-project/litecoin#643.

(In addition to this, the repo is not maintained for more than two years.
You should catch up to the upstream repo, or may cause a significant security defect.)

RPC連続アクセスが制限されます

localhostよりRPCに高頻度でアクセスしています。
しかし他のcoindと比べると500エラーによりアクセスを制限されます。
おそらくDDOS対策が組み込まれていると思われますが、コマンドや起動オプションで解除できませんでしょうか？

Monacoin 0.17.1

ひとまずmonacoinprojectとは分けて作成。
https://github.com/xwatanabek/monacoin

・Auto wallet backup は廃止
・hardcoded seeds は以前のまま
（ただし実際はほぼ使用されないと思われる）
・feeは現状維持

人柱版の実行ファイルもwin版のみ用意してあります。
https://github.com/xwatanabek/monacoin/releases/tag/preview-0.17.1

コイン画像とか要望があれば変更しても良いかも。

monacoind(0.16.3) update for bittrex

I asked bittrex to update monacoind and the following sentences came back.
"If you are not one of the Coin's developers or representative from the coin team we will not be responding to your ticket. Please do not submit this form if you answer NO."

Tentatively, can you approve here by saying representative from the coin team?

Bittrexにmonacoindのアップデートをお願いしたところ以下のような文章が返ってきました。
コインの開発者やコインチームの代理人でなければ、あなたのチケットには返答しません。あなたが「いいえ」と答えた場合は、このフォームを提出しないでください。

仮に、ここで代理人として承認をしていただけることは可能でしょうか？

Is there a release note for 0.20.2?

I'd like to know what changed.

How do you mine Monacoin?

I downloaded the Monacoin wallet and got it synched and caught up but after that, I have no clue what I'm supposed to do, I know it needs files and codes to work but that's about it. I would greatly appreciate any help with what I need to do.

Mailing list

Could you open a project page for monacoin in Sourceforge? (or some other place having mailing list supports, but sf may be the best)

We may need mailing lists to discuss and maintain monacoin and its community from technology aspect.

thanks!

Hi Dev, please make Monacoin listing on Binance or Huobi or OKEx or Kucoin, please....

NP

wiki の無効化

wikiが誰でも編集できると報告に来てくれたようです。
https://github.com/monacoinproject/monacoin/wiki/Publicly-Editable-wiki-bug

wiki の無効化方法です。
https://help.github.com/articles/disabling-wikis/

bootstrap.datがある条件を満たすと読み込めなくなる

bootstrap.datのブロックの順序が正しくない場合、そこで読み込みを停止してしまいます。

blk.dat内のブロックは正しくない順序になる可能性があるそうです。
https://learnmeabitcoin.com/technical/blkdat
一般的にbootstrap.datはblk.datを連結して作成するので、読み込みが途中で止まる可能性があります。

以下のbootstrap.pyを実行し検証しました。

import requests
import json

magicbyte = "fbc0b6db"
apiurl = "https://insight.electrum-mona.org/insight-api-monacoin/rawblock/"
# block 0-10
blockhash = [
"ff9f1c0116d19de7c9963845e129f9ed1bfc0b376eb54fd7afa42e0d418c8bb6",
"a378b7a601e00a877160357137c72befc6c06c22c5997eedb30ce9976710d28b",
"8c28b5233fc0023d9ed26cb1f7fcbff57a062cfd823d7b8b33f5a0534e054682",
"36a3b7235aa7a05d654a2afe7b3b3faade820e99a70db0262b5afd2d624412e9",
"afc9e42b4ab917ccf9f7c7ab5b98a817a61d91e8da8c18c53ff748ea12976363",
"f88c455d4d9c22654868ad8bdbead18d5decc3d4b4f105c5f9e2b4391297d600",
"e1b2fb921ff4f15ce5b2573595f2a835ab9cd109624c4e3d4324a97ca4d3380d",
"6916c6ccdfc826a0aab14faaa7f6c7fc419d118f5ab17607219c59e1de1754d4",
"4f429775bb724c033d4a2c3e982c08918d31e5766de94b7d7e6656ceacd5fef2",
"d9aef59eb07dc561f099d0e62babe5a4dac431ceed121b3a605e577ccd19c400",
"e69143d5e252aff8d4013ea7487e52670905eac5edd5e75708526b3c20addd7d"
]

blockdata = []

for i in blockhash:
    block = json.loads(requests.get(apiurl+i).text)["rawblock"]
    blockdata.append(magicbyte + bytes.fromhex(hex(len(block)//2)[2:].zfill(8))[::-1].hex() + block)

correct_order_bootstrap = "".join(blockdata)

# block_5とblock_6を入れ替える
blockdata[4], blockdata[5] = blockdata[5], blockdata[4]
wrong_order_bootstrap = "".join(blockdata)

with open("bootstrap_correct.dat", mode="wb") as f:
    f.write(bytes.fromhex(correct_order_bootstrap))
with open("bootstrap_wrong.dat", mode="wb") as f:
    f.write(bytes.fromhex(wrong_order_bootstrap))

bootstrap_correct.datを使用した場合、debug.logを確認すると10ブロックまで読み込んでいましたが、bootstrap_wrong.datを使用した場合は4ブロックまでしか読み込みませんでした。

Updated new wallet but always reports: Monacoin is downloading blocks...

it seems something is not right with the new wallet.... it always reports downloading blocks even when it is up-to-date....

monacoin-cli getblocktemplate
error code: -10
error message:
Monacoin is downloading blocks...

Incoming transaction

Its litecoin icon.

nFeePaid can be overflow.

From @wakiyamap #72 (comment)

If value of nFeePaid is 10512000000000000(MAX_MONEY), it's overflow?
nFeePaid * 1000 =
10,512,000,000,000,000,000
int64_t of max is
9,223,372,036,854,775,807

So......how about adding the following?
assert(nFeePaid<= MAX_MONEY);

Personaly, I'd like to believe that maybe this isn't the case.

v0.13.2.2-a8aa999 doesn't start

Dear Monacoin Team,
A few days ago, I downloaded the new Monacoin version from your website. Unfortunately, this version does not start, please see the screnshot:

Maybe there are more people with the same start error message?
Could you help me please? Currently, I have no access to my coins.
Thanks a lot :)
Kai

Lyra2REv3

Is there a chance switch to Lyra2REv3 (Made by Vertcoin) to avoid ASICs?

Digisheld or Digishield?

monacoin/src/chainparams.cpp

Line 87 in af84510

consensus.nPowTargetTimespanDigisheld = 1.5 * 60;

Digisheld or Digishield?

it's not an actual problem, but i wonder to know... 🤔

Release v0.20.3.

libbitcoinconsensusのこと

前からArchのパッケージを維持していて、一つのことを気づきました。他のフォークはlibbitcoinconsensusをリネームしてるけどmonacoinはそうしない。必要ないでしょうか？

たとえば、0.15.1向けこのチェンジを行いました
https://aur.archlinux.org/cgit/aur.git/tree/0001-rename-libbitcoinconsensus-to-libmonacoinconsensus.patch?h=monacoin-qt&id=78c5666016dfeaa451f8a4652012084306832335

第三者のアプリ開発に必要ないならあんまり気にせず0.16.3に更新しますが、あったほうがいいなら本家に投入したいと思う

Fix the invalid value in MESSAGE_MAGIC

リポジトリがカオスな件

問題点

現在このリポジトリには以下のような問題が放置されています。

「0.8.7.1」といったバージョン番号を名前としたブランチが存在する
しかもブランチ0.8.7.0がタグ0.8.7.0と違うコミットを指している
ブランチ「8.6.1」の存在（0.8.6.1では？）
ブランチにあってタグに無いバージョン番号（0.8.6台）
ブランチmasterが遥か後方のバージョン0.8.6.2を指している
それに対する対応が何故か「リポジトリのHEAD（デフォルトブランチ）をブランチ0.8.7.1にする」というもの
0.8.7.1の次が0.10.2.2という謎の命名規則
しかもその0.10.2.2にどんどんコミットが作られてnextブランチと全く違った内容になっており、開発者のコメントが読めるブログなども無いためどちらが次期バージョンなのかわからない
さらにこのissueを書いている間にブランチ0.10.2.2-Lyra2REv2が作られもはやカオス

これでは他の開発者のみならず利用者も混乱し、Monacoinの成長を大いに阻害する要因になっていると思います。

解決案

バージョン番号を名前としたブランチ（ただし0.10.2.2以外）をタグに移行して削除する
その際にブランチ8.6.1をタグ0.8.6.1に修正する
ブランチmasterを現行バージョンの0.8.7.1に同期させ、リポジトリのデフォルトブランチをmasterに戻す
nextと0.10.2.2のどちらが次期バージョン開発ブランチなのかはっきりさせ、それをnextブランチとする（nextが次期バージョンでないなら削除する）

開発者が全くコメントを発信せず「謎の人物」になってしまっていることもMonacoin発展の阻害要因だと思うので、できれば開発者の意向が読めるブログなども作ってくださると嬉しいのですが、少なくともこれらの点は修正していただきたいです。

バージョン番号の命名規則について

なお、バージョン番号の命名規則には広く使われているSemantic Versioningをおすすめします。

これはバージョン番号はa.b.cのように３段階にし、マイニングアルゴリズム変更など互換性のない変更ではaの数を、機能拡張など互換性を保った変更はbの数を、バグフィクスなどの軽微な変更ではcの数を上げるというものです。

広く使われている命名規則の方が新しい開発協力者が集まりやすいと思います。バージョン１からはそのようにしてみてはいかがでしょうか？

csv,segwitのsoftforkについて

getblockchaininfoのリターンで定義されているstartTime 1488931200を超えても
bip9_softforksのcsv,segwitのstatusがstartedにならずdefinedになっています

Chainfiles please?

Hi Guys,

downloaded the Monacoin Core wallet and now i have to download the last 4 years and 38 hours..... This takes years to download..

My question.. You have chainfiles or a way to speed up the download that i can use this wall?

If yes, please send me a link..

Best regards,
Jan

Huge amount of stuck MONA coins on Livecoin

There's a big amount of MONA coins stuck on Livecoin due to the attack, take your responsibility and fix this.

Message from Livecoin:
"Dear clients, as you all know, MONA network has been attacked recently, and all the exchanges suffered at some point due to fake incoming transactions. The fact of attack has been publicly acknowledged by the developers.

We contacted the developers several times on the issues concerning the cancellation of fake transactions or providing compensations for the losses sustained by the exchanges as a result of the hackers' attack on MONA blockchain. Today we got an answer: the developers won't take any actions. We, in our turn, have nothing to do than keep MONA deposit/withdrawal closed, in accordance with the terms of services providing. If the developers of MONA will ever take steps to cover the losses, incurred by the attack on the blockchain, we would be glad to make this asset available again. If you want to influence the situation somehow, please, send collective claims to MONA developers."

Source: https://www.livecoin.net/news/view/719?lang=en

Is help message of rpcport wrong?

$ ./monacoind --help | grep rpcport
-rpcport= Listen for JSON-RPC connections on (default: 9402 or testnet: 19402)

$ grep -n 9402 bitcoinrpc.cpp
42: return GetBoolArg("-testnet", false) ? 9402 : 19402;

Which is wrong?

Add getauxblock

Problem implementing mining-pool support for Monacoin

I'm currently working to implement support for Monacoin into our stratum mining engine: https://github.com/coinfoundry/miningcore

Supporting new coins based on bitcoin-core is normally straight forward but somehow I must be missing something. Below is a link to the part where the hashing is configured for all supported coins:

https://github.com/coinfoundry/miningcore/blob/master/src/MiningCore/Blockchain/Bitcoin/BitcoinJobManager.cs#L248

Do you see anything that's incorrect?

test_monacoin errors

Running test_monacoin I get lots of errors, and finally a segfault...

OS: Ubuntu 17.04

test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(54): error: in "main_tests/subsidy_limit_test": check MoneyRange(nSum) has failed
test/main_tests.cpp(56): error: in "main_tests/subsidy_limit_test": check nSum == 8399999990760000ULL has failed [10515161278759000 != 8399999990760000]
test/miner_tests.cpp(226): error: in "miner_tests/CreateNewBlock_validity": check ProcessNewBlock(state, chainparams, __null, pblock, true, __null, false) has failed
test/miner_tests.cpp(227): error: in "miner_tests/CreateNewBlock_validity": check state.IsValid() has failed
test/miner_tests.cpp(226): error: in "miner_tests/CreateNewBlock_validity": check ProcessNewBlock(state, chainparams, __null, pblock, true, __null, false) has failed
test/miner_tests.cpp(227): error: in "miner_tests/CreateNewBlock_validity": check state.IsValid() has failed
test/miner_tests.cpp(226): error: in "miner_tests/CreateNewBlock_validity": check ProcessNewBlock(state, chainparams, __null, pblock, true, __null, false) has failed
test/miner_tests.cpp(227): error: in "miner_tests/CreateNewBlock_validity": check state.IsValid() has failed
test/miner_tests.cpp(226): error: in "miner_tests/CreateNewBlock_validity": check ProcessNewBlock(state, chainparams, __null, pblock, true, __null, false) has failed
test/miner_tests.cpp(227): error: in "miner_tests/CreateNewBlock_validity": check state.IsValid() has failed
test/miner_tests.cpp(226): error: in "miner_tests/CreateNewBlock_validity": check ProcessNewBlock(state, chainparams, __null, pblock, true, __null, false) has failed
test/miner_tests.cpp(227): error: in "miner_tests/CreateNewBlock_validity": check state.IsValid() has failed
test/miner_tests.cpp(226): error: in "miner_tests/CreateNewBlock_validity": check ProcessNewBlock(state, chainparams, __null, pblock, true, __null, false) has failed
test/miner_tests.cpp(227): error: in "miner_tests/CreateNewBlock_validity": check state.IsValid() has failed
test/miner_tests.cpp(226): error: in "miner_tests/CreateNewBlock_validity": check ProcessNewBlock(state, chainparams, __null, pblock, true, __null, false) has failed
test/miner_tests.cpp(227): error: in "miner_tests/CreateNewBlock_validity": check state.IsValid() has failed
test/miner_tests.cpp(226): error: in "miner_tests/CreateNewBlock_validity": check ProcessNewBlock(state, chainparams, __null, pblock, true, __null, false) has failed
test/miner_tests.cpp(227): error: in "miner_tests/CreateNewBlock_validity": check state.IsValid() has failed
test/miner_tests.cpp(226): error: in "miner_tests/CreateNewBlock_validity": check ProcessNewBlock(state, chainparams, __null, pblock, true, __null, false) has failed
test/miner_tests.cpp(227): error: in "miner_tests/CreateNewBlock_validity": check state.IsValid() has failed
test/miner_tests.cpp(226): error: in "miner_tests/CreateNewBlock_validity": check ProcessNewBlock(state, chainparams, __null, pblock, true, __null, false) has failed
test/miner_tests.cpp(227): error: in "miner_tests/CreateNewBlock_validity": check state.IsValid() has failed
test/miner_tests.cpp(226): error: in "miner_tests/CreateNewBlock_validity": check ProcessNewBlock(state, chainparams, __null, pblock, true, __null, false) has failed
test/miner_tests.cpp(227): error: in "miner_tests/CreateNewBlock_validity": check state.IsValid() has failed
test/miner_tests.cpp(226): error: in "miner_tests/CreateNewBlock_validity": check ProcessNewBlock(state, chainparams, __null, pblock, true, __null, false) has failed
test/miner_tests.cpp(227): error: in "miner_tests/CreateNewBlock_validity": check state.IsValid() has failed
test/miner_tests.cpp(226): error: in "miner_tests/CreateNewBlock_validity": check ProcessNewBlock(state, chainparams, __null, pblock, true, __null, false) has failed
test/miner_tests.cpp(227): error: in "miner_tests/CreateNewBlock_validity": check state.IsValid() has failed
test/miner_tests.cpp(226): error: in "miner_tests/CreateNewBlock_validity": check ProcessNewBlock(state, chainparams, __null, pblock, true, __null, false) has failed
test/miner_tests.cpp(227): error: in "miner_tests/CreateNewBlock_validity": check state.IsValid() has failed
test/miner_tests.cpp(226): error: in "miner_tests/CreateNewBlock_validity": check ProcessNewBlock(state, chainparams, __null, pblock, true, __null, false) has failed
test/miner_tests.cpp(227): error: in "miner_tests/CreateNewBlock_validity": check state.IsValid() has failed
test/miner_tests.cpp(226): error: in "miner_tests/CreateNewBlock_validity": check ProcessNewBlock(state, chainparams, __null, pblock, true, __null, false) has failed
test/miner_tests.cpp(227): error: in "miner_tests/CreateNewBlock_validity": check state.IsValid() has failed
test/miner_tests.cpp(226): error: in "miner_tests/CreateNewBlock_validity": check ProcessNewBlock(state, chainparams, __null, pblock, true, __null, false) has failed
test/miner_tests.cpp(227): error: in "miner_tests/CreateNewBlock_validity": check state.IsValid() has failed
test/miner_tests.cpp(226): error: in "miner_tests/CreateNewBlock_validity": check ProcessNewBlock(state, chainparams, __null, pblock, true, __null, false) has failed
test/miner_tests.cpp(227): error: in "miner_tests/CreateNewBlock_validity": check state.IsValid() has failed
test/miner_tests.cpp(226): error: in "miner_tests/CreateNewBlock_validity": check ProcessNewBlock(state, chainparams, __null, pblock, true, __null, false) has failed
test/miner_tests.cpp(227): error: in "miner_tests/CreateNewBlock_validity": check state.IsValid() has failed
test/miner_tests.cpp(226): error: in "miner_tests/CreateNewBlock_validity": check ProcessNewBlock(state, chainparams, __null, pblock, true, __null, false) has failed
test/miner_tests.cpp(227): error: in "miner_tests/CreateNewBlock_validity": check state.IsValid() has failed
unknown location(0): fatal error: in "miner_tests/CreateNewBlock_validity": std::runtime_error: CreateNewBlock: TestBlockValidity failed: bad-txns-inputs-missingorspent (code 16)
test/miner_tests.cpp(272): last checkpoint
test/pow_tests.cpp(29): error: in "pow_tests/get_next_work": check CalculateNextWorkRequired(&pindexLast, nLastRetargetTime, params) == 0x1c093f8d has failed [470819297 != 470368141]
test/pow_tests.cpp(57): error: in "pow_tests/get_next_work_lower_limit_actual": check CalculateNextWorkRequired(&pindexLast, nLastRetargetTime, params) == 0x1b01d73c has failed [453708649 != 453105468]
test/pow_tests.cpp(71): error: in "pow_tests/get_next_work_upper_limit_actual": check CalculateNextWorkRequired(&pindexLast, nLastRetargetTime, params) == 0x1b054c60 has failed [453115044 != 453332064]
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
Error: Error: A fatal internal error occurred, see debug.log for details
test_monacoin: /home/ubuntu/build/monacoin/depends/x86_64-linux-gnu/share/../include/boost/thread/pthread/recursive_mutex.hpp:104: boost::recursive_mutex::~recursive_mutex(): Assertion `!pthread_mutex_destroy(&m)' failed.
Segmentation fault (core dumped)

Assertion failed! file: wallet/crypter.cpp, line 198 ?

How to fix?
even typing the right password, either to change the password or send monacoin. The message appears.

And I already resented the monacoin core and I used 2 different backups. And nothing worked.

file: wallet/crypter.cpp, line 198

No DNS Seeds on Testnet

There is currently no online nodes when you start the client on testnet. It's also quite hard to find an IP list online that has nodes that are alive.

Is it possible to update this with a couple of long active nodes in the near future?

Increase default minconf

Monacoin Core - wallet/crypter.cpp, line 198 Wrong Passphrase Passaword

OS Windows 10 64bit
Monacoin core
v0.14.2.0-6d65019 (64-bit)

Hi
I have some problem with my wallet
passphrase is 100% correct
I can see the balance, but when I enter the right passphrase to send the currency or change passphrase.
This message appears

Assertion failed!
file: wallet/crypter.cpp, line 198

the program opens and synchronizer without problems
I tested the backup on another computer and it presented same problem.

maxfeerateの導入について

関連 bitcoin/bitcoin#13541
bitcoin0.19.0より導入するようで、monacoinについては現状litecoinを追っている関係上
おそらく次の次のバージョンで導入予定かと予想しています。

現在monad(golang版monacoinフルノード)のコードを保守しているとその関係のコードが出てきます。
monasuite/monad@fc6fe2b

導入しないならこのコードについては次バージョンでコメントアウトしてしまおうかと考えています。
一応確認と言うことで次の次のバージョンのLitecoinの対応次第ということでよろしいでしょうか？

Revert "volatile-checkpoint" and "alert".

I suppose recent hashrates of Monacoin mainnet is enough powerful to avoid selfish mining attack.
It's a time to revert "volatile-checkpoint" and "alert" functions, IMO.

Mac OSX make error

Describe the issue

following the osX build notes results in errors.

Can you reliably reproduce the issue?

If so, please list the steps to reproduce below:

after installing brew dependencies

run ./autogen.sh
run ./confugure
run make

Expected behaviour

make to complete successfully

Actual behaviour

error

Screenshots.

What version of litecoin-core are you using?

0.14

Machine specs:

OS: 10.12.6

Any extra information that might be useful in the debugging process.

error output from make
https://pastebin.com/NVTNudtf

有効なコマンドでHelpに記述されていないものが数個あります

walletlock, walletpassphrase, walletpassphrasechange
reconsiderblock
setmocktime

これらのhelpへの記述がありませんでした