模块化治理论有三个部分。 1. 治理必须随着时间的推移而适应。单一框架无法快速、安全和便宜地适应。 2. 并非所有事物都可以由同样的人以相同的方式治理。你必须有不同的流程,由不同的人经过不同的阶段。 3. 治理应该被最小化。乐观的治理更快且更简单。自动化意味着更少的决策。不可变意味着不需要做出决策。 走模块化,抛弃单一化。使用 @AragonProject
Nick White
Nick White8月13日 23:45
There are three parts to the modular thesis, each at varying degrees of validation 1. Teams will want to launch their own chains for greater control 2. Teams will prefer to launch their chains as rollups rather than L1s bc it gives them the same level of control without the overhead 3. Teams will value secure interoperability between their apps so they’ll colocate their rollups on the same consensus and DA layer 1 is basically validated at this point. Most major apps and enterprises are launching their own chains, NOT building smart contracts on shared execution L1s. 2 is somewhat validated but many teams are still opting to do L1s over rollups. I think the tide will change here as the modular stack matures (more DA, better rollup frameworks, better interop solutions) and the market is better educated about the benefits of rollups. There’s still an L2 stigma and an L1 premium, and I think rollups are seen as riskier because they introduce more dependencies than L1s. 3 is still to be seen and may take years before it manifests but as more value is held and transacted onchain the more important it will be that these systems are as secure as possible. IMO when it happens it will be like gravity, pulling all assets and apps onto one shared security layer. TL;DR - Modular thesis is looking good here
4.83K