Skip to content

fix(provider): prevent access-key retry after dispatch#680

Open
skyc1e wants to merge 1 commit into
tempoxyz:mainfrom
skyc1e:fix/access-key-send-fallback
Open

fix(provider): prevent access-key retry after dispatch#680
skyc1e wants to merge 1 commit into
tempoxyz:mainfrom
skyc1e:fix/access-key-send-fallback

Conversation

@skyc1e

@skyc1e skyc1e commented Jun 21, 2026

Copy link
Copy Markdown

Closes #644

Access-key send failures were all treated as safe fallback points, including failures returned after a signed raw transaction had already been handed to the transport. That could open the root wallet and submit the transaction a second time.

This keeps the existing wallet fallback for preparation and signing failures, with the original error logged, but wraps transport errors with the signed transaction hash and propagates them to the caller. The localnet regression test simulates a lost response after dispatch and verifies that only one raw transaction is sent.

Tested with:

  • pnpm exec tsc -b --noEmit
  • vp lint src/core/internal/AccessKeyTransaction.ts src/core/Provider.ts src/core/Provider.localnet.test.ts
  • vp test src/core/AccessKey.test.ts src/core/Provider.test.ts (42 tests)

The new localnet case was not run locally because Docker is unavailable.

@vercel

vercel Bot commented Jun 21, 2026

Copy link
Copy Markdown

@skyc1e is attempting to deploy a commit to the Tempo Team on Vercel.

A member of the Team first needs to authorize it.

@skyc1e skyc1e marked this pull request as ready for review June 21, 2026 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Silent access-key send fallback: swallowed errors, double-send risk

1 participant