Neo X Users Can Finally Fill Their NeoFS Buckets Without Touching Neo N3

Bane Labs has dropped NeoFS Fund Proxy contracts, letting Neo X users and apps fund NeoFS storage containers without dealing with Neo N3 directly. AxLabs, one of the three teams behind Bane Labs, also updated its 3vm developer tool with a live wallet-connected interface for depositing $GAS to NeoFS from Neo X. Because nothing says "user-friendly blockchain" like forcing people to juggle two networks just to store some cat pictures.

NeoFS is Neo's distributed, decentralized object storage network where users pay for storage by depositing $GAS to the NeoFS smart contract. Previously, funding a NeoFS container meant transacting directly with Neo N3—the blockchain equivalent of going through customs twice for a connecting flight you didn't ask for. The Fund Proxy eliminates that requirement for Neo X users by routing the entire funding flow through the Message Bridge, the cross-chain communication layer launched in December 2025 that connects Neo X and Neo N3.

What this enables The Fund Proxy opens NeoFS storage to the Neo X user base without requiring them to manage Neo N3 wallets or transactions. Applications building on Neo X can now programmatically fund storage containers as part of their on-chain logic. This is the second major feature built on the Message Bridge infrastructure, following the Oracle Gateway launch in March, and delivers on a use case listed in the Message Bridge documentation at launch: interacting with NeoFS from EVM-based applications. Finally, developers can store things on-chain without needing a degree in Neo archaeology.

How it works The Fund Proxy operates through a two-step cross-chain flow combining both components of the bridge infrastructure. First, the EVM-side contract initiates a token bridge operation moving $GAS from Neo X to Neo N3, directing it to the N3 NeoFSFundProxy contract address. Second, the contract sends an executable message through the bridge calling a funding function on the N3 contract. The N3 contract then claims the bridged $GAS and forwards it to the NeoFS smart contract on behalf of the specified beneficiary. The entire cross-chain call is encoded on-chain using a Solidity serialization library, meaning the EVM contract constructs the N3 contract call parameters without off-chain intermediaries. Users call a single function on the EVM side, providing the beneficiary address, the amount of $GAS to fund, and maximum bridge fees. The contract handles both the token transfer and the cross-chain message in one transaction. The N3-side contract, built with neow3j, accepts the bridged $GAS through a NEP-17 payment callback and forwards the balance to NeoFS when triggered by the message bridge. It's like a relay race, but the runners are smart contracts and nobody trips.

Other AxLabs tools Bane Labs is the collaborative development entity behind Neo X tooling, comprising Neo Global Development, AxLabs, and Neo SPCC. AxLabs previously released TypeScript SDKs for NeoFS that handle storage operations, including container management and object uploads. The Fund Proxy complements that tooling by handling the payment side. Think of it as the difference between having a fancy kitchen and having money for groceries—both necessary, neither sufficient on their own.

AxLabs also updated 3vm, its developer tool for inspecting and debugging the Message Bridge, to include support for NeoFS deposits. Users can connect a wallet at 3vm.axlabs.net and deposit $GAS to NeoFS from Neo X, taking advantage of the Fund Proxy. No more manually bridging tokens while whispering prayers to the blockchain gods—just click, fund, and pretend you understood all the technical steps happening under the hood.