Skip to content

docs: add introduction to Blockchain Indexing#4577

Closed
davd-gzl wants to merge 53 commits into
gnolang:masterfrom
davd-gzl:tx-indexer-docs
Closed

docs: add introduction to Blockchain Indexing#4577
davd-gzl wants to merge 53 commits into
gnolang:masterfrom
davd-gzl:tx-indexer-docs

Conversation

@davd-gzl

@davd-gzl davd-gzl commented Jul 28, 2025

Copy link
Copy Markdown
Member

Close: #2295
Depends on: gnolang/tx-indexer#219

Minimal Documentation to introduce Blockchain indexing through tx-indexer.
I've as well made made an introduction video with a GraphQL live coding example : https://www.youtube.com/watch?v=8ld0nsV37SA.

@github-actions github-actions Bot added the 📖 documentation Improvements or additions to documentation label Jul 28, 2025
@Gno2D2 Gno2D2 requested a review from a team July 28, 2025 10:04
@Gno2D2 Gno2D2 added the review/triage-pending PRs opened by external contributors that are waiting for the 1st review label Jul 28, 2025
@Gno2D2

Gno2D2 commented Jul 28, 2025

Copy link
Copy Markdown
Collaborator

🛠 PR Checks Summary

All Automated Checks passed. ✅

Manual Checks (for Reviewers):
  • IGNORE the bot requirements for this PR (force green CI check)
Read More

🤖 This bot helps streamline PR reviews by verifying automated checks and providing guidance for contributors and reviewers.

✅ Automated Checks (for Contributors):

🟢 Maintainers must be able to edit this pull request (more info)
🟢 Pending initial approval by a review team member, or review from tech-staff

☑️ Contributor Actions:
  1. Fix any issues flagged by automated checks.
  2. Follow the Contributor Checklist to ensure your PR is ready for review.
    • Add new tests, or document why they are unnecessary.
    • Provide clear examples/screenshots, if necessary.
    • Update documentation, if required.
    • Ensure no breaking changes, or include BREAKING CHANGE notes.
    • Link related issues/PRs, where applicable.
☑️ Reviewer Actions:
  1. Complete manual checks for the PR, including the guidelines and additional checks if applicable.
📚 Resources:
Debug
Automated Checks
Maintainers must be able to edit this pull request (more info)

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 The pull request was created from a fork (head branch repo: davd-gzl/gno)

Then

🟢 Requirement satisfied
└── 🟢 Maintainer can modify this pull request

Pending initial approval by a review team member, or review from tech-staff

If

🟢 Condition met
└── 🟢 And
    ├── 🟢 The base branch matches this pattern: ^master$
    └── 🟢 Not (🔴 Pull request author is a member of the team: tech-staff)

Then

🟢 Requirement satisfied
└── 🟢 If
    ├── 🟢 Condition
    │   └── 🟢 Or
    │       ├── 🟢 User MikaelVallenet already reviewed PR 4577 with state APPROVED
    │       ├── 🟢 At least 1 user(s) of the team tech-staff reviewed pull request
    │       └── 🔴 This pull request is a draft
    └── 🟢 Then
        └── 🟢 Not (🔴 This label is applied to pull request: review/triage-pending)

Manual Checks
**IGNORE** the bot requirements for this PR (force green CI check)

If

🟢 Condition met
└── 🟢 On every pull request

Can be checked by

  • Any user with comment edit permission

@n0izn0iz

Copy link
Copy Markdown
Contributor

I think you should use something else than balance as an example, since for that you can simply query the chain.

I think a good example is building a search tool.

Example, for social content: indexing blog posts and building a full-text-search feature over posts content on top of that, which is something that would cost a huge amount of gas if done on-chain.
Also search for usernames is a good example.

@davd-gzl

Copy link
Copy Markdown
Member Author

@n0izn0iz I modified the section to add more detailed and relevant example following your feedback! 👍

@davd-gzl davd-gzl marked this pull request as draft August 1, 2025 11:59
@Gno2D2 Gno2D2 removed the review/triage-pending PRs opened by external contributors that are waiting for the 1st review label Aug 1, 2025
@leohhhn

leohhhn commented Aug 5, 2025

Copy link
Copy Markdown
Contributor

Hey @Davphla, let me know when you are ready for another round of reviews.

@davd-gzl davd-gzl marked this pull request as ready for review August 20, 2025 11:34
@Gno2D2 Gno2D2 added the review/triage-pending PRs opened by external contributors that are waiting for the 1st review label Aug 20, 2025
@davd-gzl

davd-gzl commented Aug 20, 2025

Copy link
Copy Markdown
Member Author

I re-open it.
I reworked it since it was not really great before.

I add a full example implementation step by step (i tried it it's all working great, I can upload it in a separate repository).
It's a lot of code in the documentation, but I believe in that specific case that's the most efficient way to share knowledge.
It's quite hard to implement when you don't know anything about it (as I got when writing this documentation).
I'm open to listen any changes and review!

@codecov

codecov Bot commented Aug 29, 2025

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@leohhhn leohhhn left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey! Thank you so much for working on the docs. I've left a few comments, and I can take a look again soon.

Comment thread docs/resources/indexing-gno.md Outdated
Comment thread docs/resources/indexing-gno.md Outdated
Comment thread docs/resources/indexing-gno.md Outdated
Comment thread docs/resources/indexing-gno.md Outdated
Comment thread docs/resources/indexing-gno.md Outdated
Comment thread docs/resources/indexing-gno.md Outdated
Comment thread docs/resources/indexing-gno.md Outdated
Comment thread docs/resources/indexing-gno.md Outdated
Comment thread docs/resources/indexing-gno.md Outdated
Comment thread docs/resources/indexing-gno.md Outdated
@davd-gzl davd-gzl marked this pull request as draft September 12, 2025 20:23
@Gno2D2 Gno2D2 removed the review/triage-pending PRs opened by external contributors that are waiting for the 1st review label Sep 12, 2025
Comment thread docs/resources/indexing-gno.md Outdated
@davd-gzl

davd-gzl commented Oct 8, 2025

Copy link
Copy Markdown
Member Author

Code available at: https://github.com/samouraiworld/tx-indexer-example (To be moved in Gnoverse).

I've modified through the new update:

  • Remove the database part from the documentation. I think is unrelated to the use of the indexer -- Though it is still available through the link above.
  • Use of embedmd to extract the code to the _assets folder.
  • Use a json structure to match the GraphQL structure

@davd-gzl davd-gzl moved this from In Review to Triage in 🧙‍♂️Gno.land development Apr 14, 2026
@davd-gzl davd-gzl added the a/ux User experience, product, marketing community, developer experience team label Apr 14, 2026
@nemanjantic

Copy link
Copy Markdown

@davd-gzl is this still relevant?

@davd-gzl

Copy link
Copy Markdown
Member Author

Hi @nemanjantic, this is still relevant, I'm gonna rework the content before asking for a review

@davd-gzl

Copy link
Copy Markdown
Member Author

Per gnoverse/gnopls#39, I think this doc is too specialized and should be moved entirely on tx-indexer repository.

@davd-gzl davd-gzl closed this May 12, 2026
@github-project-automation github-project-automation Bot moved this from In Progress to Done in 💪 Bounties & Worx May 12, 2026
@github-project-automation github-project-automation Bot moved this from Waiting for core Review to Done in FlashorgSprint: Gnocore Minicrew 🥷 May 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

a/ux User experience, product, marketing community, developer experience team 📖 documentation Improvements or additions to documentation 🐹 golang Pull requests that update Go code

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

[docs] Add a guide on tx-indexer

8 participants