Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feat(builder): lazy UTxO resolvers for retry-safe buildEffect

Open
  • Is something wrong?
#199 0 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
typescript
Domain
backend-api-design

Research direction

Start with BuildOptions and resolveAvailableUtxos in TransactionBuilder.ts, then inspect CollectFromParams.inputs and createCollectFromProgram in Collect.ts. Confirm how static arrays are handled before extending both inputs to support lazy Effects. Done means static behavior remains compatible and lazy resolvers are evaluated at build or program execution time so retries obtain fresh UTxOs.

Written by the indexing model from the issue text.

Description

enhancement

Problem

BuildOptions.availableUtxos and collectFrom inputs are static arrays resolved before buildEffect() runs. When an action is retried via Effect.retry, the same stale UTxO arrays are reused — the provider is never queried again.

Proposed Solution

Allow availableUtxos and collectFrom.inputs to also accept a lazy resolver () => Effect<ReadonlyArray<UTxO>> evaluated at build time:

client.newTx()
  .collectFrom({ inputs: () => client.Effect.getUtxos(scriptAddress), redeemer })
  .buildEffect({ availableUtxos: () => client.Effect.getWalletUtxos() })
  .pipe(Effect.flatMap(s => s.Effect.signAndSubmit()))
  .pipe(Effect.retry(Schedule.recurs(3)))

Each retry calls the resolver fresh, so UTxOs are always up to date with no extra boilerplate required from the user.

Affected Areas

  • BuildOptions.availableUtxos — extend type to accept () => Effect<ReadonlyArray<UTxO>>
  • resolveAvailableUtxos in TransactionBuilder.ts — yield the Effect at build time when lazy
  • CollectFromParams.inputs — same lazy extension
  • createCollectFromProgram in Collect.ts — evaluate resolver at program execution time

Non-breaking — static arrays continue to work as-is.

Dominant language
TypeScript
Stars
22
Forks
31
Avg merge
3d 4h
Merged PRs (30d)
27

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IntersectMBO/evolution-sdk

All issues in IntersectMBO/evolution-sdk

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.