Hi,
Excellent boilerplate! How about adding support for sockets in this to make a more complete boilerplate?
Also instructions on deployment using Docker/native would be very helpful.
Thanks.

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

We currently use the following three steps to point a user to org settings:

{{ site.data.reusables.profile.access_profile }}

• file path = data/resuables/profile
{{ site.data.reusables.profile.access_org }}
• file path = data/resuables/profile
{{ site.data.reusables.organizations.org_settings }}
• file path = data/resuables/org_settings

However, there is a sli

Summary

Allow removing search input for filtering options

It is currently expected that UIs will figure out when to hide msg_history_show messages by themselves.

I think this is bad for two reasons:

• It makes UIs less similar, increasing the number of things to learn when going from one UI to another.
• It makes UIs different from the TUI, which offers a press ENTER prompt when the time to hide msg_history_show messages has come.

After [di