E2E L2 -> L1

[LHerskind]

For a full E2E of L2 to L1 messages, we need:

• acir simulator to emit L2->L1 msg
  • acir simulator to emit L2 -> L1 messages #518
• messageboxes deployed on L1
  • Build contract for output side of L2 -> L1 message box #516
  • Add registry and update rollup contract to consume/push message in boxes #523
• portal deployed to L1 (token bridge for start)
  • Token bridge portal contract (l2 native asset) #519

Nice to haves:

• abi-like encoding in noir, to follow some of the best practices in https://docs.aztec.network/aztec/how-it-works/l1-l2-messaging#structure-of-messages

---

L2 native asset with token bridge:

• Deploy token portal on L1 and L2, (specifying the L1 contract as portal for L2)
• Mint tokens on L2
• Initiate a "withdraw" on L2 which will emit the message
• Sequencer includes tx in rollup on L1
  • This inserts messages into the messages box
• Execute "withdraw" on portal contract which will consume the message and mint the tokens on L1

[LHerskind]

This was finished, but tracking issue was never closed.