signing keys
the v1 signing key
◆ sol pbc says
this key verifies the v1 chain only; it signs nothing new.
| algorithm | ed25519 |
| fingerprint | 5FCC81CD3DE12315 |
| status | v1 only, no new signatures |
| raw key file | https://transparency.solstone.app/releases/keys/solpbc-transparency-1.pub |
full public key text
untrusted comment: minisign public key 5FCC81CD3DE12315 RWQVI+E9zYHMX0sa2cZZ6lQs8eyL1U/uOX0Vq1LyVA/zDLy78bBOpGwq
the v2 signing root
◆ sol pbc says
this is sol pbc's v2 signing root, version 1: one key id, which signs alone. it is renewed yearly, and every prior witness log line stays published when it is.
| root version | 1 |
| signing threshold | 1 of 1 |
| root key ids | 050ecd6f44be9fefb96e67f07a568c838c747f2d7e9289d517b8797a04405606 |
| root file sha256 | 3a3f2f8eba390aa466ca77cd226d2609e415943008a55dea4fa3187f2223344a |
| raw root file | https://transparency.solstone.app/v2/metadata/1.root.json |
the witness log lines for this root
solpbc-tuf-root keyid: 050ecd6f44be9fefb96e67f07a568c838c747f2d7e9289d517b8797a04405606 solpbc-tuf-root v1 sha256: 3a3f2f8eba390aa466ca77cd226d2609e415943008a55dea4fa3187f2223344a
◆ sol pbc says
these lines are published at more than one location sol pbc controls, listed below; they are a cross-check for a root you have already pinned, not a trust root themselves. in the witness log, each root version adds one sha256 line, and the key id line covers every sha256 line below it, reappearing only when the key set changes.
- the pinned root in the public verifier repository: https://github.com/solpbc/solstone-transparency/blob/main/protocol/tuf-root.json
- the witness log on solpbc.org: https://solpbc.org/transparency/tuf-root.txt