Fountain: Podcasts & Music

What Bitcoin Did • The Coldcard Disaster: Everything You Need to Know | Lloyd Fournier & Nick Farrow • Watch on Fountain

“They’re saving all their money in Bitcoin and they’re doing all the right things. They’re self-custodying it. And then overnight, it’s j...

View quoted note →

Please update BTCPay Server to version 2.4.2 If you use LND, consider macarroon files compromised and if you run (which most don't) a hot wallet in store, send funds out. Afaik not an RNG issue but files could be read from disk over endpoint. @BTCPay Server

Fountain: Podcasts & Music

The Peter McCormack Show • #179 - Simon Dixon - The One World Government Is Already Here • Listen on Fountain

Simon Dixon joins me to discuss AI, Bitcoin, algorithms, media capture, central banking, programmable money, geopolitics and how to escape the syst...

View quoted note →

Intrresting that suspicious and controversial figures can't help themselves and go full retard eventually. He even does not mind robbing patoshi coins. This will be a huge nothingburger but for sure he will find some fools financing his and his pals retirement. Stay humble, stack sats. Don't get fooled by self-proclaimed saviours of Bitcoin. View quoted note →

Buying hash from big (and small) hashing farms so it doesn't end up in centralized mining pools but instead build on your own block templates (via DATUM and SV2) sounds like a net positive to me. Running your own mining hardware is better that's for sure but the next best thing is to buy hash that would otherwise end up in centralized mining pools giving them more power. Not as bad as cloud mining as you can point an exact hash rate you bought to a specific pool/mine your preferred block templates. What's the argument why this is bad?

👀 View quoted note →

Imagine being hostile against another well funded implementation ensuring there is no single point of failure and further reducing the attack surface by decentralising development. Unless you have already influence in the current reference implementation and want to make sure your (shitcoin) agenda gets pushed through. Same people that praised LibreRelay and told you nobody can stop them now being hostile against another implementation going the opposite way to not break and rush things and ensure Bitcoin will survive 1000+ years. View quoted note →

An additional Bitcoin client implementation, desperately needed, imho.

ProductionReady Launches

ProductionReady, a new U.S. 501(c)(3) nonprofit, will fund development of a Bitcoin client focused on stability, user sovereignty, and conservative...

Land of the free? Only if you didn't make uncle Donald angry, no congress approval or change of law needed? Even here in EUdssR they at least do some democratic theater and push through laws when countries get sanctioned. View quoted note →

Huge opportunity for Bitcoin / LN, we have everything setup already. It's easy for agents to get an LN wallet working without KYC. You as agent operator (or your agent) should reach out to merchants and ask them to support Bitcoin payments. There are plenty of solutions like @BTCPay Server and other self-custodial and custodial solutions out there that are easy to setup for merchants - without them having to do a masterclass in LN channel management. This is a great trend and opportunity we should use to push for Bitcoin adoption. Let's go! View quoted note →

#openclaw lessons: crash during update, all broken, `openclaw` commands do not work anymore ##What happened: When running `openclaw update` there were some warnings but the usual screen that asks you for restarting the service did not appear, it just stopped. **Error on console you see when that happens during `openclaw update` (or not if you let openclaw update itself 💀 ** `Update Result: ERROR Root: /home/ndeet/.npm-global/lib/node_modules/openclaw Reason: global update Before: 2026.2.15` When trying to run `openclaw status` there was an error that the binary was not found anymore: `$ openclaw -bash: /home/ndeet/.npm-global/bin/openclaw: File or directory not found` ##What happened (in my case): System ran out of memory and I did not have a swapfile configured. I run openclaw on a local server using proxmox kvm VM and it has 4GB of ram. **to check if your server also ran out of memory: ** `journalctl -b | grep -i "out of memory\|oom\|killed process"` if it shows some crashes of openclaw.service or npm then you likely have the same issue as me In my case the old install was moved to temporary directory but new version not installed yet due to error ``` $ ls -lah ~/.npm-global/bin/ total 8,0K drwxrwxr-x 2 ndeet ndeet 4,0K 18. Feb 11:29 . drwxrwxr-x 4 ndeet ndeet 4,0K 30. Jän 17:35 .. lrwxrwxrwx 1 ndeet ndeet 44 30. Jän 18:06 clawdhub -> ../lib/node_modules/clawdhub/bin/clawdhub.js lrwxrwxrwx 1 ndeet ndeet 40 30. Jän 18:06 mcporter -> ../lib/node_modules/mcporter/dist/cli.js lrwxrwxrwx 1 ndeet ndeet 41 16. Feb 11:54 .openclaw-8sOzPP85 -> ../lib/node_modules/openclaw/openclaw.mjs ``` note that there is no symbolic link pointing to openclaw.mjs but only the temporarily moved one of `openclaw-8sOzPP85` Solution: move symlink so openclaw works again `mv ~/.npm-global/bin/.openclaw-8sOzPP85 ~/.npm-global/bin/openclaw` Now openclaw should work again (try by running `openclaw status`) but doing update would likely crash again. The best solution would be to allocate more RAM but it could also be that you did not have any swap configured that can be used for ram spikes like this (check with `free -h | grep Swap`). So if you don't have any swap you can create a swapfile. ##Create a swapfile: ``` # Create the file sudo fallocate -l 4G /swapfile # Secure it (only root should read it) sudo chmod 600 /swapfile # Format as swap sudo mkswap /swapfile # Enable it sudo swapon /swapfile # Verify free -h ``` Make it permanent across reboots: `echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab` Optionally, tune swappiness (default is 60, lower = RAM preferred over swap): `echo 'vm.swappiness=10' | sudo tee -a /etc/sysctl.conf` `sudo sysctl vm.swappiness=10` **You can now try the update again and it should work. 🥳 **

You didn't sell your whole stash, right? Just living expenses, right? View quoted note →

🤣 View quoted note →

Don't use #openclaw wrapper services that make it easier to run. It's already easy and the creator of openclaw discourages it himself. He constantly works to make it easy as possible to do it yourself. Most wrapper services will be gone when the hype dies off. When you use wrapper service you expose data to: - wrapper service - hosting provider (maybe subcontractor of datacenter) - model provider When you host at VPS provider: - hosting provider (maybe subcontractor of datacenter) - model provider When you host at home *: - model provider ** * you don't need a mac mini, completely overblown, you can run on e.g proxmox server (2-4gb ram plenty enough), start9, or old laptop, you don't even need it run 24/7 ** you can use Maple AI which anonymizes data, not sure about ppq.ai. Best would be local models but not economically possible with big models atm. No matter what as long as local models not possible, you will always send sensitive data to model providers to complete tasks. Better avoid other 3rd parties that can also read your data. If you can't do it yourself ask someone you trust to set it up on your home server or on a VPS rented by you. Avoid convenient wrappers.