From a traditional development perspective, blockchain protocols indeed require more standardized processes. Generally speaking, any protocol-level changes should be announced 3 to 6 months in advance to inform the community, allowing contributors enough time to understand and review, and making it easier to collect the relevant CLA signatures.
Of course, not having all the information makes it difficult to draw definitive conclusions. However, from an engineering standards perspective, taking these steps early on is always the right approach.
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
12 Likes
Reward
12
2
Repost
Share
Comment
0/400
ThreeHornBlasts
· 12-20 17:55
Isn't it all like this? Announcing in advance can indeed avoid a lot of trouble.
View OriginalReply0
Tokenomics911
· 12-20 17:40
Bro is right, announcing this in advance is indeed important, otherwise the community will always be caught off guard.
From a traditional development perspective, blockchain protocols indeed require more standardized processes. Generally speaking, any protocol-level changes should be announced 3 to 6 months in advance to inform the community, allowing contributors enough time to understand and review, and making it easier to collect the relevant CLA signatures.
Of course, not having all the information makes it difficult to draw definitive conclusions. However, from an engineering standards perspective, taking these steps early on is always the right approach.