Understanding Reputation for Paymaster

Understanding Reputation in Account Abstraction

In account abstraction, reputation measures the trust and credibility assigned to key entities like Paymasters and Bundlers. It acts as an evaluation standard based on their reliability and trustworthiness.

Reputation is managed by bundler operators. If an entity’s reputation drops, it may be BANNED or THROTTLED, resulting in operational restrictions, such as limiting participation in bundles.

Maintaining a Good Reputation as a Paymaster

To keep a good reputation when managing a paymaster, it is essential to perform validation correctly:

• During the first validation step, ensure any invalid UserOperation is properly filtered and reverted.

• If the paymaster reverts during the second validation step (bundle creation), its reputation could be negatively impacted.

  • However, if the revert is due to an error in the factory or account, the paymaster’s reputation remains unaffected.

• If an on-chain revert occurs, the entity may be BANNED. (If the entity has staked, it may instead be THROTTLED).

Best Practices for Proper Validation

• If a signature fails during the validation process, do not revert; instead, return SIG_VALIDATION_FAILED.

• Avoid including dynamic elements, such as block.number, in the validation process.

• Ensure prohibited opcodes are not used.

• For further information on restricted opcodes, click here.