Nostr notes by

This bridging trick sounds great. ...

2026-01-25T13:30:18Z

This bridging trick sounds great.

https://fountain.fm/episode/QMpGyNifZM37FW3P1a7x

quoting
nevent1q…9hed

There seems to be genuine confusion about how open source works. ...

2025-05-10T11:35:39Z

There seems to be genuine confusion about how open source works. In particular some people believe that Bitcoin Core developers have a fiduciary duty, either towards them personally or towards some general notion of the Bitcoin network. They are surprised that I and some others respond to this rather aggressively.

Remember that this is the argument Craig Wright tried to make. He failed, but not after millions of dollars were burnt on defending these developers. And not after several quit because of the stress. Don't go down this path.

To put it as a catchy phrase: open source means you can do whatever you want with the code, not with the people who write it.

Open source lets you fork code, and modify it to your liking. That's pretty much what I do every day, which isn't to say that I don't also try to make sure other people like it. I get paid in Bitcoin and OpenSats keeps their whole treasury in it, so the idea that I want destroy potential future income is rather retarded.

Part of CSW's demands was that Bitcoin Core wrote specific (confiscation) code for him. Eventually he just hired people to write it for him, as one should, but somehow that still wasn't enough for him. I get a very similar vibe from people who run Knots but yet don't find that enough. Should we worry about a new round of lawsuits?

It's also unclear what he's offended by. If it's the ...

2025-05-10T10:02:17Z

In reply to nevent1q…349g
_________________________

It's also unclear what he's offended by. If it's the "catholic" part, I'm merely describing the suspect without any value judgement. There's additional context that allowed me to narrow it down. I won't share that, because it's something only the perpetrator would know, so potentially relevant if they escalate.

Ja, ik ben een van de (daadwerkelijke) reviewers van de pull ...

2025-05-10T09:54:26Z

In reply to nevent1q…yhhe
_________________________

Ja, ik ben een van de (daadwerkelijke) reviewers van de pull request(s) die de op_return limiet verwijderen. Mijn ack heeft aanzienlijk meer gewicht dan een drive-by commenter. Daarnaast heb ik een vrij uitgesproken en geïnformeerde (toch?) mening over dit onderwerp hier op nostr en mijn podcast.

Ik ben hier niet bepaald gevoelig voor, danwel ik raak er extra gemotiveerd van, maar veel developers zijn een stuk voorzichtiger en zouden hier wel degelijk door ontmoedigd worden. Zie bijvoorbeeld de opmerking op Reddit van achow101 dat ze onmiddellijk op unsubscribe drukte van die eerste pull request.

Intimidatie. Zelfde principe als een granaat voor je door, alleen ...

2025-05-10T09:44:03Z

In reply to nevent1q…yfa6
_________________________

Intimidatie. Zelfde principe als een granaat voor je door, alleen een mildere stap. Probleem is dat je niet weet wat de volgende stap is.

No. Donations are not a contract for performance of specific ...

2025-05-10T09:42:29Z

In reply to nevent1q…26kf
_________________________

No. Donations are not a contract for performance of specific tasks or the creation of a fiduciary relationship. They are appreciated of course.

Someone, probably a US based catholic young male, subscribed my ...

2025-05-10T08:21:42Z

Someone, probably a US based catholic young male, subscribed my email to a bunch of lists in order to spam me. I can't be bothered to trace the IP they used for this. But Luke, control your herd.

Reminds me of a Bitcoin lawyer who was often a guest on ...

2025-05-06T18:55:30Z

In reply to nevent1q…d7pz
_________________________

Reminds me of a Bitcoin lawyer who was often a guest on Junseth's podcast, forgot his name, who used to say: "I'm a lawyer, but not YOUR lawyer"

cc @npub1xap…cnde

2025-05-06T18:51:14Z

In reply to nevent1q…pfsx
_________________________

cc Shinobi (npub1xap…cnde)

Excellent take by me! :-) The fact that many Bitcoin Core ...

2025-05-06T18:49:43Z

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 developers directly if you want to work on your behalf.

quoting
nevent1q…x62e
Ridiculous take by nprofile1qqsgdp0taan9xwxadyc79nxl8svanu895yr8eyv0ytnss8p9tru047qpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3samnwvaz7tmwdaehgu3wwdc8ymmkdahhxapwdekqzrthwden5te0dehhxtnvdakqm9jn0c (nprofile…jn0c) & Shinobi.

Core is well funded & will continue to be even moreso as more countries get involved with Bitcoin.

Nostr event nevent1qqsfyy35ne8pm7mx08tt6sqt8kpf4htr2ku2j2q0ep7w5w6g386s2dqzyzrgt6l0vefn3htfx83veheur8vlpedpqe7frrezuuypcf2clra0sx2f9gu

2025-05-06T18:44:05Z

In reply to nevent1q…rvd3
_________________________

nevent1qvzqqqqqqypzpp59a0hkv5ecm45nrckvmu7pnk0sukssvly33u3wwzquy4v037hcqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgewaehxw309ahx7um5wgh8xurjdamx7mmnwshxump0qqsvgyvfqz383j30szkg24hzyvvcvenmzdp2areaea68n0g8wnspdcqj6tstn

Quadrupple it!

2025-05-06T18:36:48Z

In reply to nevent1q…0wem
_________________________

Quadrupple it!

That particular section was mostly written ten years ago, even ...

2025-05-06T18:20:11Z

In reply to nevent1q…lu58
_________________________

That particular section was mostly written ten years ago, even before the Blocksize wars. Social media powered brigading wasn't much of a thing back then. It could make sense to update it and mention that each fork may or may not have a moderation policy.

Especially important now: 3. Rough consensus is achieved when all ...

2025-05-06T18:12:15Z

In reply to nevent1q…usew
_________________________

Especially important now:
3. Rough consensus is achieved when all issues are addressed, but not necessarily accommodated

On Consensus and Humming in the IETF (Internet Engineering Task ...

2025-05-06T18:11:20Z

On Consensus and Humming in the IETF (Internet Engineering Task Force)

Classic read.
https://datatracker.ietf.org/doc/html/rfc7282

Moderation guidelines are not in the Bitcoin Core codebase ...

2025-05-06T18:06:06Z

In reply to nevent1q…6h30
_________________________

Moderation guidelines are not in the Bitcoin Core codebase itself. That would make no sense, since any fork could and should have its own policy.

There's ongoing effort to move bitcoin/bitcoin to bitcoin-core/bitcoin to reduce that confusion.
https://github.com/bitcoin-core/meta/blob/main/MODERATION-GUIDELINES.md

Well, according to AI - which must be right - this way the best ...

2025-05-06T18:00:02Z

Well, according to AI - which must be right - this way the best quote from me in the Bitcoin Optech (npub1hku…432p) podcast: https://riverside.fm/guest-page?sessionId=2c859898-b88a-4016-abb6-c0fc6e8cb3c8&clientId=3d897568-30e6-4244-8a6d-59ebb8c8855b&archiveId=sjors-qg14v9s75&t=080a6fc0b5a20ddcd074

How many times do people need to repeat this? USE SOMETHING ELSE ...

2025-05-06T15:54:00Z

In reply to nevent1q…tmsc
_________________________

How many times do people need to repeat this? USE SOMETHING ELSE IF YOU'RE UNHAPPY.

There's also the question of how many people audit the 1370 ...

2025-05-06T14:13:28Z

In reply to nevent1q…6slx
_________________________

There's also the question of how many people audit the 1370 commits that make Knots different. It's basically a giant patch set on top of Bitcoin Core, similar to what Liquid does. Despite my issues with Luke, I do trust him to not steal peoples coins.

But that's not an ideal trust model. Part of the problem is a lack of upstreaming. And that's not always because of a fundamental disagreement on functionality. Sometimes the patches just don't meet the review bar for Bitcoin Core. That itself isn't the end of the world either, but it does make comparative review harder.

But I hear OpenSats is going to fix that with grants? :-)
https://github.com/bitcoin/bitcoin/compare/v28.1...bitcoinknots:bitcoin:28.x-knots

quoting
nevent1q…g5j7
if you are a bitcoin knots contributor, you should apply to opensats

https://opensats.org

Here's an alternative timeline to consider: Bitcoin Core as a ...

2025-05-06T13:35:21Z

In reply to nevent1q…ypkl
_________________________

Here's an alternative timeline to consider: Bitcoin Core as a project seizes to exist, no more updates appear on Github. The current developers are all hired by different companies that can afford it. They continue to work, and informally exchange patches.

Some of those patches are published, and maybe one or two developers maintain a public collection of the most useful patches. The end result would be that most users are running inferior software compared to the corporations with money. Afaik this would be perfectly legal under the MIT license.

People seem to be confused about the fact that although Bitcoin ...

2025-05-06T13:23:15Z

People seem to be confused about the fact that although Bitcoin Core is open source software, the bitcoin/bitcoin Github repository is a private space, not a public square. As a private space it has rules. Very few, and there's not much enforcement, but they're there. And those rules are not decided by users (in fact, ultimately Microsoft controls the domain).

People are free to fork the code and create an alternative space to work on that code. There they can have whatever rules they want. You can make it completely private. The MIT license is very permissive, you don't even have to share the resulting code. You could also allow anyone to comment and sell viagra pills. Up to you!

Such code forks are not ideal though. It could create confusion around where to download the "real" Bitcoin Core. Slightly different codebases make things difficult to audit. When implementations diverge too much, it will make future soft forks hard to coordinate. But if contributors to Bitcoin Core can't get any work done when doing so in public, they'll have to find another way to get work done.

So as a user, you should not be happy when brigading happens on the repo. Those are precious developer days being wasted, in which actual bugs are not being fixed - or even introduced because tired developers make mistakes.

Even if you disagree with a specific change, you have an interest in that being communicated in a non-disruptive manner.

quoting
nevent1q…dctu
It was already multiple times on that pull request that conceptual discussion needs to happen on the mailinglist. Yet people ignore that instruction. And as I predicted, they kept doing so.

When people break into your office and start screaming at staff, sending them away is not "censorship".

> You suggested censoring people which is a form of harassment ...

2025-05-06T12:44:35Z

In reply to nevent1q…sarz
_________________________

> You suggested censoring people which is a form of harassment

It's complete nonsense and I don't have time to engage bad faith actors like "BitcoinIsFuture".

[1] De Volkskrant, 29 april 2025, ‘Cryptomijnen in een land ...

2025-05-06T12:38:52Z

In reply to nevent1q…x526
_________________________

[1] De Volkskrant, 29 april 2025, ‘Cryptomijnen in een land onder hoogspanning’, (https://www.volkskrant.nl/kijkverder/v/2025/ethiopie-bitcoin-miners-crypto~v1402259/)

Ethiopië is niet eens een voormalige kolonie, maar de Tweede ...

2025-05-06T12:38:47Z

Ethiopië is niet eens een voormalige kolonie, maar de Tweede Kamer wil er zich mee bemoeien. Tekst van de motie:

Vragen van de leden Diederik van Dijk, Stoffer en Flach (allen SGP) aan de ministers van Buitenlandse Zaken, van Financiën en voor Buitenlandse Handel en Ontwikkelingshulp over het bericht ‘Cryptomijnen in een land onder hoogspanning’. 
 
• Bent u bekend met het artikel ‘Cryptomijnen in een land onder hoogspanning’?[1] 
• Welke Nederlandse of Europese wet- en regelgeving, dan wel IMVO-normen, zijn van toepassing op Nederlandse ondernemers en bedrijven die actief zijn in het cryptomijnen in derde landen? 
• Wat is precies de toegevoegde waarde van het cryptomijnen in Ethiopië aan de lokale economie en samenleving? 
• In hoeverre profiteert de lokale bevolking van Ethiopië van de praktijken die in het artikel genoemd worden? 
• Kan het kabinet toelichten wat volgens haar de wenselijkheid is van het cryptomijnen in Ethiopië door Nederlandse ondernemers en bedrijven? 
• Hoe ziet de inzet van het kabinet eruit om de beperkte elektriciteit die voorradig is in Ethiopië ten goede te laten komen aan de bevolking zelf? 
• Acht het kabinet het noodzakelijk om met extra regelgeving te komen om de negatieve gevolgen van cryptomijnen in derde landen te verminderen, en zo nee, waarom niet? 
• Wat is het morele oordeel van het kabinet over het artikel, met name met het oog op de schrijnende armoede en grote maatschappelijke problemen die een land als Ethiopië teisteren? 
• Hoe verhoudt de ontwikkeling die in het artikel genoemd wordt zich tot de Nederlandse hulp aan Ethiopië? Werken deze elkaar niet tegen? 

https://www.tweedekamer.nl/kamerstukken/kamervragen/detail?id=2025D19807&did=2025D19807

Roger Ver 'calm and politely' calling out Bitcoin Core ...

2025-05-02T17:51:25Z

Roger Ver 'calm and politely' calling out Bitcoin Core censorship, even of people who've been around since the early days. He calls out their conflicts of interest and corruption, their deviation from the original version of Bitcoin... And they always go off on these super technical tangents. And they're mean on camera. "Won't even answer a single question".

Install Bitcoin ABC, now! (yes, it's still actively maintained)

P.S. wow people were young back then
https://youtu.be/dUxXGmgv5mo

I don't mean to diss OP here, but free market analogies have ...

2025-05-02T16:23:48Z

I don't mean to diss OP here, but free market analogies have often misguided people. Sometimes you need good engineering. It really is what led to Bitcoin Cash.

But that doesn't mean blindly trusting engineers. You should find out if they really know what they're doing. How to find out? That's a hard problem, i.e. they can't all get on a person phone call with you, some have an abrasive communication style, sometimes a problem seems very simple but take a lot of curriculum knowledge to grok. You can't just trust them either when they say "it's complicated", because that what charlatans would say too.

quoting
nevent1q…5yle
To cite Roger Ver:
> The market determines the ideal block size and network fee.
https://www.reddit.com/r/btc/comments/errkm2/the_market_determines_the_ideal_block_size_and/

To cite Roger Ver: > The market determines the ideal block ...

2025-05-02T16:20:07Z

In reply to nevent1q…xux3
_________________________

To cite Roger Ver:
> The market determines the ideal block size and network fee.
https://www.reddit.com/r/btc/comments/errkm2/the_market_determines_the_ideal_block_size_and/

I would recommend Greg Maxwell and AJ Towns latest replies on the ...

2025-05-02T16:10:13Z

In reply to nevent1q…8q2c
_________________________

I would recommend Greg Maxwell and AJ Towns latest replies on the mailinglist. It's harmful if people use different settings, whether that's by configuration option (-datacarriersize) or by code forks (Knots). The chaos of a "free market" for settings is disruptive for the network, which only helps its real adversary: governments.

The custom Knots default of 42 bytes caused problems in the past for Samurai wallet (which they in turn used for their drama marketing). In theory it should also interfere with compact block relay (I haven't seen measurements though).
https://gnusha.org/pi/bitcoindev/aBSVn7nJnrheLy5Z@erisian.com.au/

Yes, that's on. But I get a notification for each zap afaik. ...

2025-05-02T14:16:53Z

In reply to nevent1q…ukpp
_________________________

Yes, that's on. But I get a notification for each zap afaik. I don't get that many, a few per day, but I really don't like push notifications :-)

So although I understand it doesn't look great when I respond ...

2025-05-02T13:22:15Z

In reply to nevent1q…2fs9
_________________________

So although I understand it doesn't look great when I respond like this, it would have been even worse if I attacked him without provocation. Even though perhaps that would have been more ethical.

Since then he hasn't attacked me personally, until now, ...

2025-05-02T13:20:03Z

In reply to nevent1q…8sh5
_________________________

Since then he hasn't attacked me personally, until now, because I reviewed a pull request he hates.

In the mean time Luke has attacked Bitcoin Core on multiple occasions, e.g. creating needless drama around Taproot activation. Meanwhile despite calling Bitcoin Core all sort of bad names, he uses 99.99% of its code for Knots. Although he does occasionally contribute back, and of course has contributed much in the far past, it's not a healthy open source relationship.

Much of the drama he creates also comes across as either blatant self-promotion or his company Ocean (which I like, so that's unfortunate).

To be fair, my router runs BSD, I have several Ubuntu machine, a ...

2025-05-02T13:12:19Z

In reply to nevent1q…z2qk
_________________________

To be fair, my router runs BSD, I have several Ubuntu machine, a Mac to get actual work done and a Windows machine for Bitcoin Core occasional testing.

* after which he block me

2025-05-02T13:03:21Z

In reply to nevent1q…3cq0
_________________________

* after which he block me

If you're saying I should have called him out earlier, ...

2025-05-02T13:02:48Z

In reply to nevent1q…8cdz
_________________________

If you're saying I should have called him out earlier, you're correct.

In fact I probably did back in 2017 on Twitter, because he blocked me for a few years.

Looks like there's a beta? ...

2025-05-02T11:00:25Z

In reply to nevent1q…0a77
_________________________

Looks like there's a beta? https://bitcoinops.org/en/topics/utreexo/

If you're worried about sitting on user funds for too long, ...

2025-05-02T10:59:21Z

In reply to nevent1q…tznm
_________________________

If you're worried about sitting on user funds for too long, and the app can't do all this in the background, it's fine if the app nags me once a day or so collect the sats. And send a push message like: X dust ready to collect!

@npub1kva…tkzv can you add a threshold amount setting below ...

2025-05-02T10:56:55Z

Minibits (npub1kva…tkzv) can you add a threshold amount setting below which:
1. You don't send a push notification
2. You don't show the transaction
3. You do collect the zap(s), either in the background or the next online session
#spam #zapvertising

That's what I've been told, I don't know if ...

2025-05-02T09:29:04Z

In reply to nevent1q…6hwa
_________________________

That's what I've been told, I don't know if there's (public) data on this.

It does make sense. While the big corporate miners can hire fancy developers, who would use Mac or Linux, there's many very small miners out there. Those are often "normal" people who are good at buying equipment and getting access to electricity. Most "normal" people use Windows.

One way to look at OP_RETURN usage by "L2" projects, is ...

2025-05-02T09:04:50Z

In reply to nevent1q…3k23
_________________________

One way to look at OP_RETURN usage by "L2" projects, is to get a sense of what future op codes could look like. If people keep sticking zero knowledge proofs there, maybe at some it makes sense to just add a zero knowledge proof output type. Obviously that's a _very_ long time out, and there might be very good reasons to never do it. But you can look at it as a (permissionless) draft.

And yes, Linux people look at Mac users they way Mac users look ...

2025-05-02T09:01:32Z

In reply to nevent1q…s9mc
_________________________

And yes, Linux people look at Mac users they way Mac users look at Windows users.

Windows is back! Although Satoshi started out with a Windows ...

2025-05-02T09:00:57Z

Windows is back!

Although Satoshi started out with a Windows client, and apparently many miners still use it, most sane developers and security conscious people use Mac or Linux. Over time this led to increasing neglect of Windows support in #BitcoinCore, to the point where some people joked (?) about just dropping it entirely.

But it seems there's renewed attention.

From a PR point of view I agree that tone matters. But I find it ...

2025-05-02T08:53:26Z

In reply to nevent1q…0gwm
_________________________

From a PR point of view I agree that tone matters. But I find it unreasonable to expect people to be very nice and friendly when they're attacked by a brigade of mostly bad faith actors, whether it's just people who refuse to read up on a topic before expressing their strong opinion, or actually targeted attacks to intimate developers into not writing or reviewing code.

That, and he's just French :-)

And from that I'm assuming various BitVM schemes will work in ...

2025-05-02T08:42:38Z

In reply to nevent1q…xzr6
_________________________

And from that I'm assuming various BitVM schemes will work in similar ways. Hard to predict what ends up being successful here.

The Stack Exchange post links to the mailinglist post by Antoine ...

2025-05-02T08:41:44Z

In reply to nevent1q…snug
_________________________

The Stack Exchange post links to the mailinglist post by Antoine Poinsot. It it turn uses Citrea as the example. They use some sort of watch-tower scheme that needs to look for zero-knowledge proofs on chain and then react.

This also illustrates that if we had made this change earlier, ...

2025-05-02T08:40:24Z

In reply to nevent1q…rzqg
_________________________

This also illustrates that if we had made this change earlier, they would not have designed the system to create unspendable public keys in the first place.

They have no financial incentive to deviate from the original design. And once such a system goes live, assuming it has any uptake, their engineers will be busy with all sorts of more urgent things.

Any typical corporate CTO would look at this situation and say: hey look, there's a bunch of drama here, let's assume the brigaders win and the OP_RETURN limit stays in place. So let's just stick to the original design. We're not price sensitive, so it's the safest option. It also saves us a bunch of engineering hours. Also, it protects our engineers from being harassed.

Finally, this also goes to show that we really need to make progress on Utreexo, because UTXO set growth is a sitting duck. All we can do is ask people nicely to not grow it needlessly.

Right, that would make more sense. In the insane scheme of ...

2025-05-02T08:25:48Z

In reply to nevent1q…pdvx
_________________________

Right, that would make more sense. In the insane scheme of things.

Stamps use CounterParty under the hood, which simply switches to ...

2025-05-02T08:18:35Z

In reply to nevent1q…970x
_________________________

Stamps use CounterParty under the hood, which simply switches to bare multisig once the payload goes over 80 bytes. With the proposed Bitcoin Core change to policy, or just considering relay reality, CounterParty could stop doing that. But afaik nobody is maintaining it, and the inefficiency is a feature for some of its users (stamps).

With stamps the explicit goal was to bloat the UTXO set. Their ...

2025-05-02T08:17:20Z

In reply to nevent1q…hwn2
_________________________

With stamps the explicit goal was to bloat the UTXO set. Their marketing framed that as "unprunable".

Counterparty was designed before SegWit and due to fee spikes around that time was pretty much unmaintained afaik.

BRC-20 is just crazy. JK, I have no idea how that one works.

https://bitcoinexplainedpodcast.com/@nado/episodes/bitcoin-explained-76-stamps-and-the-invalid-block-caused-by-it

This seemed worth clarifying, so I did the thing where I ask a ...

2025-05-02T08:07:19Z

This seemed worth clarifying, so I did the thing where I ask a question and answer it myself:
https://bitcoin.stackexchange.com/q/126208/4948

With regards to what I said here: > This then encourages them ...

2025-05-02T07:19:13Z

In reply to nevent1q…3uzq
_________________________

With regards to what I said here:

> This then encourages them to be on the safe side and use these filters. Bitcoin Core might then have to adopt similar rules in order to produce blocks that are safe.

This would be a "nice" use case for what Greg Maxwell suggested today on the mailing list (and earlier on Reddit), to separate relay policy from mining policy - where the latter can be more strict:

> That said, Bitcoin core has generally not
had knobs to adjust relay policy as distinct from mining policy in large
part because of the design assumption that the two need to be the same.
But in this case if there were a knob here I think would make more sense
for it to control mining policy rather than relay policy, since it would
actually have some effect in the mining context (in excluding the txn from
your own blocks) while as a relay only thing it is impotent.

Luke is signalling his followers to attack me via his clown ...

2025-05-02T06:24:46Z

In reply to nevent1q…hqqj
_________________________

Luke is signalling his followers to attack me via his clown emojis. That has nothing to do with being on the side of any argument. It's an intimidation tactic to stop me from reviewing the pull request. It's as effective as the filters though.

My observation that he is a cult leader is not based solely on this incident. He's been consistently behaving like one since at least the 2017 UASF days.

To be clear, this won't permanently censor these transactions ...

2025-05-02T06:17:43Z

In reply to nevent1q…nxc9
_________________________

To be clear, this won't permanently censor these transactions either, but because not everyone is going to be sufficiently intimidated. But it will delay them more than in the scenario where those miners only exclude things from their own blocks. And definitely delay them more than can be achieved with just policy, even if 90% of nodes used these filters.

I should also emphasise the word "might", in contrast to ...

2025-05-02T06:13:49Z

In reply to nevent1q…jm8t
_________________________

I should also emphasise the word "might", in contrast to the current proposals which certainly don't work.

The goal of the filter people is to censor OP_RETURN and inscriptions specifically. They have no rational basis for this, as you explained, but I'm just taking this goal at face value.

Without a consensus change it's impossible to stop the transactions from going through eventually, but you could try intimating miners into self-censorship. We know from human societies that a fairly small group of people can control a very large group at fairly low cost. A key ingredient seems to be to disproportionately punish offenders to set an example.

So if you can gather a few percent of hash rate that enforces these arbitrary filters through reorgs (N deep, depending on budget), some pools will experience noticeable losses. This then encourages them to be on the safe side and use these filters. Bitcoin Core might then have to adopt similar rules in order to produce blocks that are safe.

https://en.wikipedia.org/wiki/The_pot_calling_the_kettle_black

2025-05-02T06:01:59Z

In reply to nevent1q…t9aj
_________________________

https://en.wikipedia.org/wiki/The_pot_calling_the_kettle_black

How convenient that you don't have to read anything!

2025-05-01T17:39:57Z

In reply to nevent1q…vgkn
_________________________

How convenient that you don't have to read anything!

Nostr event nevent1qqsws6u67r4v05tswxe4se56hlm9letd7h4erxpeajk56h6fe99ve0czyzrgt6l0vefn3htfx83veheur8vlpedpqe7frrezuuypcf2clra0syhq4zv

2025-05-01T17:24:49Z

quoting
nevent1q…jpg0
The pull request links to a mailinglist post that explains all of this. You're not required to read it, but this "burden of proof" has been more than bet. On the flip side, those who oppose the pull request have not raised a single technically valid argument. And rather than just running Knots, many of them choose to harass developers and frustrate the Github repo.

* met

2025-05-01T17:21:27Z

In reply to nevent1q…cdcc
_________________________

* met

The pull request links to a mailinglist post that explains all of ...

2025-05-01T17:21:11Z

In reply to nevent1q…y8qw
_________________________

The pull request links to a mailinglist post that explains all of this. You're not required to read it, but this "burden of proof" has been more than bet. On the flip side, those who oppose the pull request have not raised a single technically valid argument. And rather than just running Knots, many of them choose to harass developers and frustrate the Github repo.

I also think that if you explore technical solutions that might ...

2025-05-01T13:54:49Z

In reply to nevent1q…l7eg
_________________________

I also think that if you explore technical solutions that might _actually work_ (though also require people to spend their own money), rather than the current and proposed feel good settings, you quickly end up attacking the heart of censorship resistance.
nostr.

quoting
nevent1q…shlf
The most effective way to encourage significant censorship by all miners is to credibly threaten them with reorgs if they include bad things. Needless to say, that would set terrible precedent and probably be the actual end of Bitcoin.
nevent1q…9hdj

I'm happy to give @npub12rv…85vg some artistic license ...

2025-05-01T13:40:56Z

In reply to nevent1q…ps0x
_________________________

I'm happy to give calle (npub12rv…85vg) some artistic license here. It's also worth considering that the people who advocate for filters do not have a clearly articulated position. That includes a lack of clarity about how far they're willing to go. Is the line really at automatic updates? Just because nobody said it out loud? The arguments in favour of filtering seem to vary by who you ask. So that means any attempt at summarising the position can be interpreted as a straw man by someone who has a slightly different position that the other person.

"Life changing" - anonymous person who first learned ...

2025-05-01T12:04:13Z

"Life changing" - anonymous person who first learned about this
https://lornajane.net/posts/2011/navigating-bash-history-with-ctrlr

* before the release is even out

2025-05-01T08:32:32Z

In reply to nevent1q…z2hg
_________________________

* before the release is even out

You can't change consensus on a whim. Standardness filters ...

2025-05-01T08:32:02Z

In reply to nevent1q…hrhw
_________________________

You can't change consensus on a whim. Standardness filters don't work. But even if they did, Bitcoin Core does a release once every six months and people can take years to upgrade. Spammers can adjust because the release is even out. So for all intends and purposes these filters are static.

Now you add a privileged public key to each that accepts new filters in real time. Then they wouldn't be static. And then OFAC asks for the corresponding private key.

Yes please, at least with sigops there's some serious skin in ...

2025-04-30T18:53:30Z

In reply to nevent1q…q2fp
_________________________

Yes please, at least with sigops there's some serious skin in the game if you overestimate your own skill: https://bitcoinexplainedpodcast.com/@nado/episodes/bitcoin-explained-76-stamps-and-the-invalid-block-caused-by-it

Additionally, for each of these topics there is / was at least ...

2025-04-30T18:52:13Z

In reply to nevent1q…39zv
_________________________

Additionally, for each of these topics there is / was at least one well respected developer very fanatic but (imo) misguided about it. That's pretty much the same dynamic as the "blah blah medical doctor says establishment is hiding miracle cure".

Because they're obviously hard to understand, so people are ...

2025-04-30T18:50:12Z

In reply to nevent1q…35ja
_________________________

Because they're obviously hard to understand, so people are reluctant to immediately have strong opinions about it. The problem with things like the block size, op return and RBF is that they're deceptively simple. People don't feel like they need to spend a bunch of time reading up on the topic to form an opinion. Combine that with "influencers" to up the emotional ante and you have a recipe for drama.

It's a very similar dynamic as with bike shedding.

> I don't understand how smart technical people believe ...

2025-04-30T18:38:00Z

In reply to nevent1q…hgka
_________________________

> I don't understand how smart technical people believe [X]

Unfortunately this is completely normal human behaviour (which I don't pretend to be immune for, but I try).

Did you read the mailinglist thread where this was explained? ...

2025-04-30T18:36:28Z

In reply to nevent1q…wq5e
_________________________

Did you read the mailinglist thread where this was explained? https://gnusha.org/pi/bitcoindev/CAAANnUy08NBOq3B++80Rpna2qkD6NJV9RdV9v0Oi8c3G8eq_4g@mail.gmail.com/T/#mb13230a0c1c39b82b74f928791726d6a254063a4

Meant to link to a later post in that thread: #nevent1q…shlf

2025-04-30T18:35:00Z

In reply to nevent1q…ne53
_________________________

Meant to link to a later post in that thread:

quoting nevent1q…shlf
The most effective way to encourage significant censorship by all miners is to credibly threaten them with reorgs if they include bad things. Needless to say, that would set terrible precedent and probably be the actual end of Bitcoin.
nevent1q…9hdj

It's not a strawman. Static content filters do not mitigate ...

2025-04-30T18:33:41Z

In reply to nevent1q…fxap
_________________________

It's not a strawman. Static content filters do not mitigate spam on the blockchain at all.

To continue the police analogy, to reduce spam you need actual deterrence in the form of very serious real cost. Such cost should ideally be imposed on the spammer or on the miner that facilitates the spammer. The former would require KYC. The latter can be done. But be careful what you wish for.

quoting
nevent1q…kzjv
> If development were primarily about choice the developers ought to instead just ship a copy of GCC: there tada, you get all the choices, write your own node. :)

/u/nullc

Jokes aside, it's a good post.
https://old.reddit.com/r/Bitcoin/comments/1kab15o/bitcoin_cores_github_mods_have_been_banning_users/mpou6xb/

Nobody owns the project, you can simply fork it, and enforce your ...

2025-04-30T17:05:00Z

In reply to nevent1q…jld4
_________________________

Nobody owns the project, you can simply fork it, and enforce your own views.

Paid volunteers are a thing. Especially if you consider the ...

2025-04-30T17:03:12Z

In reply to nevent1q…lene
_________________________

Paid volunteers are a thing. Especially if you consider the opportunity cost of not working for Google.

From the point of view of a user it doesn't matter if a developer is working from savings, government welfare, or hired by a benevolent rich Bitcoiner. Users are not customers of the developers. There's no fiduciary duty. They don't get to make demands. You would treat them exactly as you would a volunteer in the more narrow sense of an unpaid volunteer.

The most effective way to encourage significant censorship by all ...

2025-04-30T16:57:24Z

In reply to nevent1q…gq7c
_________________________

The most effective way to encourage significant censorship by all miners is to credibly threaten them with reorgs if they include bad things. Needless to say, that would set terrible precedent and probably be the actual end of Bitcoin.

quoting
nevent1q…9hdj
If you're going to reorg a block because its content is evil, or just doesn't obey your favorite new soft fork rules, please put its hash in a coinbase OP_RETURN of your alternative block.

That proves you saw the block but chose not to accept it. As opposed to just having missed it, as with a typical stale block.

Call it a Bad Uncle block?

You could even do this with weak blocks (reduced proof of work) if all you have is a BitAxe.

Interesting idea, could stimulate people to use Stratum v2 / ...

2025-04-30T16:55:22Z

In reply to nevent1q…sg4l
_________________________

Interesting idea, could stimulate people to use Stratum v2 / DATUM without having to run a fork of Bitcoin Core:

> While discussing this here it does occur to me that there is a different line of compromise which might make more sense-- Bitcoin Core conflates relay policy and mining policy. The historical reason for this is that they should match or vaguely bad things happen. But in case where there is a dispute over policy it makes more sense for mining to be the more restrictive of the two, because the negative effects largely come from miners including txn nodes weren't expecting. So maybe it would make sense to change the option to be one that only changed mining policy. At least as mining policy it has a real effect (assuming you're mining!) -- I'm not sure, this is just an off the cuff thought.

Though this also sounds like an implementation headache, and it's still ultimately a placebo. Since this would only be used by tiny miners, the thing they don't like will go in the next block.

From that same thread: https://www.reddit.com/r/Bitcoin/comments/1kab15o/comment/mprj4tv/?context=3

So is this point from a followup: > Sometimes developers have ...

2025-04-30T16:48:42Z

In reply to nevent1q…hen3
_________________________

So is this point from a followup:

> Sometimes developers have left in options to silence disputes from people in the sense of "look if there is an option it will have no effect because virtually no one will set it, and the people committed to this argument can feel that they won, that they did something, but it's really just a placebo". It's expedient but arguably it's not particularly respectful. Especially in a case like this where even if virtually everyone set the option it still wouldn't have the intended effect.

> If development were primarily about choice the developers ...

2025-04-30T16:42:40Z

> If development were primarily about choice the developers ought to instead just ship a copy of GCC: there tada, you get all the choices, write your own node. :)

/u/nullc

Jokes aside, it's a good post.
https://old.reddit.com/r/Bitcoin/comments/1kab15o/bitcoin_cores_github_mods_have_been_banning_users/mpou6xb/

They're used to their customer bank accounts getting hacked / ...

2025-04-30T14:12:22Z

In reply to nevent1q…f4zn
_________________________

They're used to their customer bank accounts getting hacked / phished that they're just adding this delay by default.

Indeed, and also there's really no need to directly respond ...

2025-04-30T14:09:23Z

In reply to nevent1q…93wh
_________________________

Indeed, and also there's really no need to directly respond to someone who insults you.

Bitcoin users are not paying customers of Bitcoin developers. ...

2025-04-30T14:06:19Z

In reply to nevent1q…t4qx
_________________________

Bitcoin users are not paying customers of Bitcoin developers. It's not the same kind of relationship. As Craig Wright found out.

It's still a volunteer effort in the sense that users are not ...

2025-04-30T14:04:03Z

In reply to nevent1q…mlej
_________________________

It's still a volunteer effort in the sense that users are not paying customers.

Dutch hipster bank #Bunq just added support for buying and ...

2025-04-30T13:53:20Z

Dutch hipster bank #Bunq just added support for buying and selling crypto in collaboration with Kraken. There seems to be no way to withdraw coins, which not even their FAQ seems worth mentioning. It says something about the "crypto" market in general that any company thinks they get away with that.
https://together.bunq.com/d/61673-bunq-crypto

Packs of wolves?

2025-04-30T08:17:53Z

In reply to nevent1q…3yc6
_________________________

Packs of wolves?

Indeed, if you don't have enough inbound liquidity, ...

2025-04-30T08:17:29Z

In reply to nevent1q…wdts
_________________________

Indeed, if you don't have enough inbound liquidity, you're just not spending enough :-)

My first impression of Bitcoin Core, during the blocksize wars, ...

2025-04-30T08:12:52Z

My first impression of Bitcoin Core, during the blocksize wars, was also that of arrogance. It's an unfortunate side-effect of people losing patience when having to re-explain something a hundred times. Time they're not spending on writing code, and energy they're losing to remain motivated to write code.

The project is run by volunteers who do not have time, and should not waste time, for maintaining useless functionality. Having people in the project that are (somewhat) comfortable in delivering such bad news is extremely important. I've been on the receiving end of that too internally.

You do not want Bitcoin Core to be a please-everyone kind of project. That's a recipe for unmaintainable code and really bad bugs down the line.

quoting
nevent1q…na9k
Not sure you guys realize how arrogant, snobbish and elitist this comes across.

"Shut up and dribble you plebs! The Pros will handle this. This is Devs-only business!"

You *will* the support of the user base, if such important changes are just pushed through by a handful of ppl - while other changes (which you may not like) are filibustered for yearz.

And snarly sentiment a la "Good luck with your fork" just confirms this. Disappointing.

Always great when stuff gets merged after two years, especially ...

2025-04-30T08:03:23Z

Always great when stuff gets merged after two years, especially after a few months I tend to forget what my code is doing. Shout out to Daniela Brozzoni for the diagram.

quoting
nevent1q…jsn9
[bitcoin] Merged PR from Sjors (nprofile1qyvhwumn8ghj7mn0wd68ytnnwpex7an0daehgtnwdshsqgyxsh477ejn8rwkjv0zen0ncxwe7rj6zpnujx8j9ecgrsj43786lqyul0f2 (nprofile…l0f2)): validation: log which peer sent us a header https://github.com/bitcoin/bitcoin/pull/27826

Sorry, but it's time to move to bolt12 and BIP352. ...

2025-04-30T07:57:44Z

Sorry, but it's time to move to bolt12 and BIP352.

Ironically since I replaced my self-custodial BTCPay based zap setup to LNBits, I do still rely on LNURL. Happy to try a bolt12 based self-sovereign setup when there's a spec.

Leuk geprobeerd though: ...

2025-04-30T07:10:51Z

Leuk geprobeerd though: https://www.accountancyvanmorgen.nl/2025/04/29/hoge-raad-bevestigt-cryptovaluta-in-box-3/ #box3

You already have the followers, which I suspect any discovery ...

2025-04-29T11:48:07Z

In reply to nevent1q…j5wl
_________________________

You already have the followers, which I suspect any discovery algorithm takes into account.

What makes you believe that your success on Twitter is due to ...

2025-04-29T11:23:39Z

In reply to nevent1q…kwjn
_________________________

What makes you believe that your success on Twitter is due to their discovery algorithm? And which version of it? Maybe you just got lucky there, or as others point out, put in more (audience targeted) effort and time.

Speaking of frequent sources of drama that deter many people from ...

2025-04-29T11:19:27Z

In reply to nevent1q…e7zp
_________________________

Speaking of frequent sources of drama that deter many people from seriously looking at these proposals.

My main concern with moderation is that it can drag culture war ...

2025-04-29T11:17:38Z

In reply to nevent1q…dulq
_________________________

My main concern with moderation is that it can drag culture war stuff into a project. But I think the moderation process is transparent enough to keep an eye on that.

Still need to decide if I'm going to do Drama Mondays and not go anywhere this stuff on other days. Like today.

> without warning/notice The whole thread was full of ...

2025-04-29T11:13:25Z

In reply to nevent1q…3nl7
_________________________

> without warning/notice

The whole thread was full of warnings. Warnings don't have to be individually tailored. Moderators are often developers too and have better things to do with their time than to give a non-contributor extreme benefit of doubt. Or even to have rigorous due process. Every second these people have to waste on this nonsense is time they're not fixing the next CVE.

Do you really want to play the censorship victim card? ...

2025-04-29T08:54:10Z

Do you really want to play the censorship victim card?
https://www.reddit.com/r/btc/comments/1cpavfc/roger_ver_fights_against_censorship_and_believes/

* The former requires broad consensus

2025-04-29T08:40:50Z

In reply to nevent1q…hjes
_________________________

* The former requires broad consensus

Citrea is much further along than a whitepaper. The limits were ...

2025-04-29T08:39:14Z

In reply to nevent1q…39h4
_________________________

Citrea is much further along than a whitepaper.

The limits were on the verge of being dropped two years ago because inscriptions made them useless. That change was only held back by the argument that there's a small range of sizes where OP_RETURN is cheaper.

That was never a strong argument, so yes, a single example like Citrea was plenty to dismiss that last remaining argument.

I explained all that in my mailinglist post, feel free to read it.

Consensus changes like CTV is totally different from standardness. The latter requires broad consensus, because the consequence of inconsistent enforcement are catastrophic, etc.

Modetating harassers is perfectly legitimate. His concern about a conflict of interest was absolutely spurious here. It's also been stated multiple times that discussions about standardness should be had on the mailinglist, not in the pull request.

Pretending to be a censorship victim is the oldest trick in the book.

And specifically to Nostr, discoverability is quite low. Not as ...

2025-04-29T08:13:58Z

In reply to nevent1q…k88h
_________________________

And specifically to Nostr, discoverability is quite low. Not as bad as with podcasts though :-)

Cross-posting without tailoring to the platform often doesn't ...

2025-04-29T08:12:17Z

In reply to nevent1q…n2jr
_________________________

Cross-posting without tailoring to the platform often doesn't work well. Someone might be big on Youtube and non-existent on X.

Give the man more followers! #note1kph…ltt8

2025-04-29T08:09:40Z

Give the man more followers!

quoting
note1kph…ltt8
NOSTR really sucks for me.

Sorry, I should have split that reply. The first part was an ...

2025-04-29T08:06:43Z

In reply to nevent1q…sfgm
_________________________

Sorry, I should have split that reply. The first part was an answer to your question, the last bit referred to Bitcoin Mechanic, who should know better which forums are appropriate for which concerns.

Unless those leaked nudes are on the blockchain :-(

2025-04-29T08:04:08Z

In reply to nevent1q…3gu2
_________________________

Unless those leaked nudes are on the blockchain :-(