Nostr View

π•Όπ–šπ–Žπ–Šπ–™ π–‚π–†π–—π–—π–Žπ–”π–— @QW - 1y

Does Coinjoin exceed standard 42 bytes? Wonder why Samurai does… πŸ€”

0
0
0

ODELL @ODELL - 1y

OP_RETURN LIMIT IS 80 BYTES IN CORE. LUKE MADE UP HIS OWN LOWER LIMIT AND THEN SAID THEY DID NOT COMPLY.

0
0
0

π•Όπ–šπ–Žπ–Šπ–™ π–‚π–†π–—π–—π–Žπ–”π–— @QW - 1y

Wow… πŸ˜‚πŸ˜‚πŸ˜‚

0
0
0

I)ruid @I)ruid - 1y

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.

0
0
0

56ce3 - 1y

Seems this is not a mistake, nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m 😬

0
0
0

semisol @semisol - 1y

there is no standard bitcoin core used to have a 40 byte limit and knots stuck with it

0
0
0

π•Όπ–šπ–Žπ–Šπ–™ π–‚π–†π–—π–—π–Žπ–”π–— @QW - 1y

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.

0
0
0
Showing page 1 of 1 pages