ASI Product & Development Update | Edition 18
This eighteenth edition of the biweekly ASI Alliance Product and Developm | Hanami
ASI Product & Development Update | Edition 18
This eighteenth edition of the biweekly ASI Alliance Product and Development Update covers progress from October 17 to October 28, 2026. During this period:
ASI:Chain development addressed stalled block confirmation, strengthened checks on data exchanged between nodes, and expanded bridge testing with larger transfer amounts. The updated Wallet SDK and redesigned Web Wallet completed QA.
Singularity Compute released Super Decider, an open-source decision model with strong benchmark results, available through ASI:Cloud with free inference while supply lasts.
Omega development focused on tool use, memory transfer, and startup behavior, including loading newly added skills without restarting the agent.
ASI:Chain
Node Infrastructure
Network identity checks were completed to prevent nodes holding data from an earlier network from interfering after a relaunch. These checks reject data from the wrong chain and prevent repeated connection attempts between incompatible nodes. Peer authentication was tightened to verify that a connecting node owns the identity it presents.
A fix was developed for a problem that caused the network to stop confirming blocks as the number of validators increased. Investigation identified another scaling constraint: repeated reads of block information become increasingly expensive as more validators participate. Both problems are being addressed, alongside changes that adapt block processing to the available CPU capacity and limit incoming transaction work to what a node can process.
A problem that could stall transaction execution was fixed. Parts of the node's execution system could become stuck waiting on one another, preventing affected transactions from being processed. Additional changes are being developed to validate data received from other nodes during synchronization. This includes addressing cases where an invalid response could prevent a joining node from completing synchronization.
Balance and Reward Calculations
The number-handling limit mentioned in the previous edition has been fixed. During staking tests, a reward calculation had exceeded the largest number the node could represent, interrupting reward processing and block production. The revised approach supports larger whole numbers, allowing balances and rewards to be calculated at the network's intended precision of 18 decimal places.
Support for these larger amounts was extended to the bridge, staking contracts, client library, indexer, and explorer. An updated test environment was deployed, and checks corrected problems with transfer reporting, initial token allocations, and explorer results. Further changes are being developed to make reporting of large amounts consistent across the node's interfaces.
Bridge Development
Bridge testing covered ASI:Chain and test networks for Ethereum, Base, FetchHub, and Cardano. Transfers above the previous number limit passed, with balances matching the amounts held by the bridge on both sides. Testing also verified that bridge processing could recover after a restart. These results establish that the updated bridge can carry larger amounts accurately across the tested routes; testing of the wider staking and rewards flow is continuing.
Wallet SDK and Web Wallet
The updated Wallet SDK and redesigned Web Wallet completed QA and were awaiting final product approval at the reporting cutoff.
The SDK update resolves the keyfile import problem described in the previous edition. Wallets created from the same recovery phrase but with different settings for generating accounts are distinguished correctly, preventing imported account addresses from becoming mismatched with the keys used to sign transactions. Existing stored wallets are updated automatically when opened. Invalid account entries are rejected before an import creates any accounts.
Transaction handling was refined to prevent a wallet from reopening while a submission is still in progress and restoring an incomplete view of reserved funds. Network configuration checks were extended to prevent simultaneous changes from creating duplicate entries.
Network Operations and Cost Accounting
Network operations planning covered configuration, isolation, monitoring, and recovery. Monitoring requirements include checking that blocks continue to be confirmed, alongside tracking node health and infrastructure metrics. A recovery approach is being developed to preserve chain data across container restarts, avoiding the need to download and verify the entire chain again.
Testing began on the revised cost-accounting model, which changes how the network accounts for the computational work required by transactions. Introducing it requires a coordinated network update, including changes to how transactions are formatted. Once the new model is active, transactions using the previous format will no longer be accepted.
Singularity Compute and ASI:Cloud
Super Decider
Singularity Compute released Super Decider, an open-source decision model available on GitHub and as a hosted service through ASI:Cloud. It takes information about a situation and returns an answer in a format an application can use directly, together with probabilities for the available choices. For example, an application can ask which team should handle a support request and use the model's confidence to decide whether to route it automatically or ask a person to review it.
Super Decider ranked first on JevBench with a composite score of 78.5. The benchmark measures decision quality, how well confidence matches correctness, speed, and cost.
Free inference is being offered through the ASI:Cloud API while supply lasts, allowing everyone to try the model without paying for those requests during the offer.
Learn more about Super Decider.
Omega
Development focused on tool use, memory transfer, and startup behavior. These changes are planned for the next public feature release.
Tool Use and Skills
Omega was updated to send tool definitions to its language model through the model provider's standard API fields. Previously, these definitions were included in the agent's system instructions. This gives the model a structured list of tools it can call and provides a foundation for further agent development.
The updated implementation can refresh the agent's available skills while it is running. A newly added skill can be loaded after a refresh without restarting the agent's container.
Memory Transfer and Startup
Memory transfer was reworked so you can export, list, download, and remove agent memory through a consistent process. The implementation uses Docker volumes, which store the agent's data separately from its running container, and was validated on Linux and macOS.
An optional background-indexing mode allows the agent's communication channels to become available while its knowledge directory is still being prepared for search. Users who enable it can begin interacting with the agent without waiting for that preparation to finish. The option is disabled by default.
Related improvements addressed startup reliability, simultaneous memory exports, token-limit notifications, and launcher configuration.
Experimental GPU Configuration
An experimental configuration provides a working route for users who want to try Omega with GPU access. It requires manual setup and does not yet constitute full, officially supported GPU functionality.
Benchmarking
Benchmarking continues alongside long-running tests that check whether the agent stays running and responsive over many hours of continuous conversation.
Visit the ASI Alliance website to learn more.
See you in two weeks.
The ASI Alliance Product & Development Team(Historical earnings: For fiscal 2027 Q2 (period ended 2026-07-26), NVIDIA reported basic EPS of 4.87, diluted EPS of 4.85, net income of USD 118.010 billion, and revenue of USD 177.837 billion.
Consensus expectations: For fiscal 2027 Q3 (event date 2026-11-17), consensus expects EPS of 2.49 and revenue of USD 111.356 billion.)