Michael Bucher

AxLabs (@ax_labs) has launched the Neo Bridge Indexer, a public dashboard that tracks the live status of the native bridge between Neo N3 and Neo X. Both the frontend and backend codebases have been open-sourced on GitHub under the bane-labs organization. neonewstoday.com/development/ax…

Announcing 🥁🥁🥁 Neo Bridge Indexer is now live: a public dashboard to track the status of the bridge between Neo N3 and Neo X. It helps answer simple but important questions: Is the bridge working? Are there delays? Is maintenance affecting operations? More transparency for the @Neo_Blockchain community. 👉 indexer.xbridge.neo.org AxLabs will develop and maintain the Neo Bridge Indexer as a public good for the ecosystem, which is why it is published under the Neo domain. Feedback and feature requests are welcome. Drop a comment below 👇

@snakey_rob @r3ejimmy @Neo_Blockchain @dahongfei @erikzhang @ax_labs @NEOnewstoday @cityofzion_neo @ngd_neo Getting it done reliably matters more than a few days. - The tx has a defined window (starting Monday, ~1 week) - Operators needed to prep for 3s block time (node config changes) - Alignment in a meeting ≠ singing on-chain The delay is negligible – rollout safety came first.

@r3ejimmy @Neo_Blockchain @dahongfei @erikzhang @ax_labs @NEOnewstoday @cityofzion_neo @ngd_neo Good to finally see some alignment, but why does it take so long for everyone to execute the vote when basically everyone who voted was already in the meeting?

Over 13 council signatures are collected, valid for the 3-second-consensus activation. neo3scan.com/tools/governan…. Transaction will be sent 22 hours later. @Neo_Blockchain @dahongfei @erikzhang @ax_labs @NEOnewstoday @cityofzion_neo @ngd_neo

@GrabowskiDylan 🤣

The crypto markets are starting to feel resilient. There’s geopolitical and macro events, DeFi hacks with extreme contagion, and wide scale brain drain to AI. But BTC and ETH are sitting strong in their range, impervious to negative sentiment.

Who decides which users get sacrificed? 17% of rsETH is unbacked. Contracts paused. No redemptions. Kelp DAO has 2 ugly choices: 1) Socialize the 20% loss across all holders 2) Dump 100% of the pain onto L2 rsETH holders only. Who holds the power to pick the losers?

Backends have CI/CD. Frontends have CI/CD. Smart contract interfaces (ABIs) still live in Slack or Discord threads, docs, and Git repos. This is still far too manual. Too fragmented. There has to be a better way. So we built GitMyABI. Announcing 🥁🥁🥁 gitmyabi.com GitMyABI turns smart contract interfaces (ABIs) into proper build artifacts: - deterministic ABI outputs - stable URLs - versioned npm packages with bindings - reproducible builds for every commit Instead of: "Hey, do you have the latest ABI?" You get a URL. You get an npm package. You get a specific version. This becomes even more important in a world of AI agents, where smart contract integrations need reliable, ready-to-consume interfaces they can plug directly into dApps. We also use decentralized storage (NeoFS) to store smart contract npm packages, enabling: - immutable packages - decentralized hosting - verifiable artifact distribution And we’re not stopping there. We’re building an MCP interface so LLMs and agents can connect directly to GitMyABI and fetch contract artifacts more easily. This is just the beginning. Try it out and tell us what you think: 👉 gitmyabi.com

Catch up on last week's $NEO ecosystem news with our Week in Review, feat. Neo co-founder Da Hongfei (@dahongfei) publishing a proposal to restructure the Neo Foundation & Erik Zhang (@erikzhang) releasing a Neo Governance Restoration Proposal. youtu.be/Il02-YtF7Go

Thank you @lllwvlvwlll github.com/neo-project/pr… @Neo_Blockchain $NEO

Two proposals, one community. Neo's co-founders have each published a vision for Foundation reform. We've put the topics side by side to make it easy for everyone to contribute feedback on specific items and help shape one shared path forward. proposals.neonewstoday.com

“Zurich3: The non-profit community space for builders” by Adrian Kögl Adrian Kögl addresses how Switzerland’s world-class blockchain talent remains fragmented and makes the case for Zurich3, a dedicated non-profit community space to foster real collaboration.

Yet another day, yet another announcement: NeoFS deposits can now be initiated from Neo X. 🤩 This means users and apps on Neo X can fund NeoFS without needing to interact directly with Neo N3. As we said before, our goal is to expose the best features of Neo N3 to Neo X. The Message Bridge is a key enabler for this and many other cross-chain use cases. A small step in UX, a big step toward a more connected Neo ecosystem. Contract repos: 👉 github.com/bane-labs/neof… 👉 github.com/bane-labs/neof… 1/3 @neospcc @Neo_Blockchain @ngd_neo

Of course we’ll be at @EthereumZurich! 😅 @gsmachado will be speaking about why smart contract interfaces should be treated more like modern software artifacts: versioned, discoverable, provenance-linked, and ready for AI agents. Talk: “Smart Contract Interfaces (ABIs) Deserve Better” When: Friday, April 10 Looking forward to making new connections and seeing old friends too! @uzh_blockchain @zurich3_space @zuitzerland

Learned a new term today: JOMO – Joy of Missing Out. In crypto we're constantly surrounded by FOMO: new tokens, new narratives, "last chances" everywhere. But maybe the real edge is JOMO: staying calm, skipping the noise, and focusing on what actually matters.

@r3ejimmy I like that direction – feels like the missing layer. From what we’ve seen, operators want visibility into configs/plugins, but it’s still too manual (even updates mean digging through raw changes). So unless it’s mainnet, most just use public nodes.

thank you for sharing this, what i focus is actually about manage the node, like working with a GUI, a page, to install/config plugins, know what is what, one click update nodes, know what has being changed in config, and if there is any conflict, node status, rpc management, wallet security, alike, more about DevOps.

@isleepcode @r3ejimmy @ax_labs That’s right – we tried a 1-click node setup at @ax_labs for testnet/mainnet before, but sunset it due to no real demand.

@r3ejimmy I believe @ax_labs offers one click node deployment already or at least have in the past

would be better to be able to provide node service directly,,,, cause i am also thinking about somthing like "one click to setup a devnet"..... but a manager also works so far.

@r3ejimmy We do have a Docker-based devnet that spins up the full bridge infra (N3 + Neo X, monitoring), which is pretty close to what you’re describing. More for dev use, but you can reuse the node parts from it. Repo: github.com/AxLabs/neox-br…

From day one, part of the vision for Neo X was clear: when it makes sense, bring the best of Neo N3 into the EVM world. 🔗 Today, we’re announcing: Neo Oracle Gateway A new step toward making Neo N3’s native capabilities, starting with its built-in Oracle service, available to developers building on Neo X. The Neo Oracle Gateway uses the Message Bridge and is now deployed on both 'testnet' and 'mainnet', across Neo X and Neo N3. Want to try it? Check the docs and see how to make Oracle calls from Neo X: 👉 xdocs.ngd.network/integrations/o…

Neo has entered into an integration agreement with LayerZero (@LayerZero_Core), the omnichain messaging protocol, to bring cross-chain communication to Neo X. TestNet integration is expected to be completed by the end of the month, with MainNet to follow. neonewstoday.com/general/neo-si…

Hey @Neo_Blockchain fam 👋 Neo N3 native Oracles… for Neo X and EVM smart contracts. 👀 Stay tuned. @NEOnewstoday @r3ejimmy @erikzhang @dahongfei @ngd_neo