ASI Product & Development Update | Edition 17 This seventeenth edition of the biweekly ASI Alliance Product and Development Update covers progress from October 3 to October 16, 2026. During this period: ASI:Chain development covered node reliability, the release of Wallet SDK 2.0.0, a redesigned Web Wallet entering QA, and further delegated staking testing. Omega received security and reliability fixes, configuration improvements and upgrades, additional capabilities for Oma, and a new skills evaluation framework. ASI:Chain Node Infrastructure Staking tests exposed a problem that prevented the test network from processing rewards and producing new blocks. A reward calculation exceeded the largest number the node could represent, causing a numeric overflow. A change to support larger numbers is under review. A fix was implemented to prevent block replay, where a node repeats a block’s computations to verify it, from interrupting receipt of new blocks. Interpreter changes are also being developed to limit memory use when a computation repeatedly calls itself. Nodes holding data from an earlier network could reconnect after a network relaunch and send old data into the new network. Network identity checks were added to reject those messages and are undergoing testing. Investigation uncovered further problems with requests between nodes and how new nodes first obtain chain data. Work to address these problems is underway. Wallet SDK Wallet SDK 2.0.0 was released on npm, making the revised wallet architecture covered in recent editions available to developers. The release supports signing sessions with configurable auto-lock, allowing users to enter their password once for a series of operations. It includes custom network configuration, wallet and account keyfile import and export, and transaction reservations that applications can manage through the SDK. Subsequent development addressed several reliability problems. Invalid auto-lock settings no longer leave signing sessions open indefinitely, and a failed wallet opening no longer leaves the SDK treating the wallet as unlocked. Number handling in node responses was corrected to prevent unusually formatted responses from freezing the SDK. Transaction reservation handling was extended so funds set aside for a transaction are released if submission fails, but remain reserved if the outcome is uncertain. Network configuration gained checks to prevent duplicate entries and conflicting updates. Keyfile import checks were tightened, though some account imports can still produce mismatches between addresses and keys, and some SDK-exported files exceed their own import limits. Work is underway to address both import problems. Web Wallet The visual redesign described in the previous edition is complete and has entered another QA round. It covers wallet creation and import, the dashboard, account management, transfers, transaction history, bridging, and network settings. The update includes changes to how the wallet behaves on smaller screens: transaction history rows can scroll horizontally, long alerts wrap within the available space, and balances adapt to their display area. Recovery phrase entry was corrected to handle pasted phrases, and copying to the clipboard was made consistent across the interface. Delegated Staking Following the state-loss fix reported in the previous edition, further delegated staking tests in the internal developer environment examined cases where delegation should be rejected and how validator withdrawals affect delegated funds. Previously, a validator’s withdrawal was rejected if other users still had stake delegated to them. The updated handling places those delegations into pending undelegation, starting the process of releasing the delegated stake instead of rejecting the validator’s withdrawal. Simultaneous delegation transactions can still conflict because they update the same staking record. Affected transactions must be recovered later, which can delay their inclusion in a block. Recovery is expected to prevent the same transaction from being applied twice. Omega Security and Reliability A command injection vulnerability was fixed in the handling of relayed text. Certain escape-token sequences or Unicode line breaks in messages, files, web pages, or scanned content could trigger unauthorized shell commands. The fix prevents those sequences from interfering with command parsing. Gateway timeouts were extended to accommodate longer model requests. Explicit timeout notifications were added so the agent reports when an upstream request takes too long, addressing cases where gateway errors had left it silent. Configuration and Upgrades The deployment launcher uses the cloud embedding provider when ASI:Cloud is selected, fixing a case where it incorrectly defaulted to local embeddings. Compatibility with existing local vector stores was preserved. Numeric settings supplied through the command line are parsed as numbers, fixing arithmetic failures caused by treating them as text. Migration bugs were fixed so upgrades automatically transfer memory from older storage layouts on initial startup. Earlier agent containers are stopped during the upgrade, and legacy authentication tokens remain supported when new secrets have not been configured. Oma Tools and Management An administrative monitoring tool was built for Oma, the Telegram agent active in the ASI Alliance community channel. Authorized users can view agent activity live and start, stop, or restart instances. It streams runtime logs for diagnostics and displays security indicators, including potential compromise, attempts to escape the bot’s operating environment, and unauthorized outbound connection attempts. Oma gained the ability to send files and attachments through a secure gateway and to recognize and decode QR codes from images. A routing fix ensures file and media downloads in the messaging integration pass through the gateway, addressing requests that had bypassed it and returned errors. Skills Evaluation and Testing A benchmark suite was created to evaluate an agent’s ability to generate, register, and apply skills. Answer recognition and multi-line response scoring were refined, while prompt handling and reconnection after restarts were improved to prevent disrupted or missed test cases. Automated testing gained checks for configuration loading and setting priority, while remote integration tests previously skipped due to a configuration issue were enabled. Visit the ASI Alliance website to learn more. See you in two weeks. The ASI Alliance Product & Development Team(Historical earnings: For fiscal 2026 Q3 (period ended 2026-05-28), Micron Technology reported basic EPS of 41.97, diluted EPS of 41.4, and net income of USD 47.268 billion. In the prior-year period (ended 2025-05-29), basic EPS was 4.79, diluted EPS was 4.75, and net income was USD 5.338 billion. For fiscal 2026 Q2 (period ended 2026-02-26), basic EPS was 16.91, diluted EPS was 16.68, and net income was USD 19.025 billion, compared with prior-year basic EPS of 3.1, diluted EPS of 3.08, and net income of USD 3.453 billion. Consensus expectations: The next upcoming consensus is for fiscal 2026 Q4, with an EPS estimate of 32.5625.)