FIP0001 - specs update process #678
Replies: 2 comments 1 reply
-
Side note that spec reconciliation is also a challenge in other protocols like Ethereum (which move slower than Filecoin). The current published yellow paper captures Berlin and is 6 hard forks behind Paris (currently live). https://ethereum.github.io/yellowpaper/paper.pdf Solving this efficiently will IMO require a dedicated spec maintenance squad that works in the background. Synchronously throttling the FIP innovation process on FIP authors updating the spec (esp. in the state it's in today) is shooting ourselves in the foot. |
Beta Was this translation helpful? Give feedback.
-
Let's remove this requirement from FIP-0001 since it was DOA, and start a thread on spec update/maintenance? This can be crowdsourced IMO -- a good model is Ethereum Cat Herders. |
Beta Was this translation helpful? Give feedback.
-
FIP0001 states:
currently the last commit to the
master
branch of the specs repo was made on May 25th 2022!How is this supposed to be handled? There seem to be a lot of FIPs not represented in the specs at the current point in time.
Seeking clarification here about at what point the specs need to be updated to represent the implementation of a FIP.
Beta Was this translation helpful? Give feedback.
All reactions