We're providing a different angle to the blockchain data stack - one where the developer is in control of every stage of the data pipeline.

Our mission is to enable great end-user experiences. User experience doesn't just mean great UI, design, and more. To us, a great user experience means enabling teams to:

• provide truly real-time data to their users
• allow users to access data in intuitive ways
• control the data with minimum lock-in

Real-time is the difference between using the blockchain for analytics and background processes, and using blockchain data for your front-end.

Without real-time data, teams have to either compromise on the user experience by exposing delayed data to their users, or mock a real-time experience by using off-chain data.

With real-time data, teams can have a snappy live experience without having to manage complex backends. They can use Goldsky to build a representation of the blockchain that they treat as their single source of truth.

With this definition of real-time, batch processing pipelines don't cut it. Even a 5 second refresh rate is not real-time. Goldsky is designed to ingest, transform, and deliver data as soon as the block registers on the chain (and in the future, before they register).

Blockchain data is most commonly served in two ways:

1. SQL-based interfaces, powered by a backing warehouse or datalake implementation (the Public BigQuery Dataset, Dune, etc)
2. REST/GraphQL APIs, often with fixed or limited search parameters

SQL data interfaces usually have 1s+ response times for medium-to-complex queries, and aren't suited for real-time apps. The way they're implemented also means that the data is refreshed in intervals rather than in real-time. Great for analytics, less so for user experiences.

APIs tend to respond a lot faster and can have real-time data, but are limited in how you fetch your data. If a team needs an aggregation (all volume in the last X hours) and the API doesn't support it, they would have to grab raw data from that API and aggregate it themselves.

Goldsky allows teams to select and define the data they need, then pipe it into an API, managed database, or their own infrastructure with Bridges. Every bridge we offer supports real-time syncing with re-org handling. This offers unparalleled flexibility and the ability to always have the right data in the right backend for users.

Finally, we wanted to make sure that the teams using us felt in control as much as possible.

• Dedicated database instances first over shared instances
• Ability to pipe into your data infrastructure
• No trade-offs with exports - it’s a first-class citizen

A bit of alpha...