Asset naming #27

Open
opened 2025-12-28 17:10:26 +00:00 by sami · 1 comment
Owner

Originally created by @NeoDashboard on GitHub (Mar 19, 2024).

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.

Originally created by @NeoDashboard on GitHub (Mar 19, 2024). 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.
Author
Owner

@roman-khimov commented on GitHub (Mar 19, 2024):

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 commented on GitHub (Mar 19, 2024): > 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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/fs-neo-org#27
No description provided.