pull down to refresh

Dear developers who work on Bitcoin.
No.
Thank you, with Love.
But No.
This is the default frame of Bitcoin node runners. And it should be.
The burden of proof is on you to make clear your case for your proposed feature. If that feature requires a change in consensus rules, you have good faith work to do.
If you do not make clear the specific benefits of your feature,
If you do not make clear the specific cost(s) of your feature,
If you whine about covert social contracts being violated,
If you make bad arguments,
If you engage in trolling,
If you engage in bad faith,
If you conflate, if you gaslight, if you lie,
If you play dumb to avoid the truth,
If you misrepresent opposing arguments,
If you gloss over the true cost of your feature,
If you hide the true purpose of your feature,
If you compromise Bitcoin,
Then you have earned that “No.”
Nothing more, nothing less. Just a simple No.
The default answer was already No, but now you’ve earned it by satisfying any one of the above conditions.
We appreciate you, we love you for maintaining this walled garden of freedom and hope.
But we will not submit what Bitcoin needs to your wants.
Thank you for enduring. We know it’s not easy, but you can handle this.
So act in good faith, Be worthy of a Yes... Few Are.
To the Bitcoin Miners. There is zero appetite for any kind of softfork at this time. Let alone a Miner Activated Soft Fork. Indeed the sentiment for a Miner Activated Softfork is extremely negative in principle at this time, given recent events surrounding taproot activation and related consequences.
If you want to fuck around with a Miner Activated Softfork at this time, you will find out, in more ways then one.
To the Bitcoin Community at large, Run a Node. Learn what that means and it’s implications for you and the Bitcoin network at large.
No one is in control of the Bitcoin Network. But node runners can have a say.
Be one.
Have a say.
Exercise your logos. Run Bitcoin.
What about if you have raised millions from shitcoin VCs that you're protecting? What do you say to those people that try to change Core?
reply
I Say, Not On My Node.
reply
You mean like blockstream ?
reply
"Exercise your logos. Run Bitcoin." Well said, it's so simple yet so profound.
reply
Dear Users,
Yes.
You're Welcome, so Yes.
Your counter arguments have exhausted rationality.
Eat Crow.
Taproot and Ordinal consequences, are exactly why we need one small change so that future changes are not left up a central priesthood of devs with limited neurons, but instead chosen by the consumer, with effects isolated to the consumer.
Core stays the same, the original rules we all chose to play by, stay the same. POW, stays the same, Supply remains intact, which is quite conservative compared to what some of those in your camp are asking for with tail emissions.
There is no "users" or "we" there is only a "user", an individual.
The free market will always be more powerful than a planned economy, which is what we have now with a few interested and funded companies dictating the future of bitcoin on a censored platform like twitter.
A corporate fascist bitcoin. Cyber-Punk instead of Cypher-Punk. A theocracy of Brahmin that must be placated in a forum dominated by biased caste members. A college of bishops burning white or black smoke, ACKS, signaling where bitcoin can go and what it can do.
Or worse, changes must launch a political campaign to convince the mob. Democracy. Democracy has a long and studied history of predictable shortcomings and weakenesses. Democratic money, your node vote, will over time vote itself new supply.
Bring on alternatives; ARK, PRIME & Radiant and RGB, spider this or space that. “We” like them, we want them, but they are, after years, either codeless concepts or impractical and custodial. They are catch-up solutions to innovations and desirable features already executed on other networks.
Intitutional and national Dominance is around the corner. We don't have time anymore.
One small change, the addition of ** a single OP code ** enables innovation to happen on Bitcoin L2 without endangering L1. L2 affects are isolated. You never have to participate, but you benefit from a more secure network with broader and more encompassing userbase. These changes are OPT-IN, the way movie selection on a plane is user chosen, but we all arrive at the same destination.
Consider that you might be the recipient of a well funded marketing campaign by certain companies, devs and influencers who stand to lose a lot of money and time in research made irrelevant by the "more freedom" option. Their stance is explicitly that relying on state legal institutions for trusting your bitcoin is "better". Not very cypherpunk.
No one wants a contentious SF or MASF. "We" would rather your opposing arguments were original and legitimate. "We" would rather your were right, that this is a new dangerous idea by forces trying to harm Bitcoin, rather than an old and tested idea, with enormous amounts of documentation, software and actionable use cases.
Worthy of a Yes, and has been for years.
reply
No. Thank you.
reply
I don't know enough about this issue to have an opinion (I try to not opine when I don't know wtf I'm talking about) but this was a nice return of serve.
reply
Miners are pushing for an MASF ?
I must have been staring out the window again, cos i've missed this bit of gossip.
reply
devs are pushing for a MASF, miners just go along with it, hence the appeal for them to be aware and switch pool affiliation to reflect their choice.
some of them are more cavalier and borderline malicious though.
reply
Likewise.....
reply
reply
reply
Lets Gooooo!
reply
Well said. I think in the future the pressures to both soft and hard fork will be immense. Imagine the block size wars but with the full weight of Blackrock, Chase, the rest of Wall St, and the corporate/govt propaganda machine (aka mainstream media) behind it. They will lean on both devs and miners very hard to get what they want. It will be up to the pleb node runners to defend bitcoin.
reply
Yes to this post, and no to what changes I will make to my node
reply
deleted by author
reply