Professional Attestation Ledger

Every release a credentialed professional makes — cryptographically chained and tamper-evident forever.

Authyr's second primitive surface. Sibling to verified-customer attestation. The same hash-chained ledger substrate, but the actor at the front is the credentialed professional — physician, attorney, contractor, mechanic, advisor — at the moment of release. Every signature bound to a state license or board certification. Every release a link in a public-verifiable chain.

Legal opinion releases · Pre-procedure sign-offs · Code closeouts · Safety releases · Fiduciary attestations Patent P4 · Hash-chained release attestation Public-verifiable · Tamper-evident · Audit-ready
The pattern

A signed release. Chained to the one before it. Verifiable forever.

Across legal, medical, contractor, auto, and financial services, credentialed professionals issue dozens of "release" decisions every week — opinions, sign-offs, safety clearances, suitability attestations. Today those releases live in paper folders, PDFs, or proprietary practice-management systems. None of them are cryptographically anchored. None of them survive an audit without an evidentiary battle.

Today's status quo

Asserted attestation — by signature alone, easily disputed

Professional releases sit in proprietary systems with mutable timestamps and weak audit trails. When a malpractice claim, code dispute, recall investigation, or regulator audit lands two years later, the professional's defense rests on whatever the practice-management vendor's logs happened to capture — and the integrity of those logs depends entirely on trusting the vendor.

Authyr Professional Attestation Ledger

Cryptographic chain — credential-bound, tamper-evident, public-verifiable

Each release is signed at the moment of issuance, bound to the professional's verified credential (state license, board certification), and hash-anchored to the prior release in the same ledger. The chain extends back to a genesis attestation. Any tampering breaks the chain. Third parties (auditors, examiners, opposing counsel) verify the chain independently — they don't have to trust the practice or the platform.

The ledger, live

An Authyr Professional Attestation Ledger across five verticals.

Below is a mock of how the ledger reads when populated. Same hash-chain primitive applied across five service verticals at once — each release signed by a credentialed professional, each one chained back to the previous entry, each one independently verifiable.

Live ledger 6 total releases 5 verticals 6 credentialed signatories 100% chain integrity
ID Timestamp Action / context Release decision Signatory Chain
apl-00006 2026-05-27 19:36:45 UTC MED Pre-procedure verification
cosmetic-derm · 2-area injectables · age 47F · consent v3.2
RELEASED
procedure cleared for execution
Dr. Lia Reyes, MD
ABDA #11244 · NPI 1538947726
6473fb061682…
prev: 39e30324181c…
apl-00005 2026-05-22 14:08:12 UTC LEG M&A opinion-letter release
target: Aristae Holdings · purchase agreement v8 · TX-Sec.13.301 closing
RELEASED
opinion delivered to closing escrow
Marcus Pell, Esq.
TX Bar #24081933 · Pell & Avery LLP
39e30324181c…
prev: 79db56a2a451…
apl-00004 2026-05-19 21:14:03 UTC CON Electrical permit closeout
200A residential service · NEC 2023 · IRC §E3702 · permit COH-244871
RELEASED
final inspection passed · permit closed
Samuel Riley, M-Elec.
TX Master Electrician #112493 · Riley Contracting LLC
79db56a2a451…
prev: c9b621a272d5…
apl-00003 2026-05-15 11:42:51 UTC AUT Brake-system safety release
VIN 1HGCV1F3XLA901… · rotors+pads+ABS bleed · road-test 4.2mi
RELEASED
vehicle cleared for customer pickup
Marco DeSantis
ASE Master #M.A1-A9.L1 · 18 yrs
c9b621a272d5…
prev: f93b47d27566…
apl-00002 2026-05-12 16:55:08 UTC FIN Fiduciary suitability attestation
client portfolio rebalance · IRA · 60/40 → 70/30 · risk profile 4
RELEASED
trade executed via custodian
Priya Anand, CFP®
CRD #6814092 · Series 7/65/66
f93b47d27566…
prev: 5418116dcd40…
apl-00001 2026-05-09 08:20:11 UTC MED Controlled-substance dispense
oxycodone 5mg #20 · post-surgical · DEA 222C · 14-day refill lock
RELEASED
dispense logged · prescriber + pharmacist co-sign
Anjali Mehta, PharmD
TX PHM #28471 · DEA AM4791336
5418116dcd40…
prev: genesis

Above table is a mock illustration. The signatories, credentials, and timestamps are not real. The chain structure (hash-of-prev-attestation, cryptographic signature, public-verifiability) is the actual product. Founding cohort populates the first real entries.

How the chain works

Every release hashes the one before it.

If anyone modifies an old release — backdates a sign-off, alters a release decision, swaps a signatory — the hash of that entry changes, and every subsequent hash in the chain becomes invalid. Tampering is visible immediately. The integrity check is a single cryptographic verification.

genesis
Ledger initialized
0000000000000000
0000000000000000
apl-00001
First release
5418116dcd40…
prev: genesis
apl-00002
Second release
f93b47d27566…
prev: 5418116dcd40…
apl-00006
Latest release
6473fb061682…
prev: 39e30324181c…

Each block's hash is computed over (release_payload + signature + prev_hash). Any change to a prior block invalidates the chain from that block forward. The most recent hash is the cryptographic fingerprint of the entire ledger history.

Anatomy of a release

What's inside a single attestation entry.

A single Authyr Professional Attestation entry binds the release decision to the credentialed professional, to the prior chain link, and to the moment in time. Below is the field-by-field anatomy.

Release context (the WHAT)

Attestation ID
apl-00006
Timestamp
2026-05-27T19:36:45.094ZRFC 3339 UTC, anchored to a trusted timestamp authority
Action class
Pre-procedure verificationPulled from a vertical-specific taxonomy — never a free-text label
Release decision
RELEASED · procedure clearedBounded values: RELEASED, HELD, REJECTED, AMENDED
Action payload hash
sha256:7c8d4a2e…b39f01Hash of the full release record (consent form, procedure notes, etc.) — payload stored separately, often encrypted at rest

Signatory + chain (the WHO + the WHEN)

Signatory
Dr. Lia Reyes, MDResolved from the practice's verified-credential roster
Credential
ABDA #11244 · NPI 1538947726Board cert verified against issuing authority at signing time
Signature
ed25519:a3f9…c92fBound to the credential, not just the device
Previous-link hash
prev: 39e30324181c…The hash of the entry immediately before this one — the chain link
Verify URL
authyr.com/verify/apl-00006Public verification endpoint — any third party can validate without trusting Authyr
Vertical applications

What gets signed and chained, by industry.

Same primitive across every vertical. The differences are which actions get attested and which credentials anchor the signatures. Below: the actions where Authyr Professional Attestation produces immediate audit-defense and regulator-compatible value.

🩺

Medical

Outpatient cosmetic, dermatology, plastic surgery, infusion, urgent care, dental, veterinary. Anywhere a credentialed clinician signs off on a clinical release decision.

Actions chained
  • Pre-procedure verification (surgical "time-out" attestation)
  • Device-QA release (medical-equipment calibration sign-off)
  • Lab / imaging result release (pathologist, radiologist co-sign)
  • Controlled-substance dispense (prescriber + pharmacist)
  • Informed-consent chain (witnessed, dated, immutable)

Legal

Personal injury, family, estate, immigration, M&A. Whenever an attorney signs off on a release that affects a client or counterparty.

Actions chained
  • Opinion-letter release (M&A closing, regulatory compliance, tax)
  • Settlement-document execution (release-of-claims, indemnity)
  • Escrow disbursement attestation
  • Ethics-firewall + conflict-clearance sign-offs
  • Privilege-log entries (chained, immutable)
🔧

Contractor / trades

Electrical, plumbing, roofing, fire-suppression, HVAC. Anywhere a licensed trade closes out a permit-required system.

Actions chained
  • Code-compliance sign-off (NEC, IRC, IECC, IFC)
  • Permit closeout attestation (city / county AHJ filing)
  • Safety-system release (fire suppression, combustion, CO)
  • EPA refrigerant handling certification
  • Warranty-bearing system commissioning
🚗

Auto · body · dealer

Repair shops, body shops, dealer service departments, mobile mechanics. Every release that affects a safety-critical vehicle system.

Actions chained
  • Brake / airbag / ADAS release post-repair
  • Pre-delivery inspection (dealer new + used)
  • Recall-defense documentation (when work was performed)
  • Warranty handoff attestation
  • Diagnostic-trouble-code clearance chain
💼

Financial

RIAs, fee-only advisors, CPAs, insurance brokers, mortgage brokers. Releases that affect client allocations, suitability, or regulatory disclosure.

Actions chained
  • Fiduciary suitability attestation (per-trade or per-rebalance)
  • Disclosure-delivery chain (Reg BI, Form CRS, ADV Part 2)
  • Audit-report release (CPA · year-end)
  • Continuing-education / CE credit attestation chain
  • Examiner-prep documentation
🛡

Compliance & safety officers (cross-vertical)

Any licensed officer making periodic release decisions — chief compliance officer, designated safety officer, qualified individual.

Actions chained
  • Periodic compliance attestation (monthly / quarterly)
  • Incident-response sign-off (data breach, safety event)
  • Vendor / supplier qualification release
  • Internal audit findings closure
  • Examiner-response submission attestation
What this enables

What changes the day you turn this on.

The Professional Attestation Ledger isn't a marketing feature. It's audit-trail infrastructure. Below: what becomes possible the moment your verified releases are hash-chained.

🛡

Audit-defense

State boards, professional licensure examiners, regulators — all want chronological evidence. The chain provides it without your IT department fielding subpoenas.

Malpractice / liability defense

"Was the time-out attestation performed?" stops being a memory question. The signed, timestamped, chain-anchored release is the evidence — no proprietary log to subpoena.

🔁

Recall defense (auto, contractor)

Recalls and manufacturer-defect claims live or die on whether the release was performed correctly. The chain produces decade-long evidence of every release decision.

🪪

Credential-portability

When a professional moves practices, their signed releases travel with them as portable verifiable evidence of competence — independent of any one employer's record-keeping.

🏛

Board / examiner readiness

FDA, SEC, FINRA, AHJ inspectors, AAPM auditors all increasingly accept (and increasingly require) cryptographically anchored audit trails. Authyr meets that bar by default.

🤝

Inter-party verification

Counterparties — insurers, opposing counsel, escrow agents, regulators — verify chain integrity without going through your office. They run the verification themselves.

The signing ceremony

Five steps from "decision made" to "chain link sealed."

The professional doesn't change their workflow. Authyr captures the release event from inside the practice-management system (Clio, Dentrix, Athena, ServiceTitan, Wealthbox, etc.), runs the signing flow in the background, and posts the resulting entry to the chain.

STEP 01
Release decision captured

Practice-management system signals a release event. Authyr ingests the action payload + context.

STEP 02
Credential verified

Signatory's state license / board cert / NPI / CRD / ASE number checked against issuing authority at signing time.

STEP 03
Action payload hashed

SHA-256 over the full release record (consent, notes, scope, parameters). Payload stored encrypted, only the hash is public.

STEP 04
Chain link signed

ed25519 signature bound to the credential, anchored to prev-hash. The signing key never leaves the credential's hardware root of trust.

STEP 05
Entry posted, chain advances

New entry appended to the public-verifiable ledger. Chain pointer advances. Verify URL goes live within seconds.

Patent posture

Patent P4 — broad parent claim covers the ledger primitive.

The hash-chained release-attestation architecture is the subject of a deliberately-broad patent filing. The parent claim is generic enough to cover the customer-attestation ledger (Authyr's other surface) and the professional-attestation ledger (this surface) under the same filing.

Patent P4 · Hash-chained audit log with release-attestation binding

One patent. Both Authyr surfaces protected.

The Frequentor LLC patent series includes a deliberately-broad parent claim covering hash-chained per-action attestations bound to signed release contexts. The same filing protects the customer-attestation ledger (verified-customer reviews + 30-day mitigation window) and the professional-attestation ledger described on this page. Specializations are claimed as continuations.

Claim 1 Hash-chained log of per-action attestations, each bound to a signed release context. (Broadest — covers both surfaces.)
Claim 2 Specialization: clinical or technical action + credentialed-professional release attestation. (Covers the Professional Attestation Ledger.)
Claim 3 Specialization: verified-customer attestation + business attestation context. (Covers the customer-attestation ledger.)
Claim 4 Methods of public verification of chain integrity without trust in the issuing authority.

What Authyr Professional Attestation does NOT do

The ledger is evidentiary infrastructure. It is not clinical judgment, legal advice, engineering signoff, or fiduciary discretion. Every entry on the chain is signed by a real credentialed human exercising real professional judgment. We make that judgment durable, verifiable, and portable — we do not replace it.

Phrases we will never use
  • "AI signs off on the release for you"
  • "Automatic release approval"
  • "Authyr replaces your physician / attorney / engineer / advisor"
  • "Compliance guaranteed" — compliance is a property of the underlying decision, not the chain
  • "Public ledger of patient / client / case data" — we hash payloads, we don't expose them
What we actually do
  • Capture the release decision the professional already made
  • Verify the signatory's credential against the issuing authority at signing time
  • Hash the action payload (full record stored encrypted at rest)
  • Sign the chain link with a key bound to the verified credential
  • Post the entry to a chain anyone can independently verify
  • Hold the chain immutable forever — owner cannot delete, signatory cannot revise

Make every release defensible.

The Professional Attestation Ledger ships on Firm tier and as an add-on for Practice tier. Founding cohort gets it included.

Apply for the Founding cohort → Read the whitepaper