This repository was archived by the owner on Apr 8, 2024. It is now read-only.
Merged
Conversation
arijoon
force-pushed
the
feat/PI-139-registration-payload
branch
from
281c57f to
16a5b0c
Compare
arijoon
force-pushed
the
feat/PI-139-registration-payload
branch
from
dff9561 to
811115c
Compare
sjpbeale
approved these changes
Aug 4, 2023
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Tested using Tenderly and the generated signature works. It can yield a successful transaction and register the user onchain
Currently looking into the validation of this on the BE, one of the following options, I favour the second but very likely to go with first one as the initial implementation