The privacy layer for onchain apps. Add private payments, swaps and yield to your app with one SDK.
Joined February 2025
- Tweets30
- Following1
- Followers91
- Likes143
Step by step:
Cash App: senddy.com/blog/cash-app-usd…
Venmo: senddy.com/blog/venmo-pyusd-…
Every trade you make on @fomo is public. Wallet finders unmask the rest, and copy bots buy right behind you.
Move your profits into Senddy, then fund a fresh Fomo account from it. Your new trades aren't linked onchain to your old one.
How it works: senddy.com/blog/fomo-private…
Fund your @HyperliquidX or @Lighter_xyz account without linking it to your wallet.
Senddy now deposits and withdraws across 11 networks, including Solana, Ethereum and Arbitrum, straight from your private balance.
senddy.com/?v
Wishing the @payy_link team a fast recovery.
Senddy is not affected: our prover and verifier run Barretenberg v5.0.1, which includes the fix.
We review our systems and dependencies weekly, and we upgrade cryptographic libraries on every release, whether or not it comes with an advisory. Security fixes don't always get announced. We'd urge every team building in ZK to do the same.
We're also evaluating @worldcoinfnd's ProveKit as a second, independent proving backend, so no single proving system is a point of failure for user funds.
Post mortem for the September 24th, 2026 exploit of Payy's bridge contract.
Based on our investigation, it appears that an attacker submitted an invalid burn proof that Payy’s deployed Noir/Barretenberg verifier accepted.
The first burn released 1,828,589.378132 USDC from the Payy rollup even though it appears that the transaction was invalid. A second burn of 1 USDC was paid early by a burn substitutor and later reimbursed. The second transaction released 90,202.820016 USDC to the same receiving wallet.
It appears there was a proving-system vulnerability in the Noir/Barretenberg verifier, developed by Aztec.
Full report: polybase.notion.site/Payy-US…
Senddy retweeted
Privacy + memes + stocks = ?
Coming soon to @RobinhoodCrypto
Hood up! 👀
Senddy Prepaid Cards are live.
Turn your private USDC into a virtual card for online checkouts. Funded through a one-time address, so the card never touches a wallet with your history on it. No ID upload.
Get started → senddy.com
Senddy now gives you a fresh address for every deposit, generated on your device. Gasless, one step, retired after use.
Live now → senddy.com
Developer APIs are coming.
Get an API key, add a few lines of code, and your app has private stablecoin transfers.
No ZK expertise needed. No blockchain infra to manage. Just REST calls.
Early access → senddy.com/developers
This is a known operational risk with Groth16. We chose universal SNARKs (Noir/UltraHonk) specifically to eliminate this failure mode — no circuit-specific ceremony means this entire class of vulnerability doesn't exist.
Privacy infrastructure shouldn't require a pinky promise.
The first two known exploits against live ZK circuits just happened, and they weren't subtle underconstrained bugs.
They were Groth16 verifiers deployed without completing the trusted setup ceremony. One was white-hat rescued for ~$1.5M, the other drained for 5 ETH.
🧵
We're not building a payments app. We're building the privacy layer for stablecoin infrastructure.
Any fintech, neobank, or exchange can plug Senddy in and offer private payments without building ZK systems from scratch.
We're onboarding early integrators now — DM us if you're building.
We built Senddy's consumer app to prove the tech works.
But the real product is the infrastructure underneath - private stablecoin payment rails any developer can plug into.
Sub-penny transactions. On/Off ramps. ZK privacy by default.
Docs 👇
senddy.com/docs
Private stablecoin payments 👁️
Fully shielded 🛡️
Non-custodial 🔑
Earn yield 💹
And more 💳
👇
senddy.com
Private testing is now live.
Want early access? 🔗 t.me/senddyapp
Dive into the docs & roadmap here: 📖 senddy.gitbook.io/senddy-doc…
