Deep Dive
1. Protocol Upgrade to v2 (12 August 2026)
Overview: This was an in-place proxy upgrade on the Base network, meaning contract addresses and user funds remained unchanged. For everyday traders using the web app, nothing changed. However, it was a breaking change for developers, bots, and market makers who integrate directly with the protocol.
The upgrade moved from a model where integrations called smart contracts directly to an "API-first and intent-based" system. Key changes include using signed order intents (EIP-712) that are relayed gaslessly, dedicated API keys for trading bots that cannot withdraw funds, and HTTP-based read APIs for market data instead of complex multicall queries. New order types like coin-sized orders, "Upside" markets, and TWAP were introduced.
What this means: This is bullish for AVNT because it makes the platform much more accessible and efficient for developers and automated trading systems. It reduces friction by eliminating gas fees for users and provides a more robust, scalable infrastructure, which could attract more sophisticated users and increase protocol activity.
(Veranta SDK)
2. Rebrand from Avantis to Veranta (September 2026)
Overview: This update was primarily a name change. The project formerly known as Avantis was rebranded to Veranta. The underlying protocol, smart contracts, and API keys did not change, ensuring a seamless transition for users.
The practical impact was on software development kits (SDKs). Package names on PyPI and npm changed from avantis-trader-sdk to veranta-sdk, and environment variables were updated to use the VERANTA_* prefix. The old names continue to work for backward compatibility.
What this means: This is neutral for AVNT as it doesn't alter the token's utility or the protocol's functionality. It reflects the project's evolving ambition to serve global on-chain markets but doesn't directly affect security, speed, or costs for end-users.
(INDODAX)
Conclusion
Veranta's development trajectory is focused on professionalizing its infrastructure, as evidenced by the substantial v2 upgrade that prioritizes developer experience and scalability. The recent rebrand aligns with this broader vision. Will the improved developer tools in v2 translate into measurable growth in protocol usage and total value locked?