This is the
crashnet configuration of the Kadena Devnet.
The Chainweb Node service is running on this node. Its service
endpoint is available at port 1848, however the public HTTP
API is configured to proxy requests to this port.
This container has a block explorer connected to the devnet.
This container comes with a chainweb-mining-client in
on-demand mode and a mining-trigger service
that triggers mining periodically and also in response to incoming
transactions. You can customise the mining behaviour by setting environment variables.
Wait for this period, in seconds, after receiving a transaction and then mine blocks on the chain where the transaction was received. This period is used to batch transactions and avoid mining a block for each transaction. Increasing this period also makes mining more realistic compared to the public networks (default: 5.0)
The number of blocks to mine faster after transactions; This makes it quicker to get a transaction confirmed. (default: 5)
The period, in seconds, to wait after minting the confirmation blocks of transactions (default: 5.0)
Disable quick mining for confirming transactions. Note that if you want to mint the blocks containing transactions only and no further confirmations, don’t disable this option and use MINING_CONFIRMATION_COUNT=1 instead. (default: false)
Disable periodic mining when the network is idle. Note that this is NOT RECOMMENDED for most cases, since in the absence of mining, the node’s current time will lag behind and transactions will not be accepted. Consider increasing MINING_IDLE_PERIOD instead. (default: false)
The average time, in seconds, it takes to mine blocks and advance the block height by one while the network is idle (i.e. no incoming transactions) (default: 30.0)
Kadena GraphQL uses chainweb-data’s database and various
chainweb-node endpoints to provide a GraphQL interface to the Kadena
blockchain data. The service is running at port 4000,
however the HTTP API is configured to proxy the GraphQL endpoint at the
/graphql route.
Useful pages for interacting with the chainweb-data
service.
The chainweb-data service is configured to use
additional migrations from these folders:
/cwd-extra-migrations/nix/store/1d39bs9vc...les/@kadena/graph//cwd-extra-migrations/The chainweb-data service is configured to listen to
port 1849, however, the public HTTP API is configured to
proxy requests to this port.
These commands are available inside the devnet container:
psql-cwd: Start a psql session as the
chainweb-data service.chainweb-data-fill: Run the fill operation
of chainweb-data.cwtool: A collection of tools that are helpful for
maintaining, testing, and debugging Chainwebkadena: CLI to interact with Kadena and its ecosystem
v1.0.0attach: Attach to the Process Compose management
interface8080: Public HTTP API4000: Graph service port1790: On-Demand Mining API1791: Mining Trigger API1848: Chainweb node’s service port1789: Chainweb node’s p2p API port1849: Chainweb data API port9999: Process Compose management API/data: Persistent data folder/cwd-extra-migrations: chainweb-data’s
extra migrations folderMINING_BATCH_PERIOD:
Waiting period after transaction (default: 5.0)MINING_CONFIRMATION_COUNT:
Number of confirmation blocks (default: 5)MINING_CONFIRMATION_PERIOD:
Confirmation period (default: 5.0)MINING_DISABLE_CONFIRMATION:
Disable confirmation mining (default: false)MINING_DISABLE_IDLE:
Disable idle mining (default: false)MINING_IDLE_PERIOD:
Time to mint when idle (default: 30.0)PC_TUI_ENABLED: When true, enables the
container’s process-compose TUI, when false, logs to
stdout, defaults to true if a TTY is detected or
false otherwise