pull down to refresh

On LND you already can get some of this with HTLC Interceptors and Channel Acceptors.
On Chromium 153 I am now getting only around 15.6 - 15.9 Mkeys/s with build v100.
Edit: Nevermind. I stopped and restarted and I briefly reached 16.4 Mkeys/s. But then hovering around 16.0 Mkeys/s
Is your mempool explorer publicly accessible? Maybe someone used the "Broadcast Transaction" (https://mempool.space/tx/push) feature?
a custodian
https://mempool.space/tx/a6d697a25266ce3c78774fd1d75f896b7af522ada209b0f6228ea497bc49a46d
Looks like 3400 Bitcoin have been returned.
4k BTC is almost the entire liquidity in Liquid according to https://liquid.network
I've seen something similar a few years ago:
https://github.com/standardsats/plugin-fiat-channels
I thought Bitcoin-Blake2B already has one way replay protection. Why not use that instead?
Unified sighash:
A new opt-in SIGHASH_UNIFIED format works across legacy, SegWit and Taproot inputs.
It provides linear signature hashing, commits to every input amount and gives one-way replay protection.
Source: #1558342
Read the release notes:
From block 961,640 until the parent block’s median-time-past reaches 1 September 2027, blocks are limited to 800,000 weight units, approximately 300 kB
The block was found in July and this is not bad news.
Even if you supply your own entropy to the hardware wallet, you still have to trust it to actually use your entropy.
Best way to know that your seed is truly random is to print out the word list, cut the words out and then randomly pick 11 words. The twelth word needs to be chosen with the help of the hardware wallet, since it contains a checksum.
Awesome, very convenient to have that.
I also built a very primitive BCUR QR code reader a few years ago:
https://filiprogrammer.github.io/bcur_qr_reader/
Is the balance still onchain by default and they swap for Lightning?
Yes. Not a real Lightning wallet. The wallet backup is also non-standard.
Block withholding attacks can be prevented by simply not using FPPS.