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

Asset naming #47

Open
NeoDashboard opened this issue Mar 19, 2024 · 1 comment
Open

Asset naming #47

NeoDashboard opened this issue Mar 19, 2024 · 1 comment
Labels
I3 Minimal impact question Further information is requested S3 Minimally significant U3 Regular

Comments

@NeoDashboard
Copy link

For me It's a bit confusing the doc is stating that Neo GAS is used for payments in NeoFS (here https://fs.neo.org/#payments).
Because in fact when you look at your balance the asset named GAS is not used but It's the one named NEOFS. And then there is a bridge between GAS (N3) <-> NEOFS (NeoFS). I'm wondering if It would be clearer is It was renamed like this:

GAS -> fsGAS (or something else)
NEOFS -> GAS

It could also solve confusion when you import NeoFS network on NEON wallet for example which is mismatching GAS/NEOFS prices due to naming. By the way It could be nice to have NeoFS mainnet/testnet available as networks on NEON by default and make It possible to import on Neoline (for now It doesn't seem to work)?
But probably there is some advantage in the current naming I didn't realize that's why I'm tagging this as a question.

@NeoDashboard NeoDashboard added question Further information is requested U3 Regular labels Mar 19, 2024
@roman-khimov
Copy link
Member

GAS -> fsGAS (or something else)

This can't be done. It's GAS in the same way testnet has GAS, it's a native token.

NEOFS -> GAS

However calling this fsGAS is something that we can think of, because "NEOFS" doesn't make much sense, we better signify that it's still GAS, just in another form (like fUSDT or wBTC). Technically, it'd be against NEP-17 though.

@roman-khimov roman-khimov added S3 Minimally significant I3 Minimal impact labels Mar 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I3 Minimal impact question Further information is requested S3 Minimally significant U3 Regular
Projects
None yet
Development

No branches or pull requests

2 participants