Aligned Layer primary sources — 2026-05-09

Classification takeaway

Aligned Layer is best cataloged as proof-verification and aggregation infrastructure anchored to Ethereum rather than as a zkVM, a generic prover marketplace, or an independent verification chain. The key reusable mechanism is the combination of a batcher, data-service commitments, a restaked operator set that verifies proofs off-EVM, and a BLS-signature aggregator that posts quorum-backed results to Ethereum. The practical analytical value is that it exposes where trust sits when verification is outsourced to an AVS-style operator layer instead of happening directly inside Ethereum contracts.

Primary sources reviewed

1. Docs overview / About Aligned — https://docs.alignedlayer.com/ and https://docs.alignedlayer.com/introduction/0_about_aligned.md

   • Best high-level statement of Aligned’s positioning as a vertically integrated stack for a verifiable internet.
   • Useful mainly for classification and for distinguishing the verification layer from the wider product ambition.

2. Proof Verification Layer — https://docs.alignedlayer.com/architecture/1_proof_verification_layer.md

   • Most important mechanism page.
   • Describes the batcher → data service → operator verification → BLS aggregation → Ethereum settlement flow.
   • Important because it shows the exact place where trust and quorum assumptions enter the design.

3. Aggregator — https://docs.alignedlayer.com/architecture/1_proof_verification_layer/5_aggregator.md

   • Short but useful confirmation that an aggregator collects operator BLS signatures and submits task responses once quorum is reached.
   • Reinforces that Aligned’s receipt path depends on an operator-signature aggregation layer.

4. Proof Aggregation Service — https://docs.alignedlayer.com/architecture/2_aggregation_mode.md

   • Important for distinguishing the second product line from the fast verification layer.
   • Shows that Aligned supports a separate recursive-proof compression path rather than only AVS-style verification.

5. Supported verifiers — https://docs.alignedlayer.com/architecture/0_supported_verifiers.md

   • Useful for understanding Aligned as proof-system-agnostic infrastructure.
   • Shows current support across gnark Groth16/Plonk, SP1, Risc0, Circom, and Mina, with other systems planned.

6. Docs sitemap — https://docs.alignedlayer.com/sitemap.md

   • Helpful inventory of the public documentation surface, including operator docs, local setup guides, contract addresses, and aggregation-mode guides.
   • Good sanity check that the project has more than a single landing page.

7. Official site — https://alignedlayer.com/

   • Currently provides relatively little readable mechanism detail through static extraction, but it is still the canonical project domain.
   • Useful mostly as the main identity anchor.

8. Official whitepaper — https://whitepaper.alignedlayer.com/

   • Canonical technical paper for the project.
   • Saved locally as aligned-layer-whitepaper.pdf for future deeper comparisons.

9. Official GitHub repo / README — https://github.com/yetanotherco/aligned_layer and https://raw.githubusercontent.com/yetanotherco/aligned_layer/main/README.md

   • Confirms a live open-source repo and, importantly, notes the project is currently testnet only.
   • Useful maturity/context signal when comparing Aligned to more production-focused proving infrastructure.

Why it stays in the active corpus

• Gives a clean comparison class for the proof-verification layer of the ZK stack, as distinct from proof generation, zkVM design, or proving marketplaces.
• Helps sharpen comparison between AVS-style verification, dedicated verification chains, and recursive aggregation services.
• Useful for future cluster work on where authority sits in the proving stack: operator-set admission, quorum rules, verifier support, batching defaults, and Ethereum receipt semantics.