Safe Pro: Early Partner Program is live. We're offering the best possible terms to our longstanding users for a limited time before Safe Pro becomes available for all. Read more: Waitlist:

My take on RWAs and tokenized stocks — the winning market structure must support both open retail/permissionless flows and institutional requirements. Hayden’s correlated-pairs idea is on point because it keeps the market structure(s) programmable and onchain. Critics who are insisting everything must look like traditional systems are essentially advocating to return to the very intermediary-heavy systems crypto set out to challenge, replace and improve. Ideal would be for those systems to be rebuilt with self-custody and open access as defaults.

My observed trends in web3 for rest of 2026 - More consolidation across projects via mergers, acquisitions or acquihires - Security teams selling AI driven vulnerability mining solutions - L2s are getting recycled — a lot of projects dying but new bets are taking form - Hardware wallets optimizing for card like devices - Security teams offering SOC2 equivalent for Web3 to capture vendor maturity - All consumer wallets are after perps - RWAs taking the center stage. The “big bet” for crypto to bring in new money - Stablecoins finding early maturity. Payroll and remittances next - Big exchanges using their wallet and L2 subsidiary companies as loss-leading units to funnel growth into primary business - All web3 incumbents focusing on institutional and enterprise - Privacy solutions ramping up but slow. Regulation uncertainty. This is not a dig.

A lot of people are now looking to multisig as “the” solution for the recent data leak incidents with trezor, ledger, coldcard etc. Even though I could be biased building @safe I can tell you that there is no silver bullet. However the fundamental choices Safe made in its design are to help people be more in control of their custody, security and sovereignty. A more secure setup than a standard EOA. Crypto industry has a tendency to use these incidents as trigger points in order to influence buyer choices with a cheeky marketing tactic like “How our solution X could have prevented the hack Y” — it’s FUD. The real hard work is in addressing these security goals proactively and bake them into your design choices. And yes, it makes your build more complicated and complex — I think many people in crypto will tell you that it’s not easy to build in web3. We don’t do it because it’s easy and helps people get rich, we do it because it’s a better way to build finance and helps people be more free. When you’re using self custody, a simple question to ask yourself is how to avoid “single point of failure” — be it a hardware wallet or a software wallet. A single private key loss should not result in a full compromise of your account. You shouldn’t be forced to share your personal details to having basic self custody over your owned assets. If you’re looking into Multisig, a simple and strong setup for a cold wallet could look like - a 2-or-3 setup with a self-custody recovery - Use hardware + dedicated mobile devices for signers. Leverage Safe Mobile - Make these signers dedicated to the multisig account - A clean and curated address book This would already go a long way and be far superior to a single wallet setup. My personally preferred use case for hardware devices are for signing only and not for storage. A more advanced setup would involve - Onchain policy like an allowlist of addresses you interact with (ex: hot wallets) - Another onchain policy like a time delay on your transactions - A solution over your account setup to monitor any drift in risk and be notified (ex: address poisoning, private key compromise, etc) - A solution over your assets and defi positions and be notified so you can act quickly (ex: protocol compromise, stablecoin depeg, etc) - An even more advanced setup would be to have means to auto unwind your positions An important note: a cold wallet setup is intentionally meant to be designed with friction to move assets. These are your long term holdings, your life savings etc — it should not be overly convenient to operate these. Having a separate hot wallet is always the best practice. All of these are possible with @safe multisig products today and we’re increasingly productizing these without compromising user sovereignty. Safe allows you to be intentional with your setup, your security and your convenience configuration. There is no silver bullet for the ultimate secure setup in anything. But that doesn’t mean that you can’t harden your setup. You should.

For many teams, what started as a single safe evolves into many safes. What started as a simple cold wallet now grew into a treasury. What started as a simple multisig turned into a mature account with tightened policies. Workspaces are designed to help these teams operate their safes as an operating system and in a professional way.

Happy to see @RequestNetwork live on @Safe. Finance teams can route stablecoin payouts through Safe, set signer thresholds, and batch multichain payments with multisig approval, built on the Safe API. Great to have Hypernative watching over every transaction too 🙌

The problem of managing safes across multiple networks have seen a huge evolution --- from multi-chain, to cross-chain, to keystore rollups. This is where @etheconomiczone gets it right i.e., solving it at the architectural layer 🫡

Gotta say that I love how the glamsterdam EIP updates are packaged in a digestible way for different stakeholders. Kudos @ethereumfndn 7708 is one of those almost invisible things but a big UX unlock for @safe users.