On-chain DAO Ops

Orchestrate your DAOs, proposals and tasks on top of Arkiv.

This board turns the classic DAO → Proposal → Task structure into on-chain entities using Arkiv. Every decision, task and role is recorded with TTL, advanced queries and real-time events.

• Create DAOs and memberships without exposing keys in the frontend.
• Define proposals with on-chain deadlines and explicit TTL.
• Break your roadmap into trackable tasks, fully queryable through Arkiv.

Start building See how it works

dao: Roxium DAO Ops
  ├─ proposal: "Daily standup at 9:30?"
  │    ├─ task: "Update calendar"
  │    └─ task: "Notify in #dev channel"
  └─ proposal: "New PR review policy"
       └─ task: "Configure rules in GitHub"

storage: Arkiv · Mendoza Testnet
TTL-aware · Queryable · Subscribable

What problem does this board solve?

Many DAOs live in docs, Discord and spreadsheets. Here the goal is to anchor the operational structure in Arkiv, but keep it usable for human beings: create, read and connect DAOs, proposals and tasks from a modern frontend.

DAO-first, on-chain

Each DAO, proposal and task is stored as an Arkiv entity, keeping history and structure at the data layer.

Real TTL and deadlines

Proposals and tasks are created with expiration (TTL), aligning team deadlines with on-chain lifetime.

Safe reads from the frontend

The frontend talks to a backend that signs and writes to Arkiv; from Next.js you only fetch your DAOs/proposals/tasks.

Queries and global board

List all your DAOs, proposals and tasks and build Kanban-style views, boards or custom dashboards.

How it works under the hood

The frontend (Next.js) calls a RoxiumLabs backend via REST.
The backend uses the Arkiv SDK to create entities: dao, user-on-dao, proposal, task.
Each entity is stored with metadata: status, deadlines, ids and relationships (daoKey / proposalKey).
The frontend queries aggregated views: a board per DAO, proposal detail, etc.

All of this without exposing the private key or the Arkiv RPC in the browser. The frontend only sees friendly JSON.

Dev flow

// 1) Create DAO
POST /api/arkiv/daos

// 2) Create proposal for that DAO
POST /api/arkiv/proposals

// 3) Create linked tasks
POST /api/arkiv/tasks

// 4) Read everything in a board
GET /api/arkiv/daos/:daoKey/board