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
Extract the following details to get denom trace information:
5
+
- **hash** (string): The hash of the denomination to trace
5
6
6
-
**Description**:
7
-
This query retrieves the denomination trace for a specific hash within the IBC (Inter-Blockchain Communication) module. Denomination traces are essential for tracking the origin and path of tokens as they move across different blockchain networks. Understanding denomination traces helps in verifying token authenticity, preventing double-spending, and ensuring seamless cross-chain operations.
- **countTotal** (boolean): Whether to count total records
62
39
63
-
**Description**:
64
-
This query fetches a list of all denomination traces within the IBC module, with optional pagination parameters. Denomination traces track the movement and origin of tokens across different chains, ensuring transparency and security in cross-chain transactions. Monitoring denomination traces helps in auditing token flows, identifying token sources, and maintaining the integrity of the token ecosystem.
40
+
Provide the request in the following JSON format:
65
41
66
-
**Request Format**:
67
42
\`\`\`json
68
43
{
69
44
"pagination": {
70
-
"limit": number, // (Optional) Number of denomination traces to retrieve
71
-
"offset": number // (Optional) Starting point for retrieval
45
+
"key": "",
46
+
"offset": 0,
47
+
"limit": 100,
48
+
"countTotal": true
72
49
}
73
50
}
74
51
\`\`\`
75
52
76
-
**Example Request**:
53
+
The response will contain an array of denom traces:
54
+
- **denomTraces** (array): List of denomination traces, each containing:
55
+
- **path** (string): Chain of port/channel identifiers
56
+
- **baseDenom** (string): Base denomination
57
+
- **pagination** (object): Pagination response information
58
+
59
+
Response format:
60
+
77
61
\`\`\`json
78
62
{
63
+
"denomTraces": [
64
+
{
65
+
"path": "transfer/channel-0/transfer/channel-1",
66
+
"baseDenom": "uatom"
67
+
},
68
+
{
69
+
"path": "transfer/channel-2",
70
+
"baseDenom": "uosmo"
71
+
}
72
+
],
79
73
"pagination": {
80
-
"limit": 10,
81
-
"offset": 0
74
+
"nextKey": "",
75
+
"total": 10
82
76
}
83
77
}
84
78
\`\`\`
85
79
86
-
**Response Format**:
87
-
\`\`\`json
88
-
{
89
-
"height": number,
90
-
"txHash": string,
91
-
"codespace": string,
92
-
"code": number,
93
-
"data": string, // Optional: Base64 encoded data containing list of denomination traces
This message broadcasts a transaction to perform an IBC (Inter-Blockchain Communication) transfer. IBC transfers enable the movement of tokens between different blockchain networks, facilitating interoperability and expanding the utility of assets across multiple ecosystems. Successfully executing an IBC transfer ensures that tokens are securely and accurately moved to the intended recipient on the target chain.
85
+
Extract the following details for IBC token transfer:
86
+
- **sourcePort** (string): Source port ID (e.g., "transfer")
87
+
- **sourceChannel** (string): Source channel ID
88
+
- **token** (object): Token to transfer containing:
89
+
- **denom** (string): Token denomination
90
+
- **amount** (string): Token amount
91
+
- **receiver** (string): Receiver address on destination chain
0 commit comments