Skip to content

Latest commit

 

History

History
19 lines (15 loc) · 934 Bytes

README.md

File metadata and controls

19 lines (15 loc) · 934 Bytes

How to fetch data from Karura

  • acala.js: Querying the chain directly (?). I went with this option after having issues with using the SubQuery (outdated KSM price).
  • Karura SubQuery: Probably the sweetspot, as it's low maintenance for the user and yields a load of readily aggregated data. Currently has issues and is thus not up-to-date.
  • Self-rolled SubQuery: Most effort, but also most control. Custom aggregations take strain from the client-side. Reliability is basically defined by the provider and team behind the SubQuery project.

Two random addresses for testing:

  • omRCxDttLgqMeTADypXT5PDss23ucFPUWDy8rTvd9up6jen
  • p7nKeJt1wXXE8UCSgKKvsHn5ysZNx9vKXkbzSxjSg2oT4hX

Sorry random user, if this your address and you don't wish to see it here, notice me and I will remove it asap!