Peanut primary-source snapshot
Fetched: 2026-04-27 UTC
1) llms.txt
Source: https://peanut.me/llms.txt
Selected excerpts from the official site:
Instant global peer-to-peer payments in digital dollars.
Peanut is the easiest way to send digital dollars to anyone, anywhere. No banks, no borders — just fast, cheap money transfers.
Self-custodied accounts — your funds sit in your own smart account, secured by biometric passkeys
Additional signals from the source:
- Peanut publishes a compact AI-facing project index, which is already a useful primary-source surface even without a separate formal whitepaper
- The short index immediately frames the project around digital-dollar payments, payment links, self-custody, and local bank cash-out rather than around speculation or DeFi
- The corridor list strongly suggests Latin America is the main initial operating footprint
2) llms-full.txt
Source: https://peanut.me/llms-full.txt
Selected excerpts from the official site:
Peanut is a peer-to-peer payments app that lets users send and receive money globally using digital dollars (USDC stablecoins).
Self-custodied smart accounts: User funds sit in ERC-4337 smart accounts, not on Peanut servers
Biometric passkeys: Account access is secured by the device’s Secure Enclave
Core features (send, receive, payment links) work without KYC
Technical Stack … ERC-4337 smart accounts on Base (Ethereum L2)
Additional signals from the source:
- This file is unusually high-signal because it compresses product, compliance, security-model, target-market, and technical-stack information into one primary document
- The combination of Base, ERC-4337, passkeys, and low-friction send flows makes Peanut look like app-layer money UX built on account abstraction rather than a conventional exchange account
- The explanation that Peanut cannot access, freeze, or move user funds is a central trust-model claim worth preserving
3) Help center
Source: https://peanut.me/support
Selected excerpt from the official site:
Get help with Peanut — verification, passkeys, payments, deposits, and account recovery.
Additional signals from the source:
- Even this lightweight support page is useful because it reveals the live user-operating surface
- Verification, passkeys, deposits, and recovery are all first-class topics, which reinforces that Peanut is trying to hide crypto complexity behind consumer support flows
4) GitHub organization
Source: https://github.com/peanutprotocol
Selected excerpts/signals from the public org page:
Smart Contracts Repository
SDK Repository
API Repository
UI Repository
We have an open bug bounty and have paid out more than $15k to date.
Additional signals from the source:
- The repo inventory shows Peanut is not only a mobile/web frontend; it also maintains contracts, SDK, API, and UI layers
- The public bug-bounty reference is a useful security-process signal for a consumer payments app handling self-custodied value flows
5) Smart contracts repo
Source: https://github.com/peanutprotocol/peanut-contracts
Selected excerpts/signals from the repo page:
Repo for peanut smart contracts
See list of deployed contracts on contracts.json
If you find any vulnerabilities, please report them to us asap. We have a bug bounty program and a history of payouts!
Additional signals from the source:
- The repo confirms an onchain contract layer exists beneath the app
- Deployed-contract references and chain-specific examples make the product look operational rather than conceptual
6) SDK repo
Source: https://github.com/peanutprotocol/peanut-sdk
Selected excerpts/signals from the repo page:
Send tokens via cryptographically secure links.
npm i @squirrel-labs/peanut-sdk
Additional signals from the source:
- The SDK framing clarifies that Peanut’s payment-link flow is not just a marketing story; it is a reusable developer primitive
- This strengthens the case that Peanut belongs in the library as payments infrastructure, not merely as a consumer app
Notes
- Peanut appears best cataloged as a consumer stablecoin payments app / self-custodial remittance infrastructure / smart-account wallet.
- No canonical whitepaper or litepaper surfaced in this pass.
- The strongest categorization clue is the combination of
llms.txt/llms-full.txt, which jointly expose the trust model, operating corridors, compliance posture, and technical stack more clearly than the homepage alone.