Feedback on using the SuperchainERC20 Starter Kit

[zainbacchus]

Hi there! We noticed you recently forked the SuperchainERC20 Starter Kit and were curious if you had any feedback you could share.

We'd love to know:

• How'd you find the starter kit?
• What were you looking to do?
• Was it easy to follow?
• Did you deploy a SuperchainERC20 token? If so, where? If not, why?
• How can we improve it?

Thanks,
Zain & @pharger

Requesting feedback from:
@bartolampb
@jeanevanss813
@nruthqxo2u
@ronaldperez7708056
@williamwalker2122094
@melinonoori
@xlinda2758
@edwardmiller8192501
@mylenegokmen
@reinhildtempl
@kevinedwards1335670
@paulmiller3600281
@hamzahaluk
@mishunir
@ReimagineTruth
@mdqst
@Cryptomoon7
@leopardracer
@yusufky63
@parseb
@lennardevertz
@diempi
@leonkanosekprouqe08
@garstkentxed5l1
@RamirezXxX
@shulsejigemi14
@varlandy7c5h8
@frolovqfm9
@lunzwetiwakejezo
@lilianamolfettadwgj3
@berhalterhofzm9p2
@heightgco9
@matthiesqopicukamalu
@roxanewzg0
@martiebuttersjwb
@lenzwillandrjp8
@fullertonkypercgc5gxj5a
@minmimuyemivayi
@aderholtdamolomev
@lenjonemcse
@HullyAI
@Wanmea
@Farzad3000
@erikside
@hulk0x
@BunsDev
@FractalVisionz
@FDDImax
@soldat13

[zainbacchus]

Requesting feedback from (cont):
@Ahverdil
@matizion
@robocups
@0xmjqarai
@naserkhomari
@adelalizadeh13
@naserya10
@Nassami1
@nsking7
@saeed21
@JRojeres
@khosroaraz
@bars26
@romz237
@whyte01
@hamedn53sv
@JaysonKit241990
@Josofia
@Bangbee13
@lardydellvunulobij
@silasteofila
@nataljalewis13354
@escamillamirad
@riikkaprez
@levensrabulas
@luigibolden
@balduinomalacan
@jonnadekok
@Phuong2554
@Hoangphuong2551
@bizzyisme146
@m4zeftiedwards
@nanceewilmott53
@kimbroshanon
@habcav856
@manupakhorshidul320
@rahcfbipomg
@gayetosijek
@dhdrgd97
@hoangphuong2550
@MrTrade59
@kgblackst0ne
@opthailand
@YINDEE9
@Agustinus13
@Chronique
@Sommatra
@jhont666
@Sanrababa
@Polonssk

[zainbacchus]

Requesting feedback from (cont):
@Morratt
@hamedsheibani
@Sfirnando
@olgamiran
@sakuragund
@pavel9213
@Nidish-Devops
@TheSalade
@YFiN99
@Ramees4
@mlinyekxy
@mikl10
@Guyincharge001
@MpcOS77
@tabshaikh
@Jensey35
@omahs
@tarunkhasnavis
@jessgusclark
@pariaskh
@s4rv4d

[TheSalade]

Hey,

• I found it by searching for the Superchain application on Google and the Superchain forum
• I am looking to build a Superchain Hyperlane Bridge
• Yeah, the template is really easy to use. I deployed the template token without difficulty
• I deployed a few to test my bridge. I started on the OP testnet
• For new features, I will certainly have more ideas in the future. I will come back with them

[Bangbee13]

Better i look the newly features right

[Agustinus13]

Yeah. That's a good plan. I agree with that. Pada Kam, 12 Des 2024 03.33, TRTtheSalad ***@***.***> menulis:

…

Hey, - I found it by searching for the Superchain application on Google and the Superchain forum - I am looking to build a Superchain Hyperlane Bridge - Yeah, the template is really easy to use. I deployed the template token without difficulty - I deployed a few to test my bridge. I started on the OP testnet - For new features, I will certainly have more ideas in the future. I will come back with them — Reply to this email directly, view it on GitHub <#586 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BH6WVWP26ZLJQP7VONKSPIL2FCHQTAVCNFSM6AAAAABTMCVKVOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNJTGY4TIMA> . You are receiving this because you were mentioned.Message ID: ***@***.*** .com>

[mlinyekxy]

what this? Pada Kam, 12 Des 2024 02.56, Agustinus13 ***@***.***> menulis:

…

Yeah. That's a good plan. I agree with that. Pada Kam, 12 Des 2024 03.33, TRTtheSalad ***@***.***> menulis: > Hey, > > - I found it by searching for the Superchain application on Google and > the Superchain forum > - I am looking to build a Superchain Hyperlane Bridge > - Yeah, the template is really easy to use. I deployed the template > token without difficulty > - I deployed a few to test my bridge. I started on the OP testnet > - For new features, I will certainly have more ideas in the future. I > will come back with them > > — > Reply to this email directly, view it on GitHub > < #586 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/BH6WVWP26ZLJQP7VONKSPIL2FCHQTAVCNFSM6AAAAABTMCVKVOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNJTGY4TIMA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.*** > .com> > — Reply to this email directly, view it on GitHub <#586 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJRFKT3VDYGRJMTT5HNTI732FCKG5AVCNFSM6AAAAABTMCVKVOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNJTG4YTCNI> . You are receiving this because you were mentioned.Message ID: ***@***.*** .com>

[parseb]

The tooling works. Feels good.
Seeing totalSuppy sync across chain feels magical and a bit scary.
The muti-super-chain deployment and environment feels maybe a bit too opinionated but it's probably just because it packs a lot. The downside being the environment is token focused so any higher level interactions are designed and tested elsewhere. Which is actually not that bad. Anyway, does what it was designed to do.

[Abuchtela]

1. How’d you find the starter kit?

I discovered the starter kit while researching tools for building on the Optimism Superchain. It was mentioned in a developer forum as a good starting point for creating scalable ERC20 tokens.

2. What were you looking to do?

My goal was to experiment with deploying an ERC20 token that could operate seamlessly across the Superchain ecosystem. I wanted to understand how interoperability works between chains and assess how the kit could be used for projects like public goods funding or Sybil-resistant tools.

3. Was it easy to follow?

The setup instructions were clear, and the code was well-organized. However, I think adding a detailed flow diagram showing how the token interacts across chains would help beginners grasp the multi-chain logic more intuitively.

4. Did you deploy a SuperchainERC20 token? If so, where? If not, why?

Yes, I deployed a SuperchainERC20 token on a testnet to experiment with the functionality. I used the Optimism Goerli testnet, which worked smoothly. However, for those new to deploying contracts, additional steps or troubleshooting tips (e.g., funding the wallet or handling deployment errors) might be helpful.

5. How can we improve it?
   • Provide a step-by-step guide with visuals for non-technical users.
   • Include common use cases or scenarios, such as integrating the token with dApps or bridging between chains.
   • Add a section on testing and verifying the deployment. For instance, how to interact with the token using a block explorer or web3 tools.
   • Offer more guidance on deploying on mainnet, including cost estimates and best practices.

[JaysonKit241990]

is there a step by step guide on how to do this? Deploying a SuperchainERC20 ?

…

On Mon, Jan 27, 2025 at 9:15 AM amber buchtela ***@***.***> wrote: 1. How’d you find the starter kit? I discovered the starter kit while researching tools for building on the Optimism Superchain. It was mentioned in a developer forum as a good starting point for creating scalable ERC20 tokens. 2. What were you looking to do? My goal was to experiment with deploying an ERC20 token that could operate seamlessly across the Superchain ecosystem. I wanted to understand how interoperability works between chains and assess how the kit could be used for projects like public goods funding or Sybil-resistant tools. 3. Was it easy to follow? The setup instructions were clear, and the code was well-organized. However, I think adding a detailed flow diagram showing how the token interacts across chains would help beginners grasp the multi-chain logic more intuitively. 4. Did you deploy a SuperchainERC20 token? If so, where? If not, why? Yes, I deployed a SuperchainERC20 token on a testnet to experiment with the functionality. I used the Optimism Goerli testnet, which worked smoothly. However, for those new to deploying contracts, additional steps or troubleshooting tips (e.g., funding the wallet or handling deployment errors) might be helpful. 5. How can we improve it? • Provide a step-by-step guide with visuals for non-technical users. • Include common use cases or scenarios, such as integrating the token with dApps or bridging between chains. • Add a section on testing and verifying the deployment. For instance, how to interact with the token using a block explorer or web3 tools. • Offer more guidance on deploying on mainnet, including cost estimates and best practices. — Reply to this email directly, view it on GitHub <#586 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJB366MLMEKDG5RLY7FDXW32MWCEJAVCNFSM6AAAAABTMCVKVOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOJWGM2TIMQ> . You are receiving this because you were mentioned.Message ID: ***@***.*** .com>

[Abuchtela]

Should be able to find the documentation here.... https://docs.optimism.io/app-developers/starter-kit

[Abuchtela]

To deploy a SuperchainERC20 token across the Superchain, you can utilize the SuperchainERC20 Starter Kit, which streamlines the creation, deployment, and testing of these tokens. Here’s a step-by-step guide:

1. Install Foundry

The SuperchainERC20 Starter Kit requires anvil, part of the Foundry toolchain. Follow the Foundry installation guide to set it up.

2. Clone the Repository

Clone the SuperchainERC20 Starter Kit repository and navigate into its directory:

git clone https://github.com/ethereum-optimism/superchainerc20-starter.git
cd superchainerc20-starter

3. Install Dependencies

Install the project dependencies using pnpm:

pnpm install

4. Initialize Environment Variables

Set up your environment variables by initializing the .env files:

pnpm init:env

5. Start the Development Environment

Launch the local development environment:

pnpm dev

6. Configure RPC URLs

Edit the .env files to include the RPC URLs of the chains where you intend to deploy your token. Ensure these URLs point to the correct network endpoints.

7. Modify Deployment Configuration

Adjust the deployment configuration parameters in the deploy-config file to suit your token’s specifications. This includes setting the token name, symbol, initial supply, and other relevant details.

8. Deploy the Token

With the configurations in place, deploy your SuperchainERC20 token:

pnpm deploy

This command will deploy the token contract to the specified chains, ensuring it has the same address across all deployments.

Best Practices:
• Use Create2 for Deployment: To maintain a consistent contract address across all chains, utilize the Create2 deployment method. This ensures your token remains fungible across different networks.
• Set Safe Permissions: Configure crosschainMint and crosschainBurn permissions carefully to prevent unauthorized minting or burning of tokens.

For more detailed information and advanced configurations, refer to the SuperchainERC20 Starter Kit documentation.

By following these steps, you can successfully deploy a SuperchainERC20 token across the Superchain, enabling seamless interoperability and consistent token behavior across multiple chains.

[Abuchtela]

To deploy a SuperchainERC20 token across the Superchain, you can utilize the SuperchainERC20 Starter Kit, which streamlines the creation, deployment, and testing of these tokens. Here’s a step-by-step guide:

1. Install Foundry

The SuperchainERC20 Starter Kit requires anvil, part of the Foundry toolchain. Follow the Foundry installation guide to set it up.

2. Clone the Repository

Clone the SuperchainERC20 Starter Kit repository and navigate into its directory:

git clone https://github.com/ethereum-optimism/superchainerc20-starter.git
cd superchainerc20-starter

3. Install Dependencies

Install the project dependencies using pnpm:

pnpm install

4. Initialize Environment Variables

Set up your environment variables by initializing the .env files:

pnpm init:env

5. Start the Development Environment

Launch the local development environment:

pnpm dev

6. Configure RPC URLs

Edit the .env files to include the RPC URLs of the chains where you intend to deploy your token. Ensure these URLs point to the correct network endpoints.

7. Modify Deployment Configuration

Adjust the deployment configuration parameters in the deploy-config file to suit your token’s specifications. This includes setting the token name, symbol, initial supply, and other relevant details.

8. Deploy the Token

With the configurations in place, deploy your SuperchainERC20 token:

pnpm deploy

This command will deploy the token contract to the specified chains, ensuring it has the same address across all deployments.

Best Practices:
• Use Create2 for Deployment: To maintain a consistent contract address across all chains, utilize the Create2 deployment method. This ensures your token remains fungible across different networks.
• Set Safe Permissions: Configure crosschainMint and crosschainBurn permissions carefully to prevent unauthorized minting or burning of tokens.

For more detailed information and advanced configurations, refer to the SuperchainERC20 Starter Kit documentation.

By following these steps, you can successfully deploy a SuperchainERC20 token across the Superchain, enabling seamless interoperability and consistent token behavior across multiple chains.

Info found here and much more....
https://docs.optimism.io/app-developers/starter-kit

@Abuchtela

[naserkhomari]

Yeah. That's a good plan. I agree with that

[Agustinus13]

Yes, I agree. Pada Sel, 28 Jan 2025 06.59, naserkhomari ***@***.***> menulis:

…

Yeah. That's a good plan. I agree with that — Reply to this email directly, view it on GitHub <#586 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BH6WVWKFEBWZEREQQSA6MJ32M3B4TAVCNFSM6AAAAABTMCVKVOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOJXG44TQMY> . You are receiving this because you were mentioned.Message ID: ***@***.*** .com>

[Ramees4]

Good 👍

…

On Tue, 28 Jan 2025, 5:39 am Agustinus13, ***@***.***> wrote: Yes, I agree. Pada Sel, 28 Jan 2025 06.59, naserkhomari ***@***.***> menulis: > Yeah. That's a good plan. I agree with that > > — > Reply to this email directly, view it on GitHub > < #586 (comment)>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/BH6WVWKFEBWZEREQQSA6MJ32M3B4TAVCNFSM6AAAAABTMCVKVOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOJXG44TQMY> > . > You are receiving this because you were mentioned.Message ID: > ***@***.*** > .com> > — Reply to this email directly, view it on GitHub <#586 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXXOCQCQJMEMI4WYG7LOX5D2M3DCJAVCNFSM6AAAAABTMCVKVOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOJXHAYDGNI> . You are receiving this because you were mentioned.Message ID: ***@***.*** .com>

[robocups]

Hi there! We noticed you recently forked the SuperchainERC20 Starter Kit and were curious if you had any feedback you could share.

We'd love to know:

• How'd you find the starter kit?
• What were you looking to do?
• Was it easy to follow?
• Did you deploy a SuperchainERC20 token? If so, where? If not, why?
• How can we improve it?

Thanks, Zain & @pharger

Requesting feedback from: @bartolampb @jeanevanss813 @nruthqxo2u @ronaldperez7708056 @williamwalker2122094 @melinonoori @xlinda2758 @edwardmiller8192501 @mylenegokmen @reinhildtempl @kevinedwards1335670 @paulmiller3600281 @hamzahaluk @mishunir @ReimagineTruth @mdqst @Cryptomoon7 @leopardracer @yusufky63 @parseb @lennardevertz @diempi @leonkanosekprouqe08 @garstkentxed5l1 @RamirezXxX @shulsejigemi14 @varlandy7c5h8 @frolovqfm9 @lunzwetiwakejezo @lilianamolfettadwgj3 @berhalterhofzm9p2 @heightgco9 @matthiesqopicukamalu @roxanewzg0 @martiebuttersjwb @lenzwillandrjp8 @fullertonkypercgc5gxj5a @minmimuyemivayi @aderholtdamolomev @lenjonemcse @HullyAI @Wanmea @Farzad3000 @erikside @hulk0x @BunsDev @FractalVisionz @FDDImax @soldat13

I think everything is fine, I just had some errors during deployment and compilation, which I later realized were due to my own libraries.

[Josofia]

I think everything is fine, I’ve not deployed a SuperchainERC20 token because I’m still gathering my funds for liquidity