Skip to content

Support multiple inputs #54

Description

@xgreenx

The current implementation assumes that there always exists a huge input that we want and can use to queue transactions on top of each other.

We need to teach the faucet to consume other inputs to minimize the dust.

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions