Skip to content

Library breaks with float feeRate #87

@Distance71

Description

@Distance71

Float fee rates are not something uncommon. Something like 0.1, 100.2, ...

On the other hand, If We check uintOrNaN, float fee rates are not handled by the library

As much as I could see, it can be easily fixed by removing that line on utils uintOrNaN, setting Math.round() on both accumulative and blackjack, and finalize

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