Arweave TX
Sentio Referral Code: Reach out to @is_ye in the sentio telegram chat and give the referral code evandekim2025 for a 20% discount for Sentio subscription!
Sentio is a game-changing development platform that enables end-to-end data observability for web3 data pipelines. The platform provides a fully integrated, hosted experience that combines modern monitoring, alerting, and debugging capabilities.
What makes Sentio particularly powerful is its real-time processing architecture: developers write and deploy typed processor code to Sentio, which automatically handles everything from historical data backfilling to real-time blockchain streaming, including automatic adjustments for chain reorganizations.
Sentio's TypeScript pipeline interface transforms complex multi-chain development into a straightforward process, eliminating the traditional headaches of handling different blockchain protocols across multiple smart contract languages. The platform excels at:
Supporting diverse blockchains- EVM, SVM, MOVE, Fuel, and Starknet (supported networks)
Strongly typed objects for events and functions
Data processing, observability, and debugging wrapped up in a hosted db solution with easy sql and graphql endpoint creation for analytics
Robust testing suites for data pipelines
To illustrate Sentio's capabilities, let's consider the Sui LST Dashboard, a comprehensive analytics tool built using Sentio pipelines and integrated with Dune's frontend. The sentio processor code can be found here. This dashboard provides real-time insights into the liquid staking ecosystem on the Sui blockchain.
Real-Time Data Streaming: Continuously monitors transactions and events on the Sui network.
Comprehensive Analytics: Utilizes SQL and GraphQL endpoints for detailed data queries and aggregations.
Seamless Integration with Dune: Enables the creation of dynamic and interactive visualizations, making data accessible and actionable for stakeholders.
This infrastructure enables developers to quickly spin up observable data platforms that emit pipeline metrics, event logs, entities, webhook and http endpoint integrations. The great thing here is that it’s all done in the background and all that’s left are for developers to use a polished product.
The integrated nature of these features creates a seamless development experience, where monitoring, debugging, and analytics all work together in real-time, making it significantly easier to build and maintain robust cross chain analytics solutions.
This section is an overview that shows an end to end flow from setting up a Sentio processor with a dune dashboard as an end product. To replicate this process, simply fork the repository and add it to your own Sentio project.
The main entrypoint that Sentio uses is the processor.ts file for instructions on how to index data. Contracts can be added with the command yarn sentio add –chain sui_mainnet contract_address. The abi is generally automatically fetched. Then the command yarn sentio build to generate the typed files.
A processor can be defined by importing a specific class generated from the typings that contain functions. For example you can CTRL + F for onEvent… to find the event function bindings and click through the code to find the decoded data fields that each event holds as well. Some well prompted AI requests can make this process delightfully easy to set up multiple events from a single contract.
Once the processor code has been defined, run the command yarn sentio upload to upload the processor code to Sentio, which will be queued up for indexing. Right out of the box, Sentio is pretty good about automatically finding the best start block point. The indexing (backfilling) process is relatively fast as well. Along the way, additional logs can be implemented into the processor to troubleshoot a data pipeline such as if there is data missing or something is not working the way it should be. These logs will appear in real time when the data gets backfilled.
While Sentio is backfilling data, the project tables get populated in real time, so the query construction work can get started before data has finished backfilling completely. The Data Studio is where exploratory data analytics can be done and queries created for analytics such as daily aggregations, joins, and other transformations.
After the query is ready, endpoints can be created from saved queries in 2 clicks. After the endpoint is created, the data is ready to be used outside of Sentio. In this case, Dune is used as a hosted frontend of choice. An AI connector can be used to craft Dune queries from the Sentio endpoint (see AI Prompt Miscellaneous Section).
Once the data is in dune, then it can be treated as if it was any other Dune query and the dashboard can be created as usual. Note that the query has to be private to hide the Sentio API keys.
Maintaining robust and observable data pipelines is paramount for the success of blockchain applications. Sentio stands out as a powerful tool for developers and data engineers, providing a seamless, integrated platform that streamlines multi-chain development and boosts real-time data observability.
By automating complex processes such as historical data backfilling and real-time blockchain streaming, Sentio not only alleviates the technical burden but also accelerates the development lifecycle. Its comprehensive feature set, including strongly typed objects and robust testing suites, empowers teams to build, monitor, and debug their data pipelines with ease and confidence.
As blockchain technology continues to scale and diversify, data observability tools like Sentio become indispensable for ensuring that data remains reliable, accessible, and actionable.
Context: You are using Dune's LiveFetch functions to execute SQL queries that interact with external APIs. Below is the documentation for the LiveFetch feature, followed by an example endpoint. Use this information to generate SQL queries tailored to specific API endpoints.
Functions and Operators
LiveFetch functions
Description: LiveFetch functions send HTTP requests to a specified URL, allowing interaction with HTTP servers directly within SQL queries. They can fetch data from external APIs or invoke remote procedure calls.
Supported Functions:
http_get(url: varchar) → varchar
http_get(url: varchar, headers: array(varchar)) → varchar
http_post(url: varchar, body: varchar) → varchar
http_post(url: varchar, body: varchar, headers: array(varchar)) → varchar
Additional Details:
Call timeout: 5 seconds
Throttling: 50 requests per second per proxy
Response size limit: 2 MiB
Request size limit (http_post): 1,000,000 bytes
You have an API endpoint accessible via the following curl command:
curl -L -X POST 'https://endpoint.sentio.xyz/evandekim/sui-lst/circulating_lsts' \
-H 'api-key: api_key_here \
-H 'Content-Type: application/json' \
--data-raw '{}'
Your Task:
Generate a Dune SQL query using the LiveFetch functions to interact with the provided API endpoint. Ensure that all necessary headers and the request body are correctly included. If the response is in JSON format, demonstrate how to parse and extract specific fields from the response.
URL: https://endpoint.sentio.xyz/evandekim/sui-lst/circulating_lsts
Method: POST
Headers:
api-key: api_key_here
Content-Type: application/json
Body: {}
Requirements:
Use http_post to send the POST request.
Include the necessary headers.
Handle the JSON response to extract relevant data (e.g., list of circulating LSTs).
Ensure the query adheres to Dune's LiveFetch limitations.
SELECT json_parse(
http_post(
'https://endpoint.sentio.xyz/evandekim/sui-lst/circulating_lsts',
'{}',
ARRAY[
'api-key: api_key_here,
'Content-Type: application/json'
]
)
) AS response_data
To further process the JSON response, you can use Dune's JSON functions. For example:
SELECT
json_extract_scalar(response_data, '$.field_name') AS extracted_field
FROM (
SELECT json_parse(
http_post(
'https://endpoint.sentio.xyz/evandekim/sui-lst/circulating_lsts',
'{}',
ARRAY[
'api-key: api_key_here,
'Content-Type: application/json'
]
)
) AS response_data
)
WITH response AS (
SELECT http_post(
'https://endpoint.sentio.xyz/evandekim/sui-lst/circulating_lsts',
'{}',
ARRAY[
'api-key: api_key_here,
'Content-Type: application/json'
]
) AS resp
),
parsed AS (
SELECT json_parse(resp) AS j
FROM response
),
rows_array AS (
SELECT json_extract(j, '$.syncSqlResponse.result.rows') AS rows_j
FROM parsed
),
unnested_rows AS (
SELECT row_data
FROM rows_array
CROSS JOIN UNNEST(CAST(rows_j AS array(json))) AS t(row_data)
)
SELECT
json_extract_scalar(row_data, '$.event_date') AS event_date,
json_extract_scalar(row_data, '$.token_name') AS token_name,
CAST(json_extract_scalar(row_data, '$.circulating_supply') AS double) AS circulating_supply,
CAST(json_extract_scalar(row_data, '$.cumulative_minted_conv') AS double) AS cumulative_minted,
CAST(json_extract_scalar(row_data, '$.cumulative_redeemed_conv') AS double) AS cumulative_redeemed,
CAST(json_extract_scalar(row_data, '$.circulating_supply_usd') AS double) AS circulating_supply_usd,
CAST(json_extract_scalar(row_data, '$.cumulative_minted_usd') AS double) AS cumulative_minted_usd,
CAST(json_extract_scalar(row_data, '$.cumulative_redeemed_usd') AS double) AS cumulative_redeemed_usd
FROM unnested_rows
WHERE json_extract_scalar(row_data, '$.token_name') not in ('afsui', 'vsui', 'hasui', 'springsui_lsts', 'spring_sui')
