Connect Discord

Connect Discord in the Provider Portal so renters can invite you into private pod support channels. Without a connected provider Discord account, renters see Provider has not connected Discord on pods running on your machines and cannot create the shared channel from the pod detail page. Subnet incentives for rented and idle nodes go to providers whose connected Discord account is a member of the Lium Discord server.

Discord and extra incentives

Subnet incentives go to providers whose Discord account is connected in the Provider Portal and is a member of the Lium Discord server. The rule covers both incentive pools: the rented pool while a node is rented and the unrented pool while it is idle. It applies to every node on your provider account. The Overview and Nodes pages show a notice while your account has no Discord connected.

Connecting adds your account to the Lium Discord server. Lium re-reads each account's membership at most once an hour. While the connected account is outside the server, your nodes earn 0 from both pools each epoch, and their job logs carry the reason provider_discord_not_connected. When Discord cannot answer the membership check, your nodes keep earning.

To earn again, rejoin the Lium Discord server with the connected account, or disconnect Discord and connect it again in Profile Settings (click Disconnect Discord, then Connect Discord); connecting adds the account back to the server. Pay resumes in stages: Lium re-reads membership within 60 minutes, the validator picks that up in its next 15-minute check, and weights are set at the next tempo, about 72 minutes later. Allow up to about 2.5 hours. The first payment after you rejoin is partial; the full share returns one tempo later.

Rental fees that renters pay for active GPU usage reach your coldkey as usual. See Getting Paid.

Connect your provider account

1. Sign in to provider.lium.io.
2. Open Profile Settings.
3. Find the Discord section.
4. Click Connect Discord.
5. Approve the Discord OAuth prompt.
6. Return to the Provider Portal and confirm the Discord section shows Connected.

The Provider Portal stores your Discord user ID on your provider profile. The support channel flow uses that ID to grant you access to channels for pods rented from your machines.

Connect from the CLI

After logging in with the provider CLI:

lium provider portal login
lium provider config connect-discord

The CLI opens the Discord authorization URL when possible. On a headless machine or in an agent workflow, use:

lium provider config connect-discord --json --no-wait

Open the returned authorization_url as the Discord account owner and approve the OAuth prompt. Check readiness with:

lium provider status --json

Look for discord_connected: true and extra_incentive_eligible: true.

Disconnect Discord

Use Disconnect Discord from the same Discord section if you need to unlink the account. After disconnecting, new renter support channels cannot include you until you connect Discord again.

How renter support channels work

When a renter clicks Request Discord Support on a pod detail page:

1. Lium checks that the renter has connected Discord.
2. Lium checks that the provider assigned to that pod has connected Discord.
3. Lium creates a private Discord text channel under the configured Lium support category, or returns the existing pod channel if one already exists.
4. Lium grants channel access to the renter, the provider, and the configured support role.
5. Lium posts a pod context message with the pod ID, machine details, Docker image, ports, SSH command, hardware, price, and location.

The channel name is generated from the pod name and pod ID. The channel is stored on the pod record, so a repeated support request reopens the same channel.

When the pod is removed, Lium attempts to delete the stored Discord channel during pod cleanup.

Open the channel yourself

You can open the channel yourself. On your node's page in the Provider Portal, the Pod Statuses table has a Discord icon on every rented pod: click it to open the pod's support channel — say, to warn the renter before a maintenance window. It is the same channel the renter's Request Discord Support button creates, with the same members, so whoever opens it first, the other side lands in the same place; clicking again returns the existing channel. The icon tells you why it cannot open one: Connect Discord in Profile Settings when your own account is not linked, or Renter has not connected Discord — a channel needs both sides, so reach that renter through Lium support instead. Only the renter's opt-out can stop you: a renter who has turned off incoming support connections refuses channels you open; they can still open one themselves, and you land in it. A provider-side opt-out, when one is offered, refuses channels renters open; it never stops you opening one.

Troubleshooting

Issue	What to check
Connect Discord fails immediately	The Provider Portal backend Discord OAuth configuration may be missing. Contact Lium support.
OAuth returns Discord Connection Failed	Retry the connection. If it repeats, contact Lium support with the error shown in the notification.
The portal says Discord is connected but renters still cannot request support	Confirm the pod is running on a machine owned by the same provider hotkey that has Discord connected.
You cannot see a support channel after a renter says they requested one	Confirm you are signed in to Discord with the connected account. If you recently disconnected/reconnected, ask the renter to retry from the pod detail page.