User:George: Difference between revisions
Jump to navigation
Jump to search
Add placeholder AZ guidelines |
No edit summary |
||
| Line 14: | Line 14: | ||
# Is the change accompanied by user facing documentation? | # Is the change accompanied by user facing documentation? | ||
# Is there clear direction on upgrade/deprecation path? (spork vs hardfork vs etc) | # Is there clear direction on upgrade/deprecation path? (spork vs hardfork vs etc) | ||
## Is there a communication plan with third-party ecosystem providers? (e.g CEX) | |||
==== Performance Changes ==== | ==== Performance Changes ==== | ||
Latest revision as of 17:57, 27 November 2024
Contact
matrix: @georgezgeorgez:hc1.chat
Maintainer guidelines
go-zenon
Protocol Changes
- Do the changes follow an implementation neutral specification?
- Is there proof that a supermajority of validators want the change?
- Is the change well tested? (unit testing, functional and performance testing on testnets)
- Is the change accompanied by user facing documentation?
- Is there clear direction on upgrade/deprecation path? (spork vs hardfork vs etc)
- Is there a communication plan with third-party ecosystem providers? (e.g CEX)
Performance Changes
- Does the change meet one of the following:
- Improves average performance
- Improves situational performance AND does not worsen average performance
- Given that most performance considerations require trade-offs, it should not be necessary to prove that a performance change does not worsen situational performance
- Is there clear direction on upgrade/deprecation path? (data migrations vs resync vs etc)
Misc/QoL
- Is there clear direction on upgrade/deprecation path? (api lifecycle vs etc)
AZ Voting Guidelines
WIP