Skip to content
Ashlane

Guide, manifest format 3, updated 14 May 2026

Signed manifests

Your players trust a build because your key signed it. Ashlane never holds a key that can sign for you, so a compromise of our network cannot change what runs on their machines.

What is signed

The signature covers the canonical JSON of the manifest: title, version, channel, creation time, and every file path with its ordered list of chunk hashes. Chunks themselves are not signed individually; they are verified by hash against the signed list.

{
  "title": "hollowmere",
  "version": "1.8.2",
  "channel": "live",
  "created": "2026-10-22T09:41:07Z",
  "format": 3,
  "files": [
    { "path": "bin/hollowmere.exe", "size": 148230144, "chunks": ["b3:7e1f...", "b3:09ac..."] },
    { "path": "data/world/vale.pak", "size": 2147483648, "chunks": ["b3:c4d2...", "..."] }
  ],
  "signature": { "key": "k-2026-03", "alg": "ed25519", "sig": "base64:Qm9u..." }
}

Set up a key

On Playtest, builds are signed with a shared key and clients accept it. On Studio and above, generate a key pair and register the public half:

ash key generate --name k-2026-03
ash key register hollowmere k-2026-03.pub
# private key stays in ~/.ashlane/keys, mode 0600

On Launch and Enterprise plans, the private key can live in a PKCS#11 hardware module or a cloud key service. ash push --sign-with pkcs11:slot=2 signs through the module and the key never touches the build machine.

How clients verify

  1. Download the manifest for the channel from any edge site.
  2. Check that signature.key is in the list of trusted keys compiled into the launcher or fetched with the title record.
  3. Verify the Ed25519 signature over the canonical manifest bytes.
  4. Reject the manifest if its version is older than the one installed, unless an explicit rollback flag signed by the same key is present.

Rotate without stranding players

Rotation takes two releases. In the first, you add the new public key as also trusted and keep signing with the old key. Once the share of clients on that release passes your threshold (the dashboard shows it), you switch signing to the new key. A third release can then drop the old key.

ReleaseSigns withTrusts
1.8.0k-2026-03k-2026-03
1.8.1k-2026-03k-2026-03, k-2027-01
1.9.0k-2027-01k-2027-01
If a key is lost or exposed, write to security@n74.assetlines.net and mark the message urgent. We can freeze a title within 15 minutes, which stops all new manifests from being served until you confirm.