Dev only. This package is a local development fixture — it accepts any S3 credentials, carries no auth or metrics, and only ships an ephemeral in-memory backing. It is not meant for production at this time; production chains are published to real object storage (S3/R2) behind the standard sub-domain layout.

Serves an XL1/XYO published-chain layout from a single origin using subfolders (/blocks, /state, /indexes) instead of the production sub-domains. The subfolders are S3 buckets on an embedded S3-compatible server (s3rver), so the existing ariesi xyo s3 ... publish commands write into it unchanged while readers (RestBlockViewer, curl) fetch the same layout paths over plain HTTP. The server also accepts an explicit TLS certificate and key. The aries chain up --ssl auto command configures those inputs with a locally trusted macOS development certificate and advertises https://chain.aries.test:8791.

Backings (CHAIN_BACKING): memory (ephemeral temp directory, wiped on shutdown). disk and s3 are planned.

The daemon bin (dist/bin/chainServer.mjs) is spawned by aries chain up; env config: CHAIN_PORT (default 8791), HOST (default 127.0.0.1), CHAIN_BACKING (default memory), CHAIN_PUBLIC_HOST, CHAIN_TLS_CERT, and CHAIN_TLS_KEY.