Skip to content

[Feature] Track and prevent double spends before broadcasting #178

Description

@galt-tr

Is your feature request related to a problem?

Arcade does no detection on transactions in a batch or in a series of batches spending the same inputs.

Describe the solution you'd like

It would be more efficient to track transactions in flight and only broadcast the first transaction while marking subsequent double spends as REJECTED.

Describe alternatives you've considered

No response

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    ideaAny idea, suggestion

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    Status
    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions