Skip to content

Conversation

@tupui
Copy link
Contributor

@tupui tupui commented Dec 23, 2025

I am opening this to add Exaion as a RPC provider and also to discuss the general structure of the service providers in the docs.

Exaion first: https://crypto.exaion.com/protocols/stellar

From the French electricity and already being used behind the scene by real businesses.


(I can spin this off into an issue if wanted.)

On the structure. After #2055 we now have a few pages for service providers: API, Analytics, Indexers and Oracles.

I had a hard time to find some providers as I was expected them to be in indexers and they ended up being in Analytics. E.g. SonarX, whose description states that it is an indexer. I was also looking for Quasar and saw that there was a specific page for Galexie provider. Same goes with Dune which I also thought would be listed as an indexer.

After discussing with @chadoh and others, we all seem to have varying definitions on what is an indexer, a data provider, something else.

Hence, I would suggest to flatten and simplify the structure to help users find their way. Have a single Analytics-Indexing section (name to be defined) and have a single provider page for it, with sections if we want to separate concerns.

Reviewing this, I also found some other services which could be added: Zettablock (I read there is a SDF partnership even?), Bitwave (had a SCF), BlockEden, 3xpl, Ginco, Bitquery.

Some products seem to also gain capabilities. e.g. Quicknode shows on their page that indexing like features might be coming soon. Same with validationcloud with their new Mavrik Data x Ai.

I am happy to work on making a proposal. Let me know!

cc @johncanneto

Copy link
Contributor

@ElliotFriend ElliotFriend left a comment

Choose a reason for hiding this comment

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

Thanks for the contribution and thoughts, @tupui !!

You bring up some great points and really important things to consider. I tend to agree that the data/providers pages can be somewhat confusing to navigate and figure out the lay of the land.

I think it would make the most sense to spin that into an issue of its own where we could figure out and discuss a better strategy. That way we can get this simple addition added and merged without waiting on any other conversation or decisions.

How does that sound to you?

As a heads-up: SDF is on a holiday break until the new year. So, you may not hear much input from others until then.

@tupui
Copy link
Contributor Author

tupui commented Dec 24, 2025

Hey @ElliotFriend 👋

Same here haha. Merry Christmas to you and the team and a happy new year 🎊!!

I will make an issue with the last part of my message 👍

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

Successfully merging this pull request may close these issues.

2 participants