Skip to content

Handle double spending transactions #1

Description

@anon-real

It may be the case that two simultaneous proposals happen to have one or more identical boxes in their inputs. So one of them gets approved sooner and its associated tx will be mined. So now the other proposal's tx is invalid anyway, however, it may be the case that some commitments are already generated for the proposal. This case should be handled somehow!

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions