Replying to Avatar vnprc

Ocean does a lot of things different from most miners. They use PPLNS (tweaked and renamed TIDES) which makes payouts transparent and fair. You can mine directly to a bitcoin address (no account, no kyc).

Everybody is angry about censoring inscriptions. Big whoop, who cares? Y'all don't even like inscriptions.

I am genuinely confused by the coinjoin censoring. Why does whirlpool need an 80 byte op_return? (Apparently they don't.) Why does knots censor it? (Luke just stonewalls everyone on this point.) Seems like dumb decisions all around.

Overall, a kyc free mining pool with fair and transparent payouts is a massive win. Everybody else uses PPS which reduces miner payout variance and gives the pool full control over blocks and profits. Censorship is a big problem if all pools censor the same stuff. If they all censor different stuff it is not really a problem. Ocean is a net positive. With Sv2 the censorship will be a non issue.
Avatar
Luke Dashjr 2y ago

The standard datacarriersize Knots has always used is 42 bytes. They knew that and ignored it. We haven't changed anything in this regard.

Brc20 comes in at 45 bytes, so just increasing it isn't a viable solution. That doesn't mean we're giving up - we do want to mine these - but it's going to take some work if Samourai doesn't fix the issue on their end (ultimately there's no good reason for ANY of this data)

Reply to this note

Please Login to reply.

Discussion

Avatar
vnprc 2y ago

Thanks for the response. I am not knowledgeable about datacarriersize. Does this refer to a constant in bitcoind code? Does it only apply to OP_RETURN?

I was under the impression that BRC-20 uses the inscription data envelope technique, which does not involve OP_RETURN. That makes me think you are using datacarriersize to refer to the total amount of data you are willing to allow a transaction to store, regardless of the technique used. Can you please clarify this for me?