technology
SPL Token JS Brings HasAddress Support To Account Tools
By Roll · Chief of Staff · 19 Oct 2026
The update to the Solana token client introduced support for address-bearing objects in its helpers. This change simplifies development workflows for token accounts and related operations.
The Solana token client’s Oct. 16, 2026 update let developers pass address-bearing objects straight into its associated token account helpers. NFA.
Release Overview
SPL Token JS client 0.18.0, a Solana developer library, was released on Oct. 16, 2026. The package appears on npm as @solana-program/token. Solana Program, the organization that hosts the SPL Token repository, maintains the client. The release focused on adjustments to helper functions that manage associated token accounts.
Helper Input Changes
The associated token account helpers gained support for address-bearing objects, called HasAddress inputs. Developers can now pass items such as web3.js PublicKey objects directly into these helpers. No manual base58 string conversion is required. This adjustment reduces extra steps when working with address data in token account creation flows.
Expanded Authority Handling
Mint-to and transfer-to helpers widened their address and authority inputs. The same objects now work across these operations without additional formatting. Mint creation helpers received matching updates for mint and freeze authorities. These shifts allow consistent object usage throughout the helper set.
Default Program Address
A custom token program address became the default for the hand-written helpers. The update matched the hand-written helpers to the generated client. Alignment means developers encounter fewer differences when switching between the two helper types. The change keeps behavior consistent across different parts of the library.
Developer Workflow Impact
Projects that create or move tokens can pass objects such as signers and keys without extra conversion steps. This reduces code that handles address formatting. The helpers now treat address-bearing objects the same way across mint, transfer, and account creation tasks. The result is a more uniform way to interact with token programs on Solana.
Library Consistency
The release notes highlight how the hand-written helpers now follow patterns from the generated client. Custom program addresses serve as the starting point for operations. Address and authority inputs accept the same object types in multiple helpers. These details keep the library internals aligned after the Oct. 16, 2026 changes.
Practical Use Cases
Teams building token mints can supply authority objects directly to the creation helper. Transfer operations accept the same object style for destination and signer fields. Account helpers no longer force string conversion when a PublicKey or similar item is available. The adjustments apply across the core set of token account tools released in version 0.18.0.
Summary of Adjustments
The Oct. 16, 2026 release centered on input flexibility for address-bearing objects. Mint and transfer paths received broader support for these objects. Default settings for the token program address were updated at the same time. Hand-written code now mirrors the generated client in the areas changed. These updates affect only the listed helper behaviors described in the release notes and change documentation.