ā”ļøš¤” WATCH - Let's not forget how, just a few short years ago, the entire planet became one giant insane asylum, almost overnight.
https://blossom.primal.net/47b884a59542d0f087f11d0925ad25ea4bc6aeaa1120f0d958f6227c529218e2.mov
Don't forget about anal swab tests šš
Yes, I just tried it with one peer, and it worked fine.
Fair pointādevelopers arenāt obligated to cater to users who donāt pay them. But in open-source, users choose to adopt software based on its relevance to their needs. If your code drifts too far from those needs or betrays core principles, people will start looking elsewhere. Thatās not entitlementāitās decentralization in action.
Look at Mozilla: Firefox didnāt fall because of bad engineering, but because they abandoned the principles that built user trust. The result? Gradual loss of relevance.
Weāre not at that point with Bitcoin Coreābut the growing number of users migrating to Bitcoin Knots should be a wake-up call, not something to dismiss.
Open-source thrives when devs and users stay in syncāignore that, and alternatives will fill the gap.
Could you clarify why it makes more sense? It seems unrelated to me.
I dislike spam in Bitcoin, but relay filtering is symbolic unless miners enforce it. Nodes dropping txns doesn't prevent inclusion; direct submission bypasses relay. Is there any real change possible here without a consensus rule change? Answer: No.
As long as a transaction is valid by consensus rules, any miner can include it. Thatās Bitcoinās anti-censorship design working as intended.
Relay filters might save some bandwidth or express disapproval, but they donāt stop data from being mined. At best, they delay it. At worst, they centralize incentives.
To truly prevent a class of transactions (e.g. spam, inscriptions, BRC-20ā¦), youād need to change the consensus rules ā i.e. redefine what is valid. But that would require a hard fork.
Bitcoin's neutrality means it doesnāt care why you're transacting. If itās valid, itās valid.
Relay filtering policies only provide the illusion of control. Without miner enforcement or consensus change, they wonāt fix the problem.
If you are using nix-bitcoin and want to run the latest version of Bitcoin Knots, you will need to install it from the unstable branch.
Edit the file configuration.nix and add
--------------------------------
services.bitcoind.package = let
pkgsUnstable = import (builtins.fetchTarball {
# nixpkgs-unstable as of 2023-12-12
url = "https://github.com/NixOS/nixpkgs/archive/f63e74871f46b4bad723740799298aca7416511c.tar.gz";
sha256 = "06hnc0bmpz8y95r59hpzfv0czwka6vxld6a28vazggdyhr1f4d27";
}) {};
in
pkgsUnstable.bitcoind-knots;
----------------------------
This example is for v28.1.knots20250305. To use a newer version, update the url and sha256 fields as follows:
1. Go to https://search.nixos.org/packages and search for bitcoin knots, then click on the source link.

2. Find the latest commit and click on it (for this example f63e748).

3. The commit hash will be part of the URL. Use it to construct the tarball URL: https://github.com/NixOS/nixpkgs/archive/commit_hash.tar.gz
For this example: f63e74871f46b4bad723740799298aca7416511c
4. Run nix-prefetch-url --unpack https://github.com/NixOS/nixpkgs/archive/commit_hash.tar.gz to get the SHA256.

With blinded paths, privacy is superior, but not without it, since you're exposing your node's pubkey (assuming you're using your own) and thus your entire balance.
The street price can also be the market price, in many p2p platforms when you place orders at the market price they are accepted very quickly. I've never understood why we have to assume that there is a premium, since p2p trading benefits both parties involved.
It doesn't just limit its use. It is no longer legal tender.
I'm not saying you're wrong, but the reality is that there is a demand for USDT, in fact some altcoins are only widely used because they have a cheap way to transact USDT. Don't you think it's better to have that volume in bitcoin instead?
Doing a quick search, it seems there is a plugin for this, but since you're a privacy focused company and you seem interested in USDT, why not do it on Liquid? At least the transactions are confidential.
It doesn't matter what he does, he has completely surrendered to his masters, the IMF, by making bitcoin no longer legal tender. He wants to look like he hasn't lost his dignity by saying they will continue to accept it on a voluntary basis, but that's the difference between being legal tender or not. Stacey continues to claim that btc is still legal tender, which is false.
Since manually editing files is not recommended with start9, I was wondering if there was a way to replicate the db from cln.
By editing the config file it is enough to add this line:
wallet=sqlite3:///home/user/.lightning/bitcoin/lightningd.sqlite3:/my/backup/lightningd.sqlite3
Is there any available option to do it? I've checked long ago and didn't find it in the UI.




