technology
SPL Token JS Accepts Address Objects For Account Helpers
By Roll · Chief of Staff · 19 Oct 2026
The Solana token client's Oct. 16, 2026 update let developers pass address-bearing objects straight into its associated token account helpers. NFA.
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 reached developers on Oct. 16, 2026. The package appears on npm under the name @solana-program/token. Solana Program maintains the repository that houses the client. The release focused on changes to helper functions that manage associated token accounts.
Direct Object Support
Associated token account helpers now accept HasAddress inputs. Developers can supply objects such as web3.js PublicKey instances without first converting them to base58 strings. This adjustment removes an intermediate step when constructing calls that reference token accounts.
Expanded Input Options
Mint-to and transfer-to helpers widened the range of accepted address and authority values. The mint creation helper adopted the same objects for its mint authority and freeze authority parameters. These shifts allow a consistent pattern across several token operations.
Program Address Default
Hand-written helpers now default to a custom token program address. The change brings their behavior into line with the generated client. Developers who rely on the hand-written path encounter fewer differences when switching between the two implementations.
Ownership And Utility
Token holders benefit when the tools that manage their accounts operate with fewer manual conversions. The update gives developers a direct route to pass signers and keys into account helpers. Utility increases because the same address-bearing objects work across mint, transfer, and creation flows. Ownership records stay intact while the code path shortens.
Developer Workflow
A developer preparing a mint-to action can hand an object that already carries the required address. No separate extraction of the address string is needed. The helper reads the address from the object and proceeds with the instruction. This pattern repeats for transfer-to calls and mint creation steps.
Alignment With Generated Code
The hand-written helpers now follow the same defaults used by the generated client. Custom program addresses serve as the starting point for both paths. Consistency reduces the chance that one helper set behaves differently from the other during routine token tasks.
The release notes document each of these adjustments. The change page details the HasAddress support and the widened inputs. Together they describe a library update that simplifies object handling for associated token accounts.