How does Kaspa's ATAN let a new node verify transaction history without trusting the node it syncs from?

When a new, untrusting ATAN joins the network, it independently recomputes a cryptographic value called a SequencingCommitment for every block and checks it against what the synced node provided — so it never has to take the data on faith. The synced node first sends the new node a starting pruning-point hash and its SequencingCommitment; the new node confirms that pruning point with its own Kaspa full node. Then, for each chain block that follows, the new node recomputes the expected SequencingCommitment by hashing together the parent block's commitment and a Merkle root of the accepted transactions. If the recomputed value matches what the synced node sent, the transaction list is verified as authentic. This cryptographic bootstrapping process means anyone running an ATAN can trust the transaction history they receive without trusting any individual node in the network.