oceanprotocol
let publisher choose data token name & symbol
During publish we want users to choose a name & symbol for their to-be-minted data token.
I am not entirely sure we should have this in the beginning since it makes it really simple to create tokens with name & symbol which already exist, opening it up for trying to fraud people.
I am not entirely sure we should have this in the beginning since it makes it really simple to create tokens with name & symbol which already exist, opening it up for trying to fraud people.
Is this argument based on previous experience or is it of speculative nature? If you look at the marketplace today, there's many well-known projects with difficult to connect token symbols.
E.g. Datawhale's is called TREPEL-36. Dataunion's is called QUICRA-0. There's many WONPELS or WOMPATs.
I've been working with these symbols since last November, and I think it terms of usability, they've helt back major adoption of OP.
Additionally, I think a nice UX solution could be found that isn't as awkward as today's. Nobody knows what a QUICRA is.
E.g. if the marketplace team wants to discipline the publishers, why not do so in a nice way? E.g. you could allow teams to create their symbol names based on whitelisted and related terms e.g. from dictionary like:
- web
- data
- file
- ethereum
- union
- csv
Then people could chose to create the "WEBUNION-1" data set or whatever.
Another option that fraud could be prevented is by e.g. banning all existing token names. E.g. https://github.com/ethereum-lists/tokens exists, so why not disallow anyone from using one of those symbols?
trentmc added the Priority: Low label on Mar 20
I don't understand the tagging of issues according to this priority ranking. As a user, I honestly feel offended to create an issue that then gets labeled "priority: low", when my expectation rather mandates that me contributing to the repo should increase an issues priority.