Bitcoin Forum
July 27, 2024, 04:14:03 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Android Electrum and dynamic fee display  (Read 338 times)
DuddlyDoRight (OP)
Sr. Member
****
Offline Offline

Activity: 318
Merit: 260



View Profile WWW
May 07, 2017, 04:18:42 PM
 #1

Shouldn't dynamic fees be displayed on "Send" screen as amount field is changed to a valid amount?

I have faith that one day this forum will get threads where people won't just repeat their previous posts or what others have already stated in the same thread. Also that people will stop acting like BTC is toy-money and start holding vendors accountable. Naive? Maybe.
Cereberus
Legendary
*
Offline Offline

Activity: 910
Merit: 1000



View Profile
May 09, 2017, 05:55:39 PM
 #2

Shouldn't dynamic fees be displayed on "Send" screen as amount field is changed to a valid amount?

That would be a good option but it is easily changeable to whatever fee you like, just go to the 3 dots on the right top left of the screen, then settings. There you will see a tab FEES, by default it is in the maximum fee which will enable your transaction to be confirmed in the next block (really soon). I agree with you though, they can make such tab in the send screen.




    ██    ██    ██    ██
  ██    ██    ██    ██
██    ██    ██    ██
              ██    ██
            ██    ██
          ██    ██
        ██    ██
      ██    ██       
    ██    ██    ██    ██
  ██    ██    ██    ██
██    ██    ██    ██
TRADEPLAYZ
█ 
█ 
█     
█  █
█  █ 
█  █ 
█  █
    █  █
  █  █
  █  █
        █
    █
      █   
TOURNAMENT PVP SYSTEM
  FACEBOOK |  TWITTER  |  LINKEDIN  |  TELEGRAM  |  GITHUB  |  ANN  | INSTAGRAM 

█ 
█ 
█     
█  █
█  █ 
█  █ 
█  █
    █  █
  █  █
  █  █
        █
    █
      █   

                     █▄
                     ████▄
                     ██████▄
                     ████████▄
                     ██████████▄
                     ████████████▄
                     ██████████████▄
                     ███████████████
                     ██████████████▀
                     ████████████▀
                     ██████████▀
                     ████████▀
                     ██████▀
                     ████▀
                     █
█▀
GOOGLE PLAY

                            ▄█████████████▄
                            ███████████████
                            █░░░░░░░░░░░░░█
                            █░░░░░░░░░░░░░█
                            █░░░░░░░░░░░░░█
                            █░░░░░░░░░░░░░█
                            █░░░░░░░░░░░░░█
                            █░░░░░░░░░░░░░█
                            █░░░░░░░░░░░░░█
                            █░░░░░░░░░░░░░█
                            █░░░░░░░░░░░░░█
                            █░░░░░░░░░░░░░█
                            █░░░░░░░░░░░░░█
                            ██████▀▀▀██████
                             ▀████▄▄▄▄████▀
  APPSTORE
DuddlyDoRight (OP)
Sr. Member
****
Offline Offline

Activity: 318
Merit: 260



View Profile WWW
May 10, 2017, 06:28:04 AM
 #3

Shouldn't dynamic fees be displayed on "Send" screen as amount field is changed to a valid amount?

That would be a good option but it is easily changeable to whatever fee you like, just go to the 3 dots on the right top left of the screen, then settings. There you will see a tab FEES, by default it is in the maximum fee which will enable your transaction to be confirmed in the next block (really soon). I agree with you though, they can make such tab in the send screen.

It's "Dynamic" by default. People should know what they are spending before they spend..

I have faith that one day this forum will get threads where people won't just repeat their previous posts or what others have already stated in the same thread. Also that people will stop acting like BTC is toy-money and start holding vendors accountable. Naive? Maybe.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!