viz-js-lib 0.12.3 → 0.12.4

package/.qoder/repowiki/en/content/API Reference/Configuration Options.md

@@ -11,11 +11,21 @@
 - [api/transports/ws.js](file://src/api/transports/ws.js)
 - [api/transports/http.js](file://src/api/transports/http.js)
 - [broadcast/index.js](file://src/broadcast/index.js)
+- [broadcast/helpers.js](file://src/broadcast/helpers.js)
+- [broadcast/operations.js](file://src/broadcast/operations.js)
 - [package.json](file://package.json)
 - [examples/index.html](file://examples/index.html)
 - [examples/server.js](file://examples/server.js)
+- [examples/broadcast.html](file://examples/broadcast.html)
 </cite>
 
+## Update Summary
+**Changes Made**
+- Added documentation for new configuration options: `reference_irreversible_block` and `tx_expiration_seconds`
+- Updated Configuration Reference section with comprehensive details about the new options
+- Enhanced Broadcast Configuration section to explain the impact of these new options
+- Updated Troubleshooting Guide to include guidance for the new configuration options
+
 ## Table of Contents
 1. [Introduction](#introduction)
 2. [Project Structure](#project-structure)
@@ -32,7 +42,7 @@
 This document explains the configuration system of the VIZ JavaScript library. It covers all configurable parameters, default values, and how they are resolved and applied across transports and broadcasting. It also documents environment-specific behavior (browser vs Node.js), security-related settings, and provides practical guidance for programmatic configuration changes, validation, and performance tuning.
 
 ## Project Structure
-The configuration system centers around a small, shared configuration module that exposes getter/setter functions. Defaults are loaded from a JSON file and can be overridden at runtime. The API module reads the configured endpoint to select a transport (WebSocket or HTTP), while the broadcaster consults a boolean flag to choose the appropriate broadcast method.
+The configuration system centers around a small, shared configuration module that exposes getter/setter functions. Defaults are loaded from a JSON file and can be overridden at runtime. The API module reads the configured endpoint to select a transport (WebSocket or HTTP), while the broadcaster consults configuration flags to choose the appropriate broadcast method and transaction preparation strategy.
 
 ```mermaid
 graph TB
@@ -44,55 +54,57 @@ api["api/index.js<br/>VIZ class"] --> cfg
 api --> tr_ws["transports/ws.js"]
 api --> tr_http["transports/http.js"]
 bcast["broadcast/index.js<br/>Broadcast logic"] --> cfg
-ex_b["examples/index.html<br/>Browser usage"] --> br
+ex_b["examples/broadcast.html<br/>Broadcast usage"] --> bcast
 ex_s["examples/server.js<br/>Node usage"] --> idx
 ```
 
 **Diagram sources**
-- [config.js](file://src/config.js#L1-L10)
-- [config.json](file://config.json#L1-L7)
-- [index.js](file://src/index.js#L1-L20)
-- [browser.js](file://src/browser.js#L1-L30)
-- [package.json](file://package.json#L15-L18)
-- [api/index.js](file://src/api/index.js#L1-L271)
-- [api/transports/ws.js](file://src/api/transports/ws.js#L1-L136)
-- [api/transports/http.js](file://src/api/transports/http.js#L1-L53)
-- [broadcast/index.js](file://src/broadcast/index.js#L1-L137)
-- [examples/index.html](file://examples/index.html#L1-L23)
-- [examples/server.js](file://examples/server.js#L1-L34)
+- [config.js:1-10](file://src/config.js#L1-L10)
+- [config.json:1-9](file://config.json#L1-L9)
+- [index.js:1-20](file://src/index.js#L1-L20)
+- [browser.js:1-30](file://src/browser.js#L1-L30)
+- [package.json:15-18](file://package.json#L15-L18)
+- [api/index.js:1-271](file://src/api/index.js#L1-L271)
+- [api/transports/ws.js:1-136](file://src/api/transports/ws.js#L1-L136)
+- [api/transports/http.js:1-53](file://src/api/transports/http.js#L1-L53)
+- [broadcast/index.js:1-146](file://src/broadcast/index.js#L1-L146)
+- [examples/broadcast.html:1-108](file://examples/broadcast.html#L1-L108)
+- [examples/server.js:1-34](file://examples/server.js#L1-L34)
 
 **Section sources**
-- [config.js](file://src/config.js#L1-L10)
-- [config.json](file://config.json#L1-L7)
-- [index.js](file://src/index.js#L1-L20)
-- [browser.js](file://src/browser.js#L1-L30)
-- [package.json](file://package.json#L15-L18)
-- [examples/index.html](file://examples/index.html#L1-L23)
-- [examples/server.js](file://examples/server.js#L1-L34)
+- [config.js:1-10](file://src/config.js#L1-L10)
+- [config.json:1-9](file://config.json#L1-L9)
+- [index.js:1-20](file://src/index.js#L1-L20)
+- [browser.js:1-30](file://src/browser.js#L1-L30)
+- [package.json:15-18](file://package.json#L15-L18)
+- [examples/broadcast.html:1-108](file://examples/broadcast.html#L1-L108)
+- [examples/server.js:1-34](file://examples/server.js#L1-L34)
 
 ## Core Components
 - Configuration module: Provides a simple key-value store with get and set functions backed by defaults loaded from config.json.
-- Defaults: Address prefix, chain ID, and broadcast behavior are defined centrally.
+- Defaults: Address prefix, chain ID, broadcast behavior, transaction expiration, and irreversible block reference are defined centrally.
 - API module: Reads the configured endpoint to dynamically select a transport (WebSocket or HTTP) and manages lifecycle.
 - Transports: WebSocket transport uses the configured endpoint; HTTP transport uses the same endpoint for JSON-RPC calls.
-- Broadcast module: Uses a boolean flag to choose synchronous or callback-based broadcast.
+- Broadcast module: Uses configuration flags to choose synchronous or callback-based broadcast and to control transaction preparation strategy.
 
 Key configuration parameters:
 - websocket: Endpoint URL for the node (WebSocket or HTTP). Used by both transports.
 - address_prefix: Chain identifier prefix used in address encoding.
 - chain_id: Unique chain identifier for signing and verification.
 - broadcast_transaction_with_callback: Boolean switch controlling broadcast method selection.
+- reference_irreversible_block: Boolean flag controlling whether to reference irreversible blocks for transaction validity.
+- tx_expiration_seconds: Number of seconds after which transactions expire.
 
 **Section sources**
-- [config.js](file://src/config.js#L1-L10)
-- [config.json](file://config.json#L1-L7)
-- [api/index.js](file://src/api/index.js#L34-L62)
-- [api/transports/ws.js](file://src/api/transports/ws.js#L34-L48)
-- [api/transports/http.js](file://src/api/transports/http.js#L48-L51)
-- [broadcast/index.js](file://src/broadcast/index.js#L41-L43)
+- [config.js:1-10](file://src/config.js#L1-L10)
+- [config.json:1-9](file://config.json#L1-L9)
+- [api/index.js:34-62](file://src/api/index.js#L34-L62)
+- [api/transports/ws.js:34-48](file://src/api/transports/ws.js#L34-L48)
+- [api/transports/http.js:48-51](file://src/api/transports/http.js#L48-L51)
+- [broadcast/index.js:41-43](file://src/broadcast/index.js#L41-L43)
 
 ## Architecture Overview
-The configuration system is intentionally minimal and centralized. Defaults are loaded once and can be overridden at runtime. The API module inspects the configured endpoint to determine the transport type and delegates all communication to the selected transport. Broadcasting logic reads a boolean flag to decide which broadcast method to use.
+The configuration system is intentionally minimal and centralized. Defaults are loaded once and can be overridden at runtime. The API module inspects the configured endpoint to determine the transport type and delegates all communication to the selected transport. Broadcasting logic reads configuration flags to decide which broadcast method to use and how to prepare transactions.
 
 ```mermaid
 sequenceDiagram
@@ -119,9 +131,9 @@ end
 ```
 
 **Diagram sources**
-- [api/index.js](file://src/api/index.js#L34-L62)
-- [api/transports/ws.js](file://src/api/transports/ws.js#L34-L48)
-- [api/transports/http.js](file://src/api/transports/http.js#L48-L51)
+- [api/index.js:34-62](file://src/api/index.js#L34-L62)
+- [api/transports/ws.js:34-48](file://src/api/transports/ws.js#L34-L48)
+- [api/transports/http.js:48-51](file://src/api/transports/http.js#L48-L51)
 
 ## Detailed Component Analysis
 
@@ -139,12 +151,12 @@ Get --> Return["Return stored value"]
 ```
 
 **Diagram sources**
-- [config.js](file://src/config.js#L3-L9)
-- [config.json](file://config.json#L1-L7)
+- [config.js:3-9](file://src/config.js#L3-L9)
+- [config.json:1-9](file://config.json#L1-L9)
 
 **Section sources**
-- [config.js](file://src/config.js#L1-L10)
-- [config.json](file://config.json#L1-L7)
+- [config.js:1-10](file://src/config.js#L1-L10)
+- [config.json:1-9](file://config.json#L1-L9)
 
 ### Defaults and Environment
 - Defaults are defined in config.json and consumed by the configuration module.
@@ -155,9 +167,9 @@ Environment-specific notes:
 - The WebSocket transport selects the appropriate WebSocket class depending on the environment (Node vs browser).
 
 **Section sources**
-- [config.json](file://config.json#L1-L7)
-- [package.json](file://package.json#L15-L18)
-- [api/transports/ws.js](file://src/api/transports/ws.js#L8-L14)
+- [config.json:1-9](file://config.json#L1-L9)
+- [package.json:15-18](file://package.json#L15-L18)
+- [api/transports/ws.js:8-14](file://src/api/transports/ws.js#L8-L14)
 
 ### API Transport Selection
 - The API module determines the transport based on the configured endpoint:
@@ -176,13 +188,13 @@ D --> |No| F["Throw error: unknown transport"]
 ```
 
 **Diagram sources**
-- [api/index.js](file://src/api/index.js#L34-L42)
-- [api/transports/ws.js](file://src/api/transports/ws.js#L34-L48)
-- [api/transports/http.js](file://src/api/transports/http.js#L48-L51)
+- [api/index.js:34-42](file://src/api/index.js#L34-L42)
+- [api/transports/ws.js:34-48](file://src/api/transports/ws.js#L34-L48)
+- [api/transports/http.js:48-51](file://src/api/transports/http.js#L48-L51)
 
 **Section sources**
-- [api/index.js](file://src/api/index.js#L34-L62)
-- [api/transports/base.js](file://src/api/transports/base.js#L1-L34)
+- [api/index.js:34-62](file://src/api/index.js#L34-L62)
+- [api/transports/base.js:1-34](file://src/api/transports/base.js#L1-L34)
 
 ### WebSocket Transport
 - Creates a WebSocket connection using the configured endpoint.
@@ -206,10 +218,10 @@ WS-->>API : resolve/reject
 ```
 
 **Diagram sources**
-- [api/transports/ws.js](file://src/api/transports/ws.js#L27-L94)
+- [api/transports/ws.js:27-94](file://src/api/transports/ws.js#L27-L94)
 
 **Section sources**
-- [api/transports/ws.js](file://src/api/transports/ws.js#L1-L136)
+- [api/transports/ws.js:1-136](file://src/api/transports/ws.js#L1-L136)
 
 ### HTTP Transport
 - Issues JSON-RPC POST requests against the configured endpoint.
@@ -229,29 +241,37 @@ HTTP-->>API : resolve/reject
 ```
 
 **Diagram sources**
-- [api/transports/http.js](file://src/api/transports/http.js#L43-L52)
+- [api/transports/http.js:43-52](file://src/api/transports/http.js#L43-L52)
 
 **Section sources**
-- [api/transports/http.js](file://src/api/transports/http.js#L1-L53)
+- [api/transports/http.js:1-53](file://src/api/transports/http.js#L1-L53)
 
 ### Broadcast Configuration
 - The broadcaster conditionally chooses between two broadcast methods based on a boolean flag.
 - The flag is read from configuration, enabling or disabling callback-based broadcasting.
+- Transaction preparation uses configuration values to set expiration and reference blocks.
+
+**Updated** Enhanced to include new configuration options for transaction preparation
 
 ```mermaid
 flowchart TD
 Start(["Broadcast request"]) --> Check["Read flag from config"]
 Check --> |true| CB["Use broadcast with callback"]
 Check --> |false| Sync["Use synchronous broadcast"]
-CB --> Done(["Return signed transaction"])
-Sync --> Done
+CB --> Prep["Prepare transaction with config"]
+Sync --> Prep
+Prep --> Exp["Set expiration from tx_expiration_seconds"]
+Prep --> Ref["Set reference block from reference_irreversible_block"]
+Exp --> Done(["Return signed transaction"])
+Ref --> Done
 ```
 
 **Diagram sources**
-- [broadcast/index.js](file://src/broadcast/index.js#L41-L43)
+- [broadcast/index.js:41-43](file://src/broadcast/index.js#L41-L43)
+- [broadcast/index.js:49-93](file://src/broadcast/index.js#L49-L93)
 
 **Section sources**
-- [broadcast/index.js](file://src/broadcast/index.js#L1-L137)
+- [broadcast/index.js:1-146](file://src/broadcast/index.js#L1-L146)
 
 ### Programmatic Configuration Changes
 - To change the endpoint, use the configuration setter with the key for the endpoint.
@@ -264,19 +284,19 @@ Practical steps:
 - Restart after changes: stop and start the API to reinitialize the transport.
 
 **Section sources**
-- [config.js](file://src/config.js#L5-L8)
-- [api/index.js](file://src/api/index.js#L44-L62)
-- [examples/index.html](file://examples/index.html#L10-L20)
-- [examples/server.js](file://examples/server.js#L1-L34)
+- [config.js:5-8](file://src/config.js#L5-L8)
+- [api/index.js:44-62](file://src/api/index.js#L44-L62)
+- [examples/broadcast.html:1-108](file://examples/broadcast.html#L1-L108)
+- [examples/server.js:1-34](file://examples/server.js#L1-L34)
 
 ### Security-Related Settings
 - address_prefix and chain_id are part of the default configuration and are used during signing and verification routines elsewhere in the library. They ensure signatures are bound to the correct chain and address format.
 - The endpoint configuration itself does not include TLS settings; however, secure variants (wss, https) should be used to protect communications.
 
 **Section sources**
-- [config.json](file://config.json#L3-L4)
-- [api/transports/ws.js](file://src/api/transports/ws.js#L34-L48)
-- [api/transports/http.js](file://src/api/transports/http.js#L19-L27)
+- [config.json:3-4](file://config.json#L3-L4)
+- [api/transports/ws.js:34-48](file://src/api/transports/ws.js#L34-L48)
+- [api/transports/http.js:19-27](file://src/api/transports/http.js#L19-L27)
 
 ### Environment-Specific Behavior (Browser vs Node.js)
 - The browser build disables certain Node-specific modules via the browser field in package.json.
@@ -284,12 +304,12 @@ Practical steps:
 - The HTTP transport relies on cross-fetch, which is designed to work in both environments.
 
 **Section sources**
-- [package.json](file://package.json#L15-L18)
-- [api/transports/ws.js](file://src/api/transports/ws.js#L8-L14)
-- [api/transports/http.js](file://src/api/transports/http.js#L1-L2)
+- [package.json:15-18](file://package.json#L15-L18)
+- [api/transports/ws.js:8-14](file://src/api/transports/ws.js#L8-L14)
+- [api/transports/http.js:1-2](file://src/api/transports/http.js#L1-L2)
 
 ## Dependency Analysis
-The configuration module is a thin layer that underpins the API and broadcast modules. The API module depends on configuration for transport selection and lifecycle management. The transport modules depend on configuration for the endpoint. The broadcast module depends on configuration for the broadcast method.
+The configuration module is a thin layer that underpins the API and broadcast modules. The API module depends on configuration for transport selection and lifecycle management. The transport modules depend on configuration for the endpoint. The broadcast module depends on configuration for the broadcast method and transaction preparation.
 
 ```mermaid
 graph LR
@@ -298,21 +318,27 @@ Config --> Bcast["broadcast/index.js"]
 API --> T_WS["transports/ws.js"]
 API --> T_HTTP["transports/http.js"]
 API --> T_Base["transports/base.js"]
+Bcast --> Helpers["broadcast/helpers.js"]
+Bcast --> Ops["broadcast/operations.js"]
 ```
 
 **Diagram sources**
-- [config.js](file://src/config.js#L1-L10)
-- [api/index.js](file://src/api/index.js#L1-L271)
-- [broadcast/index.js](file://src/broadcast/index.js#L1-L137)
-- [api/transports/base.js](file://src/api/transports/base.js#L1-L34)
-- [api/transports/ws.js](file://src/api/transports/ws.js#L1-L136)
-- [api/transports/http.js](file://src/api/transports/http.js#L1-L53)
+- [config.js:1-10](file://src/config.js#L1-L10)
+- [api/index.js:1-271](file://src/api/index.js#L1-L271)
+- [broadcast/index.js:1-146](file://src/broadcast/index.js#L1-L146)
+- [broadcast/helpers.js:1-82](file://src/broadcast/helpers.js#L1-L82)
+- [broadcast/operations.js:1-475](file://src/broadcast/operations.js#L1-L475)
+- [api/transports/base.js:1-34](file://src/api/transports/base.js#L1-L34)
+- [api/transports/ws.js:1-136](file://src/api/transports/ws.js#L1-L136)
+- [api/transports/http.js:1-53](file://src/api/transports/http.js#L1-L53)
 
 **Section sources**
-- [config.js](file://src/config.js#L1-L10)
-- [api/index.js](file://src/api/index.js#L1-L271)
-- [broadcast/index.js](file://src/broadcast/index.js#L1-L137)
-- [api/transports/base.js](file://src/api/transports/base.js#L1-L34)
+- [config.js:1-10](file://src/config.js#L1-L10)
+- [api/index.js:1-271](file://src/api/index.js#L1-L271)
+- [broadcast/index.js:1-146](file://src/broadcast/index.js#L1-L146)
+- [broadcast/helpers.js:1-82](file://src/broadcast/helpers.js#L1-L82)
+- [broadcast/operations.js:1-475](file://src/broadcast/operations.js#L1-L475)
+- [api/transports/base.js:1-34](file://src/api/transports/base.js#L1-L34)
 
 ## Performance Considerations
 - Transport selection: Using WebSocket (wss) can reduce overhead compared to repeated HTTP requests, especially for streaming or frequent polling scenarios.
@@ -320,8 +346,8 @@ API --> T_Base["transports/base.js"]
 - Request batching: Where applicable, batch operations to reduce round trips.
 - Logging and debugging: The API emits performance tracking events; enable only when needed to avoid overhead.
 - Browser vs Node: In browsers, ensure the WebSocket class is available; in Node, ensure the ws dependency is present.
-
-[No sources needed since this section provides general guidance]
+- Transaction expiration: Adjust tx_expiration_seconds based on network conditions and expected confirmation times.
+- Irreversible block reference: Enable reference_irreversible_block for higher transaction safety at the cost of slower confirmation times.
 
 ## Troubleshooting Guide
 Common configuration issues and resolutions:
@@ -329,22 +355,23 @@ Common configuration issues and resolutions:
 - Connection failures: Verify the endpoint is reachable and uses secure variants (wss/https) when required by policy.
 - Incorrect broadcast behavior: Confirm the broadcast flag is set appropriately for your needs.
 - Environment mismatch: In browsers, confirm that Node-specific modules are disabled and that the WebSocket class is available.
+- Transaction expiration errors: Adjust tx_expiration_seconds based on network conditions and expected confirmation times.
+- Irreversible block reference issues: Disable reference_irreversible_block if the node doesn't support irreversible block references.
 
 Operational checks:
 - Validate endpoint format before setting it.
 - Restart the API after changing the endpoint to ensure the new transport is initialized.
 - Monitor transport logs and performance events to diagnose issues.
+- Test transaction broadcasting with different configuration combinations to verify behavior.
 
 **Section sources**
-- [api/index.js](file://src/api/index.js#L34-L42)
-- [api/transports/ws.js](file://src/api/transports/ws.js#L34-L48)
-- [api/transports/http.js](file://src/api/transports/http.js#L48-L51)
-- [broadcast/index.js](file://src/broadcast/index.js#L41-L43)
+- [api/index.js:34-42](file://src/api/index.js#L34-L42)
+- [api/transports/ws.js:34-48](file://src/api/transports/ws.js#L34-L48)
+- [api/transports/http.js:48-51](file://src/api/transports/http.js#L48-L51)
+- [broadcast/index.js:41-43](file://src/broadcast/index.js#L41-L43)
 
 ## Conclusion
-The VIZ JavaScript library’s configuration system is intentionally simple and centralized. Defaults are loaded from a JSON file and can be overridden at runtime. The API module uses the configured endpoint to select the appropriate transport, while the broadcast module uses a boolean flag to choose the broadcast method. Understanding these mechanisms enables safe and efficient configuration across environments and deployment scenarios.
-
-[No sources needed since this section summarizes without analyzing specific files]
+The VIZ JavaScript library's configuration system is intentionally simple and centralized. Defaults are loaded from a JSON file and can be overridden at runtime. The API module uses the configured endpoint to select the appropriate transport, while the broadcast module uses configuration flags to choose the broadcast method and control transaction preparation. Understanding these mechanisms enables safe and efficient configuration across environments and deployment scenarios.
 
 ## Appendices
 
@@ -353,15 +380,31 @@ The VIZ JavaScript library’s configuration system is intentionally simple and
 - address_prefix: Chain identifier prefix used in address encoding.
 - chain_id: Unique chain identifier for signing and verification.
 - broadcast_transaction_with_callback: Boolean flag controlling broadcast method selection.
+- reference_irreversible_block: **New** Boolean flag controlling whether to reference irreversible blocks for transaction validity. When true, transactions reference the last irreversible block; when false, they reference the head block.
+- tx_expiration_seconds: **New** Number of seconds after which transactions expire. Controls how long transactions remain valid for submission to the network.
+
+**Updated** Added documentation for new configuration options
 
 **Section sources**
-- [config.json](file://config.json#L1-L7)
-- [broadcast/index.js](file://src/broadcast/index.js#L41-L43)
+- [config.json:1-9](file://config.json#L1-L9)
+- [broadcast/index.js:49-93](file://src/broadcast/index.js#L49-L93)
 
 ### Example Usage Patterns
 - Browser usage: Initialize the library and call API methods after configuring the endpoint.
 - Node.js usage: Require the library and call API methods after configuring the endpoint.
+- Transaction configuration: Set reference_irreversible_block to true for higher safety or false for faster confirmation times.
+- Expiration configuration: Adjust tx_expiration_seconds based on network conditions and expected confirmation targets.
+
+**Section sources**
+- [examples/broadcast.html:1-108](file://examples/broadcast.html#L1-L108)
+- [examples/server.js:1-34](file://examples/server.js#L1-L34)
+
+### Best Practices for Configuration
+- Production environments: Set reference_irreversible_block to true for maximum transaction safety, adjust tx_expiration_seconds based on expected confirmation times.
+- Development environments: Set reference_irreversible_block to false for faster testing cycles, use shorter tx_expiration_seconds.
+- High-frequency operations: Consider enabling reference_irreversible_block to prevent transaction reverts due to fork conflicts.
+- Network reliability: Increase tx_expiration_seconds on unreliable networks to accommodate longer confirmation times.
 
 **Section sources**
-- [examples/index.html](file://examples/index.html#L10-L20)
-- [examples/server.js](file://examples/server.js#L1-L34)
+- [broadcast/index.js:49-93](file://src/broadcast/index.js#L49-L93)
+- [config.json:6-7](file://config.json#L6-L7)