Avatar
Dikaios1517
b7274d28e3e983bf720db4b4a12a31f5c7ef262320d05c25ec90489ac99628cb
│Christian│Husband│Father│Presbyterian│Bitcoiner│ In that order. Find my reviews at nostr:npub1rsv7kx5avkmq74p85v878e9d5g3w626343xhyg76z5ctfc30kz7q9u4dke Bolt12: lno1pgz95ctswvtzzq3kw0eghxwlgwrsq84tp28uqc8cewk83vhendsnz3jdum7hut3y75

That's more of a protection against in-transit manipulation of the device.

The evil maid attack is just referring to anyone who has trusted access to your home or wherever you store your device, and who would therefore have opportunity to maliciously flash firmware that could leak your private key, such as the dark skippy attack. It could also be done by someone breaking into your home and gaining physical access to your device, but it's still called the evil maid attack regardless.

With a ColdCard, the indicator light turning red on boot-up is a dead giveaway that firmware that hasn't been signed by the manufacturer is currently running. There is no such safeguard on a SeedSigner.

So, yes. Verifying the signature on firmware you download and install yourself is a great protection when you can be absolutely certain that the firmware running is what you personally installed. But if that device is ever out of your sight, how can you be certain that the firmware is still what you installed?

Yeah, the block-size war really proved who is in charge of what "upgrades" get implemented on Bitcoin; namely the folks who run full-nodes and actually use them for transacting.

It is a story of how the plebs who run the nodes successfully defended the network from having a block-size increase forced on them by the big miners and exchanges. An increase that would have had a centralizing effect, since it would have meant running a node would require beefier and more expensive hardware that maybe the average pleb could no longer afford.

Replying to Avatar Constantin

My dive into understanding Bitcoin got an interesting boost with nostr:npub1h8nk2346qezka5cpm8jjh3yl5j88pf4ly2ptu7s6uu55wcfqy0wq36rpev's podcast, Bitcoin Audible.

If you're a beginner, and a little paranoid, here's a good episode to extinguish some of those fears. I have a long journey ahead but I wanted to mark his first episode that I interacted with in the forever memory of Nostr.

Here's the link from nostr:npub1v5ufyh4lkeslgxxcclg8f0hzazhaw7rsrhvfquxzm2fk64c72hps45n0v5

https://fountain.fm/episode/FZHLYW6kdFGVnI3dqOaN

This and the block-size war proved just how incredibly resilient Bitcoin is to attacks from both without and within.

They really have! Nostr Wallet Connect is an incredible tool for the entire Lightning ecosystem, whether you use any of Alby's other services or not. Then they come out with Alby Hub, which is an incredibly versatile tool for self-custody lightning, whether you have your own node hardware or not. And now a native mobile wallet that connects WAY faster than most LNDHub wallets, because it leverages NWC.

Excited to see what they come up with next!

Welcome to the party!

Set up a lightning address so we can zap you!

Some risk? Sir, you have approaching 15 Bitcoin in total capacity. Even assuming only ~1/2 of that is on your side of any given channel, that is far more money in a hot wallet than most plebs even own, let alone would be willing to have in a hot wallet.

So it's not just time and effort and decent hardware that is needed to run a profitable routing node. It's also a decent amount of capital outside of cold storage.

Wen NIP-46 and/or NIP-55 login support so we can use our regular npub without giving the app our nsec or being forced to use a random nsec/npub?

noStrudel is probably the most full featured of all the web apps, but yeah, some of the UI elements are annoying.

Coracle is probably my favorite for how it looks and how much control I have over my feed, but I miss being able to have a variety of reactions.

Another one to try out is satellite.earth

Nostr devs: Please remember that we want to protect our nsec, and requiring us to enter it into your client will result in many of us simply not using your app at all. There are multiple ways to allow for login and signing of events without requiring an nsec. Please support at least one of them when you release your client and want people to start trying it out. Ideally, support more than one.

NIP-07 for web app login using a browser extension.

NIP-46 for remote signing over relays, which is OS agnostic.

NIP-55 for native Android apps.

Right. While using nos2x as your signer, correct?

The above allow you to use Amber on your phone as your signer for a couple web apps on desktop.

It may also have to do with what wallet you are using for zapping, rather than anything to do with signer permissions.

The amount of transactions in blocks is still plenty high. Blocks are full, just of low fee rate transactions. This just means there there aren't a lot of folks trying to get their transactions prioritized. My mempool still shows 74 block's worth of transactions waiting to clear, and mempool.space shows 97 blocks worth.

So, the amount of activity actually hitting the chain is the same, because mempools still haven't cleared. We're not seeing any partially full blocks at all. It's just that most of the transactions waiting in the mempools are in no rush to make it into a block.

Values based largely on the summarization of the moral law of God in the 10 commandments, which both Jews and Christians share, last I checked, further summarized in the two greatest commandments: You shall love the Lord your God with all your heart and with all your soul and with all your might, (Deuteronomy 6:5, summarizing commandments 1-4) and you shall love your neighbor as yourself (Leviticus 19:18, summarizing the last 6).

So, while the two faiths may not be theologically compatible, they are largely compatible when it comes to ethics/values.

Controversial take of the night: We all knew that spam was going to be a major issue to resolve eventually. We hoped we wouldn't see massive levels of spam for some time, and we could deal with it then.

Yet, some things just never get attention until the problem is painful. There's always more exciting things to work on in the moment. New features to implement, new interoperability opportunities, and new ideas for "other stuff" clients to build. No one will find the time to deal with the things we KNOW need to be dealt with in the midst of that. Not unless they are pushed to it by pain.

As the saying goes, "Necessity is the mother of invention."