[OP Stack Deployment] Configuring the sequencer on custom L2 to cover L1 fees for users #637
Unanswered
surhud004
asked this question in
Deploying the OP Stack
Replies: 1 comment
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Did you check the documentation?
Did you check for duplicate questions?
Issue Description
Hello OP Stack team,
I’m running a custom L2 chain locally connected to the Holesky testnet on L1. In this setup, I’ve configured the L2 chain to set all L2 transaction fees to zero.
Issue
However, even though L2 transaction fees are zero, the sender account is still being charged the L1 fee component for transactions. As a result, users still need to have at least some gas tokens in their accounts to initiate transactions. This requirement complicates the onboarding experience for users, as they need to acquire gas tokens from a faucet or enable it in their wallet. Ideally, users should be able to connect to L2 and execute transactions immediately without any extra setup, including managing the gas costs.
Expected Behavior
Users connect to the L2 network and can directly perform transactions without needing any gas tokens or ETH or additional steps. The sequencer should ideally cover the L1 fee component on behalf of the user.
Request for Assistance
I believe there may be a way to configure the sequencer to absorb these L1 fees on the user’s behalf. Could you guide me through the relevant parts of the codebase where I can adjust this behavior? Any advice on where this configuration might reside and changes, I’d need to make would be greatly appreciated.
Thank you for your help and for all the work on OP Stack!
Logs
Sending 50 custom ERC-20 tokens with zero gas token as balance of sender - failed transaction
Additional Information
No response
Feedback
No response
Beta Was this translation helpful? Give feedback.
All reactions