Vaulta node operators recently met to go over some important updates. The team discussed the latest on the Spring 2.0 hard fork, including a new developer preview. They also talked about a new system for events on the chain and how the new gossip network is being adopted. It was a pretty packed meeting with a lot of technical details.
Key Takeaways
-
The Spring 2.0 hard fork is moving along, with a developer preview now available for testing. Node operators should check out the changes, especially with CDT 5.0, and report any issues they find. This testing is important for catching bugs early.
-
A new event system is being built, which will help track what's happening on the chain. The next preview will add events, and feedback from node operators is needed to make sure it works well and doesn't cause problems with storage or performance.
-
Adoption of the gossip network is starting slowly, with more peer keys being registered. Getting the network fully running without manual setup is the next step, and feedback from major block producers will help figure out how to make it easier for everyone to join.
Antelope Spring 2: Developer Preview Series
The Antelope Spring 2 release is rolling out its Developer Preview Series, giving folks a chance to kick the tires on new features. The first preview is already up and running on the testnet. You don't need to be a block producer to get involved; just running a test node is enough. The main things being looked at right now are updates to how transactions get checked and the first bits of support for sync calls. If you're building things with CDT 5.0, now's a good time to deploy those contracts and see how they work with this preview. Early testing has already turned up a bug related to sync calls, which really shows why having the community test things out is so important.
Transaction Validation Updates
This preview includes changes to how transactions are checked before they get added to blocks. The goal is to make this process more robust and catch potential issues earlier.
Initial Sync Call Support
Work has started on supporting sync calls, which are a new way for smart contracts to interact. This initial support is basic but lays the groundwork for more advanced features later on.
Community Testing Encouraged
Node operators and developers are strongly encouraged to set up test nodes and deploy contracts. Providing feedback on bugs and performance helps iron out problems before the official release.
Event System Development and Roadmap
The development of the event system is moving forward, and it's a pretty big deal for how we see what's happening on the network. Think of events as a way for outside systems to get a clear picture of what's going on, especially with sync calls. They're not going to show up in every single place you might look, like some API outputs, but they will be available in standard places such as the Trace API and DeepMind. This is important because a lot of future features will depend on this event system working right.
Developer Preview 2: Events Without Proofs
The team is aiming to get Developer Preview 2 out in early September. This version will introduce the event system, but without the proofs attached. The main goal right now is to make sure it's easy to use and understand. The idea of adding proofs to these events might come later, possibly in Preview 3. This staged approach let the team get the core functionality out there for people to try.
Roadmap and Future Considerations
The roadmap for the event system is pretty straightforward for now. The immediate focus is on getting the system stable and usable. After that, they'll look at adding proofs, which will make the events verifiable. This means node operators will need to plan for how events will be stored and indexed, as they're different from regular blockchain state. They're added on, kind of like a log. The team is really hoping people will jump into testing Preview 2 when it drops so they can get feedback on how it performs. That feedback is going to help them iron out any issues before the main network upgrade.
Node Impact and Feedback for Events
The introduction of events into the Antelope protocol brings about noticeable changes for node operators. These changes primarily stem from the new requirements for on-disk storage and the indexing necessary to make event data accessible. Unlike the core blockchain state, events are designed as append-only records, which means careful consideration must be given to resource allocation and planning. Node operators are strongly encouraged to get involved with the upcoming Developer Preview 2. This testing phase is a prime opportunity to provide direct feedback on the performance implications of event handling. The insights gathered from these early adopters will be instrumental in refining the event system before its official integration via a hard fork.
Gossip Peering Adoption Update
The adoption of gossip peering is showing early signs of progress, with a steady increase in registered peer keys. This indicates that node operators are beginning to integrate this new networking capability. The current phase focuses on gathering data and feedback to refine the system before wider deployment.
Current Status and Challenges
-
Peer Key Registrations: A gradual rise in the number of peer keys being registered has been observed. This is a positive indicator of initial uptake.
-
Manual Configuration: At present, setting up gossip peering still requires manual configuration. This is a temporary measure, but it presents a barrier to fully decentralized peer discovery.
-
Network Mesh Assessment: To better understand the network's connectivity, top block producers have been asked to share their active gossip peer lists privately. This information will help map the progress of the gossip network's mesh.
Future Improvements
Efforts are underway to streamline the process of establishing peer connections. The goal is to reduce the initial setup effort for node operators and to build a more robust and resilient network. Future updates are expected to address the manual configuration requirement, making it easier for nodes to find and connect with each other automatically.
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.