[#71] Stop using obsolete .github directory

This commit is a part of multi-repo cleanup effort:
TrueCloudLab/frostfs-infra#136

Signed-off-by: Vitaliy Potyarkin <v.potyarkin@yadro.com>

.forgejo/workflows/dco.yaml

@@ -0,0 +1,19 @@
+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

@@ -0,0 +1,17 @@
+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

@@ -0,0 +1,18 @@
+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

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

.github/workflows/buf.yml

@@ -1,36 +0,0 @@
-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

@@ -1,21 +0,0 @@
-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,2 +1 @@
 .idea
-

.pre-commit-config.yaml

@@ -0,0 +1,24 @@
+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

@@ -0,0 +1 @@
+.*   @alexvanin @realloc @fyrchik @a.bogatyrev

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://github.com/TrueCloudLab/frostfs-api/issues) and
+- Check the open [issues](https://git.frostfs.info/TrueCloudLab/frostfs-api/issues) and
-  [pull requests](https://github.com/TrueCloudLab/frostfs-api/pulls) for existing
+  [pull requests](https://git.frostfs.info/TrueCloudLab/frostfs-api/pulls) for existing
   discussions.
 
 - Open an issue first, to discuss a new feature or enhancement.
@@ -25,19 +25,20 @@ 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 GitHub Repository
+### Set up your 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://github.com/TrueCloudLab/frostfs-api
+$ git clone https://git.frostfs.info/TrueCloudLab/frostfs-api
 ```
 
 ### Set up git remote as ``upstream``
 ```sh
 $ cd frostfs-api
-$ git remote add upstream https://github.com/TrueCloudLab/frostfs-api
+$ git remote add upstream https://git.frostfs.info/TrueCloudLab/frostfs-api
 $ git fetch upstream
 $ git merge upstream/master
 ...
@@ -86,7 +87,7 @@ $ git push origin feature/123-something_awesome
 ```
 
 ### Create a Pull Request
-Pull requests can be created via GitHub. Refer to [this
+Pull requests can be created via git.frostfs.info. 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,27 +1,35 @@
 #!/usr/bin/make -f
 SHELL=bash
 
-# BRanch to match for BReaking changes
+include help.mk
-BRBR?=master
 
-.PHONY: lint
+.PHONY: doc fmt pre-commit unpre-commit pre-commit-run
-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=.github/markdown.tmpl,$${f}.md \
+			--doc_opt=.forgejo/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,19 +1,18 @@
 <p align="center">
-<img src="./.github/logo.svg" width="500px" alt="FrostFS">
+<img src="./.forgejo/logo.svg" width="500px" alt="FrostFS">
 </p>
 <p align="center">
-  <a href="https://objectstorage.info">FrostFS</a> API language-agnostic protocol definitions
+  <a href="https://frostfs.info">FrostFS</a> API language-agnostic protocol definitions
 </p>
 
 ---
-![GitHub release (latest SemVer)](https://img.shields.io/github/v/release/TrueCloudLab/frostfs-api?sort=semver)
+![Release](https://git.frostfs.info/TrueCloudLab/frostfs-api/badges/release.svg)
-![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://github.com/TrueCloudLab/frostfs-api-go)
+- [frostfs-api-go](https://git.frostfs.info/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 NeoFS sidechain via
+// Accounting service provides methods for interaction with FrostFS sidechain
-// other NeoFS nodes to get information about the account balance. Deposit and
+// via other FrostFS nodes to get information about the account balance. Deposit
-// Withdraw operations can't be implemented here, as they require Mainnet NeoFS
+// and Withdraw operations can't be implemented here, as they require Mainnet
-// smart contract invocation. Transfer operations between internal NeoFS
+// FrostFS smart contract invocation. Transfer operations between internal
-// accounts are possible if both use the same token type.
+// FrostFS accounts are possible if both use the same token type.
 service AccountingService {
-  // Returns the amount of funds in GAS token for the requested NeoFS account.
+  // Returns the amount of funds in GAS token for the requested FrostFS 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 NeoFS sidechain `Balance` smart
+  // is used. It can be any existing account in FrostFS sidechain `Balance`
-  // contract. If omitted, client implementation MUST set it to the request's
+  // smart contract. If omitted, client implementation MUST set it to the
-  // signer `OwnerID`.
+  // request's 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 NeoFS due to inexactness
+// Standard floating point data type can't be used in FrostFS 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 NeoFS nodes and
+  // Filter service headers. These are not processed by FrostFS nodes and
   // exist for service use only.
   SERVICE = 3;
 }
 
 // Describes a single eACL rule.
 message EACLRecord {
-  // NeoFS request Verb to match
+  // FrostFS 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
-// NeoFS Technical Specification section for detailed description.
+// FrostFS Technical Specification section for detailed description.
 message EACLTable {
   // eACL format version. Effectively, the version of API library used to create
   // eACL Table.

buf.yaml

@@ -1,10 +0,0 @@
-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,14 +5,13 @@ 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 NeoFS sidechain via other NeoFS nodes. All of those actions can be done
+// in FrostFS sidechain via other FrostFS nodes. All of those actions can be
-// equivalently by directly issuing transactions and RPC calls to sidechain
+// done equivalently by directly issuing transactions and RPC calls to sidechain
 // nodes.
 service ContainerService {
   // `Put` invokes `Container` smart contract's `Put` method and returns
@@ -62,24 +61,9 @@ service ContainerService {
   // - **CONTAINER_ACCESS_DENIED** (3074, SECTION_CONTAINER): \
   //   container list access denied.
   rpc List(ListRequest) returns (ListResponse);
-
-  // 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);
 }
 
-// New NeoFS Container creation request
+// New FrostFS 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
@@ -87,7 +71,7 @@ message PutRequest {
   // the stable-marshalled container strucutre, hence there is no need for
   // additional signature checks.
   message Body {
-    // Container structure to register in NeoFS
+    // Container structure to register in FrostFS
     container.Container container = 1;
 
     // Signature of a stable-marshalled container according to RFC-6979.
@@ -106,7 +90,7 @@ message PutRequest {
   neo.fs.v2.session.RequestVerificationHeader verify_header = 3;
 }
 
-// New NeoFS Container creation response
+// New FrostFS 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
@@ -135,7 +119,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 NeoFS
+    // Identifier of the container to delete from FrostFS
     neo.fs.v2.refs.ContainerID container_id = 1;
 
     // `ContainerID` signed with the container owner's key according to
@@ -261,52 +245,3 @@ message ListResponse {
   // 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;
-}

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 NeoFS network only if the global network hashing
+  //   could be accepted in a FrostFS 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 neofs-api release process and can be used as a TODO
+This documents outlines the frostfs-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 GitHub issues, where
+describing each change briefly with a reference to 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 Github
+## Push changes and release tag to repository
 
 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 Github release
+## Make a proper release
 
-Edit an automatically-created release on Github.
+Edit an automatically-created release on git.frostfs.info
 
 Release title has to follow `<version> <Romanized codename> (<Hangeul, Hanja
 codename> )` scheme for major releases and just `<version>` for regular point
@@ -58,6 +58,5 @@ releases.
 
 ## Post-release actions
 
-* Close corresponding X.Y.Z Github milestone
+* Close corresponding X.Y.Z milestone
 * Make announcements in Matrix and Discord channels
-* Update [NeoFS Technical Specification](https://github.com/nspcc-dev/neofs-spec)

help.mk

@@ -0,0 +1,11 @@
+.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 NeoFS nodes.
+// from other FrostFS 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 NeoFS network.
+  // Read recent information about the FrostFS 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 NeoFS epoch.
+  // Returns network map snapshot of the current FrostFS 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 NeoFS API version in use
+    // Latest FrostFS API version in use
     neo.fs.v2.refs.Version version = 1;
 
     // NodeInfo structure with recent information from node itself

netmap/types.proto

@@ -122,7 +122,7 @@ message PlacementPolicy {
   // bucket
   repeated Replica replicas = 1 [ json_name = "replicas" ];
 
-  // Container backup factor controls how deep NeoFS will search for nodes
+  // Container backup factor controls how deep FrostFS will search for nodes
   // alternatives to include into container's nodes subset
   uint32 container_backup_factor = 2 [ json_name = "containerBackupFactor" ];
 
@@ -136,25 +136,25 @@ message PlacementPolicy {
   bool unique = 5 [ json_name = "unique" ];
 }
 
-// NeoFS node description
+// FrostFS node description
 message NodeInfo {
-  // Public key of the NeoFS node in a binary format
+  // Public key of the FrostFS 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 NeoFS Storage Node.
+  // Administrator-defined Attributes of the FrostFS 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 NeoFS
+  // last one). A string representation of the chain of attributes in FrostFS
   // Storage Node configuration uses ":" and "/" symbols, e.g.:
   //
-  //        `NEOFS_NODE_ATTRIBUTE_1=key1:val1/key2:val2`
+  //        `FrostFS_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 +201,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 model]
+  //   Node's continent name according to the [Seven-Continent
-  //   (https://en.wikipedia.org/wiki/Continent#Number). Calculated
+  //   model](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 +210,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 NeoFS Technical Specification.
+  // corresponding section in FrostFS Technical Specification.
   message Attribute {
     // Key of the node attribute
     string key = 1 [ json_name = "key" ];
@@ -222,13 +222,13 @@ message NodeInfo {
     // `Country`.
     repeated string parents = 3 [ json_name = "parents" ];
   }
-  // Carries list of the NeoFS node attributes in a key-value form. Key name
+  // 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.
   repeated Attribute attributes = 3 [ json_name = "attributes" ];
 
-  // Represents the enumeration of various states of the NeoFS node.
+  // Represents the enumeration of various states of the FrostFS node.
   enum State {
     // Unknown state
     UNSPECIFIED = 0;
@@ -243,7 +243,7 @@ message NodeInfo {
     MAINTENANCE = 3;
   }
 
-  // Carries state of the NeoFS node
+  // Carries state of the FrostFS node
   State state = 4 [ json_name = "state" ];
 }
 
@@ -256,7 +256,7 @@ message Netmap {
   repeated NodeInfo nodes = 2 [ json_name = "nodes" ];
 }
 
-// NeoFS network configuration
+// FrostFS network configuration
 message NetworkConfig {
   // Single configuration parameter. Key MUST be network-unique.
   //
@@ -275,7 +275,7 @@ message NetworkConfig {
   //   Fee paid for container creation by the container owner.
   //   Value: little-endian integer. Default: 0.
   // - **EpochDuration** \
-  //   NeoFS epoch duration measured in Sidechain blocks.
+  //   FrostFS epoch duration measured in Sidechain blocks.
   //   Value: little-endian integer. Default: 0.
   // - **HomomorphicHashingDisabled** \
   //   Flag of disabling the homomorphic hashing of objects' payload.
@@ -287,8 +287,39 @@ 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 NeoFS object measured in bytes.
+  //   Maximum size of physically stored FrostFS 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.
@@ -309,18 +340,18 @@ message NetworkConfig {
   repeated Parameter parameters = 1 [ json_name = "parameters" ];
 }
 
-// Information about NeoFS network
+// Information about FrostFS network
 message NetworkInfo {
-  // Number of the current epoch in the NeoFS network
+  // Number of the current epoch in the FrostFS network
   uint64 current_epoch = 1 [ json_name = "currentEpoch" ];
 
-  // Magic number of the sidechain of the NeoFS network
+  // Magic number of the sidechain of the FrostFS network
   uint64 magic_number = 2 [ json_name = "magicNumber" ];
 
-  // MillisecondsPerBlock network parameter of the sidechain of the NeoFS
+  // MillisecondsPerBlock network parameter of the sidechain of the FrostFS
   // network
   int64 ms_per_block = 3 [ json_name = "msPerBlock" ];
 
-  // NeoFS network configuration
+  // FrostFS 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 NeoFS Technical
+  // Header's filed values. Please see the corresponding FrostFS Technical
   // Specification section for more details.
   //
   // Extended headers can change `Search` behaviour:
@@ -285,16 +285,20 @@ 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 attributes
+  // the address of the object that is going to get patched. If the object's
-  // are patched, then these attrubutes must be set only within the first stream message.
+  // attributes are patched, then these attrubutes must be set only within the
+  // first stream message.
   //
-  // If the patch request is performed by NOT the object's owner but if the actor has the permission
+  // If the patch request is performed by NOT the object's owner but if the
-  // to perform the patch, then `OwnerID` of the object is changed. In this case the object's owner
+  // actor has the permission to perform the patch, then `OwnerID` of the object
-  // loses the object's ownership after the patch request is successfully done.
+  // is changed. In this case the object's owner loses the object's ownership
+  // after the patch request is successfully done.
   //
-  // As objects are content-addressable the patching causes new object ID generation for the patched object.
+  // As objects are content-addressable the patching causes new object ID
-  // This object id is set witihn `PatchResponse`. But the object id may remain unchanged in such cases: 
+  // generation for the patched object. This object id is set witihn
-  // 1. The chunk of the applying patch contains the same value as the object's payload within the same range;
+  // `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;
   // 2. The patch that reverts the changes applied by preceding patch;
   // 3. The application of the same patches for the object a few times.
   //
@@ -870,25 +874,29 @@ 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 define how
+    // New attributes for the object. See `replace_attributes` flag usage to
-    // new attributes should be set.
+    // define how 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 replaced by `new_attributes` list.
+    // If this flag is set, then the object's attributes will be entirely
-    // The empty `new_attributes` list with `replace_attributes = true` just resets attributes list for the object.
+    // replaced by `new_attributes` list. The empty `new_attributes` list with
+    // `replace_attributes = true` just resets attributes list for the object.
     //
-    // Default `false` value for this flag means the attributes will be just merged. If the incoming `new_attributes`
+    // Default `false` value for this flag means the attributes will be just
-    // list contains already existing key, then it just replaces it while merging the lists. 
+    // merged. If the incoming `new_attributes` list contains already existing
+    // 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 patch's chunk.
+      // The range of the source object for which the payload is replaced by the
-      // If the range's `length = 0`, then the patch's chunk is just appended to the original payload
+      // patch's chunk. If the range's `length = 0`, then the patch's chunk is
-      // starting from the `offest` without any replace.
+      // just appended to the original payload starting from the `offest`
+      // without any replace.
       Range source_range = 1;
 
-      // The chunk that is being appended to or that replaces the original payload on the given range.
+      // The chunk that is being appended to or that replaces the original
+      // payload on the given range.
       bytes chunk = 2;
     }
 
@@ -924,7 +932,8 @@ 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 authenticate
+  // Carries response verification information. This header is used to
-  // the nodes of the message route and check the correctness of transmission.
+  // authenticate the nodes of the message route and check the correctness of
+  // 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 NeoFS Technical Specification.
+  // corresponding section in FrostFS Technical Specification.
   message Attribute {
     // string key to the object attribute
     string key = 1 [ json_name = "key" ];

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 NeoFS sidechain via
+Accounting service provides methods for interaction with FrostFS sidechain
-other NeoFS nodes to get information about the account balance. Deposit and
+via other FrostFS nodes to get information about the account balance. Deposit
-Withdraw operations can't be implemented here, as they require Mainnet NeoFS
+and Withdraw operations can't be implemented here, as they require Mainnet
-smart contract invocation. Transfer operations between internal NeoFS
+FrostFS smart contract invocation. Transfer operations between internal
-accounts are possible if both use the same token type.
+FrostFS 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 NeoFS account.
+Returns the amount of funds in GAS token for the requested FrostFS 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 NeoFS sidechain `Balance` smart
+is used. It can be any existing account in FrostFS sidechain `Balance`
-contract. If omitted, client implementation MUST set it to the request's
+smart contract. If omitted, client implementation MUST set it to the
-signer `OwnerID`.
+request's 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 NeoFS due to inexactness
+Standard floating point data type can't be used in FrostFS 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,4 +170,3 @@ 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,11 +71,12 @@ 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 even undefined)
+These chains are meant to serve as overrides to the already defined (or
-APE chains for the target (see contract `Policy`).
+even undefined) APE chains for the target (see contract `Policy`).
 
-The server-side processing of the bearer token with set APE overrides must verify if a client is permitted
+The server-side processing of the bearer token with set APE overrides
-to override chains for the target, preventing unauthorized access through the APE mechanism.
+must verify if a client is permitted to override chains for the target,
+preventing unauthorized access through the APE mechanism.
 
 
 | Field | Type | Label | Description |
@@ -106,7 +107,7 @@ Describes a single eACL rule.
 
 | Field | Type | Label | Description |
 | ----- | ---- | ----- | ----------- |
-| operation | [Operation](#neo.fs.v2.acl.Operation) |  | NeoFS request Verb to match |
+| operation | [Operation](#neo.fs.v2.acl.Operation) |  | FrostFS 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 |
@@ -174,7 +175,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
-NeoFS Technical Specification section for detailed description.
+FrostFS Technical Specification section for detailed description.
 
 
 | Field | Type | Label | Description |
@@ -210,7 +211,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 NeoFS nodes and exist for service use only. |
+| SERVICE | 3 | Filter service headers. These are not processed by FrostFS nodes and exist for service use only. |
 
 
 
@@ -282,4 +283,3 @@ 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,4 +85,3 @@ 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,4 +267,3 @@ 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,19 +8,10 @@
       - [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)
@@ -33,10 +24,6 @@
       - [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)
@@ -62,8 +49,8 @@
 
 ### Service "neo.fs.v2.container.ContainerService"
 `ContainerService` provides API to interact with `Container` smart contract
-in NeoFS sidechain via other NeoFS nodes. All of those actions can be done
+in FrostFS sidechain via other FrostFS nodes. All of those actions can be
-equivalently by directly issuing transactions and RPC calls to sidechain
+done equivalently by directly issuing transactions and RPC calls to sidechain
 nodes.
 
 ```
@@ -71,9 +58,6 @@ 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);
 
 ```
 
@@ -141,114 +125,9 @@ 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
@@ -272,7 +151,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 NeoFS |
+| container_id | [neo.fs.v2.refs.ContainerID](#neo.fs.v2.refs.ContainerID) |  | Identifier of the container to delete from FrostFS |
 | signature | [neo.fs.v2.refs.SignatureRFC6979](#neo.fs.v2.refs.SignatureRFC6979) |  | `ContainerID` signed with the container owner's key according to RFC-6979. |
 
 
@@ -298,58 +177,6 @@ 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
@@ -452,7 +279,7 @@ List containers response body.
 <a name="neo.fs.v2.container.PutRequest"></a>
 
 ### Message PutRequest
-New NeoFS Container creation request
+New FrostFS Container creation request
 
 
 | Field | Type | Label | Description |
@@ -474,14 +301,14 @@ additional signature checks.
 
 | Field | Type | Label | Description |
 | ----- | ---- | ----- | ----------- |
-| container | [Container](#neo.fs.v2.container.Container) |  | Container structure to register in NeoFS |
+| container | [Container](#neo.fs.v2.container.Container) |  | Container structure to register in FrostFS |
 | 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 NeoFS Container creation response
+New FrostFS Container creation response
 
 
 | Field | Type | Label | Description |
@@ -504,54 +331,6 @@ 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 -->
@@ -612,7 +391,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 NeoFS network only if the global network hashing
+  could be accepted in a FrostFS network only if the global network hashing
   configuration value corresponds with that attribute's value. After
   container inclusion, network setting is ignored.
 
@@ -654,4 +433,3 @@ 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,4 +61,3 @@ 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 NeoFS nodes.
+from other FrostFS 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 NeoFS network.
+Read recent information about the FrostFS 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 NeoFS epoch.
+Returns network map snapshot of the current FrostFS 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 NeoFS API version in use |
+| version | [neo.fs.v2.refs.Version](#neo.fs.v2.refs.Version) |  | Latest FrostFS 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
-NeoFS network configuration
+FrostFS 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** \
-  NeoFS epoch duration measured in Sidechain blocks.
+  FrostFS epoch duration measured in Sidechain blocks.
   Value: little-endian integer. Default: 0.
 - **HomomorphicHashingDisabled** \
   Flag of disabling the homomorphic hashing of objects' payload.
@@ -327,8 +327,39 @@ 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 NeoFS object measured in bytes.
+  Maximum size of physically stored FrostFS 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.
@@ -349,45 +380,45 @@ System parameters:
 <a name="neo.fs.v2.netmap.NetworkInfo"></a>
 
 ### Message NetworkInfo
-Information about NeoFS network
+Information about FrostFS network
 
 
 | Field | Type | Label | Description |
 | ----- | ---- | ----- | ----------- |
-| current_epoch | [uint64](#uint64) |  | Number of the current epoch in the NeoFS network |
+| current_epoch | [uint64](#uint64) |  | Number of the current epoch in the FrostFS network |
-| magic_number | [uint64](#uint64) |  | Magic number of the sidechain of the NeoFS network |
+| magic_number | [uint64](#uint64) |  | Magic number of the sidechain of the FrostFS network |
-| ms_per_block | [int64](#int64) |  | MillisecondsPerBlock network parameter of the sidechain of the NeoFS network |
+| ms_per_block | [int64](#int64) |  | MillisecondsPerBlock network parameter of the sidechain of the FrostFS network |
-| network_config | [NetworkConfig](#neo.fs.v2.netmap.NetworkConfig) |  | NeoFS network configuration |
+| network_config | [NetworkConfig](#neo.fs.v2.netmap.NetworkConfig) |  | FrostFS network configuration |
 
 
 <a name="neo.fs.v2.netmap.NodeInfo"></a>
 
 ### Message NodeInfo
-NeoFS node description
+FrostFS node description
 
 
 | Field | Type | Label | Description |
 | ----- | ---- | ----- | ----------- |
-| public_key | [bytes](#bytes) |  | Public key of the NeoFS node in a binary format |
+| public_key | [bytes](#bytes) |  | Public key of the FrostFS 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 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. |
+| 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. |
-| state | [NodeInfo.State](#neo.fs.v2.netmap.NodeInfo.State) |  | Carries state of the NeoFS node |
+| state | [NodeInfo.State](#neo.fs.v2.netmap.NodeInfo.State) |  | Carries state of the FrostFS node |
 
 
 <a name="neo.fs.v2.netmap.NodeInfo.Attribute"></a>
 
 ### Message NodeInfo.Attribute
-Administrator-defined Attributes of the NeoFS Storage Node.
+Administrator-defined Attributes of the FrostFS 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 NeoFS
+last one). A string representation of the chain of attributes in FrostFS
 Storage Node configuration uses ":" and "/" symbols, e.g.:
 
-       `NEOFS_NODE_ATTRIBUTE_1=key1:val1/key2:val2`
+       `FrostFS_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
@@ -434,8 +465,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 model]
+  Node's continent name according to the [Seven-Continent
-  (https://en.wikipedia.org/wiki/Continent#Number). Calculated
+  model](https://en.wikipedia.org/wiki/Continent#Number). Calculated
   automatically from `UN-LOCODE` attribute.
 * ExternalAddr
   Node's preferred way for communications with external clients.
@@ -443,7 +474,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 NeoFS Technical Specification.
+corresponding section in FrostFS Technical Specification.
 
 
 | Field | Type | Label | Description |
@@ -464,7 +495,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 NeoFS will search for nodes alternatives to include into container's nodes subset |
+| container_backup_factor | [uint32](#uint32) |  | Container backup factor controls how deep FrostFS 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 |
@@ -522,7 +553,7 @@ hash distance.
 <a name="neo.fs.v2.netmap.NodeInfo.State"></a>
 
 ### NodeInfo.State
-Represents the enumeration of various states of the NeoFS node.
+Represents the enumeration of various states of the FrostFS node.
 
 | Name | Number | Description |
 | ---- | ------ | ----------- |
@@ -550,6 +581,7 @@ Operations on filters
 | OR | 7 | Logical OR |
 | AND | 8 | Logical AND |
 | NOT | 9 | Logical negation |
+| LIKE | 10 | Matches pattern |
 
 
  <!-- end enums -->
@@ -575,4 +607,3 @@ 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 NeoFS Technical
+Header's filed values. Please see the corresponding FrostFS Technical
 Specification section for more details.
 
 Extended headers can change `Search` behaviour:
@@ -404,16 +404,20 @@ 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 attributes
+the address of the object that is going to get patched. If the object's
-are patched, then these attrubutes must be set only within the first stream message.
+attributes are patched, then these attrubutes must be set only within the
+first stream message.
 
-If the patch request is performed by NOT the object's owner but if the actor has the permission
+If the patch request is performed by NOT the object's owner but if the
-to perform the patch, then `OwnerID` of the object is changed. In this case the object's owner
+actor has the permission to perform the patch, then `OwnerID` of the object
-loses the object's ownership after the patch request is successfully done.
+is changed. In this case the object's owner loses the object's ownership
+after the patch request is successfully done.
 
-As objects are content-addressable the patching causes new object ID generation for the patched object.
+As objects are content-addressable the patching causes new object ID
-This object id is set witihn `PatchResponse`. But the object id may remain unchanged in such cases: 
+generation for the patched object. This object id is set witihn
-1. The chunk of the applying patch contains the same value as the object's payload within the same range;
+`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;
 2. The patch that reverts the changes applied by preceding patch;
 3. The application of the same patches for the object a few times.
 
@@ -996,8 +1000,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 attribute
+  If the object is stored according to EC policy, then ec_parent
-  is set to return an id list of all related EC chunks.
+  attribute 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:
@@ -1160,7 +1164,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 NeoFS Technical Specification.
+corresponding section in FrostFS Technical Specification.
 
 
 | Field | Type | Label | Description |
@@ -1319,4 +1323,3 @@ 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 NeoFS are addressed by their ContainerID and ObjectID.
+Objects in FrostFS 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
-NeoFS container identifier. Container structures are immutable and
+FrostFS container identifier. Container structures are immutable and
 content-addressed.
 
 `ContainerID` is a 32 byte long
@@ -90,8 +90,9 @@ with/without paddings are accepted.
 <a name="neo.fs.v2.refs.ObjectID"></a>
 
 ### Message ObjectID
-NeoFS Object unique identifier. Objects are immutable and content-addressed.
+FrostFS Object unique identifier. Objects are immutable and
-It means `ObjectID` will change if the `header` or the `payload` changes.
+content-addressed. It means `ObjectID` will change if the `header` or the
+`payload` changes.
 
 `ObjectID` is a 32 byte long
 [SHA256](https://csrc.nist.gov/publications/detail/fips/180/4/final) hash of
@@ -141,7 +142,7 @@ with/without paddings are accepted.
 <a name="neo.fs.v2.refs.Signature"></a>
 
 ### Message Signature
-Signature of something in NeoFS.
+Signature of something in FrostFS.
 
 
 | Field | Type | Label | Description |
@@ -230,4 +231,3 @@ 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 NeoFS Technical Specification for details.
+section of FrostFS 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 NeoFS 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 FrostFS 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) |  | NeoFS network magic. Must match the value for the network that the server belongs to. |
+| magic_number | [uint64](#uint64) |  | FrostFS 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
-NeoFS Session Token.
+FrostFS 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 NeoFS 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 FrostFS Technical Specification for details. |
 | signature | [neo.fs.v2.refs.Signature](#neo.fs.v2.refs.Signature) |  | Signature of `SessionToken` information |
 
 
@@ -364,4 +364,3 @@ 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 NeoFS RPC protocol.
+Declares the general format of the status returns of the FrostFS RPC
-Status is present in all response messages. Each RPC of NeoFS protocol
+protocol. Status is present in all response messages. Each RPC of FrostFS
-describes the possible outcomes and details of the operation.
+protocol 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 NeoFS is unambiguously associated with the code value.
+operation in FrostFS 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 NeoFS network. Details: - [**0**] Magic number of the served NeoFS network (big-endian 64-bit unsigned integer). |
+| 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). |
 | 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 NeoFS successful return codes.
+Section of FrostFS successful return codes.
 
 | Name | Number | Description |
 | ---- | ------ | ----------- |
@@ -195,4 +195,3 @@ Section of NeoFS 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 NeoFS network.
+purged from the FrostFS network.
 
 
 | Field | Type | Label | Description |
 | ----- | ---- | ----- | ----------- |
-| 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. |
+| 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. |
 | 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,4 +60,3 @@ purged from the NeoFS 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 NeoFS are addressed by their ContainerID and ObjectID.
+// Objects in FrostFS are addressed by their ContainerID and ObjectID.
 //
 // String presentation of `Address` is a concatenation of string encoded
 // `ContainerID` and `ObjectID` delimited by '/' character.
@@ -16,8 +16,9 @@ message Address {
   ObjectID object_id = 2 [ json_name = "objectID" ];
 }
 
-// NeoFS Object unique identifier. Objects are immutable and content-addressed.
+// FrostFS Object unique identifier. Objects are immutable and
-// It means `ObjectID` will change if the `header` or the `payload` changes.
+// content-addressed. It means `ObjectID` will change if the `header` or the
+// `payload` changes.
 //
 // `ObjectID` is a 32 byte long
 // [SHA256](https://csrc.nist.gov/publications/detail/fips/180/4/final) hash of
@@ -37,7 +38,7 @@ message ObjectID {
   bytes value = 1 [ json_name = "value" ];
 }
 
-// NeoFS container identifier. Container structures are immutable and
+// FrostFS container identifier. Container structures are immutable and
 // content-addressed.
 //
 // `ContainerID` is a 32 byte long
@@ -90,7 +91,7 @@ message Version {
   uint32 minor = 2 [ json_name = "minor" ];
 }
 
-// Signature of something in NeoFS.
+// Signature of something in FrostFS.
 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 NeoFS Technical Specification for details.
+// section of FrostFS Technical Specification for details.
 service SessionService {
   // Open a new session between two peers.
   //

session/types.proto

@@ -50,7 +50,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 NeoFS container referenced by `container` field.
+    // to be stored in the FrostFS container referenced by `container` field.
     // Each element MUST have correct format.
     repeated refs.ObjectID objects = 2 [ json_name = "objects" ];
   }
@@ -88,7 +88,7 @@ message ContainerSessionContext {
   refs.ContainerID container_id = 3 [ json_name = "containerID" ];
 }
 
-// NeoFS Session Token.
+// FrostFS Session Token.
 message SessionToken {
   // Session Token body
   message Body {
@@ -126,7 +126,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
-  // NeoFS Technical Specification for details.
+  // FrostFS Technical Specification for details.
   Body body = 1 [ json_name = "body" ];
 
   // Signature of `SessionToken` information
@@ -186,7 +186,7 @@ message RequestMetaHeader {
   // `RequestMetaHeader` of the origin request
   RequestMetaHeader origin = 7 [ json_name = "origin" ];
 
-  // NeoFS network magic. Must match the value for the network
+  // FrostFS 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 NeoFS RPC protocol.
+// Declares the general format of the status returns of the FrostFS RPC
-// Status is present in all response messages. Each RPC of NeoFS protocol
+// protocol. Status is present in all response messages. Each RPC of FrostFS
-// describes the possible outcomes and details of the operation.
+// protocol 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 NeoFS is unambiguously associated with the code value.
+// operation in FrostFS 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 NeoFS successful return codes.
+// Section of FrostFS 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 NeoFS network.
+  // [**1025**] Wrong magic of the FrostFS network.
   // Details:
-  //  - [**0**] Magic number of the served NeoFS network (big-endian 64-bit
+  //  - [**0**] Magic number of the served FrostFS network (big-endian 64-bit
   //  unsigned integer).
   WRONG_MAGIC_NUMBER = 1;
 

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 NeoFS network.
+// purged from the FrostFS network.
 message Tombstone {
-  // Last NeoFS epoch number of the tombstone lifetime. It's set by the
+  // Last FrostFS epoch number of the tombstone lifetime. It's set by the
-  // tombstone creator depending on the current NeoFS network settings. A
+  // 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.