> For the complete documentation index, see [llms.txt](https://airouterprotocol.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://airouterprotocol.gitbook.io/whitepaper/protocol-architecture/delivery-and-verification.md).

# Delivery and Verification

<figure><img src="https://1640383613-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FikmP30ueNFl1f4xaKXqB%2Fuploads%2FKTRP4a1kKJV3GTILqXJK%2Fimage.png?alt=media&amp;token=80e128fc-70de-4e22-aa5b-1858a1efbce3" alt=""><figcaption></figcaption></figure>

Once data has traversed the routing path and reaches its final destination, it is decrypted and verified by the receiving node or application. Verification includes checking cryptographic signatures, validating hash values, and confirming that the message has not been tampered with. The process is automatic, transparent, and verifiable on-chain.

This end-to-end assurance ensures that only the intended recipient can access the message, and that the message’s content is exactly what was originally sent. Because all validation steps are recorded on-chain, it becomes possible to audit any transmission with full confidence in its origin and integrity.