Daedalus Wallet is a non-custodial, full-node desktop wallet for managing ADA, the cryptocurrency of Cardano. It combines a wallet interface with a local node that verifies blockchain data. Non-custodial means users control the keys that authorize spending rather than handing that responsibility to a wallet provider. ADA itself remains recorded on the blockchain, not inside the application.
How the Full-Node Design Works
Daedalus Wallet downloads Cardano’s blockchain history and checks it locally against the network’s rules. Its node communicates with network peers to obtain blocks and transactions; independent validation does not mean operating without a network connection. The node checks the data it receives instead of relying on a wallet provider’s server to perform ledger validation on its behalf.
As synchronization progresses, the wallet uses the validated blockchain data to determine balances and transaction history. When a user sends ADA, the wallet prepares and signs a transaction with the relevant keys and submits it to the network. Submission is not the same as confirmation: the transaction must be included in the blockchain before it is confirmed. Running a full node does not by itself give a wallet authority to produce blocks or guarantee transaction inclusion.
Keys and Wallet Controls
For a software wallet created or restored in Daedalus Wallet, private keys are encrypted on the user’s computer. These keys authorize spending; a receiving address lets others send ADA without giving them access to those keys. The interface supports sending, receiving, and reviewing wallet transactions, while the local node supplies the blockchain view behind those functions.
The recovery phrase provides a way to restore access if the local wallet installation is lost. It is therefore part of the wallet’s custody responsibility, not simply an application password. Anyone who obtains it may be able to control the associated funds. Keeping the application installed or retaining an encrypted wallet file is not a substitute for protecting the recovery phrase.
Looking for liquidity, exploring on-ramp/off-ramp services, or seeking expert guidance?
Get startedSynchronization and Resource Requirements
The defining trade-off of Daedalus Wallet is the time and resources required for local validation. Initial synchronization must process blockchain history, which can delay access to an up-to-date view of funds and transactions. Disk usage grows as the blockchain grows, and synchronization also uses bandwidth and computing capacity. After time offline, the node must catch up with the blocks it has missed.
A light wallet generally obtains blockchain information through remote infrastructure instead of maintaining and validating the full history locally. This reduces local storage and processing demands, but changes which infrastructure the wallet relies on for its blockchain view. Full-node status and custody are separate properties: a light wallet can also leave private keys under the user’s control.
Security Benefits and Limitations
Daedalus Wallet reduces reliance on a remote wallet provider for ledger validation, but that benefit has a specific scope. It does not make the desktop computer immune to malware or ensure that every displayed address is the intended recipient. Local key encryption does not eliminate risks from compromised software, phishing, or recovery-phrase theft.
User-controlled keys also mean that a provider cannot simply reset wallet access in the way an online service resets a password. If the necessary keys and recovery information are lost, access to the funds may be lost. Independent validation, device security, and recovery-phrase protection address different risks; none replaces the others.
