Do not call main chain as `mainnet` #1299

New issue

Open

opened 2025-12-28 17:22:30 +00:00 by sami · 1 comment

sami commented

2025-12-28 17:22:30 +00:00

Owner

Originally created by @cthulhu-rider on GitHub (Dec 13, 2024).

inspired by https://github.com/nspcc-dev/neofs-node/pull/3038

NeoFS runs above two chains - main and FS ones. And there is a public NeoFS network - NeoFS Mainnet. Sometimes main chain-related stuff is called mainnet. Like here nspcc-dev/neofs-node@474d5413f8/config/example/ir.yaml (L99)

this is legit for NeoFS Mainnet itself, but confuses me in general

i propose to call main chain as main chain (mainchain where appropriate) everywhere where it is not NeoFS Mainnet itself that is meant (like https://github.com/nspcc-dev/neofs-node/tree/master/config/mainnet). With this, there will be main and FS chains pair instead of mainnet and FS chain

old configs must keep working ofc

Originally created by @cthulhu-rider on GitHub (Dec 13, 2024). * inspired by https://github.com/nspcc-dev/neofs-node/pull/3038 NeoFS runs above two chains - main and FS ones. And there is a public NeoFS network - [NeoFS Mainnet](https://status.fs.neo.org/). Sometimes main chain-related stuff is called _mainnet_. Like here https://github.com/nspcc-dev/neofs-node/blob/474d5413f894149457526057584d2f52133e06f7/config/example/ir.yaml#L99 this is legit for NeoFS Mainnet itself, but confuses me in general i propose to call main chain as `main chain` (`mainchain` where appropriate) everywhere where it is not NeoFS Mainnet itself that is meant (like https://github.com/nspcc-dev/neofs-node/tree/master/config/mainnet). With this, there will be _main and FS chains_ pair instead of _mainnet and FS chain_ old configs must keep working ofc