Key points
- Zerohash launched AUTH on October 19 for transfers between linked accounts and wallets.
- The directory lists 639 wallets and four institutional accounts; Kraken is marked Beta.
- Actual availability depends on the platform’s product, asset, network and transfer settings.
PANTHER JOURNAL #041
The transfer screen looks calmer: no pasted string, no network menu, just an account and a confirmation. Zerohash AUTH, launched on October 19, is trying to make that the normal way crypto moves between platforms.
The consequential change is not that blockchains stop using addresses. It is that users no longer have to handle those details themselves. The question shifts from “Did I copy the right destination?” to “Which account am I linking, and what am I approving?”
What Zerohash AUTH actually launched
Zerohash announced the account-linking product at Money20/20 USA in Las Vegas at 09:00 ET on October 19. Its launch announcement describes transfers involving crypto, stablecoins and tokenized securities through more than 600 connections.
CoinDesk independently reported the launch later that morning. The availability detail matters more than the big headline number.
639 wallets is not 639 exchanges
The developer network directory, checked October 20, lists 639 wallets and four institutional accounts. Coinbase, Robinhood and Gemini are marked Live; Kraken is marked Beta.
Those are different categories of connection, not hundreds of exchange integrations. More importantly, the directory expressly warns that a listing does not establish availability for every product, asset, network or platform configuration.
A reader should therefore not assume that seeing a familiar wallet name means every token in it can already move through any participating app. The useful test is the specific route: this account, this asset, this network, this direction.
The app still chooses the route
The AUTH overview describes a flow inside a participating platform: select a supported account or wallet, authenticate and grant linking permission, then review and authorize a transfer. Multi-factor authentication applies when required by the selected connection.
Its two supported product contexts also have different outcomes. Account Funding can take a crypto deposit into a fiat balance, or send crypto out from a fiat balance. Crypto Transfers keeps the platform balance in crypto. A similar-looking button need not produce the same kind of balance.
The configuration guide tells platforms to select products, transfer directions, connections, assets and networks with Zerohash, then test the enabled combinations. That is integration work, not universal access switched on by a launch announcement.
Less copying does not settle every safety question
Zerohash’s product FAQ says AUTH is secured by Connect Ltd., a Bermuda affiliate, and users must agree to Connect’s terms. It also says conventional address-based transfers can remain available when preferred or when an account is unsupported.
Panther’s assessment: hiding a manual step can reduce the opportunities to make that particular mistake. It does not, by itself, establish protection against a compromised login, a deceptive approval or a mistaken transfer. We have not independently tested AUTH’s security or measured its effect on losses.
Before using a new flow, check the authenticated account, destination, asset, amount, fees and resulting balance. Read the permissions and recovery terms rather than treating a smoother interface as a guarantee. Where a transaction is visible onchain, Panther’s public-explorer guide explains how to inspect the record independently.
The launch release also warns that offerings may be unavailable in some jurisdictions and that Zerohash accounts do not carry FDIC or SIPC protection. Those disclosures are not erased by simpler screens.
The Panther takeaway
Crypto’s next usability improvement may be a familiar account selector rather than another address format. AUTH makes that shift tangible.
But count usable routes, not logos. A linked account is a clearer interface—not unlimited availability, independently proven safety or a promise that a bad transfer can be reversed.
Sources and verification
Primary evidence: Zerohash’s dated launch release, product FAQ and developer documentation linked above. Independent confirmation: CoinDesk, October 19, 2026, 10:58 EDT. Connection statuses were checked October 20; they can change. Product claims remain attributed to Zerohash. Cover: conceptual illustration, not documentary evidence.
Responses
No responses yet. Start the conversation.
Panther Journal — The intelligence brief
Stay ahead of the story.
Free. New investigations delivered when published. Unsubscribe anytime.






