Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
nielstron opened this issue Apr 14, 2023 · 1 comment
Open
Labels
enhancement New feature or request Feature request

Comments

@nielstron
Copy link
Contributor

nielstron commented Apr 14, 2023

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

@nielstron
Copy link
Contributor Author

Note for example that BF also supports fetching specific tx_ids https://docs.blockfrost.io/#tag/Cardano-Scripts/paths/~1scripts~1datum~1%7Bdatum_hash%7D~1cbor/get

@cffls cffls added Feature request enhancement New feature or request labels Apr 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Feature request
Projects
None yet
Development

No branches or pull requests

2 participants