pull down to refresh

293 sats \ 0 replies \ @anon 9 Jun
This PR, replacing #32359, doesn’t remove the -datacarrier or -datacarriersize options. Contrary to what many are saying, the PR does not force the user to accept larger datacarrier transactions in transaction relay. Setting -datacarrier=0 still turns it off, and -datacarriersize=83 gives you the original default (the same amount of data but across 1 or more outputs).
reply
2351 sats \ 3 replies \ @petertodd 9 Jun
Finally we can spend our energies on something that worthwhile.
That was the dumbest controversy since full-rbf. Maybe dumber.
reply
Mr "we need to finance miners" spamrelay has spoken.
reply
But do you think we still need a better way to fight spam on the network?
reply
The 8 billion people wanting and needing to use Bitcoin... fit within 4mb/1mb of transaction data is the ultimate 'filter'. You want to use it you pay.
reply
Those shitcoiners will not be around in a few years while Bitcoiners will march on.
reply
We will see Bitcoin Core's real motivation in a few months, or maybe even sooner. Stay vigilant.
reply
Their 'motivation' is to create the most technically sound, ethically sound, economically sound monetary network possible given the technical limitations.
reply
Sure, buddy.
On a completely different subject, do you want to buy a bridge that just became available? It's a golden opportunity.
reply
Where is the 'spam' in this block?
This is ALL the "data" (op_return inscriptions bare multisig everything)
And this is all the 'inscriptions'
They are gone 99% among 8 billion people.
Don't let 'influencers' spoil you brain and tell you what to think. Think for yourself
reply
Just wait and see, buddy.
reply
You clearly don't understand the technical nuance of the discussion then. Larger op_returns would actually make blocks smaller, and arguably easier to relay.
deleted by author
3051 sats \ 0 replies \ @LibreHans 9 Jun
A sad day. "Bitcoin, not crypto" has no meaning any more.
reply