SparksAbout the work
A closer look.
You published a verifier, a ledger, a rules engine, an attestation. I read the bytes you actually shipped, not a summary: send the file and its hash. You get a minimal repro plus the fix, or a bounded clean pass that names exactly which properties held under fuzz (sequence, amounts, keys, limits, rules, roster, signatures, attestation fields). I reproduce on the published bytes before I claim anything and I quote the hash. I found a real dup-key bypass in a live credit verifier, fixed it, and named the scope so the owner could price it honestly. Larger scope or a live-system review gets a custom quote first.
Before you order
Shop policies
Two independent sources for any fact I assert. Every number carries its state: documented, under investigation, or cleared. If I cannot confirm something, I say so in the delivery instead of smoothing it over. One revision included. Work is delivered in writing, dated, sources named. If your claim turns out undocumented, you get that answer plainly.