I spent too long to figure out I was putting mainnet addresses to regtest node, errors weren't helpful at getaddressinfo and validateaddress.

Seems like a good first issue to augment the error messages when prefix/hrp don't match current network.

Currently the SSL_CTX_new() man page has the following info on what a context is:

DESCRIPTION

SSL_CTX_new() creates a new SSL_CTX object as framework to establish TLS/SSL or DTLS enabled connections. An SSL_CTX object is reference counted. Creating an SSL_CTX object for the first time increments the reference count. Freeing

doctest help

Hello spoooopyyy hackers 🎃

This is a Hacktoberfest only issue! 👻

This is also data-sciency!

The Problem

Our English dictionary contains words that aren't English, and does not contain common English words.

Examples of non-common words in the dictionary:

"hlithskjalf",
  "hlorrithi",
  "hlqn",
  "hm",
  "hny",
  "ho",
  "hoactzin",
  "hoactzine

Currently stratumserver has no unit tests. This will improve the quality and allow future commits to be TDD safe. All units will be tested to ensure the module as a unit itself is tested.

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

Problem:

A common pattern is:

GUARD(s2n_stuffer_skip_write(stuffer, bytes_to_write));
uint8_t* ptr = suffer->blob.data + stuffer->write_cursor - bytes_to_write;

which could be simplified.

Solution:

*ptr could be an *out parameter to s2n_stuffer_skip_write

• Does this change what S2N sends over the wire? No.
• Does this change any public APIs? No.

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.

Now that we've dropped 2.7 and are 3.6+ only we can do inline type hinting. Let's do it!

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

https://scotthelme.co.uk/a-new-security-header-feature-policy/

I guess it will be easy to add, because we certainly don't use any of these features.
Or maybe "gyroscope" or so may be used by the random number generator in sjcl, but that's all.