I’m relatively new to Bitcoin; my journey started in 2021 after listening to a Lex Fridman podcast featuring Robert Breedlove. That episode sent me down a rabbit hole (I’m sure many of you can relate), and I’ve since decided to contribute to the community. For the past two years, I’ve been developing a Desktop Wallet.
Coming from a background in business application software development, I’ve focused on usability and innovative features that could make it more accessible to “non-techies.”

Two of the main “new” features I’ve worked on are:
•   Consensus Backup
•   Delegated Multisignature

I’ve dedicated all my free time over the last two years to this project, and I’d really appreciate your honest feedback. Am I on the right track, or have I missed the mark?
Your insights would mean a lot to me. Thank you in advance for your time and help.

~angelo


In this link I explain (and have a video) on how the Concensus Backup works:
https://wiki.distributedcryptography.com/wiki.aspx?1048,Consensus+Backup

On the following one about the Delegated Multisignature”:
https://wiki.distributedcryptography.com/wiki.aspx?1049,Delegated+Multisignature

I’ve included many more features focus on security that I haven’t been able to post on the wiki yet, but are available on the actual application, if you want to try it

The wallet support the following Bitcoin standards:
•   Brain Wallets (not recommended).
•   Wallet Import Format (WIF) for legacy individual keys.
•   Hierarchical Deterministic Wallets (BIP 32).
•   Mnemonic code for generating deterministic keys (BIP 39).
•   Multi-Account Hierarchy for Deterministic Wallets - Legacy Format of HD (BIP 44)
•   Derivation scheme for P2WPKH-nested-in-P2SH based accounts (BIP 49)
•   Derivation scheme for P2WPKH based accounts (BIP 84)
•   Segregated Witness (BIP 141), (BIP 143) and (BIP 144)
•   Bech32 segwit address implementation with error detection (BIP 163)
•   Key Derivation for Single Key P2TR Outputs (BIP 86) ~ our default mode
•   Validation of Taproot Scripts (BIP 341 and BIP 342)
•   Electrum protocol compatible
•   Multy spending paths (address and script)
•   K of N multisignature (using Huffman TapTrees)