Skip to content

FR: Generalize ChainContext.utxos for TransactionInput and addresses #207

Open
@nielstron

Description

@nielstron

Is your feature request related to a problem? Please describe.
In general most backends are able to map a specific transaction id to a UTxO and an address to a set of UTxOs. Some backends even provide optimized code to fetch specific patterns (like kupo) or to fetch several addresses (like the cli)

Describe the solution you'd like
Extending ChainContext.utxos to support all of

  • str (bech32 encoded address, hex encoded address, kupo pattern or txid#index)
  • Address
  • TransactionInput
  • List of any of the above

And use additional context for optimization.

Describe alternatives you've considered
None

Additional context
None

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions