Skip to main content

Support Channels

Need help with Salud? Here’s how to get support from the community and developers.

GitHub Issues

The primary support channel for Salud is GitHub Issues.

Before Creating an Issue

Check existing issues first:
  1. Search existing issues to see if your problem has already been reported
  2. Check closed issues for solutions to similar problems
  3. Review the Troubleshooting Guide for common solutions

Creating a New Issue

If you didn’t find a solution, create a new issue:
1

Go to GitHub Issues

2

Choose Issue Type

Select the appropriate template:
  • Bug Report: For reporting bugs or errors
  • Feature Request: For suggesting new features
  • Documentation: For documentation improvements
  • Question: For general questions
3

Provide Detailed Information

Include the following in your issue:For Bug Reports:
  • Clear description of the problem
  • Steps to reproduce the issue
  • Expected behavior vs actual behavior
  • Error messages (if any)
  • Screenshots or screen recordings (if applicable)
  • Environment details:
    • Operating system
    • Node.js version (node --version)
    • Browser and version
    • Frontend/backend versions
  • Whether you’re using Demo Mode or blockchain mode
For Feature Requests:
  • Description of the feature
  • Use case and why it would be valuable
  • Proposed implementation (if you have ideas)
Example Bug Report:
## Description
Unable to create medical records - getting "Failed to create record" error

## Steps to Reproduce
1. Connect wallet with private key
2. Click "New Record" button
3. Fill in all fields
4. Click Submit
5. Error appears

## Expected Behavior
Record should be created and appear in the records list

## Actual Behavior
Error message: "Failed to create record"

## Error Messages
Backend console shows:
Error: Insufficient credits

## Environment
- OS: macOS 14.0
- Node.js: v18.17.0
- Browser: Chrome 120.0
- Mode: Blockchain (not demo mode)
- Balance: 0 credits

## Screenshots
[Attach screenshot of error]
4

Submit and Monitor

  • Submit your issue
  • Watch for responses from maintainers and community
  • Provide additional information if requested
  • Test proposed solutions and report results

Aleo Community

For questions about the Aleo blockchain, Leo programming language, or general Aleo development:

Aleo Discord

Join the Aleo Community Discord for:
  • General Aleo blockchain questions
  • Leo programming language help
  • Testnet support and faucet requests
  • Community discussions
  • Network status updates

Join Aleo Discord

Connect with the Aleo developer community

Aleo Resources

Aleo Documentation

Official Aleo developer documentation

Leo Language Docs

Learn the Leo programming language

Aleo SDK

Aleo SDK documentation and examples

Aleo Explorer

View transactions and blocks on Aleo

Contributing

Want to help improve Salud? Contributions are welcome!

How to Contribute

1

Fork the Repository

Fork the Salud repository to your GitHub account
2

Create a Feature Branch

git checkout -b feature/your-feature-name
3

Make Your Changes

  • Follow existing code style and conventions
  • Add tests for new features
  • Update documentation as needed
  • Test your changes thoroughly
4

Submit a Pull Request

  • Push your branch to your fork
  • Create a pull request with a clear description
  • Reference any related issues
  • Wait for review and address feedback

Contribution Guidelines

Code Quality:
  • Write clean, readable code
  • Follow TypeScript/JavaScript best practices
  • Add comments for complex logic
  • Ensure all tests pass
Documentation:
  • Update README if adding features
  • Document new API endpoints
  • Add inline code comments
  • Update user guides if needed
Testing:
  • Test in both Demo Mode and blockchain mode
  • Test on different browsers
  • Verify mobile responsiveness
  • Check for console errors

Security Issues

Found a security vulnerability? DO NOT create a public GitHub issue.

Reporting Security Vulnerabilities

Security issues should be reported privately to protect users.
To report a security issue:
  1. Create a private security advisory on GitHub in the SALUD-MVP repository
  2. Include:
    • Description of the vulnerability
    • Steps to reproduce
    • Potential impact
    • Suggested fix (if you have one)
  3. Wait for response before disclosing publicly
  4. Coordinate disclosure timing with maintainers

Security Best Practices

When using Salud:
  • Never share your private key
  • Store private keys in secure password managers
  • Use hardware wallets for production use
  • Keep dependencies updated
  • Review code before self-hosting
  • Use HTTPS in production

Documentation Feedback

Found an issue with the documentation?

How to Provide Feedback

Report Documentation Issues

Report errors or suggest improvements

Edit on GitHub

Submit a pull request with fixes
Documentation improvements welcome for:
  • Typos or grammar errors
  • Outdated information
  • Missing or unclear explanations
  • Additional examples or tutorials
  • Translation to other languages

Response Times

What to expect:
ChannelExpected Response Time
GitHub Issues1-3 business days
Pull Requests3-7 business days
Security IssuesWithin 24 hours
Aleo DiscordCommunity-driven (varies)
Salud is an open-source project maintained by volunteers. Response times may vary based on maintainer availability.

Self-Help Resources

Before reaching out for support, try these resources:

Installation Guide

Setup and configuration instructions

Troubleshooting

Common issues and solutions

FAQ

Frequently asked questions

API Reference

Technical API documentation

Community Guidelines

When participating in the Salud community:
  • Be respectful and professional
  • Stay on topic in discussions
  • Search before asking to avoid duplicates
  • Provide context when asking for help
  • Share solutions if you find them
  • Help others when you can
  • Give credit to contributors
  • Follow the code of conduct

Stay Updated

Stay informed about Salud updates:
  • Watch the GitHub repository for releases
  • Star the project to show support
  • Follow discussions and announcements
  • Subscribe to release notifications

Thank you for being part of the Salud community!

Build docs developers (and LLMs) love