Author

Topic: Idea for new client. (Read 1119 times)

legendary
Activity: 1820
Merit: 1001
June 06, 2015, 06:17:15 PM
#5
Well having this ability to archive wallet address makes it simpler to find addresses in wallet that you want to use
You don't normally 'find' addresses in Bitcoin Core. You generate new ones when you ask for one. It does not normally give you a list of your own addresses.

Quote
This could free up resources used within client or loading time. If someone has tuns of addresses in it and has to rebuild or load up
Resource usage per address is very neglgible. Even with tens of thousands of addressees it doesn't take a noticable amount of time.

Quote
and if one of the old addresses receives payment it then gets auto shifted to active and a little notice popup saying you received payment on archived address that has now been made active.

Well if it does that, it's not actually deleted!


It is sort of 2 ideas one to perm delete so no longer have it or archive system to have it and save for layer.

In mine I have a bunch generated from clicking send payment that didn't use my main address or didn't tick request to send from option. Not sure what has gone on with it having a bunch of random addresses populate in it that never used or sent any transactions on it so not sure how their their. Since backed up my priv keys of onces wanting to keep deleted wallet and imported since doing seems to run smoother on loading and sending payments and downloading. Not sure what problem could be but was just a few ideas had that could be worth while for people.
staff
Activity: 4284
Merit: 8808
June 06, 2015, 05:39:33 PM
#4
Well having this ability to archive wallet address makes it simpler to find addresses in wallet that you want to use
You don't normally 'find' addresses in Bitcoin Core. You generate new ones when you ask for one. It does not normally give you a list of your own addresses.

Quote
This could free up resources used within client or loading time. If someone has tuns of addresses in it and has to rebuild or load up
Resource usage per address is very neglgible. Even with tens of thousands of addressees it doesn't take a noticable amount of time.

Quote
and if one of the old addresses receives payment it then gets auto shifted to active and a little notice popup saying you received payment on archived address that has now been made active.

Well if it does that, it's not actually deleted!
legendary
Activity: 1820
Merit: 1001
June 06, 2015, 12:42:48 PM
#3
You haven't said anything about the motivation, it's not self apparent.

How would a wallet with this behavior be noticeably functionally different than without it?

Well having this ability to archive wallet address makes it simpler to find addresses in wallet that you want to use and have others like bank system to only use when needed and encrypted. Also with this in place to load up only transactions that are in active core and not in archive and only activated when in active section. This could free up resources used within client or loading time. If someone has tuns of addresses in it and has to rebuild or load up am sure will be good to have this in it. and if one of the old addresses receives payment it then gets auto shifted to active and a little notice popup saying you received payment on archived address that has now been made active.

Sorry did not explain in more details or add all above Smiley Hope this explains of the feature for client more.
staff
Activity: 4284
Merit: 8808
June 06, 2015, 12:33:35 PM
#2
You haven't said anything about the motivation, it's not self apparent.

How would a wallet with this behavior be noticeably functionally different than without it?
legendary
Activity: 1820
Merit: 1001
June 06, 2015, 12:25:43 PM
#1
Not sure if this has been put forward to the core team devs. Have the option to delete dormant or mistaken bitcoin addresses made in client. Option allows next to it to delete address and confirm deletion with password popup or some sort of archive system so that their still their but in a separate section of wallet that is used along top like in menu for it.
Jump to: