Sato Hub
Security Tool

PRXVT

Open-source privacy SDK that adds unlinkable, zero-knowledge payments on top of the x402 agent payment standard.

  • Sato Score68
  • ChainsEthereum, Base +1
EarlySelf-Reported

PRXVT is an open-source security tool by PRXVT on Ethereum, Base and Polygon, with no code activity tracked. Sato Score 68/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-23. How the score works →

See how to install PRXVT →

No code activity tracked

Listed from prxvt.com on 2026-06-08. Install: reproduced by Sato Hub on 2026-07-21. Evidence →

Next step

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Ask Sato Hub what is on record about PRXVT before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

PRXVT builds privacy-preserving infrastructure for AI-agent commerce, starting with px402, a privacy wrapper around the x402 payment standard where an agent obtains blinded credentials so payment patterns stay confidential. Its open-source Privacy SDK uses Groth16 zero-knowledge proofs and encrypted note storage, and the team is building related tools such as HushKit for private agent-to-agent communication. PRXVT integrates with ERC-8183 agentic-commerce hooks and has a $PRXVT token; the token is speculative and the cryptography has not been independently audited.

Sato Score

68/100· Medium

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
20/35
Code transparency
16/20
Interface verifiability
8/10
Docs & demo
6/10
Listing transparency & provenance
15/15
Independent verification
3/10

Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).

Sato Check

v1.0.2 · as of 2026-09-26
Does it take your key?
Asks for a key
Does your key leave?
Not yet run
Can it move funds on its own?
Unknown
Full profile, evidence and limits →

A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".

Evidence — listed vs checked · what the words mean

Listed from prxvt.com on 2026-06-08. Install: reproduced by Sato Hub on 2026-07-21.

ClaimValueEvidenceSourceChecked
Chains supportedEthereum, Base, Polygonself-reportedgithub.com/prxvt/sdkas of 2026-06-25
Verification statusSelf-Reported — not independently reviewedself-reportedprxvt.comas of 2026-10-23
Install worksreproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour✓ reproducedgithub.com/prxvt/sdk2026-07-21
Website answersanswered (HTTP 200)observedprxvt.com2026-10-23
Daily check record90 of 90 daily checks since 2026-07-25 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-22
Takes your keyasks for a private key or seed phrasedeclaredsatohub.aias of 2026-09-26
Key leaves the machinenot yet run with planted test keysthe sandbox lane has not run on this versionobservedsatohub.ainot dated
Moves funds on its ownunknown — could not read what it exposestracedsatohub.ai2026-09-26
Built byPRXVTconfidence 0.75self-reportedgithub.com/prxvt/sdkas of 2026-06-25
Creator profilehttps://github.com/PRXVTconfidence 0.80self-reportedgithub.com/prxvt/sdkas of 2026-06-25
Deploys asnpmconfidence 0.85self-reportedprxvt.comas of 2026-06-25
Works withx402confidence 0.80self-reportedprxvt.comas of 2026-06-25
Sato Score68/100 (Medium)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-23

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — reproduced in a container Jul 21, 2026

Runtime: node

npm install @prxvt/sdk
import { PrivacySDK } from '@prxvt/sdk'; const sdk = new PrivacySDK({ chain: 'base' })

You supply: A funding private key to deposit USDC and create the initial private note (per README quick-start)

Read from the project’s own docs as of 2026-07-21. What a deploy spec is →

Observed record — 91 daily checks since 2026-07-25

100%of 91 checks since 2026-07-25 succeeded
Currently responding for 91 days
Succeeded
91
Failed
0
Their error
0
Unattributed
0

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 38 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-23, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
68
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Ethereum, Base, Polygon
Agent types
Privacy, Payments
Open source
Yes
Pricing
Open-source SDK; usage tied to PRXVT token/x402 payments
Deploys as
npm
Works with
x402
Last checked
2026-10-23

Marketplace Signals

  • ▸ Open to tokenization

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#privacy#zero-knowledge#x402#agent-payments#sdk#erc-8183#open-source
See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to PRXVT's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Jul 26, 2026
    Sato Hub began tracking this listing
  2. Jul 21, 2026
    Verified: deploy spec
  3. Jun 25, 2026
    Enriched: creator name, marketplace notes
  4. Jun 25, 2026
    Auto-enriched: creator profile url, supported integrations, deployment options, chains supported

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about PRXVT

Is PRXVT open source?
Yes. PRXVT is open source under the MIT license; the repository is https://github.com/prxvt. Checked as of 2026-10-23.
Which chains does PRXVT support?
PRXVT lists support for Ethereum, Base, Polygon as of 2026-10-23.
Is PRXVT still maintained?
Sato Hub tracks no commit or release for PRXVT; it cannot say whether it is maintained.
How do I install or run PRXVT?
node. Install: npm install @prxvt/sdk. Entry: import { PrivacySDK } from '@prxvt/sdk'; const sdk = new PrivacySDK({ chain: 'base' }). Sato Hub reproduced this install in a container on 2026-07-21.
Is PRXVT verified on Sato Hub?
Sato Hub holds one earned check for PRXVT: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 68 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "PRXVT — Sato Hub." Sato Hub, updated 2026-10-23, accessed 2026-10-23. https://satohub.ai/resources/prxvt

Data last refreshed 2026-10-23; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.