Topic: Transaction fees magically appearing, how to account for them? (Read 7480 times)

Unfortunately, there isn't anything like that. Read here:
https://bitcointalksearch.org/topic/bitcoind-transaction-fees-one-annoying-shit-i-have-stumbled-upon-45259

This is the exact reason why i created my fork. There isn't any way to force sending money without any fee currently.

Is there already a RPC API solution for getting the estimated fees OR a feature that blocks the sending if the account balance would become insufficent? Anything planned for the next version? I think this is very important for handling accounts and running bitcoin services!

I created the fork.

Read here:
http://forum.bitcoin.org/index.php?topic=22434.msg281703#msg281703

Binary Linux packages will be soon built, also I am currently looking for Windows & MacOS maintainers.

OK....

I shall be setting the fork on Github this weekend.

I will post details here (and in a new topic) once i create the fork.

I've got a compiler set up for Windows.  I barely know how to use it, but I did successfully compile 0.3.23.

Thanks for the SF link, I'll use that for now.

I have the 0.3.20.2 install file if anyone wants to trust a random stranger on the internet 

For now, stick to the 0.3.20 version.

http://sourceforge.net/projects/bitcoin/files/Bitcoin/

Unfortunately compiling for windows is not as easy as it is with linux.
Also, i don't have any windows installed at the moment.

I hope we find some maintainers for other operating systems.

And if you could do it for Windows, I would throw a bitcoin or two (at current rates) your way as a "Awesome! Thanks!"

You should be able to select an older version via Github.
Of course, that's source-only.

Also, there are 0.3.20 (and older) binaries on SourceForge.
http://sourceforge.net/projects/bitcoin/files/Bitcoin/

The problem with fork is i can only compile it for Linux, somebody else has to compile Windows version.

EDIT:

Completely forgot about MacOS.
I am not doing MacOS as well.

I think the transaction fees should have a difficulty to keep the block growth at a goal of 1 mb/day or 5 mb/day.  The island of yap had large stone money, the fed had gold bars, even the lydian lion were too valuable to be used.  But, I think in the future the transaction fee might rise to 0.1 or 1 or even 10.  Now you say that would make bitcoin useless.

You could join a mining pool such as deepbit.  Then directly deposit those coins on an exchange with the receive address they give you.  Buy goods, all without ever installing the bitcoin client.  The large transactions will be part of the network, however the smaller transactions will be done through wallets, exchanges, and mining pools.

This could actually strengthen the network.  In a year no one will have the client installed anyway due to block growth.  However, high transaction fees will allow everyone to install the block.  At the end of the year December 31st, the blocks can be cleaned out and verified before the baby new year and the new fresh block such as block000002012, leaving a little bit of zeros to plan for the future.

So say in 2017 and BTC is worth $5000 per coin and you have 100 of them and the transaction fee is 1.  Now to protect your coins you might leave a computer on 24-7 to protect the network, before selling out to a bigger fish and using exchanges or wallets for your small time $500,000.

nice. But I still can't send anyone a satoshi for free

There is, by intentional design, no way to cancel a transaction, other than to get a conflicting transaction included in the hash chain. If a miner includes it in the chain, then it happens.

Also, i thought there were some measures in place so that if due to some statistical blip a transaction stayed floating unconfirmed for too long it would be canceled, so even if all miners reject a transaction the money wouldn't stay in limbo forever...

There is the possibility. If no miners are willing to accept a transaction, it will wait around for confirmation forever. In practice, at least for now, there are enough lulls in the transaction load and miners willing to take any transaction at all that there's not a problem.

They do.  Well, coins that wait around longer get priority, at any rate.

Is there really the possibility free small transactions will hang around waiting for confirmations forever? I thought transactions that were waiting for confirmations for too long automaticly gained more priority regardless of the size or even presence of tx fees....

Shadow, you mentioned that you downgraded to 0.3.20... is there still a link available somewhere to download a compiled version of 0.3.20?

I would 100% support a fork for a client that doesn't force transaction fees.

+1


I am starting to think seriously about maintaining a "No-Forced-TX-Fee" fork of the main client.

If transaction fees are going to be randomly enforced with no way to stop it, may as well just slap a tx fee on every tx.  Make the minimum tx fee 0.0005 BTC every time, with the option to pay more to potentially get a tx to go through faster.

But having the option to set tx fee to 0, then pay tx fees, that's just confusing, misleading, and frustrating.

If they were, then if you set the transaction fee per KB to zero, you'd never pay any transaction fees. On 0.3.23, you will pay transaction fees even if you set the fee per KB to zero. How you want to interpret this is up to you. You can say the client is not honoring the fee per KB of zero. You can say the client is imposing a transaction fee that's not per KB and is honoring the fee per KB of zero. You say po-TAY-to, I say po-TAH-to.