VSL Backend Architecture
Last updated
Last updated
The Verifiable Settlement Layer (VSL) integrates with pod, to provide a reliable verification mechanism for claims and proofs. While pod is not a blockchain, it has an interface similar to one, allowing transaction processing and logging.
This document explains how VSL functions in conjunction with pod, detailing the backend architecture that powers this system.
pod operates like a distributed ledger where transactions are submitted, verified, and appended to a log. When a transaction is executed by a majority of nodes, it becomes part of the pod log. This ensures a decentralized and verifiable record of operations.
VSL verification logic is deployed as a precompile within pod. This functions similarly to Ethereum precompiles, where a specific address is called to trigger execution of binary code.
To use VSL, a user must submit a claim along with a proof to the VSL precompile address. The process is as follows:
The claim and proof are sent to the VSL precompile address.
The VSL precompile code executes and verifies the claim and proof.
If verification is successful, the transaction is appended to the pod log.
Once a transaction is stored in pod, the VSL Client subscribes to the VSL channel to receive notifications whenever a claim is verified. Upon verification, the VSL Client retrieves the verified claim and the pod certificate. The pod certificate serves as cryptographic proof that the claim has been validated.
Once verified, the claim and pod certificate can be used by decentralized applications (dApps) that require this information. This ensures that any external system relying on VSL has a tamper-proof record of claim verification.
