[#56] object: Introduce Patch method

* Introduce rpc `Patch` and corresponding types;
* Generate docs.

Signed-off-by: Airat Arifullin <aarifullin@yadro.com>

.forgejo/workflows/dco.yaml

@@ -1,19 +0,0 @@
-name: DCO action
-on: [pull_request]
-
-jobs:
-  dco:
-    name: DCO
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v3
-        with:
-          fetch-depth: 0
-      - name: Setup Go
-        uses: actions/setup-go@v3
-        with:
-          go-version: '1.22'
-      - name: Run commit format checker
-        uses: https://git.frostfs.info/TrueCloudLab/dco-go@v3
-        with:
-          from: 'origin/${{ github.event.pull_request.base.ref }}'

.forgejo/workflows/fmt.yaml

@@ -1,17 +0,0 @@
-name: Formatters
-on: [pull_request]
-
-jobs:
-  fmt:
-    name: Run fmt
-    runs-on: ubuntu-22.04
-    steps:
-      - uses: actions/checkout@v3
-      - name: Install deps
-        run: |
-          apt update
-          apt install -y clang-format
-      - name: Run fmt
-        run: |
-          make fmt
-          git diff --exit-code --quiet

.forgejo/workflows/pre-commit.yaml

@@ -1,18 +0,0 @@
-name: Pre-commit hooks
-on: [pull_request]
-
-jobs:
-  pre-commit:
-    name: Pre-commit
-    env:
-      # Skip pre-commit hooks which are executed by other actions.
-      SKIP: make-fmt
-    runs-on: ubuntu-22.04
-    steps:
-      - uses: actions/checkout@v3
-      - name: Install deps
-        run: |
-          apt update
-          apt install -y pre-commit
-      - name: Run pre-commit
-        run: pre-commit run --all-files --hook-stage manual --color=always

.github/CODEOWNERS

@@ -0,0 +1 @@
+*   @alexvanin @realloc @fyrchik @anatoly-bogatyrev

.github/workflows/buf.yml

@@ -0,0 +1,36 @@
+name: Buf lint
+
+on:
+  pull_request:
+    branches:
+      - master
+
+jobs:
+  lint:
+    runs-on: ubuntu-20.04
+    steps:
+      - uses: actions/checkout@v2
+      - uses: wizhi/setup-buf@v1
+        with:
+          version: 0.20.5
+      - run: buf check lint
+
+  breaking:
+    runs-on: ubuntu-20.04
+    steps:
+      - name: Setup buf
+        uses: wizhi/setup-buf@v1
+        with:
+          version: 0.20.5
+      - name: Check out ref code
+        uses: actions/checkout@v2
+        with:
+          ref: ${{ github.base_ref }}
+          path: baseref
+      - run: cd baseref && buf image build -o image.bin
+
+      - name: Check out code
+        uses: actions/checkout@v2
+        with:
+          path: prclone
+      - run: cd prclone && buf check breaking --against-input ../baseref/image.bin

.github/workflows/dco.yml

@@ -0,0 +1,21 @@
+name: DCO check
+
+on:
+  pull_request:
+    branches:
+      - master
+
+jobs:
+  commits_check_job:
+    runs-on: ubuntu-latest
+    name: Commits Check
+    steps:
+    - name: Get PR Commits
+      id: 'get-pr-commits'
+      uses: tim-actions/get-pr-commits@master
+      with:
+        token: ${{ secrets.GITHUB_TOKEN }}
+    - name: DCO Check
+      uses: tim-actions/dco@master
+      with:
+        commits: ${{ steps.get-pr-commits.outputs.commits }}

.gitignore

@@ -1 +1,2 @@
 .idea
+

.pre-commit-config.yaml

@@ -1,24 +0,0 @@
-repos:
-  - repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v4.6.0
-    hooks:
-      - id: check-added-large-files
-      - id: check-case-conflict
-      - id: check-executables-have-shebangs
-      - id: check-shebang-scripts-are-executable
-      - id: check-merge-conflict
-      - id: check-json
-      - id: check-xml
-      - id: check-yaml
-      - id: trailing-whitespace
-        args: [--markdown-linebreak-ext=md]
-      - id: end-of-file-fixer
-        exclude: ".svg$"
-
-  - repo: local
-    hooks:
-      - id: make-fmt
-        name: Run make fmt
-        entry: make fmt
-        language: system
-        pass_filenames: false

CODEOWNERS

@@ -1,3 +0,0 @@
-.*   @alexvanin @realloc @fyrchik @a.bogatyrev @TrueCloudLab/storage-sdk-developers
-.forgejo/.* @potyarkin
-Makefile    @potyarkin

CONTRIBUTING.md

@@ -3,8 +3,8 @@
 First, thank you for contributing! We love and encourage pull requests from
 everyone. Please follow the guidelines:
 
-- Check the open [issues](https://git.frostfs.info/TrueCloudLab/frostfs-api/issues) and
+- Check the open [issues](https://github.com/TrueCloudLab/frostfs-api/issues) and
-  [pull requests](https://git.frostfs.info/TrueCloudLab/frostfs-api/pulls) for existing
+  [pull requests](https://github.com/TrueCloudLab/frostfs-api/pulls) for existing
   discussions.
 
 - Open an issue first, to discuss a new feature or enhancement.
@@ -25,20 +25,19 @@ Start by forking the `frostfs-api` repository, make changes in a branch and then
 send a pull request. We encourage pull requests to discuss code changes. Here
 are the steps in details:
 
-### Set up your repository
+### Set up your GitHub Repository
-
+Fork [NeoFS node upstream](https://github.com/TrueCloudLab/frostfs-api/fork) source
-Fork [FrostFS upstream](https://git.frostfs.info/TrueCloudLab/frostfs-api/fork) source
 repository to your own personal repository. Copy the URL of your fork (you will
 need it for the `git clone` command below).
 
 ```sh
-$ git clone https://git.frostfs.info/TrueCloudLab/frostfs-api
+$ git clone https://github.com/TrueCloudLab/frostfs-api
 ```
 
 ### Set up git remote as ``upstream``
 ```sh
 $ cd frostfs-api
-$ git remote add upstream https://git.frostfs.info/TrueCloudLab/frostfs-api
+$ git remote add upstream https://github.com/TrueCloudLab/frostfs-api
 $ git fetch upstream
 $ git merge upstream/master
 ...
@@ -87,7 +86,7 @@ $ git push origin feature/123-something_awesome
 ```
 
 ### Create a Pull Request
-Pull requests can be created via git.frostfs.info. Refer to [this
+Pull requests can be created via GitHub. Refer to [this
 document](https://help.github.com/articles/creating-a-pull-request/) for
 detailed steps on how to create a pull request. After a Pull Request gets peer
 reviewed and approved, it will be merged.

Makefile

@@ -1,35 +1,27 @@
 #!/usr/bin/make -f
 SHELL=bash
 
-include help.mk
+# BRanch to match for BReaking changes
+BRBR?=master
 
-.PHONY: doc fmt pre-commit unpre-commit pre-commit-run
+.PHONY: lint
+lint:
+	buf check lint
+	buf check breaking --against-input '.git#branch=$(BRBR)'
 
+.PHONY: doc
 # Regenerate documentation for proto files:
 doc:
 	@for f in `find . -type f -name '*.proto' -exec dirname {} \; | sort -u `; do \
 		echo "⇒ Documentation for $$(basename $$f)"; \
 		protoc \
-			--doc_opt=.forgejo/markdown.tmpl,$${f}.md \
+			--doc_opt=.github/markdown.tmpl,$${f}.md \
 			--proto_path=.:/usr/local/include \
 			--doc_out=proto-docs/ $${f}/*.proto; \
 	done
 
-# Run clang-format
 fmt:
 	@for f in `ls **/*.proto`; do \
 		echo "⇒ Formatting $$f"; \
 		clang-format -i $$f; \
 	done
-
-# Activate pre-commit hooks
-pre-commit:
-	pre-commit install --hook-type pre-commit
-
-# Deactivate pre-commit hooks
-unpre-commit:
-	pre-commit uninstall --hook-type pre-commit
-
-# Run pre-commit hooks
-pre-commit-run:
-	@pre-commit run --all-files --hook-stage manual

README.md

@@ -1,18 +1,19 @@
 <p align="center">
-<img src="./.forgejo/logo.svg" width="500px" alt="FrostFS">
+<img src="./.github/logo.svg" width="500px" alt="FrostFS">
 </p>
 <p align="center">
-  <a href="https://frostfs.info">FrostFS</a> API language-agnostic protocol definitions
+  <a href="https://objectstorage.info">FrostFS</a> API language-agnostic protocol definitions
 </p>
 
 ---
-![Release](https://git.frostfs.info/TrueCloudLab/frostfs-api/badges/release.svg)
+![GitHub release (latest SemVer)](https://img.shields.io/github/v/release/TrueCloudLab/frostfs-api?sort=semver)
+![License](https://img.shields.io/github/license/TrueCloudLab/frostfs-api.svg?style=popout)
 
 ## Overview
 
 FrostFS-API repository is the basis for language-specific libraries, e.g.:
 
-- [frostfs-api-go](https://git.frostfs.info/TrueCloudLab/frostfs-api-go)
+- [frostfs-api-go](https://github.com/TrueCloudLab/frostfs-api-go)
 
 Those libraries contain compiled protocol buffers definitions, wrapped with
 language-specific code. Use them to integrate applications with FrostFS.

accounting/service.proto

@@ -9,13 +9,13 @@ import "accounting/types.proto";
 import "refs/types.proto";
 import "session/types.proto";
 
-// Accounting service provides methods for interaction with FrostFS sidechain
+// Accounting service provides methods for interaction with NeoFS sidechain via
-// via other FrostFS nodes to get information about the account balance. Deposit
+// other NeoFS nodes to get information about the account balance. Deposit and
-// and Withdraw operations can't be implemented here, as they require Mainnet
+// Withdraw operations can't be implemented here, as they require Mainnet NeoFS
-// FrostFS smart contract invocation. Transfer operations between internal
+// smart contract invocation. Transfer operations between internal NeoFS
-// FrostFS accounts are possible if both use the same token type.
+// accounts are possible if both use the same token type.
 service AccountingService {
-  // Returns the amount of funds in GAS token for the requested FrostFS account.
+  // Returns the amount of funds in GAS token for the requested NeoFS account.
   //
   // Statuses:
   // - **OK** (0, SECTION_SUCCESS):
@@ -27,9 +27,9 @@ service AccountingService {
 // BalanceRequest message
 message BalanceRequest {
   // To indicate the account for which the balance is requested, its identifier
-  // is used. It can be any existing account in FrostFS sidechain `Balance`
+  // is used. It can be any existing account in NeoFS sidechain `Balance` smart
-  // smart contract. If omitted, client implementation MUST set it to the
+  // contract. If omitted, client implementation MUST set it to the request's
-  // request's signer `OwnerID`.
+  // signer `OwnerID`.
   message Body {
     // Valid user identifier in `OwnerID` format for which the balance is
     // requested. Required field.

accounting/types.proto

@@ -5,7 +5,7 @@ package neo.fs.v2.accounting;
 option go_package = "git.frostfs.info/TrueCloudLab/frostfs-api-go/v2/accounting/grpc;accounting";
 option csharp_namespace = "Neo.FileStorage.API.Accounting";
 
-// Standard floating point data type can't be used in FrostFS due to inexactness
+// Standard floating point data type can't be used in NeoFS due to inexactness
 // of the result when doing lots of small number operations. To solve the lost
 // precision issue, special `Decimal` format is used for monetary computations.
 //

acl/types.proto

@@ -89,14 +89,14 @@ enum HeaderType {
   // Filter object headers
   OBJECT = 2;
 
-  // Filter service headers. These are not processed by FrostFS nodes and
+  // Filter service headers. These are not processed by NeoFS nodes and
   // exist for service use only.
   SERVICE = 3;
 }
 
 // Describes a single eACL rule.
 message EACLRecord {
-  // FrostFS request Verb to match
+  // NeoFS request Verb to match
   Operation operation = 1 [ json_name = "operation" ];
 
   // Rule execution result. Either allows or denies access if filters match.
@@ -165,7 +165,7 @@ message EACLRecord {
 // Extended ACL rules table. A list of ACL rules defined additionally to Basic
 // ACL. Extended ACL rules can be attached to a container and can be updated
 // or may be defined in `BearerToken` structure. Please see the corresponding
-// FrostFS Technical Specification section for detailed description.
+// NeoFS Technical Specification section for detailed description.
 message EACLTable {
   // eACL format version. Effectively, the version of API library used to create
   // eACL Table.
@@ -196,8 +196,7 @@ message BearerToken {
     // valid for this specific container. Otherwise, any container of the same
     // owner is allowed.
     //
-    // Deprecated: eACL tables are no longer relevant - `APEOverrides` should be
+    // Deprecated: eACL tables are no longer relevant - `APEOverrides` should be used instead.
-    // used instead.
     EACLTable eacl_table = 1 [ json_name = "eaclTable" ];
 
     // `OwnerID` defines to whom the token was issued. It must match the request
@@ -224,12 +223,11 @@ message BearerToken {
     bool allow_impersonate = 4 [ json_name = "allowImpersonate" ];
 
     // APEOverride is the list of APE chains defined for a target.
-    // These chains are meant to serve as overrides to the already defined (or
+    // These chains are meant to serve as overrides to the already defined (or even undefined)
-    // even undefined) APE chains for the target (see contract `Policy`).
+    // APE chains for the target (see contract `Policy`).
     //
-    // The server-side processing of the bearer token with set APE overrides
+    // The server-side processing of the bearer token with set APE overrides must verify if a client is permitted
-    // must verify if a client is permitted to override chains for the target,
+    // to override chains for the target, preventing unauthorized access through the APE mechanism.
-    // preventing unauthorized access through the APE mechanism.
     message APEOverride {
       // Target for which chains are applied.
       frostfs.v2.ape.ChainTarget target = 1 [ json_name = "target" ];

buf.yaml

@@ -0,0 +1,10 @@
+lint:
+  use:
+    - DEFAULT
+    - COMMENTS
+    - ENUM_FIRST_VALUE_ZERO
+  except:
+    - PACKAGE_DIRECTORY_MATCH
+    - PACKAGE_VERSION_SUFFIX
+    - ENUM_VALUE_PREFIX
+    - ENUM_ZERO_VALUE_SUFFIX

container/service.proto

@@ -5,13 +5,14 @@ package neo.fs.v2.container;
 option go_package = "git.frostfs.info/TrueCloudLab/frostfs-api-go/v2/container/grpc;container";
 option csharp_namespace = "Neo.FileStorage.API.Container";
 
+import "acl/types.proto";
 import "container/types.proto";
 import "refs/types.proto";
 import "session/types.proto";
 
 // `ContainerService` provides API to interact with `Container` smart contract
-// in FrostFS sidechain via other FrostFS nodes. All of those actions can be
+// in NeoFS sidechain via other NeoFS nodes. All of those actions can be done
-// done equivalently by directly issuing transactions and RPC calls to sidechain
+// equivalently by directly issuing transactions and RPC calls to sidechain
 // nodes.
 service ContainerService {
   // `Put` invokes `Container` smart contract's `Put` method and returns
@@ -52,7 +53,7 @@ service ContainerService {
   //   access to container is denied. 
   rpc Get(GetRequest) returns (GetResponse);
 
-  // Returns all owner's containers from `Container` smart contract storage.
+  // Returns all owner's containers from 'Container` smart contract' storage.
   //
   // Statuses:
   // - **OK** (0, SECTION_SUCCESS): \
@@ -62,19 +63,44 @@ service ContainerService {
   //   container list access denied.  
   rpc List(ListRequest) returns (ListResponse);
 
-  // Returns all owner's containers from `Container` smart contract storage
+  // Invokes 'SetEACL' method of 'Container` smart contract and returns response
-  // via stream.
+  // immediately. After one more block in sidechain, changes in an Extended ACL
+  // are added into smart contract storage.
   //
   // Statuses:
   // - **OK** (0, SECTION_SUCCESS): \
-  //   container list has been successfully read;
+  //   request to save container eACL has been sent to the sidechain;
   // - Common failures (SECTION_FAILURE_COMMON);
   // - **CONTAINER_ACCESS_DENIED** (3074, SECTION_CONTAINER): \
-  //   container list access denied.
+  //   set container eACL access denied.  
-  rpc ListStream(ListStreamRequest) returns (stream ListStreamResponse);
+  rpc SetExtendedACL(SetExtendedACLRequest) returns (SetExtendedACLResponse);
+
+  // Returns Extended ACL table and signature from `Container` smart contract
+  // storage.
+  //
+  // Statuses:
+  // - **OK** (0, SECTION_SUCCESS): \
+  //   container eACL has been successfully read;
+  // - Common failures (SECTION_FAILURE_COMMON);
+  // - **CONTAINER_NOT_FOUND** (3072, SECTION_CONTAINER): \
+  //   container not found;
+  // - **EACL_NOT_FOUND** (3073, SECTION_CONTAINER): \
+  //   eACL table not found;
+  // - **CONTAINER_ACCESS_DENIED** (3074, SECTION_CONTAINER): \
+  //   access to container eACL is denied.  
+  rpc GetExtendedACL(GetExtendedACLRequest) returns (GetExtendedACLResponse);
+
+  // Announces the space values used by the container for P2P synchronization.
+  //
+  // Statuses:
+  // - **OK** (0, SECTION_SUCCESS): \
+  //   estimation of used space has been successfully announced;
+  // - Common failures (SECTION_FAILURE_COMMON).
+  rpc AnnounceUsedSpace(AnnounceUsedSpaceRequest)
+      returns (AnnounceUsedSpaceResponse);
 }
 
-// New FrostFS Container creation request
+// New NeoFS Container creation request
 message PutRequest {
   // Container creation request has container structure's signature as a
   // separate field. It's not stored in sidechain, just verified on container
@@ -82,7 +108,7 @@ message PutRequest {
   // the stable-marshalled container strucutre, hence there is no need for
   // additional signature checks.
   message Body {
-    // Container structure to register in FrostFS
+    // Container structure to register in NeoFS
     container.Container container = 1;
 
     // Signature of a stable-marshalled container according to RFC-6979.
@@ -101,7 +127,7 @@ message PutRequest {
   neo.fs.v2.session.RequestVerificationHeader verify_header = 3;
 }
 
-// New FrostFS Container creation response
+// New NeoFS Container creation response
 message PutResponse {
   // Container put response body contains information about the newly registered
   // container as seen by `Container` smart contract. `ContainerID` can be
@@ -130,7 +156,7 @@ message DeleteRequest {
   // the container owner's intent. The signature will be verified by `Container`
   // smart contract, so signing algorithm must be supported by NeoVM.
   message Body {
-    // Identifier of the container to delete from FrostFS
+    // Identifier of the container to delete from NeoFS
     neo.fs.v2.refs.ContainerID container_id = 1;
 
     // `ContainerID` signed with the container owner's key according to
@@ -257,14 +283,18 @@ message ListResponse {
   neo.fs.v2.session.ResponseVerificationHeader verify_header = 3;
 }
 
-// List containers stream
+// Set Extended ACL
-message ListStreamRequest {
+message SetExtendedACLRequest {
-  // List containers stream request body.
+  // Set Extended ACL request body does not have separate `ContainerID`
+  // reference. It will be taken from `EACLTable.container_id` field.
   message Body {
-    // Identifier of the container owner.
+    // Extended ACL table to set for the container
-    neo.fs.v2.refs.OwnerID owner_id = 1;
+    neo.fs.v2.acl.EACLTable eacl = 1;
+
+    // Signature of stable-marshalled Extended ACL table according to RFC-6979.
+    neo.fs.v2.refs.SignatureRFC6979 signature = 2;
   }
-  // Body of list containers stream request message.
+  // Body of set extended acl request message.
   Body body = 1;
 
   // Carries request meta information. Header data is used only to regulate
@@ -277,15 +307,117 @@ message ListStreamRequest {
   neo.fs.v2.session.RequestVerificationHeader verify_header = 3;
 }
 
-// List containers stream
+// Set Extended ACL
-message ListStreamResponse {
+message SetExtendedACLResponse {
-  // List containers stream response body.
+  // `SetExtendedACLResponse` has an empty body because the operation is
-  message Body {
+  // asynchronous and the update should be reflected in `Container` smart
-    // List of `ContainerID`s belonging to the requested `OwnerID`
+  // contract's storage after next block is issued in sidechain.
-    repeated refs.ContainerID container_ids = 1;
+  message Body {}
-  }
 
-  // Body of list containers stream response message.
+  // Body of set extended acl response message.
+  Body body = 1;
+
+  // Carries response meta information. Header data is used only to regulate
+  // message transport and does not affect request execution.
+  neo.fs.v2.session.ResponseMetaHeader meta_header = 2;
+
+  // Carries response verification information. This header is used to
+  // authenticate the nodes of the message route and check the correctness of
+  // transmission.
+  neo.fs.v2.session.ResponseVerificationHeader verify_header = 3;
+}
+
+// Get Extended ACL
+message GetExtendedACLRequest {
+  // Get Extended ACL request body
+  message Body {
+    // Identifier of the container having Extended ACL
+    neo.fs.v2.refs.ContainerID container_id = 1;
+  }
+
+  // Body of get extended acl request message.
+  Body body = 1;
+
+  // Carries request meta information. Header data is used only to regulate
+  // message transport and does not affect request execution.
+  neo.fs.v2.session.RequestMetaHeader meta_header = 2;
+
+  // Carries request verification information. This header is used to
+  // authenticate the nodes of the message route and check the correctness of
+  // transmission.
+  neo.fs.v2.session.RequestVerificationHeader verify_header = 3;
+}
+
+// Get Extended ACL
+message GetExtendedACLResponse {
+  // Get Extended ACL Response body can be empty if the requested container does
+  // not have Extended ACL Table attached or Extended ACL has not been allowed
+  // at the time of container creation.
+  message Body {
+    // Extended ACL requested, if available
+    neo.fs.v2.acl.EACLTable eacl = 1;
+
+    // Signature of stable-marshalled Extended ACL according to RFC-6979.
+    neo.fs.v2.refs.SignatureRFC6979 signature = 2;
+
+    // Session token if Extended ACL was set within a session
+    neo.fs.v2.session.SessionToken session_token = 3;
+  }
+  // Body of get extended acl response message.
+  Body body = 1;
+
+  // Carries response meta information. Header data is used only to regulate
+  // message transport and does not affect request execution.
+  neo.fs.v2.session.ResponseMetaHeader meta_header = 2;
+
+  // Carries response verification information. This header is used to
+  // authenticate the nodes of the message route and check the correctness of
+  // transmission.
+  neo.fs.v2.session.ResponseVerificationHeader verify_header = 3;
+}
+
+// Announce container used space
+message AnnounceUsedSpaceRequest {
+  // Container used space announcement body.
+  message Body {
+    // Announcement contains used space information for a single container.
+    message Announcement {
+      // Epoch number for which the container size estimation was produced.
+      uint64 epoch = 1;
+
+      // Identifier of the container.
+      neo.fs.v2.refs.ContainerID container_id = 2;
+
+      // Used space is a sum of object payload sizes of a specified
+      // container, stored in the node. It must not include inhumed objects.
+      uint64 used_space = 3;
+    }
+
+    // List of announcements. If nodes share several containers,
+    // announcements are transferred in a batch.
+    repeated Announcement announcements = 1;
+  }
+
+  // Body of announce used space request message.
+  Body body = 1;
+
+  // Carries request meta information. Header data is used only to regulate
+  // message transport and does not affect request execution.
+  neo.fs.v2.session.RequestMetaHeader meta_header = 2;
+
+  // Carries request verification information. This header is used to
+  // authenticate the nodes of the message route and check the correctness of
+  // transmission.
+  neo.fs.v2.session.RequestVerificationHeader verify_header = 3;
+}
+
+// Announce container used space
+message AnnounceUsedSpaceResponse {
+  // `AnnounceUsedSpaceResponse` has an empty body because announcements are
+  // one way communication.
+  message Body {}
+
+  // Body of announce used space response message.
   Body body = 1;
 
   // Carries response meta information. Header data is used only to regulate

container/types.proto

@@ -50,7 +50,7 @@ message Container {
   //   (`__NEOFS__DISABLE_HOMOMORPHIC_HASHING` is deprecated) \
   //   Disables homomorphic hashing for the container if the value equals "true"
   //   string. Any other values are interpreted as missing attribute. Container
-  //   could be accepted in a FrostFS network only if the global network hashing
+  //   could be accepted in a NeoFS network only if the global network hashing
   //   configuration value corresponds with that attribute's value. After
   //   container inclusion, network setting is ignored.
   //

doc/release_instructions.md

@@ -1,6 +1,6 @@
 # Release instructions
 
-This documents outlines the frostfs-api release process and can be used as a TODO
+This documents outlines the neofs-api release process and can be used as a TODO
 list for a new release.
 
 ## Pre-release checks
@@ -20,7 +20,7 @@ Add an entry to the CHANGELOG.md following the style established there.
 Add a codename for releases with the new major version, version and release date in
 the heading. Write a paragraph describing the most significant changes done in
 this release. Then add sections with what has been added, changed and removed,
-describing each change briefly with a reference to issues, where
+describing each change briefly with a reference to GitHub issues, where
 available.
 
 ## Release commit
@@ -38,7 +38,7 @@ Release v2.9.0 - Anmyeondo (안면도, 安眠島)
 Use `vX.Y.Z` tag following the semantic versioning standard. For pre-release
 versions use `vX.Y.Z-rc.N` scheme.
 
-## Push changes and release tag to repository
+## Push changes and release tag to Github
 
 This step should bypass the default PR mechanism to get a correct result (so
 that releasing requires admin privileges for the project), both the `master`
@@ -48,9 +48,9 @@ branch update and tag must be pushed simultaneously like this:
 $ git push origin master v2.7.0
 ```
 
-## Make a proper release
+## Make a proper Github release
 
-Edit an automatically-created release on git.frostfs.info
+Edit an automatically-created release on Github.
 
 Release title has to follow `<version> <Romanized codename> (<Hangeul, Hanja
 codename> )` scheme for major releases and just `<version>` for regular point
@@ -58,5 +58,6 @@ releases.
 
 ## Post-release actions
 
-* Close corresponding X.Y.Z milestone
+* Close corresponding X.Y.Z Github milestone
 * Make announcements in Matrix and Discord channels
+* Update [NeoFS Technical Specification](https://github.com/nspcc-dev/neofs-spec)

help.mk

@@ -1,11 +0,0 @@
-.PHONY: help
-
-# Show this help prompt
-help:
-	@echo '  Usage:'
-	@echo ''
-	@echo '    make <target>'
-	@echo ''
-	@echo '  Targets:'
-	@echo ''
-	@awk '/^#/{ comment = substr($$0,3) } /^[a-zA-Z][a-zA-Z0-9_-]+:/{ print "   ", $$1, comment; comment = "" }' $(MAKEFILE_LIST) | column -t -s ':' | grep -v 'IGNORE' | sort | uniq

netmap/service.proto

@@ -12,7 +12,7 @@ import "session/types.proto";
 // `NetmapService` provides methods to work with `Network Map` and the
 // information required to build it. The resulting `Network Map` is stored in
 // sidechain `Netmap` smart contract, while related information can be obtained
-// from other FrostFS nodes.
+// from other NeoFS nodes.
 service NetmapService {
   // Get NodeInfo structure from the particular node directly.
   // Node information can be taken from `Netmap` smart contract. In some cases,
@@ -27,7 +27,7 @@ service NetmapService {
   // - Common failures (SECTION_FAILURE_COMMON).
   rpc LocalNodeInfo(LocalNodeInfoRequest) returns (LocalNodeInfoResponse);
 
-  // Read recent information about the FrostFS network.
+  // Read recent information about the NeoFS network.
   //
   // Statuses:
   // - **OK** (0, SECTION_SUCCESS):
@@ -35,7 +35,7 @@ service NetmapService {
   // - Common failures (SECTION_FAILURE_COMMON).
   rpc NetworkInfo(NetworkInfoRequest) returns (NetworkInfoResponse);
 
-  // Returns network map snapshot of the current FrostFS epoch.
+  // Returns network map snapshot of the current NeoFS epoch.
   //
   // Statuses:
   // - **OK** (0, SECTION_SUCCESS):
@@ -65,7 +65,7 @@ message LocalNodeInfoRequest {
 message LocalNodeInfoResponse {
   // Local Node Info, including API Version in use.
   message Body {
-    // Latest FrostFS API version in use
+    // Latest NeoFS API version in use
     neo.fs.v2.refs.Version version = 1;
 
     // NodeInfo structure with recent information from node itself

netmap/types.proto

@@ -36,9 +36,6 @@ enum Operation {
 
   // Logical negation
   NOT = 9;
-
-  // Matches pattern
-  LIKE = 10;
 }
 
 // Selector modifier shows how the node set will be formed. By default selector
@@ -122,7 +119,7 @@ message PlacementPolicy {
   // bucket
   repeated Replica replicas = 1 [ json_name = "replicas" ];
 
-  // Container backup factor controls how deep FrostFS will search for nodes
+  // Container backup factor controls how deep NeoFS will search for nodes
   // alternatives to include into container's nodes subset
   uint32 container_backup_factor = 2 [ json_name = "containerBackupFactor" ];
 
@@ -136,25 +133,25 @@ message PlacementPolicy {
   bool unique = 5 [ json_name = "unique" ];
 }
 
-// FrostFS node description
+// NeoFS node description
 message NodeInfo {
-  // Public key of the FrostFS node in a binary format
+  // Public key of the NeoFS node in a binary format
   bytes public_key = 1 [ json_name = "publicKey" ];
 
   // Ways to connect to a node
   repeated string addresses = 2 [ json_name = "addresses" ];
 
-  // Administrator-defined Attributes of the FrostFS Storage Node.
+  // Administrator-defined Attributes of the NeoFS Storage Node.
   //
   // `Attribute` is a Key-Value metadata pair. Key name must be a valid UTF-8
   // string. Value can't be empty.
   //
   // Attributes can be constructed into a chain of attributes: any attribute can
   // have a parent attribute and a child attribute (except the first and the
-  // last one). A string representation of the chain of attributes in FrostFS
+  // last one). A string representation of the chain of attributes in NeoFS
   // Storage Node configuration uses ":" and "/" symbols, e.g.:
   //
-  //        `FrostFS_NODE_ATTRIBUTE_1=key1:val1/key2:val2`
+  //        `NEOFS_NODE_ATTRIBUTE_1=key1:val1/key2:val2`
   //
   // Therefore the string attribute representation in the Node configuration
   // must use "\:", "\/" and "\\" escaped symbols if any of them appears in an
@@ -201,8 +198,8 @@ message NodeInfo {
   //   [ISO 3166-2](https://en.wikipedia.org/wiki/ISO_3166-2). Calculated
   //   automatically from `UN-LOCODE` attribute.
   // * Continent \
-  //   Node's continent name according to the [Seven-Continent
+  //   Node's continent name according to the [Seven-Continent model]
-  //   model](https://en.wikipedia.org/wiki/Continent#Number). Calculated
+  //   (https://en.wikipedia.org/wiki/Continent#Number). Calculated
   //   automatically from `UN-LOCODE` attribute.
   // * ExternalAddr
   //   Node's preferred way for communications with external clients.
@@ -210,7 +207,7 @@ message NodeInfo {
   //   Must contain a comma-separated list of multi-addresses.
   //
   // For detailed description of each well-known attribute please see the
-  // corresponding section in FrostFS Technical Specification.
+  // corresponding section in NeoFS Technical Specification.
   message Attribute {
     // Key of the node attribute
     string key = 1 [ json_name = "key" ];
@@ -222,13 +219,13 @@ message NodeInfo {
     // `Country`.
     repeated string parents = 3 [ json_name = "parents" ];
   }
-  // Carries list of the FrostFS node attributes in a key-value form. Key name
+  // Carries list of the NeoFS node attributes in a key-value form. Key name
   // must be a node-unique valid UTF-8 string. Value can't be empty. NodeInfo
   // structures with duplicated attribute names or attributes with empty values
   // will be considered invalid.
   repeated Attribute attributes = 3 [ json_name = "attributes" ];
 
-  // Represents the enumeration of various states of the FrostFS node.
+  // Represents the enumeration of various states of the NeoFS node.
   enum State {
     // Unknown state
     UNSPECIFIED = 0;
@@ -243,7 +240,7 @@ message NodeInfo {
     MAINTENANCE = 3;
   }
 
-  // Carries state of the FrostFS node
+  // Carries state of the NeoFS node
   State state = 4 [ json_name = "state" ];
 }
 
@@ -256,7 +253,7 @@ message Netmap {
   repeated NodeInfo nodes = 2 [ json_name = "nodes" ];
 }
 
-// FrostFS network configuration
+// NeoFS network configuration
 message NetworkConfig {
   // Single configuration parameter. Key MUST be network-unique.
   //
@@ -275,7 +272,7 @@ message NetworkConfig {
   //   Fee paid for container creation by the container owner.
   //   Value: little-endian integer. Default: 0.
   // - **EpochDuration** \
-  //   FrostFS epoch duration measured in Sidechain blocks.
+  //   NeoFS epoch duration measured in Sidechain blocks.
   //   Value: little-endian integer. Default: 0.
   // - **HomomorphicHashingDisabled** \
   //   Flag of disabling the homomorphic hashing of objects' payload.
@@ -287,39 +284,8 @@ message NetworkConfig {
   //   Flag allowing setting the MAINTENANCE state to storage nodes.
   //   Value: true if any byte != 0. Default: false.
   // - **MaxObjectSize** \
-  //   Maximum size of physically stored FrostFS object measured in bytes.
+  //   Maximum size of physically stored NeoFS object measured in bytes.
   //   Value: little-endian integer. Default: 0.
-  //
-  //   This value refers to the maximum size of a **physically** stored object
-  //   in FrostFS. However, from a user's perspective, the **logical** size of a
-  //   stored object can be significantly larger. The relationship between the
-  //   physical and logical object sizes is governed by the following formula
-  //
-  //   ```math
-  //   \mathrm{Stored\ Object\ Size} \le
-  //   \frac{
-  //     \left(\mathrm{Max\ Object\ Size}\right)^2
-  //   }{
-  //     \mathrm{Object\ ID\ Size}
-  //   }
-  //   ```
-  //
-  //   This arises from the fact that a tombstone, also being an object, stores
-  //   the IDs of inhumed objects and cannot be divided into smaller objects,
-  //   thus having an upper limit for its size.
-  //
-  //   For example, if:
-  //   * Max Object Size Size = 64 MiB;
-  //   * Object ID Size = 32 B;
-  //
-  //   then:
-  //   ```math
-  //     \mathrm{Stored\ Object\ Size} \le
-  //     \frac{\left(64\ \mathrm{MiB}\right)^2}{32\ \mathrm{B}} =
-  //     \frac{2^{52}}{2^5}\ \mathrm{B} =
-  //     2^{47}\ \mathrm{B} =
-  //     128\ \mathrm{TiB}
-  //   ```
   // - **WithdrawFee** \
   //   Fee paid for withdrawal of funds paid by the account owner.
   //   Value: little-endian integer. Default: 0.
@@ -340,18 +306,18 @@ message NetworkConfig {
   repeated Parameter parameters = 1 [ json_name = "parameters" ];
 }
 
-// Information about FrostFS network
+// Information about NeoFS network
 message NetworkInfo {
-  // Number of the current epoch in the FrostFS network
+  // Number of the current epoch in the NeoFS network
   uint64 current_epoch = 1 [ json_name = "currentEpoch" ];
 
-  // Magic number of the sidechain of the FrostFS network
+  // Magic number of the sidechain of the NeoFS network
   uint64 magic_number = 2 [ json_name = "magicNumber" ];
 
-  // MillisecondsPerBlock network parameter of the sidechain of the FrostFS
+  // MillisecondsPerBlock network parameter of the sidechain of the NeoFS
   // network
   int64 ms_per_block = 3 [ json_name = "msPerBlock" ];
 
-  // FrostFS network configuration
+  // NeoFS network configuration
   NetworkConfig network_config = 4 [ json_name = "networkConfig" ];
 }

object/service.proto

@@ -151,7 +151,7 @@ service ObjectService {
   rpc Head(HeadRequest) returns (HeadResponse);
 
   // Search objects in container. Search query allows to match by Object
-  // Header's filed values. Please see the corresponding FrostFS Technical
+  // Header's filed values. Please see the corresponding NeoFS Technical
   // Specification section for more details.
   //
   // Extended headers can change `Search` behaviour:
@@ -285,20 +285,16 @@ service ObjectService {
   rpc PutSingle(PutSingleRequest) returns (PutSingleResponse);
 
   // Patch the object. Request uses gRPC stream. First message must set
-  // the address of the object that is going to get patched. If the object's
+  // the address of the object that is going to get patched. If the object's attributes
-  // attributes are patched, then these attrubutes must be set only within the
+  // are patched, then these attrubutes must be set only within the first stream message.
-  // first stream message.
   //
-  // If the patch request is performed by NOT the object's owner but if the
+  // If the patch request is performed by NOT the object's owner but if the actor has the permission
-  // actor has the permission to perform the patch, then `OwnerID` of the object
+  // to perform the patch, then `OwnerID` of the object is changed. In this case the object's owner
-  // is changed. In this case the object's owner loses the object's ownership
+  // loses the object's ownership after the patch request is successfully done.
-  // after the patch request is successfully done.
   //
-  // As objects are content-addressable the patching causes new object ID
+  // As objects are content-addressable the patching causes new object ID generation for the patched object.
-  // generation for the patched object. This object id is set witihn
+  // This object id is set witihn `PatchResponse`. But the object id may remain unchanged in such cases: 
-  // `PatchResponse`. But the object id may remain unchanged in such cases:
+  // 1. The chunk of the applying patch contains the same value as the object's payload within the same range;
-  // 1. The chunk of the applying patch contains the same value as the object's
-  // payload within the same range;
   // 2. The patch that reverts the changes applied by preceding patch;
   // 3. The application of the same patches for the object a few times.
   //
@@ -633,8 +629,8 @@ message SearchRequest {
     // * $Object:split.splitID \
     //   16 byte UUIDv4 used to identify the split object hierarchy parts
     // * $Object:ec.parent \
-    //   If the object is stored according to EC policy, then ec_parent
+    //   If the object is stored according to EC policy, then ec_parent attribute
-    //   attribute is set to return an id list of all related EC chunks.
+    //   is set to return an id list of all related EC chunks.
     //
     // There are some well-known filter aliases to match objects by certain
     // properties:
@@ -874,29 +870,25 @@ message PatchRequest {
     // The address of the object that is requested to get patched.
     neo.fs.v2.refs.Address address = 1;
 
-    // New attributes for the object. See `replace_attributes` flag usage to
+    // New attributes for the object. See `replace_attributes` flag usage to define how
-    // define how new attributes should be set.
+    // new attributes should be set.
     repeated neo.fs.v2.object.Header.Attribute new_attributes = 2;
 
-    // If this flag is set, then the object's attributes will be entirely
+    // If this flag is set, then the object's attributes will be entirely replaced by `new_attributes` list.
-    // replaced by `new_attributes` list. The empty `new_attributes` list with
+    // The empty `new_attributes` list with `replace_attributes = true` just resets attributes list for the object.
-    // `replace_attributes = true` just resets attributes list for the object.
     //
-    // Default `false` value for this flag means the attributes will be just
+    // Default `false` value for this flag means the attributes will be just merged. If the incoming `new_attributes`
-    // merged. If the incoming `new_attributes` list contains already existing
+    // list contains already existing key, then it just replaces it while merging the lists. 
-    // key, then it just replaces it while merging the lists.
     bool replace_attributes = 3;
 
     // The patch for the object's payload. 
     message Patch {
-      // The range of the source object for which the payload is replaced by the
+      // The range of the source object for which the payload is replaced by the patch's chunk.
-      // patch's chunk. If the range's `length = 0`, then the patch's chunk is
+      // If the range's `length = 0`, then the patch's chunk is just appended to the original payload
-      // just appended to the original payload starting from the `offest`
+      // starting from the `offest` without any replace.
-      // without any replace.
       Range source_range = 1;
 
-      // The chunk that is being appended to or that replaces the original
+      // The chunk that is being appended to or that replaces the original payload on the given range.
-      // payload on the given range.
       bytes chunk = 2;
     }
 
@@ -921,8 +913,8 @@ message PatchRequest {
 message PatchResponse {
   // PATCH response body
   message Body {
-    // The object ID of the saved patched object.
+      // The object ID of the saved patched object.
-    neo.fs.v2.refs.ObjectID object_id = 1;
+      neo.fs.v2.refs.ObjectID object_id = 1;
   }
 
   // Body for patch response message.
@@ -932,8 +924,7 @@ message PatchResponse {
   // message transport and does not affect request execution.
   neo.fs.v2.session.ResponseMetaHeader meta_header = 2;
 
-  // Carries response verification information. This header is used to
+  // Carries response verification information. This header is used to authenticate
-  // authenticate the nodes of the message route and check the correctness of
+  // the nodes of the message route and check the correctness of transmission.
-  // transmission.
   neo.fs.v2.session.ResponseVerificationHeader verify_header = 3;
 }

object/types.proto

@@ -155,7 +155,7 @@ message Header {
   //   MIME Content Type of object's payload
   //
   // For detailed description of each well-known attribute please see the
-  // corresponding section in FrostFS Technical Specification.
+  // corresponding section in NeoFS Technical Specification.
   message Attribute {
     // string key to the object attribute
     string key = 1 [ json_name = "key" ];
@@ -209,15 +209,13 @@ message Header {
     // Chunk of a parent header.
     bytes header = 5 [ json_name = "header" ];
     // As the origin object is EC-splitted its identifier is known to all
-    // chunks as parent. But parent itself can be a part of Split (does not
+    // chunks as parent. But parent itself can be a part of Split (does not relate to EC-split).
-    // relate to EC-split). In this case parent_split_id should be set.
+    // In this case parent_split_id should be set.
     bytes parent_split_id = 6 [ json_name = "parentSplitID" ];
-    // EC-parent's parent ID. parent_split_parent_id is set if EC-parent,
+    // EC-parent's parent ID. parent_split_parent_id is set if EC-parent, itself, is a part of Split and
-    // itself, is a part of Split and if an object ID of its parent is
+    // if an object ID of its parent is presented. The field allows to determine how EC-chunk is placed
-    // presented. The field allows to determine how EC-chunk is placed in Split
+    // in Split hierarchy.
-    // hierarchy.
+    neo.fs.v2.refs.ObjectID parent_split_parent_id = 7 [ json_name = "parentSplitParentID" ];
-    neo.fs.v2.refs.ObjectID parent_split_parent_id = 7
-        [ json_name = "parentSplitParentID" ];
     // EC parent's attributes.
     repeated Attribute parent_attributes = 8 [ json_name = "parentAttributes" ];
   }

proto-docs/accounting.md

@@ -35,11 +35,11 @@
 <a name="neo.fs.v2.accounting.AccountingService"></a>
 
 ### Service "neo.fs.v2.accounting.AccountingService"
-Accounting service provides methods for interaction with FrostFS sidechain
+Accounting service provides methods for interaction with NeoFS sidechain via
-via other FrostFS nodes to get information about the account balance. Deposit
+other NeoFS nodes to get information about the account balance. Deposit and
-and Withdraw operations can't be implemented here, as they require Mainnet
+Withdraw operations can't be implemented here, as they require Mainnet NeoFS
-FrostFS smart contract invocation. Transfer operations between internal
+smart contract invocation. Transfer operations between internal NeoFS
-FrostFS accounts are possible if both use the same token type.
+accounts are possible if both use the same token type.
 
 ```
 rpc Balance(BalanceRequest) returns (BalanceResponse);
@@ -48,7 +48,7 @@ rpc Balance(BalanceRequest) returns (BalanceResponse);
 
 #### Method Balance
 
-Returns the amount of funds in GAS token for the requested FrostFS account.
+Returns the amount of funds in GAS token for the requested NeoFS account.
 
 Statuses:
 - **OK** (0, SECTION_SUCCESS):
@@ -78,9 +78,9 @@ BalanceRequest message
 
 ### Message BalanceRequest.Body
 To indicate the account for which the balance is requested, its identifier
-is used. It can be any existing account in FrostFS sidechain `Balance`
+is used. It can be any existing account in NeoFS sidechain `Balance` smart
-smart contract. If omitted, client implementation MUST set it to the
+contract. If omitted, client implementation MUST set it to the request's
-request's signer `OwnerID`.
+signer `OwnerID`.
 
 
 | Field | Type | Label | Description |
@@ -131,7 +131,7 @@ rounding.
 <a name="neo.fs.v2.accounting.Decimal"></a>
 
 ### Message Decimal
-Standard floating point data type can't be used in FrostFS due to inexactness
+Standard floating point data type can't be used in NeoFS due to inexactness
 of the result when doing lots of small number operations. To solve the lost
 precision issue, special `Decimal` format is used for monetary computations.
 
@@ -170,3 +170,4 @@ description.
 | <a name="bool" /> bool |  | bool | boolean | boolean |
 | <a name="string" /> string | A string must always contain UTF-8 encoded or 7-bit ASCII text. | string | String | str/unicode |
 | <a name="bytes" /> bytes | May contain any arbitrary sequence of bytes. | string | ByteString | str |
+

proto-docs/acl.md

@@ -71,12 +71,11 @@ Deprecated: eACL tables are no longer relevant - `APEOverrides` should be used i
 
 ### Message BearerToken.Body.APEOverride
 APEOverride is the list of APE chains defined for a target.
-These chains are meant to serve as overrides to the already defined (or
+These chains are meant to serve as overrides to the already defined (or even undefined)
-even undefined) APE chains for the target (see contract `Policy`).
+APE chains for the target (see contract `Policy`).
 
-The server-side processing of the bearer token with set APE overrides
+The server-side processing of the bearer token with set APE overrides must verify if a client is permitted
-must verify if a client is permitted to override chains for the target,
+to override chains for the target, preventing unauthorized access through the APE mechanism.
-preventing unauthorized access through the APE mechanism.
 
 
 | Field | Type | Label | Description |
@@ -107,7 +106,7 @@ Describes a single eACL rule.
 
 | Field | Type | Label | Description |
 | ----- | ---- | ----- | ----------- |
-| operation | [Operation](#neo.fs.v2.acl.Operation) |  | FrostFS request Verb to match |
+| operation | [Operation](#neo.fs.v2.acl.Operation) |  | NeoFS request Verb to match |
 | action | [Action](#neo.fs.v2.acl.Action) |  | Rule execution result. Either allows or denies access if filters match. |
 | filters | [EACLRecord.Filter](#neo.fs.v2.acl.EACLRecord.Filter) | repeated | List of filters to match and see if rule is applicable |
 | targets | [EACLRecord.Target](#neo.fs.v2.acl.EACLRecord.Target) | repeated | List of target subjects to apply ACL rule to |
@@ -175,7 +174,7 @@ keys to match.
 Extended ACL rules table. A list of ACL rules defined additionally to Basic
 ACL. Extended ACL rules can be attached to a container and can be updated
 or may be defined in `BearerToken` structure. Please see the corresponding
-FrostFS Technical Specification section for detailed description.
+NeoFS Technical Specification section for detailed description.
 
 
 | Field | Type | Label | Description |
@@ -211,7 +210,7 @@ Enumeration of possible sources of Headers to apply filters.
 | HEADER_UNSPECIFIED | 0 | Unspecified header, default value. |
 | REQUEST | 1 | Filter request headers |
 | OBJECT | 2 | Filter object headers |
-| SERVICE | 3 | Filter service headers. These are not processed by FrostFS nodes and exist for service use only. |
+| SERVICE | 3 | Filter service headers. These are not processed by NeoFS nodes and exist for service use only. |
 
 
 
@@ -283,3 +282,4 @@ Target role of the access control rule in access control list.
 | <a name="bool" /> bool |  | bool | boolean | boolean |
 | <a name="string" /> string | A string must always contain UTF-8 encoded or 7-bit ASCII text. | string | String | str/unicode |
 | <a name="bytes" /> bytes | May contain any arbitrary sequence of bytes. | string | ByteString | str |
+

proto-docs/ape.md

@@ -72,8 +72,8 @@ TargetType is a type target to which a rule chain is defined.
 | ----------- | ----- | -------- | --------- | ----------- |
 | <a name="double" /> double |  | double | double | float |
 | <a name="float" /> float |  | float | float | float |
-| <a name="int32" /> int32 | Uses variable-length encoding. Inefficient for encoding negative numbers – if your field is likely to have negative values, use sint32 instead. | int32 | int | int |
+| <a name="int32" /> int32 | Uses variable-length encoding. Inefficient for encoding negative numbers - if your field is likely to have negative values, use sint32 instead. | int32 | int | int |
-| <a name="int64" /> int64 | Uses variable-length encoding. Inefficient for encoding negative numbers – if your field is likely to have negative values, use sint64 instead. | int64 | long | int/long |
+| <a name="int64" /> int64 | Uses variable-length encoding. Inefficient for encoding negative numbers - if your field is likely to have negative values, use sint64 instead. | int64 | long | int/long |
 | <a name="uint32" /> uint32 | Uses variable-length encoding. | uint32 | int | int/long |
 | <a name="uint64" /> uint64 | Uses variable-length encoding. | uint64 | long | int/long |
 | <a name="sint32" /> sint32 | Uses variable-length encoding. Signed int value. These more efficiently encode negative numbers than regular int32s. | int32 | int | int |
@@ -85,3 +85,4 @@ TargetType is a type target to which a rule chain is defined.
 | <a name="bool" /> bool |  | bool | boolean | boolean |
 | <a name="string" /> string | A string must always contain UTF-8 encoded or 7-bit ASCII text. | string | String | str/unicode |
 | <a name="bytes" /> bytes | May contain any arbitrary sequence of bytes. | string | ByteString | str |
+

proto-docs/apemanager.md

@@ -267,3 +267,4 @@ operation could not be performed is an error returning to a client.
 | <a name="bool" /> bool |  | bool | boolean | boolean |
 | <a name="string" /> string | A string must always contain UTF-8 encoded or 7-bit ASCII text. | string | String | str/unicode |
 | <a name="bytes" /> bytes | May contain any arbitrary sequence of bytes. | string | ByteString | str |
+

proto-docs/container.md

@@ -8,10 +8,19 @@
       - [ContainerService](#neo.fs.v2.container.ContainerService)
     
   - Messages
+      - [AnnounceUsedSpaceRequest](#neo.fs.v2.container.AnnounceUsedSpaceRequest)
+      - [AnnounceUsedSpaceRequest.Body](#neo.fs.v2.container.AnnounceUsedSpaceRequest.Body)
+      - [AnnounceUsedSpaceRequest.Body.Announcement](#neo.fs.v2.container.AnnounceUsedSpaceRequest.Body.Announcement)
+      - [AnnounceUsedSpaceResponse](#neo.fs.v2.container.AnnounceUsedSpaceResponse)
+      - [AnnounceUsedSpaceResponse.Body](#neo.fs.v2.container.AnnounceUsedSpaceResponse.Body)
       - [DeleteRequest](#neo.fs.v2.container.DeleteRequest)
       - [DeleteRequest.Body](#neo.fs.v2.container.DeleteRequest.Body)
       - [DeleteResponse](#neo.fs.v2.container.DeleteResponse)
       - [DeleteResponse.Body](#neo.fs.v2.container.DeleteResponse.Body)
+      - [GetExtendedACLRequest](#neo.fs.v2.container.GetExtendedACLRequest)
+      - [GetExtendedACLRequest.Body](#neo.fs.v2.container.GetExtendedACLRequest.Body)
+      - [GetExtendedACLResponse](#neo.fs.v2.container.GetExtendedACLResponse)
+      - [GetExtendedACLResponse.Body](#neo.fs.v2.container.GetExtendedACLResponse.Body)
       - [GetRequest](#neo.fs.v2.container.GetRequest)
       - [GetRequest.Body](#neo.fs.v2.container.GetRequest.Body)
       - [GetResponse](#neo.fs.v2.container.GetResponse)
@@ -24,6 +33,10 @@
       - [PutRequest.Body](#neo.fs.v2.container.PutRequest.Body)
       - [PutResponse](#neo.fs.v2.container.PutResponse)
       - [PutResponse.Body](#neo.fs.v2.container.PutResponse.Body)
+      - [SetExtendedACLRequest](#neo.fs.v2.container.SetExtendedACLRequest)
+      - [SetExtendedACLRequest.Body](#neo.fs.v2.container.SetExtendedACLRequest.Body)
+      - [SetExtendedACLResponse](#neo.fs.v2.container.SetExtendedACLResponse)
+      - [SetExtendedACLResponse.Body](#neo.fs.v2.container.SetExtendedACLResponse.Body)
     
 
 - [container/types.proto](#container/types.proto)
@@ -49,8 +62,8 @@
 
 ### Service "neo.fs.v2.container.ContainerService"
 `ContainerService` provides API to interact with `Container` smart contract
-in FrostFS sidechain via other FrostFS nodes. All of those actions can be
+in NeoFS sidechain via other NeoFS nodes. All of those actions can be done
-done equivalently by directly issuing transactions and RPC calls to sidechain
+equivalently by directly issuing transactions and RPC calls to sidechain
 nodes.
 
 ```
@@ -58,6 +71,9 @@ rpc Put(PutRequest) returns (PutResponse);
 rpc Delete(DeleteRequest) returns (DeleteResponse);
 rpc Get(GetRequest) returns (GetResponse);
 rpc List(ListRequest) returns (ListResponse);
+rpc SetExtendedACL(SetExtendedACLRequest) returns (SetExtendedACLResponse);
+rpc GetExtendedACL(GetExtendedACLRequest) returns (GetExtendedACLResponse);
+rpc AnnounceUsedSpace(AnnounceUsedSpaceRequest) returns (AnnounceUsedSpaceResponse);
 
 ```
 
@@ -125,9 +141,114 @@ Statuses:
 | Name | Input | Output |
 | ---- | ----- | ------ |
 | List | [ListRequest](#neo.fs.v2.container.ListRequest) | [ListResponse](#neo.fs.v2.container.ListResponse) |
+#### Method SetExtendedACL
+
+Invokes 'SetEACL' method of 'Container` smart contract and returns response
+immediately. After one more block in sidechain, changes in an Extended ACL
+are added into smart contract storage.
+
+Statuses:
+- **OK** (0, SECTION_SUCCESS): \
+  request to save container eACL has been sent to the sidechain;
+- Common failures (SECTION_FAILURE_COMMON);
+- **CONTAINER_ACCESS_DENIED** (3074, SECTION_CONTAINER): \
+  set container eACL access denied.
+
+| Name | Input | Output |
+| ---- | ----- | ------ |
+| SetExtendedACL | [SetExtendedACLRequest](#neo.fs.v2.container.SetExtendedACLRequest) | [SetExtendedACLResponse](#neo.fs.v2.container.SetExtendedACLResponse) |
+#### Method GetExtendedACL
+
+Returns Extended ACL table and signature from `Container` smart contract
+storage.
+
+Statuses:
+- **OK** (0, SECTION_SUCCESS): \
+  container eACL has been successfully read;
+- Common failures (SECTION_FAILURE_COMMON);
+- **CONTAINER_NOT_FOUND** (3072, SECTION_CONTAINER): \
+  container not found;
+- **EACL_NOT_FOUND** (3073, SECTION_CONTAINER): \
+  eACL table not found;
+- **CONTAINER_ACCESS_DENIED** (3074, SECTION_CONTAINER): \
+  access to container eACL is denied.
+
+| Name | Input | Output |
+| ---- | ----- | ------ |
+| GetExtendedACL | [GetExtendedACLRequest](#neo.fs.v2.container.GetExtendedACLRequest) | [GetExtendedACLResponse](#neo.fs.v2.container.GetExtendedACLResponse) |
+#### Method AnnounceUsedSpace
+
+Announces the space values used by the container for P2P synchronization.
+
+Statuses:
+- **OK** (0, SECTION_SUCCESS): \
+  estimation of used space has been successfully announced;
+- Common failures (SECTION_FAILURE_COMMON).
+
+| Name | Input | Output |
+| ---- | ----- | ------ |
+| AnnounceUsedSpace | [AnnounceUsedSpaceRequest](#neo.fs.v2.container.AnnounceUsedSpaceRequest) | [AnnounceUsedSpaceResponse](#neo.fs.v2.container.AnnounceUsedSpaceResponse) |
  <!-- end services -->
 
 
+<a name="neo.fs.v2.container.AnnounceUsedSpaceRequest"></a>
+
+### Message AnnounceUsedSpaceRequest
+Announce container used space
+
+
+| Field | Type | Label | Description |
+| ----- | ---- | ----- | ----------- |
+| body | [AnnounceUsedSpaceRequest.Body](#neo.fs.v2.container.AnnounceUsedSpaceRequest.Body) |  | Body of announce used space request message. |
+| meta_header | [neo.fs.v2.session.RequestMetaHeader](#neo.fs.v2.session.RequestMetaHeader) |  | Carries request meta information. Header data is used only to regulate message transport and does not affect request execution. |
+| verify_header | [neo.fs.v2.session.RequestVerificationHeader](#neo.fs.v2.session.RequestVerificationHeader) |  | Carries request verification information. This header is used to authenticate the nodes of the message route and check the correctness of transmission. |
+
+
+<a name="neo.fs.v2.container.AnnounceUsedSpaceRequest.Body"></a>
+
+### Message AnnounceUsedSpaceRequest.Body
+Container used space announcement body.
+
+
+| Field | Type | Label | Description |
+| ----- | ---- | ----- | ----------- |
+| announcements | [AnnounceUsedSpaceRequest.Body.Announcement](#neo.fs.v2.container.AnnounceUsedSpaceRequest.Body.Announcement) | repeated | List of announcements. If nodes share several containers, announcements are transferred in a batch. |
+
+
+<a name="neo.fs.v2.container.AnnounceUsedSpaceRequest.Body.Announcement"></a>
+
+### Message AnnounceUsedSpaceRequest.Body.Announcement
+Announcement contains used space information for a single container.
+
+
+| Field | Type | Label | Description |
+| ----- | ---- | ----- | ----------- |
+| epoch | [uint64](#uint64) |  | Epoch number for which the container size estimation was produced. |
+| container_id | [neo.fs.v2.refs.ContainerID](#neo.fs.v2.refs.ContainerID) |  | Identifier of the container. |
+| used_space | [uint64](#uint64) |  | Used space is a sum of object payload sizes of a specified container, stored in the node. It must not include inhumed objects. |
+
+
+<a name="neo.fs.v2.container.AnnounceUsedSpaceResponse"></a>
+
+### Message AnnounceUsedSpaceResponse
+Announce container used space
+
+
+| Field | Type | Label | Description |
+| ----- | ---- | ----- | ----------- |
+| body | [AnnounceUsedSpaceResponse.Body](#neo.fs.v2.container.AnnounceUsedSpaceResponse.Body) |  | Body of announce used space response message. |
+| meta_header | [neo.fs.v2.session.ResponseMetaHeader](#neo.fs.v2.session.ResponseMetaHeader) |  | Carries response meta information. Header data is used only to regulate message transport and does not affect request execution. |
+| verify_header | [neo.fs.v2.session.ResponseVerificationHeader](#neo.fs.v2.session.ResponseVerificationHeader) |  | Carries response verification information. This header is used to authenticate the nodes of the message route and check the correctness of transmission. |
+
+
+<a name="neo.fs.v2.container.AnnounceUsedSpaceResponse.Body"></a>
+
+### Message AnnounceUsedSpaceResponse.Body
+`AnnounceUsedSpaceResponse` has an empty body because announcements are
+one way communication.
+
+
+
 <a name="neo.fs.v2.container.DeleteRequest"></a>
 
 ### Message DeleteRequest
@@ -151,7 +272,7 @@ smart contract, so signing algorithm must be supported by NeoVM.
 
 | Field | Type | Label | Description |
 | ----- | ---- | ----- | ----------- |
-| container_id | [neo.fs.v2.refs.ContainerID](#neo.fs.v2.refs.ContainerID) |  | Identifier of the container to delete from FrostFS |
+| container_id | [neo.fs.v2.refs.ContainerID](#neo.fs.v2.refs.ContainerID) |  | Identifier of the container to delete from NeoFS |
 | signature | [neo.fs.v2.refs.SignatureRFC6979](#neo.fs.v2.refs.SignatureRFC6979) |  | `ContainerID` signed with the container owner's key according to RFC-6979. |
 
 
@@ -177,6 +298,58 @@ and done via consensus in Inner Ring nodes.
 
 
 
+<a name="neo.fs.v2.container.GetExtendedACLRequest"></a>
+
+### Message GetExtendedACLRequest
+Get Extended ACL
+
+
+| Field | Type | Label | Description |
+| ----- | ---- | ----- | ----------- |
+| body | [GetExtendedACLRequest.Body](#neo.fs.v2.container.GetExtendedACLRequest.Body) |  | Body of get extended acl request message. |
+| meta_header | [neo.fs.v2.session.RequestMetaHeader](#neo.fs.v2.session.RequestMetaHeader) |  | Carries request meta information. Header data is used only to regulate message transport and does not affect request execution. |
+| verify_header | [neo.fs.v2.session.RequestVerificationHeader](#neo.fs.v2.session.RequestVerificationHeader) |  | Carries request verification information. This header is used to authenticate the nodes of the message route and check the correctness of transmission. |
+
+
+<a name="neo.fs.v2.container.GetExtendedACLRequest.Body"></a>
+
+### Message GetExtendedACLRequest.Body
+Get Extended ACL request body
+
+
+| Field | Type | Label | Description |
+| ----- | ---- | ----- | ----------- |
+| container_id | [neo.fs.v2.refs.ContainerID](#neo.fs.v2.refs.ContainerID) |  | Identifier of the container having Extended ACL |
+
+
+<a name="neo.fs.v2.container.GetExtendedACLResponse"></a>
+
+### Message GetExtendedACLResponse
+Get Extended ACL
+
+
+| Field | Type | Label | Description |
+| ----- | ---- | ----- | ----------- |
+| body | [GetExtendedACLResponse.Body](#neo.fs.v2.container.GetExtendedACLResponse.Body) |  | Body of get extended acl response message. |
+| meta_header | [neo.fs.v2.session.ResponseMetaHeader](#neo.fs.v2.session.ResponseMetaHeader) |  | Carries response meta information. Header data is used only to regulate message transport and does not affect request execution. |
+| verify_header | [neo.fs.v2.session.ResponseVerificationHeader](#neo.fs.v2.session.ResponseVerificationHeader) |  | Carries response verification information. This header is used to authenticate the nodes of the message route and check the correctness of transmission. |
+
+
+<a name="neo.fs.v2.container.GetExtendedACLResponse.Body"></a>
+
+### Message GetExtendedACLResponse.Body
+Get Extended ACL Response body can be empty if the requested container does
+not have Extended ACL Table attached or Extended ACL has not been allowed
+at the time of container creation.
+
+
+| Field | Type | Label | Description |
+| ----- | ---- | ----- | ----------- |
+| eacl | [neo.fs.v2.acl.EACLTable](#neo.fs.v2.acl.EACLTable) |  | Extended ACL requested, if available |
+| signature | [neo.fs.v2.refs.SignatureRFC6979](#neo.fs.v2.refs.SignatureRFC6979) |  | Signature of stable-marshalled Extended ACL according to RFC-6979. |
+| session_token | [neo.fs.v2.session.SessionToken](#neo.fs.v2.session.SessionToken) |  | Session token if Extended ACL was set within a session |
+
+
 <a name="neo.fs.v2.container.GetRequest"></a>
 
 ### Message GetRequest
@@ -279,7 +452,7 @@ List containers response body.
 <a name="neo.fs.v2.container.PutRequest"></a>
 
 ### Message PutRequest
-New FrostFS Container creation request
+New NeoFS Container creation request
 
 
 | Field | Type | Label | Description |
@@ -301,14 +474,14 @@ additional signature checks.
 
 | Field | Type | Label | Description |
 | ----- | ---- | ----- | ----------- |
-| container | [Container](#neo.fs.v2.container.Container) |  | Container structure to register in FrostFS |
+| container | [Container](#neo.fs.v2.container.Container) |  | Container structure to register in NeoFS |
 | signature | [neo.fs.v2.refs.SignatureRFC6979](#neo.fs.v2.refs.SignatureRFC6979) |  | Signature of a stable-marshalled container according to RFC-6979. |
 
 
 <a name="neo.fs.v2.container.PutResponse"></a>
 
 ### Message PutResponse
-New FrostFS Container creation response
+New NeoFS Container creation response
 
 
 | Field | Type | Label | Description |
@@ -331,6 +504,54 @@ returned here to make sure everything has been done as expected.
 | ----- | ---- | ----- | ----------- |
 | container_id | [neo.fs.v2.refs.ContainerID](#neo.fs.v2.refs.ContainerID) |  | Unique identifier of the newly created container |
 
+
+<a name="neo.fs.v2.container.SetExtendedACLRequest"></a>
+
+### Message SetExtendedACLRequest
+Set Extended ACL
+
+
+| Field | Type | Label | Description |
+| ----- | ---- | ----- | ----------- |
+| body | [SetExtendedACLRequest.Body](#neo.fs.v2.container.SetExtendedACLRequest.Body) |  | Body of set extended acl request message. |
+| meta_header | [neo.fs.v2.session.RequestMetaHeader](#neo.fs.v2.session.RequestMetaHeader) |  | Carries request meta information. Header data is used only to regulate message transport and does not affect request execution. |
+| verify_header | [neo.fs.v2.session.RequestVerificationHeader](#neo.fs.v2.session.RequestVerificationHeader) |  | Carries request verification information. This header is used to authenticate the nodes of the message route and check the correctness of transmission. |
+
+
+<a name="neo.fs.v2.container.SetExtendedACLRequest.Body"></a>
+
+### Message SetExtendedACLRequest.Body
+Set Extended ACL request body does not have separate `ContainerID`
+reference. It will be taken from `EACLTable.container_id` field.
+
+
+| Field | Type | Label | Description |
+| ----- | ---- | ----- | ----------- |
+| eacl | [neo.fs.v2.acl.EACLTable](#neo.fs.v2.acl.EACLTable) |  | Extended ACL table to set for the container |
+| signature | [neo.fs.v2.refs.SignatureRFC6979](#neo.fs.v2.refs.SignatureRFC6979) |  | Signature of stable-marshalled Extended ACL table according to RFC-6979. |
+
+
+<a name="neo.fs.v2.container.SetExtendedACLResponse"></a>
+
+### Message SetExtendedACLResponse
+Set Extended ACL
+
+
+| Field | Type | Label | Description |
+| ----- | ---- | ----- | ----------- |
+| body | [SetExtendedACLResponse.Body](#neo.fs.v2.container.SetExtendedACLResponse.Body) |  | Body of set extended acl response message. |
+| meta_header | [neo.fs.v2.session.ResponseMetaHeader](#neo.fs.v2.session.ResponseMetaHeader) |  | Carries response meta information. Header data is used only to regulate message transport and does not affect request execution. |
+| verify_header | [neo.fs.v2.session.ResponseVerificationHeader](#neo.fs.v2.session.ResponseVerificationHeader) |  | Carries response verification information. This header is used to authenticate the nodes of the message route and check the correctness of transmission. |
+
+
+<a name="neo.fs.v2.container.SetExtendedACLResponse.Body"></a>
+
+### Message SetExtendedACLResponse.Body
+`SetExtendedACLResponse` has an empty body because the operation is
+asynchronous and the update should be reflected in `Container` smart
+contract's storage after next block is issued in sidechain.
+
+
  <!-- end messages -->
 
  <!-- end enums -->
@@ -391,7 +612,7 @@ There are some "well-known" attributes affecting system behaviour:
   (`__NEOFS__DISABLE_HOMOMORPHIC_HASHING` is deprecated) \
   Disables homomorphic hashing for the container if the value equals "true"
   string. Any other values are interpreted as missing attribute. Container
-  could be accepted in a FrostFS network only if the global network hashing
+  could be accepted in a NeoFS network only if the global network hashing
   configuration value corresponds with that attribute's value. After
   container inclusion, network setting is ignored.
 
@@ -433,3 +654,4 @@ And some well-known attributes used by applications only:
 | <a name="bool" /> bool |  | bool | boolean | boolean |
 | <a name="string" /> string | A string must always contain UTF-8 encoded or 7-bit ASCII text. | string | String | str/unicode |
 | <a name="bytes" /> bytes | May contain any arbitrary sequence of bytes. | string | ByteString | str |
+

proto-docs/lock.md

@@ -61,3 +61,4 @@ a lock object via ObjectService.Delete RPC call.
 | <a name="bool" /> bool |  | bool | boolean | boolean |
 | <a name="string" /> string | A string must always contain UTF-8 encoded or 7-bit ASCII text. | string | String | str/unicode |
 | <a name="bytes" /> bytes | May contain any arbitrary sequence of bytes. | string | ByteString | str |
+

proto-docs/netmap.md

@@ -55,7 +55,7 @@
 `NetmapService` provides methods to work with `Network Map` and the
 information required to build it. The resulting `Network Map` is stored in
 sidechain `Netmap` smart contract, while related information can be obtained
-from other FrostFS nodes.
+from other NeoFS nodes.
 
 ```
 rpc LocalNodeInfo(LocalNodeInfoRequest) returns (LocalNodeInfoResponse);
@@ -83,7 +83,7 @@ information about the server has been successfully read;
 | LocalNodeInfo | [LocalNodeInfoRequest](#neo.fs.v2.netmap.LocalNodeInfoRequest) | [LocalNodeInfoResponse](#neo.fs.v2.netmap.LocalNodeInfoResponse) |
 #### Method NetworkInfo
 
-Read recent information about the FrostFS network.
+Read recent information about the NeoFS network.
 
 Statuses:
 - **OK** (0, SECTION_SUCCESS):
@@ -95,7 +95,7 @@ information about the current network state has been successfully read;
 | NetworkInfo | [NetworkInfoRequest](#neo.fs.v2.netmap.NetworkInfoRequest) | [NetworkInfoResponse](#neo.fs.v2.netmap.NetworkInfoResponse) |
 #### Method NetmapSnapshot
 
-Returns network map snapshot of the current FrostFS epoch.
+Returns network map snapshot of the current NeoFS epoch.
 
 Statuses:
 - **OK** (0, SECTION_SUCCESS):
@@ -149,7 +149,7 @@ Local Node Info, including API Version in use.
 
 | Field | Type | Label | Description |
 | ----- | ---- | ----- | ----------- |
-| version | [neo.fs.v2.refs.Version](#neo.fs.v2.refs.Version) |  | Latest FrostFS API version in use |
+| version | [neo.fs.v2.refs.Version](#neo.fs.v2.refs.Version) |  | Latest NeoFS API version in use |
 | node_info | [NodeInfo](#neo.fs.v2.netmap.NodeInfo) |  | NodeInfo structure with recent information from node itself |
 
 
@@ -287,7 +287,7 @@ Network map structure
 <a name="neo.fs.v2.netmap.NetworkConfig"></a>
 
 ### Message NetworkConfig
-FrostFS network configuration
+NeoFS network configuration
 
 
 | Field | Type | Label | Description |
@@ -315,7 +315,7 @@ System parameters:
   Fee paid for container creation by the container owner.
   Value: little-endian integer. Default: 0.
 - **EpochDuration** \
-  FrostFS epoch duration measured in Sidechain blocks.
+  NeoFS epoch duration measured in Sidechain blocks.
   Value: little-endian integer. Default: 0.
 - **HomomorphicHashingDisabled** \
   Flag of disabling the homomorphic hashing of objects' payload.
@@ -327,39 +327,8 @@ System parameters:
   Flag allowing setting the MAINTENANCE state to storage nodes.
   Value: true if any byte != 0. Default: false.
 - **MaxObjectSize** \
-  Maximum size of physically stored FrostFS object measured in bytes.
+  Maximum size of physically stored NeoFS object measured in bytes.
   Value: little-endian integer. Default: 0.
-
-  This value refers to the maximum size of a **physically** stored object
-  in FrostFS. However, from a user's perspective, the **logical** size of a
-  stored object can be significantly larger. The relationship between the
-  physical and logical object sizes is governed by the following formula
-
-  ```math
-  \mathrm{Stored\ Object\ Size} \le
-  \frac{
-    \left(\mathrm{Max\ Object\ Size}\right)^2
-  }{
-    \mathrm{Object\ ID\ Size}
-  }
-  ```
-
-  This arises from the fact that a tombstone, also being an object, stores
-  the IDs of inhumed objects and cannot be divided into smaller objects,
-  thus having an upper limit for its size.
-
-  For example, if:
-  * Max Object Size Size = 64 MiB;
-  * Object ID Size = 32 B;
-
-  then:
-  ```math
-    \mathrm{Stored\ Object\ Size} \le
-    \frac{\left(64\ \mathrm{MiB}\right)^2}{32\ \mathrm{B}} =
-    \frac{2^{52}}{2^5}\ \mathrm{B} =
-    2^{47}\ \mathrm{B} =
-    128\ \mathrm{TiB}
-  ```
 - **WithdrawFee** \
   Fee paid for withdrawal of funds paid by the account owner.
   Value: little-endian integer. Default: 0.
@@ -380,45 +349,45 @@ System parameters:
 <a name="neo.fs.v2.netmap.NetworkInfo"></a>
 
 ### Message NetworkInfo
-Information about FrostFS network
+Information about NeoFS network
 
 
 | Field | Type | Label | Description |
 | ----- | ---- | ----- | ----------- |
-| current_epoch | [uint64](#uint64) |  | Number of the current epoch in the FrostFS network |
+| current_epoch | [uint64](#uint64) |  | Number of the current epoch in the NeoFS network |
-| magic_number | [uint64](#uint64) |  | Magic number of the sidechain of the FrostFS network |
+| magic_number | [uint64](#uint64) |  | Magic number of the sidechain of the NeoFS network |
-| ms_per_block | [int64](#int64) |  | MillisecondsPerBlock network parameter of the sidechain of the FrostFS network |
+| ms_per_block | [int64](#int64) |  | MillisecondsPerBlock network parameter of the sidechain of the NeoFS network |
-| network_config | [NetworkConfig](#neo.fs.v2.netmap.NetworkConfig) |  | FrostFS network configuration |
+| network_config | [NetworkConfig](#neo.fs.v2.netmap.NetworkConfig) |  | NeoFS network configuration |
 
 
 <a name="neo.fs.v2.netmap.NodeInfo"></a>
 
 ### Message NodeInfo
-FrostFS node description
+NeoFS node description
 
 
 | Field | Type | Label | Description |
 | ----- | ---- | ----- | ----------- |
-| public_key | [bytes](#bytes) |  | Public key of the FrostFS node in a binary format |
+| public_key | [bytes](#bytes) |  | Public key of the NeoFS node in a binary format |
 | addresses | [string](#string) | repeated | Ways to connect to a node |
-| attributes | [NodeInfo.Attribute](#neo.fs.v2.netmap.NodeInfo.Attribute) | repeated | Carries list of the FrostFS node attributes in a key-value form. Key name must be a node-unique valid UTF-8 string. Value can't be empty. NodeInfo structures with duplicated attribute names or attributes with empty values will be considered invalid. |
+| attributes | [NodeInfo.Attribute](#neo.fs.v2.netmap.NodeInfo.Attribute) | repeated | Carries list of the NeoFS node attributes in a key-value form. Key name must be a node-unique valid UTF-8 string. Value can't be empty. NodeInfo structures with duplicated attribute names or attributes with empty values will be considered invalid. |
-| state | [NodeInfo.State](#neo.fs.v2.netmap.NodeInfo.State) |  | Carries state of the FrostFS node |
+| state | [NodeInfo.State](#neo.fs.v2.netmap.NodeInfo.State) |  | Carries state of the NeoFS node |
 
 
 <a name="neo.fs.v2.netmap.NodeInfo.Attribute"></a>
 
 ### Message NodeInfo.Attribute
-Administrator-defined Attributes of the FrostFS Storage Node.
+Administrator-defined Attributes of the NeoFS Storage Node.
 
 `Attribute` is a Key-Value metadata pair. Key name must be a valid UTF-8
 string. Value can't be empty.
 
 Attributes can be constructed into a chain of attributes: any attribute can
 have a parent attribute and a child attribute (except the first and the
-last one). A string representation of the chain of attributes in FrostFS
+last one). A string representation of the chain of attributes in NeoFS
 Storage Node configuration uses ":" and "/" symbols, e.g.:
 
-       `FrostFS_NODE_ATTRIBUTE_1=key1:val1/key2:val2`
+       `NEOFS_NODE_ATTRIBUTE_1=key1:val1/key2:val2`
 
 Therefore the string attribute representation in the Node configuration
 must use "\:", "\/" and "\\" escaped symbols if any of them appears in an
@@ -465,8 +434,8 @@ explicitly set:
   [ISO 3166-2](https://en.wikipedia.org/wiki/ISO_3166-2). Calculated
   automatically from `UN-LOCODE` attribute.
 * Continent \
-  Node's continent name according to the [Seven-Continent
+  Node's continent name according to the [Seven-Continent model]
-  model](https://en.wikipedia.org/wiki/Continent#Number). Calculated
+  (https://en.wikipedia.org/wiki/Continent#Number). Calculated
   automatically from `UN-LOCODE` attribute.
 * ExternalAddr
   Node's preferred way for communications with external clients.
@@ -474,7 +443,7 @@ explicitly set:
   Must contain a comma-separated list of multi-addresses.
 
 For detailed description of each well-known attribute please see the
-corresponding section in FrostFS Technical Specification.
+corresponding section in NeoFS Technical Specification.
 
 
 | Field | Type | Label | Description |
@@ -495,7 +464,7 @@ storage policy definition languages.
 | Field | Type | Label | Description |
 | ----- | ---- | ----- | ----------- |
 | replicas | [Replica](#neo.fs.v2.netmap.Replica) | repeated | Rules to set number of object replicas and place each one into a named bucket |
-| container_backup_factor | [uint32](#uint32) |  | Container backup factor controls how deep FrostFS will search for nodes alternatives to include into container's nodes subset |
+| container_backup_factor | [uint32](#uint32) |  | Container backup factor controls how deep NeoFS will search for nodes alternatives to include into container's nodes subset |
 | selectors | [Selector](#neo.fs.v2.netmap.Selector) | repeated | Set of Selectors to form the container's nodes subset |
 | filters | [Filter](#neo.fs.v2.netmap.Filter) | repeated | List of named filters to reference in selectors |
 | unique | [bool](#bool) |  | Unique flag defines non-overlapping application for replicas |
@@ -553,7 +522,7 @@ hash distance.
 <a name="neo.fs.v2.netmap.NodeInfo.State"></a>
 
 ### NodeInfo.State
-Represents the enumeration of various states of the FrostFS node.
+Represents the enumeration of various states of the NeoFS node.
 
 | Name | Number | Description |
 | ---- | ------ | ----------- |
@@ -581,7 +550,6 @@ Operations on filters
 | OR | 7 | Logical OR |
 | AND | 8 | Logical AND |
 | NOT | 9 | Logical negation |
-| LIKE | 10 | Matches pattern |
 
 
  <!-- end enums -->
@@ -607,3 +575,4 @@ Operations on filters
 | <a name="bool" /> bool |  | bool | boolean | boolean |
 | <a name="string" /> string | A string must always contain UTF-8 encoded or 7-bit ASCII text. | string | String | str/unicode |
 | <a name="bytes" /> bytes | May contain any arbitrary sequence of bytes. | string | ByteString | str |
+

proto-docs/object.md

@@ -254,7 +254,7 @@ Statuses:
 #### Method Search
 
 Search objects in container. Search query allows to match by Object
-Header's filed values. Please see the corresponding FrostFS Technical
+Header's filed values. Please see the corresponding NeoFS Technical
 Specification section for more details.
 
 Extended headers can change `Search` behaviour:
@@ -404,20 +404,16 @@ been deleted;
 #### Method Patch
 
 Patch the object. Request uses gRPC stream. First message must set
-the address of the object that is going to get patched. If the object's
+the address of the object that is going to get patched. If the object's attributes
-attributes are patched, then these attrubutes must be set only within the
+are patched, then these attrubutes must be set only within the first stream message.
-first stream message.
 
-If the patch request is performed by NOT the object's owner but if the
+If the patch request is performed by NOT the object's owner but if the actor has the permission
-actor has the permission to perform the patch, then `OwnerID` of the object
+to perform the patch, then `OwnerID` of the object is changed. In this case the object's owner
-is changed. In this case the object's owner loses the object's ownership
+loses the object's ownership after the patch request is successfully done.
-after the patch request is successfully done.
 
-As objects are content-addressable the patching causes new object ID
+As objects are content-addressable the patching causes new object ID generation for the patched object.
-generation for the patched object. This object id is set witihn
+This object id is set witihn `PatchResponse`. But the object id may remain unchanged in such cases: 
-`PatchResponse`. But the object id may remain unchanged in such cases:
+1. The chunk of the applying patch contains the same value as the object's payload within the same range;
-1. The chunk of the applying patch contains the same value as the object's
-payload within the same range;
 2. The patch that reverts the changes applied by preceding patch;
 3. The application of the same patches for the object a few times.
 
@@ -1000,8 +996,8 @@ prefix to the name. Here is the list of fields available via this prefix:
 * $Object:split.splitID \
   16 byte UUIDv4 used to identify the split object hierarchy parts
 * $Object:ec.parent \
-  If the object is stored according to EC policy, then ec_parent
+  If the object is stored according to EC policy, then ec_parent attribute
-  attribute is set to return an id list of all related EC chunks.
+  is set to return an id list of all related EC chunks.
 
 There are some well-known filter aliases to match objects by certain
 properties:
@@ -1164,7 +1160,7 @@ And some well-known attributes used by applications only:
   MIME Content Type of object's payload
 
 For detailed description of each well-known attribute please see the
-corresponding section in FrostFS Technical Specification.
+corresponding section in NeoFS Technical Specification.
 
 
 | Field | Type | Label | Description |
@@ -1323,3 +1319,4 @@ String presentation of object type is the same as definition:
 | <a name="bool" /> bool |  | bool | boolean | boolean |
 | <a name="string" /> string | A string must always contain UTF-8 encoded or 7-bit ASCII text. | string | String | str/unicode |
 | <a name="bytes" /> bytes | May contain any arbitrary sequence of bytes. | string | ByteString | str |
+

proto-docs/refs.md

@@ -32,7 +32,7 @@
 <a name="neo.fs.v2.refs.Address"></a>
 
 ### Message Address
-Objects in FrostFS are addressed by their ContainerID and ObjectID.
+Objects in NeoFS are addressed by their ContainerID and ObjectID.
 
 String presentation of `Address` is a concatenation of string encoded
 `ContainerID` and `ObjectID` delimited by '/' character.
@@ -65,7 +65,7 @@ Depending on checksum algorithm type, the string presentation may vary:
 <a name="neo.fs.v2.refs.ContainerID"></a>
 
 ### Message ContainerID
-FrostFS container identifier. Container structures are immutable and
+NeoFS container identifier. Container structures are immutable and
 content-addressed.
 
 `ContainerID` is a 32 byte long
@@ -90,9 +90,8 @@ with/without paddings are accepted.
 <a name="neo.fs.v2.refs.ObjectID"></a>
 
 ### Message ObjectID
-FrostFS Object unique identifier. Objects are immutable and
+NeoFS Object unique identifier. Objects are immutable and content-addressed.
-content-addressed. It means `ObjectID` will change if the `header` or the
+It means `ObjectID` will change if the `header` or the `payload` changes.
-`payload` changes.
 
 `ObjectID` is a 32 byte long
 [SHA256](https://csrc.nist.gov/publications/detail/fips/180/4/final) hash of
@@ -142,7 +141,7 @@ with/without paddings are accepted.
 <a name="neo.fs.v2.refs.Signature"></a>
 
 ### Message Signature
-Signature of something in FrostFS.
+Signature of something in NeoFS.
 
 
 | Field | Type | Label | Description |
@@ -231,3 +230,4 @@ pair.
 | <a name="bool" /> bool |  | bool | boolean | boolean |
 | <a name="string" /> string | A string must always contain UTF-8 encoded or 7-bit ASCII text. | string | String | str/unicode |
 | <a name="bytes" /> bytes | May contain any arbitrary sequence of bytes. | string | ByteString | str |
+

proto-docs/session.md

@@ -48,7 +48,7 @@
 `SessionService` allows to establish a temporary trust relationship between
 two peer nodes and generate a `SessionToken` as the proof of trust to be
 attached in requests for further verification. Please see corresponding
-section of FrostFS Technical Specification for details.
+section of NeoFS Technical Specification for details.
 
 ```
 rpc Create(CreateRequest) returns (CreateResponse);
@@ -168,7 +168,7 @@ Carries objects involved in the object session.
 | Field | Type | Label | Description |
 | ----- | ---- | ----- | ----------- |
 | container | [neo.fs.v2.refs.ContainerID](#neo.fs.v2.refs.ContainerID) |  | Indicates which container the session is spread to. Field MUST be set and correct. |
-| objects | [neo.fs.v2.refs.ObjectID](#neo.fs.v2.refs.ObjectID) | repeated | Indicates which objects the session is spread to. Objects are expected to be stored in the FrostFS container referenced by `container` field. Each element MUST have correct format. |
+| objects | [neo.fs.v2.refs.ObjectID](#neo.fs.v2.refs.ObjectID) | repeated | Indicates which objects the session is spread to. Objects are expected to be stored in the NeoFS container referenced by `container` field. Each element MUST have correct format. |
 
 
 <a name="neo.fs.v2.session.RequestMetaHeader"></a>
@@ -187,7 +187,7 @@ request meta headers are folded in matryoshka style.
 | session_token | [SessionToken](#neo.fs.v2.session.SessionToken) |  | Session token within which the request is sent |
 | bearer_token | [neo.fs.v2.acl.BearerToken](#neo.fs.v2.acl.BearerToken) |  | `BearerToken` with eACL overrides for the request |
 | origin | [RequestMetaHeader](#neo.fs.v2.session.RequestMetaHeader) |  | `RequestMetaHeader` of the origin request |
-| magic_number | [uint64](#uint64) |  | FrostFS network magic. Must match the value for the network that the server belongs to. |
+| magic_number | [uint64](#uint64) |  | NeoFS network magic. Must match the value for the network that the server belongs to. |
 
 
 <a name="neo.fs.v2.session.RequestVerificationHeader"></a>
@@ -237,12 +237,12 @@ Verification info for the response signed by all intermediate nodes
 <a name="neo.fs.v2.session.SessionToken"></a>
 
 ### Message SessionToken
-FrostFS Session Token.
+NeoFS Session Token.
 
 
 | Field | Type | Label | Description |
 | ----- | ---- | ----- | ----------- |
-| body | [SessionToken.Body](#neo.fs.v2.session.SessionToken.Body) |  | Session Token contains the proof of trust between peers to be attached in requests for further verification. Please see corresponding section of FrostFS Technical Specification for details. |
+| body | [SessionToken.Body](#neo.fs.v2.session.SessionToken.Body) |  | Session Token contains the proof of trust between peers to be attached in requests for further verification. Please see corresponding section of NeoFS Technical Specification for details. |
 | signature | [neo.fs.v2.refs.Signature](#neo.fs.v2.refs.Signature) |  | Signature of `SessionToken` information |
 
 
@@ -338,7 +338,6 @@ Object request verbs
 | DELETE | 5 | Refers to object.Delete RPC call |
 | RANGE | 6 | Refers to object.GetRange RPC call |
 | RANGEHASH | 7 | Refers to object.GetRangeHash RPC call |
-| PATCH | 8 | Refers to object.Patch RPC call |
 
 
  <!-- end enums -->
@@ -364,3 +363,4 @@ Object request verbs
 | <a name="bool" /> bool |  | bool | boolean | boolean |
 | <a name="string" /> string | A string must always contain UTF-8 encoded or 7-bit ASCII text. | string | String | str/unicode |
 | <a name="bytes" /> bytes | May contain any arbitrary sequence of bytes. | string | ByteString | str |
+

proto-docs/status.md

@@ -26,12 +26,12 @@
 <a name="neo.fs.v2.status.Status"></a>
 
 ### Message Status
-Declares the general format of the status returns of the FrostFS RPC
+Declares the general format of the status returns of the NeoFS RPC protocol.
-protocol. Status is present in all response messages. Each RPC of FrostFS
+Status is present in all response messages. Each RPC of NeoFS protocol
-protocol describes the possible outcomes and details of the operation.
+describes the possible outcomes and details of the operation.
 
 Each status is assigned a one-to-one numeric code. Any unique result of an
-operation in FrostFS is unambiguously associated with the code value.
+operation in NeoFS is unambiguously associated with the code value.
 
 Numerical set of codes is split into 1024-element sections. An enumeration
 is defined for each section. Values can be referred to in the following ways:
@@ -98,7 +98,7 @@ Section of failed statuses independent of the operation.
 | Name | Number | Description |
 | ---- | ------ | ----------- |
 | INTERNAL | 0 | [**1024**] Internal server error, default failure. Not detailed. If the server cannot match failed outcome to the code, it should use this code. |
-| WRONG_MAGIC_NUMBER | 1 | [**1025**] Wrong magic of the FrostFS network. Details: - [**0**] Magic number of the served FrostFS network (big-endian 64-bit unsigned integer). |
+| WRONG_MAGIC_NUMBER | 1 | [**1025**] Wrong magic of the NeoFS network. Details: - [**0**] Magic number of the served NeoFS network (big-endian 64-bit unsigned integer). |
 | SIGNATURE_VERIFICATION_FAIL | 2 | [**1026**] Signature verification failure. |
 | NODE_UNDER_MAINTENANCE | 3 | [**1027**] Node is under maintenance. |
 | INVALID_ARGUMENT | 4 | [**1028**] Invalid argument error. If the server fails on validation of a request parameter as the client sent it incorrectly, then this code should be used. |
@@ -165,7 +165,7 @@ Section of statuses for session-related operations.
 <a name="neo.fs.v2.status.Success"></a>
 
 ### Success
-Section of FrostFS successful return codes.
+Section of NeoFS successful return codes.
 
 | Name | Number | Description |
 | ---- | ------ | ----------- |
@@ -195,3 +195,4 @@ Section of FrostFS successful return codes.
 | <a name="bool" /> bool |  | bool | boolean | boolean |
 | <a name="string" /> string | A string must always contain UTF-8 encoded or 7-bit ASCII text. | string | String | str/unicode |
 | <a name="bytes" /> bytes | May contain any arbitrary sequence of bytes. | string | ByteString | str |
+

proto-docs/tombstone.md

@@ -26,12 +26,12 @@
 
 ### Message Tombstone
 Tombstone keeps record of deleted objects for a few epochs until they are
-purged from the FrostFS network.
+purged from the NeoFS network.
 
 
 | Field | Type | Label | Description |
 | ----- | ---- | ----- | ----------- |
-| expiration_epoch | [uint64](#uint64) |  | Last FrostFS epoch number of the tombstone lifetime. It's set by the tombstone creator depending on the current FrostFS network settings. A tombstone object must have the same expiration epoch value in `__SYSTEM__EXPIRATION_EPOCH` (`__NEOFS__EXPIRATION_EPOCH` is deprecated) attribute. Otherwise, the tombstone will be rejected by a storage node. |
+| expiration_epoch | [uint64](#uint64) |  | Last NeoFS epoch number of the tombstone lifetime. It's set by the tombstone creator depending on the current NeoFS network settings. A tombstone object must have the same expiration epoch value in `__SYSTEM__EXPIRATION_EPOCH` (`__NEOFS__EXPIRATION_EPOCH` is deprecated) attribute. Otherwise, the tombstone will be rejected by a storage node. |
 | split_id | [bytes](#bytes) |  | 16 byte UUID used to identify the split object hierarchy parts. Must be unique inside a container. All objects participating in the split must have the same `split_id` value. |
 | members | [neo.fs.v2.refs.ObjectID](#neo.fs.v2.refs.ObjectID) | repeated | List of objects to be deleted. |
 
@@ -60,3 +60,4 @@ purged from the FrostFS network.
 | <a name="bool" /> bool |  | bool | boolean | boolean |
 | <a name="string" /> string | A string must always contain UTF-8 encoded or 7-bit ASCII text. | string | String | str/unicode |
 | <a name="bytes" /> bytes | May contain any arbitrary sequence of bytes. | string | ByteString | str |
+

refs/types.proto

@@ -5,7 +5,7 @@ package neo.fs.v2.refs;
 option go_package = "git.frostfs.info/TrueCloudLab/frostfs-api-go/v2/refs/grpc;refs";
 option csharp_namespace = "Neo.FileStorage.API.Refs";
 
-// Objects in FrostFS are addressed by their ContainerID and ObjectID.
+// Objects in NeoFS are addressed by their ContainerID and ObjectID.
 //
 // String presentation of `Address` is a concatenation of string encoded
 // `ContainerID` and `ObjectID` delimited by '/' character.
@@ -16,9 +16,8 @@ message Address {
   ObjectID object_id = 2 [ json_name = "objectID" ];
 }
 
-// FrostFS Object unique identifier. Objects are immutable and
+// NeoFS Object unique identifier. Objects are immutable and content-addressed.
-// content-addressed. It means `ObjectID` will change if the `header` or the
+// It means `ObjectID` will change if the `header` or the `payload` changes.
-// `payload` changes.
 //
 // `ObjectID` is a 32 byte long
 // [SHA256](https://csrc.nist.gov/publications/detail/fips/180/4/final) hash of
@@ -38,7 +37,7 @@ message ObjectID {
   bytes value = 1 [ json_name = "value" ];
 }
 
-// FrostFS container identifier. Container structures are immutable and
+// NeoFS container identifier. Container structures are immutable and
 // content-addressed.
 //
 // `ContainerID` is a 32 byte long
@@ -91,7 +90,7 @@ message Version {
   uint32 minor = 2 [ json_name = "minor" ];
 }
 
-// Signature of something in FrostFS.
+// Signature of something in NeoFS.
 message Signature {
   // Public key used for signing
   bytes key = 1 [ json_name = "key" ];

session/service.proto

@@ -11,7 +11,7 @@ import "session/types.proto";
 // `SessionService` allows to establish a temporary trust relationship between
 // two peer nodes and generate a `SessionToken` as the proof of trust to be
 // attached in requests for further verification. Please see corresponding
-// section of FrostFS Technical Specification for details.
+// section of NeoFS Technical Specification for details.
 service SessionService {
   // Open a new session between two peers.
   //

session/types.proto

@@ -36,9 +36,6 @@ message ObjectSessionContext {
 
     // Refers to object.GetRangeHash RPC call
     RANGEHASH = 7;
-
-    // Refers to object.Patch RPC call
-    PATCH = 8;
   }
   // Type of request for which the token is issued
   Verb verb = 1 [ json_name = "verb" ];
@@ -50,7 +47,7 @@ message ObjectSessionContext {
     refs.ContainerID container = 1 [ json_name = "container" ];
 
     // Indicates which objects the session is spread to. Objects are expected
-    // to be stored in the FrostFS container referenced by `container` field.
+    // to be stored in the NeoFS container referenced by `container` field.
     // Each element MUST have correct format.
     repeated refs.ObjectID objects = 2 [ json_name = "objects" ];
   }
@@ -88,7 +85,7 @@ message ContainerSessionContext {
   refs.ContainerID container_id = 3 [ json_name = "containerID" ];
 }
 
-// FrostFS Session Token.
+// NeoFS Session Token.
 message SessionToken {
   // Session Token body
   message Body {
@@ -126,7 +123,7 @@ message SessionToken {
   }
   // Session Token contains the proof of trust between peers to be attached in
   // requests for further verification. Please see corresponding section of
-  // FrostFS Technical Specification for details.
+  // NeoFS Technical Specification for details.
   Body body = 1 [ json_name = "body" ];
 
   // Signature of `SessionToken` information
@@ -186,7 +183,7 @@ message RequestMetaHeader {
   // `RequestMetaHeader` of the origin request
   RequestMetaHeader origin = 7 [ json_name = "origin" ];
 
-  // FrostFS network magic. Must match the value for the network
+  // NeoFS network magic. Must match the value for the network
   // that the server belongs to.
   uint64 magic_number = 8 [ json_name = "magicNumber" ];
 }

status/types.proto

@@ -5,12 +5,12 @@ package neo.fs.v2.status;
 option go_package = "git.frostfs.info/TrueCloudLab/frostfs-api-go/v2/status/grpc;status";
 option csharp_namespace = "Neo.FileStorage.API.Status";
 
-// Declares the general format of the status returns of the FrostFS RPC
+// Declares the general format of the status returns of the NeoFS RPC protocol.
-// protocol. Status is present in all response messages. Each RPC of FrostFS
+// Status is present in all response messages. Each RPC of NeoFS protocol
-// protocol describes the possible outcomes and details of the operation.
+// describes the possible outcomes and details of the operation.
 //
 // Each status is assigned a one-to-one numeric code. Any unique result of an
-// operation in FrostFS is unambiguously associated with the code value.
+// operation in NeoFS is unambiguously associated with the code value.
 //
 // Numerical set of codes is split into 1024-element sections. An enumeration
 // is defined for each section. Values can be referred to in the following ways:
@@ -78,7 +78,7 @@ enum Section {
   SECTION_APE_MANAGER = 5;
 }
 
-// Section of FrostFS successful return codes.
+// Section of NeoFS successful return codes.
 enum Success {
   // [**0**] Default success. Not detailed.
   // If the server cannot match successful outcome to the code, it should
@@ -93,9 +93,9 @@ enum CommonFail {
   // use this code.
   INTERNAL = 0;
 
-  // [**1025**] Wrong magic of the FrostFS network.
+  // [**1025**] Wrong magic of the NeoFS network.
   // Details:
-  //  - [**0**] Magic number of the served FrostFS network (big-endian 64-bit
+  //  - [**0**] Magic number of the served NeoFS network (big-endian 64-bit
   //  unsigned integer).
   WRONG_MAGIC_NUMBER = 1;
 
@@ -106,8 +106,7 @@ enum CommonFail {
   NODE_UNDER_MAINTENANCE = 3;
 
   // [**1028**] Invalid argument error. If the server fails on validation of a
-  // request parameter as the client sent it incorrectly, then this code should
+  // request parameter as the client sent it incorrectly, then this code should be used. 
-  // be used.
   INVALID_ARGUMENT = 4;
 }
 

tombstone/types.proto

@@ -8,10 +8,10 @@ option csharp_namespace = "Neo.FileStorage.API.Tombstone";
 import "refs/types.proto";
 
 // Tombstone keeps record of deleted objects for a few epochs until they are
-// purged from the FrostFS network.
+// purged from the NeoFS network.
 message Tombstone {
-  // Last FrostFS epoch number of the tombstone lifetime. It's set by the
+  // Last NeoFS epoch number of the tombstone lifetime. It's set by the
-  // tombstone creator depending on the current FrostFS network settings. A
+  // tombstone creator depending on the current NeoFS network settings. A
   // tombstone object must have the same expiration epoch value in
   // `__SYSTEM__EXPIRATION_EPOCH` (`__NEOFS__EXPIRATION_EPOCH` is deprecated)
   // attribute. Otherwise, the tombstone will be rejected by a storage node.