Update tuto "Explorer"

[MathieuConte]

This PR aims to:

• update obsolete info, links, and illustrations from the " Explorer" tutorial
• Remove the " Smart contract interaction " part which is related to the nemeton Testnet

Action items :

• Remove the " Smart contract interaction " part
• Change Title from " Explorer & smart contract" to " Explorer"
• Change all the links related to the nemeton Explorer
• Modify step " Send Transaction " by replacing an illustration and the new explorer address
• Reorganize some points

Suggestions:

Should we modify the GitHub repo "Awesome block explorer"?

There is a link to this repo in the tutorial. Maybe we have to update something but I'm not sure about what we have to change in this repo (some testnet links and some documentation links)

Summary by CodeRabbit

• Documentation
  • Updated links and text in the tutorial for the OKP4 Explorer, including changing references to the "OKP4 Drunemeton testnet" and minor adjustments to instructions for interacting with the explorer interface.

[coderabbitai]

Walkthrough

The recent update focuses on refining the documentation for the OKP4 Explorer by specifically renaming references from "OKP4 testnet" to "OKP4 Drunemeton testnet." This change ensures clarity and specificity in the documentation. Additionally, there are slight modifications to the instructions for utilizing the explorer's interface, enhancing user guidance without altering the fundamental operations or logic of the explorer.

Changes

File Path	Change Summary
docs/tutorials/explorer-sc.md	Updated references from "OKP4 testnet" to "OKP4 Drunemeton testnet" and minor instructional adjustments.

🐰✨
In the realm of codes and nets, a change does stir,
From testnet to Drunemeton, the documents concur.
With hops and skips, instructions refine,
A guide through the digital vine.
Celebrate we do, with a cheer,
For clarity and guidance, ever so near.
🌟📚

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
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• 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 tests 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 from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.
• The JSON schema for the configuration file is available here.
• 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/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between f3b47cb and d2cbc48.

Files selected for processing (1)

• docs/tutorials/explorer-sc.md (4 hunks)

Files skipped from review due to trivial changes (1)

• docs/tutorials/explorer-sc.md

[bot-anik]

Device	URL
desktop	http://localhost:3000/

Device	URL
mobile	http://localhost:3000/

Not what you expected? Are your scores flaky? GitHub runners could be the cause.
Try running on Foo instead

[ccamel]

This LGTM. I'm just holding off for the fix in axone-protocol/axoned#583 to address the linter issue you have in this PR.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between a86cdff and c713ca2.

Files selected for processing (1)

• docs/tutorials/explorer-sc.md (4 hunks)

Files skipped from review as they are similar to previous changes (1)

• docs/tutorials/explorer-sc.md

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between a86cdff and 738ce52.

Files selected for processing (1)

• docs/tutorials/explorer-sc.md (4 hunks)

Files skipped from review as they are similar to previous changes (1)

• docs/tutorials/explorer-sc.md

[ccamel]

Great! Thx 👍