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
- [ ] #3868
- [ ] #3938
- [ ] #4031
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/4250
When we have handled the above our hands are less tied, and we can get properly started.
### Tasks
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/4560
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/4561
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/4562
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/4768
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/4769
Inbox
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
- [x] discussion: align on divide and conquer or a new circuit then write stuff here
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/4558
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/4678
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/4633
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/4833
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/4829
### Contracts
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/4825
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/4828
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/5071
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/5072
### Misc
- [ ] #3976
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/5263
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/5264
### Finale
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/5073
- [ ] #697
- [ ] https://github.com/AztecProtocol/aztec-packages/issues/5836
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.
When we have handled the above our hands are less tied, and we can get properly started.
Inbox
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.