How concordium/concordium-misc-tools works
Project Type and Purpose
• This is a monorepo (“Collection of miscellaneous tools”) containing a set of small, mostly independent command-line applications and light services, each written in Rust (with a few having light front-ends).
• The primary tools listed in the root README are:
• wallet-proxy-load-simulator
• state-compare
• genesis-creator
• kpi-tracker
• Additional utilities/services (not yet listed in root README) include chain-prometheus-exporter, company-id-gui (Tauri/React desktop app), id-verifier (Rust backend + JS frontend), notification-server, recover-id-object, generator, wallet-connect-test-bench, and common Rust SDKs under deps/.
High-Level Architecture
• There is no single “all-in-one” runtime. Instead each tool is a standalone binary (or binary + front end).
• Shared code lives under deps/ (git-submodules for concordium-dapp-libraries and concordium-rust-sdk).
• Each tool may interact with external systems such as:
• A Concordium blockchain node (via its JSON RPC API)
• Wallet-proxy service (for load simulation)
• PostgreSQL database (kpi-tracker) + Grafana (for metrics)
• File system (reading/writing genesis files or WASM artifacts)
• External cloud APIs (notification-server to Google Cloud, etc.)
Main Components
• Shared Libraries (deps/)
• wallet-proxy-load-simulator
• state-compare
• genesis-creator
• kpi-tracker
• chain-prometheus-exporter
• notification-server (with API & service binaries)
• recover-id-object
• id-verifier (Rust backend & JS/ESBuild frontend)
• company-id-gui (Tauri/Rust & React TypeScript)
• generator
• wallet-connect-test-bench (smart-contract lib & front-end)
• External Services:
• Concordium Node (RPC endpoint)
• Wallet-proxy API
• PostgreSQL DB
• Grafana UI
• Google Cloud Pub/Sub (or equivalent)
• Filesystem / S3 / local resource files
Relationships and Data Flows
• wallet-proxy-load-simulator → Wallet-proxy API
• state-compare → Concordium Node RPC (pull block states)
• genesis-creator → Local FS / resource files → Outputs genesis TOML
• kpi-tracker → Node RPC → PostgreSQL → Grafana
• chain-prometheus-exporter → Node RPC → Prometheus endpoint
• notification-server → HTTP clients (API) → DB → Google Cloud
• id-verifier frontend ↔ id-verifier Rust backend → Node RPC
• company-id-gui (Tauri) ↔ local Rust core → Node RPC / Wallet-proxy
• wallet-connect-test-bench front-end ↔ smart-contract lib → Node RPC
• Shared deps/ as a library layer that all Rust binaries link against.
Architectural Patterns & Principles
• Microservice / Polyglot CLI pattern: each tool is its own deployable unit.
• Clear separation of concerns:
• CLI tools focus on a single responsibility (load simulation, state diff, genesis file generation).
• Services with persistent state (kpi-tracker, notification-server) encapsulate API, database, and external integration.
• Reuse of common SDKs (concordium-rust-sdk) via Git submodules.
Detail Level
• For each tool, capture only its key external interactions—no need to show internal module structure.
• For services like kpi-tracker and notification-server, show sub-components if helpful:
• API layer vs Processor vs Database
• Every component from the file tree (especially any crate with a Cargo.toml at top level) is on the map.