# sol pbc v2 transparency root — witness log
# each v2 root's fingerprint is published at more than one location sol pbc controls:
# its lines here, and the root file itself at protocol/tuf-root.json, which holds one
# version at a time, in the public solpbc/solstone-transparency repository.
# every root version adds a sha256 line naming that version, taken over its own root
# file's bytes; a key id line covers the sha256 lines below it and reappears only when
# the key set changes. to check a pinned root, match its digest against the sha256 line
# for your copy's signed.version, and its key ids against the nearest key id line
# above that; then confirm no higher version line appears. a version with no sha256
# line here is not yet recorded.
# these lines are a cross-check for a root you have already pinned, not a trust root
# themselves.
# append-only: prior lines are never removed.
solpbc-tuf-root keyid: 050ecd6f44be9fefb96e67f07a568c838c747f2d7e9289d517b8797a04405606
solpbc-tuf-root v1  sha256:    3a3f2f8eba390aa466ca77cd226d2609e415943008a55dea4fa3187f2223344a
# clarifying append: in the header above, "its key ids" means the key ids in the pinned
# root's signed.roles.root.keyids. it does not mean signed.keys, which also carries keys
# for the other roles.