---
# System prepended metadata

title: Wasm Split Publish Options

---

# Wasm Split Publish Options

Things I'd like:

- MUST be able to cryptographically verify all content
- Single-file-only implementations without too much extra complexity
- Dedupe common content (static assets, components, modules)
  - Incremental validation of already-acquired content

## Single file content digest

- :+1: Simplest implementation for single file consumer
- :-1: Cannot calculate digest incrementally for split files

## Only publish split form

Publisher splits as desired, publishes just split files.

Content digest is of "root" split file.

- :+1: Relatively simple implementation
- :-1: All consumers must support splicing (no single-file option)

## Canonical split

Specify a canonical process for splitting one file into many.

Content digest is of "root" split file.

- :+1: Allows single &harr; many conversions without metadata
- :-1: Single-file consumers must know how to canonical-split
- :-1: Might be tricky/fragile to spec, e.g. "which data sections get split?"

## Multiple content digest types

Registry may support multiple digests of different content forms, e.g. single file _and_ split file.

- :+1: Avoids the downsides above
- :-1: New attack surface: different forms may not match