Damus
TracaChang profile picture
TracaChang
@TracaChang
Relays (12)
  • wss://nos.lol/ – read & write
  • wss://nostr.oxtr.dev/ – read & write
  • wss://yabu.me/ – read & write
  • wss://nostr.bitcoiner.social/ – read & write
  • wss://relay.0xchat.com/ – read & write
  • wss://relay.damus.io/ – read & write
  • wss://eden.nostr.land/ – write
  • wss://nostr-pub.wellorder.net/ – read & write
  • wss://nostr.huszonegy.world/ – write
  • wss://auth.nostr1.com/ – write
  • wss://relay.siamstr.com/ – read & write
  • ws://skzzn6cimfdv5e2phjc4yr5v7ikbxtn5f7dkwn5c7v47tduzlbosqmqd.onion/ – read & write

Recent Notes

Rizful.com (zap tester) · 20w
we did some zap tests on this note… your profile only specifies a nip05 nostr address, but not a lightning address, so we tried to zap your nip05 address.... we made six attempts to⚡zap this note, at [email protected], over a period of about 1 hour. in each case, we found that your light...
ko yaa nis fiatsi · 36w
"Not so bad, what's the problem?" says Forbes 🙄 Never forget the anal swabs that make up the MSM https://www.forbes.com/sites/roberthart/2021/02/01/anal-swab-covid-test-wont-make-you-waddle-like-a-penguin-china-says/
🥚 · 38w
Tap on the nickname at the top.
Sjors Provoost (possibly compromised) · 51w
Excellent take by me! :-) The fact that many Bitcoin Core developers are paid by someone, when that someone is NOT YOU, does not make YOU a customer that gets to demand things. You need to hire devel...
TracaChang profile picture
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.
nostrich · 50w
Thank you very much.
TracaChang profile picture
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.
❤️1
TracaChang profile picture
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.