new-wallet-fundr

New-wallet-fundr automates the full flow of privately funding a fresh wallet across EVM chains. It makes it easy to break on-chain links between your funding source and your DeFi activity — without complex and time-consuming manual steps.

The Problem

When you fund a new wallet from an established address, you carry its history with you. That address becomes your public identity onchain — linked to your past transactions, net worth, and behavior.

Today, the process to break this link is manual and error-prone:

• Bridge funds to a privacy-supported chain
• Shield into Railgun
• Wait for PPOI (Privacy Pool Origin Integrity)
• Unshield to a fresh address
• Bridge out to destination chain

One misstep breaks privacy.

The Solution

New-wallet-fundr turns this into a single automated pipeline. It uses li.fi for cross-chain bridging and Railgun for shielding/unshielding with ZK proofs.

For protocols like Privacy Pools where withdrawal timing matters, we integrate Allium on-chain data to monitor pool activity — TVL, withdrawal volume — and automatically recommend the best time for withdrawal, maximizing the privacy set.

Note: Due to time constraints at Hack Money, this project remains in the design and planning phase. No full implementation was completed yet.

Background on this project: we got the idea after using Privacy Pools protocol and wathcing how people use Railgun to fund fresh wallets. The process works, but it's painful: you have to bridge funds, shield them, wait over an hour for PPOI clearance, generate a ZK proof to unshield, waint more, and then bridge again to your destination chain/wallet. It's too time consuming and manual. Most people either skip steps or make mistakes that break the privacy guarantee entirely. We wanted to fix it.

The key component of this project is the orchestration of multiple privacy and bridging protocols into a single automated pipeline. Instead of manually executing five separate steps to privately fund a wallet, new-wallet-fundr chains them together so that one command handles everything from bridge-in to bridge-out.

The first and last steps use the li.fi SDK for cross-chain bridging. li.fi aggregates routes across 20+ EVM chains and finds the best rate, so the tool is chain-agnostic out of the box. A user can start on Ethereum mainnet and end up on Base without needing to think about which bridge to use. The privacy layer relies on the Railgun Wallet SDK. After bridging to a Railgun-supported chain (Arbitrum by default), the tool shields funds into Railgun's private pool. It then polls the PPOI (Privacy Pool Origin Integrity) bucket status every 5 minutes until the funds become spendable (typically about an hour).Once cleared, it generates a ZK proof and unshields to a completely fresh address with no on-chain history.

The trickiest part of the design is withdrawal timing. For protocols like Privacy Pools, where you deposit and withdraw from a shared pool, the size of the anonymity set matters. If withdrawal volume is low, it becomes statistically possible to correlate the depositor and withdrawer. To address this, we integrate Allium on-chain data to monitor pool activity — TVL, deposit/withdrawal volume — and recommend the optimal time to withdraw, when the privacy set is largest.

The V1 interface is a Node.js / TypeScript CLI with inputs like --source-chain, --token, --amount, and --destination-chain. The tool generates a fresh EOA offline and only needs read access to the funding wallet.

Future versions may add a local AI interface and support for Privacy Pools as an alternative privacy backend.

Tech Stack:

li.fi SDK — cross-chain bridge aggregation (bridge-in and bridge-out across 20+ EVM chains) Railgun Wallet SDK — shielding, PPOI polling, ZK-proof generation, unshielding Allium — on-chain data API for monitoring pool TVL and withdrawal activity Node.js / TypeScript — orchestration runtime Privacy Pools — alternative privacy backend (planned)

Note: Due to time constraints at Hack Money, this project remains in the design and planning phase. No full implementation was completed.