1sealsemantic last-mile verification

Research / Finding

Fix empty collated data / Removing null-consensus

F-TON-010-001

Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Read the evidence · View in research browse

Recorded evidence

—score not recorded
ton-blockchain/tonReported fixton-blockchain/ton

Fix empty collated data / Removing null-consensus

fixed publicly (mapped by date and fix area)
details
Finding IDs
F-TON-010-001
Status
fixed publicly (mapped by date and fix area)
Reported via
TON contest / security process
Note
two strong public fix candidates landed on 2026-03-19: PR #2211 commit 4d49b714ecfbc2e1bf23e75b9fadc75399122fb0 (Fix empty collated data) and PR #2209 commit 39731934d4fbbf6dce4d84509afed424a44c853c (Removing null-consensus). both commits remain present in current testnet and master; mapping is by reported fix date and consensus-area change, not public F-TON disclosure.

F-TON-010-001: Needs source detail. Two public fix candidates remain; the exact mechanism is not established by the recorded mapping. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-TON-010-001

Security area (1seal assessment): Unclassified. The record names two different candidate fixes. The precise reported defect remains unresolved, so consensus-related project context is not used as a substitute. Reviewed 24 Sep 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.