release-2026.08.31.1
Phala gateway deployment manifest, digest-pinned.
| Source ref (input) | main |
| Commit | 0b9d96b1c8a97458a2010b742a6b76db1549ce1c |
| Gateway image | ghcr.io/0gfoundation/0g-pc-e2ee-gateway@sha256:db868b8e3d04506df5590ef349a3faffd935f6e58390ba69e457458611e997c9 |
| Image origin | reused existing published image |
| Release compose sha256 | 7c5755e6830d3002d83c95d6f271b93dedeb0241c9128623222f586548dcbcd5 |
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.