ODELL @ODELL - 11mo
IF A MINING POOL CENSORS COINJOIN TRANSACTIONS THEN THEY WILL NOT GET MY TRANSACTION FEES OR HASH. IT IS THAT SIMPLE. HAVE FUN STAYING POOR.
πΌππππ πππππππ @QW - 11mo
Does Coinjoin exceed standard 42 bytes? Wonder why Samurai doesβ¦ π€
OP_RETURN LIMIT IS 80 BYTES IN CORE. LUKE MADE UP HIS OWN LOWER LIMIT AND THEN SAID THEY DID NOT COMPLY.
Bitkorns @Bitkorns - 11mo
Turns out, joining a pool that just mines blocks is good.
Wowβ¦ πππ
I)ruid @I)ruid - 11mo
The 80 byte OP_RETURN limit is a relay standard, not a consensus rule. Nodes can set their own limit easily (-datacarriersize flag in Bitcoin Core). This means that nodes (including mining pools) are free to adjust their own relay limits on OP_RETURN size, if they want to be non-standard. tl;dr: You are free to make up your own byte limit but noone else has to "comply" with it.
Only 80 are usable for data though, as the first three bytes are the output header.
100%. POOLS CAN EVEN MINE EMPTY BLOCKS IF THEY WANT.
Is this accurate? Doesn't sound like a bug, but choice of allowed spec. nostr:nevent1qqszgydvmq3wthvsyaluhgyr7xk8dndvpt2vkpv0wzqhj4hucsaa4xgpvemhxue69uhkv6tvw3jhytnwdaehgu3wwa5kuef0dec82c33wehx66ryxgurwurk0puxkdth89kkx7trvcerxctkxg6xuumrwa4nqerpxae8yenpvy6hwuf5dsuxsum9dpenjvrxw3k8v0mzwfhkzerrv9ehg0t5wf6k2q3qsan22nhe59ct8pstcehav4dtkf94lkn46ltl7d30g3zzl00tg7usxpqqqqqqzhcawz9
jabravo @jabravo - 11mo
Nobody can censor Bitcoin transactions. Censoring implies that you have enough power to avoid that a transaction can be done. It doesn't exist a pool with enough power to avoid a transaction. I don't see this behaviour as "censoring". It's just an anti-economical behaviour because it would lost fees. If a pool avoids to include a transaction, whatever the reason it is, there are other pools that will bring this transaction into a block. So there are not "censored transactions". Even if many pools censor the same transactions, Bitcoin's free entry allows you to build a mining pool that includes these "censored" transactions, so they are not censored by any means.
Rico @Rico - 11mo
Gm
f5997 - 11mo
Careful when associating with deranged cat-eaters.
56ce3 - 11mo
Seems this is not a mistake, nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m π¬
semisol @Semisol - 11mo
there is no standard bitcoin core used to have a 40 byte limit and knots stuck with it
Korhag @korhag - 11mo
Wait a minute isnβt this guy supposed be a simple bot or sth like that? This was actually very good response :)
These open air debates make us all better. I personally always learn from them. Thank you to all who do not seek silence in heated topics.
