technology
SPL Token JS Brings Address Objects Into Helpers
By Roll · Chief of Staff · 19 October 2026
Developers now face a simpler path when passing address data into Solana token account tools. The Oct. 16, 2026 release changed how inputs work for several core helpers.
What changes when address data no longer needs manual conversion in Solana token helpers? The Oct. 16, 2026 release of the SPL Token JS client answered that question by letting developers pass address-bearing objects straight into associated token account helpers.
The client, published on npm as @solana-program/token and maintained by the Solana Program organization, added HasAddress input support across its account tools. A web3.js PublicKey instance can now go directly into the helper without first turning it into a base58 string.
What the release changed
Mint-to and transfer-to helpers widened their address and authority inputs to accept the same objects. The mint creation helper also took the new format for both mint and freeze authorities. Hand-written helpers now default to a custom token program address to stay consistent with the generated client.
These adjustments came from the release notes and the linked change page that tracked the pull request. The updates removed extra conversion steps that developers had handled before.
Why the shift matters now
Developers working with token accounts can reduce boilerplate code in their projects. The change keeps hand-written tools in line with generated ones, so teams using either path see matching behavior.
The release notes list the HasAddress feature as the main addition. Related helpers picked up the same object support at the same time, creating one consistent pattern across mint, transfer, and account creation flows.
What readers should check next
Pull the latest version of the client and scan the associated token account helpers in your current codebase. Replace any manual base58 conversions with direct object passes where the new inputs apply. Test mint-to and transfer calls first, since those helpers gained the widest input changes.
Review the release notes at the Solana Program token repository to see the full list of updated functions. Run your existing tests after the swap to confirm no address handling broke during the update.
Teams that maintain custom wrappers around these helpers should map the new object support into their own interfaces. That step keeps downstream code aligned without extra string handling layers.
Practical next actions
Clone the repository or bump the package in your project to pull the Oct. 16, 2026 changes. Focus on any place where PublicKey or signer objects already exist, since those now plug in without extra steps.
Document the input types in your local setup so future contributors know the helpers accept address objects directly. This small adjustment can cut repeated conversion logic across multiple files.
The update keeps the client moving toward fewer manual transformations, which helps any developer who builds on Solana token accounts on a regular basis.