Irys primary sources — 2026-05-09

Classification takeaway

Irys is best cataloged as programmable storage-and-execution infrastructure rather than just another decentralized storage network. The key reusable mechanism is the protocol’s multi-ledger data lifecycle plus a native execution layer that is supposed to compute directly on stored data. The main analytical value is that retention class, proof of data ingress, storage-oriented consensus, and computation are all exposed as first-class design variables.

Primary sources reviewed

1. Main site — https://irys.xyz/

   • Gives the cleanest short definition of the project.
   • Official framing: a blockchain that stores large volumes of data onchain, lets smart contracts use it directly, and proves the data remains available over time.

2. Core-features page — https://irys.xyz/core-features

   • Useful for the project’s own explanation of why it calls itself a datachain rather than just a storage layer.
   • Search-result snippet from this official page states that IrysVM is a high-performance, EVM-compatible execution layer designed to work natively with onchain data.

3. Official whitepaper — https://irys.xyz/assets/IrysWhitepaper.pdf

   • Strongest primary source for mechanism-level classification.
   • The title explicitly calls Irys A Programmable Datachain for Verifiable Storage and Onchain Computation.
   • Even where full text extraction was limited in this environment, the document metadata and outline were recoverable and especially useful: multi-ledger partition lifecycle, PoW/S consensus, VDF synchronization, ingress proofs, programmable-data pricing, term vs. permanent fees, and Submit Ledger expiry/payment processing are all first-order sections.
   • Saved locally as irys-whitepaper.pdf.

4. Official docs root — https://docs.irys.xyz/

   • Canonical docs surface, though it is heavily client-rendered in this environment.
   • Important mainly as the official documentation root and canonical namespace for the protocol docs.

5. Official docs / ledgers page — https://docs.irys.xyz/protocol/ledgers

   • Search-result snippet from this official docs page is analytically important.
   • It describes the Publish Ledger as containing only data provably uploaded to the network through the Submit Ledger system, producing a ledger without holes and enabling reliable retrieval for programmable-data computations.

6. Alternative official/community docs surface — https://docs.irys.club/

   • Search-result snippet usefully summarized the Submit Ledger → Publish Ledger progression: data first enters the Submit Ledger for validation, then is promoted to the Publish Ledger for permanent trustworthy storage.
   • Treated as supplemental to the canonical docs.irys.xyz site, not a replacement.

7. GitHub org — https://github.com/Irys-xyz

   • Confirms a live implementation and documentation surface.
   • Helpful for establishing that the project is more than a marketing site or static whitepaper.

8. Core repo — https://github.com/Irys-xyz/irys

   • Repository README is sparse for protocol design but confirms an active codebase and names the system a multi-ledger storage blockchain.

9. Docs repo — https://github.com/Irys-xyz/Irys-docs

   • Confirms an official docs repository even though the published docs are JS-heavy for this environment.

Whitepaper / technical-doc status

• The official whitepaper has been saved locally as irys-whitepaper.pdf.
• The docs site is currently harder to extract from than the whitepaper metadata and search snippets, so this entry leans more heavily than usual on the official whitepaper plus canonical-doc URLs.

Why it stays in the active corpus

• Gives a useful comparison class for storage systems that try to make stored data directly computational rather than merely retrievable.
• Sharpens the distinction between archival storage, programmable storage, and a true datachain where retention classes and finalized availability are part of ledger design.
• Adds a helpful mechanism example where payment distribution, ingress proofs, and ledger promotion are core trust surfaces instead of background implementation details.