Skip to content
All work
At CRASTONICWeb3ArchivedJul 2022 — Aug 2023

Decir DAO

On-chain governance that ordinary members can actually use.

RoleFull-stack Developer
CompanyCRASTONIC
Website
  • Solidity
  • Next.js
  • wagmi
  • The Graph
  • IPFS
  • viem
Not live
Status
Governance
Domain
CRASTONIC
Company

Company timeline

CRASTONIC

Full-stack Developer · Jul 2022 — Aug 2023 · Tokyo, Japan (Remote)

Full-stack engineering for CRASTONIC’s creative / Web3 ecosystem — company platform work and DAO governance products.

Technologies I used

  • TypeScript
  • Next.js
  • React
  • wagmi
  • viem
  • Ethers.js
  • The Graph
  • IPFS

Products & sites from this role

Visit CRASTONIC
01

Overview

Decir made DAO governance more approachable — proposals, voting, and participation with a clearer interface. Built during my time at CRASTONIC. The public site at decir.io is no longer live.

02

The Problem

  • Governance tooling assumed deep crypto fluency and discouraged participation.
  • Members needed clearer proposal and voting flows without drowning in calldata.
  • Gas costs and UX friction concentrated power among a few power users.
03

The Solution

  • Human-readable proposal and voting experiences on a modern web client.
  • Web3 integrations for wallets, proposals, and on-chain settlement paths.
  • Product focus on participation, not just protocol novelty.
04

Architecture

  • Next.js frontend with wallet connectivity for governance actions.
  • On-chain governance primitives paired with off-chain readability aids.
  • Indexed reads for proposal and voting history where needed.
05

Engineering Decisions

Legibility over maximalism

We optimized for understanding proposals, not exposing every protocol knob.

Web client as the product

Most members meet governance through the UI — that surface deserved first-class engineering.

06

Challenges

Usable governance

The hard part was not another voting contract — it was making members confident about what they were approving.

Shipping under Web3 volatility

Product priorities shifted with the market; durable UX decisions mattered more than temporary chain trends.

07

Lessons Learned

  • In Web3, UX is still the adoption bottleneck.
  • Not every shipped product stays online — the engineering lessons still transfer.
  • Archive honestly when a product is no longer live.
08

Tech Stack

Smart Contracts

  • Solidity
  • OpenZeppelin

Frontend

  • Next.js
  • wagmi
  • React

Web3 Infra

  • The Graph
  • IPFS
09

Screenshots

Next case study

Vome
Work with me