Lists taraxa testnet and mainnet

[VargaElod23]

Add New Chain

Thanks for your pull request to add a new support in Sourcify.

If you haven't done so, please follow the instructions on how to request chain support in docs.

Please check the following items before submitting your pull request for a speedy review.

Checklist

• [x] The branch is named as add-chain-<chainId>.
• [x] I haven't modified the chains.json file directly.
• [x] In sourcify-chains.json file
  • [x] I've set supported: true.
  • [x] I haven't added an rpc field but the one in chains.json is used (if not, please explain why).
• [x] I've added a test in chain-tests.js file.
• [x] test-new-chain test in Circle CI is passing.

Summary by CodeRabbit

• New Features

  • Added support for Taraxa Mainnet and Taraxa Testnet with configurations including RPC endpoints and API for fetching contract creation transactions.

• Tests

  • Added verification tests for contracts on Taraxa Mainnet and Taraxa Testnet.

[coderabbitai[bot]]

[!IMPORTANT]

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The changes introduce configuration settings for the Taraxa Mainnet and Testnet into the sourcify-chains-default.json file. Additionally, corresponding tests for verifying contracts on these networks were added to the chains/chain-tests.spec.ts file. These updates enable support and interaction with the Taraxa blockchain networks within the service.

Changes

Files	Change Summary
services/server/src/sourcify-chains-default.json	Added configuration details for Taraxa Mainnet and Testnet, including their names, support status, RPC endpoints, and contract creation transaction API.
services/server/test/chains/chain-tests.spec.ts	Added tests for verifying contracts on Taraxa Mainnet and Testnet.

Poem

In lands of code both near and far,
Where nodes and chains a'dance,
Taraxa now joins the spar,
In both mainnet and testnet's chance.
With endpoints set and tests anew,
In blockchain light, our service grew.
✨🐰💻

---

[!TIP]

Early access features: enabled

We are currently testing the following features in early access: - **OpenAI `gpt-4o` model for code reviews and chat**: OpenAI claims that this model is better at understanding and generating code than the previous models. We seek your feedback over the next few weeks before making it generally available. Note: - You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file. - Please join our [Discord Community](https://discord.com/invite/GsXnASn26c) to provide feedback and report issues. - OSS projects are currently opted into early access features by default.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)

Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

[manuelwedler]

Hey there! Thanks for the PR. We were experimenting with Coderabbit lately, but it should actually not be running on the chain adding PRs. Please ignore these suggestions and remove your last commit. It is not necessary to have the chainId field there.

Could you please also remove the rpc fields? We are already getting these from the chains.json

[VargaElod23]

All done @manuelwedler

[manuelwedler]

Please also remove the chainId fields

[VargaElod23]

Oh, I thought I amended that, sorry, it slipped out somehow. Done now @manuelwedler

[kuzdogan]

Is the given contract for the Taraxa Testnet (842) changed? Now the bytecode of 0x98edEa58C0500287B973348ec315f3d26D0e189A is returning a different result and the test is failing. I can see this PR is from Jul 2 but the explorer shows this contract was deployed on Jul 26: https://testnet.explorer.taraxa.io/address/0x98edea58c0500287b973348ec315f3d26d0e189a Is this testnet being reset?

Please fix the contract otherwise we'll have to remove support for the testnet