Update for TAC Mainnet and fix TAC Testnet #7411
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
You successfully submitted a PR! Due to the amount of PRs coming in: we will only look at PRs that the CI is happy with. We can also not hold your hand getting the CI green - just look how others that where merged did it and RTFM. So as long as there is any CI check that reports an error - no human will look at this. You might be able to ask for some support after supporting the project - e.g. by sending funds to lists.eth. When you fixed things after a requested change - then you also need to (re-)request a review. |
FrederikBolding
approved these changes
Jun 17, 2025
|
PR merged - please consider contributing some funds to lists.eth |
Contributor
Author
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey @ligi sir gm,
I know you're not actively merging PR because of the upcoming onchain registry. However, we just had our genesis mainnet, and there are many teams with automated deployment scripts still targeting this repo (including, but not limited to, Safe, Curve, and more).
Asking all of them to fork this repo and change their deployment script is a big issue for everyone.
As a previous donor to this project, I commit to keep donating for every new merge, and I really hope we can have a soft migration from the GitHub repo to the upcoming onchain registry, but it should be done in a way to minimize disruptions, at least wait for it to be live, or handover the merging privileges to someone else in the community.
Without these merge activities, it's very hard to get the teams deploying on new chains or L2s.
I hope you guys can understand our pain as builders.
With this specific PR i'm adding the details about TAC Mainnet, adding our second testnet that went live 2 months ago and correcting the first testnet data.
I hope you can understand my position.
Many thanks,
Marco