Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not call main chain as mainnet #3052

Open
cthulhu-rider opened this issue Dec 13, 2024 · 1 comment
Open

Do not call main chain as mainnet #3052

cthulhu-rider opened this issue Dec 13, 2024 · 1 comment
Labels
config Configuration format update or breaking change enhancement Improving existing functionality I2 Regular impact S3 Minimally significant U4 Nothing urgent

Comments

@cthulhu-rider
Copy link
Contributor

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

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

@roman-khimov
Copy link
Member

Related to #2702/#3021, makes sense.

@roman-khimov roman-khimov added U4 Nothing urgent config Configuration format update or breaking change S3 Minimally significant I2 Regular impact labels Dec 13, 2024
@roman-khimov roman-khimov added the enhancement Improving existing functionality label Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
config Configuration format update or breaking change enhancement Improving existing functionality I2 Regular impact S3 Minimally significant U4 Nothing urgent
Projects
None yet
Development

No branches or pull requests

2 participants