Why the anchor matters
A credentialing file in a hospital system records that a check happened. It does not prove when, and it can be edited by anyone with database access. That gap is what a plaintiff's attorney works on after a negligent credentialing claim.
An anchored Merkle root removes the gap. The hash of the credential state at the moment of verification sits in a public block with a timestamp nobody controls. The hospital can prove what it knew and when it knew it, and so can the clinician.
- Merkle root
- 32 bytes per batch
- Leaf count
- Credentials in the batch
- Block timestamp
- Set by the network, not by Credool
- Submitter address
- The ledger service signer
Not on chain
No name, no NPI, no licence number, no date of birth. A leaf is only meaningful to someone who already holds the record it describes.