Skip to content

[sui-custom-indexer] How to enable checkpoint stream for use with custom indexer on local node? #22246

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

Open
vladilen11 opened this issue May 28, 2025 · 3 comments

Comments

@vladilen11
Copy link
Contributor

Description

I'm currently running a local Sui node and working on a custom indexer that needs to consume checkpoint stream data in real-time.

Question

So I'd like to ask:

How can I enable the checkpoint stream from the node?
Are there specific configuration options or flags I need to set when starting the node?

Are there any example projects or docs you could point me to for integrating with the checkpoint stream?

Copy link
Contributor

Thank you for opening this issue, a team member will review it shortly. Until then, please do not interact with any users that claim to be from Sui support and do not click on any links!

@vladilen11 vladilen11 changed the title How to enable checkpoint stream for use with custom indexer on local node? [sui-custom-indexer] How to enable checkpoint stream for use with custom indexer on local node? May 28, 2025
@hyd628
Copy link
Collaborator

hyd628 commented May 28, 2025

Hey @vladilen11 , are you using the Mysten customer indexer? https://docs.sui.io/guides/developer/advanced/custom-indexer

@vladilen11
Copy link
Contributor Author

vladilen11 commented May 28, 2025

Yes, I’ve found a working setup for enabling checkpoint data output on a local node.

Here’s what worked for me:

sui start --with-faucet --data-ingestion-dir=./chk --force-regenesis
  • This starts a local node with faucet enabled.

  • The --data-ingestion-dir=./chk flag ensures that checkpoint data is continuously written to the ./chk directory.

  • A custom indexer can then directly read and process checkpoint files from that directory.

However, there's one caveat:

The --force-regenesis flag does not automatically clear the previous contents of the --data-ingestion-dir.
To avoid potential data inconsistency, developers need to manually delete the contents of the ./chk directory before starting the node again with --force-regenesis.

Hope this helps others looking to use checkpoint data in their custom indexing pipelines.

Anyway thanks @hyd628 ❤️

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

No branches or pull requests

2 participants