Onchain Storage

CDN Domains

Irys serves web content through dedicated CDN domains, separate from the core gateway and bundler infrastructure. This architecture improves security, reliability, and static site deployment.

Warning

Always use gateway.irys.xyz/<transaction-id> to link to content. Never link directly to CDN domains — they may be rotated or replaced at any time.

Overview

CDN traffic is served from its own set of domains rather than from irys.xyz. This separation ensures that the bundler, gateway, and documentation are not affected by CDN-level reputation issues. The current CDN domains are:

datasprite-cdn.com

Note

Existing gateway.irys.xyz/<transaction-id> links continue to work. Read-layer paths are automatically mapped to a healthy CDN domain.

Per-Transaction Subdomains

Web content is served using per-transaction subdomains instead of the previous path-based format. Each transaction gets its own subdomain, which gives it its own browser security boundary (origin).

URL Format

The old path-based format:

node.irys.xyz/<transaction-id>

The new subdomain-based format:

<sandbox-id>.<node>.<cdn-domain>.com/<transaction-id>

Why Subdomains

Stable base paths for static sites: Static site frameworks assume a known base path at build time. Under the old path-based model, the base path could not be known until after the transaction was signed and uploaded, forcing developers to do post-hoc rewrites. With the transaction ID in the subdomain, the base path is always the root directory.

Browser security isolation: Under the old model, every static site served through the gateway shared the same origin, meaning they shared the same browser security sandbox. A vulnerability in one site could, in principle, reach across to another. With per-transaction subdomains, each site gets its own origin, making cross-site scripting between sites architecturally impossible.

For Builders

Warning

Do not link directly to CDN domains. Always use gateway.irys.xyz/<transaction-id> in your applications and links. The gateway automatically routes requests to a healthy CDN domain. CDN domains may be rotated or replaced at any time without notice, so direct links to them will break.

For most use cases, no changes are required. Existing links and apps continue to work as gateway.irys.xyz/<transaction-id> paths are mapped automatically.

If you are deploying static sites, you benefit from the subdomain model automatically — your site will be served with a stable root base path and its own browser security boundary.