Authorize attestation #41
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request
Description
Adds authorizeAttestation and reworks attest.
A user can now authorize an attestation by providing the hybrid allocator with a signature of a signer as approval. This is stored in transient storage, so the authorize call must happen within the same transaction that the user is performing the ERC6909 token transfer on the compact.
The user can do an arbitrary amount of transfers, as long as the total amount transferred is not exceeding the authorization of the token.
The nonce used by the off chain signer must follow the hybrid allocators nonce pattern and will be burned on the compact.