For now I think we are all stuck with upgrades being controlled by a single source of control, like Maker and rDAI, which publish documentation to record the history of changes. But even that would introduce lots of systemic risk. My jerk reaction is that this is only useful in a specific application that includes permission-based "cut" control. I'm curious to see how this intersects with governance. You've clearly put a lot of thought into it, and it is very well written. This looks interesting, albeit very ahead of it's time. (Putting discussion here since I don't see an external link) I'm confused are you trying to make a new EIP? I think you need to add the proper table to the top of this file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |