Configuration

Currently, the QAN daemon (qand) accepts a TOML config file which has the following configuration variables:

  • rpc_addr where the RPC should bind to, accepts an ipv4:port pair
  • data_dir where the ledger should be saved. Make sure to have plenty of space here as QAN's ledger is especially large!
  • boostrap_addr the initial peer we should use to get more peers from. In public networks it's discarded after having enough peers, in a private (PoA) setting this is the message broker node.
  • nats_path an optional flag that's only used in the PoA setting, pointing to the NATS binary that handles our overlay network.
  • chain_id a number indicating which chain (testnets, mainnet etc) should the node be operate on
  • genesis_path path to an ethereum-style JSON file containing the genesis block:
{
  "alloc": {
    "3017cdacfdd62c18258d0ecec94a9d625ec68d89": {
      "balance": "3735928559"
    },
    "34afd10b29b9b326ac829666fbb567a06314004a": {
      "balance": "3735928559"
    },
    "438fd045604618dd63f32e8308d4d666ac7620c2": {
      "balance": "3735928559"
    },
    "439c8d610f4a09988eee2f2b8594a064bd6565f8": {
      "balance": "3735928559"
    },
    "5ae8549d6a278ac289f773ed14fe41b1aef54eca": {
      "balance": "3735928559"
    },
    "5db9f9b0fcbccce9fcc54eada399237496b4154b": {
      "balance": "3735928559"
    },
    "863d6d60f3bd13589733c4c3857cc50701f10731": {
      "balance": "3735928559"
    },
    "9285c8d6a314d9bd579fe5d3012151d4cf6d6977": {
      "balance": "3735928559"
    },
    "af08e7a5d727e8974b4f479c6325fafbd50b7dda": {
      "balance": "3735928559"
    },
    "fa131cbfa8703f5a3dd46089807552012ddf5587": {
      "balance": "3735928559"
    },
    "52c4ba9a2237cc9e03192cd448e8e5e9a17211dd": {
      "balance": "3735928559"
    }
  },
  "coinbase": "0",
  "difficulty": "0",
  "extraData": "dedicato imperatum ultra articulo mortis",
  "gasLimit": "10000000",
  "gasUsed": "0",
  "mixHash": "0",
  "nonce": "0",
  "number": "0",
  "parentHash": "0000000000000000000000000000000000000000000000000000000000000000",
  "timestamp": "1592997601671"
}