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

[Feedback]: Account Type Capability Ambiguous #148

Open
1 task done
parseb opened this issue Jun 27, 2024 · 1 comment
Open
1 task done

[Feedback]: Account Type Capability Ambiguous #148

parseb opened this issue Jun 27, 2024 · 1 comment
Assignees
Labels
feedback Comment on existing content

Comments

@parseb
Copy link

parseb commented Jun 27, 2024

Page

https://docs.zksync.io/build/developer-reference/account-abstraction

Description

The text mentions EOAs, Contract accounts and then jumps to smart accounts. It does not seem clear for me if I can sponsor transactions for EOAs as most projects rely on existing ownership relations (msg.sender).

The major question being, can I sponsor a transaction for an EOA while keeping msg.sender the EOA?
Feedback might be rushed, did not ponder, but first read, it was not clear for me.

Code of Conduct

  • I agree to follow this project's Code of Conduct
@parseb parseb added feedback Comment on existing content triage Queue for review labels Jun 27, 2024
@itsacoyote itsacoyote removed the triage Queue for review label Jul 3, 2024
@itsacoyote itsacoyote self-assigned this Jul 3, 2024
@Romsters
Copy link
Contributor

Romsters commented Jul 5, 2024

@parseb yes, you can use paymaster. Paymaster can sponsor any transaction, transaction sender remains unchanged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feedback Comment on existing content
Projects
None yet
Development

No branches or pull requests

3 participants