Devnet Deployment

1. Some macOS machine showing an issue with forge while trying the devnet deployment. We are working on it and will give an update once it is resolved. If you are facing the same issue, please mention your machine architecture details in the feedback log.

2. Devnet deployment failed with the following error message.

   failed to solve: ethereum/client-go:v1.13.15: failed to resolve source metadata for docker.io/ethereum/client-go:v1.13.15: error getting credential
   

   Solution: Change the docker config file

   1. Run the following command

      nano $HOME/.docker/config.json
      

   2. If the value of credsStore is set as desktop , replace it to osxkeychain  and save.

   3. Retry the devnet deployment

Testnet Deployment

1. The contract deployment stage is taking longer than the expected 15–30 minutes. What should I do in this case?

   Solution:

   Typically, contract deployment completes within the expected timeframe under normal conditions. However, if you feel stuck, consider the following checks:

   1. Verify account balance — Ensure your account meets the minimum balance requirement as specified in the prerequisites.
   2. Check network conditions — A congested network or high gas fees can delay the deployment process. Confirm if the network is experiencing heavy traffic.
   3. Retry if necessary — If everything appears correct but the deployment is still stuck, you may exit the process and restart the deployment using the SDK. While retrying on the testnet doesn't involve real funds, mainnet deployments do, so proceed with caution.

   If you need further assistance, feel free to contact us via the support form or Discord.

2. Even I deployed the chain with trh-sdk deploy command, the chain is not working fine as I follow this double check guide.

   • op-geth and op-node pod are still pending.
   • op-batcher and op-proposer are still being initiated.

   Solution:

   1. Get the helm release name with the following command.

      Command: helm list -n <chain-name>

      helm list -n grass
      NAME                	NAMESPACE	REVISION	UPDATED                                	STATUS  	CHART                  	APP VERSION
      external-secrets    	grass    	1       	2025-05-13 08:53:02.824664508 +0000 UTC	deployed	external-secrets-0.16.2	v0.16.2    
      grass-1747126592    	grass    	1       	2025-05-13 09:03:48.135846506 +0000 UTC	deployed	thanos-stack-1.0.5     	           
      op-bridge-1747126664	grass    	1       	2025-05-13 08:57:47.287060347 +0000 UTC	deployed	op-bridge-1.0.2     
      

      

   2. Uninstall the helm chart with the following command

      Command: helm uninstall <release-name> -n <chain-name>

      ubuntu@ip-172-31-8-20:~$ helm uninstall grass-1747126592  -n grass
      release "grass-1747126592" uninstalled
      

   3. Reinstall the helm chart. (Please make sure that you run the command in the root of deployment directory.)

      Command: helm install <release-name> ./tokamak-thanos-stack/charts/thanos-stack --values ./tokamak-thanos-stack/terraform/thanos-stack/thanos-stack-values.yaml --namespace <chain-name>

      ubuntu@ip-172-31-8-20:~$ helm install grass-1747126592 ./tokamak-thanos-stack/charts/thanos-stack --values ./tokamak-thanos-stack/terraform/thanos-stack/thanos-stack-values.yaml --namespace grass
      NAME: grass-1747126592
      LAST DEPLOYED: Tue May 13 09:50:28 2025
      NAMESPACE: grass
      STATUS: deployed
      REVISION: 1
      TEST SUITE: None
      
      

   4. Please wait for 5 mins and double check if everything is working well following this guide.