If we config the cache options in the config file, then it will be overwritten.

In this error message:

Error: There was a timeout while attempting to connect to the network.
       Check to see that your provider is valid.
       If you have a slow internet connection, try configuring a longer timeout in your Truffle config. Use the networks[networ

We already have a specialized checked exponentiation when the base is a literal and exponent can only be known at compile time.

Implement the case where exponent is a literal and base is only known at compile time. Vyper already has this: vyperlang/vyper#2072

Setup

Versions

• Rust: 1.48.0
• **D

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

A parametrized option to set the blocksize would be useful to experiment with. As quorum is used in a private setting I think this option should be available

Triggered by tendermint/tendermint#5805

We should modify our logger to format byte slices as base 16 (upper case) automatically, which will remove the need for fmt.Sprintf("%X", hash) calls.

Clients that support multiple server connections would like to have a way to decide which server connection is best able to handle a query. Servers currently "sort of" expose their load as fees, but there's no real exposure of server load in a useful way. Some parameter should be added to the "server" publication stream that clients can just compare across servers to decide which is most likely to