# Source Authority Each credential has a digital signature created using keys, with the public key pair listed on a ledger account tied to the issuer. Velocity Network guarantees that this account can only be accessed by signing a transaction using the account's private key. Velocity protocols for credential issuance and presentation sharing operate in a peer-to-peer manner, directly connecting organizational agents and holder wallets. Data is securely transferred only if the parties are authenticated. This process enables the individual to authenticate the counterparty and verify that they have not had their system hijacked. Issuer credentials undergo checks to validate that the issuer has the authority to issue the credentials offered to the holder. If a validation error is detected, the credential will not be issued by that agent. Issuer identity on the Velocity ecosystem is checked and verified as part of the protocol of multi-dimensional credential checks implemented by relying party agents. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://velocity-network.gitbook.io/velocity-network/implementing-proof-of-qualifications-at-scale/source-authority.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.