Chronicle Protocol audit

ABDK ConsultingNot recorded. See the report

ABDK Consulting reviewed Chronicle (Chronicle Protocol audit) on 10 Aug 2023: 61 findings, 0 critical; 13 marked fixed, 48 acknowledged.

No open critical findings
Open the reportOpen Chronicle’s security record

Report hosted on GitHub.

Statuses are the security firm’s own, from this report. Trustblock does not review code.

Findings61

Statuses are the security firm’s own, from its report.

SeverityOpenAcknowledgedFixed
Critical000
High065
Medium0132
Low0296
HighFlaw in Schnorr.mdFixed

The report gives no description here.

HighProcedural in IScribe.solFixed

The report gives no description here.

HighSuboptimal in IScribe.solFixed

The report gives no description here.

HighSuboptimal in LibBytes.solFixed

The report gives no description here.

HighUnclear behavior in Schnorr.mdFixed

The report gives no description here.

MediumUnclear behavior in LibSchnorr.solFixed

The report gives no description here.

MediumUnclear behavior in LibSchnorr.solFixed

The report gives no description here.

LowBad datatype in ScribeOptimistic.solFixed

The report gives no description here.

LowDocumentation in ScribeOptimistic.solFixed

The report gives no description here.

LowProcedural in IScribe.solFixed

The report gives no description here.

Show 3 more
LowSuboptimal in LibSchnorr.solFixed

The report gives no description here.

LowSuboptimal in LibSecp256k1.solFixed

The report gives no description here.

LowSuboptimal in LibSecp256k1.solFixed

The report gives no description here.

Contracts in scope

No deployed address is recorded for this audit.

The report names a repository or files. Open the report to see its scope.

Part of Chronicle’s security record

Chronicle
Audits2 audits by 1 firmLast audit Aug 2024, by ABDK Consulting.
Critical findingsNo open critical findingsAcross 2 reports.
Open Chronicle’s security record

Security firm

ABDK Consulting

31 projects reviewed · 64 reports · latest Jan 2026

See ABDK Consulting’s audits

Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.

Tell us