The source project of this merge request has been removed.
Update chip to move it forward
- Updates language to be more formal in many places,
- added further clarification on risk and costs,
- included reference to repurposing by external actor if we do not enforce it.
- included historical information on usage,
- added a stakeholder section,
- added additional statements,
- updated the proposal details (unsure about quality, please review),
- set myself as co-owner (not sure if this is the right way, please review)
and probably a handful of more things I might've forgot.
Edited by Jonathan Silverblood
Merge request reports
Activity
Note that this is marked as draft and I'm requesting review since I am not a technical consensus / full node developer.
If I made some misstake, help me do it better and I'll update.
There is also at least one statement that I expect to update the text for (josh green) once I get a more clear statement to use.
- Resolved by Jonathan Silverblood
- Resolved by Jonathan Silverblood
- Resolved by Jonathan Silverblood
- Resolved by Jonathan Silverblood
- Resolved by Jonathan Silverblood
- Resolved by Jonathan Silverblood
- Resolved by Jonathan Silverblood
- Resolved by Jonathan Silverblood
- Resolved by Jonathan Silverblood
added 1 commit
- 07af788e - Fix incorrect reference to handling, to instead reference parsing.
added 1 commit
- ec6f184b - Simplify note about current state and include a clear list of valid numbers as...
Please register or sign in to reply