Cheap again. Picking out the easy notes to reply to. You're not obligated to reply. But if you're going to, try replying to the matter at hand. Not that I have high expectations.
We can try here if the matter at hand isn't clear for you.
Does it live up to your responsibility as a core developer to advocate for - and push through - a highly controversial change to bitcoin core, if the usecase for that change is an extreme edge case?
I'm not a Core developer, I'm co-founder and Chief Security Officer of a self custody company.
I have the same rights and responsibilities as any Bitcoin user to advocate for whatever I damn well please.
Go flash your rights somewhere else, whats within your rights isn't always whats the right thing to do.
Again cheap answers. Well, "answers".
It's a yes or no question, but avoidance is what's keeping your own sanity alive.
Don't answer me, i have zero expectations. Answer yourself though!!
Does it live up to your responsibility to advocate for a change in bitcoin core that serves - in your own damn words - an extreme edge case?
Yes, it does. You have to be extremely deep in the weeds to understand highly nuanced issues such as this.
And I am by no means deeply into the weeds of the op_return issue.
I do however understand that we need to be EXTREMELY careful when making changes to a bitcoin implementation that is so widely used -- AND I also understand that supporting bitcoin core changes to help "extreme edge cases", given the above point of extreme care, just doesn't compute.
So, based on your own words in video above - I disagree with you, in that it lives up to your responsibility as whatever person in bitcoin you are (of higher than average importance) to support such a change.
Remember! My disagreement here is based 👏 on 👏 your 👏 own 👏 words 👏 PLUS the idea that changes to bitcoin core should be taken with EXTREME CARE.
Your disagreement is noted and hereby discarded since you clearly can't comprehend how it's possible to be quite careful with software changes while handling edge cases.
Says the man positioned to profit from the changes.
—BITCOIN IS NOT YOURS TO FUCK WITH—
Do you even hear yourself?
If you develop an open source calculator and make "software changes" that carefully consider edge cases, sure.
When talking about the future of money, i think throwing that in under trivial "software changes" depicts your disrespect for the project you're influencing changes on.
Its simply too risky to implement changes, so we avoid it unless the benefits are extremely obvious and the risks have been studied deeply.
Do you run a node or not?
After learning how Bitcoin actually works now I will only take opinions of people who run their own nodes seriously.
Everyone else is just talking shit.
Show us your node running on core30 or are you a hypocrite?
What kind of ignorant bot are you?
I've been maintaining my own fork of Bitcoin Core for a decade and published innumerable tweets and essays about running nodes.
Look at the release notes for v30 and you'll find my name.
Merit and logic is gone from Core. Majority of Core devs are compromised and are just cucks to shitcoiners and VCs like Jameson Lopp.
We have seen Core's so called "arguments" and we have seen their actions.
shouldn't we consider every case, no matter how "extreme edge" it is?
Thinking that Jameson Lopp is a core developer shows you are clueless.
I actually thought Lopp was a core contributor. I disagree that being mistaken on that voids my point in this thread.
Completely irrelevant to the points being made.
He’s a highly influential personality in the space.
He absolutely contributes time, money and influence on the topic at hand.
It’s just another dishonest take and more evidence of his dishonest character.
It voids any contributions you have on the topic. It shows you have not done *any* homework and have no idea.
Precision is important.
A "Core Developer" is someone who consistently contributes to Core, generally as their primary occupation.
A "Core Contributor" is anyone who has ever made a code contribution to the repository.
I average one trivial code contribution per year. I'm a contributor but by no means a developer.
