connect_nodes(self.nodes[a], b) is confusing because

• the types of the arguments differ
• the test framework is aware of all nodes, so solving a to self.nodes[a] can be done hidden from the caller

This should be fixed by replacing connect_nodes(self.nodes[a], b) with self.connect_nodes(a, b) and removing the global connect_nodes.

I am using openSSL 1.1.1g.

In order to be compatible with Web Crypto API (and its wrapper openCrypto) regarding encryption RSA keys, The pKCS8 (and PBKDF2) is needed. The documentation is lacking info on PKCS5_pbe2_set_iv. Is it possible to create it? Thanks.

• Adding hints and doctest to old codes
• Reviewing Pending PRs
• Helping new Contributors
• Add more algorithms #14 #195

thank you

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:

URLs are encoded like so:

" " == "%20"

There are many more encodings other than space, this is just one example.

Resources

https://www.w3schools.com/tags/ref_urlencode.ASP
https://www.urlencoder.org/

URL Decoding in Python

https://stackoverflow.com/questions/16566069/url-decode-utf-8-in-python
https://www.urldecoder.io/python/

Guide on how to add thi

Problem:

As mentioned in the comment New cipher suites MUST be added here, IN ORDER, or they will not be properly initialized.

https://github.com/awslabs/s2n/blob/64297d8ce45a38394094f1c31b2ecf5735472edb/tls/s2n_cipher_suites.c#L768-L772

Solution:

Unit test to validate the array order.

• **Does

The blockchain v2 reactor utilizes concurrency to saturate the bottleneck of writing blocks to disk. This concurrency is internal to the reactor where the reactor itself will launch and manage internal state machines running as go-routines. This configuration makes testing difficult as we don't know when messages processed by internal state machines will be processed and when we can assert that th

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.