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

Naming for the Implemention #9458

Open
HardenedSteel opened this issue Aug 27, 2024 · 2 comments
Open

Naming for the Implemention #9458

HardenedSteel opened this issue Aug 27, 2024 · 2 comments

Comments

@HardenedSteel
Copy link

We need to make disambiguation for the Monero C++ implementation. It causes confusion between the implementation(s) and the network.

This will also be useful when Cuprate is released.

So how we should refer to the Monero C++ implementation? Monerod? Monero Core? MoneroC++?

@SyntheticBird45
Copy link
Contributor

In general, the reference implementation of a cryptocurrency is called Core. And Core generally include node + wallet. So I think there is no disambiguation:

Core software is the reference implementation of monero, which includes monerod (The monero daemon/node) and monero-wallet-cli/gui (The reference wallet implementation)

I wouldn't be worry about cuprate since the deamon will be named cuprated. get it? cuprate daemon. Hard to be confused.

@HardenedSteel
Copy link
Author

HardenedSteel commented Aug 27, 2024

monerod is still confusing, Monero is the currency's name not the software implementation of Monero. These both should be disambiguated

Referring as Monero Core sounds good to me.

Look at this blog post; Monero 0.18.3.4 'Fluorine Fermi' released. Releasing Monero? How this is even possible? We should say Monero core 0.18.3.4 released and when cuprate releases in future we would say Cuprate x.x.x released.

Monero GUI and CLI also should be named but these are different issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants
@HardenedSteel @SyntheticBird45 @0xFFFC0000 and others