<aside> 👉

This page is a living, public log of what AxLabs has been building and delivering for the Neo ecosystem.

</aside>

<aside> 🎯

The goal is simple: if you’re wondering “what has AxLabs been doing for Neo lately?”, this is the single place to check.

</aside>

<aside> 🗓️

We aim to publish updates weekly (typically on Fridays), but we don’t treat cadence as a hard rule. Some weeks we’ll publish more updates, sometimes we’ll bundle updates bi-weekly, and holidays may create gaps. What matters is consistency over time: clear, concrete progress snapshots as work lands.

</aside>

April 3, 2026

✅ Delivered

👉 General

• Upgraded AxLabs’ Neo X nodes to v0.5.3 release version.
• Collaborated with the Neo community to push the original proposal for the creation of a “Strategy and Treasury Board” (more details can be found here). Talked to co-founders and related entities (like NGD), given that there was a pause in talks during February.

👉 BaneLabs (Neo X)

• NeoFS Fund Proxy
  • Deployment on mainnet + testnet
  • Final tests
  • 3vm integration
  • Usage example for on-chain interaction
  • Watch tower bug fixes
• Bridge Validator & Relayer — RabbitMQ Resilience, Observability & Runtime Correctness
  • Released v4.3.0, consolidating resilience, observability, and runtime correctness improvements across validator and relayer components
  • Restored backward-compatible withdrawal JSON encoding (0x-prefixed addresses) to maintain wire compatibility with pre-v5 (v4.2) relayers
  • Eliminated relayer queue dead-ends by introducing centralized ack handling, drop-and-ack semantics for malformed messages, and explicit consumer tagging/cancellation
  • Hardened validator processing by classifying transient publish dependency failures and retrying the same block in both catch-up and normal operation
  • Improved RabbitMQ outage handling by reducing log noise for recoverable failures and introducing explicit degraded-mode transition signaling
  • Added first-class Prometheus observability for relayer degraded mode, including state, transitions, duration, and true retry metrics
  • Tightened degraded-mode tracking semantics and initialization guarantees to better reflect actual incident vs retry behavior
  • Refined logging behavior and startup semantics to more accurately represent operational state (e.g., consumption readiness only after successful setup)
  • Continued strengthening runtime correctness and failure handling across relayer and validator loops under adverse conditions

🔜 What’s Next

• Explore EIP-3009 (xGAS) and x402
• Finalize the Bridge Indexer backend and frontend
• Monitor and stabilize Bridge Validator & Relayer in production (post v4.3.0)
• Iterate on NeoFS Fund Proxy based on mainnet usage and feedback

• March 20, 2026
• March 6, 2026
• February 20, 2026
• January 30, 2026
• January 9, 2026