-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Contributing
Besu welcomes contributions in many forms: code, documentation, raising issues, and helping others in chat.
Everything you need to decide whether and how to contribute lives in the Contributing guide (CONTRIBUTING.md) in the main repository. It covers:
- Setting up your GitHub and Discord accounts
- Choosing something to work on (good first issues and help wanted)
- The fork → branch → commit → pull request workflow
- Reporting bugs and suggesting enhancements
- Pull request and code review expectations
- The Developer Certificate of Origin (DCO), copyright, and licensing
If you just have a quick question, check the Besu documentation or ask in the Besu Discord. Please don't open an issue to ask a question.
Once you've read the contributing guide, these wiki pages go deeper on specific areas:
- Working with DCO: signing off commits and fixing DCO check failures
- Besu CLI Style Guide
- Testing
- Logging
- Building from source
besu-eth/wiki and edits made here are overwritten on the next publish. To change a page, open a pull request against the source repo instead. See Home for how.
Contributing
Development & Testing
Developing & Conventions
Project Process
Governance
Incident Reports
- 2024-01-06 Mainnet Halting Event
- 2022-11-11 Fork on Sepolia
- 2022-05-30 Phishing PRs
- 2021-08-04 Value Transfer Public Transactions Rejected
- 2021-04-23 ATs Failures
Performance & Stability
- Improvements Since the Merge
- Memory Usage Investigations (23.7.3-RC)
- Reduce Memory Usage
- Testing Taskforce Brainstorming
- Q4 2022 Stability and Improvements
- Permissioned Chain Testing
Design Documents
- Design Documents
- Modular Besu
- Refactor EVM into a Standalone Library
- Bonsai Tries Design Overview
- Bonsai Archive Feature
- Bonsai Archive State Proofs
- Switchable Consensus Parameters
- SECP256R1 Support
- RPC Endpoint Service
- Feature Proposal Template
- Feature Flags
- CI/CD Tooling and Process
Programs & Mentorship