It looks to me from reading about ECDSA that the private key can be anything - a random number
Currently a lot of users are afraid to lose access to their wallets - so they make backups etc..
I am concerned that some users will find out the private key can be anything they want and will generate\use easy to remember keys like DEADBEEF (address:1KNrMaMfiqKzRC5fzi1gqTeDC96PAqJPZy)
Whenever I need to change the password for my bank account - there is a minimal complexity required - it won't let me use a simple password.
Can something like this be implemented for the bitcoin client? some kind of a complexity check of the private key?
rejecting the key will cause a lot of trouble, but for example the client can create a new address and transfer all the funds there if a simple private key is detected, or at least warn the user that the key is bad.
