IRC logs

sanket1729: How can decoderawtransaction RPC know reqSigs if the output scriptpubkey is p2sh/p2wsh? I think it is returning 1 everytime.
sipa: sanket1729: it only works for bare multisig
sipa: we should probably just remove it

The output parameter for reqSigs is confusing as it outputs 1 for all scripts but bare multisig in the scriptpubkey. Considering the limited applicab

The app_get0_propq (from apps/lib/apps.c) is used throughout many openssl apps to define propq used to fetch the algorithms. Currently, it just returns NULL and its comment says "TODO(3.0): Make this an environment variable if required".
If a provider is used that does not implement all algorithms (e.g. reuses STORE from the default one) the propq needs to be defined to fetch the right implemen

Welcome to JavaScript community

Describe your change:

• Add an algorithm?
• Fix a bug or typo in an existing algorithm?
• Documentation change?

Checklist:

• I have read CONTRIBUTING.md.
• This pull request is all my own work -- I have not plagiarized.
• I know that p

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

The current grin client uses the V1 API which is now removed.
Convert it to v2. https://github.com/mimblewimble/grin/blob/v5.0.0-beta.2/src/bin/cmd/client.rs#L159v

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.

We will be supporting v0.33 till the next major release (0.35). We should bump golangci-lint version to the latest version to fix ci failures. In doing so many linting errors will arise, these should be cleaned up in the same PR.

This is an easy first contribution to Tendermint, if you are looking to get your hands dirty :)

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.