alchemyplatform / alchemyplatform/aa-sdk
Why the `SupportedAccounts` on `useSendUserOperation` hook is limited to Alchemy Web Signers?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 321
- Forks
- 231
- Avg merge
- 43m
- Merged PRs (30d)
- 3
Description
As per title, I am looking to understand the rationale behind this choice, which looks like a limitation to me.
I am building an app that should allow other custom signers and I see no reason why this should be a limitation for the use of react hooks.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with account-kit/core/src/types.ts at the linked line and trace how SupportedAccounts is used by the useSendUserOperation hook. Review the surrounding type definitions and related hook entry points to determine whether the restriction is intentional. Done means the rationale is documented or the required scope for supporting custom signers is clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100