Money that
keeps quiet.
For people, teams and AI agents paid in stablecoins. Hold, send and run payroll on public chains without publishing who you pay, how much, or what you have left.
- MOMaya OkaforSalary · Oct 28−6,400.00
- NLNorthline StudioInvoice 0193 · Oct 24+12,750.00
- AGResearch agentAPI calls · Oct 22−0.84
- HVHarbor VendorsOrder 88 · Oct 19−18,900.00
One quiet layer.
Three ways in.
Use the app today, verify the contracts yourself, or put private payments inside your own product. Same vault, same proofs, same guarantees.
Try it today
Hold, pay and run payroll privately from the wallet you already have. Dimpsy never holds your keys and has no admin withdraw.
Try the demoOpen vault contracts
Settlement stays public and auditable. The amounts and the people stay out of it.
Verify the contractsBuild on it
Private balances, payments and proofs for your app or agent, in one package.
Explore the SDKOn a public chain, every payment is a press release.
Anyone with a block explorer can read every amount, every balance and every counterparty, forever. Fine for a protocol. Not for a salary, a supplier or a runway. Dimpsy keeps settlement public and redacts the rest.
Private money,
try it now.
Deposit privately, pay anyone, and prove what you hold without showing the number. The demo is live now and runs with test money.
Pick an amount, then flip the view.The public sees a deposit. Not your balance.
Move USDG, USDC or USDT into a balance only you can see.
Pay a Dimpsy address or send a claim link. The explorer never learns how much.
Holds at least $10,000
Your balance behind itShow a lender, an auditor or a counterparty exactly what they need. Nothing more.
A payment has one owner. Nobody else should hold the key.
Private auctions and lending pools compute on many people's hidden data, so someone has to hold a key for all of them. A payment doesn't need that. You prove it on your own device.
A committee or an operator holds the key.
If it is ever breached, everyone who used it can be exposed. Past payments included.
Your device makes the proof. Nobody else holds a key.
If one device is breached, one person is exposed. Not everyone.
Some private payment services generate your proof on their own servers, which means the server sees your amounts. Dimpsy proofs are made in your browser or app, never on our machines. How Dimpsy compares
Built for money that shouldn't be public.
Stablecoins made onchain money fast and cheap. Dimpsy makes it discreet enough for the people who actually move it: you, your team, your company and your agents.
Your own money
Get paid, save and send to friends and family without strangers looking up your balance.
Freelancers
Get paid by every client without each one seeing what the others pay you.
Payroll
Pay your team in USDG or USDC. Nobody can look up who earns what.
Agent payments
Agents pay per call over x402 and MCP without exposing the treasury behind them.
Suppliers & treasury
Pay vendors and move company money without broadcasting your costs or your runway.
Tokenized assets
Hold tokenized stocks and funds with the size of your position off the public record.
Run payroll in one upload.
Drop in a list of names and amounts. Dimpsy pays everyone from your private balance and relays each payment for you, so your company wallet never shows up either.
Upload a CSVName, Dimpsy address or email, amount
Check what the public seesNo names, no amounts, no wallet
Pay everyoneAbout 8 seconds each, proved on your device
October payroll
5 people · USDGAdd private payments to anything.
The SDK gives any app or agent private balances, private payments and proofs. The MCP server lets an AI agent pay over x402 with spending limits, without showing its treasury.
import { createPayment, relay } from "@dimpsy/sdk"; const payment = await createPayment({ to: "dimpsy1q7…9xWd", amount: "250", asset: "USDG", }); const receipt = await relay(payment); // settled. the explorer shows a valid transfer, no amount, no wallet
import { dimpsyMcp } from "@dimpsy/mcp"; const server = dimpsyMcp({ budget: { daily: "25", perCall: "0.10", asset: "USDG" }, allow: ["api.search.example", "api.maps.example"], }); // your agent pays per call over x402. // providers get paid, nobody sees the treasury. server.listen();
import { proveAtLeast } from "@dimpsy/sdk"; const proof = await proveAtLeast({ asset: "USDG", threshold: "10000", audience: "ridge-credit", // only this reader can verify expires: "24h", }); // share proof.url. it fails if the reader or date changes.
Private payments you can prove.
Dimpsy isn't new cryptography. It is a new building block for finance: privacy by default, disclosure on your terms.
Payroll total proof
Prove a run of up to 32 payments added up to exactly a total, without showing who got what.
How it worksProofs for one reader
Each proof names who it is for and when it expires. Change either and it fails.
How proofs workPrivate payments for agents
Private x402 payments and an MCP server with hard spending limits your agent can't exceed.
Agents guideNobody can touch the money. Including us.
No admin withdraw
There is no function that lets anyone, including the Dimpsy team, take money out of the vault.
Three days of public notice
Any change to how payments are verified is announced on-chain 72 hours before it can take effect. Time enough to leave.
Open source, end to end
Contracts, circuits, app and SDK are public. Check the deployed bytecode against the repository yourself.
Proved on your device
Your amounts never reach a Dimpsy server. The proof is made where your keys already live.
Questions,
answered.
Still curious? The docs go deeper on every one of these.
Say less. Pay anyone.
Try the demo with the wallet you already have, or a demo wallet. No real money moves.