This week’s team hangout featured Kieran, Frontend Developer at Dusk, who walked us through a live demo of the Dusk bridge integration in the web wallet, connecting the L1 (DuskDS) and L2 (DuskEVM), which allows users to move native DUSK seamlessly between layers..
The session also covered the latest testing progress and frontend development updates, the purpose behind the withdrawal finalization period, and plans for transaction history in the Web Wallet.
You can find a breakdown of the key questions and answers below 
Q1: Kieran, could you give us a short introduction about your background and what you’ve been working on at Dusk?
- Kieran has been with Dusk for roughly seven years, joining in the project’s earliest days after a background in enterprise e-commerce. Before Dusk, he worked on Oracle’s Professional Services team, building front and back-end systems for large enterprise clients.
- He’s been the driving force behind nearly everything web-related at Dusk, from the Explorer and Web Wallet to the website and various frontend integrations, shaping how Dusk’s products are presented and used.
- His current focus is the Dusk bridge, connecting the L1 (DuskDS) and L2 (DuskEVM), which allows users to move native DUSK seamlessly between layers.
- The UI is still being polished, but the core transaction logic is already functional, deposits, withdrawals, and sync between DuskDS and DuskEVM are now live in testing.
Q2: What’s the current status of testing for deposits and withdrawals on the bridge?
- The core bridge functionality, deposits from DuskDS to DuskEVM and withdrawals in the opposite direction, is now fully working in the internal build.
- Kieran mentioned the team has focused heavily on ensuring correct data encoding and decoding between the two environments. This involves translating transaction data between the Dusk Virtual Machine (Rusk) and the Ethereum Virtual Machine, handling serialization/deserialization of byte data.
- The bridge relies on a smart contract in WebAssembly (WASM) for cross-chain communication. While this introduced some challenges early on, the team systematically worked through them and now has a stable architecture in place.
- A major design goal was to make the bridge’s low-level libraries developer-friendly and reusable, so third-party builders can use the same tools to connect DuskDS and DuskEVM in their own apps.
Q3: Will the withdrawal “finalization period” remain in future releases?
- The current setup borrows from the Optimism-style challenge model, where transactions can be disputed for a limited time before finalization. In Dusk’s implementation, this delay exists mainly as a defensive safeguard, giving the team a window to intervene if anomalies occur during the early stages of rollout.
- Dusk will eventually move to a “pessimistic-optimistic” model, where the consensus layer itself validates all rollup submissions before they’re finalized, eliminating the need for a separate waiting period.
- The long-term goal is instant deterministic finality across both DuskDS and DuskEVM. Unlike probabilistic systems such as Ethereum, Dusk achieves irreversible settlement once blocks are finalized, a key requirement for regulated financial transactions.
Q4: Will the Web Wallet include full transaction history upon release?
- The current bridge demo only shows pending transactions, but Kieran confirmed that full transaction history is planned for a future update.
- The goal is to eventually show complete transaction histories, including both DuskDS and EVM-layer operations, within the wallet interface.
- For the DuskEVM side, users will still be able to view their full transaction history directly through MetaMask or other Web3 wallets, since these natively support such tracking.
You can watch the full recording and bridge demo here: https://youtu.be/rC2uvQpdpVw
Have more questions? Drop them below and we’ll include them in a future session.
Join us live every week in the Dusk Community
See you next week!