Vaulta, formerly known as EOS, held its Node Operator Meeting on August 13, 2025. The meeting covered a lot of ground, from software updates and support changes to the future direction of the Antelope Spring development. It seems like things are moving pretty fast in the Vaulta ecosystem, with new features and changes on the horizon. The discussion also touched on how these meetings are run, which is always interesting to see how things evolve.
Key Takeaways
-
The Vaulta Node Operator Meeting on August 13, 2025, discussed recent and upcoming software releases, including Antelope Spring 2.0 Developer Preview and patch 1.2.2.
-
Antelope Spring 1.3 is planned with features like "transaction notify" and CLI improvements, while Spring 2.0 aims for early 2026 with "events" for lighter node operations.
-
Ubuntu support is changing, with Antelope Spring 2.0 dropping support for Ubuntu 20, requiring Ubuntu 22 or 24.
-
Development on Spring 2.0 is progressing, with the "events" system being a major focus to enable more efficient node types.
-
Due to lower attendance, organizers are considering changes to the frequency and format of the Node Operator meetings.
Node Op Meeting Attendance and Format Changes
Participation in the regular Node Operator meetings has seen a noticeable drop lately. Organizers are looking into ways to make these sessions more engaging and accessible. Discussions about potential changes to the meeting frequency or format will be held within the dedicated Telegram roundtable group. This approach aims to gather direct feedback from operators on how best to proceed. The goal is to find a structure that better suits the community's needs and encourages more active involvement.
Antelope Spring 2.0 Dev Preview
The Antelope Spring 2.0 Developer Preview, version 1.2, was made available today. This release is mainly for developers to test out new features and includes a fix for a rare crash that could happen during sync calls. Most node operators won't need to upgrade to this preview version, but smart contract developers are encouraged to redeploy their contracts on the Dev Preview 1 testnet. This will help them check for any compatibility issues before the main release.
Key Changes in 1.2
-
Fix for sync call crash: Addresses a specific, infrequent issue that could cause a node to crash during synchronization.
-
Developer focus: This version is primarily intended for testing and feedback from the developer community.
-
Testnet redeployment: Smart contract developers should redeploy on the testnet to ensure their applications work correctly with this preview.
Antelope Spring Upcoming Patch Release 1.2.2
The Antelope Spring 1.2.2 patch release is anticipated shortly, likely within the next week. This update is recommended for all node operators to install. It addresses a critical race condition that could halt the progress of Block Producer (BP) nodes. Additionally, the patch resolves an issue related to block MAC resets, which had been impacting block propagation across the network. These fixes are important for maintaining stable and efficient node operation.
Antelope Spring 1.3 Planned Features
Antelope Spring 1.3 is shaping up to be a pretty significant update, with a tentative release planned for about six weeks from now. One of the big things is continued support for Ubuntu, specifically adding Ubuntu 24 while keeping things compatible with Ubuntu 20 and 22. This gives folks a bit of breathing room before the bigger changes in Spring 2.0.
Transaction Notify
This release is also introducing a feature called "transaction notify." The idea here is to cut down on how much redundant network traffic is sent around. It should make things a bit more efficient.
CLI Improvements
There are also some planned improvements for the command-line interface (CLI). These updates are focused on the $A Token and Core Volta contracts. You'll see things like an option to exclude the ForkDB from block log output, which should make managing and inspecting logs a bit easier for operators.
Ubuntu Support
As mentioned, Spring 1.3 will maintain support for Ubuntu 20, 22, and will add Ubuntu 24. This is a bit of a stepping stone, as the upcoming Spring 2.0 release will eventually drop support for Ubuntu 20, making Ubuntu 22 and 24 the minimum requirements. This approach allows node operators to plan their upgrades gradually.
Ubuntu Support Roadmap
Support for older Ubuntu versions is changing. Antelope Spring 2.0 will no longer support Ubuntu 20.04 LTS. The minimum requirement will shift to Ubuntu 22.04 LTS and Ubuntu 24.04 LTS. This change is being implemented to align with current operating system standards and to take advantage of newer features available in more recent Ubuntu releases.
To help with this transition, the upcoming Antelope Spring 1.3 release will not change the minimum Ubuntu version. This provides a window for node operators to plan and execute upgrades to Ubuntu 22.04 LTS or 24.04 LTS before the full cutover with Spring 2.0.
Here's a breakdown of the planned support:
-
Antelope Spring 1.3: Continues support for Ubuntu 20.04 LTS, 22.04 LTS, and 24.04 LTS.
-
Antelope Spring 2.0: Minimum support will be Ubuntu 22.04 LTS and 24.04 LTS. Ubuntu 20.04 LTS will be dropped.
Node operators are advised to begin testing their environments on Ubuntu 22.04 LTS and 24.04 LTS to prepare for the eventual shift.
Spring 2.0 Development Progress
Development on Antelope Spring 2.0 is moving along, with the team focusing on key new features. The first developer preview, which addressed a sync call crash, came out last month. Now, the team is working on the next preview, Preview 2. This upcoming release is set to introduce the "events" feature.
The "events" feature aims to let applications send specific data in a way that can be proven, without needing a full node. Initially, the focus for this feature will be on making it easy to use through the API, rather than having all the complex cryptographic checks in place right away.
Here's a look at what's planned:
-
Preview 2 Target: The goal is to release Preview 2 sometime in September 2025. However, this date isn't set in stone because the design details are still being discussed.
-
Event System: Event logs will be kept by block producer nodes and will become part of how consensus works.
-
Light Nodes: There's a possibility of creating "light nodes" that would only store event data. This could mean they wouldn't need as much powerful hardware to run.
-
Future Possibilities: Later on, these light nodes might even be able to send transactions without having to validate everything fully. This could make it easier for applications and exchanges to get and prove data they need without needing the whole history.
Event System and Light Node Concepts for 2.0
Antelope Spring 2.0 is looking at some pretty interesting changes with its event system and the idea of light nodes. Basically, the plan is to have Block Producer (BP) nodes keep event logs, and these logs will actually be part of how consensus works. This is a pretty big deal because it opens the door for what they're calling "light nodes."
Think about it: these light nodes could potentially store just the event data. This would mean they wouldn't need as much hardware to run, making it easier for more people to participate.
Here’s a breakdown of what that could mean:
-
Reduced Hardware Needs: Light nodes could significantly lower the barrier to entry for running a node, as they wouldn't need to store the entire blockchain history.
-
Focused Data Access: Applications and exchanges might use these light nodes to get specific data they need, without having to process everything.
-
Future Transaction Propagation: Down the line, these light nodes might even be able to send transactions without needing to do a full validation of the entire chain. This could speed things up and make the network more efficient.
The initial focus for the event system is on making the API easy to use, even if it means not having all the super-strong cryptographic guarantees right away. They want to get this functionality out there and make it practical for developers.
Looking Ahead for Vaulta Node Operators
The recent Vaulta node operator meeting laid out a clear path forward, with updates on Antelope Spring releases like 1.2.2 and the upcoming 1.3. It’s good to see support for Ubuntu 24 being added in 1.3, with a shift away from Ubuntu 20 in Spring 2.0, so keeping systems updated will be important. The big news is the progress on Spring 2.0, especially the new "events" system. This could really change how nodes work, making them lighter and more efficient, which is something many operators have been asking for. They also talked about changing how often they meet because fewer people are showing up, so keep an eye on those discussions in the Telegram group. Overall, it seems like a lot is happening, and staying informed will be key for anyone running a Vaulta node.
This article was created with support from AI-driven technology, drawing on multiple reputable sources. The final content has been thoroughly reviewed and edited by BlockzHub's editorial team to ensure accuracy, clarity, and coherence. Original reporting sources are credited whenever appropriate and as required. The opinions expressed in this article do not necessarily represent the official views or positions of BlockzHub. This article is intended for informational purposes only and should not be considered financial or professional advice. Investing involves risk, and you should consult a qualified financial advisor before making any investment decisions.