Dojo been banning knots peers since that time. Nothing new, ocean known this since long before this drama. Today is amplified like never before but nothing changed. And v30 did not change op_return its all propaganda from ocean team

Once again hard -> money <- one cannot fuck with The OP_RETURN size remained unchanged; it was the default relay policy that changed in v30. Therefore adjusting relay policy does not constitute a structural network change because relay policy is a locally enforced preference and has no impact on network-wide behavior proof subsat summer to this day understand that core seeks to synchronize relay policies with consensus rules to maintain node efficiency, as it recognizes that economic incentives and consensus ultimately drive network behavior Here https://bitcoincore.org/en/2025/06/06/relay-statement/ published June 6,2025 read the blog post where everything is explained and stop listening to propaganda by Ocean team

When Ashigaru.rs in the Zapstore?

You said it yourself still need to trust wasabi

Sure but wasabi was not any better this 6 years old fud was debunked use your own node and users knew when they were using sw infrastructure that using someone’s else’s node not their own node have risks. For a light client trade offs were disclosed but in reality One didnt need anything else by their mobile wallet.

Monero already have stealth addresses Sure use it why not? SW devs who are still in jail serving time making Bitcoin like it supposed to be private and based on probabilities and not deterministic when spending Privacy of monero suppose to be by default on Bitcoin oh well this is the nature of Homo sapiens

BIP47 is primarily designed for entities handling repeated payments to and from counterparties—think exchanges, mining pools, salary-paying companies, merchants, and the like. Targeting these players makes perfect sense, as they're now the biggest culprits behind address reuse, which erodes privacy for the entire Bitcoin ecosystem. Silent Payments (SP), by contrast, aren't a superior alternative; they simply don't aim at the same high-impact users or problems. Although one does not require notification txn if both parties are online and actively interacting synchronous P2P via Soroban. https://medium.com/samourai-wallet/wallet-update-0-99-96-introducing-soroban-adc9a36a7ddb A standout feature of BIP47 is its notification transaction, which eliminates the need for synchronous communication between parties. It seamlessly conveys the sender's identity while serving as a key backup for the receiver—all without relying on any server infrastructure. Yes, this introduces a partially public element, but that's a worthwhile trade-off for true serverless operation. Far from a drawback, the notification transaction is a clear win: receivers are far less vulnerable to dusting attacks, and senders avoid crafting transactions with Taproot outputs—a script type that privacy-conscious users rightly shun for on-chain exposure. SP, meanwhile, invites dust attacks, burdens wallets with heavy scanning overhead, and still demands those privacy-compromising Taproot outputs. The core operational gap between the two - BIP47 involves checking each transaction output against a set of monitored addresses (say, n of them), while SP piles on extra work by computing the P0 value for every output scanned. Crucially, this P0 computation in SP is decoupled from the number of tracked addresses, which is why some argue labels could boost SP's scalability. But don't overlook the serverless edge here: BIP47's model keeps everything decentralized and lightweight, with no central coordinator or server to introduce single points of failure, trust assumptions, or downtime risks. SP's added load—tied to output volume rather than tracked addresses—may scale with block size limits, but it still demands scanning every output in every block for every user, ballooning computational costs in a fully serverless setup. Wallet recovery under SP - That's a nightmare: reprocessing the entire blockchain's outputs from genesis. And on security - BIP47 stays lean and public-key-only, exposing nothing sensitive during monitoring. SP, however, requires the scanning private key (b_scan) to live on the node doing the heavy lifting - a risky concession in any serverless environment where nodes must operate independently and securely. BIP47's serverless purity keeps privacy robust without these compromises. look at the picture of what it looks like on the recivers end one can even Refund and notification txn lets you prove recovery process. Do you still need BTCPay Server? no need for complicated server set up or domian hosting etc... just post your PM8 and you are done.

it is called Auth47 not many people aware of this handy little tool that you can use within your SW(ashigaru) https://thebitcoinmanual.com/articles/auth47-paynym-accounts/

IYKYK adding instance of fulcrum to it instead of electrs

. Getting that directed into the HVAC Intake to heat my place and decentralize mining hashing towards my own instance of Bitcoin Core and Stratum server. As Decentralized as it gets no POOLs no worries!