opentimestamps-client VS electrs

OpenTimeStamp-client v0.7.1 (Released: 26th August 2022) - https://github.com/opentimestamps/opentimestamps-client/releases

if you sign your commits, you should also consider timestamping your commits. I use OpenTimestamps for this. Docs and some rationale here: https://github.com/opentimestamps/opentimestamps-client/blob...

from the doc:

> My signing keys (e.g. blog or Qubes code signing keys) do not have expiration dates. This is not laziness. There is a fundamental problem with using an expiration date on keys used for code signing (e.g. git tag -s), because it is unclear what the outcome should be when one verifies some old code (written and signed when the key was still valid) in the future when the key has already expired?

> Naturally we would like the old code, written and signed when the key was still valid, to continue to verify fine also in the future, after the key expires (and the developer passed away, perhaps). However, it is very problematic to prevent the attacker from creating falsified code pretending to be an old one.

There seems to be a Rust implementation of the server (electrs via https://github.com/romanz/electrs ). It was recommended as part of a Medium article on how to set up an Electrum server. So far it seems fine - but, what are your inputs on it?

romanz/electrs. This is a common choice for its low resource requirements, and most full-node distros use it. But while this implementation works great for basic queries, it will struggle with heavier ones (e.g. looking up addresses with many transactions)—especially when running on low-power hardware like a Raspberry Pi.

Electrs v0.9.10 (Released: 3st November 2022) - https://github.com/romanz/electrs/releases

To gain some privacy by using Electrum you should set up Tor on Network preferences or by installing your own Electrum server via Electrum Personal Server, ElectrumX or Electrs.

Electrum can be connected to you full node if you also run this: https://github.com/romanz/electrs

Electrs: https://github.com/romanz/electrs (Instead of electrs you can also use "Electrum personal server" to connect Bitcoin core to Electrum).

LND v0.14.3 - Release page - Upgrade guide This release contains only a series of bug fixes, and doesn't introduce any backwards compatible changes (database migrations, etc) from the prior version. Notable fixes in this release include: a fix to an invoice registry related deadlock, a fix for an edge case when running the remote signer operating mode, and a fix to ensure that 3rd parties sweeping an anchor UTXO doesn't lead to the wallet having a fragmented internal UTXO state, and a fix for a payment state inconsistency (a payment looks like it was stuck though no HTLCs exist).Full release notes.