DGT DOCS
  • 1. INTRODUCTION
    • 1.1 Executive Summary
    • 1.2 Why DGT
    • 1.3 Distributed Ledgers Technology
      • 1.3.1 Decentralization approach
      • 1.3.2 Consensus Mechanism
      • 1.3.3 Transactions
      • 1.3.4 Layered Blockchain Architecture
      • 1.3.5 Tokenomics
      • 1.3.6 Web 3 Paradigm
      • 1.3.7 Common Myths about Blockchain
    • 1.4 The DGT Overview
      • 1.4.1 Platform Approach
      • 1.4.2 DGT Functional Architecture
      • 1.4.3 Technology Roadmap
    • 1.5 How to create a Solution with DGT Networks
    • 1.6 Acknowledgments
  • 2. REAL WORLD APPLICATIONS
    • 2.1 Case-Based Approach
      • 2.1.1 DGT Mission
      • 2.1.2 The Methodology
      • 2.1.3 Case Selection
    • 2.2 Supply Chain and Vertical Integration
      • 2.2.1 Logistics Solution for Spare Parts Delivery
      • 2.2.2 DGT Based Solution for Coffee Chain Products
    • 2.3 Innovative Financial Services
      • 2.3.1 Crowdfunding Platform
      • 2.3.2 Real World Assets Tokenization
      • 2.3.3 Virtual Neobank over DGT Network
      • 2.3.4 DGT based NFT Marketplace
    • 2.4 Decentralized Green Energy Market
      • 2.4.1 Peer To Peer Energy Trading
      • 2.4.2 DGT based Carbon Offset Trading
    • 2.5 B2B2C Ecosystems and Horizontal Integration
      • 2.5.1 KYC and User Scoring
      • 2.5.2 Decentralized Marketing Attribution
      • 2.5.3 Case Decentralized Publishing Platform
      • 2.5.4 Value Ecosystem
    • 2.6 More Cases
  • 3. DGT ARCHITECTURE
    • 3.1 Scalable Architecture Design
      • 3.1.1 High Level Architecture
      • 3.1.2 DGT Approach
      • 3.1.3 Unique contribution
      • 3.1.4 Component Based Architecture
    • 3.2 Performance Metrics
    • 3.3 Network Architecture
      • 3.3.1 Nework Architecture in General
      • 3.3.2 Network Identification
      • 3.3.3 H-Net Architecture
      • 3.3.4 Transport Level
      • 3.3.5 Segments
      • 3.3.6 Static and Dynamic Topologies
      • 3.3.7 Cluster Formation
      • 3.3.8 Node Networking
      • 3.3.9 Permalinks Control Protocol
    • 3.4 Fault-Tolerant Architecture
      • 3.4.1 Introduction to Fault Tolerance
      • 3.4.2 F-BFT: The Hierarchical Consensus Mechanism
      • 3.4.3 Cluster Based Algorithms
      • 3.4.4 Arbitrator Security Scheme
      • 3.4.5 Heartbeat Protocol
      • 3.4.6 Oracles and Notaries
      • 3.4.7 DID & KYC
    • 3.5 Transactions and Performance
      • 3.5.1 Transaction Basics
      • 3.5.2 Transaction Processing
      • 3.5.3 Transaction and block signing
      • 3.5.4 Transaction Families
      • 3.5.5 Transaction Receipts
      • 3.5.6 Smart Transactions
      • 3.5.7 Private Transactions
      • 3.5.8 Multi signature
    • 3.6 Data-Centric Model
      • 3.6.1 Data layer overview
      • 3.6.2 Global State
      • 3.6.3 Genesis Record
      • 3.6.4 Sharding
      • 3.6.5 DAG Synchronization
    • 3.7 Cryptography and Security
      • 3.7.1 Security Architecture Approach
      • 3.7.2 Base Cryptography
      • 3.7.3 Permission Design
      • 3.7.4 Key Management
      • 3.7.5 Encryption and Decryption
      • 3.7.6 Secure Multi Party Computation
      • 3.7.7 Cryptographic Agility
      • DGTTECH_3.8.4 Gateway Nodes
    • 3.8 Interoperability
      • 3.8.1 Interoperability Approach
      • 3.8.2 Relay Chain Pattern
      • 3.8.3 Virtual Machine Compatibility
      • 3.8.4 Gateway Nodes
      • 3.8.5 Token Bridge
    • 3.9 DGT API and Consumer Apps
      • 3.9.1 Presentation Layer
      • 3.9.2 Application Architecture
    • 3.10 Technology Stack
    • REFERENCES
  • 4. TOKENIZATION AND PROCESSING
    • 4.1 Introduction to Tokenization
      • 4.1.1 DGT Universe
      • 4.1.2 Driving Digital Transformation with Tokens
      • 4.1.3 Real-World Tokenization
      • 4.1.4 Key Concepts and Definitions
    • 4.2 Foundations of Tokenization
      • 4.2.1 Definition and Evolution of Tokenization
      • 4.2.2 Tokenization in the Blockchain/DLT Space
      • 4.2.3 The Tokenization Process
      • 4.2.4 Tokenization on the DGT Platform
      • 4.2.5 Regulatory and Legal Aspects of Tokenization
      • 4.2.6 Typical Blockchain-Based Business Models
    • 4.3 The DEC Transaction Family
      • 4.3.1 DEC Transaction Family Overview
      • 4.3.2 DEC Token Features
      • 4.3.3 DEC Token Protocol
      • 4.3.4 DEC Account Design
      • 4.3.5 DEC Transaction Family Flow
      • 4.3.6 DEC Commands
      • 4.3.7 DEC Processing
      • 4.3.8 Payment Gateways
    • 4.4 Understanding Secondary Tokens
      • 4.4.1 The different types of tokens supported by DGT
      • 4.4.2 How secondary tokens are produced
  • 5. EXPLORING TOKENOMICS
    • 5.1 Introduction
      • 5.1.1 What does tokenomics mean?
      • 5.1.2 Goals of Building the Model for DGT Network
      • 5.1.3 Tokens vs Digital Money
      • 5.1.4 The Phenomenon of Cryptocurrency
      • 5.1.5 Basic Principles of Tokenomics
      • 5.1.6 AB2023 Model
    • 5.2 Node & User Growth
      • 5.2.1 Node Ecosystem
      • 5.2.2 User Growth and Retention Modeling
    • 5.3 Transactions
      • 5.3.1 Transaction Amount Components
      • 5.3.2 Shaping the Transaction Profile: A Three-pronged Approach
      • 5.3.3 Calculation of Transaction Number
    • 5.4 Network Performance Simulation
      • 5.4.1 Endogenous Model
      • 5.4.2 Network Entropy
      • 5.4.3 Network Utility
    • 5.5 Token Supply Model
      • 5.5.1 Introduction to Supply and Demand Dynamics
      • 5.5.2 Token distribution
      • 5.5.3 Supply Protocol
      • 5.5.4 Token Balance and Cumulative Supply
    • 5.6 Token Demand Model
      • 5.6.1 Node-Base Demand
      • 5.6.2 Transaction-Based Token Demand
      • 5.6.3 Staking Part Modeling
      • 5.6.4 Total Demand
    • 5.7 Token Price Simulation
      • 5.7.1 Nelson-Siegel-Svensson model
      • 5.7.2 The Price Model
    • 5.8 Decentralization Measurement
      • 5.8.1 Active Node Index
      • 5.8.2 Node Diversity in Hybrid Networks
      • 5.8.3 Token distribution
      • 5.8.4 Integral Calculation of Decentralization Metric
    • 5.9 Aggregated Metrics
      • 5.9.1 Transaction Throughput: Evaluating Network Performance and Scalability
      • 5.9.2 Market Capitalization: A Dimension of Valuation in Cryptocurrency
      • 5.9.3 Total Value Locked (TVL): A Spotlight on Network Engagement and Trust
  • 6. ADMINISTRATOR GUIDE
    • 6.1 Introduction
      • 6.1.1 Administrator Role
      • 6.1.2 Platform sourcing
      • 6.1.3 DGT Virtualization
      • 6.1.4 Using Pre-Built Virtual Machine Images
      • 6.1.5 Server Preparation
      • 6.1.6 OS Setup and initialization
    • 6.2 DGT CORE: Single Node Setup
      • 6.2.1 Launch the First DGT Node
      • 6.2.2 Dashboard setup
      • 6.2.3 Nodes Port Configuration
      • 6.2.4 Single Node Check
    • 6.3 DGT CORE: Setup Private/Public Network
      • 6.3.1 Network launch preparation
      • 6.3.2 A Virtual Cluster
      • 6.3.3 A Physical Network
      • 6.3.4 Attach node to Existing Network
    • 6.4 DGT Dashboard
    • 6.5 DGT CLI and base transaction families
    • 6.6 GARANASKA: Financial Processing
      • 6.6.1 Overview of DGT’s financial subsystem
      • 6.6.2 DEC emission
      • 6.6.3 Consortium account
      • 6.6.4 User accounts
      • 6.6.5 Payments
    • 6.7 Adjust DGT settings
      • 6.7.1 DGT Topology
      • 6.7.2 Manage local settings
    • 6.8 DGT Maintenance
      • 6.8.1 Stopping and Restarting the Platform
      • 6.8.2 Backing up Databases
      • 6.8.3 Network Performance
      • 6.8.4 Log & Monitoring
Powered by GitBook
On this page
  1. 6. ADMINISTRATOR GUIDE

6.5 DGT CLI and base transaction families

Previous6.4 DGT DashboardNext6.6 GARANASKA: Financial Processing

Last updated 1 year ago

Each node has a CLI (Command Line Interface) service as a component. To run the CLI, you need to access the bash shell inside the container:

docker exec -it shell-dgt-c1-1 bash

Inside, it is possible to enter commands regarding the node’s status and the testing families of transactions. Different families of commands may have some differences in options; here is a general view based on the dgt transaction family:

#

Command

Description

Example

1

dgt Family

A set of commands that provide basic information about the node and its environment, as well as a way to access the most important common functions.

1.1

dgt settings list

Displays a list of settings for the node and current network.

Since multiple nodes can be running in a container, a clarification in the form of a url flag is needed

dgt settings list --url http://api-dgt-c1-1:8108

1.2

dgt batch list

Displays a list of transaction batches: BATCH_ID, the number of transactions in a batch and signatures.

Information can be exported to a file with the -F option and output redirection

dgt batch list –url http://api-dgt-c1-1:8108

1.3

dgt batch status

Status of the given batch with BATCH_ID shown (obtained, for example, from the dgt batch list command)

dgt batch status 3044022052d2468ef…

1.4

dgt batch submit

The command sends one or several batches to the validator.

A batch is a binary file, coded in BatchList protobuf, represented by a FILENAME file.

1.5

dgt block list

Output of packed blocks as a list in NUM format:

BLOCK_ID; BATS; TXNS; SIGNER

1.6

dgt block show

Shows the contents of a block, displayed on command

dgt block show [-h] [--url URL] block_id

dgt block show 102678a34f…

1.7

dgt keygen

Key pair generation (private and public). As a result, files are created in the specified directory:

<key_dir>/<key_name>.priv and <key_dir>/<key_name>.pub

Command format: dgt keygen [-h] [--key-dir KEY_DIR] [--force] [-q] [key_name]

-q – don’t display output

--key-dir KEY_DIR – directory where keys are generated

--force – files are overwritten

dgt keygen NEWKEY

creates NEWKEY.priv and NEWKEY.pub in the /root/.dgt/keys/ catalogue by default

1.8

dgt peer list

List of addresses of connected validators. If there are no connected nodes, an empty string is displayed.

dgt peer list

1.9

dgt state list

Printing entries in the ledger, returns the corresponding addresses in the format ADDRESS; SIZE;DATA

dgt state list

1.10

dgt state show

The command outputs a specific ledger entry for the given address:

dgt state list [-h] [--url URL[-F {csv,json,yaml,default}] [--head HEAD][subtree]

Here:

address – address in DAG;

--head HEAD - specify the id of the block to set as the chain head

dgt state show

1.11

dgt transaction list

Returns a list of transactions for the given node. Command format:

transaction list [-h] [--url URL] [-u USERNAME[:PASSWORD]] [-F {csv,json,yaml,default}]

Default information output: Transaction_ID; Family; Vers,Size;Payload

dgt transaction list

1.12

dgt transaction show

Displays information about a specific transaction, requires TRANSACTION_ID:

dgt transaction show [-h] [--url URL] [-k KEY] [-F {yaml,json}] transaction_id

--url URL identify the URL of the validator's REST API

-k KEY, --key KEY displays a single property from the block or header

dgt transaction list

1.13

dgt dag show integrity

dag integrity check.

dgt dag show integrity –url URL

1.14

dgt dag show val

List of vertices to join

dgt dag show val –url URL

The number of the block:

the block’s ID fragment (leaves for new blocks to join).

For example,

0:30450221

112:30440220

2

xcert Family

Management of node certificates. Several scenarios for joining a node to the network may require the creation of a relevant certificate.

2.1

xcert set

Creation of a new certificate:

Edit the PROJECT-FOLDER/etc/certificate.json file

Generate a certificate with the command:

xcert --user USER --url URL --keyfile KEYFILE --wait [WAIT] --before BEFORE --after AFTER –cb CRYPTO_BACK, here:

xcert set /project/dgt/etc/certificate.jsomcn --user /root/.dgt/keys/root.priv

2.2

xcert list

Output of previously generated certificates. Command format:

xcert list --url URL --keyfile KEYFILE --cb CRYPTO_BACK

xcert list

2.3

xcert show

Prints the specified certificate to the screen. Format:

xcert show name

The public key is used as the name (also accessible in the output of the xcert list command)

xcert show 3056301006072a8648ce3 ... cabfe613909acb6c5791cbfebd0ef5b8630fa6c9b3182

2.4

xcert upd

Certificate renewal, specified in the format:

xcert upd VALUE --url URL --keyfile KEYFILE --before BEFOREDAYS --after AFTERDAYS

Here:

VALUE – link to the JSON – file with parameters;

--url – node URL

--keyfile – link to a certificate with a private key

--before – the number of days before today’s date that allow the certificate to be considered valid

--after – the link to the number of days after, which allow the certificate to be considered valid

3

dgtset

Topology transaction family

3.1

dgtset genesis

Performed automatically when launching a node with a -G parameter, does not require repetition

âš  NOT RECOMMENDED FOR USE OUTSIDE OF DEVELOPMENT

3.2

dgtset proposal

This command is used only when launching a node and creates a command file (batch) for recording the genesis block – including the topology

âš  NOT RECOMMENDED FOR USE OUTSIDE OF DEVELOPMENT

3.3

dgtset topology

Displays the current topology: dgtset topology list –url URL

The statistic topology is given in the CORE/etc/dgt.net.static file. It is loaded into the genesis block during the network initialization and is modified by topology commands

4

bgt Family

Test family of transactions; provides the creation of wallets and the transfer of abstract bgt tokens to them

4.1

bgt set

Creation of a new wallet with a command format of:

bgt set name value –url URL –keyfile KEYFILE –wait [WAIT]

4.2

bgt inc

Increasing the volume of tokens in the wallet:

bgt inc name value --url URL --keyfile KEYFILE –wait [WAIT]

bgt inc WAL1 50 –url http://api-dgt-c1-1:8108

4.3

bgt dec

Reducing the number of tokens in the wallet:

bgt inc name value --url URL --keyfile KEYFILE –wait [WAIT]

bgt dec WAL1 50 –url http://api-dgt-c1-1:8108

4.4

bgt trans

Transferring tokens from wallet to wallet:

bgt trans name value to --url URL --keyfile KEYFILE --wait [WAIT]

4.5

bgt show

Shows the value of BGT Tokens for a given wallet: bgt show --url URL

bgt show --url http://api-dgt-c1-1:8108

4.6

bgt list

Displays all available wallets.

bgt list --url URL

bgt list --url http://api-dgt-c1-1:8108

dgt batch list –url -F > 1.csv

--url

dgt batch submit --url -f FILENAME

dgt block list --url

--url

--url

--url

--url 00000034c8768f9d68b36c758…

--url

--url 023567df4e2345…

dgt dag show integrity –url

dgt dag show val --url

xcert upd /project/bgx/etc/certificate.json --url --keyfile /root/.dgt/keys/root.priv --before 245 –after 164

dgtset topology list –url

bgt set WAL1 1000 –url

bgt trans WAL1 50 WAL2 –url

http://api-dgt-c1-1:8108
http://api-dgt-c1-1:8108
http://api-dgt-c1-1:8108
http://api-dgt-c1-1:8108
http://api-dgt-c1-1:8108
http://api-dgt-c1-1:8108
http://api-dgt-c1-1:8108
http://api-dgt-c1-1:8108
http://api-dgt-c1-1:8108
http://api-dgt-c1-1:8108
http://api-dgt-c1-1:8108
http://api-dgt-c1-1:8108
http://api-dgt-c1-1:8108
http://api-dgt-c1-1:8108
http://api-dgt-c1-1:8108
http://api-dgt-c1-1:8108