release-2026.08.28.1
Phala gateway deployment manifest, digest-pinned.
| Source ref (input) | main |
| Commit | d02550c20fbac14206336a3cf55ef64c220586cb |
| Gateway image | ghcr.io/0gfoundation/0g-pc-e2ee-gateway@sha256:684b5bc8d560c3417bbd3f0a7bc8d07e83be68de3dc3e53ec37a557bfd7b6092 |
| Image origin | reused existing published image |
| Release compose sha256 | bfeca01ea9ad2e670a0a01a0c5952c93695c729fd5fa9c9daafefb0d3204a775 |
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 that hash's leading 20 bytes). 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.