the idea is creating a standard rather than a unique identifier database on Ethereum.
http://cuid.services/decode/?ETH100001
ETH100002 - ETHOS
http://cuid.services/decode/?ETH100002
What kind of standard made them choose 1 and 2 respectively? There will have to be a central resource controlling duplicate numbers.
Is 1 or 2 really important when they are unique?
If both sides use these identifiers then 'cuid' field in APIs will be a standard. We are creating a reference list, are trying to get attention, are filling a pool with unique identifiers with minimum info. Also, the information that we stored is also public information about projects.
You can check database, find a CUID which is not already listed, then request yours from Github.
Also, we are developing a smart-contract creating CUID with a call.
However, even there is smart-contract, we need a platform to gather people and work on introducing it. Or what are your possible solutions?
Maybe the first question is:
Is name/symbol conflict a problem while sharing project/market data (or defining project itself)?