# Worker architecture The two currently supported platforms (Ethereum and Solana) follow a similar process: 1. Application server becomes aware of a block/slot 2. Application server classifies Fluid Asset interactions in the block/slot as either * a standard Fluid Asset transfer * an application transaction utilising a Fluid Asset (e.g. a swap on Uniswap, Saber use) 3. For application transactions, the Application server decodes the interaction and attaches a decorated structure containing information such as its associated fees 4. Application server sends all Fluid Asset interactions to the Worker Server 5. Worker computes the current state of the TRF using every available variable (fees paid for each application used, past state history, averages if there are any) and sends it to the Worker client queue 6. Worker optionally computes more variables after fetching data (this system is disintermediated since some upstream dependencies are unreliable and can dilute the calculation in the previous stage) 7. Worker either sends the transaction depending on the backend (Solana) or sends it to the final stage which aggregates the batched payouts (Ethereum) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.fluidity.money/docs/developers/fluidity-architecture/worker-architecture.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.