A wallet is mostly a chain of small, well-specified steps. Twelve words become a seed (BIP-39). The seed becomes a tree of keys (BIP-32). A key becomes an address, in one of several encodings. A transaction is serialized, hashed and signed with secp256k1. Each step has a public specification and public test vectors.
In a Dart app, these steps can end up spread over several dependencies: a general crypto library, a web3 client, a mnemonic package. The more packages touch your private keys, the more code someone has to read before trusting the signing path.
crypto_wallet_core puts the whole chain in one small package: mnemonics, HD key derivation, addresses, secp256k1 signing and Ethereum transaction signing. Its only runtime dependency is package:crypto , and it does not use web3dart.
Before anything else, the warning from the top of the README: it is not audited, private keys must be handled with care, and pure Dart gives no constant-time guarantees .…