Channels

Channels are group conversations organized around a topic. They work similarly to Discord channels or Telegram groups — a shared space where multiple users can send and read messages. Each channel has a unique numeric ID, a permanent slug, a display name, and a type (public or private).

1 Channel Types

There are two types of channels in Ogmara:

  • Public — Anyone can join, and all messages are visible to everyone. Public channels appear in the channel list and can be found by browsing or searching.
  • Private — Invite-only. Messages are visible only to members. Private channels do not appear in the public channel list — you need an invite link to join.

2 Joining a Channel

To join a public channel, browse the channel list in the sidebar and click or tap on any channel that interests you. You will be added as a member immediately and can start reading and sending messages.

For private channels, you need an invite link from an existing member or the channel owner. Open the link, and you will be added to the channel.

3 Creating a Channel

Creating a channel requires an on-chain registration on the Klever blockchain, which costs approximately 4.8 KLV. This one-time cost ensures that channel slugs are globally unique and permanently reserved.

To create a channel:

  1. Choose a slug — This is the URL-friendly name for your channel (for example, rust-devs or klever-news). The slug is permanent and cannot be changed after creation, so choose carefully.
  2. Set the display name and description — These are what users see in the channel list. Unlike the slug, you can update these at any time.
  3. Choose public or private — Decide whether anyone can join or only invited members.

When you confirm, the slug is registered on the Klever blockchain through a smart contract call. This guarantees uniqueness across the entire network — no two channels can ever have the same slug.

Important: The slug cannot be changed or transferred after creation. Double-check the spelling before confirming the transaction.

You must have a registered on-chain identity to create channels. If you have not registered yet, see the Wallet & Identity tutorial.

4 Finding Your Channel ID

Every channel is assigned a permanent numeric ID when it is created (for example, 42). You will need this ID when configuring bots, setting up dashboard alerts, or using the API. There are three ways to find it:

Method 1: Channel Settings

Open the channel, then open Channel Settings. The Channel ID is displayed near the top of the settings panel, along with a copy button to copy it to your clipboard.

Method 2: URL Bar

In the web app, look at your browser's address bar. The URL follows the pattern /app/#/chat/{channel_id} — the number at the end is your channel ID. For example, if the URL is /app/#/chat/42, your channel ID is 42.

Method 3: REST API

Query the node's REST API to get a list of channels with their IDs:

GET /api/v1/channels?page=1&limit=20

The response includes a channel_id field for each channel. This is especially useful when you need to look up multiple channel IDs at once or integrate with external tools.

The channel ID is assigned permanently at creation time and never changes. You can safely hard-code it in bot configurations and API integrations.

5 Channel Settings and Moderation

The channel owner has full control over channel settings and moderation:

  • Update channel info — Change the display name, description, and logo at any time.
  • Add or remove moderators — Grant trusted members the ability to moderate the channel.

Moderators can remove messages from display. Because Ogmara is decentralized, content is not deleted from the network — instead, moderation works at the client level by filtering out flagged messages. This keeps the network censorship-resistant while still giving channel owners tools to maintain quality.

6 Pinned Channels (Node Operators)

If you run an Ogmara node, you can pin specific channels in your node configuration. Pinned channels are always stored and served by your node, regardless of how active they are. This is useful for ensuring that important channels are reliably available on your node, even during periods of low activity.

See the Run a Node tutorial for details on node configuration, including how to set pinned channels.