Kind describes the kind of transaction as a "/" tuple.
The domain acts as a namespace for the concreate type. Right now we use "bns",
"ethereum", "lisk" and "rise" for chain-specific transactions. We also use the
special domain "bcp" for any kind that can be supported in multiple chains.
This should be used for type detection only and not be encoded somewhere. It
might be migrated to a Java-style package names like "io.lisk.mainnet" or
other way of namespacing later on, so don't use the kind property as a value.
Kind describes the kind of transaction as a "/" tuple.
The domain acts as a namespace for the concreate type. Right now we use "bns", "ethereum", "lisk" and "rise" for chain-specific transactions. We also use the special domain "bcp" for any kind that can be supported in multiple chains.
This should be used for type detection only and not be encoded somewhere. It might be migrated to a Java-style package names like "io.lisk.mainnet" or other way of namespacing later on, so don't use the
kindproperty as a value.