https://astrograph.io Summary: Astrograph is a framework that lowers the entry threshold to the Stellar ecosystem and makes it possible to develop Stellar-based applications in days, not weeks—significantly reducing Stellar application development costs and time-to-market. Instead of doing complex requests using old-school APIs and writing own tooling, developers can use Astrograph to search the ledger using a single GraphQL interface and Astrograph’s own Stellar core data ingester. With Astrograph, it is also possible to work with the Stellar network state in real-time. Astrograph is ready to use, open-source software. We are applying to the SCF to make sure that we’ll have the time to grow and improve Astrograph. Goals Astrograph aims to provide a full-featured GraphQL interface to Stellar network, making the ecosystem more appealing to developers and lowering the entry barrier. Since its first release in April 2019, Astrograph provides access to current and historical state of the ledger, including real-time updates about ongoing changes—all available through a single GraphQL endpoint. The current objectives are: Finish the development of Astrologer — a tool to ingest data from Stellar core node into Elastic Search Switch all queries to use Astrograph's own storage — to reduce the coupling with stellar-core, and remove dependency on Horizon Improve the stability, fix discovered bugs Provide docker images and document deployment scenarios Description : Astrograph is the client-facing GraphQL server for the Stellar ecosystem. It is quite similar to Horizon, except that instead of exposing RESTful API, it provides a single endpoint to explore the Stellar network state and history using powerful GraphQL queries. It also offers reliable WebSocket-based subscriptions, allowing developers to add real-time capabilities to the apps faster and with less effort. Check our blog post to get more details about the project. We run a demo instance of Astrograph so you can explore Stellar through GraphQL right in our playground , we welcome you to start testing your queries. At this point, we primarily want to see how our current schema fits your real-world needs and how it can be improved. Are you building a product based on a Stellar network and think you can benefit from GraphQL’s flexibility and ease of use? Feel free to tell us about your specific needs so we can introduce more queries, connections, filters or subscriptions. Links : Astrograph.io Demo playground Github

Awesome project! I will definitely be playing around with the tick subscription in the next iteration.

Awesome! Great to see some more work going on the GraphQL space for Stellar. A few endpoints I'd like to see added which folks using my solution have used would be showing all accounts holding a particular asset. So essentially trustlines filtered by assetcode. Another would be all operations for a given account. In general just being able to ask account and trustline specific questions is a tremendous improvement over what we get with the Horizon API. The last two popular ones would be the ability query by memo values and account metadata keys and values. We're storing a lot of various things in memos and account data these days so being able to list accounts which match those queries is really nice. Overall this is a really solid start, especially interested to see where you're able to take this with your own custom ingestion query engine. That's definitely where I've been heading myself as the Horizon database just leaves so much to be desired and the Core has everything obfuscated in XDRs. Great work so far and good luck!

Great work! It seems that it solves many of the problems of sampling specific combinations of data from Stellar .. We will follow the development, good luck.

This looks like a very good idea to build out! GraphQL APIs are very nice to work with, I would love to integrate your API with my project to generate statistics more easily.

tyvdh Thank you for the detailed feedback! At this stage our biggest challenge is to understand the actual developer needs and evolve the Astrograph schema accordingly, so we really appreciate your insight and query suggestions. I’m happy to say that Astrograph already supports some of those queries: filtering operations by account or by ledger was there from the launch date, and the PR with asset holders functionality have just landed. I started a wiki page which provides a few examples of currently supported queries. Filtering transactions by memo is on our roadmap and we’ll get back to it when we finish the internal ingestion engine and no longer depend on Horizon for historical data. As for filtering accounts by metadata, I think that’s a great idea, I created #157 to track the progress. Currently filtering by data entry key looks pretty straightforward, but I’m not quite sure how to handle filtering by value, which is a raw byte array. I guess simple equality condition for byte arrays wouldn’t be very useful. Could you please elaborate a bit on the use case where you need this functionality and what’s the actual data values look like?

@[deleted] Being able to search keys is good but being able to search key values is even better. In my case I use custom data for one of two things. 1) Storing locations for external data. So if I'm recording an account as a holder or issuer of a particular NFT I may record the metadata for that NFT in an external database with a marker in the issuer account's custom data. In this case the key would be unique and the data would be unknown and thus unnecessary to search for. 2) In the other case however I'm starting in an external database and trying to find a particular account by some marker value. So maybe I have marked accounts with ipfs address locations and would like to be able to find the Stellar account which matches one or more of a particular ipfs address which I have stored in custom data. In this case I would search for the value and not the key. Granted I have to search for the serialized value but that's not difficult as Stellar has the method for how they do the serialization so you just have to do that to the term before searching for it. Hopefully that makes sense. Being able to do both has been very valuable in my own application development and while others have mentioned primarily searching key values and not the data itself both are valuable.

nebolsin Being able to search keys is good but being able to search key values is even better. In my case I use custom data for one of two things. 1) Storing locations for external data. So if I'm recording an account as a holder or issuer of a particular NFT I may record the metadata for that NFT in an external database with a marker in the issuer account's custom data. In this case the key would be unique and the data would be unknown and thus unnecessary to search for. 2) In the other case however I'm starting in an external database and trying to find a particular account by some marker value. So maybe I have marked accounts with ipfs address locations and would like to be able to find the Stellar account which matches one or more of a particular ipfs address which I have stored in custom data. In this case I would search for the value and not the key. Granted I have to search for the serialized value but that's not difficult as Stellar has the method for how they do the serialization so you just have to do that to the term before searching for it. Hopefully that makes sense. Being able to do both has been very valuable in my own application development and while others have mentioned primarily searching key values and not the data itself both are valuable.

My primary concern at the moment is being able to filter accounts based on signers and home domains.

You've probably seen it, but if not: https://thegraph.com/

Hi there 👋 Astrograph team here. Recently we introduced a couple of useful queries to Astrograph schema: filtering accounts by data entry keys and values (as @tyvdh requested): accounts( data: { name: "foo", value: "bar" }, first: 5 ) { nodes { id } } } querying assets from issuer’s account node: account(id: "GBSTRUSD7IRX73RQZBL3RQUH6KS3O4NYFY3QCALDLZD77XMZOPWAVTUK") { assets(first: 5) { nodes { code holdersCount unauthorizedHoldersCount totalSupply authRequired } } } } Playground still available at https://demo.astrograph.io/graph

Astrograph — Explore the new horizons of Stellar network

nebolsin

MisterTicot signer type is part of the schema now: https://github.com/astroband/astrograph/pull/172

charlie_wasp

Hello, folks! Astrograph team here 🚀 Some quick project updates:

1) We added our own payment paths finding mechanism. We don't use Horizon for it anymore. Here how it looks:

{
  findPaymentPaths(
    sourceAccountID: "GA4DMQ3VSHIVROQ42PJVJOD7X4PYT5BXAWV672CAWOWIADXC3RGZEOMZ",
    destinationAsset: "USD-GBSTRUSD7IRX73RQZBL3RQUH6KS3O4NYFY3QCALDLZD77XMZOPWAVTUK",
    destinationAmount: "0.3"
  ) {
    sourceAsset {
      id
    }
    destinationAsset {
      id
    }
    sourceAmount
    path {
      id
    }
  }
}

There are some differences with Horizon output. Astrograph returns only one best path for each asset in source account's trustlines (plus native lumens). Also, it doesn't search for "detour" if the source account has destination asset in its trustlines.

2) We drop Horizon usage in serving orderbooks too. The schema stays the same

Astrograph still has a playground at https://demo.astrograph.io/graph. And we still would love to hear your feedback 🙂

mangadul

nebolsin very usefull project

nebolsin

StellarGuard currently there's no query to get all the voters for given inflation destination, but it sounds like the one relatively easy to implement. Could you please create an issue with this feature request, so we don't forget about it: https://github.com/astroband/astrograph/issues.

mangadul

mangadul bostravel sakura Thank you for taking time to review and evaluate our project. Please let us know if you face any bugs or missing features.

bostravel

nebolsin need more cool tools on stellar just like this. I like this

StellarGuard

Is there a way to get all accounts who have set a given inflation destination?

charlie_wasp

StellarGuard now there is 😃 You can query them like this: accounts(inflationDestination: "GBZD..H25T", first: 5)

sakura

Great project, I will try it later.

sakura

I hope this project has great performance.

StellarGuard

charlie_wasp Great! Thanks!

manug96

Hey, I am currently thinking of developing an application using astrograph. Is it possible to find transactions by memo?

« Previous Page