diff --git a/blogPosts/en/blog/Editorial/arranging-participation.mdx b/blogPosts/en/blog/Editorial/arranging-participation.mdx index 6654a3192f..0d792a7801 100644 --- a/blogPosts/en/blog/Editorial/arranging-participation.mdx +++ b/blogPosts/en/blog/Editorial/arranging-participation.mdx @@ -23,7 +23,7 @@ We gathered a great deal of creativity and intellect, and then often put people It is that very same activation energy which makes facilitation hard, because we come in with the expectation that listening to Vitalik speak is more valuable than talking to a stranger. This is obviously untrue if you’ve ever had a meaningful conversation with someone you don’t know, or have tried to follow one of Vitalik’s random tangents, but we are misled by the evolutionary machinery in our brains which is highly attuned to social status. -Good facilitation breaks the expectation that the most value you can get from an hour is in listening to high status people by gently weaving everyone into smaller conversations likely to prove meaningful, and reminding people that you’re far better off reading [vitalik.ca](https://vitalik.ca/) or listening to [Bankless](https://www.bankless.com/listen) if you really want to learn from those kind of people. +Good facilitation breaks the expectation that the most value you can get from an hour is in listening to high status people by gently weaving everyone into smaller conversations likely to prove meaningful, and reminding people that you’re far better off reading [vitalik.eth.limo](https://vitalik.eth.limo/) or listening to [Bankless](https://www.bankless.com/listen) if you really want to learn from those kind of people. We need to orient people towards each other, rather than at a perceived authority. This amounts to rewiring our perception of who and what is valuable, which is exactly the same work we do when we write meaningful economic code capable of [incentivising different social structures](/learn/module-5/incentives). diff --git a/content/cn/start/principled-people.mdx b/content/cn/start/principled-people.mdx new file mode 100644 index 0000000000..870212849a --- /dev/null +++ b/content/cn/start/principled-people.mdx @@ -0,0 +1,82 @@ +--- +title: Kernel 原则 +order: 0 +featuredImage: images/shares/giving.png +description: 首当其冲，Kernel 是关于组成更好网络的人以及我们所共享的心灵品质。 +--- + +# Kernel 原则 + +Kernel 的主要目标很简单：**一起学习**。我们通过精心设计的同伴学习环境以实现它。在创造这样的环境时，我们遵循两个原则，一个针对 "web3"，另一个更个人化： + + + +**不伤害** + +**玩，永无止境** + + + +根据这两个核心追求，我们可以衍生出 16 个更细致的原则。 + + + + + +### ⌛️ Web3 原则 + +1. 信任不仅限于交易。 +2. 共享的真相创造价值。 +3. 学习限制，然后自由。 +4. 货币即言论。 +5. 激励影响一切。 +5. 解放激进的机构。 +7. 在经济上抵制审查。 +8. 使能力规模化。 + + + + + +### 🌈 个人化原则 + +1. 把玩模式。 +2. 开发工具，抵达意义。 +3. 提出更好的问题。 +4. 首先考虑你的意图。 +5. 听更好的故事，讲更好的故事。 +6. 在一起时，个体就能够很好地治理。 +7. 学习如何爱上学习。 +8. 给予神圣。 + + + + + +## 遇见 Kernel 伙伴们 + +. + + + + + + + +## 先给予 + +在这里我们为彼此服务，因为我们是彼此的环境。真正的服务也引导我们走向任何有意义的自我认知的目标：实际上，没有所谓的他者。 + +我们还有一个共同的外部目标：**支持自由货币的持续创造**。在这个背景下，Kernel 是一份礼物。它确实源于此：Vivek 开始回馈一个曾赋予他生计和宝贵成长经历的社区。Andy 开始为 Vivek 提供实现这一愿景的教育模式。每一期 Kernel 都是由各种才华横溢的人精心打造的，我们独特，但有着与周围世界分享天赋的共同愿望。这是一种老派生活方式依然跳动的心脏，我们正慢慢将其带入数字世界。 + +我们相互学习，奉献自己，直到自我和他者失去那种常常主宰其间互动的分离感。在这个过程中，有一种无法被给予或接受的真相。只有在你开始信任自己已有的价值时，它才会在你心中生根发芽。 + +## 项目与团队 + +. + + + + + + diff --git a/content/en/build/regeneration/phoenix.mdx b/content/en/build/regeneration/phoenix.mdx index 70c69fc398..82e9c47da8 100644 --- a/content/en/build/regeneration/phoenix.mdx +++ b/content/en/build/regeneration/phoenix.mdx @@ -90,7 +90,7 @@ _“A tree is in a forest, but there is also a forest in each tree.”_ -“[The boundary between multiple intersecting worlds is the most interesting palace to be](https://vitalik.ca/general/2020/12/28/endnotes.html)”, and a great part of the art of conversation with trees revolves around managing these edges carefully, dancing to the different music–birdsong, pollinators, livestock, flowers, brambles, and sprouts–which fills them in each season. Care for the edges is how one can create fractals; whether it is the care one takes to measure coastlines, or the care with which one cultivates sunflowers. Logan learns this repeatedly in all the different places he visits: +“[The boundary between multiple intersecting worlds is the most interesting palace to be](https://vitalik.eth.limo/general/2020/12/28/endnotes.html)”, and a great part of the art of conversation with trees revolves around managing these edges carefully, dancing to the different music–birdsong, pollinators, livestock, flowers, brambles, and sprouts–which fills them in each season. Care for the edges is how one can create fractals; whether it is the care one takes to measure coastlines, or the care with which one cultivates sunflowers. Logan learns this repeatedly in all the different places he visits: > “It was a way to make edges, and edges within edges, multiplying the conditions in the landscape, so creatures that loved different habitats all could thrive. This landscape of dynamic edges has recently been dubbed _satoyama_, marking the interface between town and mountain.” diff --git a/content/en/learn/module-4/consensus.mdx b/content/en/learn/module-4/consensus.mdx index ebb56f0c39..3bf37e34b4 100644 --- a/content/en/learn/module-4/consensus.mdx +++ b/content/en/learn/module-4/consensus.mdx @@ -212,7 +212,7 @@ Sheer number of people or votes **does not determine consensus**. What is problematic now is that consensus is "called" by a chair, which is a position of authority we cannot afford if we are to build truly decentralized systems. However, it's exactly the authority conferred by the formal position of "chair" which gives individuals the power to **get work done** once all technical objections have been addressed. So how are we to balance the lack of authority with our need to move forward along the most fertile paths? -The proposed solutions to this question generally take the form of some kind of distributed and dynamic reputation system, because [reputation gives certain individuals the legitimacy required](https://vitalik.ca/general/2021/03/23/legitimacy.html) to shift conversations and social conventions. This is a necessary and salient point to acknowledge in the social protocols and culture which inform any system of technical governance. Where there are shadow hierarchies, there is abuse and inefficiency, and so individuals must be aware of the regard in which they are held within their chosen communities and respond accordingly. We [state elsewhere](https://sign.kernel.community/essay) that the idea for any kind of leader - read: host, or server - is to give away their importance without shirking responsibility. +The proposed solutions to this question generally take the form of some kind of distributed and dynamic reputation system, because [reputation gives certain individuals the legitimacy required](https://vitalik.eth.limo/general/2021/03/23/legitimacy.html) to shift conversations and social conventions. This is a necessary and salient point to acknowledge in the social protocols and culture which inform any system of technical governance. Where there are shadow hierarchies, there is abuse and inefficiency, and so individuals must be aware of the regard in which they are held within their chosen communities and respond accordingly. We [state elsewhere](https://sign.kernel.community/essay) that the idea for any kind of leader - read: host, or server - is to give away their importance without shirking responsibility. However, we can perhaps turn to some economics for other sustainable and resilient solutions. The old idea is "running code and rough consensus". However, the code we now all run establishes consensus, and makes money (literally). So, rather than having a single chair who specifies which path is best to follow for the whole working group, why not have as many working groups as we can currently fund by means of our shared code? We can even program non-linear funding mechanisms which also act as on-chain economic signals of support - as we saw with [EIP-1559](https://gitcoin.co/grants/946/eip-1559-community-fund) - in order to determine collectively the best technical outcomes. @@ -308,7 +308,7 @@ What Constitutes Consensus? - + Applied to Blockchains diff --git a/content/en/learn/module-4/governance.mdx b/content/en/learn/module-4/governance.mdx index 6e23d3ee17..1495950c8e 100644 --- a/content/en/learn/module-4/governance.mdx +++ b/content/en/learn/module-4/governance.mdx @@ -56,7 +56,7 @@ Help each other. ## Rough consensus -Anarchy does not mean the tyranny of structurelessness. To us, it means individuals collaborating of their own volition on projects they choose to undertake. It means emergent forms of organisation that need not be permanent, because they arise as a response to the needs of a group in a particular moment. Being able to program incentives and the flow of value through society means we don't have to hold static popularity contests every four years, premised on partisan debates: we can govern dynamically by continuously modelling, assessing and updating our understanding of [legitimacy](https://vitalik.ca/general/2021/03/23/legitimacy.html). +Anarchy does not mean the tyranny of structurelessness. To us, it means individuals collaborating of their own volition on projects they choose to undertake. It means emergent forms of organisation that need not be permanent, because they arise as a response to the needs of a group in a particular moment. Being able to program incentives and the flow of value through society means we don't have to hold static popularity contests every four years, premised on partisan debates: we can govern dynamically by continuously modelling, assessing and updating our understanding of [legitimacy](https://vitalik.eth.limo/general/2021/03/23/legitimacy.html). The best example of this kind of internet age governance is, unsurprisingly, the [IETF](/learn/module-4/consensus): diff --git a/content/en/learn/module-4/liberal-radical.mdx b/content/en/learn/module-4/liberal-radical.mdx index 26f805b22d..855bfd3629 100644 --- a/content/en/learn/module-4/liberal-radical.mdx +++ b/content/en/learn/module-4/liberal-radical.mdx @@ -147,25 +147,25 @@ Multidisciplinary Approaches - + Grants Round 9: The Next Phase - + Grants Round 7 Retrospective - + Grants Round 6 Analysis - + Grants Round 5 Analysis diff --git a/content/en/learn/module-4/self-enquiry.mdx b/content/en/learn/module-4/self-enquiry.mdx index dd1cc5a7a2..1bc7dfb034 100644 --- a/content/en/learn/module-4/self-enquiry.mdx +++ b/content/en/learn/module-4/self-enquiry.mdx @@ -202,7 +202,7 @@ Pseudonymous. -In [response to an essay entitled, “On the Limits of Cryptoeconomics”](https://vitalik.ca/general/2021/09/26/limits.html#finance-is-the-absence-of-collusion-prevention), Vitalik argues that finance is a set of patterns which naturally emerge in systems that do not prevent collusion. Hence, many aspects of social media have become financialized, precisely because the limits of what is transactional and what is not are never clearly defined. It’s a fascinating question: does the introduction of economic code lead to the hyper-financialization of everything, or does it allows us to create more clear delineations around what is transactional and what exceeds the transactional such that we can better avoid the kinds of [collusion](https://vitalik.ca/general/2019/04/03/collusion.html) which tend to develop in systems that do no actively disincentivise certain behaviours? +In [response to an essay entitled, “On the Limits of Cryptoeconomics”](https://vitalik.eth.limo/general/2021/09/26/limits.html#finance-is-the-absence-of-collusion-prevention), Vitalik argues that finance is a set of patterns which naturally emerge in systems that do not prevent collusion. Hence, many aspects of social media have become financialized, precisely because the limits of what is transactional and what is not are never clearly defined. It’s a fascinating question: does the introduction of economic code lead to the hyper-financialization of everything, or does it allows us to create more clear delineations around what is transactional and what exceeds the transactional such that we can better avoid the kinds of [collusion](https://vitalik.eth.limo/general/2019/04/03/collusion.html) which tend to develop in systems that do no actively disincentivise certain behaviours? Kei’s point is that accounts–especially multi-signature ones–enable portable, group-based identities which persist irrespective of the application in which they are used. In this sense, you’re not dependent on any single platform: you depend on the cryptography which secures your keys knowing that those keys can be used in multiple different interfaces. Portable identities make it easier to experiment with different incentives, because one person’s “collusion” is another person’s “healthy market” and it seems unlikely that we will ever reach universal agreement on an exact set of behaviours which is either desirable or undesirable. Rather, we can persist (pseudonymous, communal) identities in the medium itself and create many different interfaces, each of which define and protect against collusion on their own terms, allowing communities to pick and choose what works for them and their unique context. diff --git a/content/en/learn/module-5/prosocial-value.mdx b/content/en/learn/module-5/prosocial-value.mdx index 9b79f60cff..dce4aad298 100644 --- a/content/en/learn/module-5/prosocial-value.mdx +++ b/content/en/learn/module-5/prosocial-value.mdx @@ -93,7 +93,7 @@ formalisms. Though these are toy economies, and have well-defined boundaries with the real world, we can still build meaningful relationships between virtual objects. These elements originate mostly -in systems theory and include: tokens, sources, pools, sinks and +in systems theory and include: tokens, sources, pools, sinks and transforms, agents like the player, and "black boxes". Together, these elements and agents can be used to model the entire internal economy, and balance our games with the correct incentive structures. @@ -274,7 +274,7 @@ players), and coordination games are every bit as popular as other kinds. If there are infinite resources, won't we just have imbalanced economies? -> It is important to internalize that as a game economy designer, you control the sources, the sinks and the narrative justification for why the world works as it does. Scarcity as well as abundance are aesthetic choices. +> It is important to internalize that as a game economy designer, you control the sources, the sinks and the narrative justification for why the world works as it does. Scarcity as well as abundance are aesthetic choices. There are arbitrary per player caps, or per group caps, or transaction costs, or sinks that can achieve balanced incentive structures. Again, the mapping from games to the real world is not exact: diff --git a/content/en/learn/module-6/censorship-resistance.mdx b/content/en/learn/module-6/censorship-resistance.mdx index ce43b5d879..7a57fab305 100644 --- a/content/en/learn/module-6/censorship-resistance.mdx +++ b/content/en/learn/module-6/censorship-resistance.mdx @@ -62,7 +62,7 @@ Quasi Turing-complete object models (i.e. Ethereum) already provide interesting censorship costly outside the actual consensus mechanism. For instance, we prevent the Halting Problem and denial of service attacks by assigning a "gas" cost to each operation and limiting the amount of gas per block to ensure all programs terminate. Much Ethereum 2.0 research is about -both higher fault tolerance +both higher fault tolerance and stronger censorship resistance based on more complete threat models and cost analysis. Such research and implementation indicate why economic engineering is orders of magnitude more effective than legal lip-service. diff --git a/content/en/learn/module-6/serenity.mdx b/content/en/learn/module-6/serenity.mdx index db512a1b28..abe935641d 100644 --- a/content/en/learn/module-6/serenity.mdx +++ b/content/en/learn/module-6/serenity.mdx @@ -384,7 +384,7 @@ The Beacon Book - + The Limits to Blockchain Scalability diff --git a/content/en/resources/research.mdx b/content/en/resources/research.mdx index f2e9f0fce3..e903848185 100644 --- a/content/en/resources/research.mdx +++ b/content/en/resources/research.mdx @@ -395,7 +395,7 @@ _H/T Roshan Raghupathy_ **PLONK** -Enjoy two for the price of one with the PLONK paper by the AZTEC team and Vitalik’s comments. +Enjoy two for the price of one with the PLONK paper by the AZTEC team and Vitalik’s comments. diff --git a/content/en/tokens/token-studies/rocket-pool.mdx b/content/en/tokens/token-studies/rocket-pool.mdx index 4c14f1db72..8b50a66312 100644 --- a/content/en/tokens/token-studies/rocket-pool.mdx +++ b/content/en/tokens/token-studies/rocket-pool.mdx @@ -53,7 +53,7 @@ This is what it all looks like [mapped out visually](https://www.figma.com/file/ The fact that I need to stake RPL when becoming a node operator is what generates ongoing demand. -The act of staking it means there is a good “[token sink](https://vitalik.ca/general/2017/10/17/moe.html)” in the protocol. +The act of staking it means there is a good “[token sink](https://vitalik.eth.limo/general/2017/10/17/moe.html)” in the protocol. The fact that my stake in RPL is what insures the protocol against potential slashing events is what makes it intrinsically critical to the proper functioning of the whole system. diff --git a/content/en/tokens/tokenomics/nouns.mdx b/content/en/tokens/tokenomics/nouns.mdx index a143ce9942..a3504133a6 100644 --- a/content/en/tokens/tokenomics/nouns.mdx +++ b/content/en/tokens/tokenomics/nouns.mdx @@ -16,7 +16,7 @@ This conversation revolves around Non-Fungible Tokens for the first time in the ### Additional Resources -1. This article on [legitimacy](https://vitalik.ca/general/2021/03/23/legitimacy.html) will provide useful context. +1. This article on [legitimacy](https://vitalik.eth.limo/general/2021/03/23/legitimacy.html) will provide useful context. 2. The NounsDAO monorepo is one of the best there is. The auction house is forked from Zora, the ERC721 from OpenZepellin (with some small but well thought-out and documented changes), the governance from Compound. Take a look at [this contract in particular](https://github.com/nounsDAO/nouns-monorepo/blob/master/packages/nouns-contracts/contracts/governance/NounsDAOLogicV1.sol) if you're a developer. ## Group Work diff --git a/content/es/build/outsmarting-contracts/reenter-the-kingdom.mdx b/content/es/build/outsmarting-contracts/reenter-the-kingdom.mdx new file mode 100644 index 0000000000..b281677a28 --- /dev/null +++ b/content/es/build/outsmarting-contracts/reenter-the-kingdom.mdx @@ -0,0 +1,42 @@ +--- +title: Volviendo a entrar al reino +order: 4 +hideLanguageSelector: false +featuredImage: images/shares/learn.png +--- + +# Volviendo a entrar al reino + +## Porqué + +Hemos aprendido las formas básicas en que podemos atacar los smart contracts. Hemos implementado nuestros propios contratos para practicar opuestos complementarios en público. Hemos profundizado en el almacenamiento público y permanente de todas las cosas. Ahora es el momento de recurrir a la vulnerabilidad más clásica que existe y volver a entrar conscientemente en el truco que casi lo desentraña todo. + +Jugaremos por el trono, subiremos al último piso y volveremos a firmar un contrato para reclamarlo todo. Este es realmente el clímax. ¿Quién diría que los smart contracts podrían presentar una telenovela tan dramática? + +## Preparación + +1. Asegúrate de que todavía le quede algo de Sepolia ETH en su cuenta. +2. Lee sobre el truco de DAO. +3. Siéntate y respira tranquilamente durante al menos 20 minutos. Utiliza esta [música](https://www.youtube.com/watch?v=g_LNp8xY1YM) si te ayuda. O [este](https://www.youtube.com/watch?v=b5H3b_Hh0Lw). + +## Aplicación + +Vamos a investigar hacks más avanzados que utilizan funciones alternativas (o la falta de ellas) y patrones en funciones que no protegen adecuadamente contra ellas. También veremos algunas armas de fuego más en Solidity, como modificadores de alcance engañosos e interfaces de interferencia. + +Al redactar algunos contratos de ataque más avanzados, aprenderás a escribir tus propios contratos y a hacerlo de forma más segura, al mismo tiempo. Si el tiempo lo permite, también echaremos un vistazo al depurador de Remix e intentaremos realizar una llamada de función para rastrear lo que sucede en el EVM. + +## Resumen + +En esta sesión habrás aprendido: + +1. Formas más complejas de utilizar funciones alternativas para explotar código deficiente. +2. Qué tipo de patrones evitar al redactar tus propios contratos. +3. Cómo utilizar más funciones de Remix para ayudarte en tu propio desarrollo. +4. Por qué leer código es un asunto de múltiples capas y cuán matizada es realmente la confianza. +5. Cómo pensar en el tipo de patrones lógicos que los buenos desarrolladores tienen por costumbre. + +## Grabación + +