Private payments for the internet. Accept Zcash in minutes. Non-custodial.
Joined June 2025
- Tweets349
- Following155
- Followers614
- Likes390
Cipherpay retweeted
Q3 retroactive grants have come to an end, and both @cipherpay_app and @cipherscan_app received funding.
I want to sincerely thank Zcash coinholders for placing their trust in me and for recognizing the work that went into both projects. It means a lot.
I was surprised by some of the results, but my message to everyone building in the ecosystem is simple: keep working hard and keep showing up.
There’s a unique opportunity in front of us to help move the world in a direction where privacy, individual sovereignty, and freedom are core values.
Zcash needs everyone.
Stay tuned for what’s next with Cipherscan.
Back to building 🧱🔨
Amazing news!
Use zodl and start selling goods online for zcash 🫡
This is amazing news for the Zcash community.
Now the next step is when can we buy @Ledger with shielded ZEC ? 👀
Cipherpay retweeted
Amsterdam vlog is live 🇳🇱
Recapping the recent Cypherpunk Week with the ZECsy team which included:
🌷 @CryptoCanal Common S3nse Conference & Hackathon
🔷 @Dashpay DashCon
💫 @Zcash Walking Tours of the city
And more! Thanks to everyone who came through- see you in India for @EFDevcon 🪷
And you'll be able to buy it with zcash:native
FIRE!
@joinwebzero is gonna drop these soon!
They offered me model 001/100 🫶🫶🫶
Go buy some shit immediately
Trial decryption just got 1.5x faster.
That's the operation CipherPay runs on every shielded
transaction to detect payments. Merchants x actions,
every block, every mempool push.
Good work @ZakuraZcash. The entire ecosystem benefits when infrastructure gets faster 🫡
Introducing Zakura Common.
We just shipped 14x faster proving, 21x faster hashing, 1.5x faster trial decryption, and 4-8x faster verification.
New releases of Zakura and wallets that use Zakura Common (such as @vizorwallet) will benefit immediately.
zakura.com/announcements/zak…
Cipherpay retweeted
Give this a shot!
It uses @cipherpay_app for a VERY smooth experience.
@astrea_systems takes the top spot!
Love the idea of your product!🔥 As AI becomes more common place it only makes sense to privatize and encrypt.
Cipherpay retweeted
We installed with a Shopify integration via @cipherpay_app, check it out and any questions ask @k6nb4k!
Cipherpay retweeted
Desde @zcashesp1 queremos dar gracias al equipo de @cipherpay_app, quienes facilitaron la solución con la para la campaña de donación #Zcash por Venezuela.
Hoy cerramos la campaña con un 100% de recaudación completado. Más detalles aquí:
forum.zcashcommunity.com/t/z…
It’s a MUST at this points. How many data leeks or wrench attacks do we need ?
Privacy = Security.
If you work for cold wallet company now is the time to enter the future.
Hardware wallet companies NEED to start accepting private payments.
Collect less data. Keep it for less time. Delete it once the device is delivered.
This isn’t about being paranoid.
It’s about making sure a database of who owns a hardware wallet doesn’t become a list of potential wrench-attack targets.
The tools already exist.
Privacy should be the default.
@cipherpay_app → Zcash private payments.
Or don’t and your company will go bankrupt in the next two years.
Cipherpay retweeted
Beginners guide to use @cipherpay_app or @BtcpayServer to accept Zcash payments 👇
Cipherpay retweeted
Privacy is a necessity. More and more.
The good thing with @cipherpay_app is that there's no customer data to hack.
We have some difficult news to share. Unfortunately, one of our shipping providers has experienced a data breach that exposed sensitive order data. This affects new customers in the US, UK, Sweden, Colombia, Brazil, Italy, and Portugal who received an order within the 90 days prior to August 8th, 2026.
The data exposed:
- Full names
- Shipping addresses
- Phone numbers
- Email addresses
The incident affects 11,742 customers with full exposure (name, email, phone number, shipping address) and 1,947 customers with partial exposure (name, city, email). The breach is limited due to Trezor’s strict 90-day data storage policy (we were also able to negotiate the same terms with fulfillment partners, who follow the same policy).
All affected customers have been contacted separately by email.
Our systems and devices remain secure, but affected customers could experience an increase in phishing attempts.
NEVER enter your wallet backup on a website or share it with anyone, and only check for updates on official Trezor channels.
We are deeply sorry to the community and those affected.
We are investigating this situation and will post updates on our blog:
trezor.io/blog/news/recent-c…
Shielded ZEC in. Local currency out. No exchange in between.
This is what a parallel economy looks like when the
pieces connect.
You can now cash out your ZEC to everyday payment apps in 100+ currencies.
Why we built this: shielded ZEC is the most private money in crypto, right up until you need to spend it. The usual exit is a centralized exchange, with an account, your documents, and a desk watching where your coins go. Privacy should not end at the cash out, and ZEC should be easy to use outside its own ecosystem.
How it works:
1. You send shielded ZEC
2. The order goes onchain on @peerxyz
3. A peer taker pays you in your payment app of choice
Smart contracts hold the crypto and a TEE verifies the payment privately, so every cash out is verifiable and secure. Your peer taker sees a payment username, nothing else. No documents, no private account data.
What's next: a deeper writeup on the security and privacy model, support for more payment platforms, and a developer API. If you try it, tell us where the flow can be simpler.
Live now. Cash out at zcashto[.]cash
CipherPay is not affected. We have no similar vulnerability.
More importantly, even if we did, no funds could be lost.
CipherPay is non-custodial by design. We never hold spending keys. There is no hot wallet to drain.
This class of exploit is structurally impossible.
Zcash.
There is a critical vulnerability being actively exploited on BTCPay Server, which can result in the loss of funds.
Please update your BTCPayServer to 2.4.2 by going to Admin Dashboard -> Server -> Maintenance -> Update & verify the 2.4.2 version string in the footer.
If you are unable to update right away, turn off your BTCPay Server to prevent unauthorized access until you can update.