bitcoin

Trying to gain rough technical consensus on covenant proposals

theonevortex

I don't understand why in the table of definitions at the top, the definitions of "deficient" and "wanting" reference "community support".

It seems like you're crossing the beams. I'd expect this evaluation to be based solely on each proposal's technical merits, which in turn would then help drive consensus. Having it contain this recursive metric of community support seems unproductive.

Also, some labels reference community support and others don't, so the scale is internally inconsistent.

Today we've seen two Bitcoin Core releases come out: version 25.2 and version 27.0.

Why is the maintenance version 25.2 needed/desired?

Why would someone upgrade to 25.2 instead of going straight for 27.0?

Music

Bitcoin-themed music is cringe.

I don't mean no disrespect. That's just what listening to it feels like to me personally.

Is the expectation that if we do it long enough it stops being cringe and will be cool at some point?

crypto

Fully Homomorphic Encryption, Practical Examples and Demos

![1000134331.jpg](https://m.stacker.news/24684)

Everybody asks "When is Halving?" Nobody asks "How is Halving?"

Hedgehog: A protocol for asynchronous layer two bitcoin payments

supertestnet

> a value Alice may reveal to Bob if she wants to revoke her ability to safely receive money in an address containing the top script. 

I'm missing something. Can you please explain the above? I don't understand why or when Alice would want to revoke her ability to safely receive money. Folks tend to want to acquire and maintain the ability to safely receive money - the more the better.

mempool

![mempool.png](https://m.stacker.news/22956)

This morning we almost got into the 5-6sat/vB zone... last time was 5 months ago

How to keep your privacy and save on fees when migrating to a new wallet

> tl;dr use an address from the new wallet as the change address for your tx

Sometimes you need to migrate wallets. For example, when moving from single sig to multisig. Or perhaps you had older UTXOs and want to migrate them to SegWit. If that's your case, this might help you. 

1. Wait until you need to make a bitcoin transaction (e.g. you bought something or, God forbid, you sold some BTC), let's say you need to send 1mBTC
2. Instead of sending funds to `bc1destination` and letting the wallet pick a change address, make it a transaction with two outputs yourself, having the second destination be an address from your new wallet
3. To do that, pick your fattest address, e.g. 10mBTC
4. Subtract from it the amount you need to send to the destination, e.g. 10mBTC - 1mBTC = 9mBTC
5. Subtract from it the amount of fees you need to pay, let's say 9mBTC - 0.06mBTC = 8.94mBTC
6. Now your tx should look like this `bc1destination,1.00000    |     bc1newwallet,8.94000`, meaning the remaining coins will be used as fee
7. Sign and broadcast
8. Once confirmed, destination should've received 1mBTC and the new wallet should've received 8.94mBTC

Make sure to properly label your transaction in the new wallet for proper coin control hygiene.

do you even multisig?

Ah, ok. You write down the seed on paper too.

Yeah you're right. I think MPC will solve this. Makes the transaction look like a single sig which is smaller.

do you?

(and "paper wallet" is not a valid answer as you'll need to move funds eventually)

What's the easiest way to get a notification when the mempool frees up?

The problem with that is that you can't delete a tx from the mempool, so if you ever need to move funds elsewhere you'll have to do a CPFP which is even costlier.

I want to make sure not to miss the next consolidation opportunity.

I also don't want to receive too many notifications (noise vs signal).