For example, I send NEM’s mosaic A to someone.
Is there a way to prove that mosaic A has been issued in the past (existence) is to search the mosaic A issued transaction from the vast amount of past transaction history?
First of all, I make a mistake that my explanation is hard to understand.
I want to know how to prove that a mosaic exists.
For example, I make a mosaic and send it to someone.
How can a recipient know how things that have been sent are legitimately made mosaics?
My idea is to refer to the transaction that mosaic was issued.
However, I think that it is very inefficient to refer to the transaction every time you do a mosaic transaction.
My other idea is that recipients just trust.
Transmission transactions are effective only when approved, so we think that mosaic is correct as long as it is approved.
But then, only new doubts are born.
The question is, “How do you prove the existence of that mosaic at the time of approval work?”
At the time of the approval work, are they searching for a transaction in which the mosaic was generated from a huge number of transactions in the past?
Or is it impossible to send unauthorized mosaic due to the mechanism of the blockchain?
Still not sure what you want to know but it’s not possible to send not existing mosaic. Also is not possible to send it if you don’t own it.
Mosaic can be worth nothing (in terms of price) but you need be owner to send it. Also recipient will see it if it’s received (for example explorer view in nanowallet) and after that it will be possible to send it.
For example, when the “dollar” is used, the American central bank guarantees that it is legitimate.
Then, if you issue a mosaic called “dollar” under the namespace “America” in NEM, I would like to know how to guarantee that it is legitimate.
I think that you can confirm that it is legitimate by checking the transaction that issued the “dollar”, but I think that it is inefficient to check each transaction each time.
And what you mean by legitimate? And what guarantess you central bank?
If some company issue mosaic best:mosaic it will be worth as many as people want pay for it. If Company X and use case is legit then it will be worth more (or not).
There is nothing to do on blockchain level. Blockchain ensures you that Company Y can’t issue same best:coin (because namespace is unique) and sell this fake on exchange.
Not sure if this answers your question.
Thanks
I may not have understood well even by myself.
I will investigate a little more and think.
I want to ask another one.
Do you know how to manage unique namespace?
While someone owns it, that namespace can not be acquired by others.
If it is the system so far, it is managed by the DB of the central administrator (company).
How do you manage blockchains?
About legitimate of mosaic. Blockchain ensures you that total amount of coins never exceed total supply and one object (mosaic instance) can belong to one address at some point of time.
You should read about NEM (and general) blockchain more. It’s distributed network of nodes. Each node has own (synchronized with other nodes) state. If someone will try introduce namespace with same name it will be rejected by network.
I can see that the same namespace is rejected from the network.
I want to know the mechanism of the refusal.
I’ve been doing mijin 's node, etc.
I have read a lot of documents, but I don’t know what to use to judge whether it is already being used or not.
I don’t know if I don’t know well what you want to know about, or you don’t know the answer.
However, even if we continue discussion here as it is, there seems to be no answer,
I will investigate myself and try.
Thanks for everything.
Not sure why you want to know if it’s used or not. If it will be used network will reject when you try create it.
If you want check if it exists you can do it in nanowallet (there is namespaces search) or directly using api call:
https://nemproject.github.io/#retrieving-root-namespaces
If you want know process how it will be rejected you must read more about blockchain and consensus algorithms. NEM tech ref also should be helpful > https://nem.io/NEM_techRef.pdf
Thx
After summarizing my idea, I may question again.
Please close this topic. Thank you.