# Alia Tokens Equal Batches of NMT Calculations

Transactions are memorialized with hashing at each step. ALIA employs a lightweight validation mechanic which stems from logging the transactional work at every stage to ensure transparency.

Computations are batched by the Parameter Server and distributed to the compute cluster. A hash record representing the job variables for the entire batch is created and transmitted to the Head Node.

The Head Node selects an available node in rotating order and appends distribution information and additional meta-information about the Compute Node. The Head Node appends the information to the log and distributes the log and work to the node.

A Compute Node receives a hash of the original instructions, a work order from the Head Node, and a batch of computations for processing. It discovers the mathematical solution for each batch calculation and appends the solution to the log.

The Compute Node returns the log history to the Head Node. The Head Node verifies the original instructions received, the instructions it sent, and the response from the Compute Node. If all hashing is equal then a log of the entire process is returned to the Parameter Server with the solution to the batched equations.

The Parameter Server receives the updated log with a hash representing each step in the transaction process. It then verifies hashes of the original job instruction, the instructions distributed by the head node and each positive response from the Compute Nodes. If all hashes match, then an approval hash is added as a hashed summation. Each step of the NMT batch calculation is sent to the Compute Node as a full transaction.

The blockchain logic stores the appropriate amount of batches until a group of batches equal to one ALIA Token then written to a block to undergo validation.