From 9ef7f29ec0fae583745b53c86ba3b42850ab3e5f Mon Sep 17 00:00:00 2001 From: Elias Rad <146735585+nnsW3@users.noreply.github.com> Date: Fri, 1 Nov 2024 00:11:42 +0200 Subject: [PATCH] fix(docs): spelling issues (#16) * Update README.md * Update README.md * Update README.md * Update chapter1/bls-multisig/README.md --------- Co-authored-by: Matthias Seitz --- README.md | 2 +- chapter1/simple-7702/README.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 23cd3eb..6478a78 100644 --- a/README.md +++ b/README.md @@ -5,7 +5,7 @@ This repository provides a step-by-step walk through for builders interested in ### Chapter 1 - [Simple Example for EIP-7702](./chapter1/simple-7702/): Showcases how EIP-7702 transactions work - [Delegate an account to a p256 key](./chapter1/delegate-p256/): Describes how EIP-7702+EIP-7212 provide the ability to sign a message with a P256 key -- [BLS Multisig](./chapter1/bls-multisig/): In-depth walk-through how to implement a Multisig based on BLS signatures verified through precompiles from EIP-2537 +- [BLS Multisig](./chapter1/bls-multisig/): In-depth walk-through of how to implement a Multisig based on BLS signatures verified through precompiles from EIP-2537 - [EOF](./chapter1/eof/): Instructions on how to deploy and inspect contracts in the new EOF format - [ERC20 Fee](./chapter1/erc20-fee/): Describes how EIP-7702 provides the ability to pay ERC20 as gas fee to the gas sponsor. diff --git a/chapter1/simple-7702/README.md b/chapter1/simple-7702/README.md index 9420c77..292aa52 100644 --- a/chapter1/simple-7702/README.md +++ b/chapter1/simple-7702/README.md @@ -59,7 +59,7 @@ $ cast code $ALICE_ADDRESS 0xef0100... ``` -Note that in this over-simplified example, you’ll already see some issues e.g. anyone could send the transaction to any address on Alice behalf, since there’s such restriction in the signed authorization. To address this issue, you would need to add additional setup functions which would be called on user's bytecode once delegation has been applied. +Note that in this over-simplified example, you’ll already see some issues e.g. anyone could send the transaction to any address on Alice's behalf, since there’s such restriction in the signed authorization. To address this issue, you would need to add additional setup functions which would be called on user's bytecode once delegation has been applied. ## Testing with foundry @@ -72,4 +72,4 @@ vm.etch(ALICE, bytes.concat(hex"ef0100", abi.encodePacked(contractToDelegate))); This cheat code allows you to **simulate that ALICE's account is no longer a regular EOA but a contract**(like `P256Delegation`) and then test how delegations or transactions behave from that new "smart contract" EOA. -You can check out complete example in [SimpleDelegateContract.t.sol](../contracts/test/SimpleDelegateContract.t.sol) +You can check out the complete example in [SimpleDelegateContract.t.sol](../contracts/test/SimpleDelegateContract.t.sol)