[General] Need clarification regarding paymaster verification rule in future.

[bxpana]

Discussed in #615

^{Originally posted by hoshiyari420 July 3, 2024}

Environment

Mainnet

Provide a brief description of the functionality you're trying to implement and the issue you are running into.

Description

I am currently building a new public good paymaster where multiple Dapps(precisely anyone) can connect to this single paymaster and provide gas sponsorship for their users without needing to deploy paymaster at all.

Since this paymaster can be used by anyone, I want to ensure that design is compliant keeping future perspective in mind. For this one of the clarification I need is regarding the topic: paymaster verification rule in future mentioned in the docs

I have checked ERC-4337 Account Abstraction and ERC-7562, although, it's way more informative and lot of ambiguity keeping ZKsync in mind. Hence, want some clarifications on the paymaster verification rule part as below:

1. Is there some close timeline regarding reputation implementation that I should be aware of?

2. Is there any further information that can be shared regarding verification rules and how ZKsync sees them?

3. As of now my understanding is, if a transaction with paymaster is rejected in the validation phase itself, it's reputation will not altered. Hence, in a scenario, where a Dapp creating failed transactions would not affect the this paymaster's reputation and other Dapps using this paymaster would not be affected at all.

4. Should I not worry about this right now as reputation implementation is far down the line?

Also if I can get some scenario, where a paymaster's reputation might be affected in future, would be quite useful.

To conclude, these clarifications would be extremely helpful in the design and development of this new paymaster. Looking forward to this discussion. Many thanks.

Repo Link (Optional)

No response

Additional Details

No response