Silent Query Layer

$SQL IS LIVE ON @Stockereum Silent Query Layer just launched on Ethereum. Private payouts by ENS name: recipients and amounts stay encrypted onchain. CA: 0x5081b481aa5f27050588eab2f10d88ff45302afe ⚠️ This is the ONLY official CA. Verify it here before you buy. Your payroll is public. It shouldn't be. $SQL #SQL #Ethereum #Privacy

Privacy is becoming a first-class priority on Ethereum, and we're building for that future. $SQL @VitalikButerin: "I'm not giving up on privacy. I'm doubling down." Ethereum's privacy wallet toolkit, Kohaku, uses @RAILGUN_Project as its backbone for private transactions. That's the same privacy layer SQL Cash runs on. Our part of the mission: make the most sensitive onchain data private by default. Salaries. What we've shipped so far: ✅ Live app on Ethereum mainnet ✅ 7/7 real-funds mainnet tests passed ✅ Shield, private payment, withdrawal, return to origin, backup recovery Receipts, not promises.

Deposited and changed your mind? There's an undo. ↩️ Railgun's return-to-origin flow lets you send an unspent deposit back to the exact wallet that funded it, even during the Proof of Innocence standby. How SQL Cash makes it safe: → You enter the original shield transaction hash → The destination comes from the chain, not from a field you can mistype → Amount and destination are re-checked right before you sign → Any change → the app refuses We tested it with real funds on mainnet: etherscan.io/tx/0x8060c2e37e… Powered by @RAILGUN_Project. Safety rails are a feature, not an afterthought.

Not your keys, not your salary. SQL Cash never holds your funds or your recovery phrase. Here's what protects you: → Connect any wallet: @MetaMask, Rabby, Coinbase Wallet or anything via @WalletConnect → Your vault gets its own 12-word phrase, and we check 3 words before it opens → Optional encrypted backup: AES-256-GCM, PBKDF2 with 600,000 iterations → Auto-lock after 10 minutes idle → Exact token approvals only, never unlimited → Every transaction is journaled before sending, so no accidental double payments Lose your phrase and your backup? Nobody can recover it. Not us, not anyone. That's what self-custody means. Back it up.

What SQL Cash hides, and what it doesn't. $SQL We'd rather tell you exactly where the line is. 🔒 PRIVATE → Who you paid → How much each person received → Private balances and payment memos 📢 PUBLIC → Your deposit (address, amount, time) → Withdrawals to public addresses → The wallet that pays gas for a transaction → ENS records you choose to publish ⚠️ HONEST LIMITS → Privacy isn't IP anonymity: RPCs and infrastructure can see network metadata → Withdrawing to the same wallet that funded you weakens privacy → A compromised device can defeat any app Want the full picture of how Railgun's privacy model works? @l2beat publishes an independent review. Privacy you can reason about > privacy marketing.

Why is my deposit "pending"? Meet Proof of Innocence. ⏳ After you shield USDC, @RAILGUN_Project puts new deposits through a Private Proof of Innocence check before they can move privately. What it means: → Usually ~1 hour of standby → Your funds are safe and visible in your vault as "pending" → Higher gas won't speed it up → Refreshing the page won't either Why it exists: it helps keep illicit funds out of the shared privacy set, which protects every honest user in it. Changed your mind during standby? SQL Cash supports return-to-origin: send the deposit back to the exact wallet that funded it. Privacy with accountability. That's how it should work.

How to receive private payments with your ENS name, in 3 steps 🧵 1/ Open SQL Cash → Receive → copy your 0zk address 2/ Go to the @ensdomains app → your name → Records → add a text record: key: railgun value: your 0zk address 3/ Share your .eth name. That's it. When someone pays you through SQL Cash, it reads that record, shows them your resolved 0zk address to review, and sends privately. What becomes public: that your ENS name links to a Railgun address. What stays private: every payment you receive, and how much. Human-readable for the payer. Invisible to everyone else.

0x vs 0zk: know the difference. $SQL 0x… is your public Ethereum address. Every balance and transfer is visible to anyone. 0zk… is a private @RAILGUN_Project receiving address. Payments to it are encrypted onchain, and only the owner's vault can decrypt them. In SQL Cash: → Your public wallet (0x) pays gas and funds deposits → Your private vault (0zk) holds and receives private USDC → They are separate: the vault has its own 12-word recovery phrase Your 0x wallet is your front door. Your 0zk vault is your safe. Never send to a 0zk address from a wallet that doesn't support Railgun, and never paste a 0x address where a 0zk is expected.

What does "shielding" actually mean? 🛡️ When you shield USDC with SQL Cash, your public tokens move into @RAILGUN_Project's privacy system on Ethereum mainnet. Step by step: 1. Your wallet approves the EXACT USDC amount, never unlimited 2. You sign a shield-key message (free, no gas) 3. The shield transaction moves USDC into Railgun 4. A private note is created, readable only by your vault What's public: your deposit address, amount and time. What's private: everything you do after that. Fee: 0.25% Railgun protocol fee + normal ETH gas. Shielding is the door. What happens inside stays inside.

Stablecoin payroll is growing. Its privacy isn't. 💵 Paying contributors in USDC from @circle is fast, global and cheap: no banks, no borders, no 3-day wire. But on a public chain, every USDC salary is broadcast forever. SQL Cash keeps the speed and fixes the exposure: → Shield USDC once → Pay up to 10 people in one private transfer → Each payment is authorized by a zero-knowledge proof → Recipients withdraw when they want, ideally to a fresh address Same dollars. Same Ethereum. No public payroll. Built for DAOs, startups, grant programs and freelancers. ░ sql.cash

Your onchain payroll is a public spreadsheet. Every time a team pays someone in crypto, the world learns: → who works for you → how much each person earns → when you pay, and how often → how much runway your treasury has left On @ethereum, that data is permanent. Anyone can map it: competitors, recruiters, scammers. This isn't a hypothetical risk. Public salaries make people targets for phishing, social engineering and worse. Transparency should apply to protocols, not to people's paychecks. That's why we built SQL Cash: private USDC payments on Ethereum mainnet. Recipients and amounts stay encrypted onchain, and you keep full custody. Your payroll is public. It shouldn't be.

Thanks for the shout 🙏 @SebastianWols17, if you try it, add your 0zk address as the railgun text record on your .eth name and anyone can pay you privately by name.

That’s the idea 🫡 Pay a name, keep the amount between you and the recipient. Try it with a small test first: sql.cash

Thanks for the signal 🫡 Payroll shouldn’t double as a public spreadsheet. The app is live and tested on Ethereum mainnet: sql.cash

The SQL Cash RAILGUN SDK is now open source. Explore our TypeScript integration for private USDC payments on Ethereum covering vault creation and recovery, shielding, private transfers, and withdrawals. Source code, documentation, and the v0.1.0 package are available: github.com/sql-hq/railgun-sd…

Funding a trading account without linking it to your main wallet is a real use case, not a niche one. Private USDC that moves where people actually use it is the right direction. Nice ship.

Agreed. More than one privacy layer live on Ethereum mainnet is a good sign, not competition. The next step is making them feel like normal payments: send to a name, pay a team, done. That’s the UX we’re building toward.

Shielded transfers aren’t a loophole. They’re how payroll, donations and treasuries avoid becoming public spreadsheets. Good to see this argued on the record. Privacy across chains is better for everyone.

Glad you caught it. An expired name doesn’t just cost you the name: whoever re-registers it also receives every payment sent to it. Renew for years, not months.

USDC to register the name. USDC to get paid privately to it.On sql.cash, payers type a .eth name, we read its railgun text record, and the USDC lands shielded via @RAILGUN_Project. Names in, amounts private. Same name, both directions: pay for it in USDC, receive private USDC at it.Add your Railgun 0zk address as a railgun text record and anyone can pay you privately by name on sql.cash. This closes a nice loop. Your ENS name already routes payments. With a railgun text record, it can route private USDC too. Tested on Ethereum mainnet.

✅ SQL Cash: mainnet financial tests PASSED Real funds on Ethereum mainnet via Railgun. 7/7 transactions confirmed: [/> CYCLE A · NORMAL 1 Approve → etherscan.io/tx/0x8800e177eb… 2 Shield → etherscan.io/tx/0x448241176a… 3 Private payment → etherscan.io/tx/0xa6c04d697e… 4 Withdrawal → etherscan.io/tx/0x89c960b562… [/> CYCLE B · RETURN TO ORIGIN 5 Approve → etherscan.io/tx/0xa641ebde56… 6 Shield → etherscan.io/tx/0x45a63d2051… 7 Return to origin → etherscan.io/tx/0x8060c2e37e… ✓ Encrypted backup recovery: balances + history match 0.02 USDC tested · 0.00139 ETH in fees Withdrawal credited 0.009776 USDC · return to origin 0.009951 USDC Small-value acceptance tests, not an independent audit. We ship receipts, not promises. ░ sql.cash✅ SQL Cash: mainnet financial tests PASSED Real funds on Ethereum mainnet via Railgun. 7/7 transactions confirmed: [/> CYCLE A · NORMAL 1 Approve → etherscan.io/tx/0x8800e177eb… 2 Shield → etherscan.io/tx/0x448241176a… 3 Private payment → etherscan.io/tx/0xa6c04d697e… 4 Withdrawal → etherscan.io/tx/0x89c960b562… [/> CYCLE B · RETURN TO ORIGIN 5 Approve → etherscan.io/tx/0xa641ebde56… 6 Shield → etherscan.io/tx/0x45a63d2051… 7 Return to origin → etherscan.io/tx/0x8060c2e37e… ✓ Encrypted backup recovery: balances + history match 0.02 USDC tested · 0.00139 ETH in fees Withdrawal credited 0.009776 USDC · return to origin 0.009951 USDC Small-value acceptance tests, not an independent audit. We ship receipts, not promises. ░ sql.cash