Nostr Web Client

Thanks for engaging too! Like I said, we want the same thing.

I also know what it's like to be scared for Bitcoin's future, because I lived through the block size war when it genuinely felt like bitcoin was headed towards its end. Then I spent all my free time following Craig Wright back when there seemed to be a chance he could actually win and make bitcoin development all but illegal.

The fear and upset are real, because self-sovereign money is so important. We have this chance, and we must protect bitcoin at all cost.

But with respect, you're overreacting in this case, and you're in good company, because this is being encouraged by certain people.

I'm just a stranger on the internet, but I can tell you this with great conviction: if bitcoin goes bad, it will not be because of any changes Core makes to its OP_RETURN policy.

FernandoTheKoala 7mo ago 💬 1

lol I love how our engagament has evolved!

Thanks for recognizing and reasurring a "younger" bitcoiner in distress, much appreciated man

I do hope me and others are overreacting over nothing, but I think the reason why this thing got so many ppl (who don't get the tech 100%) uneasy is the fact that some things (which have nothing to do with tecnhical aspects) stink.... I'm referring to:

- PR being locked, then unlocked to let someone submit ACK, then locked again

- ppl paid to submit PR withouth disclosing it upfront

- the focus being on miners wellbeing rather than nodes

- core smirking at oppostion during btc++ debate

- core devs saying things like "if you don't like what we are doing just change software", instead of reassuring ppl when they express concern for what you are doing

I don't know man, I do hope I am the retard here and my impressions are totally wrong. But anyway like many said, in the end this whole debate is good because it has fostered engagement and highlighted some issues to work on

Reply to this note

Please Login to reply.

Discussion

f0a8bcfd... 7mo ago 💬 1

> - PR being locked, then unlocked to let someone submit ACK, then locked again

This wasn't handled well, but a PR isn't a battleground for non-contributors to go in and say "NACK" in large numbers and then expect their comments to be tallied as a vote. It needed to be handled in some way.

> - ppl paid to submit PR withouth disclosing it upfront

This is influencer propaganda. We should be thankful that many talented people are able to collect a salary for their work. There is no ill intention – that's just something influencers want you to believe in order to make you angry.

> - the focus being on miners wellbeing rather than nodes

The focus is on bitcoin's well-being. Bloating the UTXO set dangerously impacts the cost of running a node, OP_RETURN avoids this cost. You may think you can avoid or reduce undesired data in the blockchain, but this is demonstrably wrong (look at the blocks you're storing). You can choose between bloating the UTXO set and not bloating the UTXO set.

> - core smirking at oppostion during btc++ debate

I'm sorry you found someone's demeanor offensive. That's not a technical argument. A smirk is bad, but probably not as bad as the accusations of corruption and hidden agendas that a lot of bitcoin developers face these days. This person shouldn't have smirked, but this gesture probably didn't come out of nowhere; people are upset and frustrated.

> - core devs saying things like "if you don't like what we are doing just change software", instead of reassuring ppl when they express concern for what you are doing

It's difficult to communicate effectively. I thought Greg Maxwell did a decent job here: nevent1qqsgsc3lfarzl6sjrnrewxxl88fme3ztewhrtf4tp5u56l7uhuxzdmcr9hwpf

People are complex and difficult. When it comes to bitcoin, we need to focus on technical arguments to protect bitcoin's decentralization, and not choose our actions based on who has offended us.

FernandoTheKoala 7mo ago 💬 1

On the "offending topic" and ppl being complex, I understand that devs are way better at coding and technical aspects, rather than communication. But you gotta admit that when someone is pretty shit at comunicating it has its impact (quite hard to completely discern the technical content from the way it is presented). Maybe core devs should also dedicate some time on how to better convey info, because it is a very imprtant aspect too

Anyway thanks a lot for your time man, I'm re-considering my stance here. As already mentioned I'm very emotionally invested in this and my emotions might have clouded my judgement initially!

Last question to you: if it turns out this change creates harmful consequences, can we simply roll it back withouth any issue? In this case the only way to roll it back would be through consensus change, correct? I'm all for experimenting to see what works best, but it is pretty hammered in my head that any change to btc is risky and should be heavily weighted as it might generated unforseen consequences

f0a8bcfd... 7mo ago 💬 1

Bitcoin's developers have long been criticized for not being the best communicators. You should have seen how it was when we tried to get SegWit activated. Eventually they published a pretty good FAQ. Later we got the OpTech newsletter etc. It's a lot better today compared to then, but it's probably not good enough. Developer time is scarce, and it would be nice to let them just work instead of becoming expert communicators able to convey nuanced technical concepts to regular people.

> if it turns out this change creates harmful consequences, can we simply roll it back withouth any issue?

Yes, it's just a mempool policy thing. Rolling back a mempool policy change does not involve a consensus change, just a new software release with adjusted mempool policy, and then encourage people to switch to it.

That said, this stuff is very well understood by now (we literally had the first OP_RETURN war in 2014, not much is new) – there isn't really any risk of harm.

FernandoTheKoala 7mo ago 💬 1

I can understand your point about letting devs code and not having to convey their decisions, but I don't think this approach is feasible (so ppl should blindly trust what few devs do withouth any explanation?). Also I don't believe it is a 100% technical question only, like in all things there are more factors at play.

On this note I did some more thinking and what still puzzles me is this:

1) it seems the only way to stop spams is to change what a valid transaction is at the consensus level. This was discussed in the past (2 years ago PR was submitted if I am correct) but it was rejected as "controversial". But the PR that was just pushed now in a hurry (remove filters) is also clearly controversial. So why does it work in one way but not the other? And why have we given up dicussing it at the consensus level?

2) I don't understand why we are so worried about fees for miners, isn't the block reward more than enough for a few years? is any miner going to stop mining because the fees are too low now? Also, I thought the difficulty adjustment was there to self-regulate the mining ecosystem, why are we now intervening to give miners bigger fees?

3) Hypothetically, let's say that with this core 29v it does happens that spam transaction fill blocks and drive up fees, making it harder and more expensive for monmey transactions to get in. At this point will core "rewind" and reinstate the filter or discuss change at consensus level? Because from their statements it seems that in this case their stance would be "oh well btc is a database for whatever the market wants it to be, so if it is for jpeg and spamsn then let it be it"

Cheers

f0a8bcfd... 7mo ago

> I can understand your point about letting devs code and not having to convey their decisions, but I don't think this approach is feasible (so ppl should blindly trust what few devs do withouth any explanation?)

I didn't say that at all. Developers do debate and explain, but my understanding was that you cannot find explanations that are understandable to you. I was saying explaining nuanced technical matters in a way that is understandable to someone without a sufficient technical understanding is difficult.

I don't mean to be rude, but I can't spend a lot more time on this right now, and we seem to be going in circles where I thought we were maybe reaching some sort of amicable end. Thanks for the exchange, but I'll cut it off here, and wish you well.

There is a nice and relatively accessible compilation of questions and answers here which you may find useful: https://stacker.news/items/978404

As a final word: please do not assume bad faith among bitcoin developers. They keep bitcoin working for us but it can be grueling work, especially when they have to face horrible accusations from social media.