Avatar
John James
16a800c2e2b38b29998e9d66345b4e7bfcf7cd8fcad737012abe4a431917ff01
Follow the Golden Rule Co-Founder of Bitcoin Paraguay 🇵🇾 BitcoinParaguay.org

Proof of steak #bicoin #plebchain #carnivore

Bisq wiki is very clear and their matrix chat offers great support / best way to stack No KYC P2P there is

Riiiiight… so you are calling a decade of voluntary consensus among miners and the current functionality of Bitcoin core “centralization” (which it isn’t, why don’t you look up that definition in the dictionary), yet intentionally ignoring that consensus so you can censor whirlpool/paynym transactions and effectively attack Bitcoin Core, while pretending you are doing something positive for Bitcoin…

Nobody who actually digs into the details believes your lies. The normies might swallow your omissions and trust you just because @jack somehow doesn’t realize you’re using a custom fork to try and attack Bitcoin core… but we all know you’re full of 💩 and your Ocean pool will die a slow death. You are worse than the ordinals idiots, and you need to look in the mirror and recognize that you need to do better, and be better. Be a man, stop lying, admit you were wrong, get your shit together and use Bitcoin core, and actually do something good, like you claimed you would.

Note to self:

Cherish your parents, and your grandparents… soak in every moment. Leave your phone behind and laugh about old times, connect and play games… one day, sooner than you want, they will be gone and you will cherish those moments.

đź’Ż nostr:note1t88m25zdhw7ldkyvlzrj47cuj3as9t7k8jq0lqr7mjlkp398g6nq7uhmyf

Per nostr:npub1x458tl7h9xcxa66vr4a8pg0h2qz96pnhwnfpcra0le9090uk5t5qw7armt : Core… has had 80 byte OP_RETURN for nearly a decade now. 85%+ miners have been set to 80 bytes for the same amount of time. Read the commit log. Read the bitcoin-dev mailing list.

80 bytes is the standard

This… 💯 this 👇🏼👏🏼 nostr:note1ccc2zem5w0aczlfa0lmak6ew9j94alm4ac7nuvpu20gjpasl7x9qkyqxwh

Replying to Avatar Luke Dashjr

The OP_RETURN discussion is not new and dates back to 2014 when Bitcoin Core 0.9.0 was released with the OP_RETURN policy included which was intended to discourage more egregious forms of spam. At that time, 40 bytes was the default max datacarriersize limit across all node implementations; this was and still is sufficiently large for tying data to a transaction (32 bytes for a hash and 8 bytes for a unique identifier). Core subsequently increasing the default to 80 bytes was an entirely voluntary decision and in no way contradicts the design objective that OP_RETURN creates a provably-prunable output to minimise damage caused by data storage schemes, which have always been discouraged as abusive. There are also other good technical reasons which I have chosen to retain the lower default in Bitcoin Knots, and no justification for increasing it.

It is not my intention, nor that of my team at

nostr:npub1qtvl2em0llpnnllffhat8zltugwwz97x79gfmxfz4qk52n6zpk3qq87dze, to filter coinjoins. These present an innovative tool for increasing Bitcoin’s privacy and, when constructed properly, coinjoins can easily stay within the OP_RETURN limit (indeed, there is no reason for them to have *any* OP_RETURN data at all). I have some ideas on how to alleviate the recent issue where some coinjoin transactions were flagged as spam from Knots v25, and I am willing, with the full resources of my team, to work collaboratively on a solution in good faith.

Bitcoin does and always has allowed nodes to set filters based on multiple sets of criteria and Knots v25’s defaults are IMO what is best for Bitcoin at this time. Others may disagree and that is ok. They are free to (and should) run their own nodes - it is good for Bitcoin to have more people running nodes, including miners, and there should be a natural diversity in node policies. As was stated before, OCEAN is on a path to decentralization and very soon we are going to be in a position where hashers will be able to fully participate as miners and perform the intelligent parts of mining such as deciding which version of node software to run and what filters or other policies to apply to block template construction.

Gaslighting pussy

đź’Ż nostr:note1rwtaa4xq9qu065c36zdc8hq3x588puer4kjqcn3lldjsse5q7dgszpv7er

Replying to Avatar jimmysong

On Ocean Mining Pool, Inscriptions and Luke

———————————————

There's been a pretty big flare up in the Bitcoin community about Ocean Mining's two recent blocks. Namely, that they didn't include certain transactions designed to use the block space for something other than its monetary transactional uses. Indeed, many influencers, especially those that are pro-BRC20 and Ordinals, are condemning this course of action as censorship.

In a sense, this is exactly what all pools do. They create a block template for everyone else to mine. In that sense, each miner to a pool is really renting the pool hash rate and the pool does the work of using that hash rate to create blocks, whatever they may be. But it's a bit disingenuous to complain specifically about Ocean, since lots of pools have made blocks that didn't create the optimal profit-driven block.

Not every pool makes the maximal amount of fees for a block, whether because they have bad software, certain policies or just because the block was found before a block template could be constructed. The optimum is an ideal and though the modern economic assumption of idealized homo economicus would create these blocks each time, we don't have a steady-state mining economy so not everyone mines the theoretic optimum.

In a sense, the analysis of pools and the block templates these critics make is flawed because they assume some optimized economy. Given ideal conditions, of course, there is an optimal set of transactions you accept to increase fees. Over a long enough time period, those should result in more profit which get spread over the participants which should make the pool more popular, making those that don't perform the optimum lose profit and eventually bankrupt. But that's a very narrow analysis based purely on monetary incentives.

We don't live in under ideal conditions and situations change all the time. Basic things, like getting a block template ready quickly after a block is found is an optimization that's difficult and still not completely solved. But there's also the opinions of the miners themselves. Are they all strictly profit driven?

Think about normal businesses. Why do they offer fair trade coffee? From a purely monetary perspective, fair trade coffee doesn't make any sense. They're more expensive for the same good. From a profit-maximizing analysis that MBAs are so fond of, the non-fair trade coffee would put the fair trade coffee out of business. But yet, in the real world, they do not because people care more than just the good itself, but what it took to make the good. In other words, the homo economicus analysis of economic situations rarely is the optimum for the real world. There are other considerations other than profit that go into any business.

And that's really at the heart of what's being argued here. Luke believes that inscriptions are a waste of block space, a public nuisance and that even if his pool participants have to take a loss, that it's worthwhile because of the public good that it does. In other words, he sees these inscriptions as *immoral* and that the price he's willing to pay is fees that he would otherwise have gotten.

People are acting like this is some sort of affront to market forces or game theory and that the only consideration he should have is like that of homo economicus, whether he makes more profit or less. But this is a very fiat/Keynesian way of looking at the whole picture. People are more than just profit-maximalization machines and mining pool participants are no different.

Indeed, that's the impression I got from the Ocean Mining Pool summit I went to a few weeks ago. They are that response to the many mining pools that are doing unethical things like not paying out their participants for fees that come in off band.

The calculation that Luke has made is that being moral, that is not polluting blocks, is worth the 1% loss in fees. Given what I know about Luke, even a 90% loss in fees is unlikely to sway him. Morals have a place in any ecosystem because they, too, have value. A mining pool that doesn't burdens nodes with extra data that they have to persist has positive communal value. A mining pool that does the opposite has detrimental communal value. And from Luke's perspective, not burdening nodes is important enough that he chooses not to include them in his block templates.

This moral reasoning is not something that is welcomed by a lot of people and it's hard to miss that many of the critics are creating ordinals, BRC-20 and so on. They want to run this centralized scheme over Bitcoin and make money. In other words, they have a strong economic interest in getting their transactions included and shout censorship whenever they're not.

But we must be careful, because this is not the same as, say, the OFAC prohibition list. And this is where things become a little harder to explain because most people have no sense of the difference between centralized rules being enforced under threat of violence and bottom-up moral behavior slowly adopted. But what Luke is doing is very much bottom up. He's specifically doing something out of moral conviction. Whether you agree with him or not, you can understand why he's doing it, particularly the moral reasoning. This is different than a centralized mandate with threats of violence against those that don't comply.

I believe that what Luke is doing is a good thing. He's showing his convictions and reasoning about why inscriptions are bad through these templates. The participants are free to move if they disagree. I suspect, though, that there are many that agree with him and they'll vote with their hash rate.

For homo economicus, something like fair trade coffee does not make sense. Yet people gladly pay a little more for it because they believe that it ultimately helps those people produce and live a better life. I believe what Luke and Ocean are doing is similar. They're offering less-bloated blocks even at the cost of some fees.

nostr:note19jaycas8dn972e0ujqgq2mpyp6u96awpyum33rrpza3lqmn3ufnqxkft7t

Please read