Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync "Bitcoin Network Fee Policy" Across devices #3955

Open
Jacobbubble opened this issue Mar 4, 2016 · 11 comments
Open

Sync "Bitcoin Network Fee Policy" Across devices #3955

Jacobbubble opened this issue Mar 4, 2016 · 11 comments

Comments

@Jacobbubble
Copy link

This might be tricky since this is now only a global setting #3947 but other wallet-specific metadata such as notes sync across devices with the same wallet, why doesn't the fee policy sync?
It's less than optimal to have to switch the policy on every device.
Especially with multiple wallets on multiple devices, this is painful UX.

@matiu
Copy link
Contributor

matiu commented Mar 8, 2016

why doesn't the fee policy sync?

In the general case, copayers can be different persons, and each could have a different policy setup for the TX they submit.

@Jacobbubble
Copy link
Author

copayers can be different persons

What about a single, 1 of 1 wallet synced between two devices? Such as a personal wallet on a desktop and mobile device.

@matiu
Copy link
Contributor

matiu commented Mar 11, 2016

What about a single, 1 of 1 wallet synced between two devices? Such as a personal wallet on a desktop and mobile device.

Yes, it would make sense in that case.

@Jacobbubble
Copy link
Author

@matiu I believe that's a more likely scenario.
I assume:
Users with shared wallets are less common than users with personal wallets.
AND OR
Most transactions occur through personal wallets rather than shared ones.

@dabura667
Copy link
Contributor

Also, if I have 2 wallets on my phone:

  1. Private pocket spending 1 of 1
  2. Business super important 2 of 3

I don't want to have to switch between Economic for 1 and Priority for 2 every... single.. time... I want to switch wallets (this is actually happening to me)

@isocolsky
Copy link
Contributor

@dabura667 is it really the case that lower value transactions can wait longer to get confirmed? In my experience, even when I am paying for something inexpensive, I want to be certain it confirms fast. It seems to me making it a per-wallet setting would still be off with respect to real use.

@Jacobbubble
Copy link
Author

@isocolsky For spending to other parties I typically send with a higher fee, especially when confirmation time matters.

For things like transferring between my own wallets, I often use the cheapest fee possible.

@dabura667
Copy link
Contributor

It seems to me making it a per-wallet setting would still be off with respect to real use.

I think this would be true if we assume that all users only use Copay for one purpose.

If we view the average Copay user as only using their personal wallet, or maybe a multisig using Ledger as a 2FA solution, then yes, it makes sense that the user will always want the same priority every time.

tbh, I always liked the priority being in the "advanced option" of the transaction itself... but since the advanced option is no longer existing... moving the setting from global to wallet makes sense.

@KeyJockey
Copy link

I don't want to have to switch between Economic for 1 and Priority for 2 every... single... time...

@dabura667 hmm, implementing my proposal for the 'advanced fee edit control' slider ( https://github.com/bitpay/copay/issues/3111 ) would afford the user a quick & easy, simple, direct way to tweak the miner fee right on the SEND page.

Just sayin'... 😜

@dabura667
Copy link
Contributor

Doesn't change much, two taps and a swipe as compared to three taps and a swipe. The goal is 0 everything.

The point is it would be nice if the policy was a wallet parameter vs. a global parameter, as use cases can vary between wallets.

However, nowadays, you need to use priority all the time... So my problem is not a problem anymore. I get confirmed quickly every time, because the network is unstable fee-wise.

@KeyJockey
Copy link

Seems to me like it'd be only one tap (open advanced toggle) and one swipe (slider bar, set fee) on top of current operation?

And maybe if the "advanced" part of the SEND tab page would remember being left OPEN, in persistent state, for users who've used it last, then you'd not even need the first extra tap if that 'advanced' part of the Send page design stayed visible.

Then it'd be just a single ONE optional extra slider-swipe to tweak your fee number before hitting Send Transaction... i.e. "1" is pretty close to "0 everything", just enabling an extra swiping operation.

But, yeah I get your point anyway, still just sayin' 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants