{ "@context": { "CIP100": "https://github.com/cardano-foundation/CIPs/blob/master/CIP-0100/README.md#", "hashAlgorithm": "CIP100:hashAlgorithm", "body": { "@id": "CIP100:body", "@context": { "references": { "@id": "CIP100:references", "@container": "@set", "@context": { "GovernanceMetadata": "CIP100:GovernanceMetadataReference", "Other": "CIP100:OtherReference", "label": "CIP100:reference-label", "uri": "CIP100:reference-uri", "referenceHash": { "@id": "CIP100:referenceHash", "@context": { "hashDigest": "CIP100:hashDigest", "hashAlgorithm": "CIP100:hashAlgorithm" } } } }, "comment": "CIP100:comment", "externalUpdates": { "@id": "CIP100:externalUpdates", "@context": { "title": "CIP100:update-title", "uri": "CIP100:uri" } } } }, "authors": { "@id": "CIP100:authors", "@container": "@set", "@context": { "name": "http://xmlns.com/foaf/0.1/name", "witness": { "@id": "CIP100:witness", "@context": { "witnessAlgorithm": "CIP100:witnessAlgorithm", "publicKey": "CIP100:publicKey", "signature": "CIP100:signature" } } } } }, "authors": [], "body": { "comment": "I vote YES on the treasury withdrawal action “Se7en Labs: Daedalus Wallet Maintenance and Improvements 2026-2027” (d8de068952df50c862fa1bce9b8180d3387976cbae0fb2c3d9ef84f0faaf64d6#0).\n\nAs a user of Daedalus since March 2018 I am happy to see a team once again pick up the maintenance of Cardano’s only full-node wallet after years of neglect from IOG. The Yoroi/SecondFi incident recently highlighted the importance of self-sovereignty and the potential risks of closed-source light wallet providers. Running your own node is also central to the cypherpunk vision and an aspect of Bitcoin that staunch defenders have held onto and continue to champion today.\n\nDaedalus, running cardano-node, had become a resource intensive platform and restricted its recent adoption after the being the only wallet available for the first year of Cardano’s existence. Back then the chain size meant that it had reasonable resource usage. When this crept up to 16-24 GB RAM and hundreds of GB in storage it became increasingly untenable for everyday users. Enter Mithril. The perplexing nature of IOG is that it designed and built Mithril, the solution to the painfully slow Daedalus sync times but it never merged the two technologies and wondered why Mithril adoption was slow. It sometimes appears as though IOG focuses on the “what can be built” and not enough on the “what have we built”.\n\nI was sad to see that this did not get funded last year but the day that updated Daedalus was released by Se7en Labs, with the blessing of IOG, was genuinely one of the most positive days that I have had in this ecosystem in recent years, such is the contentious nature of Cardano governance these days. An updated Daedalus, hard fork ready on node version 11, with integrated Mithril. It went from fresh install to fully synced in an hour and the memory footprint on my Apple silicon Macbook Pro was just 4 GB. This is not all Mithril of course. Reduced sync times, yes. Reduced memory footprint, that is thanks to the newly implemented LSM trees and the ability to run UTXO-HD instead of having everything in memory.\n\nI look forward to an expanded feature set for Daedalus now that it has a committed and dedicated team supporting it. I also hope that it can help bring some of those long dormant ada holders, sceptical of anything but an “official” wallet might once again find their way to participating in the ecosystem. Even if that means simply moving to a non-retied stake pool and delegating to DReps once that becomes available in Daedalus. Ada should be participating in the security of the ecosystem, not lying dormant in neglected wallets.\n\nBy the way, while you’re here, stake to a Mithril Signer SPO and support helping make Daedalus great again, find one on the [HephyPool website]( https://hephy.io/mithril), and delegate in a few clicks on Cexplorer." }, "hashAlgorithm": "blake2b-256" }