Ethereum Malta Paymaster: Who Pays?
The paymaster's balance sheet is the only honest ledger in this entire racket, and in Malta's Ethereum gas abstraction game, somebody is always quietly eating the cost. Here is the brutal truth nobody on the conference circuit wants to admit: the entity funding your "gasless" transaction is never the user, and it is almost never the dApp developer either. The Ethereum Malta Paymaster model is a shell game stacked three layers deep, and if you cannot map who settles the invoice at the end of the chain, you are the mark at the table. 🎯
Let me be direct about the mechanics, because the polite version of this story is worthless. When a Maltese-licensed operation spins up a paymaster contract, the ERC-4337 flow routes user operations through a bundler, and the paymaster's deposit gets debited in ETH to cover gas. That deposit does not refill itself through good intentions. Somebody wired real capital into that contract, and that somebody is wearing one of exactly four hats. Know the hat, know the risk.
The Four Funding Hats Behind Gasless Transactions
Hat one: the dApp treasury. The developer eats the gas to onboard users, converting marketing budget into on-chain subsidy. This is the cleanest model and the fastest way to burn through a treasury, because gas abstraction subsidies scale linearly with user count while revenue scales on a curve that usually arrives late. Hat two: the paymaster-as-investor, where a liquidity provider fronts the deposit and recoups through spread, staking yield on the locked ETH, or fee capture on routed volume. Hat three: the regulated operator itself, which treats gas subsidy as customer acquisition cost and books it against gaming or exchange margin. Hat four, the ugly one: the user pays anyway, just invisibly, through a hidden markup baked into the swap rate, the deposit spread, or the withdrawal fee downstream. 💸
Here is where the gas abstraction economics get genuinely nasty. A paymaster deposit sitting in the EntryPoint contract is idle capital. It earns nothing while it waits to be spent on other people's transactions. So the operator has a hard incentive to either minimize the float or monetize it, and monetizing it means the subsidy is never truly free. Any pitch claiming zero-cost gas with no recapture mechanism is either lying or running on a treasury that will be empty in a quarter. Run the numbers on deposit burn rate against user acquisition value before you believe a single slide.
Malta's Regulatory Layer Changes the Invoice
Now stack the Maltese jurisdiction on top. An operator holding a Maltese license and running a paymaster is not just a smart contract; it is a regulated entity with reporting obligations, and gas subsidy flows can be recharacterized as promotional spend, bonus value, or even player funds depending on how the ledger is structured. That recharacterization is where audits get ugly. If the paymaster deposit is funded from player balances, you have a segregation problem. If it is funded from operator capital, you have a subsidy disclosure problem. The Malta paymaster question is never "who pays the gas" in isolation. It is "whose money is legally on the hook when the deposit drains and the bundler refuses to relay." 🧨
The signature verification layer is the second trap. Paymasters validate user operations off-chain before signing, and that validation logic is where abuse hides. A poorly scoped validation function lets an attacker drain the deposit with crafted user operations that pass the signature check but never deliver the intended payment. Malta's technical audit culture has gotten sharper about this exact vector, and the operators who survived the last two years are the ones who treated paymaster deposit limits as a hard security boundary, not a convenience setting. Cap the deposit. Cap the per-operation gas. Cap the validation window. No exceptions, no "trusted partner" exemptions.
Reading the Real Cost Line
Strip away the branding and the honest answer to who pays is this: the party with the weakest ability to pass the cost downstream. In a competitive dApp, that is the developer. In a captive user base, that is the user through hidden spread. In a regulated Maltese operation with thin margin, it is the operator's own equity, and that equity has a burn rate measured in weeks, not years. Track the EntryPoint deposit balance like a hawk tracks a field mouse. When the deposit stops refilling from a sustainable source, the paymaster is already dead; the transactions just have not reverted yet. 🦅
The final variable is bundler incentive alignment. Bundlers prioritize user operations that pay them reliably, and a paymaster with a thin deposit gets deprioritized during congestion, which means your "gasless" users experience failed transactions at exactly the moment volume peaks. That failure rate is the true cost line, and it lands on whoever owns the user relationship. Map that owner, and you have found who pays.