Skip to content

Improve usage of registration timeout height #705

Open
@jrriehl

Description

@jrriehl

Now that the timeout height is included, we should update the registration logic to ensure that only one valid transaction is in flight at any time.

See further discussion in this PR: #703.

Metadata

Metadata

Assignees

No one assigned

    Labels

    c-choreCategory: Updates that do not fit into a specific categorys-confirmedStatus: This is a confirmed issue

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions