Neo SPCC has released updates to NeoFS OAuthZ and introduced Archive.NeoFS, a new web application for generating offline node synchronization packages.

As with all Neo SPCC web applications, both Archive.NeoFS and Send.NeoFS are fully hosted on NeoFS itself.

Archive.NeoFS

Archive.NeoFS is a web application that allows node operators to generate custom block data snapshots for public Neo networks over any specified range. These snapshots are typically used to quickly bootstrap a node.

The app retrieves block data from NeoFS via the REST Gateway. This data is assembled into Neo’s custom .acc format and streamed directly to a file by the frontend client. The feature relies on modern web APIs and requires Chrome version 86 or later.

The generated chain dumps are compatible with the proposed NEP-32 standard and work with both Neo C# and Go nodes. Instructions for synchronizing from an offline package can be found in the respective node documentation. The code for Archive.NeoFS is available on GitHub here.

Download NeoFS-based offline synchronization packages at the link below:
https://archive.fs.neo.org/

NeoFS OAuthZ

Neo SPCC also released a patched version of neofs-oauthz, an authentication backend that enables users to log in to NeoFS using OAuth2 via Google or GitHub.

The neofs-oauthz utility works by associating the user’s email with their bearer token, allowing uploaded objects to be identified by user. The new release includes an additional filter for an undesired MIME type, disables log sampling, and updates several dependencies.

The service is primarily used by Send.NeoFS, a demo application by Neo SPCC that offers free, temporary file uploads while showcasing how to build with NeoFS technologies. Files uploaded through Send.NeoFS are stored in a container with an extended access control list. This EACL permits only Neo SPCC to upload or delete objects.

When users authenticate via Google or GitHub, neofs-oauthz—operated by Neo SPCC—uses the container owner’s key to issue a bearer token granting the user upload access. This token associates the user’s email with their uploaded objects and enforces additional constraints, such as size and file type limits.

Users can test Send.NeoFS at the link below:
https://send.fs.neo.org/

Tags: