Skip to content
This repository has been archived by the owner on Oct 12, 2023. It is now read-only.

On bitcoin, generate a new address when the old one be used #550

Open
bitcoinuser opened this issue Oct 16, 2020 · 7 comments
Open

On bitcoin, generate a new address when the old one be used #550

bitcoinuser opened this issue Oct 16, 2020 · 7 comments
Labels
enhancement New feature or request

Comments

@bitcoinuser
Copy link
Contributor

RWallet 1.3.1 on Android

When receiving a transaction on BTC, the next BTC address on receive should be a new one. For now, RWallet doesn't generate a new bitcoin address.

Obs. I personally don't like options with buttons to generate a new address. I prefer that wallet automatically generate a new address when the old one be used.

@chrisli30
Copy link
Contributor

Yeah, I think we should have this function.

However, it's easy for user to by default use a same address and click a button to generate a new one, but hard vice versa so we would go for the manual generate way.

What do you think?

@bitcoinuser
Copy link
Contributor Author

Yeah, I think we should have this function.

However, it's easy for user to by default use a same address and click a button to generate a new one, but hard vice versa so we would go for the manual generate way.

What do you think?

My personal preference is to automatically change to a new address when the old one receive funds (So no need to a new generate new address button). Why someone would want to receive funds on the same address? If someone wants this, he could search on the received funds and copy the address.
Maybe on the first time the user click on receive button, could popup a message like: When you receive funds on this address, a new address will be generated. This is good for privacy. But you can always use the old addresses to receive funds.

@bitcoinuser
Copy link
Contributor Author

Maybe this popup message will confuse people. I will go with change to a new address when the old one receive funds. If someone really wants to receive on the same address, this user will know how to do this. And it's a function not critical, because people will never loose funds because of it.

@bitcoinuser
Copy link
Contributor Author

Yeah, I think we should have this function.

However, it's easy for user to by default use a same address and click a button to generate a new one, but hard vice versa so we would go for the manual generate way.

What do you think?

I changed my mind. I think a button to generate a new one is better.

Could you please prioritize this? Thanks.

@chrisli30
Copy link
Contributor

Yeah, I think we should have this function.
However, it's easy for user to by default use a same address and click a button to generate a new one, but hard vice versa so we would go for the manual generate way.
What do you think?

I changed my mind. I think a button to generate a new one is better.

Could you please prioritize this? Thanks.

@bitcoinuser My team is moved off of this project today. You can ask Brendan @bguiz for the further improvements.

@bitcoinuser
Copy link
Contributor Author

Yeah, I think we should have this function.
However, it's easy for user to by default use a same address and click a button to generate a new one, but hard vice versa so we would go for the manual generate way.
What do you think?

I changed my mind. I think a button to generate a new one is better.
Could you please prioritize this? Thanks.

@bitcoinuser My team is moved off of this project today. You can ask Brendan @bguiz for the further improvements.

@chrisli30 Sad to know. Any reason to move off?

@chrisli30
Copy link
Contributor

chrisli30 commented Dec 1, 2020

Yeah, I think we should have this function.
However, it's easy for user to by default use a same address and click a button to generate a new one, but hard vice versa so we would go for the manual generate way.
What do you think?

I changed my mind. I think a button to generate a new one is better.
Could you please prioritize this? Thanks.

@bitcoinuser My team is moved off of this project today. You can ask Brendan @bguiz for the further improvements.

@chrisli30 Sad to know. Any reason to move off?

Unfortunately, no idea. Maybe organizational change, but I don't have the full picture ...

Thanks for your supporting and testing for a long time! My telegram is @kezjo, feel free to shoot me a message on Telegram for any questions.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants