Update arbitrum l1 to l2 messaging proposal to arbitrum sdk v4 #15286
Conversation
This file contains 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
- Modified command in README.md to test proposals locally on fork of base instead of mainnet
- Merged latest changes from origin
adding another method to advance
* legacy auth wrapper * migration page * migration layout * update privy config * legacy hooks and providers * update dashboard header * legacy auth context * add migration compoenents * update SignInAccount * update EnterCode component * update EnterCode component * update providers * clean up * trigger upon successful email verification * add connectingwaas component * update SignInAccount * add legacy hooks * clean up * linting * some cleanup * more cleanup * more cleanup * more work * better syntax * update ConnectViaEmail component * adding another method to advance * fix accountType * dedicated page for google sign in * update password signin component * update popup component * update google signin component * adding migration with code * update MigrateUserContent component * removed extra file * once more * update google auth flow and usage * styling * fixed styling * update import usage * updated title * use privy callback * add link to direct to dashboard settings * cleanup --------- Co-authored-by: Julien Genestoux <[email protected]>
lock upgrade test
…4832) * refactor legacy purcahse function * basic testing * update main helper to use logic * fix lock helper * add docstrings to interface * pay referrers * lint fixes * fix lint * fix erc20 keys helper * emit `PurchaseReceipt` event * add events * fire event in extend + add some tests * test for tip * rename to `PaymentReceipt` * fix receipts
…unlock-protocol#15036) * update modal component * add sign out prompt component * update user migration content
…col#15038) actually showing the captcha component
…th, and feedback (unlock-protocol#15040) * responsiveness * fully authenticate after import & comprehensive user feedback
using captcha in both places
…migration (unlock-protocol#15043) * update migration feedback component * set and apply migration status
…error logging (unlock-protocol#15044) * update waas utility function * update google sign in component * update component for google oauth
better popup oauth state handling
…tocol#15046) * refactor keyUtil * improve google sign in component * sign out nextauth session upon successful privy login * cleanup
- fix(PR): removed console.log statement used governor address from networks package
Add new blog posts Co-authored-by: julien51 <[email protected]>
…h` (unlock-protocol#15271) * update schema * update introspection * update changelog * update version
unlock-protocol#15249) * update model * add migration script * add event deployment status to types package * update event operations * update event controller * update event route * update unlockjs package * draft dashboard utilisation * update unlockjs * update operation * update controller * update model * update route * remove types * update controller * remove deprecated function * update controller * cleanup * remove deployment queue * linting * more cleanup * update to use package types
* add event deployment worker * worker registration * refactor locks job * update worker entry * update worker structure for clarity * send email after updating event status
…ol#15278) * consolidate render conditions * update conditions * update conditions
* update useAuthenticate * dedup auth context * improve context typings * update useAuthenticate * fix types
…ck-protocol#15279) * update unlockjs * improve deployment status ux * update unlockjs * cleanup * more cleanup
* update auth hook leniency * update hook
Signed-off-by: fudancoder <[email protected].>
|
Thank you for your pull request and welcome to Unlock! We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @github-actions[bot] on file. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
|
@clemsos please review |
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.
Description
Adds a new proposal to execute arbitrum l1 to l2 messaging using the arbitrum SDK v4 syntax.
Issues
Fixes #
Refs #
Checklist:
Release Note Draft Snippet