Help

Every way to get help as a Livepeer developer: Discord channels, forum categories, office hours, GitHub issues, and bug bounty reporting.

Whether you are stuck on an API call, troubleshooting a node, reporting a security vulnerability, or looking for a collaborator, this page maps every available help channel to the type of question it handles best.

Channel reference

Channel	Best for	Response time
Discord #lounge	Builder questions, general development	Hours
Discord #ai-research	AI inference, ComfyUI, pipelines	Hours
Discord #delegating	Staking, delegation, LPT	Hours
Discord #governance	Protocol proposals, governance votes	Hours to days
Livepeer Forum	In-depth technical discussions, protocol questions	Days
Developer Office Hours	Synchronous help from the core team	Bi-weekly
GitHub Issues (go-livepeer)	Bugs in node software	Days
GitHub Issues (ai-runner)	Bugs in AI inference	Days
GitHub Issues (comfystream)	ComfyStream and real-time AI	Days
Immunefi Bug Bounty	Smart contract security vulnerabilities	Per programme terms

Discord

The Livepeer Discord is the primary real-time community for builders and network participants.

Invite: discord.gg/livepeer

BUILDERS section

#lounge is the main channel for developers. Ask questions about the API, SDKs, stream configuration, video assets, and general development. This is the most active support channel for application builders.

#ai-research is dedicated to Livepeer’s AI inference capabilities. Ask about AI pipelines, ComfyUI workflows, ComfyStream, pipeline configuration, and GPU requirements.

NETWORK section

#delegating covers questions about delegating LPT, staking rewards, choosing an orchestrator, and understanding delegation mechanics.

#orchestrating covers orchestrator and transcoder operation, including go-livepeer configuration, AI model management, and hardware.

PROTOCOL section

#governance is for discussions around Livepeer Improvement Proposals (LIPs), governance votes on the Explorer, and protocol-level decisions.

Discord is best for real-time, conversational questions. For questions that deserve a permanent, searchable answer, the Forum is a better home.

Forum

The Livepeer Forum is the permanent record for technical discussions, governance proposals, and SPE reporting.

Key categories:

• AI Research for AI pipeline questions, model support, and inference debugging
• Builder for application development questions
• Treasury for SPE proposals, RFPs, and retroactive grants
• Protocol for protocol-level discussions and LIPs

Forum posts are indexed by search engines and remain discoverable long-term. Use the forum for questions that would benefit other developers finding the same issue later.

GitHub issues

File bugs against the specific repository:

Repository	Use for
livepeer/go-livepeer	Node software, broadcaster/orchestrator behaviour, payment issues
livepeer/ai-runner	AI pipeline failures, model loading errors, inference bugs
livepeer/comfystream	ComfyStream, real-time AI, WebRTC transport
livepeer/pytrickle	PyTrickle SDK, FrameProcessor, trickle protocol
livepeer/protocol	Smart contract behaviour, on-chain governance
livepeer/docs	Documentation errors, missing content, broken links

Include: the exact error message, your request body (redact API keys), the response status and body, and the versions of any Livepeer software involved.

Security vulnerabilities

Report smart contract vulnerabilities through the Immunefi bug bounty programme. Do not report security issues in public GitHub issues. See bug bounties for programme scope and reward tiers.

For non-contract security concerns (exposed keys, infrastructure vulnerabilities), contact the team via Discord DM to a Foundation member or email [e-mail].

The job debugging page covers the specific error diagnosis flow for failed AI and video jobs.