every comment within 24 hours

gets 2121 sats

NO double comments allowed

feel free to share

no better way to start your day than raw eggs and OJ

Would actually really love to know more about this and the approach you are taking and what you are learning about it. What precautions are you taking for instance to create a sparrow wallet so it is fully anonymous?

Good morning… that TikTok vid I made about #Nostr is popping off, but riddle me this: why do people keep jumping in my comments claiming Nostr was made by the CIA? 🤨 it just doesn’t seem controllable enough for those folks.

Well instagram keeps deleting my profiles for whatever reason…. So here I am! Check me out for all things mushrooms

No, multisig can be done on Ledger as well. But it sketched me out when Ledger put out their firmware upgrade allowing you to opt in to a custodial seed phrase recovery service, meaning technically they could theoretically extract your seed phrase from the device. Then I listened to a podcast with NVK, one of the founders of Coinkite (you can follow him on here), learned more about the trust associated with hardware wallets, and decided I wanted the most hardcore thing possible to protect my keys. I’ll still be using the Ledger as an intermediary wallet, just don’t want to keep all my savings on there. The podcast I listened to was on Natalie Brunell’s Coin Stories podcast btw.

I don't know much about multisig yet. Is that why you'd be moving from ledger? For the multisig capacity?

Do however Feeling a little sad and heart broken tonight 💔 but I am gonna scroll down my #nostr wall?! and look for that one thread where ya'll shared suggestions with me some weeks ago on the best self custody wallets to use, so I can get some set up and keep going with my learning journey.

If you do however feel like sharing here again: What wallet do you recommend for "get your BTC off the exchanges" move? Please do share...

Btw, here's a photo I took on my walk this eve in Petaluma... Comments and meme making welcome...

Hi friend! Beautiful place for a walk 🙂 thanks for sharing! Have some sats ⚡️

#nostr

Would you it them ?

nostr:note1xump4653e9cl7hy39pf8lh9egymkw85f924pl758c3rlq7lyer2sep0wrf

Interesting

Step 1. Ban L1 scaling.

Bitcoin: Core developers refused to scale L1, dropped all proposals to increase the block size, censored all those who opposed

Ethereum: Foundation refused to scale L1, dropped all proposals to increase the gas limit (remember EGL?), dropped sharding from the roadmap, invented the phoney "blockchain trilemma"

Step 2. Introduce scaling "solutions".

Bitcoin: introduced custodial centralized L2s financed by banksters (Lightning, Liquid, etc.)

Ethereum: introduced custodial centralized L2s financed by banksters (all rollups have admin keys despite pretending to be DAOs)

Step 3. Make L1 even more expensive.

Bitcoin: introduced special fee discount for using L2s (SegWit discount, Tapscript) so it becomes even more expensive to use L1 compared to L2

Ethereum: introduced special fee discount for using L2s (the newest hard fork)

Both call it "scaling". The truth is it's not scaling: it's just an attempt (a successful one so far) to lock people into custodial L2 products.

Youngest son helped my wife make a batch of lemon/garlic/dill sauerkraut with the first round of cabbage from our garden.

When I came home he was so excited to show me this crock that he helped tamp down.. Warms the heart

#foodstr #homesteading #grownostr #parenting

#GrapheneOS: We're continuing work on integrating ARMv9 security features. MTE is the highest impact and most interesting of these features, but there's less important work to do expanding usage of PAC and BTI. Android uses Clang's type-based CFI but not everywhere so BTI is still useful.

Pixel 8 was the first device with a usable MTE implementation despite it launching as part of ARMv8.5. Android world stayed on ARMv8.2 until ARMv9 and Apple hasn't shipped MTE. Apple was a much earlier adopter of the much less useful PAC. From our perspective, PAC was a misstep.

PAC is a weak probabilistic mitigation requiring lots of case-by-case integration. MTE can provide many deterministic guarantees and does a much better job as a probabilistic mitigation by catching memory corruption rather than only protecting specific memory corruption targets.

PAC requires bits which would have been better served by 16-bit MTE support and using a 48-bit address space. Hardware shadow stack is a better backwards edge CFI approach. MTE could be used to mimic hardware shadow stack support via a reserved tag for ShadowCallStack.

We're currently the first platform using userspace heap MTE for hardening in production. We plan to do the same with userspace stack MTE along with doing both in the kernel. Turning ShadowCallStack in the kernel into a hardware protected shadow stack would also be nice to ship.

In the kernel, Pixel OS uses PAC for backwards edge CFI and Clang type-based CFI for forward-edge. We use ShadowCallStack + PAC together and enable BTI in addition to type-based CFI due to lots of functions being excluded from type-based CFI. We plan to do the same in userspace.