NeoFS SDK Gets an Update—Here’s What’s New
Neo SPCC just dropped RC14 of its NeoFS SDK, and it’s a solid step forward for developers working with the platform. The big focus this time? Compatibility with API v2.18 and a bunch of under-the-hood tweaks aimed at making things run smoother. It’s not flashy, but for anyone building on NeoFS, these changes matter.
One of the more practical additions is the new iterator APIs for handling parameters and attributes. If you’re dealing with large datasets, this should cut down on memory overhead—no more wrestling with sluggish performance when processing streams of data. And if your app leans heavily on GRPC connections, you’ll probably notice fewer hiccups. The SDK now reuses existing connections, which means less time wasted on setup and more consistent throughput.
Features Developers Actually Asked For
This release isn’t just about optimization, though. Neo SPCC finally added support for N3 witnesses in requests and objects, something developers had been pushing for. It’s a niche thing, sure, but if your workflow involves complex transactions or verification steps, this’ll save you some headaches. There’s also better handling of unsigned GET/HEAD responses, which is handy for cases where you don’t need to bother with signature validation. Small wins, but they add up.
Another quality-of-life improvement: associate attribute handling and version string decoding. Neither is groundbreaking, but both mean less boilerplate code to write. Fewer custom utilities to maintain, fewer chances for bugs to creep in. Sometimes it’s the little things that make a difference.
Cleaning House and Squashing Bugs
RC14 also tidies up some older, deprecated components, bringing the SDK in line with current NeoFS standards. If you’re integrating with the latest network version, this should make things play nicer out of the box. And, of course, there are the usual bug fixes—connection handling, memory leaks, edge cases in object processing. Nothing earth-shattering, but the kind of stability tweaks that keep apps from crashing at the worst possible moment.
It’s worth noting that none of this is revolutionary. But then again, most good updates aren’t. They’re incremental, practical, and shaped by what developers actually need. This one feels like it checks those boxes.
For the full rundown, including the nitty-gritty details, you can check out the release notes on GitHub. No hype, just the facts—which, honestly, is refreshing.
[Read the full release notes here](https://github.com/nspcc-dev/neofs-sdk-go/releases/tag/v1.0.0-rc.14)
