Welcome to Recourse! We are committed to providing responsive, transparent support for developers, operators, and open-source contributors.
For questions about how Recourse works, protocol concepts, architectural decisions, or integration ideas:
- GitHub Discussions: Ask questions, share ideas, and connect with other contributors.
- If Discussions are not enabled on your view, feel free to open a GitHub Issue labeled
question.
If you encounter unexpected behavior, test failures, or bugs:
- Check existing GitHub Issues to see if the issue has already been reported.
- If not, open a new issue using the Bug Report Template.
- Please provide your environment details (OS, Node version, pnpm version, Rust version) and reproduction steps.
If you have suggestions for protocol improvements, new SDK features, or developer experience enhancements:
- Open a new issue using the Feature Request Template.
- Clearly describe the problem you want to solve and your proposed solution.
If you spot an outdated guide, unclear instructions, or missing documentation:
- Open a new issue using the Documentation Improvement Template.
- Describe what is unclear or missing and propose improvements.
If you discover a security vulnerability in smart contracts, cryptographic verification logic, or services:
- Do NOT open a public issue.
- Submit a private report through GitHub Security Advisories.
- See SECURITY.md for complete disclosure guidelines.
All official project communication, technical design discussions, issue triage, and governance happen transparently in this GitHub repository.
Recourse does not operate separate Discord, Telegram, or Slack servers for official governance or support. Any third-party channels claiming to represent official Recourse support should be treated with caution.