SE7EN Labs Details Daedalus dApp Plans in Roadmap Talk With Hoskinson

SE7EN Labs has merged the core code for connecting Daedalus to decentralized applications, developers reported during a roadmap discussion with Charles Hoskinson. The functionality had not yet been released, with interface improvements and security testing still ahead. The team outlined how it plans to bring application access to Cardano’s full-node desktop wallet while expanding hardware support and preparing for future protocol upgrades.

Daedalus Prepares a Built-In Browser for Cardano Applications

The integration uses CIP-30, the interface through which Cardano applications communicate with compatible wallets. It would let Daedalus users access dApps from the desktop application alongside transfers, staking and governance. According to the developer responsible for the integration, the underlying communication already works, although parts of the user experience remain unfinished.

That work extends to how Daedalus presents assets. The team acknowledged that its interface had fallen behind the ecosystem’s development of tokens and NFTs, with tokens largely represented through text descriptions. Adam Dean is expected to improve their presentation. An optional single-address wallet mode is also planned to accommodate applications that depend on a particular wallet address.

For application access, SE7EN Labs considered a browser extension that would communicate with Daedalus through a local connection. Developers rejected that design because of concerns about protecting the channel, particularly on a computer running malicious software. Their chosen approach opens each dApp in a separate browser window within Daedalus, using an isolated environment known as a sandbox. Communication with the wallet would pass through the injected CIP-30 connector, with access to other components restricted by that design.

Application developers have been invited to discuss integration, particularly for projects running on Cardano’s Preview and Preprod test networks. The proposed listing process would use submissions to the Daedalus repository containing descriptions, icons, supported networks and network-specific URLs. Musashi Dojo was mentioned as a possible later addition, while the formal submission process had not yet been established.

The team distinguished inclusion in the directory from security certification. SE7EN Labs expects to test some integrations but does not plan to certify every listed application. A separate feature in the diagnostics interface would also provide access to dApps that have not yet been added to the directory.

Full-Node Architecture and AI-Assisted Development

Hoskinson traced Daedalus’s modernization needs to its origins before Cardano’s Shelley and Goguen eras. It was built before today’s staking and application ecosystem had taken shape, leaving work across synchronization, delegation and dApp access. He also explained that Input Output’s position as a reference software developer complicated decisions about monetization, partnerships and which ecosystem participants a wallet might highlight. In his view, a specialist product team has greater flexibility to make those choices.

SE7EN Labs brought together contributors interested in continuing Daedalus development following work associated with DripDropz. Samuel Leathers credited approved Cardano Treasury funding with allowing the team to devote more attention to the wallet. Its responsibilities include user support through Ariadne, the portal built to manage support requests. Mithril integration has meanwhile addressed part of the synchronization workload by enabling the use of certified blockchain snapshots while Daedalus continues to run a local Cardano node.

Leathers outlined another architectural change already introduced: Watchdog, a supervisor written in Rust. It manages background components, including the node and wallet backend, and coordinates Mithril operations and blockchain storage. Its functions include supporting a user-selected storage drive and exposing progress information that is not readily available through the wallet API. Those responsibilities were previously handled through the application’s older process-management code.

That separation could support future integration with alternative Cardano nodes, including Dingo and Amaru. Developers discussed letting users choose a backend and download its signed software separately, although the interfaces between components would need further work. They planned to explore those requirements with other teams at a node diversity workshop in London. Hoskinson suggested that Daedalus could help distribute alternative implementations to individual users.

Electron remains the framework for Daedalus’s desktop interface. Developers clarified that replacing it is still under consideration and would be too large an undertaking to pursue immediately. On Linux, the team has moved toward native packages for Debian, RPM-based distributions, Arch and NixOS, connecting that work to operating-system requirements for dApp isolation. Under the approach outlined in the discussion, Daedalus notifies users about new versions, while updates are handled through the package manager.

The conversation also examined how the team uses AI during development. Leathers described a system that indexes source code and makes the relevant versions of libraries available to coding tools, reducing repeated searches and token consumption. He combines hosted and local models, with the latter allowing selected analysis to remain in his own environment. Another developer emphasized tightly defined specifications, multiple forms of software checks and AI-assisted security analysis of repositories, including Daedalus.

Hoskinson’s approach starts with a precise description of intended behavior, followed by modeling, implementation and verification. He discussed Quint for modeling systems and Lean for building a formal reference against which production software can be checked. Faster code generation, he argued, places greater emphasis on review and security assurance, particularly for components handling cryptographic secrets and funds. He also raised a separate possible application for Daedalus: allowing a personal AI agent to access Cardano through its owner’s local node, using a private connection such as Tailscale.

[NEWSBREAK]

Hardware Wallets and Cardano Upgrades Shape the Next Releases

Keystone integration depends on work outside Daedalus as well as changes to the wallet itself. Leathers reported that the Daedalus-side functionality was ready, while a related pull request for Keystone’s firmware was awaiting review. Ledger Flex had reached a different stage: after dependency updates and integration changes, errors he had previously encountered no longer appeared in his testing. The team had not formally advertised Flex support because broader testing remained outstanding.

For upcoming Cardano upgrades, developers are following new node releases and checking compatibility. They want test builds of Daedalus to provide early access to Dijkstra features when the necessary components become available. One requirement discussed was displaying planned direct deposits into reward accounts correctly. The team also intends to keep contributing changes to upstream wallet software where needed for compatibility.

CIP-113, the programmable token standard, is being monitored but did not yet have a dedicated implementation item in Daedalus’s roadmap. Developers are watching how projects adopt the specification before defining support. They expressed a similar approach to nested transactions, with integration expected to follow concrete applications using the feature. Such applications would also need mechanisms for routing partial transactions to other participants before completion.

Hoskinson connected that coordination problem to Moriarty, the intent-based language he is developing. Some transactions begin as an expression of what a user wants to achieve and require other parties to contribute information, assets or signatures before submission. Multisignature transactions provide an existing example: participants must exchange and sign an incomplete transaction before it can be sent to the blockchain. He argued for common interfaces that wallets could adopt to handle those exchanges and connected the same requirement to Midnight’s planned financial operations across networks.

For dApp support, SE7EN Labs plans to restore Daedalus Flight and introduce the functionality through Preview, Preprod and Flight releases before adding it to the mainnet wallet. Developers and security researchers would test application compatibility and the sandbox’s isolation boundaries during that rollout. The team did not announce a mainnet release date.