-
Notifications
You must be signed in to change notification settings - Fork 310
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.
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
New message box model #4492
Labels
T-tracking
Type: Tracking Issue. This contains tasklists.
Comments
This was referenced Feb 12, 2024
This was referenced Feb 26, 2024
Closed
This was referenced Mar 6, 2024
LHerskind
changed the title
feat!: Implement new message box model
feat!(MessageBox): Implement new message box model
Mar 8, 2024
LHerskind
changed the title
feat!(MessageBox): Implement new message box model
feat!(MessageBoxes): Implement new message box model
Mar 8, 2024
LHerskind
changed the title
feat!(MessageBoxes): Implement new message box model
New message box model
Mar 11, 2024
Remaining tasks of the message box model is low priority and can be addressed if needed at some point, but left to die off for now. |
All issues semes to have been resolved. Will be closing this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Following the new proposal put forth in #4485 we need to change the current implementation.
As described in the proposal we can do the changes of incoming and outgoing messages independently.
Since it is not changing the apis from inside the network. It don't need to be finished by 18 of Feb where dog-fooding starts again.
Note: Look for "TODO(#4492)" in the codebase.
Outbox
The circuit requirements to match the new outbox is already planned as part of the #3533 task. But some sections have not been finished yet.
Dependent on
When we have handled the above our hands are less tied, and we can get properly started.
Tasks
out_hash
in circuits #4561Inbox
The inbox requires quite a lot more changes to replace the existing implementation. However, there are no blocking dependencies before the work can be kicked off.
As the changes are quite large, we should look at targeting it piecemeal without bricking the existing system. Essentially, allow us to run the old, or the new where a few new E2E tests should be usable to check the new flow. Essentially running the uniswap example when we have a few pieces in place.
Circuits
in_hash
#4558msgKey
andentryKey
#4678Contracts
Misc
Finale
process
#5073The text was updated successfully, but these errors were encountered: