What is Zyfi?
Last updated
Last updated
Zyfi is a native Account Abstraction provider focused on flexibility and ease of integration.
Zyfi was created to accelerate adoption by providing the best on-chain UX for ZKsync and Elastic Chains, leveraging Native Account Abstraction.
The main focus of Zyfi revolves around paymasters and the features they offer. From allowing users to pay with any ERC-20 token (currently more than 80) enabling specific sponsorship logic with Sybil prevention and dashboard analytics, Zyfi helps deliver the best gas abstraction experience for users and Dapps. All is powered by an API that takes less than a day to implement, abstracting the complexities away from protocols so they can focus on building their products. Zyfi has processed over 1.5M paymaster transactions and is integrated with more than 30 DApps on ZK chains across various sectors, including PancakeSwap (DEX), ZeroLend (Supply & Borrow), SyncSwap (DEX), Gravita (CDP), Increment Fi (Perp), and zkMarkets (NFT marketplace), with many more in the pipeline.
Beyond the paymaster service, Zyfi offers a gasless portal where users can experience the power of native AA: they can swap at the best rates, send tokens without having ETH, or submit custom paymaster transactions to interact with protocols that don’t yet offer a paymaster solution.
Managing gas has always been a challenge, especially when users try to execute a complex transaction only to discover they have no gas tokens left.
New users often get confused about why native gas tokens are needed and how to acquire them, leading to wasted time and scattered funds across multiple wallets.
Smart Wallets provide a strong solution to this challenge. Pushed by ERC-4337, these advanced smart contract accounts create transactions using a completely different architecture and transaction flow. Transactions, or UserOps, use a distinct transaction mempool and bundlers to build blocks, with the ability to interact with paymaster contracts for gasless transactions. However, a key limitation remains: Externally Owned Accounts (EOAs) cannot interact with paymasters in the ERC-4337 architecture. This is due to the fact that Account Abstraction was never implemented at the core protocol layer of existing chains. Introducing native AA at this level would require substantial modifications to these chains, and such changes are not currently planned.
ZKsync is the first EVM-compatible Layer 2 to support Account Abstraction at the core protocol level. On ZKsync and ZK chains, all accounts are smart wallets by default.
When an EOA initiates a transaction on native AA chains, a DefaultAccount contract is used to simulate the behavior of an EOA. From the user's perspective, they are using a smart wallet that acts as an EOA. This enables EOAs to send transactions gaslessly with paymasters on all ZK chains through any wallet (e.g., MetaMask, TrustWallet, Rabby).
“Accounts in ZKsync Era can initiate transactions, like an EOA, but can also have arbitrary logic implemented in them, like a smart contract. This feature, called "account abstraction" (AA), aims to resolve the issues described above.” - ZKsync documentation
This is why at Zyfi, we’ve developed tools and gas abstraction solutions across all ZK chains that support native Account Abstraction.
Below is how Zyfi's paymaster tool enable an EOA to perform transactions gaslessly.
The Zyfi paymaster API allows any DApp to offer gasless transactions and lets users pay for gas with any ERC-20 token they hold.
The whole process is built with 3 major steps:
The paymaster API interacts directly with any front end. It receives the transaction data and adds the paymaster parameters, including the fee token (ERC-20) used to cover gas costs or any custom sponsorship logic applied by the Dapp.
User signing transaction data. The user then signs a gasless transaction and gives the allowance to the paymaster for the ERC-20 fee.
Paymaster execution. The Zyfi Paymaster then receives the ERC-20 fee to validate and execute the transaction while paying the ETH gas fees for the end user.
