Proposal to deprecate asset-transfer-api and endorse ParaSpell

Tech Talk
1

I’d like to call for the deprecation of asset-transfer-api (ATA) in favor of ParaSpell. This may potentially involve deprecating asset-transfer-api-registry as well, although this is lower priority as it is low maintenance and still deserves some investigation into impact.

I have recently been maintaining ATA, which has served its purpose, but ParaSpell is simply better in my opinion and the UX improvements will serve the greater community much better. In addition to the more intuitive UX, the feature set is more complete, already supporting PAPI in addition to PJS.I have posted more details in this GitHub issue.

I am posting here to see if anyone has any objections, thoughts on this matter or concerns. Migration between tools is simple, and I can offer assistance as well.

*I am limited in the number of links I can share, but the repos are easily discoverable.

2

We have deprecated ATA as of today. No concerns were raised. The GitHub and related issues have been updated.

asset-transfer-api-registry will remain for the time being as the maintenance burden is low, but may be deprecated in favor of the ParaSpell registry (npm) if any issues are encountered in the future.

If you are not familiar with ParaSpell, please check it out. The team behind it has done an absolutely fantastic job.