How opening-line/symbol_book_v3_demo_dao works
Project type and purpose
• This is a full-stack blockchain web application: a demo DAO (Decentralized Autonomous Organization) built on the Symbol blockchain.
• The README calls it “次世代組織のための実用 Symbol ブロックチェーンアプリケーションのデモアプリ(DAO)”, indicating it’s both a frontend SPA for users and a backend that wraps Symbol SDK calls.
File structure
• Top level:
• compose.yml (Docker-compose for client & server)
• client/ (React + TypeScript + Vite)
• server/ (Node.js + TypeScript + REST routes + blockchain functions)
• client/: typical Vite + React structure
• src/pages (per-feature pages: DAO, Exchange, GovernanceVoting, etc.)
• src/components (Layout, Header, SideMenu, ThemeContext)
• src/utils/config.ts
• server/:
• src/routes (HTTP endpoints, grouped by admin/exchange/governance/home/limited)
• src/functions (business logic for transactions: createMosaic, transfer, signTransaction, etc.)
• src/info (read-only queries: getAccountInfo, getMetadataInfoByQuery, etc.)
• src/utils (config, address encoding, metadata helpers)
• No relational database: data persistence and state live on the Symbol blockchain network.
README
• Describes how to set up .env (with PRIVATE_KEY), start server and client.
• No built-in database; all data operations use Symbol SDK and network calls.
Elements
• External service (orange cloud for Symbol network)
• Major modules: client/src/pages (feature modules), server/src/routes (endpoint groups), server/src/functions (logic units), server/src/info (query modules).
Final recommendations
• Major feature groups (DAO, Exchange, Governance, Point, Reward) as sub-areas or clusters within the frontend and backend.
• Do not omit the blockchain; treat it as a first-class component rather than a database.