cryptography

Similar to how the fee is returned in getblock (#18771), it should be returned in getrawtransaction.

Useful skills:

Understanding of undo data, the RPC interface and the functional tests.

Want to work on this issue?

For guidance on contributing, please read CONTRIBUTING.md before opening your pull request

What about create a design pattern directory with the most popular design patterns examples?
We can create some rules like: have to be an explanation about the design pattern, the structure and one real world example.
The directory can be:

(folder) Design Patterns
-- (folder) Abstract Factory
-- -- AbstractFactory.js
-- -- AbstractFactoryTest.js
-- -- REAME.md

I can send some :

Hey Hackers of this spoopy month! 👻
Welcome to the Ciphey repo(s)!
This issue requires you to add a decoder.

This wiki section walks you through EVERYTHING you need to know, and we've added some more links at the bottom of this issue to detail more about the decoder.
https://github.com/Ciphey/Ciphey/wiki#adding-your-own-crackers--decoders

https://www.dcode.fr/t9-cipher
https://en.wikipe

Background

If my node is asked to forward N sats to peer X via channel C, lnd is free to pick any other channel it might have to peer X. As far as I understand the code (switch.go:handlePacketForward), all channels to X (not just C) are checked for eligability, and a random eligable channel is then used for the actual forward.

As part of this eligability check (implemented in link.go:Che

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.

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.

Issue Description

Per https://blog.ripplex.io/sunsetting-ripplex-io/, the ripplex.io site is being sunset. There are several references to it (and its predecessor xpring.io) in the rippled documentation that need to be updated.

As of 1.8.0-b3:

$ grep -ri -e xpring.io -e ripplex.io
RELEASENOTES.md:This release [significantly improves memory usage](https://blog.ripplex.io/how-ripples

As I was running composer to install a new library into our repo, it warned me that:

Package yzalis/identicon is abandoned, you should avoid using it. No replacement was suggested.

I'm not familiar on what packagist.org's process is to declare a package abandoned. I see that the last commit in their repo is from 2019 and there are a number of unanswered issues and pull requests.

I