HAVEN - Privacy Multisig Wallet (@haven_wallet) header
HAVEN - Privacy Multisig Wallet (@haven_wallet) profile picture

Private stablecoins, small-caps, RWAs on Ethereum Stops wallet analysis of employees, customers, vendors @Safe app available. Powered by @Railgun_Project

» Follow to be first at launch
Joined July 2026
Photo by HAVEN - Privacy Multisig Wallet (@haven_wallet)Photo by HAVEN - Privacy Multisig Wallet (@haven_wallet)Photo by HAVEN - Privacy Multisig Wallet (@haven_wallet)Photo by HAVEN - Privacy Multisig Wallet (@haven_wallet)Photo by HAVEN - Privacy Multisig Wallet (@haven_wallet)Photo by HAVEN - Privacy Multisig Wallet (@haven_wallet)
Every payment your treasury makes is public. Payroll, vendors, trades. Anyone can read them on Etherscan. Haven fixes that. Haven is a private multisignature wallet for Ethereum treasuries, powered by the @Railgun_Project protocol. It runs standalone, or as a @Safe app. The core is built and working today: private multisig, deposit, withdraw, sign and execute. Follow @Haven_Wallet to see it go live. Everything below is where it's heading. ⚙️ What Haven does: → Standalone k/n multisig: propose, collect signatures, execute. → Private balance and transfers across tokens, RWAs, DeFi positions and NFTs. → Recurring and scheduled payments. Funds for pending proposals and schedules are reserved, so a balance is never committed twice. → Private swaps with advanced order types: stop, limit and TWAP. → Private DeFi and earn. → Proxy addresses that work like exchange deposit and withdrawal addresses (explanation below). → Privacy score per asset: how many dollars of the token the pool holds, how many transfers it sees, and what share of that pool is you. → Invoices, accounting and tax exports. → Role-based access and spending limits. 🔒 How the privacy works: → Built on @Railgun_Project, a privacy protocol made of smart contracts directly on Ethereum. No new chain, no bridge. → Funds sit in a shared private asset pool. Zero-knowledge proofs let you spend without revealing sender, recipient or amount. → Payments appear to come from the shared smart contract, not your wallet. Deposits and withdrawals are disconnected, so nobody can tell who sent or received what. 📥 Why proxies matter: Someone not using Railgun can't send to a private address. They send to a public 0x address first, then it gets shielded. Today that's manual. A Haven proxy auto-shields on arrival via EIP-7702, so incoming funds just appear in your private balance. Some exchanges also reject deposits from smart contracts. So on withdrawal, funds unshield to an EIP-7702 wallet that forwards them to the recipient. They see a normal wallet, not the Railgun contract. 🔲 Why the privacy score matters: With a 100k deposit, you blend in on the large USDT pool but stand out in a small-cap pool with few users which makes deposit/withdrawal matching easy. The score shows your share of each asset’s pool. 🛡️ How the security works: → No backend server. No database. Signing, computing and execution all happen on the client. → Signers exchange signatures over an E2E encrypted channel. Data is cached for 24 hours so not every signer has to be online at once. No logs. → The signers multisig share private keys are never stored or sent. They are derived at signing time from a normal wallet signature (e.g. MetaMask), then removed. Only the signature share leaves your device. → Cryptography combines the independent signature shares of a k/n multisig into one valid Railgun signature, like a single key would. ❓ What people ask: Is it custodial? No. No server ever gets to see any key. Your signers hold them. With the same cryptographic process as in the Haven code, transactions can also always be computed outside the Haven app. Signers just need to exchange the signatures manually then. Is it compliant? Every shield is screened against sanctions lists with Proof of Innocence. Viewing keys give auditors and tax advisors a read-only view. Privacy from the public, not from the people you choose. Do my vendors need Haven? No. Inbound, senders pay a proxy address and it auto-shields; outbound, recipients are paid at a normal address directly from the Railgun smart contract or via a proxy. What does it cost? The protocol charges 0.25% per shield and unshield. Haven adds 0% at launch. 👉 Follow @Haven_Wallet to see it go live. The launch will be announced there first. Your bank never publishes your balance. On-chain, every payment your treasury ever made is permanent and public. Why is that still normal?
4
1
8
450
A 10,000 USDT payment from a 2/3 private multisig. Here's the whole flow in the @Haven_Wallet beta, and what Etherscan sees at the end. 1. Shield Deposit funds into your private balance once from any signer wallet or Safe. They join a shared pool with everyone else's, so nobody can tell whose they are. After a quick sanctions screening they're spendable any time, and you can withdraw back to any address. 2. Proposal A signer creates the payment. The 10,000 USDT is reserved right away, so the same funds can't be promised to a second proposal. 3. Signatures Signers approve with a normal wallet signature, like MetaMask. Each signature share is broadcast to the other signers. Once enough shares are in (e.g. 2/3), any signer can execute. 4. Execution The shares combine into one valid Railgun signature. A broadcaster pays the gas and submits the transaction for you, so it is never linked to a signer's wallet. Etherscan shows the funds getting sent from the Railgun contract. Multisig, private balance, shielding, private sending and withdrawals all work in the beta. Everything a treasury needs to pay privately is already there. Follow @Haven_Wallet to see it go live. Your receiptient sees the payment. Why should they also see every other payment you've made?
1
1
1
3
135
How do you make Ethereum private without building another Ethereum? @RAILGUN_Project takes the privacy system to the smart-contract level. It does not require users to move onto a separate Layer 2 or privacy chain. Instead, assets enter a set of Railgun smart contracts and become part of a shared private pool. Here is the basic flow. 1. Start with a normal wallet You hold ETH, USDC or another supported token in a regular Ethereum wallet. That wallet has a public 0x address. 2. Shield the assets You transfer the assets into Railgun. This transaction is public because the funds have to come from your public wallet. An observer can therefore see that your address deposited assets into Railgun. But that is where the normal transaction trail changes. 3. Enter the private pool Inside Railgun, the assets are represented as private balances rather than ordinary public wallet balances. A simple way to think about it is a large pool containing funds from many users. One person may put in 10,000 USDC. Another may put in 50,000 USDC. Another may put in 500 USDC. People can hold those assets for different lengths of time and use them in different ways. Railgun uses cryptographic proofs to keep track of who is allowed to spend which funds without publishing the normal details of those balances. 4. Transact inside the pool This is where the private activity happens. Users can send funds privately. They can also swap or interact with supported DeFi applications privately. That activity creates more transactions and more possible relationships inside the pool. Imagine 100 deposits and 100 withdrawals. Some deposits are followed by activity after an hour. Some funds remain inside for weeks. Some users swap tokens. Others send funds to another private balance. The public blockchain still records that Railgun is being used. But there is no simple public list matching each private action back to the original depositor. 5. Unshield Eventually, a user can withdraw funds to a normal 0x address. That exit is public again. An observer can see that Railgun sent funds to that address. But seeing the public entry and the public exit does not automatically reveal which entry produced which exit. That distinction is important. Railgun is not trying to make Ethereum transactions disappear. It changes what information is exposed while the assets are inside the private system. Railgun provides a private environment inside an existing public blockchain, with public entry and exit points but private activity between them.
1
1
3
384
HAVEN - Privacy Multisig Wallet retweeted
😡🚨 Next round coming up: Let's fight against #ChatControl 🚨😡 In July, the European Parliament approved Chat Control 1.0 👉 NOW, On September 29, the negotiations for CHAT CONTROL 2.0 RETURN. Unfortunately, this is a much bigger threat for everybody's #privacy. At Tuta we will continue to SAY NO to Chat Control and fight for our right to privacy ✊❤️ Find more about Voluntary Chat Control 1.0 👉 tuta.com/blog/voluntary-scan… Find more about Chat Control 2.0 👉 tuta.com/blog/chat-control-c… The fight against #ChatControl must go on!
41
339
22
1,142
33,090
Why do so many crypto teams put their treasury behind Safe? A Safe can have multiple owners. Those owners might be founders, finance leads, treasury operators, or other trusted accounts responsible for approving treasury activity. The Safe also has a threshold. That threshold defines how many required owners must approve a transaction before it can execute.
🤖 Made with AI
1
1
1
3
254
So a simple treasury flow can look like this: 1. A transaction is proposed. 2. The relevant owners review it. 3. The required number of owners approve it. 4. The Safe verifies those approvals. 5. The transaction executes.
1
1
3
135
This matters because treasury control does not depend on one person holding the only key. It creates a shared authorization process that can fit the structure of a company, protocol, or DAO. Safe can also be extended with additional modules for more specialized execution and access rules. That makes it useful as the foundation for more complex treasury workflows. The key idea is simple: Safe gives a team a programmable system for controlling treasury transactions.
1
17
You do not need a company’s org chart to start mapping its financial relationships. Open a public treasury wallet on Etherscan. You can inspect its transactions, recipients, timestamps, and amounts. Then follow the addresses receiving those funds. Click into related wallets and inspect their visible incoming and outgoing transfers. Over time, recurring addresses, payment timing, and repeated transfers can reveal relationships and operating rhythms. You may not always know who ultimately controls every wallet. But you can still follow the transaction history that is publicly visible and build a picture from repeated activity. Specialized wallet-analysis tools can make this much faster by organizing transactions and wallet relationships across large amounts of public blockchain data. That is why Haven treats treasury privacy as a problem of repeated public relationships, not just individual transactions.
🤖 Made with AI
1
1
4
363
What can six weeks of public safe treasury transfers tell an outsider about a company?
1
2
79
This does not mean Safe is doing anything wrong. Safe provides the shared approval and treasury-control process teams rely on. The question is what information still becomes public when an approved transaction is executed on a public blockchain.
1
4
That is the privacy gap Haven is exploring: keeping treasury operations accountable to the people who should see them without making every recurring payment equally useful to everyone watching the chain.
4
HAVEN - Privacy Multisig Wallet retweeted
Credit cards, live streaming, SSL, VPN, the list goes on. No one realizes it's happening until it's done. Tech moves slowly, then all at once. But the same can be said for surveillance. $RAIL fixes this. Shield.
1
3
15
740