Skip to content

Problem: node operators can't run TN without storing repeat data #1420

Description

@MicBun

Half the records the network stores repeat the value of the record before them: 37.7 million out of 75.1 million. Every node keeps all of them, and 96% of streams hold at least one.

They carry nothing a reader can use. Asking for a moment with no record returns the last value at or before it, so a price that has not moved in a month is already answered correctly by the month-old record. Attestation and settlement resolve the same way.

Nearly all of it is old. 98.8% of the repeats are already more than 30 days past, so a 30-day retention window forfeits almost nothing.

Part of the total is a fixed backlog rather than an ongoing leak. The largest contributor stopped publishing in August, and its share cannot grow.

Done when repeats older than a retention threshold are removed on a schedule, storage falls accordingly, and every query returns exactly what it returned before.

Part of:

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions