How dgt-network/dgt-matagami works
DGT-Matagami is a distributed blockchain platform for tokenization and privacy, with hierarchical network clusters and two-level consensus. A user submits transactions through the CLI, REST API, or an application; the validator schedules execution by transaction-family processors, records accepted blocks, and coordinates consensus. The graph also preserves documented topology, dashboard, SDK, cryptographic, and token-family capabilities. Source excerpts are partial, so some documented platform links are shown at subsystem level; uncertain implementation-level connections are omitted.
Main entry points: execution_context.py Transaction execution · engine.py PBFT engine · route_handlers.py REST API · core.py Validator services
Components 20
Access and APIs
Validator and Ledger
- Validator services
CORE/validator/dgt_validator/server/core.py - Transaction execution
CORE/validator/dgt_validator/execution/execution_context.py - State contexts
CORE/validator/dgt_validator/execution/context_manager.py - Block journal
CORE/validator/dgt_validator/journal/block_manager.py - Block store
CORE/validator/dgt_validator/journal/block_store.py
Consensus and Network
- Consensus proxy
CORE/validator/dgt_validator/consensus/proxy.py - PBFT engine
CORE/consensus/dgt_pbft/pbft_engine/engine.py - PBFT oracle
CORE/consensus/dgt_pbft/pbft_engine/oracle.py - Cluster topology
CORE/validator/dgt_validator/gossip/fbft_topology.py
Transaction Families
- BGT processor
CORE/families/bgt_python/dgt_bgt/processor/handler.py - Settings processor
CORE/families/settings/dgt_settings/processor/handler.py - Validator registry
CORE/families/dgt_validator_registry/validator_registry/processor/handler.py
Developer and Security
- Processor SDK
CORE/sdk/python/dgt_sdk/processor/core.py - Consensus SDK
CORE/sdk/python/dgt_sdk/consensus/engine.py - Signing and crypto
CORE/signing/dgt_signing/__init__.py
Other components
- User or app
Connections 25
- User or app → DGT CLI: submits commands
CORE/cli/dgt_cli/main.py - User or app → REST API: submits requests
- User or app → Dashboard: views network
CORE/dashboard/dgt/front/components/Main.jsx - User or app → Bot API: uses bot
- DGT CLI → REST API: sends API requests
- REST API → Validator services: forwards client requests
- Dashboard → REST API: requests blockchain data
- Bot API → REST API: accesses platform
- Validator services → Transaction execution: dispatches execution
- Transaction execution → State contexts: reads and writes state
CORE/validator/dgt_validator/execution/context_manager.py - Transaction execution → Processor SDK: uses processor interface
- Transaction execution → BGT processor: runs family logic
- Transaction execution → Settings processor: runs family logic
- Transaction execution → Validator registry: runs family logic
- Validator services → Block journal: manages blocks
- Block journal → Block store: persists blocks
- Block journal → Consensus proxy: coordinates consensus
CORE/validator/dgt_validator/journal/block_manager.py - Consensus proxy → PBFT engine: dispatches engine
- PBFT engine → PBFT oracle: queries consensus state
CORE/consensus/dgt_pbft/pbft_engine/engine.py - PBFT engine → Cluster topology: uses cluster topology
CORE/consensus/dgt_pbft/pbft_engine/engine.py - PBFT engine → Consensus SDK: implements engine contract
CORE/consensus/dgt_pbft/pbft_engine/engine.py - PBFT engine → User or app: finalizes blocks
- Cluster topology → User or app: organizes clusters
- Signing and crypto → DGT CLI: signs transactions
- User or app → Signing and crypto: uses cryptographic keys