f4
Nomad
f4e8a832885dfec3c114cd69a75c413d968a319cc52164666d13e5b42886faa8
FOSS Maximalist Running Knots Bitcoin is peer-to-peer money! PRO BIP444
Replying to Avatar waxwing

I was recently trying to remember something about lightning: how "LN penalty", the current mechanism, makes multiparty channels not work. This is what I came up with:

Suppose A B C are in a multiparty channel and each hold commitment transactions of the normal form: output 1: to remote X, output 2: (to local Y after time delay, to revoc. secret Y immediately). The obvious problem is, "to revocation secret" - *whose* revocation secret? Obviously "Alice gives revocation secret to Bob and Charlie" makes no sense; then they're competing over the punishment funds.

A little thought and you might come up with "split it equally". So the idea there would be, instead of "to me after delay OR to to them with revocation secret", change it to "to me after delay OR to a multisig script for A and B and C with revoc. secret" and, to revoke old state, as well as sending revoc. secret, sign a payout, from that script, to B and C with a 50/50 split. Setting aside a counterparty going offline, this is still terrible: imagine Alice tries to revert from having 0% of balance to having 100%, then the punishment gives 50% to B and 50% to C. But if Bob was colluding with Alice, Alice now has e.g. 25% (half of Bob's share of the punishment). I'm deliberately glossing over how the B and C balances were at the time of the contract breach, because even this is enough to see that it plainly doesn't work to just say "split the punishment between the honest parties".

This is why both covenants and sighash_noinput ideas are powerful: they can push state forwards, i.e. "enforce a contract" rather than "take corrective action when a contract is broken".

The latter requires *justice*, which is to say, it requires apportioning blame (if A breached, A is clearly to blame, but that doesn't mean B and C aren't!). The former does not; at least, if the contract is well written.

I'm not a technical person. But I recently came across the Nucleus propasal. It seems like an amazing improvement.. Any chance we could see some multiparty channel implementation in the near future?

It's damn frustrating to see this kind of spam attack. Onchain is unusable.. I'm glad we have Mutiny Wallet with built-in eCash support.

After seeing your video, I tried Primal out. It's nice, but I hate their KYC.. Even WoS didn't require this much personal info.. I prefer connecting Mutiny Wallet to Primal..

You made a great video though ๐Ÿ‘

I thought Mutiny was also available on F-Droid? Couldn't find it yesterday..

Replying to Avatar Keith Mukai

Okay, holy shit I've been doing life wrong all this time.

Results were AMAZING!! Best steak I've ever cooked. By far.

Props to nostr:npub1t42gfjzfv74v8xrv65f2lrwd65jr85ysrtdmkkfrvqgcss5r4g0qk487qz and nostr:npub1xapjgsushef5wwn78vac6pxuaqlke9g5hqdfjlanky3uquh0nauqx0cnde for scolding me / coaching me to do better.

The better quality (thicker, fresher) steak plus the reverse-sear technique made for a killer upgrade combo (duh! But still... wow).

I had been buying prepackaged 1" steaks and freezing them. This time it was a ~1.5" thick ribeye directly from the meat counter (but tradeoff: those aren't grass fed).

Previous attempts were all on just cast iron or backyard grill. First time reverse-searing. 200ยฐ to an internal temp target of 120ยฐ.

Had not incorporated finishing with butter much before, first time using thyme. Garlic in there, too.

My steaks had been fairly dry (even when not overcooked), unpleasantly tough, and mostly weirdly flavorless. This one was incredibly juicy, tender, so much flavor!

The difference was like spending $6 at Denny's vs $80 at a steakhouse. NO JOKE.

I have one prepackaged 1" steak left in the freezer; will try reverse-searing it and see how much the cooking technique alone can improve upon my prior results. I expect disappointment, but worth running the experiment!

nostr:nevent1qqs8pljvzlh8x8p8cus9tg6sng8f9vsxelcqxymuzmuuk65qexe3sqczypdsardxlha6vccrs6gtxlfpdkp5tf3rese7zyd06rmn3mthj279gqcyqqqqqqgwlfglg

Proof of steak ๐Ÿ˜‚

For the people wishing to see on Nostr the features #GrapheneOS Vanadium browser has:

- Type-based Control Flow Integrity enabled

- Hardware memory tagging (MTE) enabled for the main allocator

- Strict site isolation and sandboxed iframes

- JavaScript JIT disabled by default with per-site override option

- Native Android autofill implementation to avoid needing sandboxed Google Play for autofill support

- WebGPU disabled for attack surface reduction

- WebRTC IP handling policy toggle to control peer-to-peer WebRTC mode

- Compiler hardening: automatic variable initialization, strong stack protector, well defined signed overflow

- High performance content filtering engine using EasyList + EasyPrivacy with a per-site override option

- More complete state partitioning without origin trial opt-out

- High entropy client hints replaced with the frozen user agent values to avoid leaking device/OS info

- Battery API always shows the battery as charging and at 100% capacity

- Trivial subdomain hiding disabled

- Consistent browser behavior across users without usage of feature flags and seed-based trials

- Nearly all remote services disabled by default or removed. Only connects to GrapheneOS servers by default. There are only 2 default services: component updates such as certificate authority and certificate revocation updates and DNS-over-HTTPS connectivity checks when enabled

- Web search and global search intents to replace the need for an OS search app

- Option to always open links from other apps, custom tabs and search intents in Incognito mode

Better default settings, including non-user-facing flags:

- Reduce Accept-Language header by default (only available via chrome://flags)

- Third party cookies disabled by default

- Payment support disabled by default

- Website background sync disabled by default

- Sensors access disabled by default

- Protected media (DRM) disabled by default

- Hyperlink auditing disabled by default

- Do Not Track enabled by default mainly to avoid users differentiating themselves from others by enabling it since it has no real value

- WebRTC IP handling policy set to the most private value by default instead of the least private value (turned into a user-facing option by Vanadium)

nostr:nevent1qqstu7eafcpguaqfplrvh88vu5ked4ke6kcxh7svrllastrdh9vgnnspz3mhxue69uhkummnw3ezummcw3ezuer9wcpzps26tfjesmn6ksf5mm36hpf9fkjut49sfeutfutvs2phrykn25v9qvzqqqqqqyyjcwrn

I didn't know Vanadium was so great. Thanks for the efforts ๐Ÿ‘

Coinbase is just like BitPay.. Evil.