*: get rid of "sidechain"

Use "FS chain" everywhere.

Signed-off-by: Roman Khimov <roman@nspcc.ru>

accounting/service.proto

@@ -9,7 +9,7 @@ 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 FS chain via
 // other NeoFS nodes to get information about the account balance. Deposit and
 // Withdraw operations can't be implemented here, as they require Mainnet NeoFS
 // smart contract invocation. Transfer operations between internal NeoFS
@@ -27,7 +27,7 @@ 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 FS chain `Balance` smart
   // contract. If omitted, client implementation MUST set it to the request's
   // signer `OwnerID`.
   message Body {

container/service.proto

@@ -11,32 +11,32 @@ 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
-// equivalently by directly issuing transactions and RPC calls to sidechain
+// in FS chain via other NeoFS nodes. All of those actions can be done
+// equivalently by directly issuing transactions and RPC calls to FS chain
 // nodes.
 service ContainerService {
   // `Put` invokes `Container` smart contract's `Put` method and returns
-  // response immediately. After a new block is issued in sidechain, request is
-  // verified by Inner Ring nodes. After one more block in sidechain, the container
+  // response immediately. After a new block is issued in FS chain, request is
+  // verified by Inner Ring nodes. After one more block in FS chain, the container
   // is added into smart contract storage.
   //
   // Statuses:
   // - **OK** (0, SECTION_SUCCESS): \
-  //   request to save the container has been sent to the sidechain;
+  //   request to save the container has been sent to FS chain;
   // - Common failures (SECTION_FAILURE_COMMON).
   rpc Put(PutRequest) returns (PutResponse);
 
   // `Delete` invokes `Container` smart contract's `Delete` method and returns
-  // response immediately. After a new block is issued in sidechain, request is
-  // verified by Inner Ring nodes. After one more block in sidechain, the container
+  // response immediately. After a new block is issued in FS chain, request is
+  // verified by Inner Ring nodes. After one more block in FS chain, the container
   // is added into smart contract storage.
   // NOTE: a container deletion leads to the removal of every object in that
   // container, regardless of any restrictions on the object removal (e.g. lock/locked
   // object would be also removed).
   //
   // Statuses:
   // - **OK** (0, SECTION_SUCCESS): \
-  //   request to remove the container has been sent to the sidechain;
+  //   request to remove the container has been sent to FS chain;
   // - Common failures (SECTION_FAILURE_COMMON).
   rpc Delete(DeleteRequest) returns (DeleteResponse);
 
@@ -59,12 +59,12 @@ service ContainerService {
   rpc List(ListRequest) returns (ListResponse);
 
   // Invokes 'SetEACL' method of 'Container` smart contract and returns response
-  // immediately. After one more block in sidechain, changes in an Extended ACL are
+  // immediately. After one more block in FS chain, 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;
+  //   request to save container eACL has been sent to FS chain;
   // - Common failures (SECTION_FAILURE_COMMON).
   rpc SetExtendedACL(SetExtendedACLRequest) returns (SetExtendedACLResponse);
 
@@ -93,7 +93,7 @@ service ContainerService {
 // 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
+  // separate field. It's not stored in FS chain, just verified on container
   // creation by `Container` smart contract. `ContainerID` is a SHA256 hash of
   // the stable-marshalled container strucutre, hence there is no need for
   // additional signature checks.
@@ -300,7 +300,7 @@ message SetExtendedACLRequest {
 message SetExtendedACLResponse {
   // `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.
+  // storage after next block is issued in FS chain.
   message Body { }
 
   // Body of set extended acl response message.

netmap/service.proto

@@ -10,7 +10,7 @@ import "refs/types.proto";
 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
+// required to build it. The resulting `Network Map` is stored in FS chain
 // `Netmap` smart contract, while related information can be obtained from other
 // NeoFS nodes.
 service NetmapService {
@@ -103,7 +103,7 @@ message NetworkInfoRequest {
 }
 
 // Response with NetworkInfo structure including current epoch and
-// sidechain magic number.
+// FS chain magic number.
 message NetworkInfoResponse {
     // Information about the network.
     message Body {

netmap/types.proto

@@ -290,7 +290,7 @@ message NetworkConfig {
   //   Number of EigenTrust algorithm iterations to pass in the Reputation system.
   //   Value: little-endian integer. Default: 0.
   // - **EpochDuration** \
-  //   NeoFS epoch duration measured in Sidechain blocks.
+  //   NeoFS epoch duration measured in FS chain blocks.
   //   Value: little-endian integer. Default: 0.
   // - **HomomorphicHashingDisabled** \
   //   Flag of disabling the homomorphic hashing of objects' payload.
@@ -323,10 +323,10 @@ message NetworkInfo {
     // Number of the current epoch in the NeoFS network
     uint64 current_epoch = 1 [json_name = "currentEpoch"];
 
-    // Magic number of the sidechain of the NeoFS network
+    // Magic number of FS chain of the NeoFS network
     uint64 magic_number = 2 [json_name = "magicNumber"];
 
-    // MillisecondsPerBlock network parameter of the sidechain of the NeoFS network
+    // MillisecondsPerBlock network parameter of FS chain of the NeoFS network
     int64 ms_per_block = 3 [json_name = "msPerBlock"];
 
     // NeoFS network configuration

object/service.proto

@@ -11,7 +11,7 @@ import "session/types.proto";
 import "status/types.proto";
 
 // `ObjectService` provides API for manipulating objects. Object operations do
-// not affect the sidechain and are only served by nodes in p2p style.
+// not affect FS chain and are only served by nodes in P2P style.
 service ObjectService {
   // Receive full object structure, including Headers and payload. Response uses
   // gRPC stream. First response message carries the object with the requested address.

proto-docs/accounting.md

@@ -35,7 +35,7 @@
 <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 FS chain via
 other NeoFS nodes to get information about the account balance. Deposit and
 Withdraw operations can't be implemented here, as they require Mainnet NeoFS
 smart contract invocation. Transfer operations between internal NeoFS
@@ -78,7 +78,7 @@ 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 FS chain `Balance` smart
 contract. If omitted, client implementation MUST set it to the request's
 signer `OwnerID`.
 

proto-docs/container.md

@@ -62,8 +62,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
-equivalently by directly issuing transactions and RPC calls to sidechain
+in FS chain via other NeoFS nodes. All of those actions can be done
+equivalently by directly issuing transactions and RPC calls to FS chain
 nodes.
 
 ```
@@ -80,13 +80,13 @@ rpc AnnounceUsedSpace(AnnounceUsedSpaceRequest) returns (AnnounceUsedSpaceRespon
 #### Method Put
 
 `Put` invokes `Container` smart contract's `Put` method and returns
-response immediately. After a new block is issued in sidechain, request is
-verified by Inner Ring nodes. After one more block in sidechain, the container
+response immediately. After a new block is issued in FS chain, request is
+verified by Inner Ring nodes. After one more block in FS chain, the container
 is added into smart contract storage.
 
 Statuses:
 - **OK** (0, SECTION_SUCCESS): \
-  request to save the container has been sent to the sidechain;
+  request to save the container has been sent to FS chain;
 - Common failures (SECTION_FAILURE_COMMON).
 
 | Name | Input | Output |
@@ -95,16 +95,16 @@ Statuses:
 #### Method Delete
 
 `Delete` invokes `Container` smart contract's `Delete` method and returns
-response immediately. After a new block is issued in sidechain, request is
-verified by Inner Ring nodes. After one more block in sidechain, the container
+response immediately. After a new block is issued in FS chain, request is
+verified by Inner Ring nodes. After one more block in FS chain, the container
 is added into smart contract storage.
 NOTE: a container deletion leads to the removal of every object in that
 container, regardless of any restrictions on the object removal (e.g. lock/locked
 object would be also removed).
 
 Statuses:
 - **OK** (0, SECTION_SUCCESS): \
-  request to remove the container has been sent to the sidechain;
+  request to remove the container has been sent to FS chain;
 - Common failures (SECTION_FAILURE_COMMON).
 
 | Name | Input | Output |
@@ -139,12 +139,12 @@ Statuses:
 #### 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
+immediately. After one more block in FS chain, 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;
+  request to save container eACL has been sent to FS chain;
 - Common failures (SECTION_FAILURE_COMMON).
 
 | Name | Input | Output |
@@ -457,7 +457,7 @@ New NeoFS Container creation request
 
 ### Message PutRequest.Body
 Container creation request has container structure's signature as a
-separate field. It's not stored in sidechain, just verified on container
+separate field. It's not stored in FS chain, just verified on container
 creation by `Container` smart contract. `ContainerID` is a SHA256 hash of
 the stable-marshalled container strucutre, hence there is no need for
 additional signature checks.
@@ -540,7 +540,7 @@ Set Extended ACL
 ### 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.
+storage after next block is issued in FS chain.
 
 
  <!-- end messages -->

proto-docs/netmap.md

@@ -53,7 +53,7 @@
 
 ### Service "neo.fs.v2.netmap.NetmapService"
 `NetmapService` provides methods to work with `Network Map` and the information
-required to build it. The resulting `Network Map` is stored in sidechain
+required to build it. The resulting `Network Map` is stored in FS chain
 `Netmap` smart contract, while related information can be obtained from other
 NeoFS nodes.
 
@@ -220,7 +220,7 @@ NetworkInfo request body is empty.
 
 ### Message NetworkInfoResponse
 Response with NetworkInfo structure including current epoch and
-sidechain magic number.
+FS chain magic number.
 
 
 | Field | Type | Label | Description |
@@ -321,7 +321,7 @@ System parameters:
   Number of EigenTrust algorithm iterations to pass in the Reputation system.
   Value: little-endian integer. Default: 0.
 - **EpochDuration** \
-  NeoFS epoch duration measured in Sidechain blocks.
+  NeoFS epoch duration measured in FS chain blocks.
   Value: little-endian integer. Default: 0.
 - **HomomorphicHashingDisabled** \
   Flag of disabling the homomorphic hashing of objects' payload.
@@ -355,8 +355,8 @@ Information about NeoFS network
 | Field | Type | Label | Description |
 | ----- | ---- | ----- | ----------- |
 | current_epoch | [uint64](#uint64) |  | Number of the current epoch in the NeoFS 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 NeoFS network |
+| magic_number | [uint64](#uint64) |  | Magic number of FS chain of the NeoFS network |
+| ms_per_block | [int64](#int64) |  | MillisecondsPerBlock network parameter of FS chain of the NeoFS network |
 | network_config | [NetworkConfig](#neo.fs.v2.netmap.NetworkConfig) |  | NeoFS network configuration |
 
 

proto-docs/object.md

@@ -72,7 +72,7 @@
 
 ### Service "neo.fs.v2.object.ObjectService"
 `ObjectService` provides API for manipulating objects. Object operations do
-not affect the sidechain and are only served by nodes in p2p style.
+not affect FS chain and are only served by nodes in P2P style.
 
 ```
 rpc Get(GetRequest) returns (stream GetResponse);