💻Technical Specs

[TECHNICAL SPECS] // Anticapture Architecture

This section outlines the technical architecture of Anticapture, describing the stack, infrastructure, and integration points.

Architecture Overview

Layer	Technology	Purpose
Frontend	Next.js	Web app providing the user interface to display governance security data.
Backend	Nest.js + Prisma	API server for processing requests and handling logic.
ETL / Indexer	Ponder v0.8	Extracts, transforms, and loads blockchain data into the database.
Database	PostgreSQL	Stores governance data, delegations, transactions, and wallets.
Integrations	DefiLlama API	Provides token price feeds (USD) for accurate valuations.
Infrastructure	Vercel / Railway	Vercel hosts frontend; Railway hosts backend and PostgreSQL DB.

---

🖥️ Frontend

• Built with Next.js.

• Optimized for performance and responsiveness.

• Fetches data directly from backend API and database.

⚙️ Backend

• Nest.js API: Manages requests from the frontend and external services.

• Prisma ORM: Provides type-safe database interactions.

• Ponder v0.8 ETL:

  • Extracts governance data from on-chain sources.

  • Transforms raw blockchain data into structured formats.

  • Loads into PostgreSQL for persistence.

🗄️ Database

• PostgreSQL as the primary datastore.

• Maintains all governance-related data:

  • Proposals

  • Delegations

  • Transactions

  • Wallets

🔗 Third-party Integrations

• DefiLlama API for token price feeds.

• Ensures all governance token data is converted into USD for reporting and risk signals.

🛠️ Infrastructure

• Vercel: Hosts the frontend (Next.js).

• Railway: Hosts backend services (Nest.js + Prisma) and the PostgreSQL database.

---

Technical Highlights

• Real-time indexing of DAO proposals and governance actions.

• Separation of concerns across frontend, backend, ETL, and DB.

• Scalable & modular design: New DAOs and integrations can be plugged in easily.

• Open-source by default: Built for collaboration and contribution.