Phala gateway deployment manifest, digest-pinned.
| Source ref (input) | main |
| Commit | 11e792431e63c83c0077adab9b035befa5b91781 |
| Gateway image | ghcr.io/0gfoundation/0g-pc-e2ee-gateway@sha256:23d5524cf8c085e3e74edcfa6520db852e9c7ca33b1a992df4564dda2123b5fc |
| Image origin | reused existing published image |
| Release compose sha256 | 1412f095e70004e43eb0b5630166eeccd7c27643ffbe8987206cccf0b531c122 |
Deploy: upload the attached docker-compose.release.yml to Phala Cloud. Its exact bytes go into the CVM's app-compose, whose SHA-256 is the compose_hash the quote's mr_config_id commits to. (app_id is a separate value the platform assigns when the app is created and keeps across upgrades — do not derive one from the other.) Verify per deploy/phala/README.md — the CVM's app-compose.json docker_compose_file must be byte-identical to this asset.
The tag is intentionally not v*, so it does not retrigger the image build workflow.