Paymaster - a composable component for AA of Ethereum
AAStar will try to build a public paymaster service for the Ethereum mass adoption.
Why Plancker choose this?
Paymaster will not disappear like bundler, it will be a long term component for Acount Abstraction even the ERC4337 is changed.
Ethereum need more different implementations of paymaster to be diversity and decentralization for the whole ecosystem like many versions of Ehtereum clients.
It related to mass adoption, a huge oppotunity for UX improvement using product service. We have some product strength on that.
Other reasons
it is more closer to money(gasfee) and has a simple business model: sell 50 cents gas with convenience service for 70 cents price.
We can expand more services to Applications and Users and build a small circle ecosystem like liquidity service and gas tank or cross chain gasless service.
We will build Ethereum Layer1 node and Layer2 node to simulate the transactions and be sure security, it also can expand some security service like support anti-censorship or build a FULL NODE FOR ESCAP CAPSULE OF LAYER2. Or some contract analysis service to improve the safe for users.
How
Three phases
Basic paymaster
Be composable with Application Accounts including aggregate other third party paymaster services.
Be entrance for mass adoption users with AirAccount.
Design of Basic Paymaster
APIs like Pimlico follow the opensource paymaster contract and more.
Build a basic ERC4337 wallet to send user operations and send to buldler with or without a paymaster service.
Improve the backend service, like what Jaydon mentioned in the meeting.
Basic APIs(connect with bundler or 7560 later)
Gas price calculation
Floating pricing module
Signature service
Simulation service(basic)
Lay1 and Layer2 node running service(a FULL NODE?)
Expand Paymaster
Complex package for the Game applications or others.