There are some potential feefilter cleanups mentioned and motivated in comment bitcoin/bitcoin#21509 (comment) . If you address the locking one, please be careful and make sure that round() is only called under a lock. See bitcoin/bitcoin#21509 (comment)

Useful skills:

• Bitcoin protocol messages
• Bitcoin Core

Just for RSA. Do encrypt and decrypt. Include a bold comment that this should not be used for bulk encryption.

It should be the current best practice (fetch), have proper error handling and resource allocation/deallocation and be in the style of a known answer test.

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

Background

The links to http. proto and annotations. proto no longer exist
Lower versions of GRPC may no longer work with existing code
I cannot access the public IP according to the documentation
Then I upgraded the GRPC to 1.36.0, the os-maven-plugin to 1.6.2, and the protobuf-maven-plugin to 0.6.1, everything was fine

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.

Summary

P2P module should not backoff+retry for connections to peers where there is a chain mismatch, but should expunge the address from the address book and remove it from the list of peers.

Problem Definition

Presently (v0.33; not sure if this is addresses in 0.34), if we connect to a peer on an incorrect chain, the node repeatedly reconnects to this node, and then drops the conn

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.

Summary

Include recently added validation fields in validations subscription stream messages:

• version
• cookie
• validated hash

Motivation

This information is useful for server operators, for developing who are putting together dashboards, and the community at large.

ripple/rippled#3291 (comment)

Solution

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.