$RDIFF is live on @Pumpfun .
Ringdiff shows what a stranger can read from a Solana private payment: who paid, who got paid, how much. Then it fails your CI when a payment leaks.
CA: GrRyXcKfXcZo1yYWsH4kckxCuu3QSL5vYoJFEQTppump
https://t.co/n6bwPHpUui
$RDIFF now has utility. Live on https://t.co/tM7b8Z3Dbb today.
Until now, Ringdiff was completely free. From today, your $RDIFF balance sets how much you can do in the Ringdiff Lab.
Live checks per day: → Free: 10 → Hold 100,000 $RDIFF: 250 → Hold 1,000,000 $RDIFF: no daily cap
How it works: sign in with your wallet by signing a message. Ringdiff reads your $RDIFF balance on mainnet. No transaction, no transfer. Your tokens never leave your wallet.
Pulse, the reports and the npm CLI stay free for everyone.
https://t.co/l7QVoJ4NGe
How access works: https://t.co/3xGLa53Vh7
GrRyXcKfXcZo1yYWsH4kckxCuu3QSL5vYoJFEQTppump
Where Ringdiff is, and where it's going.
Shipped so far:
✓ Ringdiff 1.0: inspect any Solana Privacy Rings payment and see exactly what a public observer can read
✓ The Lab on https://t.co/tM7b8Z3Dbb: check, diff and exposure tools in the browser
✓ Mainnet privacy reports at https://t.co/7qmt6pb9Xj
✓ Ringdiff 2.0 on npm: an SDK, test matchers for Vitest and Jest, and ringdiff scan
✓ Ringdiff Watch (2.1): follow any address and get a Discord or Slack alert when a payment leaks
✓ Ringdiff Pulse: a live privacy dashboard for Privacy Rings, updated every minute from mainnet
Coming next:
→ $RDIFF utility. Holding $RDIFF unlocks Ringdiff's hosted tools. We only check your balance: no signing, no transfers.
→ Custom Rings on Pulse, as soon as they're live on mainnet
→ A public roadmap at https://t.co/QOYQIgtnzE with everything shipped and planned, kept up to date as we build
Everything read-only. No keys, ever.
The biggest Ringdiff update yet is coming.
Since launch, Ringdiff has been completely free while we built the core and grew the user base: Inspect, Lab, Watch and live Pulse, all on Solana mainnet.
In the next update, $RDIFF gets real utility.
Holding $RDIFF unlocks Ringdiff. Connect a wallet, Ringdiff checks your balance on chain, and the hosted tools open up for you. No signing, no transfers, and your tokens never leave your wallet.
Hold more for more: full holders get unlimited access across https://t.co/tM7b8Z3Dbb.
Thresholds and the exact launch date are coming soon.
Ringdiff Pulse is live.
A live privacy dashboard for Solana Privacy Rings, built from public mainnet data.
Right now: 91% of Ring transfers keep the asset and amount encrypted and the recipient out of view. About 9% name the recipient in plain view.
Every new payment is checked as it lands: → live private vs. leaked share → hourly chart → latest payments, each linked to the explorer → Rings side by side, with Custom Rings added once they're on mainnet
No keys. No signing. Public data only.
https://t.co/sUHZrl5N4s
Solana Privacy Rings are live on mainnet, and Custom Rings are coming soon.
More Rings means one question gets harder to answer: how private is each one, really?
We're building Ringdiff Pulse.
A live, public privacy dashboard for every Privacy Ring on Solana:
→ what each Ring keeps hidden, and what anyone can still read → live leak rates, checked payment by payment → Rings compared side by side → a daily mainnet privacy report, published automatically
No keys. No signing. Public data only.
Rings bring privacy. Ringdiff checks it.
Back to Building
Ringdiff Watch is live.
Your payments, checked the moment they land on mainnet. When one shows who got paid, what or how much, you get an alert in Discord, Slack or your own webhook.
npx ringdiff watch
Read-only. No keys, no signing.
https://t.co/n6bwPHpUui
New in Ringdiff: Watch.
Until now, Ringdiff told you what a payment revealed after you asked. Now it tells you the moment it happens.
Point it at a wallet, your app, or every Privacy Rings payment on mainnet. Each new payment gets checked as it lands. If a transfer shows who got paid, what or how much, you get an alert.
npx ringdiff watch
Send alerts to Discord, Slack or your own webhook. Alerts never include addresses or amounts.
Read-only. No keys, no signing.
https://t.co/Y7Eol6tkyk
Ringdiff tells you what a payment reveals. Next it'll tell you the moment it happens.
Coming next: Ringdiff Watch.
Point it at a wallet or your app's payment flow. Every new Privacy Rings payment gets checked as it lands. If one shows the recipient or the amount in plain view, you get an alert right away.
From the terminal: ringdiff watch <address>
Or send alerts to Discord, Slack or your own webhook.
It's read-only. No keys, no signing, and it only ever looks at what's already public onchain.
Building now.
Ringdiff v2 is live.
We said it was coming. Here's what it does 👇
→ An SDK. Check any Privacy Rings payment from your own code. One line throws if the recipient leaks.
→ Test matchers. expect(report).toKeepRecipientPrivate(), in Vitest or Jest.
→ ringdiff scan. We just read 200 mainnet transactions: 159 kept the recipient hidden, 8 named it in plain view.
Read-only. Never signs, never needs a key.
325 weekly downloads built v1. Thank you. This one's for you.
npm i ringdiff
https://t.co/Y7Eol6tkyk
Ringdiff v2 is live on @npmjs .
We said v2 was coming. It's here.
v1 was a CLI. v2 is a full SDK.
→ createRingdiff(): check any Privacy Rings payment from your own code
→ Test matchers: expect(tx).toKeepRecipientPrivate()
→ ringdiff scan: see what the newest mainnet Ring transactions reveal, in one command
Same promise: know what a stranger can read on-chain before you ship.
npm i ringdiff
https://t.co/mz9km6o2HR
325 weekly downloads on npm 📦
2 days ago, ringdiff was an idea.
Today, developers are running it to check what Solana Privacy Rings payments really reveal.
Thank you to everyone who installed it, ran it, and sent feedback. That's real adoption, and it's only the start.
So we're shipping v2.
Our first release proved one thing: devs want to know what a stranger can read on-chain before they ship.
v2 takes that further.
More soon. Until then:
npx ringdiff
https://t.co/Y7Eol6tkyk
Ringdiff technical update 🔧
New today: our mainnet privacy reports now share themselves.
Drop a https://t.co/7qmt6pb9Xj link anywhere and the card shows the real data. 951 dots, one per Privacy Rings transaction, grouped by what a stranger can read:
🟢 703 transfers, no recipient in plain view
🟠 52 transfers that named the recipient
⭕ 178 deposits and withdrawals, amount public
⚫ 18 other Ring activity
How it works:
→ The scanner reads Ring transactions straight from mainnet
→ Each one is decoded and every field is labelled Public, Encrypted or Unknown
→ The report is saved as counts and public signatures only, with no wallet addresses
→ The site builds the page and the image from that same file, so the chart can't drift from the data
Every new report gets its own card automatically.
What's shipped so far:
✅ CLI + SDK on npm: npx ringdiff
✅ Policy rules that fail your CI on a leak
✅ Mainnet reports with share cards
✅ CLI video: a real payment passing, then failing one rule
Next:
🔍 Wallet-level checks
📊 Weekly reports, starting 24 November
GM ☀️ Ringdiff morning update
Done:
✅ CLI and SDK live on npm (npx ringdiff)
✅ Mainnet privacy reports live at https://t.co/7qmt6pb9Xj
✅ 951 Ring transactions read, every number checkable on-chain
✅ New 30s video: a real mainnet payment passing, then failing one rule
✅ $RDIFF tokens locked on Streamflow, publicly verifiable
✅ CA on the website
Up next:
🔧 Share previews for report pages, so the data shows up right in the timeline
📊 Report #2 on 24 November, compared week over week
🔍 Wallet-level checks: see what all of a wallet's Ring payments reveal together
Building every day. We're here for the long haul.
https://t.co/Y7Eol6tkyk
Dev update on $RDIFF 🔒
We've been doing dev burns. This time we chose to lock instead.
6.6443M $RDIFF is now locked on Streamflow until May 17, 2027 at 4:34 AM (GMT+5:30). The contract is public, so anyone can check it:
https://t.co/4FRAMk2wPr
Why a lock this time?
A burn is a one-day headline. A lock is a commitment you can watch for months.
We're here for the long haul, not for 1 or 2 days. And we'd rather show it than say it:
→ CLI and SDK live on npm
→ Real mainnet privacy reports at https://t.co/7qmt6pb9Xj
→ A new video showing a real mainnet payment failing the check
→ Wallet-level checks coming next
Let's show the world what Ringdiff is.
How Ringdiff works, in one command.
PASS: asset and amount are encrypted.
Add one rule, and the same payment FAILS: the recipient is written right there in the transaction data, bytes 94 to 127.
Across 951 Ring transactions on mainnet, 52 transfers named their recipient.
npx ringdiff
https://t.co/Y7Eol6tSnS
Here's what those 4 hours built 👇
Ringdiff's mainnet scanner:
→ Pages through every Privacy Rings transaction, newest first
→ Runs 3 parallel workers with retry and backoff, so a rate limit slows the scan instead of breaking it
→ Decodes each Ring instruction and labels the sender, recipient, asset and amount as Public, Encrypted or Unknown
→ Saves only counts and public signatures. No wallet addresses go into the report.
First run:
1,000 transactions sampled
951 read
755 transfers with amount and asset encrypted
52 transfers with the recipient in plain view
178 deposits and withdrawals with the amount in plain view
Every number checkable on-chain:
https://t.co/OnmN3QbIoj
4 hours deep into one problem today:
How do you read 1,000 private payments on Solana mainnet, the way a stranger would, without paying for a private RPC?
Public RPCs rate-limit you hard. Requests drop. Pages break mid-scan.
Ringdiff technical update : how we read a private payment 🔍
Take a real Privacy Rings transfer on Solana mainnet:
2kLk…eMbU (slot 468,868,568)
Here's what Ringdiff does with it:
1. Fetch
Pull the finalized transaction from a public RPC. No keys, no special access. Just what any stranger can see.
2. Decode
Find the Ring instruction and walk its bytes.
The sender is the transaction signer, so it's always public.
In this one, the recipient sits inline in bytes 94 to 127, so it's public too.
Asset and amount are ciphertext.
3. Classify
Each field gets one label:
Public: readable on-chain
Encrypted: provably hidden
Unknown: we can't prove either way, so we never call it private
4. Enforce
npx ringdiff inspect 2kLk…eMbU --require "recipient must be confidential"
→ FAIL, exit 1
The amount was hidden. The recipient wasn't.
That's the leak Ringdiff exists to catch, before it ships.
Try it on any Ring transaction: https://t.co/tM7b8Z3Dbb