Skip to content

Commit cf1d5b5

Browse files
Fix linting
1 parent e283f89 commit cf1d5b5

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

pages/notices/custom-gas-tokens-deprecation.mdx

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -15,17 +15,17 @@ Additionally, advancements in Account Abstraction (AA) tooling now enable gas pa
1515

1616
## Highlights
1717

18-
* Code removal: The Custom Gas Token code will be removed from the Optimism repo.
19-
* Migration to AA tooling: RaaS providers should explore Account Abstraction tools to replace Custom Gas Tokens.
20-
* End of developer support: OP Labs Developer Support will no longer address CGT-related issues or requests.
18+
* Code removal: The Custom Gas Token code will be removed from the Optimism repo.
19+
* Migration to AA tooling: RaaS providers should explore Account Abstraction tools to replace Custom Gas Tokens.
20+
* End of developer support: OP Labs Developer Support will no longer address CGT-related issues or requests.
2121

2222
## Migration recommendations
2323

24-
The Optimism ecosystem is focusing on interoperability within the Superchain, with efforts and incentives directed towards [standard configured chains](superchain/standard-configuration). We strongly recommend:
24+
The Optimism ecosystem is focusing on interoperability within the Superchain, with efforts and incentives directed towards [standard configured chains](/superchain/standard-configuration). We strongly recommend:
2525

26-
* All new chains launch with the standard ETH gas token configuration.
27-
* Utilize Account Abstraction tooling to allow users to pay gas fees in alternative tokens instead of relying on Custom Gas Tokens.
28-
* For example, a given chain can maintain ETH as its protocol gas token while using AA tooling to permit payments in their native token.
26+
* All new chains launch with the standard ETH gas token configuration.
27+
* Utilize Account Abstraction tooling to allow users to pay gas fees in alternative tokens instead of relying on Custom Gas Tokens.
28+
* For example, a given chain can maintain ETH as its protocol gas token while using AA tooling to permit payments in their native token.
2929

3030
With CGT code removed from the monorepo, chains relying on this feature will find it increasingly difficult to stay up-to-date with the latest L1 and L2 OP Stack upgrades. While an external team might be able to maintain an unofficial fork of the Optimism monorepo that includes CGT support, that is not guaranteed and introduces significant risks.
3131

@@ -37,13 +37,13 @@ There are many account abstractions providers in the space. You should find the
3737

3838
For any chain considering CGT post-deprecation, be aware of the following risks:
3939

40-
* Fee mechanism flaws: Fees are charged as a scalar on blob fees denominated in ETH. This means CGT chains will either drastically overcharge or undercharge users for transaction fees relative to their L1 Data Availability costs.
40+
* Fee mechanism flaws: Fees are charged as a scalar on blob fees denominated in ETH. This means CGT chains will either drastically overcharge or undercharge users for transaction fees relative to their L1 Data Availability costs.
4141

42-
* Higher overhead for RaaS providers: Managing CGT chains requires RaaS providers to assume additional risk exposure to the custom gas token asset.
42+
* Higher overhead for RaaS providers: Managing CGT chains requires RaaS providers to assume additional risk exposure to the custom gas token asset.
4343

44-
* Security concerns: The CGT code modifies the L1 `OptimismPortal`, where all native assets are stored, and will not have undergone third-party auditing.
44+
* Security concerns: The CGT code modifies the L1 `OptimismPortal`, where all native assets are stored, and will not have undergone third-party auditing.
4545

46-
* Lack of future compatibility: Without official support from core protocol developers, there is no guarantee that future OP Stack upgrades will function properly with CGT-based chains.
46+
* Lack of future compatibility: Without official support from core protocol developers, there is no guarantee that future OP Stack upgrades will function properly with CGT-based chains.
4747

4848
### Need help?
4949

0 commit comments

Comments
 (0)