Triage API - TrackingChains/TrackingChain GitHub Wiki

The Triage API acts as the gateway between the "Web2" world, which receives the Tracking requests, and the "Web3" world, where these requests will be saved.

Each incoming request must have three pieces of data:

Code: This field represents the key of the dictionary that will be stored on-chain (once converted to byte32). DataValue: This is the value associated with the key (to be converted to bytes). Category: Used to associate a profile. In case the incoming request does not match any profile, it will be rejected. Otherwise, it will be accepted and saved in the Triage table, awaiting processing by the Aggregator Pool Worker, which will place it in the pool of actionable transactions.

The Triage operation does not involve any concurrent processing, allowing for seamless scalability. It can accept requests simultaneously or even create multiple endpoints.