Skip to main content

Base KMS

Type
Base
Contract
0x2f83172A49584C017F2B256F0FB2Dca14126Ba9C
Gateway app
0x55760b065A3f1EAbdb1a4d7AbB94950f31B91A84
OS images
18 allowed
Devices
7 allowed for KMS nodes

Root keys

Compare the CA public key with the key-provider event in your CVM’s attestation event log. What they are for

k256 public key
0x02a335aea3df11d46ae0a373d3f26fbd1d208572ecc87e630e618dac693b7af721
CA public key
0x3059301306072a8648ce3d020106082a8648ce3d030107034200048bf84f52911056474c207cb50b4e8010d984f8975ea57b8f0c8b17502181c283e93a68a9864ad19f629508cc699f125be3871ec2e26ab0597e5bca4e29b7425f

Nodes

Each node publishes the measurements of what it runs. The compose hash is the SHA-256 of the node’s app-compose.json. When the file is published, expand a row to read it and check the hash yourself. An on-chain KMS admits only nodes whose TCB status, OS image hash, aggregated MR, and device ID it accepts.

https://kms.dstack-base-prod2.phala.network

v0.6.1git:7f143148cc49f4a09799dstack —