[OP Stack Deployment] L2 with custom gas token but getting "Wrapped Ether"

[ddoliveiraa]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

I'm working on creating an L2 using the OP Stack.

I followed the "getting-started" guide and successfully got it running. Now, I'm trying to implement a custom gas token following the instructions in the documentation. However, when I attempt to validate the implementation with a cast, it still shows "Wrapped Ether" instead of my custom token.

Here's what I've done so far:

• Added useCustomGasToken and customGasTokenAddress to the getting-started.json.
• Carefully followed the documentation multiple times.

Despite this, I haven't been able to get it to work.

Logs

No response

Additional Information

No response

Feedback

No response

[Chomtana]

Where does it show "Wrapped Ether"?

If it's in explorer or wallet then it's the client config or the env variable. You would probably look into frontend code or the env in the explorer.

I think there is no standard way to config for the native gas token name. As a result, each framework come up with its own way.

[surhud004]

Hey @ddoliveiraa I am running the same configuration setup. It returns Wrapped Ether for me as well. However, if you connect your chain with Metamask, you should be able to see your custom gas token integrated instead of ETH. Another way to verify this is to query your SystemConfigProxy contract on your L1 -

[KenianShi]

Yes, I am the same, but does this prove that my L2 deployment was successful ?

Hey @ddoliveiraa I am running the same configuration setup. It returns Wrapped Ether for me as well. However, if you connect your chain with Metamask, you should be able to see your custom gas token integrated instead of ETH. Another way to verify this is to query your SystemConfigProxy contract on your L1 -

[KenianShi]

When i do "cast call --rpc-url $L2_ETH_RPC_URL 0x4200000000000000000000000000000000000006 'name()(string)'" it prints me "Wrapped Ether". And when I do the "cast call --rpc-url $L2_ETH_RPC_URL 0x4200000000000000000000000000000000000015 'isCustomGasToken()(bool)'" it prints false.

Have you solved this problem? The same thing happened to me

[priyanshuthapliyal]

Hi @KenianShi @ddoliveiraa actually same issue i am facing so i have raised this issue with optimism team as well. You can see that issue. According to my observation it is due to how we create genesis and rollup.json using op-node newer version. Because this issue is not there in v1.7.7. Anyways chain is working fine even with new version it just the cast command output we are getting is wrong for predeploys.
https://github.com/ethereum-optimism/optimism/issues/13007

[opfocus]

"This calls the L1Block predeploy should return true" check, my return was false

In addition to trying to use a newer version, it may be necessary to wait for a while for L2 synchronization to complete. The configuration on L2 may be triggered by the deployment of the L1 contract, and may need to be synchronized before you can see the expected results.

This query may be related to the synchronization of the chain, because I have stopped my chain and cannot test again for the time being. If you encounter this too, please wait for synchronization for a period of time before trying to query again.

[Satyam78612]

I want to know what you mean by being part of the superchain enables seamless transactions, we will have full control over our chain, scalability, TPS, transaction costs?

[opfocus]

please open a new discussion for your question

[Casholey]

0x1f9090aaE28b8a3dCeaDf281B0F12828e676c326

[opfocus]

Deprecation of Custom Gas Tokens