It is possible to compile Bitcoin Core without the wallet. Though, many tests require the Bitcoin Core wallet to create and sign transactions. Ideally, every non-wallet test (for example consensus tests) are run even with the Bitcoin Core wallet disabled. This ensures that users running without the wallet can test their Bitcoin Core with the functional test suite.

Thus, tests that use the Bitco

Right now the docs correspond to what's on master. We need docs for each daemon release so developers can see what's available in the version they are using.

https://github.com/jimporter/mike may be helpful.

Background

When a node has multiple private channels with the same peer, the hop hints in their payment requests will be populated with multiple channels. The purpose of these hop hints is to specify the next node's key and indicate the fees and cltv delta needed for route construction.

In pathfinding, due to non-strict forwarding, an LND node paying to this destination will only use the

Describe your environment

(if applicable)

Operating system: UBUNTU 18.04
Python Version: 3.6.9 (python -V)
CCXT version: ccxt==1.33.72 (pip freeze | grep ccxt)
Freqtrade Version: develop-10c5b230 (freqtrade -

In step 1 of a trade, both the maker and the taker have to choose how they pay for the trade fee: in BTC or BSQ.

Most people don't know what BSQ is or where they can get it, especially new users. They probably assume that, since they don't already have any BSQ, they can't choose that option.

Therefore, Bisq should add a link to the BSQ market next to the BTC/BSQ fee selector, like this:

<

Just playing around with my miner tonight, I set burn_fee_cap = -2 and the miner stopped with a thread panic.

Process abort due to thread panic
   0: backtrace::backtrace::libunwind::trace
             at .cargo/registry/src/github.com-1285ae84e5963aae/backtrace-0.3.50/src/backtrace/libunwind.rs:95
      backtrace::backtrace::trace_unsynchronized
             at .cargo/registry/src/git