@ocap/client 1.27.14 → 1.27.16

package/docs/QUERIES.md

@@ -2244,12 +2244,13 @@ No arguments
 * **stakeFilter**, optional, null
 * **delegationFilter**, optional, null
 * **tokenFactoryFilter**, optional, null
+* **includeData**, optional, null
 
 #### Result Format
 
 ```graphql
 {
-  listTransactions {
+  listTransactions(includeData: true) {
     code
     page {
       cursor

package/docs/README.md

@@ -6218,7 +6218,9 @@ Structure of GraphQLClient.ListTransactionsParams
 Checkout the following snippet for the format of ListTransactionsParams:
 
 ```json
-{}
+{
+  "includeData": true
+}
 ```
 
 **Kind**: static typedef of [`GraphQLClient`](#GraphQLClient)\
@@ -6240,6 +6242,7 @@ Checkout the following snippet for the format of ListTransactionsParams:
 | ...stakeFilter        | [`StakeFilterInput`](#GraphQLClient.StakeFilterInput)               |
 | ...delegationFilter   | [`DelegationFilterInput`](#GraphQLClient.DelegationFilterInput)     |
 | ...tokenFactoryFilter | [`TokenFactoryFilterInput`](#GraphQLClient.TokenFactoryFilterInput) |
+| includeData           | `boolean`                                                           |
 
 ### GraphQLClient.ListTokensParams : `object`
 

package/docs/core-concepts-client-architecture.ja.md

@@ -8,33 +8,9 @@ OCAP Client は、さまざまな JavaScript 環境や特定のユースケー
 
 以下の図は、異なるクライアント実装間の関係を示しています。
 
-```d2
-direction: down
-
-GraphQLClientBase: {
-  label: "GraphQLClientBase\n(コア機能)"
-  shape: rectangle
-}
-
-GraphQLClient: {
-  label: "GraphQLClient\n(フルクライアント + ヘルパー)"
-  shape: rectangle
-}
-
-GraphqlClientLite: {
-  label: "GraphqlClientLite\n(ブラウザ向け最適化)"
-  shape: rectangle
-}
-
-NativeGraphqlClient: {
-  label: "NativeGraphqlClient\n(Node.js向け最適化)"
-  shape: rectangle
-}
-
-GraphQLClientBase -> GraphQLClient: "継承"
-GraphQLClientBase -> GraphqlClientLite: "継承"
-GraphQLClient -> NativeGraphqlClient: "継承"
-```
+<!-- DIAGRAM_IMAGE_START:architecture:4:3 -->
+![Client Architecture](assets/diagram/core-concepts-client-architecture-01.jpg)
+<!-- DIAGRAM_IMAGE_END -->
 
 ## クライアント実装
 

package/docs/core-concepts-client-architecture.md

@@ -8,33 +8,9 @@ All client variations are built upon a common base, `GraphQLClientBase`, which p
 
 The following diagram illustrates the relationship between the different client implementations:
 
-```d2
-direction: down
-
-GraphQLClientBase: {
-  label: "GraphQLClientBase\n(Core Functionality)"
-  shape: rectangle
-}
-
-GraphQLClient: {
-  label: "GraphQLClient\n(Full Client + Helpers)"
-  shape: rectangle
-}
-
-GraphqlClientLite: {
-  label: "GraphqlClientLite\n(Browser-Optimized)"
-  shape: rectangle
-}
-
-NativeGraphqlClient: {
-  label: "NativeGraphqlClient\n(Node.js-Optimized)"
-  shape: rectangle
-}
-
-GraphQLClientBase -> GraphQLClient: "Extends"
-GraphQLClientBase -> GraphqlClientLite: "Extends"
-GraphQLClient -> NativeGraphqlClient: "Extends"
-```
+<!-- DIAGRAM_IMAGE_START:architecture:4:3 -->
+![Client Architecture](assets/diagram/core-concepts-client-architecture-01.jpg)
+<!-- DIAGRAM_IMAGE_END -->
 
 ## Client Implementations
 

package/docs/core-concepts-client-architecture.zh-TW.md

@@ -8,33 +8,9 @@ OCAP 用戶端採用模組化架構設計，以滿足不同 JavaScript 環境和
 
 下圖說明了不同用戶端實作之間的關係：
 
-```d2
-direction: down
-
-GraphQLClientBase: {
-  label: "GraphQLClientBase\n(核心功能)"
-  shape: rectangle
-}
-
-GraphQLClient: {
-  label: "GraphQLClient\n(完整用戶端 + 輔助工具)"
-  shape: rectangle
-}
-
-GraphqlClientLite: {
-  label: "GraphqlClientLite\n(瀏覽器最佳化)"
-  shape: rectangle
-}
-
-NativeGraphqlClient: {
-  label: "NativeGraphqlClient\n(Node.js 最佳化)"
-  shape: rectangle
-}
-
-GraphQLClientBase -> GraphQLClient: "擴充"
-GraphQLClientBase -> GraphqlClientLite: "擴充"
-GraphQLClient -> NativeGraphqlClient: "擴充"
-```
+<!-- DIAGRAM_IMAGE_START:architecture:4:3 -->
+![Client Architecture](assets/diagram/core-concepts-client-architecture-01.jpg)
+<!-- DIAGRAM_IMAGE_END -->
 
 ## 用戶端實作
 

package/docs/core-concepts-client-architecture.zh.md

@@ -8,33 +8,9 @@ OCAP 客户端采用模块化架构设计，以满足不同 JavaScript 环境和
 
 下图说明了不同客户端实现之间的关系：
 
-```d2
-direction: down
-
-GraphQLClientBase: {
-  label: "GraphQLClientBase\n（核心功能）"
-  shape: rectangle
-}
-
-GraphQLClient: {
-  label: "GraphQLClient\n（完整客户端 + 辅助方法）"
-  shape: rectangle
-}
-
-GraphqlClientLite: {
-  label: "GraphqlClientLite\n（浏览器优化）"
-  shape: rectangle
-}
-
-NativeGraphqlClient: {
-  label: "NativeGraphqlClient\n（Node.js 优化）"
-  shape: rectangle
-}
-
-GraphQLClientBase -> GraphQLClient: "扩展"
-GraphQLClientBase -> GraphqlClientLite: "扩展"
-GraphQLClient -> NativeGraphqlClient: "扩展"
-```
+<!-- DIAGRAM_IMAGE_START:architecture:4:3 -->
+![Client Architecture](assets/diagram/core-concepts-client-architecture-01.jpg)
+<!-- DIAGRAM_IMAGE_END -->
 
 ## 客户端实现
 

package/docs/core-concepts-gas-payment.ja.md

@@ -22,36 +22,9 @@
 
 以下の図は、トランザクションの開始から実行までのガス代行支払いの全フローを示しています：
 
-```d2 ガス代行支払いのワークフロー icon=mdi:gas-station
-direction: down
-
-User-App: {
-  label: "ユーザーのアプリケーション"
-  shape: rectangle
-}
-
-Gas-Payer-Wallet: {
-  label: "ガス支払い者ウォレット\n（アプリバックエンドのウォレット）"
-  shape: cylinder
-}
-
-OCAP-Client: {
-  label: "OCAPクライアントインスタンス"
-}
-
-Blockchain-Node: {
-  label: "ブロックチェーンノード"
-  shape: rectangle
-}
-
-User-App -> OCAP-Client: "1. ユーザーがトランザクションを開始"
-OCAP-Client -> OCAP-Client: "2. ユーザーのウォレットで\nTxを準備・署名"
-Gas-Payer-Wallet -> OCAP-Client: "3. ガス代行支払いのためTxハッシュに署名"
-OCAP-Client -> Blockchain-Node: "4. Tx + ガス支払い者ヘッダーを送信"
-Blockchain-Node -> Blockchain-Node: "5. 両方の署名を検証"
-Blockchain-Node: "6. トランザクションを実行"
-Blockchain-Node -> Gas-Payer-Wallet: "7. ガス料金を差し引く"
-```
+<!-- DIAGRAM_IMAGE_START:sequence:4:3 -->
+![Gas Payment](assets/diagram/core-concepts-gas-payment-01.jpg)
+<!-- DIAGRAM_IMAGE_END -->
 
 ## 使用例
 

package/docs/core-concepts-gas-payment.md

@@ -22,36 +22,9 @@ If both signatures are valid, the transaction is executed under the user's autho
 
 The following diagram illustrates the entire gas payment flow from transaction initiation to execution:
 
-```d2 The Gas Payment Workflow icon=mdi:gas-station
-direction: down
-
-User-App: {
-  label: "User's Application"
-  shape: rectangle
-}
-
-Gas-Payer-Wallet: {
-  label: "Gas Payer Wallet\n(App Backend's Wallet)"
-  shape: cylinder
-}
-
-OCAP-Client: {
-  label: "OCAP Client Instance"
-}
-
-Blockchain-Node: {
-  label: "Blockchain Node"
-  shape: rectangle
-}
-
-User-App -> OCAP-Client: "1. User initiates transaction"
-OCAP-Client -> OCAP-Client: "2. Prepare & sign Tx with\nuser's wallet"
-Gas-Payer-Wallet -> OCAP-Client: "3. Sign Tx hash for gas"
-OCAP-Client -> Blockchain-Node: "4. Send Tx + Gas Payer headers"
-Blockchain-Node -> Blockchain-Node: "5. Verify both signatures"
-Blockchain-Node: "6. Execute transaction"
-Blockchain-Node -> Gas-Payer-Wallet: "7. Deduct gas fee"
-```
+<!-- DIAGRAM_IMAGE_START:sequence:4:3 -->
+![Gas Payment](assets/diagram/core-concepts-gas-payment-01.jpg)
+<!-- DIAGRAM_IMAGE_END -->
 
 ## Usage Example
 

package/docs/core-concepts-gas-payment.zh-TW.md

@@ -22,36 +22,9 @@ Gas 支付機制是透過標準的 HTTP 標頭來實現的。當您在客戶端
 
 下圖說明了從交易發起到執行的整個 Gas 支付流程：
 
-```d2 Gas 支付工作流程 icon=mdi:gas-station
-direction: down
-
-User-App: {
-  label: "使用者應用程式"
-  shape: rectangle
-}
-
-Gas-Payer-Wallet: {
-  label: "Gas 支付者錢包\n（應用程式後端錢包）"
-  shape: cylinder
-}
-
-OCAP-Client: {
-  label: "OCAP Client 實例"
-}
-
-Blockchain-Node: {
-  label: "區塊鏈節點"
-  shape: rectangle
-}
-
-User-App -> OCAP-Client: "1. 使用者發起交易"
-OCAP-Client -> OCAP-Client: "2. 使用使用者錢包準備並簽署交易"
-Gas-Payer-Wallet -> OCAP-Client: "3. 簽署交易雜湊值以支付 Gas"
-OCAP-Client -> Blockchain-Node: "4. 發送交易 + Gas 支付者標頭"
-Blockchain-Node -> Blockchain-Node: "5. 驗證雙方簽名"
-Blockchain-Node: "6. 執行交易"
-Blockchain-Node -> Gas-Payer-Wallet: "7. 扣除 Gas 費用"
-```
+<!-- DIAGRAM_IMAGE_START:sequence:4:3 -->
+![Gas Payment](assets/diagram/core-concepts-gas-payment-01.jpg)
+<!-- DIAGRAM_IMAGE_END -->
 
 ## 使用範例
 

package/docs/core-concepts-gas-payment.zh.md

@@ -22,36 +22,9 @@ Gas 费支付机制通过标准的 HTTP 标头实现。当您在客户端实例
 
 下图说明了从交易发起 Gas 费支付到执行的完整流程：
 
-```d2 Gas 费支付工作流程 icon=mdi:gas-station
-direction: down
-
-User-App: {
-  label: "用户应用"
-  shape: rectangle
-}
-
-Gas-Payer-Wallet: {
-  label: "Gas 费支付方钱包\n（应用后端钱包）"
-  shape: cylinder
-}
-
-OCAP-Client: {
-  label: "OCAP 客户端实例"
-}
-
-Blockchain-Node: {
-  label: "区块链节点"
-  shape: rectangle
-}
-
-User-App -> OCAP-Client: "1. 用户发起交易"
-OCAP-Client -> OCAP-Client: "2. 使用用户钱包\n准备并签署交易"
-Gas-Payer-Wallet -> OCAP-Client: "3. 为 Gas 费签署交易哈希"
-OCAP-Client -> Blockchain-Node: "4. 发送交易及 Gas 费支付方标头"
-Blockchain-Node -> Blockchain-Node: "5. 验证双方签名"
-Blockchain-Node: "6. 执行交易"
-Blockchain-Node -> Gas-Payer-Wallet: "7. 扣除 Gas 费"
-```
+<!-- DIAGRAM_IMAGE_START:sequence:4:3 -->
+![Gas Payment](assets/diagram/core-concepts-gas-payment-01.jpg)
+<!-- DIAGRAM_IMAGE_END -->
 
 ## 使用示例
 

package/docs/core-concepts-transaction-lifecycle.ja.md

@@ -10,67 +10,9 @@ OCAP Client は柔軟なメソッドセットを提供しており、最大限
 
 以下の図は、準備からブロックチェーンへの最終的な送信までのトランザクションの完全な流れを示しています。
 
-```d2 Transaction Lifecycle Diagram
-direction: down
-
-Start: {
-  label: "1. Itxの準備"
-  shape: oval
-}
-
-Encode-Tx: {
-  label: "2. トランザクションのエンコード\n(encode<Type>Tx)"
-  shape: rectangle
-}
-
-Sign-Tx: {
-  label: "3. トランザクションの署名"
-  shape: diamond
-}
-
-Single-Sign: {
-  label: "単一署名\n(sign<Type>Tx)"
-  shape: rectangle
-}
-
-Multi-Sign-Flow: {
-  label: "複数署名"
-  shape: rectangle
-  
-  Multi-Sign-1: {
-    label: "署名者1\n(multiSign<Type>Tx)"
-  }
-  
-  Multi-Sign-2: {
-    label: "署名者2\n(multiSign<Type>Tx)"
-  }
-
-  Multi-Sign-N: {
-    label: "..."
-  }
-  
-  Multi-Sign-1 -> Multi-Sign-2: "署名済みTXを渡す"
-  Multi-Sign-2 -> Multi-Sign-N: "署名済みTXを渡す"
-}
-
-Send-Tx: {
-  label: "4. トランザクションの送信\n(send<Type>Tx)"
-  shape: rectangle
-}
-
-End: {
-  label: "トランザクションハッシュ"
-  shape: oval
-}
-
-Start -> Encode-Tx
-Encode-Tx -> Sign-Tx
-Sign-Tx -> Single-Sign: "単一署名者"
-Sign-Tx -> Multi-Sign-Flow: "複数署名者"
-Single-Sign -> Send-Tx
-Multi-Sign-Flow -> Send-Tx
-Send-Tx -> End
-```
+<!-- DIAGRAM_IMAGE_START:flowchart:4:3 -->
+![Transaction Lifecycle](assets/diagram/core-concepts-transaction-lifecycle-01.jpg)
+<!-- DIAGRAM_IMAGE_END -->
 
 ## ステージ1: 準備（`itx`の作成）
 

package/docs/core-concepts-transaction-lifecycle.md

@@ -10,67 +10,9 @@ This guide breaks down each stage and illustrates both single-signature and mult
 
 The following diagram illustrates the complete journey of a transaction from preparation to its final submission to the blockchain.
 
-```d2 Transaction Lifecycle Diagram
-direction: down
-
-Start: {
-  label: "1. Prepare Itx"
-  shape: oval
-}
-
-Encode-Tx: {
-  label: "2. Encode Transaction\n(encode<Type>Tx)"
-  shape: rectangle
-}
-
-Sign-Tx: {
-  label: "3. Sign Transaction"
-  shape: diamond
-}
-
-Single-Sign: {
-  label: "Single Signature\n(sign<Type>Tx)"
-  shape: rectangle
-}
-
-Multi-Sign-Flow: {
-  label: "Multi-Signature"
-  shape: rectangle
-  
-  Multi-Sign-1: {
-    label: "Signer 1\n(multiSign<Type>Tx)"
-  }
-  
-  Multi-Sign-2: {
-    label: "Signer 2\n(multiSign<Type>Tx)"
-  }
-
-  Multi-Sign-N: {
-    label: "..."
-  }
-  
-  Multi-Sign-1 -> Multi-Sign-2: "Pass signed TX"
-  Multi-Sign-2 -> Multi-Sign-N: "Pass signed TX"
-}
-
-Send-Tx: {
-  label: "4. Send Transaction\n(send<Type>Tx)"
-  shape: rectangle
-}
-
-End: {
-  label: "Transaction Hash"
-  shape: oval
-}
-
-Start -> Encode-Tx
-Encode-Tx -> Sign-Tx
-Sign-Tx -> Single-Sign: "Single Signer"
-Sign-Tx -> Multi-Sign-Flow: "Multiple Signers"
-Single-Sign -> Send-Tx
-Multi-Sign-Flow -> Send-Tx
-Send-Tx -> End
-```
+<!-- DIAGRAM_IMAGE_START:flowchart:4:3 -->
+![Transaction Lifecycle](assets/diagram/core-concepts-transaction-lifecycle-01.jpg)
+<!-- DIAGRAM_IMAGE_END -->
 
 ## Stage 1: Preparation (Creating the `itx`)
 

package/docs/core-concepts-transaction-lifecycle.zh-TW.md

@@ -10,67 +10,9 @@ OCAP 用戶端提供了一套彈性的方法，讓您可以為了最大程度的
 
 下圖說明了一筆交易從準備到最終提交至區塊鏈的完整過程。
 
-```d2 交易生命週期圖
-direction: down
-
-Start: {
-  label: "1. 準備 Itx"
-  shape: oval
-}
-
-Encode-Tx: {
-  label: "2. 編碼交易\n(encode<Type>Tx)"
-  shape: rectangle
-}
-
-Sign-Tx: {
-  label: "3. 簽署交易"
-  shape: diamond
-}
-
-Single-Sign: {
-  label: "單一簽章\n(sign<Type>Tx)"
-  shape: rectangle
-}
-
-Multi-Sign-Flow: {
-  label: "多重簽章"
-  shape: rectangle
-  
-  Multi-Sign-1: {
-    label: "簽署人 1\n(multiSign<Type>Tx)"
-  }
-  
-  Multi-Sign-2: {
-    label: "簽署人 2\n(multiSign<Type>Tx)"
-  }
-
-  Multi-Sign-N: {
-    label: "..."
-  }
-  
-  Multi-Sign-1 -> Multi-Sign-2: "傳遞已簽署的 TX"
-  Multi-Sign-2 -> Multi-Sign-N: "傳遞已簽署的 TX"
-}
-
-Send-Tx: {
-  label: "4. 發送交易\n(send<Type>Tx)"
-  shape: rectangle
-}
-
-End: {
-  label: "交易雜湊值"
-  shape: oval
-}
-
-Start -> Encode-Tx
-Encode-Tx -> Sign-Tx
-Sign-Tx -> Single-Sign: "單一簽署人"
-Sign-Tx -> Multi-Sign-Flow: "多個簽署人"
-Single-Sign -> Send-Tx
-Multi-Sign-Flow -> Send-Tx
-Send-Tx -> End
-```
+<!-- DIAGRAM_IMAGE_START:flowchart:4:3 -->
+![Transaction Lifecycle](assets/diagram/core-concepts-transaction-lifecycle-01.jpg)
+<!-- DIAGRAM_IMAGE_END -->
 
 ## 階段 1：準備 (創建 `itx`)
 

package/docs/core-concepts-transaction-lifecycle.zh.md

@@ -10,67 +10,9 @@ OCAP 客户端提供了一套灵活的方法，允许您单独执行这些步骤
 
 下图展示了一笔交易从准备到最终提交至区块链的完整过程。
 
-```d2 交易生命周期图
-direction: down
-
-Start: {
-  label: "1. 准备 Itx"
-  shape: oval
-}
-
-Encode-Tx: {
-  label: "2. 编码交易\n(encode<Type>Tx)"
-  shape: rectangle
-}
-
-Sign-Tx: {
-  label: "3. 交易签名"
-  shape: diamond
-}
-
-Single-Sign: {
-  label: "单签名\n(sign<Type>Tx)"
-  shape: rectangle
-}
-
-Multi-Sign-Flow: {
-  label: "多签名"
-  shape: rectangle
-  
-  Multi-Sign-1: {
-    label: "签名者 1\n(multiSign<Type>Tx)"
-  }
-  
-  Multi-Sign-2: {
-    label: "签名者 2\n(multiSign<Type>Tx)"
-  }
-
-  Multi-Sign-N: {
-    label: "..."
-  }
-  
-  Multi-Sign-1 -> Multi-Sign-2: "传递已签名的交易"
-  Multi-Sign-2 -> Multi-Sign-N: "传递已签名的交易"
-}
-
-Send-Tx: {
-  label: "4. 发送交易\n(send<Type>Tx)"
-  shape: rectangle
-}
-
-End: {
-  label: "交易哈希"
-  shape: oval
-}
-
-Start -> Encode-Tx
-Encode-Tx -> Sign-Tx
-Sign-Tx -> Single-Sign: "单个签名者"
-Sign-Tx -> Multi-Sign-Flow: "多个签名者"
-Single-Sign -> Send-Tx
-Multi-Sign-Flow -> Send-Tx
-Send-Tx -> End
-```
+<!-- DIAGRAM_IMAGE_START:flowchart:4:3 -->
+![Transaction Lifecycle](assets/diagram/core-concepts-transaction-lifecycle-01.jpg)
+<!-- DIAGRAM_IMAGE_END -->
 
 ## 阶段 1：准备（创建 `itx`）
 

package/docs/overview.ja.md

@@ -4,29 +4,9 @@ OCAP Clientは、アプリケーションをOCAPベースのブロックチェ
 
 その中核となるのは、トランザクションのエンコーディングや署名の複雑さを抽象化することで、ブロックチェーンとの対話を簡素化することです。HTTP/Sを介したブロックチェーンノードとのすべての通信にGraphQL APIを使用しており、チェーンデータのクエリやトランザクションの送信が容易になります。
 
-```d2 クライアントアーキテクチャ概要 icon=mdi:graphql
-direction: down
-
-  your-app: {
-    label: "あなたのアプリケーション\n(Node.js またはブラウザ)"
-    shape: rectangle
-  }
-
-  ocap-client: {
-    label: "@ocap/client"
-    shape: rectangle
-    style.fill: "#f0f9ff"
-  }
-
-  ocap-node: {
-    label: "OCAP ブロックチェーンノード"
-    shape: cylinder
-  }
-
-  your-app -> ocap-client: "高レベル API コール\n(例: transfer(), createAsset())"
-  ocap-client -> ocap-node: "GraphQL クエリ/ミューテーション (HTTP/S)\nイベントサブスクリプション (WebSocket)"
-
-```
+<!-- DIAGRAM_IMAGE_START:architecture:4:3 -->
+![Overview](assets/diagram/overview-01.jpg)
+<!-- DIAGRAM_IMAGE_END -->
 
 ### 主な機能