Generator
Manifest
Understand the manifest generated with Doppler bytecode and SDK artifacts.
manifest.json records the identity and hashes for generated artifacts.
Example:
{
"name": "price-feed",
"programId": "fastRQJt3nLdY3QA7n8eZ8ETEVefy56ryfUGVkfZokm",
"admin": "admnz5UvRa93HM5nTrxXmsJ1rw2tvXMBFGauvCgzQhE",
"arch": "v3",
"payloadSize": 8,
"schemaHash": "sha256:...",
"elfSha256": "sha256:..."
}Fields
| Field | Description |
|---|---|
name | Artifact name from the generate command. |
programId | Program address written into generated SDK constants. |
admin | Admin address embedded in generated bytecode. |
arch | sBPF architecture used for bytecode compilation. |
payloadSize | Number of bytes in the fixed-size payload, excluding the 8-byte sequence. |
schemaHash | SHA-256 hash of the normalized payload schema. |
elfSha256 | SHA-256 hash of the compiled bytecode. |
How to Use It
Use the manifest to verify that every generated artifact belongs together:
- deployment scripts can check program ID and admin before deploying
- release tooling can publish the bytecode hash with the SDK version
Do not edit the manifest by hand. Regenerate it when the schema, admin, arch, or bytecode changes.