Preview documentation

Documentation

anonpeer is an anonymity-first finance OS for stablecoins and digital assets. These pages describe what the preview does today, how each module is meant to work, the anonymity model, and where real wallets, chains and contracts will connect.

Works today

Interactive app with five modules (currently locked)
Escrow lifecycle, treasury rules, vault previews
Runs in your browser on sample data

Not live yet

Wallet connection and any blockchain
Smart contracts, custody, live data
Anonymity: designed for, not implemented

Integration points

Modules

Five modules share one design system and one set of service interfaces. There is no trading, swap or exchange module, and no token.

Module	What it is for	Status
Dashboard	One calm overview of balances, activity and every tool on the platform.	Preview
Private Wallet	Hold and send stablecoins and digital assets from your own wallet, with anonymity as the goal.	Preview
Private Escrow	Conditional onchain payments between parties, with terms intended to stay between those involved.	Preview
AI Treasury	Automation that proposes and prepares payments. You approve every one.	Preview
Yield Vaults	Hypothetical stablecoin strategies with clear risk labels and no hidden complexity.	Hypothetical

Private Escrow

Escrow holds a payment until agreed conditions are met. The payer commits funds first, the payee delivers, and funds release milestone by milestone. In the preview the whole lifecycle runs as a local state machine, so no funds are locked and no contract exists.

Statuses

Draft: Terms are being written. Nothing is committed and either side can still change them.
Awaiting funding: Terms are agreed. The payer has not yet committed funds.
Funded: Funds are committed to the agreement. Work has not started.
In progress: Work is underway. The payee submits deliveries milestone by milestone.
Awaiting release: Every milestone is delivered. One or more are waiting for the payer to release.
Completed: All milestones are released. The agreement is closed.
Disputed: Releases are paused until the dispute is resolved. Resolution rules are not designed yet.
Cancelled: Closed without completion. Unreleased funds return to the payer.

How an agreement moves

1. Create. Title, counterparty address, asset and amount, optional milestones and the release conditions. The wizard validates every step.
2. Fund. The payer commits the amount. The balance shown in the app is reduced.
3. Deliver. The payee submits each milestone.
4. Release. Each submitted milestone is released after a release preview. When all are released the agreement completes.
5. Exceptions. Cancellation before funding is immediate. After funding it needs the counterparty. A dispute pauses releases until resolved.

Intended product

The goal is audited onchain escrow contracts with terms visible only to the parties involved. None of this exists yet, and contracts will not ship without an independent audit.

AI Treasury

AI Treasury prepares payments inside limits you define. Agents propose, people approve, and anything outside policy is blocked. The preview uses a deterministic rule engine with no model, so the same input always produces the same result.

Example rule

If a verified invoice under $250 is approved, prepare a payment for manual confirmation.

Anatomy of a rule

A rule names an agent, a trigger (invoice approved, weekly schedule, or balance above a threshold), a maximum amount, an optional recipient allow-list, whether the payee must be verified, and the approval required (one approver or two).

What the simulator checks

Check	Meaning
Rule enabled	The automation is switched on.
Agent active	The agent that owns the rule is not paused.
Trigger matches	The event is the one the rule listens for.
Within rule limit	The amount does not exceed the rule's maximum.
Within agent limits	The amount fits the agent's per-payment and remaining daily limits.
Payee verified	Only when the rule requires a verified payee.
Payee on allow-list	Only when the rule defines an allow-list.
Sufficient balance	The account holds enough of the asset.

If every check passes, the payment is prepared and waits in the approval queue. If any fails, the simulator reports exactly which one. Agents never hold keys and never move funds on their own.

Anonymity model

On a public chain, anyone can read balances and who paid whom. Addresses are pseudonymous: with enough context they can often be linked to a person or business. anonpeer exists to reduce that exposure.

Area	Goal	Status
Unlinkable payments	Outsiders cannot connect a payment to you or your counterparty.	Research
Zero-knowledge proofs	Prove facts about a balance or payment without revealing the underlying data.	Research
Selective disclosure	Share exactly what an auditor or counterparty needs, nothing more.	Research
Non-custodial	Your keys stay in your wallet. anonpeer never holds keys or funds.	Design goal
Balance hiding in the app	Masks numbers on your own screen.	Available (display only)

What exists today

Nothing in this preview provides anonymity. It does not use a blockchain, so there is nothing to anonymise. We will describe real protections precisely, and only once they exist. Anonymity tooling does not remove anyone's legal obligations.

Architecture

The interface depends only on typed service interfaces. Today they are backed by mock implementations and a browser-local store, and each can be replaced without rebuilding the UI.

UI (src/features, src/components)
   reads state      → src/hooks/use-app-state.ts
   calls actions    → src/lib/services/index.ts  (the `services` object)
        ▼
Service interfaces    src/lib/services/types.ts
        ▼
Mock implementations  src/lib/services/mock/*     ← replace these
        ▼
Local store + seed    src/lib/data/store.ts, seed.ts

Interface	Area	Today	Replaced by
WalletProvider	Wallet connectivity	Browser-local placeholder account	A wallet library, read-only first
PaymentService	Payments and networks	Updates local balances	Transaction construction and signing through the connected wallet
EscrowService	Escrow contracts	Local state machine	Audited smart contracts plus an indexer
TreasuryService	AI agent services	Deterministic rule engine	A policy engine first, a model second. Models propose, people approve
YieldService	Yield integrations	Hypothetical catalogue	Strategy adapters with sourced, timestamped data

Other integration points

Authentication. Not present. Add an auth provider and middleware for /app.
Backend and database. Replace the local store persistence. Identifiers are generated client-side today.
API endpoints. Route handlers under src/app/api/ using the types in src/types.
Networks. Chain configuration belongs in src/config/. Amounts are numbers in the preview and should be strings or bigints at a real boundary.

Full notes, including what must happen before any real funds are involved, are in docs/INTEGRATION.md in the repository.

Roadmap

Directional plans, not commitments. Order and scope may change.

V1Frontend PreviewNow
The interface, design system and product narrative.
V2Wallet ConnectivityNext
Connect an existing self-custody wallet in read-only mode first.
V3Audited Escrow & TestnetLater
Escrow contracts released only after independent audit.
V4Advanced Anonymity & AI WorkflowsLater
Research-led anonymity features and approval-gated automation.
V5Additional Financial ModulesLater
New modules once the foundations have proven themselves.

FAQ

Is anything here real?

No. Balances, payments, agreements, automations and vault figures are sample data stored in your browser. No blockchain is connected and no funds are held or moved.

Does anonpeer make me anonymous?

Not today. Hiding balances only masks numbers on your screen. Anonymity is the design goal and a research area. Public-chain addresses are pseudonymous, not anonymous.

Does AI Treasury use an AI model?

No. It uses a deterministic rule engine: the same input always gives the same result. A model may later propose payments, but the rule engine and a person would still decide.

Are the vault yields real?

No. They are hypothetical example ranges that show how the interface would work. They are not live rates, forecasts or promises, and no vault exists.

Is there a token?

No. There is no token and no token sale.

Can I trade or swap?

No. Trading, swaps and exchange features are deliberately not part of the product.

Where is my data stored?

In your browser's local storage. Clearing site data or using Reset data in Settings removes it.

Disclosures

anonpeer is a frontend preview. All balances, transactions, agreements and automations shown are simulated sample data. No blockchain is connected, no funds are held, moved or custodied, and nothing here is financial advice. Anonymity is a design goal that is not implemented in this preview, and it does not remove anyone's legal obligations.

Vault figures are hypothetical example ranges. They are not live rates, forecasts or promises, and capital can be lost in real strategies.
No security audit has been completed. No partnerships, licences or regulatory approvals are claimed.
The name anonpeer has not been checked for trademark or domain availability.
Legal pages are placeholders and must be written by qualified counsel before any public launch.

Back to home