Hey there! We’re stoked to hear that you’re interested in contributing to Bitcoin Layers. Here’s a few immediate needs where we need support.
We think we have a pretty good handle on the risk assessments. But, an extra set of eyes is always helpful. If you have a technical understanding on how Bitcoin scaling protocols operate, please consider joining on our telegram chat and ask which risk assessments are in the “review” stage. You can also review our published risk assessments here.
Defining L2s can seem like an impossible job. We’re confident in our definitions and risk framework, but acknowledge that it can be improved in some areas. If you have thoughts on our framework, please consider joining our telegram chat and offering feedback.
We host weekly community calls and are considering expanding to more community-centric content. We would need someone to take really in-depth notes during more structured calls to ensure that community members who could not attend can stay up to date. If someone wanted to completely own this role, the time commitment would be 4-5 hours a month. We currently host/coordinate community calls in our telegram chat.
A lot of the new “L2s” that are popping up are similar to Ethereum rollups / validiums / optimiums. If you have a technical understanding of these protocols, and would like to review some of their implementations in the Bitcoin space, please join our telegram so we can coordinate which reviews you can take on :)
We’re going to start hosting opinion pieces on our blog. If you’d like to write a blog related to Bitcoin scaling infrastructure, and have it featured on our site, let us know!
Not every contribution can be measured by GitHub commits. Simply jumping into our chat and being a part of the discussion is super valuable and appreciated. You may also be able to contribute to a project in a capacity that is not listed here. If that's the case, let us know. :)
Follow existing variable and file naming standards, and make sure to run npm run format to format with prettier.