Privacy on a public blockchain isn’t a feature you add. It’s the only viable UX for money.
Today we’re opening the hood on what we’ve actually built at BASEUSDP. $USDP
Ca: 0x7b29e5266634BCbA06686E580AfD4419a8c84b07
It ain’t a mixer, nor a new L1. A complete privacy-first settlement layer for humans, AI agents, and the open web. Built on @base. 🧵
BASEUSDP now has a Streamer Mode tab.
One page for everything a creator going live needs,customize the OBS tip overlay (position, accent, duration, threshold), preview it live, see real-time tip stats and top supporters, and copy your public profile + tip URLs in a click.
Live in the dashboard, fully responsive.
The BASEUSDP AI Terminal now supports voice mode.
Tap the mic to speak your request, "tip GeorgesK 5 USDC", "what's my balance", and turn on Speak to have replies read aloud. Hands-free wallet ops, in any modern browser, no extra app or extension.
Live in the dashboard.
Global finance onchain is only half the equation.
The other half is making sure it's private.
Every payment visible by default is a surveillance system, not a financial system.
We're building the privacy layer, ZK-encrypted settlements, SMS-native reach, agent-compatible from day one.
@base brings finance onchain. We make it confidential.
$USDP
Every BASEUSDP creator now has a public profile page.
https://t.co/aCIToi1wID, avatar, totals, recent tips, and a one-click "Tip me" button. A shareable surface anyone can land on without an account.
Check ours: https://t.co/r2FH52s8Wi
The bulk handle resolution endpoint on BASEUSDP now has a UI.
Previously API-only, usable by AI agents but invisible to humans. The Analytics tab now lets anyone paste up to 50 @handles, sign once, and get every wallet address back for $0.05 USDC via x402.
BASEUSDP added a second pay-per-call API: bulk handle resolution.
POST up to 50 @handles → get back the wallet addresses in one request, $0.05 USDC via x402. Built for AI agents, dashboards, and integrations that need batch lookups instead of one call at a time.
Global finance needs privacy by default.
We're building the private payment layer for it ZK-encrypted settlements, SMS-native reach, agent-compatible from day one.
Any phone number. Any agent. Any protocol. Privately settled on @base.
Check us out @davidtsocy $USDP
Let's talk about the expansion potential of what we're building.
Every project on @base that handles payments, agent settlements, API monetization, or user transactions has a privacy problem they haven't solved yet.
We're the solution layer.
→ Any protocol can integrate our ZK privacy layer and offer confidential settlements to their users
→ Any AI agent marketplace can route payments through us and keep spending patterns private
→ Any x402-compatible API can add private payment gating in a single HTTP request
→ Any app with a user base can let people send USDC to a phone number — no wallet required on the receiving end
We're not just a product. We're infrastructure.
The more @base grows, the more protocols need privacy. The more agents transact, the more confidential settlement matters. The more people onboard, the more SMS-native payments make sense.
Every new project on Base is a potential integration.
That's the expansion. $USDP
Us too. Cooking up a massive update this week, one that's going to get projects on @base actually interested in plugging into our privacy tech.
Stay close. $USDP
BASEUSDP now supports passkey step-up for large sends.
Set a USD threshold in Settings, and any send at or above it requires a fresh biometric (Touch ID, Face ID, or hardware key) before your wallet signs.
Layered security for high-value transfers, optional, configurable per device.
Let's talk about what we're actually building.
@base is becoming the blockchain for agentic settlement. Every agent needs to pay, earn, and settle on-chain.
We're building the privacy layer underneath all of it.
Here's what that looks like in practice:
→ SMS payments — send USDC to any phone number, no wallet required on the receiving end, ZK-encrypted end-to-end, funds held in escrow until claimed via a one-time secure link
→ Three privacy tiers — full private (zero on-chain footprint), semi-private (amount hidden, relay protected), or standard. You choose.
→ x402 HTTP-native payments — any API, any browser, any agent can trigger a private payment with a single HTTP request
→ Agent identity — ERC-8004 soulbound passports with hard-coded spend caps so agents can transact autonomously without exposing their full financial activity
→ Base MCP plugin — any AI connected to Base MCP can now resolve handles, send tips, and create payment requests through us. Non-custodial. Opt-in per user.
→ Integrations live — @StargazeMPP (machine intelligence marketplace), @Crotafi (AWS of AI agents on Base), @VeilCash (zk-SNARK shielded pool)
→ Flywheel — every fee from ZK transfers, SMS escrow, relay routing, and x402 payments flows back into buybacks, holder rewards, and burns
The agentic economy needs private settlement.
We built it. First and only on @base.
$USDP
And private settlement is the missing piece.
Agents settling publicly expose every spending pattern, every counterparty, every workflow to anyone watching on-chain.
We built the privacy layer for it. ZK-encrypted, SMS-native, agent-compatible, on @base.
$USDP
Agents are becoming paying customers.
And paying customers need privacy.
Every inference call, every data query, every API payment an agent makes, visible on-chain by default.
We built the fix. ZK-encrypted, SMS-native, agent-compatible private payments on @base.
The private payment layer will be next up.
$USDP
BASEUSDP now offers pay-per-call APIs.
Premium creator analytics are available for $0.01 in USDC per request, payable in one click by a person, or autonomously by an AI agent, with no subscriptions or API keys.
Powered by the x402 standard and settled onchain on Base. Machine-payable infrastructure for the agent economy.
We use both FHE and ZK proofs. Here's why both matter.
FHE (Fully Homomorphic Encryption), your balance is stored as an encrypted ciphertext on-chain. Even validators never see the plaintext amount. Transfers execute homomorphically.
ZK Proofs, power the shielded pool. You deposit USDC, receive a commitment, generate a proof. The proof verifies ownership and correct new commitments without ever revealing the amount or recipient on-chain.
FHE handles the common case. ZK handles the unlinkability proof. They're complementary, each covers what the other can't.
That's the cryptographic foundation of $USDP on @base.
Three privacy tiers. One protocol.
Full Private, ZK-encrypted, zero on-chain footprint, no amount visible, no counterparty linked. Highest fee.
Semi-Private, amount hidden, relay protected, faster settlement. Mid fee.
Standard, fully on-chain, fastest, lowest fee.
You choose your privacy level based on what the payment requires. The infrastructure handles the rest.
First and only SMS privacy payments on @base. $USDP.
Shipped: a Model Context Protocol server for BASEUSDP.
4 tools, resolve_handle, send_tip, create_payment_request, list_recent_tips, exposed to any MCP client (Claude, Cursor, ChatGPT) over streamable HTTP.
Non-custodial. Opt-in per user. Live on @base.
We just shipped BASEUSDP as a Base MCP plugin.
What that means practically:
Any AI agent connected to @base MCP can now resolve handles, send tips, create payment requests, and list recent transactions, all privately, all non-custodial, all opt-in per user.
We didn't build a crypto app. We built payment infrastructure for the agentic economy.
$USDP.
A lot of people ask how our SMS payments actually work under the hood.
Here's the full flow:
You enter a phone number and amount → USDC goes into SMSEscrow.sol → recipient gets a one-time secure claim link via text → they claim without ever needing a wallet or address.
The entire transfer is ZK-encrypted. The amount is hidden. The counterparty is hidden. Even the relay nodes routing the transaction can't see what's moving.
That's not a feature. That's the foundation.
$USDP on @base.
shipped: BASEUSDP as a @base MCP plugin.
Four public tools at /api/mcp/*, resolve handle, send tip, create payment request, list recent tips. Any AI connected to Base MCP can drive them.
Non-custodial (writes return unsigned calldata). Opt-in per user.
https://t.co/AgGiO433Wa