If you are interested in contributing to the project, we welcome and thank you. We want to make the best decentralized and effective blockchain platform available and we appreciate your willingness to help us.
The Algorand GitHub Organization has all of our open source projects, and dependencies which we fork and use in those projects. This contribution guide applies to all of these.
Some of our most active projects include:
- go-algorand - Algorand node software (this repository)
- go-algorand-sdk - Golang SDK
- java-algorand-sdk - Java SDK
- js-algorand-sdk - JavaScript SDK
- indexer - Blockchain analytics database
- ledger-app-algorand - Ledger hardware wallet application
- mule - Continuous Integration automation tool
- py-algorand-sdk - Python SDK
- sandbox - Algorand node quickstart tool
Did you discover a bug? Do you have a feature request? Filing issues is an easy way anyone can contribute and helps us improve Algorand. We use GitHub Issues to track all known bugs and feature requests.
Before logging an issue be sure to check current issues, verify that your node is synced, check the Developer Frequently Asked Questions and GitHub issues to see if your issue is described there.
If you’d like to contribute to any of the repositories, please file a GitHub issue using the issues menu item. Make sure to specify whether you are describing a bug or a new enhancement using the Bug report or Feature request button.
See the GitHub help guide for more information on filing an issue.
Please don't create issues for any security vulnerabilities. Instead, we would appreciate it if you reported them through our vulnerability disclosure form. This allows us to distribute a fix before the vulnerability is exploited.
Additionally, if you believe that you've discovered a security vulnerability, you might qualify for our bug bounty program. Visit our bug bounty site for details.
If you have any questions, don't hesitate to contact us at security@algorand.com.
For each of our repositories we use the same model for contributing code. Developers wanting to contribute must create pull requests. This process is described in the GitHub Creating a pull request from a fork documentation. Each pull request should be initiated against the master branch in the Algorand repository. After a pull request is submitted the core development team will review the submission and communicate with the developer using the comments sections of the PR. After the submission is reviewed and approved, it will be merged into the master branch of the source. These changes will be merged to our release branch on the next viable release date. For the SDKs, this may be immediate. Changes to the node software may take more time as we must ensure and verify the security, as well as apply protocol upgrades in an orderly way.
Note: some of our projects are using gitflow, for these you will open pull requests against the develop branch.
Again, if you have a patch for a critical security vulnerability, please use our vulnerability disclosure form instead of creating a PR. We'll follow up with you on distributing the patch before we merge it.
For Go code we use the Golang guidelines defined here.
- Code must adhere to the official Go formatting guidelines (i.e. uses gofmt).
- We use gofmt and golint. Also make sure to run
make sanityandmake generatebefore opening a pull request. - Code must be documented adhering to the official Go commentary guidelines.
For JavaScript code we use the MDN formatting rules.
For Java code we use Oracle’s standard formatting rules for Java.
The core development team monitors the Algorand community forums and regularly responds to questions and suggestions. Issues and Pull Requests are handled on GitHub.