Skip to content

🕒 Ledger-Sync | Enforcing Absolute Chronological Gaps Between Node Ingestions #369

@Sadeequ

Description

@Sadeequ

Description

High-frequency automated scripts can flood the network with consecutive price updates within the same ledger window, creating block noise and running up operations costs.

Technical Requirements

  • Create a persistent ledger tracking map (Map<Address, u32>) that records the exact block height of a relayer's most recent submission.
  • Reject any incoming transaction payloads if the current network ledger index has not advanced by at least 3 blocks since that node's last write operation.
  • If you find this implementation useful, please star the project and leave a review! 😊

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions