The Samourai devs were never money transmitters. They wrote code. Now they're going to prison. Developer protections are not optional. They are essential for Bitcoin and for liberty. Writing software is not a crime.

Coin Center

Senate market structure negotiations must not sacrifice hard won developer protections

The House version’s carefully drafted language is sensible and non-partisan

Just received a new router my ISP wants me to use for my network. It's for my safety and faster speeds, they say. I purchased my own router and set it up just the way I like. All traffic runs through a VPN and DNS that protects my family. It seems their hardware would merely downgrade our security while allowing them to snoop on our traffic. No thanks. It'll get thrown on a shelf.

Trump has floated the idea of HSAs and it appears the House Ways and Means is circulating language for a bill to do it. Using HSA's to fund medical costs for the needy is a FAR better option than the current Medicare/Medicaid programs. It allows for competition and less market manipulation in the healthcare industry. However, I have to wonder if part of this is to inject more government funds into the stock market to show "pretend" growth. Currently, with HSAs, you're allowed to invest your funds so they may grow over time. Better than just dollars sitting their eroding in value. I believe roughly 35% of current HSA funds are invested in the market. If we replace the $2 trillion spend in Medicaid and Medicare, and that 35% holds, then that's $700 billion that will end pushing up stock market prices.

I appreciate @Umbrel ☂️ giving users the ability to pick and choose the type of node they want to use. You can use Core and choose v29 or 30. You can run Knots if you choose. This is the way it should be done. Maintainers shouldn't be forcing their customers into one path or another but making it easy for node runners to choose what they they run. I hope @Start9 is also making it this easy to choose.

I finally figured why I kept having so many issues with @ZEUS and @LNbits working together. In a fairly regular basis, Zeus would stop being able to create invoices. I have tried this combo, using the LND Hub, without success several times. It always ends up having connection issues. Recently, I realized that when I was opening the settings in the admin section, my pwd manager was adding the LNBits pwd to the encrypted macaroon field. When I saved the settings of those I was there to change, it would save this too. Removing auto-fill for this URL has stopped this from occurring. Now, no problems. All our wallets connect and create invoices without an issue.