This document describes where to get help with the Invoice Liquidity Network protocol and which channels are actually live ahead of mainnet.
Last audited: 2026-09-24.
| Channel | Status | Use for |
|---|---|---|
| GitHub Issues (bug / feature / component templates) | Live | Bugs, feature requests, tracked work |
| GitHub Security Advisories (private) | Intended path — needs owner action | Vulnerabilities only. Private vulnerability reporting currently returns 404 for non-collaborators, so an owner must enable it; see Enabling Private Vulnerability Reporting (Owner Only) and SECURITY.md |
| Security email | None working — do not use | security@invoice-liquidity-network.local is undeliverable (.local is multicast-DNS-only) and security@invoiceliquidity.network has no DNS records. Each address is audited in Contact Status; do not mail an address found in an older document |
| GitHub Discussions | Not enabled yet on this repository | Planned for open-ended integration Q&A after launch readiness; until then use Issues |
| Discord / other chat | Out of scope pre-launch | Not stood up; do not treat as an official channel |
Scoped decision: For mainnet launch readiness we treat GitHub Issues + private security reporting as the complete public support surface. Standing up Discord (or enabling Discussions) is optional post-launch community work, not a launch blocker once Issues templates and this doc are accurate.
Report bugs by opening a GitHub issue:
Choose the template that matches the component you are having trouble with. Include steps to reproduce, expected behaviour, and actual behaviour.
GitHub Discussions are not enabled on this repository yet. Until they are:
- Open a GitHub Issue using the feature request template for new functionality, or a bug template if something is broken
- Tag maintainers via CODEOWNERS on a draft PR if you are proposing an integration change
When Discussions are enabled, this section will be updated and the checklist row will stay in sync.
Suggest new features or improvements via the feature request template.
Protocol incidents are handled under
incident-response-runbook.md. There is no separate
public status Discord; user-facing notices go through GitHub (issues/advisories)
and release notes.
| Channel | Expected Response |
|---|---|
| Bug reports (GitHub Issues) | Acknowledged within 3 business days |
| Integration / feature Issues | Best-effort, typically within 1 week |
| Security (private) | Per SECURITY.md (ack within 48 hours) |
These are targets, not guarantees. Response times may vary based on maintainer availability and issue complexity.
Do not report security vulnerabilities through public GitHub issues. See SECURITY.md for responsible disclosure instructions, including the private GitHub Security Advisory channel, the acknowledgment window, and the embargo terms. ILN has no working security email at the time of writing — Contact Status records which addresses are broken and which one an owner still has to confirm, so do not mail a security address found in an older document.