A testnet prototype for an AI-assisted treasury interface, combining a chat workflow, application-level trade checks and third-party privacy infrastructure.
Environment: Monad testnet. This repository is a technical prototype; it has not been established as a production treasury or an audited financial system.
- Tool-use loop connects the model to application tools.
- Trade validator checks allowed tokens, trade size, pause state and cooldown rules.
- Shared types describe application events and treasury state.
- Frontend contains the wallet, pool, settings and chat interface.
- Validated findings contains dated development observations; these are historical project notes, not a current security audit.
User request → model proposes a tool call
→ application validates the proposed action
→ configured testnet / SDK integration
→ result shown in the interface
A model's self-check is not an independent enforcement boundary. Application validation and any deployed contract must be evaluated separately.
This repository contains application logic, integrations and interface work developed with AI assistance, as recorded in commit history. Unlink supplies the privacy SDK and proof system; this project does not claim to have invented its cryptography. Monad supplies the test network. OpenRouter/model providers supply inference. React, Vite, Express and SQLite supply application infrastructure.
The repository's original setup uses Node.js, workspace dependencies and an environment file. Read .env.example and the relevant entry points before connecting services. Keep any keys restricted to disposable test accounts.
npm install
cp .env.example .envThe original development entry points are:
# Separate terminals, after reviewing environment configuration:
cd packages/backend
npx tsx src/trading.ts
npx tsx src/treasury.ts
# From the repository root in another terminal:
cd packages/frontend
npm run devThe application includes demo-response code, but a demo-mode flag should not be assumed to disable every external integration without tracing the relevant paths. The September 2026 review did not execute these commands or perform a transaction.
A source review on September 7, 2026 inspected the validator and compared the repository's development notes. The cooldown timestamp is held in memory in the reviewed validator; persisted settings do not make that cooldown restart-safe.
No current end-to-end transaction, deployed-contract verification, external audit or cryptographic security review is claimed. Privacy, governance and enforcement guarantees require more evidence than an architecture diagram. Testnet balances and example receipts are not revenue or customer assets.
MIT; see LICENSE.