pub fn parse_trusted_keys(raw: &[u8]) -> Result<Vec<TrustedKey>>Expand description
The same two shapes, from bytes the caller already holds.
This is the half an application compiling its anchors in needs: include_str! produces the
bytes, and they go through the parser the file path uses rather than a second reading of the
same format written at the call site. A second reading is how the single-key and bundle shapes
come to disagree between a CLI and an application that are supposed to trust identically.
ยงErrors
When the bytes are neither a single key nor a bundle.