Broadcasts and Message Channels
Our next asset type is a message channel, and we cannot talk about message channels without first talking about broadcasts, and we can't talk about broadcasts without talking about messages. It is important to note that asset broadcasts and message channels are rarely used and their use-case has not been solidified by the community.
Asset Messages
Any user can send an asset message on any asset that they own. An asset message is 34 bytes long and is seen as directed to the asset recipient.
Asset Broadcasts
In an asset transaction, if the sending address is the same as the receiving address, this is seen as a broadcast. Only message channels can broadcast messages. It is important to note that the user interface for message broadcasts do not seem to be fully implemented in the core wallet yet.
Message Channels
A message channel requires a main or sub-asset's ownership asset. A message channel is an asset specifically made for broadcasting messages. Their purpose is to add more control to whoever might be subscribed to the message channel's parent.
| Metadata | Information |
|---|---|
| Asset Name | The message channel portion of the name must at most 12 characters. It can contain letters, numbers, and '_'. '_' cannot be at the beginning or end of the message channel portion and two or more '_''s cannot be next to each other. The message channel asset name takes the form [main or sub asset name]~[message channel portion]. This full name must be 30 or less characters. |
| Ownership Asset | Message channel assets have no associated ownership asset |
| Prerequisites | A main asset or sub-asset's ownership asset |
| Asset Amount | 1 of this asset can be created |
| Cost | 4 YERB |
| Reissuability | This asset cannot be reissued |
| Divisibility | Divisibility is 0 |
| Associated Data | This asset cannot have associated data |