Architecture

Transaction flow

Current (L2/2.5 zkSync 2.0/zkPorter)

Legacy (L1 onchain)

Swap-box Structure

Kivy

The GUI is started at boot time. All the drivers are selected when the GUI starts running using a config file. Every driver is instantiated at this time as well. Only configuration operations are made in the constructors. Then, when a driver is needed, the start function of the driver is called (usually when a screen needing the specific driver is shown to the user: on_enter/on_pre_enter functions). When a driver is not needed (usually when a screen is left, on_leave/on_pre_leave functions), the stop function of said driver is called. As drivers are dynamically loaded at runtime, only one of each kind has to be working. For example, when running on a PC, you don't have to compile the custom OpenCV QR scanner, and can use zbarcam.

LED Drivers

Basic on/off functions that switch a LED. Switched ON when a QR is being scanned.

QR Scanner

Used to scan a QR representing a public key.

• ZBar Uses zbarcam utility
• OpenCV Uses custom implementation of a scanner, located in src/qr/scanner/zbar_c/

Node RPC

Performs call to buy/sell crypto. Either connects to a swap-box-web3 running instance or to scripts/mock/web3.py, both using ZMQ. A second ZMQ socket is used to push status from the node to the Kivy application in order to disable buy/sell features when the node is not connected or not synchronized. Since this features prevents the user from making actions and can be counterproductive during development, it can be disabled by commenting out self._config.STATUS.start() in TemplateApp.build function body.

Cashin/Cashout Drivers

Used when the customer puts money in the note validator or expects to receive some cash after a transaction. Either connects to an actual NV machine through serial port or scripts/mock/validator.py through ZMQ.