You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: public/content/contributing/translation-program/translators-guide/index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -122,7 +122,7 @@ The best way to handle links is to copy them directly from the source, either by
122
122
123
123
124
124
125
-
Links also appear in the source text in the form of tags (i.e. \<0>\</0>). If you hover over the tag, the editor will show its full content - sometimes these tags will represent links.
125
+
Links also appear in the source text in the form of tags (i.e. `<0>``</0>`). If you hover over the tag, the editor will show its full content - sometimes these tags will represent links.
126
126
127
127
It is very important to copy the links from the source and not change their order.
The source text also contains shortened tags, which only contain numbers, meaning that their function is not immediately obvious. You can hover over these tags to see exactly which function they serve.
162
162
163
-
In the example below, you can see that hovering over the \<0> tag shows that it represents `<code>` and contains a code snippet, therefore the content inside these tags should not be translated.
163
+
In the example below, you can see that hovering over the `<0>` tag shows that it represents `<code>` and contains a code snippet, therefore the content inside these tags should not be translated.
164
164
165
165
| <Tagvariant="solid"status="error">DAO</Tag> |[2022 DAO Research Update: What do DAO Builders Need?](https://blog.aragon.org/2022-dao-research-update/)|
36
-
| <Tagstatus="error">DeFi</Tag> |[The state of Defi 2024](https://stateofdefi.org/) (ongoing survey) |
| <Tagstatus="error">DeFi</Tag> |[ConSensys: DeFi User Research Report 2022](https://cdn2.hubspot.net/hubfs/4795067/ConsenSys%20Codefi-Defi%20User%20ResearchReport.pdf)|
39
38
| <Tagvariant="solid">Metaverse</Tag> |[Metaverse: User Research Report](https://www.politico.com/f/?id=00000187-7685-d820-a7e7-7e85d1420000)|
@@ -45,7 +44,6 @@ This is a curated list of user research done in web3 that may help with design a
-[Web3 Design Principles](https://medium.com/@lyricalpolymath/web3-design-principles-f21db2f240c1) - A framework of UX rules for blockchain based dapps
47
46
-[Blockchain Design Principles](https://medium.com/design-ibm/blockchain-design-principles-599c5c067b6e) - Lessons learned by the blockchain design team at IBM
48
-
-[W3design.io](https://w3design.io/) - A curated library of UI flows of different projects in the ecosystem
49
47
-[Neueux.com](https://neueux.com/apps) - UI library of user flows with diverse filtering options
50
48
-[Web3's Usability Crisis: What You NEED to Know!](https://www.youtube.com/watch?v=oBSXT_6YDzg) - A panel discussion on pitfalls of developer focused project building (video, 34 min)
51
49
@@ -72,7 +70,6 @@ Get involved in professional community-driven organizations or join design group
[Hoare Logic](https://en.wikipedia.org/wiki/Hoare_logic) provides a set of formal rules for reasoning about the correctness of programs, including smart contracts. A Hoare-style property is represented by a Hoare triple \{_P_}_c_\{_Q_}, where _c_ is a program and _P_ and _Q_ are predicates on the state of the _c_ (i.e., the program), formally described as _preconditions_ and _postconditions_, respectively.
73
+
[Hoare Logic](https://en.wikipedia.org/wiki/Hoare_logic) provides a set of formal rules for reasoning about the correctness of programs, including smart contracts. A Hoare-style property is represented by a Hoare triple `{P}c{Q}`, where `c` is a program and `P` and `Q` are predicates on the state of the `c` (i.e., the program), formally described as _preconditions_ and _postconditions_, respectively.
74
74
75
75
A precondition is a predicate describing the conditions required for the correct execution of a function; users calling into the contract must satisfy this requirement. A postcondition is a predicate describing the condition that a function establishes if correctly executed; users can expect this condition to be true after calling into the function. An _invariant_ in Hoare logic is a predicate that is preserved by execution of a function (i.e., it doesn't change).
Copy file name to clipboardExpand all lines: public/content/roadmap/account-abstraction/index.md
+3-28Lines changed: 3 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,9 +10,9 @@ summaryPoints:
10
10
11
11
# Account abstraction {#account-abstraction}
12
12
13
-
Users interact with Ethereum using **[externally owned accounts (EOAs)](/glossary/#eoa)**. This is the only way to start a transaction or execute a smart contract. This limits how users can interact with Ethereum. For example, it makes it difficult to do batches of transactions and requires users to always keep an ETH balance to cover gas.
13
+
Most existing users interact with Ethereum using **[externally owned accounts (EOAs)](/glossary/#eoa)**. This limits how users can interact with Ethereum. For example, it makes it difficult to do batches of transactions and requires users to always keep an ETH balance to pay transaction fees.
14
14
15
-
Account abstraction is a way to solve these problems by allowing users to flexibly program more security and better user experiences into their accounts. This can happen by [upgrading EOAs](https://eips.ethereum.org/EIPS/eip-3074) so they can be controlled by smart contracts, or by [upgrading smart contracts](https://eips.ethereum.org/EIPS/eip-2938) so they can initiate transactions. These options both require changes to the Ethereum protocol. There is also a third path involving adding a [second, separate transaction system](https://eips.ethereum.org/EIPS/eip-4337) to run in parallel to the existing protocol. Regardless of the route, the outcome is access to Ethereum via smart contract wallets, either natively supported as part of the existing protocol or via an add-on transaction network.
15
+
Account abstraction is a way to solve these problems by allowing users to flexibly program more security and better user experiences into their accounts. This can happen by [upgrading EOAs](https://eips.ethereum.org/EIPS/eip-7702) so they can be controlled by smart contracts. There is also another path involving adding a [second, separate transaction system](https://eips.ethereum.org/EIPS/eip-4337) to run in parallel to the existing protocol. Regardless of the route, the outcome is access to Ethereum via smart contract wallets, either natively supported as part of the existing protocol or via an add-on transaction network.
16
16
17
17
Smart contract wallets unlock many benefits for the user, including:
18
18
@@ -74,12 +74,6 @@ These are just a few examples of how user experiences could be leveled up by acc
74
74
75
75
Smart contract wallets exist today but are challenging to implement because the EVM does not support them. Instead, they rely on wrapping relatively complex code around standard Ethereum transactions. Ethereum can change this by allowing smart contracts to initiate transactions, handling the necessary logic in Ethereum smart contracts instead of offchain. Putting logic into smart contracts also increases Ethereum's decentralization since it removes the need for "relayers" run by wallet developers to translate messages signed by the user to regular Ethereum transactions.
76
76
77
-
<ExpandableCardtitle="EIP-2771: account abstraction using meta-transactions"eventCategory="/roadmap/account-abstract"eventName="clicked EIP-2771: account abstraction using meta-transactions">
78
-
79
-
EIP-2771 introduces the concept of meta-transactions that allow third parties to pay for a user's gas costs without making changes to the Ethereum protocol. The idea is that transactions signed by a user get sent to a `Forwarder` contract. The forwarder is a trusted entity that verifies that transactions are valid before sending them on to a gas relay. This is done offchain, avoiding the need to pay gas. The gas relay passes the transaction on to a `Recipient` contract, paying the necessary gas to make the transaction executable on Ethereum. The transaction is executed if the `Forwarder` is known and trusted by the `Recipient`. This model makes it easy for developers to implement gasless transactions for users.
80
-
81
-
</ExpandableCard>
82
-
83
77
<ExpandableCardtitle="EIP-4337: account abstraction without changing the Ethereum protocol"eventCategory="/roadmap/account-abstract"eventName="clicked EIP-4337: account abstraction without changing the Ethereum protocol">
84
78
85
79
EIP-4337 is the first step towards native smart contract wallet support in a decentralized way <em>without requiring changes to the Ethereum protocol</em>. Instead of modifying the consensus layer to support smart contract wallets, a new system is added separately to the normal transaction gossip protocol. This higher-level system is built around a new object called a <code>UserOperation</code> that package up actions from a user along with the relevant signatures. These <code>UserOperation</code> objects then get broadcast into a dedicated mempool where validators can collect them into a "bundle transaction". The bundle transaction represents a sequence of many individual <code>UserOperations</code> and can be included in Ethereum blocks just like a normal transaction, and would be picked up by validators using a similar fee-maximizing selection model.
@@ -90,25 +84,9 @@ The way wallets work would also change under EIP-4337. Instead of each wallet re
90
84
91
85
</ExpandableCard>
92
86
93
-
<ExpandableCardtitle="EIP-2938: changing the Ethereum protocol to support account abstraction"eventCategory="/roadmap/account-abstract"eventName="clicked EIP-2938: changing the Ethereum protocol to support account abstraction">
94
-
95
-
<ahref="https://eips.ethereum.org/EIPS/eip-2938">EIP-2938</a> aims to update the Ethereum protocol by introducing a new transaction type, <code>AA_TX_TYPE</code> that includes three fields: <code>nonce</code>, <code>target</code> and <code>data</code>, where <code>nonce</code> is a transaction counter, <code>target</code> is the entry point contract address and <code>data</code> is EVM bytecode. To execute these transactions, two new instructions (known as opcodes) have to be added to the EVM: <code>NONCE</code> and <code>PAYGAS</code>. The <code>NONCE</code> opcode tracks the transaction sequence and <code>PAYGAS</code> calculates and withdraws the gas required to execute the transaction from the contract's balance. These new features allow Ethereum to support smart contract wallets natively as the necessary infrastructure is built into Ethereum's protocol.
96
-
97
-
Note that EIP-2938 is currently not active. The community is currently favoring EIP-4337 because it does not require changes to the protocol.
98
-
99
-
</ExpandableCard>
100
-
101
-
<ExpandableCardtitle="EIP-3074: upgrading externally-owned accounts for account abstraction"eventCategory="/roadmap/account-abstract"eventName="clicked EIP-3074: upgrading externally-owned accounts for account abstraction">
102
-
103
-
<ahref="https://eips.ethereum.org/EIPS/eip-3074">EIP-3074</a> aims to update Ethereum's externally-owned accounts by allowing them to delegate control to a smart contract. This means smart contract logic could approve transactions originating from an EOA. This would allow features such as gas-sponsoring and batched transactions. For this to work, two new opcodes have to be added to the EVM: <code>AUTH</code> and <code>AUTHCALL</code>. With EIP-3074 the benefits of a smart contract wallet are made available <em>without needing a contract</em> - instead, a specific type of stateless, trustless, non-upgradeable contract known as an "invoker" handles the transactions.
104
-
105
-
Note that EIP-3074 is currently not active. The community is currently favoring EIP-4337 because it does not require changes to the protocol.
106
-
107
-
</ExpandableCard>
108
-
109
87
## Current progress {#current-progress}
110
88
111
-
Smart contract wallets are already available, but more upgrades are required to make them as decentralized and permissionless as possible. EIP-4337 is a mature proposal that does not require any changes to Ethereum's protocol, so it is possible that this could be implemented quickly. However, upgrades that alter Ethereum's protocol are currently not in active development, so those changes may take much longer to ship. It is also possible that account abstraction is achieved well enough by EIP-4337 that no protocol changes are ever required.
89
+
**The next two Ethereum upgrades ([Pectra](/roadmap/pectra/) and later Fusaka) will address these improvements.** Pectra will be released soon in upcomming months. Smart contract wallets are already available. EIP-4337 is a mature proposal that does not require any changes to Ethereum's protocol, so many wallets have started adopting this standard.
112
90
113
91
**Note**: You can track adoption of ERC-4337 smart contract wallets [via this dashboard](https://www.bundlebear.com/overview/all).
114
92
@@ -120,11 +98,8 @@ Smart contract wallets are already available, but more upgrades are required to
120
98
-["Account abstraction ELI5" from Devcon Bogota](https://www.youtube.com/watch?v=QuYZWJj65AY)
121
99
-[Vitalik's "Road to Account Abstraction" notes](https://notes.ethereum.org/@vbuterin/account_abstraction_roadmap#Transaction-inclusion-lists)
122
100
-[Vitalik's blog post on social recovery wallets](https://vitalik.eth.limo/general/2021/01/11/recovery.html)
Copy file name to clipboardExpand all lines: public/content/translations/cs/community/get-involved/index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,12 +59,12 @@ Pokud nejste vývojář, může být obtížné zjistit, jak začít pracovat s
59
59
60
60
### Nabídněte pomoc při psaní poznámek během komunitních hovorů {#take-notes}
61
61
62
-
- Existuje mnoho hovorů open-source komunit a mít osobu dedikovanou na zápis poznámek je velká pomoc. Pokud máte zájem, připojte se k [Discordu Ethereum Cat Herders](https://discord.com/invite/Nz6rtfJ8Cu)a představte se!
62
+
- Existuje mnoho hovorů open-source komunit a mít osobu dedikovanou na zápis poznámek je velká pomoc. Pokud máte zájem, připojte se k [Discordu Ethereum Cat Herders](https://discord.com/invite/Nz6rtfJ8Cu)a představte se!
63
63
64
64
### Překládejte obsah o Ethereu do svého rodného jazyka {#translate-ethereum}
65
65
66
66
- ethereum.org má program věnovaný překladům, který překládá webové stránky a další zdroje do mnoha různých jazyků
67
-
-[Tady](/contributing/translation-program)zjistíte, jak se můžete zapojit
67
+
-[Tady](/contributing/translation-program)zjistíte, jak se můžete zapojit
Copy file name to clipboardExpand all lines: public/content/translations/cs/contributing/translation-program/translators-guide/index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -116,7 +116,7 @@ Nejlepší způsob, jak pracovat s odkazy, je kopírovat je přímo ze zdroje, b
116
116
117
117
118
118
119
-
Odkazy se také zobrazují ve zdrojovém textu ve formě tagů (tj. \<0>\</0>). Pokud na tag umístíte kurzor, editor zobrazí jeho celý obsah – někdy tyto tagy představují odkazy.
119
+
Odkazy se také zobrazují ve zdrojovém textu ve formě tagů (tj. `<0>``</0>`). Pokud na tag umístíte kurzor, editor zobrazí jeho celý obsah – někdy tyto tagy představují odkazy.
120
120
121
121
Je velmi důležité zkopírovat odkazy ze zdroje a neměnit jejich pořadí.
122
122
@@ -154,7 +154,7 @@ nonce – _text, který není určen k překladu_
154
154
155
155
Zdrojový text také obsahuje zkrácené tagy, které obsahují pouze čísla, což znamená, že jejich funkce není okamžitě zřejmá. Můžete na tyto tagy najet kurzorem, abyste přesně zjistili, jakou funkci plní.
156
156
157
-
V příkladu níže můžete vidět, že když najedete kurzorem na tag \<0> , zobrazí se, že představuje `<code>` a obsahuje úryvek kódu, takže obsah uvnitř těchto tagů by neměl být přeložen.
157
+
V příkladu níže můžete vidět, že když najedete kurzorem na tag `<0>` , zobrazí se, že představuje `<code>` a obsahuje úryvek kódu, takže obsah uvnitř těchto tagů by neměl být přeložen.
0 commit comments