Dear Singularitarians,

SingularityNET, a Founding Member of the Artificial Superintelligence (ASI) Alliance, is pleased to announce a major update to our core platform infrastructure and documentation to support the AGIX to FET (ASI) token migration.

This represents a significant milestone that expands FET (ASI) token utility and enhances our Platform’s comprehensive suite of innovative tools and products designed to develop and utilize AI services in ways that prioritize decentralization, safety, scalability, and benefits to all.

It reflects months of coordinated development, cross-team integration, and deep collaboration across the ASI Alliance. The result is a more unified infrastructure that aligns our ecosystem under a single, powerful token standard—pushing us closer to our goal of truly decentralized, interoperable artificial intelligence.

Decentralized AI Infrastructure Updates

Our team has implemented comprehensive changes across the Platform’s architecture to support this transition:

• AI service publication: All new services are now published using the FET (ASI) token as the payment method. This standardization creates consistency across the Platform and expands FET token utility.
  
• Marketplace infrastructure: The legacy AGIX Marketplace has been deprecated as part of this transition. Services will be removed from the legacy marketplace once republished and will automatically be published in the FET (ASI) Marketplace.
  
• Contract implementation: New smart contract addresses have been deployed for both the FET (ASI) token and the Multi-Party Escrow (MPE) system. These contracts incorporate enhanced transaction handling capabilities.

This update brings tighter alignment between core platform functions and the broader ASI ecosystem. By shifting key operations to the FET (ASI) token standard, we’re enabling faster execution, simplified integration, and a more cohesive developer experience across services and marketplaces.

Developer Tooling Update

We have updated our core development tools to fully support the FET (ASI) token, with migration instructions and comprehensive version details provided in our documentation:

SDK implementation

• From SDK v4.0.0 onward, only FET (ASI) is supported
• Legacy AGIX support remains available in SDK v3.7.2

CLI enhancements

• From CLI v3.0.0 onward, only FET (ASI) is supported
• Legacy AGIX support remains available in CLI v2.4.1

The new developer tooling update is designed to optimize speed and clarity. SDK and CLI updates make it easier to publish, test, and manage services without second-guessing compatibility or token handling. Everything is designed to get out of your way so you can focus on building.

Backward Compatibility

Maintaining backward compatibility has been a top priority throughout the FET (ASI) integration. To ensure a smooth transition, services published with the AGIX token will remain accessible via the existing Marketplace, CLI, and SDK. However, we strongly recommend migrating all services to FET (ASI) to ensure ongoing compatibility and long-term support.

This careful balance ensures current users can transition at their own pace, minimizing disruptions while paving a clear pathway towards the future with FET (ASI).

Details on how to work with AGIX in legacy mode, including backward compatibility, are available in the documentation. This includes:

• How to configure the CLI to use Legacy AGIX contracts
• SDK configuration for working with AGIX services
• Instructions for withdrawing tokens from AGIX MPE
• Information about the Legacy AGIX Marketplace domains
• Guidance on interacting with legacy contract addresses

The migration process, configuration examples, contract addresses, and upgrade instructions are covered in detail in our documentation.

Acquiring FET (ASI) Tokens

As we transition to FET (ASI) token infrastructure, service users and providers need to convert their ERC-20 (Ethereum) or CNT (Cardano) AGIX tokens or acquire FET (ASI) tokens to interact with the SingularityNET Platform and other ASI Alliance ecosystem infrastructure and applications.

You can get FET (ASI) tokens to pay for AI services through various centralized and decentralized cryptocurrency exchanges. For a detailed list of supported exchanges, visit the ASI Alliance’s page on CoinMarketCap.

For development and testing purposes, our Sepolia testnet faucet provides test FET (ASI) tokens without requiring actual token acquisition, enabling developers to experiment with the Platform’s functionality.

Further Information

To support developers through this transition, we’ve created comprehensive technical resources:

• Complete migration documentation: This resource provides detailed explanations of the migration process, configuration examples for both FET (ASI) and legacy AGIX workflows, reference tables for all contract addresses, and step-by-step guides for upgrading existing services.
  
• Updated Useful Links page: This page now clearly distinguishes between FET (ASI) and deprecated AGIX marketplaces, with updated links to publisher portals, UI sandbox tools, and relevant faucets for testing environments.

We encourage all developers to review these materials and begin planning their migration to the new FET (ASI) token infrastructure.

Thank You for Being a Part of This Journey

The completion of the FET (ASI) token integration is a major leap forward for decentralized AI; and we believe it moves us forward to a future where artificial superintelligence truly benefits all. 

As we strengthen interoperability and increase utility across the ASI Alliance ecosystem, we stand firm to our commitment and dedication to openness, security, and the democratization of AI technology.

We extend our heartfelt gratitude to the vibrant SingularityNET community—developers, users, and contributors alike—for your continued support, collaboration, and commitment to our shared vision.

Together, we are not only witnessing, but actively participating in the creation of a new paradigm for decentralized AI. Stay tuned for further updates, and thank you for being a part of our collective journey.