Is it legal to take a lunch break in the middle of a git rebase? 🤓 #dev #devstr #lolstr

I've heard Silent Payments are great for privacy to avoid address reuse and hide your UTXOs from strangers.
How do I create a silent-payment receive-address in my Binance wallet?
#Bitcoin #dev #devstr #asknostr #silentpayment #silentpayments #binance

Vibe-coded features on #BitcoinFlow :
- See relative & absolute Locktimes
- See absolute fees
- Links to multiple block explorers
- Upload and see PSBTs!

If you are signing complicated chains of PSBTs, you can verify that every input is indeed connected to the intended output (an existing UTXO or another PSBT).

Next step would be create PSBTs visually! Including chains of PSBTs!

#Bitcoin #dev #devstr

https://bitcoinflow.niot.space

Weird Discovery:
I was working on my https://bitcoinflow.niot.space explorer and wanted to add an example for a Coinbase transaction.
I found this recent article about the lucky solo-miner of block 943411: https://bitcoinfoundation.org/news/bitcoin/solo-miner-one-block
It had a link to a previous lucky solo-miner, a week earlier, of block 938092, which I also loaded to the explorer.

Then I noticed that their second output goes to the same transaction! Which has another "solo-miner" input from less than a week later.
Look at inputs 1-3 of the following tx: https://mempool.space/tx/bd0c2d021bc9408948569fb8b02340a1adc4db7f196fcde3f2b694286085f2f6
They all come from a "solo-miner".
The odds that the same solo-miner found 3 blocks within 2 weeks are astronomically low, right?
So it's either not really a solo-miner, or different solo-miners that for some reason decided to give some of their profit to the same entity.
Or I'm missing something?
#asknostr #Bitcoin #dev #devstr

Wow, #lightning 2nd layer is delicious.
#foodstr

Holesail-Switchboard lets you open P2P #lightning channels on #Umbrel without a public IP address and without relying on unreliable Tor. Follow these steps:
1. On both Umbrel nodes, install: one of Bitcoin node apps (tested with Core), one of the Lightning apps (tested with LND) and the Holesail-Switchboard app: https://apps.umbrel.com/app/holesail-switchboard
2. On the channel-destination node, open Holesail-Switchboard and click Add Server with Host: "lightning_lnd_1" and Port: "9735". Do not enable the Secure checkbox (This option is designed for hiding both ends of the connection using a symmetric key. In this case, you want a public key so others can reach your node). This will generate an "hs://0000..." connection URL that others can use to connect to you.
3. On the same node, open the Lightning app, click the 3 dots in the top-right corner, and select Node ID. Under the Tor network section, you will see: "<lightning-public-key>@<address>.onion:9735". We do not need the ".onion" address, but we do need the "lightning-public-key" part, which identifies your Lightning node.
4. On the channel-source node, open Holesail-Switchboard and click the ✏️ icon on one of the clients. Paste the "hs://..." connection URL and note the assigned local port (for example: "3161").
5. Finally, in the Lightning app, open a channel using: "<lightning-public-key>@10.21.0.20:<local-port>". Example: "[email protected]:3161" (the 10.21.0.20 ip belongs to the Holesail-Switchboard app - I've tried different local hostnames but it didn't work for me).

That's it! You now have a lightning channel that uses #holepunch technology, doesn't rely on a static public ip address, and much more stable than #TOR.

@Umbrel ☂️ #dev #devstr