From a2ff3ee377b512dc41627b259fbf05f32c7bdd35 Mon Sep 17 00:00:00 2001 From: benjmhart Date: Mon, 5 Sep 2022 20:23:26 -0400 Subject: [PATCH] standardize hardfork procedures --- proposals/standardize-hardfork-procs.md | 27 +++++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 proposals/standardize-hardfork-procs.md diff --git a/proposals/standardize-hardfork-procs.md b/proposals/standardize-hardfork-procs.md new file mode 100644 index 0000000..c9ea970 --- /dev/null +++ b/proposals/standardize-hardfork-procs.md @@ -0,0 +1,27 @@ +# Standardize HardFork Procedures +Developer Experience Working Group Proposal #X + +v0.1 + +## Preamble + +Developers urgently need to understand and repair issues arising from hardforks, to prevent community panic and reduce dApps breaking during the hardfork itself. + +## Developer Experience Concerns +As seen in the Vasil hardfork, often backwards compatibility can be overestimated, resulting in a cascade of tooling and dApp updates becoming necessary. + +Additionally, developers spend a tremendous amount of time trying to understand which tools and infrastructure work well with a given featureset. + + +## Proposed solution +It is critical that developers have clear messaging around the following: +- Testnet access +- which wallets support which testnets with which featureset +- testing period +- private-network simulation +- hardfork timelines (such as multi-stage forks as seen in Vasil) +- feature breakdowns and usage examples +- Creation of a registry where specific tools can self-report as HF compliant or HF complete once they have verified - including the dependency commits used to acheive it. + +## Additional Reading +TODO