Author

Topic: [feature idea] modular encryption wallet.dat password & bitcoin splitting (Read 758 times)

member
Activity: 70
Merit: 10
I mean exactly that.. It doesn't feel like blocks are confirming transactions at their usual rate (and thus the network will correct itself right?).. At first I thought I was mistaken but I noticed a few other users mention the exact same thing.
member
Activity: 73
Merit: 10
this is being developed right now. http://forum.bitcoin.org/index.php?topic=8728.0

Quote
second, if you send a transaction now, it takes wayyyy wayyy longer to get 120 block confirmations than it did -- say 1 month ago even.. This needs to change. Screw it, even if it takes a 1 or 2 decimal hit right now it brings us that much closer to better microtransactions and more confirmations and 50 bitcoins can still be awarded so people don't feel like mining isn't profitable

I don't really understand what you mean by that, but statistically blocks should be created (and thus transactions confirmed) at about the same pace as always... Or what else do you mean?
member
Activity: 70
Merit: 10
I think its high time with all this bitcoin (trojans, worms, physical) theft and whatnot that there be a mandatory requirement that each wallet.dat have a password on it in order to open it up. The password is completely tied to the wallet.dat . Anytime you want to change the password, you have to put in its current one. If you forget your password you gotta brute force it yourself.. The encryption though could be modular so there could be hundreds, if not thousands of types password methods to input and remember extremely long character passwords.


second, if you send a transaction now, it takes wayyyy wayyy longer to get 120 block confirmations than it did -- say 1 month ago even.. This needs to change. Screw it, even if it takes a 1 or 2 decimal hit right now it brings us that much closer to better microtransactions and more confirmations and 50 bitcoins can still be awarded so people don't feel like mining isn't profitable
Jump to: