Update: I found 10! View quoted note →

Looking at the repo I see just luke doing commits ? What evidence do you have of other contributors ?

The real MVPs

for each one, I linked to their githubs so that you can review their contributions. Here are some examples of each person's contributions: - leo_haf got this code merged:

GitHub

v28.1.knots20250305 leo-haf by Retropex · Pull Request #32 · bitcoinknots/guix.sigs

Note: i was able to reproduce the signing bug for macOS build foo@bar Downloads % sha256sum -c SHA256SUMS bitcoin-28.1.knots20250305-aarch64-linux-...

- bigshiny90 got this code merged:

GitHub

28.1.knots20250305 bigshiny90 by bigshiny90 · Pull Request #37 · bitcoinknots/guix.sigs

- ataraxia got this code merged:

GitHub

29.1 Rc1 attestations by Ataraxia009 · Pull Request #38 · bitcoinknots/guix.sigs

routine attestation for rc also adding builder keys

- pithosian created this pull request, which has not yet been merged:

GitHub

Knots Privacy Tweaks · Pull Request #135 · bitcoinknots/bitcoin

Running Knots has far less potential to be personally identifying than it used to, thanks to the recent surge in Knots users 🎉, but it would sti...

- Chris Guida reviewed the above-mentioned pull request - Floppy Disk Guy reviewed it too - dr0ther created this docker container for Knots:

GitHub

GitHub - dr0ther/bitcoin-knots-docker: Bitcoin Knots Docker implementation

Bitcoin Knots Docker implementation. Contribute to dr0ther/bitcoin-knots-docker development by creating an account on GitHub.

- Kurtis worked on the font and imagery used in Knots:

GitHub

Commits · KurtisStirling/Bitcoin-Knots-Brand

Brand assets for Bitcoin Knots. Contribute to KurtisStirling/Bitcoin-Knots-Brand development by creating an account on GitHub.

- kwsantiago created this pull request, which has not yet been merged:

GitHub

feat(rpc): Export GUI Policy Options for Headless Deployments by kwsantiago · Pull Request #154 · bitcoinknots/bitcoin

Summary Add RPC commands to export/import GUI policy settings for headless systems (Start9, Umbrel). Relates to #130 Changes dumpsettings: Export ...

one of those merges is generating sigs on some files. Be serious, contributions are code or code adjacent things you're presenting these people as contributors for doodling in the margins.

Only one Knots Dev myth busted.

For me this is code signature so it’s not really a code contribution, here is a real PR with code that have been added to the latest RC

GitHub

update `-rejecttokens` to catch OpenStamps by Retropex · Pull Request #151 · bitcoinknots/bitcoin

Filter based on their own protocol. count for #64

(Due to how Luke rebase Knots, the PR won’t be merged on GitHub but directly added to the tag) here is the relevant commit:

GitHub

Policy: Update rejecttokens to catch OLGA · bitcoinknots/bitcoin@96ebf21

Co-authored-by: Léo Haf <leohaf@orangepill.ovh>

If your only objection is that the example I gave for Leo wasn't actually code, I hope the attached post strengthens the case. Let me know if any of the others shouldn't count. View quoted note →

BTW I include the word "deliberately" because, in an important way, Knots has a bunch of "accidental" contributors. Basically everyone who contributes to Bitcoin Core also contributes to Knots, knowingly or not, because Knots is mostly just Core with some patches.

Don't trust, verify. Add a badge to the purity test sash

And when 7 of them think there is a problem with Luke’s update and Luke thinks it should get published, which way will it go?

It can go to a fork, just like knots itself

I'm asking for the last time send me a picture message for your gift package 📦 so you can receive it today or tomorrow okay 🆗📦📦 Massage me Whatsapp https://wa.me/+1(541)9693337 https://wa.me/+1(541)9693337 https://wa.me/+1(541)9693337 https://wa.me/+1(541)9693337 https://wa.me/+1(541)9693337 https://wa.me/+1(541)9693337 https://wa.me/+1(541)9693337 https://wa.me/+1(541)9693337

there is also

GitHub

GitHub - lnhance/bitcoinknots-bitcoin: Bitcoin Knots enhanced Bitcoin node/wallet software

Bitcoin Knots enhanced Bitcoin node/wallet software - lnhance/bitcoinknots-bitcoin

but we are not sending stuff upstream.

nice! tell me more about your fork why did you make it?

what do you think

i don't remember what i was thinking. but clearly i was mistaken.

It's more than one guy. But his point is still valid.

This is knots contributor

Regardless Knot or Core .. the crypto always problem . There should not be so much coin in circulation that people can just issues coin as they want ! It is not sustainable to fraud for the user !!!

1st, This is first and formost false information. It's not just luke. see:

Super Testnet

At least 10 devs deliberately contribute to Knots:&#10;&#10;1 x.com/LukeDashjr, &#10;&#10;2 x.com/leo_haf, &#10;&#10;3 x.com/bigshiny90, &#10;&#10;...

2nd, you entirely miss the point and make this about who develops the software, but this is myopic and irrelevant. Bitcoin works by node runners/miners deciding what software to run. Every node implementation can propose their own version and node runners will decide whether to upgrade or switch. That is true for bitcoin knots as well as soon as luke does something node runners disagree with. The bitcoin community is wealthy enough to fund new developers if necessary. Thus, the steward is the bitcoin network or community at large, including bitcoin users too - and the great thing is that it is anonymously large so not prone to group think. There is no need for another layer of stewardship of tiny group of software developers. Core takes themselves way too important. Bitcoin is global and bitcoin is massive - this is much larger than the Blockstream company and always was - thinking otherwise is imho hybris to say the least.