Trust anchory6F3rt10CEcSakCr…· ed25519
● chain ok32 entries

Version history

Fraud risk classifier · 3 versions · sourced from L11 substrate-component log

← Spec detail
v1.2.0current

alice.morgan · MDR class-IIa workflow alignment · reviewerGate hardened

specHash

2a4072c5d8a65d149a4aacb27702ca10…

L11 entry

#42 · substrate-component log

2 fields changed vs previous

fieldbeforeafter
reviewerGate"on-low-confidence""always"
lowConfidenceThreshold0.7(removed)
v1.1.0

alice.morgan · Tighten confidence threshold based on Q1 false-positive rate analysis

specHash

8a1b3f7e9c2d4e6f8a0b2c4d6e8f0a2b…

L11 entry

#28 · substrate-component log

2 fields changed vs previous

fieldbeforeafter
lowConfidenceThreshold0.60.7
maxLatencyMs80005000
v1.0.0genesis

ops@promethean · Genesis · initial spec for paysafe fraud classifier deployment

specHash

f0e1d2c3b4a5968778695a4b3c2d1e0f…

L11 entry

#1 · substrate-component log

Initial spec commit. No prior version to diff against.

About spec version history

Every spec change writes a new L11 substrate-component log entry, signed under the operator's trust anchor. The specHash committed to each L12 entry references the specific version active at that call's time — so historical L12 entries always verify under the spec version they were produced with, even after the spec evolves.