i miss the ability or infos about the issuer of assets
can he pay out dividends to owner of the assets
can there be pre defined rules for the dividend behavior of the asset?
can the N of M multisig logic be used for the issuer of assets
and and and
wana know more about mosaics
if there is some more info available already please link me to it
Good to see you around here.
![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
Let me try to answer your questions.
For sure in this version an asset owner can manually quickly scan the blockchain, create some new dividends and then send out the bonuses to each holder. That is no problem to do, but hasn't been automated in version 1 to make it done in one click. Although a person could easily write a script to do it. Mosaics will have more versions after this version with more functions, so that can be something that is added to NCC and fully automated, but will be later.
M of N is very important throughout NEM and definitely is enabled already in mosaics.
There is no real information about Mosaics, so I just made a story for you. But first please read the old post explaining Namespaces which explains how the naming system works for Mosaics.
Hi Guys,
It is my pleasure to introduce you to Namespaces on NEM!
A domain name is required when making an asset on NEM (that asset function is called NEM Mosaics and will be explained more later). Each individual who wishes to create a mosaic needs to register a root domain name. This domain name can be thought of very much like a website domain and in NEM is known as a
namespace. This can be bought for an amount of XEM (to be defined later). The namespace length shall be limited to 16 alphanumeric characters.
A creator owning the root domain namespace can create as many sub-domains as wanted, using a convention similar to the Java namespace convention, i.e., separated by a dot “.” to represent a domain or subdomain and an asterisk surrounded by a space on each side “ * ” to represent the name of an asset. This is the current internal convention in NIS and how it is represented later in the NIS and/or NCC UI might differ. This gives the creator a practically limitless number of mosaics that can be defined within a practically limitless number of sub-domains. The sub-levels of a namespace can act as the actual name of the asset, or in some cases can be a class of assets as it is itself a sub-domain with lots of assets under that sub-domain name. This means that last part of a mosaic will always be the name of the individual asset on the NEM blockchain and the prior names will act as the domain and/or subdomain for that asset.
![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fs23.postimg.org%2F7vm1uzoqj%2Fsub_namespace2c.png&t=665&c=r5nr9gcAaGqI5g)
In the above example there are 6 assets. They are as follows:
1. jabo38.jeffsilver * halfounce
2. jabo38.jeffsilver * ounce2015
3. jabo38 * iposhares
4. jabo38.exchange * usd
5. jabo38.exchange * eur
6. jabo38.exchange * zar
In the first example the domain is
jabo38.jeffsilver and the asset is
halfounce. In the second example the domain is
jabo38.jeffsilver and the asset is
ounce2015. And in the third example the domain is
jabo38 and the asset is
iposhares.
While the first part of a namespace is globally unique on the NEM blockchain, the rest of the parts of a namespace are not. Having non-unique sub-domains in a namespace system allows for anyone to use any name in the subdomain positions, making squatting on certain names far less exclusive as they are not globally unique, and at the same time giving chances for easily recognizable names within one’s personal local network.
Now, on to a story created for you. Lets say a user name kryptonit who loves diamonds is interested in Mosaics. (I saw you profile but didn't want to exactly copy you. hehehe)
He knows he is in the diamond business and wants blockchain representation for these diamonds. Maybe the blockchain tokens will be digital assets for speculation on the price of diamonds, or maybe they will be certificates of existence, or maybe they will be used to help track the diamonds as they are moved from place to place. At anyrate, kryptonit needs some blockchain based tokens.
First, he goes into NEM and buys the namespace "kryptonit_inc" for his business.
Second, he knows his business will be very successful and have a lot of lines so he creates a sub namespace "summer2015assets".
Third, he creates his first line of mosiacs for red laser diamonds. It ended up being very successful so he needed more.
Fourth, he finally created is fifth line of red laser diamonds. Now he has decided to move on.
Fifth, in the winter he opens up a sub namespace for his new line "winter2016assets".
Sixth, he creates a mosaic for "blue_diamonds"
Seventh, there was a mistake at his factory and instead he ended up with 150,000 extra diamonds that he didn't know about, so he amends the total amount in that particular mosaic and adds those numbers. (could have destroyed them too if it was a bad mistake)
This is an example of a transferable mutable mosaic, but we can also have non transferable and fixed rate mosaics too, as well as being able to send mosaics in bags. I'll try to explain those a bit later a long with other interesting things Mosaics can do.
![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fs25.postimg.org%2F4jkcc1f7z%2Fmosaicskrypto.png&t=665&c=AS_szJ4Nrly2KA)
The above examples can also be seen on the
testnet NEMbex which Gimre just updated yesterday and is still working on more and updating.
Mosaics is being designed not to just be an IPO asset feature for scam coins and pumps, but is being designed for real world businesses to use in their daily operations. It is by far the most feature rich asset creation platform in crypto.
As mentioned above the first version of Mosaics allows the following:
Divisibility – Up to 6 decimal points.
Quantity – Either mutable, fixed, or capped.
Transferability – Asset can be locked into only being traded with the creator and the first person it was sent to, or it can be transferred to anyone.
Descriptions – An explanation about the asset.
Packagability – Assets can be bagged together with other assets
Name and Namespace – Assets will be a part of an advanced naming system on NEM
Data – Assets can be sent with messages