Welcome to the OP Stack Specs #182
tynes
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is the place for technical discussion of the OP Stack. We strive to increase legibility of the OP Stack by working in public.
Check out the discussions for longer form conversations and the issues for open ideas about future improvements to the protocol. Feel free to comment and contribute your own ideas!
All changes to the OP Stack must be specified here before they are implemented. If you would like to contribute to the OP Stack, it is recommended to start by contributing to existing ideas before coming up with your own independent ideas. This can be done by finding an open issue that is interesting and improving it. If there is general consensus on the spec, then that greatly improves the chances of the implementation being accepted.
Specs are important because they help people know exactly what they are going to build ahead of time. It also lets us know which parts of the system the feature touches so that its easier to schedule different upgrades to the system. Specs can also help with code review when they include invariants.
One important cultural tenant of OP Stack development is to give more than you take. Please give sufficient context if you are asking questions as its not scalable to respond to nuanced questions when little effort is put in when asking them.
Beta Was this translation helpful? Give feedback.
All reactions