Transaction Generator Worker - TrackingChains/TrackingChain GitHub Wiki

This service can scale and have as many instances as desired. Through a configuration file present in appsettings.json, it is possible to establish which accounts will be associated with the running instance of the worker.

Each configured account will monitor the pool, and when it detects a compatible profile, it will lock it (to notify all other accounts that an operation is already in progress) and perform the on-chain transaction in the associated smart contract and move the status into Pending.

  "Dequeuer": {
    "Accounts": [
      "6F8E591B-6A9C-486E-AB2B-2B42ABBF5B23",
      "5F8E591B-6A9C-486E-AB2B-2B42ABBF5B23",
      "4F8E591B-6A9C-486E-AB2B-2B42ABBF5B23",
      "8F8E591B-6A9C-486E-AB2B-2B42ABBF5B23",
      "9F8E591B-6A9C-486E-AB2B-2B42ABBF5B23"
    ]
  }

In this example, we have associated 5 accounts with the instance, which should be listed in the Accounts table.

---

Once the transaction has been sent, the associated transaction hash will be saved. This way, the service will consider its operation completed without waiting for on-chain block confirmation.