DefiPanda

Automated Dollar-Cost Averaging (DCA) on Ethereum Sepolia, powered by Chainlink CRE workflows, Rhinestone smart accounts with session keys, and Privy auth.

What It Does

1. User logs in via Privy, gets a Rhinestone smart account.
2. User activates a DCA strategy and signs a session key (one-time approval).
3. CRE workflow runs on a schedule — reads a Chainlink price feed, then POSTs to the backend.
4. Backend executes a USDC → WETH swap via the session key on the user's behalf.

Architecture

Component	Path	Purpose
Web	web/	Next.js frontend + API routes (auth, DCA execution, orchestrator proxy)
CRE	cre/	Chainlink CRE workflow that triggers DCA executions
Postgres	—	Stores users, sessions, DCA positions

Prerequisites

• Docker & Docker Compose
• A Privy app ID
• A Rhinestone API key
• An Ethereum Sepolia RPC URL (e.g. from Alchemy)
• A funded Sepolia private key (for backend signing + CRE)
• CRE CLI credentials (cre login on your host machine)

Quick Start (Docker)

# 1. Clone the repo
git clone <repo-url> && cd defipanda

# 2. Copy the env template and fill in your values
cp .env.docker .env

# 3. Start everything
docker compose up --build -d

# 4. Check logs
docker compose logs -f

The app will be at http://localhost:3000 and pgAdmin at http://localhost:5050.

To stop:

docker compose down        # stop containers
docker compose down -v     # stop + delete volumes (resets DB)

Environment Variables

Copy .env.docker to .env and fill in the required values:

Variable	Required	Description
NEXT_PUBLIC_PRIVY_APP_ID	Yes	Your Privy app ID
NEXT_PUBLIC_PRIVY_RPC_URL	Yes	Sepolia RPC URL
RHINESTONE_API_KEY	Yes	Rhinestone dashboard API key
BACKEND_SIGNER_PRIVATE_KEY	Yes	Backend signer private key
NEXT_PUBLIC_BACKEND_SIGNER_ADDRESS	Yes	Public address of the above key
CRE_ETH_PRIVATE_KEY	Yes	Funded Sepolia key for CRE
POSTGRES_PASSWORD	Yes	Database password
AUTH_SESSION_SECRET	Yes	Random 64-char string

See .env.docker for the full list including optional variables.

Local Development (without Docker)

# Web
cd web
pnpm install
cp .env.example .env.local   # fill in values
pnpm dev                      # http://localhost:3000

# CRE workflow (requires CRE CLI + Bun)
cd cre/dca-workflow
bun install
cre workflow simulate dca-workflow --target=staging-settings

You'll need a local Postgres instance. Set DATABASE_URL in web/.env.local accordingly.

Production Deployment (GCE + Caddy)

For deploying to a Google Compute Engine VM (or any VPS) with HTTPS:

# 1. Clone the repo on the VM
git clone <repo-url> && cd defipanda

# 2. Copy env template and fill in real values
cp .env.docker .env
# Set APP_BASE_URL=https://yourdomain.com in .env

# 3. Start with production overrides (locks down ports)
docker compose -f docker-compose.yml -f docker-compose.prod.yml up --build -d

The prod override (docker-compose.prod.yml) binds the web and pgAdmin ports to 127.0.0.1 only, and removes the Postgres port entirely. A reverse proxy like Caddy handles HTTPS in front:

# /etc/caddy/Caddyfile
yourdomain.com, www.yourdomain.com {
    reverse_proxy localhost:3000
}

To access pgAdmin remotely, use an SSH tunnel:

gcloud compute ssh <vm-name> --zone=<zone> -- -L 5050:localhost:5050
# Then open http://localhost:5050

Project Structure

defipanda/
├── web/              # Next.js app (frontend + API)
├── cre/              # CRE automation (Dockerfile + workflows)
│   └── dca-workflow/ # TypeScript DCA workflow
├── docs/             # Architecture docs
├── specs/            # System specs
├── docker-compose.yml       # Local dev (all ports open)
├── docker-compose.prod.yml  # Production overrides (locked-down ports)
├── .env.docker              # Env template for Docker
└── README.md

License

Apache License 2.0 — see LICENSE for details.