Bugfixes in SVN rev 130

5 messages BitcoinTalk Satoshi Nakamoto, Jeff Garzik, aceat64, knightmb August 12, 2010 — August 13, 2010
Satoshi Nakamoto August 12, 2010 21:20 UTC Source ·

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

Jeff Garzik (jgarzik) August 12, 2010 23:39 UTC Source ·
Quote from: satoshi on August 12, 2010, 12:20:31 PM UTC

-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?

aceat64 August 13, 2010 02:42 UTC Source ·
Quote from: Jeff Garzik on August 12, 2010, 2:39:12 PM UTC
Quote from: satoshi on August 12, 2010, 12:20:31 PM UTC

-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 Nakamoto August 13, 2010 03:15 UTC Source ·

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 August 13, 2010 03:17 UTC Source ·
Quote from: Jeff Garzik on August 12, 2010, 11:39:12 PM UTC
Quote from: satoshi on August 12, 2010, 9:20:31 PM UTC

-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?” 😁