The creation of channel is a one time process and as such is recommended to do it either from EPNS dApp, EPNS JS library or a custom JS library of your choice. Information about the channel payload specs is described here.
Interfacing directly via smart contract to protocol to create a channel can also be done by calling it
with public key registry function
createChannelWithFeesAndPublicKey(ChannelType _channelType, bytes calldata _identity, bytes calldata _publickey) external
without public key registry function
createChannelWithFees(ChannelType _channelType, bytes calldata _identity)
The type of channel to create
The identity field consists of the following parameters joined together with a delimiter.
Payload type not only indicates the content of notification but also the storage implementation stored.
Indicates the hash of the payload through which payload data can be obtained.
Pass the publickey of the wallet in bytes
Non Interest Bearing, Protocol Reserved Channel for Information
Special Interest Bearing Protocol Reserved Opt in Channel for Promotion
Interest Bearing, Open Channel
Interest Bearing, Mutual Channel
Represents storage on IPFS with letters Qm happen to correspond with the algorithm (SHA-256) and length (32 bytes) used by IPFS.