Good Monday aka Web3Privacy Newsletter day! Thank you to everyone who came to our Prague, Rome or Cluj meetups - eternal love. And while it truly is nice to meet each other and discuss privacy in real world, the news still keep coming. So here is your round-up of what happend everywhere. Lot of people are now noticing how it isn't advisable to have everything tied to one Google email. So in name of de-googling ourselves, let's take a look at @KagiHQ , our tool of this week. Other news featuring @signalapp testing automatic key verification via @CyberInsidercom, success of @Zcash, or hackers taking a look into possible BitLocker backdoor. Case study on not signing in with Google by @the_smart_ape and what to do instead from @Cybernews and much more. Check the full newsletter at Curated by @xgotchmax

Institutions want shared infrastructure. They don’t want full transparency, unpredictable costs, or crypto-native UX. That’s been the blocker. Today we’re introducing a new model: Sui Spheres 🧵

A defining moment for real-world assets. The CLARITY Act cleared the Senate Banking Committee. RWAs are closer to a defined regulatory framework than they've ever been, while the structural blocker that has kept institutional capital from flowing onchain at scale is being addressed. Mantle is the distribution layer this unlocks, connecting traditional finance to onchain liquidity. With this clarity, the path RWAs take from issuance to settlement runs through one stack. Where real-world finance flows.

Global trade has been "going digital" for more than 20 years. The problem was never digitization, but that no party would accept data from a system they didn’t trust. That’s the real blocker. A solvable infrastructure problem. TWIN is built around that reality. Powered by IOTA. #TrustedTrade#

> What happened to you? We have been consistent for years. Read "The Blocksize War" chapter 7 Thinking that the main purpose of running a node is to relay transactions is a "large blocker" misconception. While a strong relay network is important, it is nowhere near as important as enforcement of the consensus rules

Seems that some people are deeply disappointed that the 83 byte OP_Return limit wasn't a consensus rule and they think it ought to have been. Therefore they act as if it was a consensus rule. Very similar to how the larger blockers were deeply disappointed that the 1MB Blocksize limit was a consensus rule and tried to act as if it wasn't, act as if there was no such thing as consensus rules or act as if consensus rules are fuzzy. Maybe the OP_Return relay limit should have been a consensus rule, but it isn't. They need to accept that reality and accept the reality of what consensus rules mean.

Compliance? Boring? Not when you’re bringing real-world assets on-chain. For RWAs to become truly investable, they need rules, trust, validation, and institutional-grade rails. That’s what REAL is building. Compliance is not the blocker. It’s the bridge. RWA, unchained. Check what else @pauli_speaks has to say about it.

Traditional finance has always had privacy. Your counterparties don't see your positions. Your competitors don't see your book. That's just how markets work. Move onchain, and suddenly everything is visible. Every transaction, every exposure, every wallet interaction. For institutions used to TradFi norms, that's not a minor inconvenience. It's a structural blocker. The good news from Consensus Miami: the technology to close that gap is here. Selective confidentiality, policy enforcement at the transaction level, auditability without full exposure. Our Chief Revenue Officer Ulisse Dell'Orto joined the "Is Privacy Finally Possible?" panel, making a convincing case that institutions no longer have to choose between going onchain and operating with the discretion they require. Thanks to CoinDesk for the platform, and to @pbrody (Nightfall Networks), @ScottStornetta (@SuremarkDigital), @F_ZK_Now (@MidnightNtwrk), and @AdamZarazinski (@inca_digital) for a great conversation.

Over the past year, Lazer has embedded FDE teams inside some of the fastest growing AI companies in the world. Here’s 10 things we learned the hard way. Hopefully it saves you some time and $$. 1. Define KPIs before day one. No baseline = no ROI. Every engagement now starts with agreed metrics: tickets/week, time-to-first-PR, onboarding completion rate. 2. Agree on review SLAs. PR review delays were the #1# blocker. We now require a named reviewer, response SLA, and single access contact baked into the SOW. 3. First engineer builds the onboarding path. That documentation becomes the asset that makes every subsequent hire faster. Onboarding docs are part of the deliverable. 4. Schlep work is the moat. Access provisioning, environment setup, process gap filling, etc. This is exactly the work everyone else avoids. Once you’re the trusted pipe and intelligence layer, you’re very hard to rip out. 5. Calibrate talent one to two clicks above the end client’s team. Too far above and it creates friction. 6. Address the remote disadvantage proactively. In person onboarding week, inclusion in all standups, async response norms set upfront. 7. Track blockers quantitatively. Numbers surface what anecdotes hide. 8. Consequences ownership drives quality. Engineers who live with the decisions they make write better code. We push for post launch retainers on every engagement. 9. Map the real process, not the documented one. Run a workshop before scoping any agent workflow. The gap between those two is where the biggest value lives. 10. Build a reusable engagement template and let it compound. Each engagement funds the next. This is now standard practice across every FDE engagement Lazer runs. If your team is deploying agents and hitting friction at the enterprise layer, this is exactly what we’ve built for.