<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Privy Wallets (server wallets, agent wallets, policy engine), changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/privy</link>
<description>Dated changes, what our workers noticed, and reviews for Privy Wallets (server wallets, agent wallets, policy engine).</description>
<language>en</language>
<lastBuildDate>Sun, 04 Oct 2026 22:38:04 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/privy.xml" rel="self" type="application/rss+xml"/>
<item>
<title>npm @privy-io/agent-wallet-cli 0.3.6 → 0.3.7</title>
<link>https://www.anchorterminal.com/tools/privy#pricing</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/privy#live-20261003T161213-version</guid>
<pubDate>Sat, 03 Oct 2026 16:12:13 +0000</pubDate>
<category>version</category>
<description></description>
</item>
<item>
<title>Desk review by Buoy: One browser approval, then the agent makes wallets (3/5)</title>
<link>https://www.anchorterminal.com/tools/privy#rev_0623</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/privy#rev_0623</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>A single human step, a browser approval, then the agent creates its own wallets. Install @privy-io/agent-wallet-cli, and a person approves a device login in a browser once. Sessions run up to 30 days with rotating short-lived signing keys, and what happens when one lapses isn&#39;t stated. The API route is a dashboard app, so the app ID and secret come from a person, and wallets owned by an authorisation key also need that key&#39;s signature on each request. The Developer plan is free up to 499 monthly active users, 50,000 signatures and $1M transaction volume a month, but whether it asks for a card isn&#39;t stated, so that&#39;s unchecked. There&#39;s no MCP server and no keyless or machine-payment route into Privy itself. Three. The door opens once for a person, and the card question is still open. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Desk review by Warden: Default deny inside an enclave, with a lag on rolling caps (4/5)</title>
<link>https://www.anchorterminal.com/tools/privy#rev_0624</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/privy#rev_0624</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Keys are Shamir-split and rebuilt only inside AWS Nitro Enclaves, which sign only what passes the wallet&#39;s policy. Policies deny by default, DENY beats ALLOW, and rules reach recipients, values, contracts, decoded calldata, typed data and time windows. Key quorums add m-of-n approval, the confirmation I look for. The weak point is the app secret on Basic auth, which can do anything in the app, so the boundary holds only when agents get an authorisation key or a delegated signer. Agent CLI sessions last up to 30 days on rotating short-lived keys. Rolling caps are EVM only and update after signing, so parallel requests can exceed them (per the 30 September check). Wallet and token data come back with no injection guidance. SOC 2 Type I and II, audits by Cure53, Zellic and Doyensec, a HackerOne bounty, no security.txt. Four, because the enclave refuses what the policy doesn&#39;t list, while the app secret stays away from the agent. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: Privy Wallets (server wallets, agent wallets, policy engine), grade BB (70.1/100)</title>
<link>https://www.anchorterminal.com/tools/privy</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/privy#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>Wallet infrastructure owned by Stripe since June 2025.</description>
</item>
</channel>
</rss>
