[cargopete]

Which issue does this PR close?

None, docs only.

Rationale for this change

nuthatch is an open-source EVM blockchain indexer whose SQL runs on DataFusion, through Burrmill (https://github.com/nuthatch-org/burrmill), over sealed Parquet segments. It is actively maintained.

What changes are included in this PR?

One line in the Known Users list in docs/source/user-guide/introduction.md, in alphabetical order.

What is the testing strategy for this PR?

Docs only.

Are there any user-facing changes?

No.

🤖 Generated with Claude Code

[kosiew]

@cargopete,

Thanks for adding nuthatch to DataFusion's known users. The entry meets the issue's documentation goal, accurately describes the project's EVM indexing and SQL-over-Parquet use case, and fits the existing list structure. The repository's recent activity also satisfies the list's maintenance requirement.

The change stays within the appropriate documentation boundary. nuthatch uses DataFusion through Burrmill, but this section only needs to identify projects using DataFusion, not document their integration architecture. No SQL behavior, public APIs, dependencies, or runtime paths are affected.

I'm approving because the addition is correctly scoped and has no blocking concerns. The documentation formatting checks passed. I left two optional suggestions to improve link durability and accessibility for readers unfamiliar with blockchain terminology.

[kosiew]

Minor suggestion: Could we link directly to https://github.com/nuthatch-org/nuthatch? The current URL redirects there, but using the canonical repository URL avoids depending on the old namespace continuing to redirect. Please verify it resolves to the same project.

[cargopete]

done, it resolves to the same repo. thanks!!

[kosiew]

Minor suggestion: Could we expand EVM to "Ethereum Virtual Machine (EVM)"? This introduction does not define the acronym, and spelling it out would help readers unfamiliar with blockchain terminology.

[cargopete]

good call, spelled out in d4727bc

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.65%. Comparing base (76f9fde) to head (e1cef09).
⚠️ Report is 247 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #26025      +/-   ##
==========================================
- Coverage   82.65%   82.65%   -0.01%     
==========================================
  Files        1147     1147              
  Lines      446087   446087              
  Branches   446087   446087              
==========================================
- Hits       368710   368701       -9     
- Misses      54990    54994       +4     
- Partials    22387    22392       +5     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[alamb]

@cargopete -- this project seems to be a brand new single person project (which is fine) but I wonder how long lived we expect it to be?

@kosiew do you think we should make some sort of criteria to include on this page?

[kosiew]

@alamb

criteria to include on this page

Do you mean adding more criteria besides:

 <!-- "Active" means github repositories that had at least one commit in the last 6 months -->

?

[alamb]

@alamb

criteria to include on this page

Do you mean adding more criteria besides:

 <!-- "Active" means github repositories that had at least one commit in the last 6 months -->

?

Yeah -- like maybe "number of stars" or "number of contributors" or something -- otherwise I worry this page will get full of one person/agent "systems" and the real systems will get drowned out 🤔

@cargopete what is your thinking on this matter?

[alamb]

This PR appears to be waiting on the author to respond to reviewer feedback so marking as draft. Please mark ready to review when it is ready for another look

[cargopete]

@alamb fair question, thanks for asking rather than just merging.

Honest answer: yes, it's mostly me. nuthatch started in July and is still young (about 3.5k commits and 117 releases so far, the latest being 5.11.0 yesterday). It isn't a weekend agent project though. It's what I work on, and early users depend on it. There's a rotki integration in review (rotki/rotki#13375) that lets rotki users pull their account history from their own nest instead of Etherscan, and we run nests for The Graph's indexer tooling.

DataFusion is the SQL engine: nuthatch builds Burrmill with its datafusion feature over sealed Parquet segments plus a live tip, so every SQL query a nest answers runs through DataFusion.

On criteria, a minimum like stars or contributors seems reasonable to me, and we wouldn't clear a stars bar today. If you add one, I'm happy to close this and come back once nuthatch meets it. No hard feelings either way. I just wanted to say thanks to the project in the place you list users.