Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explainer for Erc-1271 and erc6492 #24

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Explainer for Erc-1271 and erc6492 #24

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b7573ff
Explainer for Erc-1271 and erc6492
OladeleSeyi Dec 22, 2024
2357e71
reference relevant blog post
OladeleSeyi Dec 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion docs/pages/sdk/v5_3_x/core-api/sign-and-verify.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,18 @@ If you are impatient, head straight to [the API](#api). Otherwise, read on to l

## Understanding ERC-1271 and ERC-6492

TODO
[ERC-1271](https://eips.ethereum.org/EIPS/eip-1271), which more popular, defines a standard function `isValidSignature`, which a verifier can call to validate a signature. However, ERC-1271 is limited to verifying signatures of deployed smart accounts.
ERC-4337 implements counterfactual deployment, an optimization that allows the computation of the address of the smart account before the account is deployed. As a result, in practice a pre-deployed smart account might generate a signature which cannot be properly verified by ERC-1271.

[ERC-6492](https://eips.ethereum.org/EIPS/eip-6492) uses a `[UniversalSigValidator contract](https://eips.ethereum.org/EIPS/eip-6492#reference-implementation)` that validates the signature as described;

- Check if the signature ends with a sequence of bytes that indicates that the signature is by a predeployed smart account;
- If yes, the deployment of the contract is simulated using `[eth-call](https://docs.alchemy.com/reference/eth-call)` and then `isValidSignature` is called to validate the signature.
- If the signature does not indicate that it is a predeployed smart account;
- `ERC-1271` is called if a smart account is found at the address provided.
- Otherwise, it is assumed that the signature is from an EOA and the signature is verified by `ecrecover`

[This blog post](https://docs.zerodev.app/blog/erc-6492-and-why-its-important-for-aa) provides a deep dive on both standards.

## API

Expand Down