đź’Ż best wallet in existence
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
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

