A new version of the Sneed Trading Bot has been released to address trade failures affecting certain ICPSwap pairs, following reports from users who encountered repeated errors during swaps.
Version 0.9.1 fixes an issue where trades failed with the message “Unsupported method ‘transferFrom’.” The problem surfaced when swapping specific tokens, including Tendy, and persisted even after ICPSwap had resumed normal operations following earlier downtime.
Users can upgrade by visiting the management page for their Sneed Trading Bot and selecting the upgrade option. An automated notification will also appear in the Sneed Hub header when an update is available, allowing users to upgrade all eligible Sneedapp applications in one click.
The error initially appeared to suggest that Tendy was not an ICRC2 token and did not support the “transferFrom” method. However, Tendy does support ICRC2, which also includes compatibility with ICRC1. Attempts to execute the same swap via the Sneedex interface produced the same result, indicating the issue was not limited to the bot itself.
According to the development team, the root cause lay in cached token metadata held by ICPSwap. To reduce cycle consumption, ICPSwap caches ICRC metadata for supported tokens rather than querying it on every swap. Tokens may support ICRC1, ICRC2, or both, and the platform provides separate APIs for each standard. When a token supports ICRC2, the corresponding API should be used.
In this case, incorrect data had entered ICPSwap’s metadata cache, leading the system to treat Tendy as if it only supported ICRC1. As a result, when the bot called the ICRC2 API, ICPSwap returned an error stating that the token did not support the required method.
The fix implemented in version 0.9.1 changes how the bot determines which API to use. Rather than relying on the token ledger’s metadata, the bot now queries ICPSwap directly to determine how the token is classified within its cache, and selects the appropriate API on that basis. The bot also maintains its own time limited cache of ICPSwap’s metadata to remain aligned with any future updates.
The developer credited another member of the ICP community, known as let4be, for identifying the issue and helping resolve it quickly.
The team emphasised that this was not a flaw in ICPSwap’s core code, but an instance of stale or corrupted cache data, which can occur at scale. The focus, they said, has been on making the bot resilient to such conditions.
The update forms part of a broader effort to streamline software delivery through the Sneed Hub, with automatic upgrade notifications designed to keep applications current with minimal user intervention.
Dear Reader,
Ledger Life is an independent platform dedicated to covering the Internet Computer (ICP) ecosystem and beyond. We focus on real stories, builder updates, project launches, and the quiet innovations that often get missed.
We’re not backed by sponsors. We rely on readers like you.
If you find value in what we publish—whether it’s deep dives into dApps, explainers on decentralised tech, or just keeping track of what’s moving in Web3—please consider making a donation. It helps us cover costs, stay consistent, and remain truly independent.
Your support goes a long way.
🧠 ICP Principal: ins6i-d53ug-zxmgh-qvum3-r3pvl-ufcvu-bdyon-ovzdy-d26k3-lgq2v-3qe
🧾 ICP Address: f8deb966878f8b83204b251d5d799e0345ea72b8e62e8cf9da8d8830e1b3b05f
Every contribution helps keep the lights on, the stories flowing, and the crypto clutter out.
Thank you for reading, sharing, and being part of this experiment in decentralised media.
—Team Ledger Life
Community Discussion