Bitcoin Forum
December 11, 2016, 12:25:38 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Bugfixes in SVN rev 130  (Read 1430 times)
satoshi
Founder
Sr. Member
*
qt
Offline Offline

Activity: 364


View Profile
August 12, 2010, 09:20:31 PM
 #1

Misc bugfixes in rev 130:

fix -datadir with relative path
autostart is now off by default except on windows
fix occasional "vector iterator not dereferencable" assertion when compiled with msvc
fix readlink compile warning on linux build
use sys/param.h and BSD define instead of __BSD__
-paytxfee switch, e.g. -paytxfee=0.01
1481459138
Hero Member
*
Offline Offline

Posts: 1481459138

View Profile Personal Message (Offline)

Ignore
1481459138
Reply with quote  #2

1481459138
Report to moderator
1481459138
Hero Member
*
Offline Offline

Posts: 1481459138

View Profile Personal Message (Offline)

Ignore
1481459138
Reply with quote  #2

1481459138
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
jgarzik
Legendary
*
qt
Offline Offline

Activity: 1470


View Profile
August 12, 2010, 11:39:12 PM
 #2

-paytxfee switch, e.g. -paytxfee=0.01

So, -paytxfee sets nTransactionFee.

Can someone explain how nTransactionFee causes a client to behave?

And more specifically, what happens when node A sets 1000.0 and all other nodes use 0.01?


Jeff Garzik, bitcoin core dev team and BitPay engineer; opinions are my own, not my employer.
Donations / tip jar: 1BrufViLKnSWtuWGkryPsKsxonV2NQ7Tcj
aceat64
Full Member
***
Offline Offline

Activity: 127



View Profile
August 13, 2010, 02:42:16 AM
 #3

-paytxfee switch, e.g. -paytxfee=0.01

So, -paytxfee sets nTransactionFee.

Can someone explain how nTransactionFee causes a client to behave?

And more specifically, what happens when node A sets 1000.0 and all other nodes use 0.01?



From what I understand a node will not include transactions in it's blocks unless the transaction includes a fee that meets the node's requirements. So in the case of a node setting the fee to 1,000 it would likely never include any transactions in blocks it generates, which means it will miss out on any transaction fees other nodes would have gotten. There really isn't a reason to set a nodes requirements higher then the rest of the network since you are basically just pricing yourself out of the market.

satoshi
Founder
Sr. Member
*
qt
Offline Offline

Activity: 364


View Profile
August 13, 2010, 03:15:23 AM
 #4

No, that's not what it is.

-paytxfee allows you to include a transaction fee with your transactions.  If transaction confirmations become slow, you can get priority by using "-paytxfee=0.01".  Any transactions you send would cost an extra 0.01.  There's no reason to use more than 0.01.

It's just there in case we need it.  It probably won't be needed, and it can be explained more if we do.
knightmb
Sr. Member
****
Offline Offline

Activity: 308


Timekoin - Save Electricity, Don't Waste It!


View Profile WWW
August 13, 2010, 03:17:25 AM
 #5

-paytxfee switch, e.g. -paytxfee=0.01

So, -paytxfee sets nTransactionFee.

Can someone explain how nTransactionFee causes a client to behave?

And more specifically, what happens when node A sets 1000.0 and all other nodes use 0.01?

You want to send someone a payment for 10BTC and it puts up a warning "it's going to cost 1010 to send the BTC?"  Grin

Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!