You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/index.html
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -9482,7 +9482,7 @@ <h1>executeSQL</h1>
9482
9482
<p></p>
9483
9483
<p class="marked">Execute SQL in a project. Go to "Data Studio" -> "SQL Editor", write your query and then click "Export as cURL"
<p class="marked">API to get Sentio call trace. It takes `txId.txHash` and `chainSpec.chainId` arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID.
18999
18999
19000
-
The results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.
19000
+
The results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/v1.0/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.
19001
19001
19002
19002
This allows you to build chart that marks the order of fund flow.
Copy file name to clipboardExpand all lines: openapi.json
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -225,7 +225,7 @@
225
225
"/api/v1/analytics/{owner}/{slug}/sql/execute": {
226
226
"post": {
227
227
"summary": "Execute SQL",
228
-
"description": "Execute SQL in a project. Go to \"Data Studio\" -\u003e\"SQL Editor\", write your query and then click \"Export as cURL\"\n\n.png)\n\nFind more: https://docs.sentio.xyz/reference/data#sql-api",
228
+
"description": "Execute SQL in a project. Go to \"Data Studio\" -\u003e\"SQL Editor\", write your query and then click \"Export as cURL\"\n\n.png)\n\nFind more: https://docs.sentio.xyz/reference/data#sql-api",
229
229
"operationId": "ExecuteSQL",
230
230
"responses": {
231
231
"200": {
@@ -1128,7 +1128,7 @@
1128
1128
"/api/v1/metrics/{owner}/{slug}/query_range": {
1129
1129
"post": {
1130
1130
"summary": "Metric range queries",
1131
-
"description": "The easiest way to build query is through UI, you could first create an insight chart, and then **Export as cURL**.\n\n.png)",
1131
+
"description": "The easiest way to build query is through UI, you could first create an insight chart, and then **Export as cURL**.\n\n.png)",
1132
1132
"operationId": "QueryRange",
1133
1133
"responses": {
1134
1134
"200": {
@@ -1222,7 +1222,7 @@
1222
1222
"/api/v1/prices/add_coin_by_gecko": {
1223
1223
"post": {
1224
1224
"summary": "Add coin by Gecko",
1225
-
"description": "adds a coin by its coingecko id.\n\ncoingecko id the API ID of the coin in coingecko web page.\n\nplease AWARE that the coingecko id is NOT the same as the symbol of the coin.\n\n",
1225
+
"description": "adds a coin by its coingecko id.\n\ncoingecko id the API ID of the coin in coingecko web page.\n\nplease AWARE that the coingecko id is NOT the same as the symbol of the coin.\n\n",
"description": "API to get Sentio call trace. It takes `txId.txHash` and `chainSpec.chainId` arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID.\n\nThe results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.\n\nThis allows you to build chart that marks the order of fund flow.\n\n%20(1)%20(1)%20(1).png)",
2577
+
"description": "API to get Sentio call trace. It takes `txId.txHash` and `chainSpec.chainId` arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID.\n\nThe results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/v1.0/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.\n\nThis allows you to build chart that marks the order of fund flow.\n\n%20(1)%20(1)%20(1).png)",
@@ -1074,11 +1074,11 @@ export class DebugAndSimulationService {
1074
1074
* Get trace by transaction
1075
1075
* API to get Sentio call trace. It takes `txId.txHash` and `chainSpec.chainId` arguments, where the first is transaction hash, and the second is the numeric ethereum chain ID.
1076
1076
*
1077
-
* The results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/main/.gitbook/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.
1077
+
* The results looks very similar to the normal [Ethereum call trace](https://raw.githubusercontent.com/sentioxyz/docs/v1.0/assets/image%20(2)%20(1)%20(1)%20(1).png). But we have an additional `startIndex` and `startIndex` on each trace entry even for the LOG, representing the execution order in the trace.
1078
1078
*
1079
1079
* This allows you to build chart that marks the order of fund flow.
0 commit comments