Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TT-856 two geth chains in crib #11964

Merged
merged 4 commits into from
Feb 8, 2024
Merged

Conversation

Tofel
Copy link
Contributor

@Tofel Tofel commented Feb 8, 2024

  • geth is not using devmode, now it's PoA with 1 node
  • we have 2 ephemermal private testnets
  • we have support for customl CLL node chain-specific TOML configuration

Copy link
Contributor

github-actions bot commented Feb 8, 2024

I see that you haven't updated any CHANGELOG files. Would it make sense to do so?

@Tofel Tofel marked this pull request as ready for review February 8, 2024 13:39
@skudasov skudasov self-requested a review February 8, 2024 14:30
@skudasov skudasov force-pushed the tt_856_two_geth_chains_in_crib branch from 799e223 to 00c495e Compare February 8, 2024 14:32
@skudasov skudasov enabled auto-merge February 8, 2024 14:45
@cl-sonarqube-production
Copy link

SonarQube Quality Gate

Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@skudasov skudasov added this pull request to the merge queue Feb 8, 2024
@skudasov skudasov removed this pull request from the merge queue due to a manual request Feb 8, 2024
@skudasov skudasov added this pull request to the merge queue Feb 8, 2024
Merged via the queue into develop with commit d98ced4 Feb 8, 2024
94 checks passed
@skudasov skudasov deleted the tt_856_two_geth_chains_in_crib branch February 8, 2024 15:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants