How pokt-network/poktroll works
Project type and purpose
• This is a full-stack blockchain node implementation (Pocket Network Shannon upgrade) built on the Cosmos SDK (CometBFT) in Go. It comprises:
• A core application (“pocketd”) exposing an ABCI app and gRPC/REST APIs
• A collection of Cosmos-SDK modules (x/application, x/gateway, x/session, x/service, x/supplier, x/proof, x/migration, x/tokenomics, x/shared)
• Client libraries (pkg/client) for external consumers
• CLI tooling (cmd/pocketd, cmd/flags, cmd/logger, cmd/morse_keys)
• Testing & dev-ops (e2e, load-testing, localnet Kubernetes manifests, Tiltfile, Makefiles)
• Documentation (docusaurus)
File structure
• Top-level “cmd” contains the node binary and CLIs
• “app” holds the ABCI wiring: app.go, keepers, genesis, upgrades
• “x/…” subdirectories each implement one Cosmos SDK module
• “api” contains auto-generated GRPC handlers for module RPCs
• “pkg” provides reusable components: client SDK, cryptography, relayer, caching, telemetry, retry logic
• “proto” houses all .proto definitions and codegen config
• “e2e” and “load-testing” drive BDD and stress tests
• “localnet” contains Kubernetes charts & Grafana dashboards for local cluster
• “tools” and “scripts” deliver helpers (migration scripts, docs-generation, load-test manifests)
Additional insights from README
• It confirms use of Go v1.23, gRPC (Protobuf), and the Shannon network upgrade
• Documentation is externalized to Docusaurus, deployed at dev.poktroll.com
Elements
• Block flow (CometBFT → ABCI → Modules → DB)
• API calls (SDK/CLI → gRPC/REST → Modules)
• Event streaming (Modules → Pulsar → Relayer/Telemetry)
• Blue for infra (Consensus, DB, Pulsar, Kubernetes)
• Green for application modules
• Orange for API/SDK/CLI
• Gray for testing/devops