[UPDATE: 2015-05-10] Bitcoin Core soft-fork "No Forced TX Fee" v0.10.1 available

[HiveLibrary]

the solution then should be options for both minimum and maximum and broadcast intent to transmit (of course this could blow up and cause people to refuse to mine certain amounts or certain addresses)

[BitHits]

Anyone got binaries of this? I was spread them around like hot cakes! This could easily overtake official client that still adheres to broken tx fee system

[FreeMoney]

I'm confused by this thread. I thought the fee was always voluntary anyway... ?

Nope, it is not voluntary if the mainline client's algorithm decides so.

I've no issue with enforced fees, but using the standard windows client, doing some testing with bitcoin, have paid more than 5 times the transaction value in fees - somewhat disproportionate - makes it just like a bank

You've tested a bank's open source software and chosen to attach a fee that ended up going to a peer? Interesting for sure ;-)

[BitHits]

I'm not saying we should have NO TX FEE at all. But at the very fucking a least a tx fee proportionate to the input value of the transaction!

[BitHits]

Code:

Administrator@PC /c/bitcoin-nftf-master/src
$ make -f makefile.mingw
g++ -c -mthreads -O2 -w -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DWIN32 -D_WINDOWS -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE -DUSE_IPV6=1 -I/c/bitcoin-nftf-master/src/leveldb/include -I/c/bitcoin-nftf-master/src/leveldb/helpers -I"/c/bitcoin-nftf-master/src" -I"/usr/local/include" -o obj/alert.o alert.cpp
alert.cpp:5:29: fatal error: boost/foreach.hpp: No such file or directory
compilation terminated.
make: *** [obj/alert.o] Error 1

after copying C:\boost_1_43_0-mgw\boost to C:\bitcoin-nftf-master\src

Code:

Administrator@PC /c/bitcoin-nftf-master/src
$ make -f makefile.mingw
g++ -c -mthreads -O2 -w -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -g -DWIN32 -D_WINDOWS -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE -DUSE_IPV6=1 -I/c/bitcoin-nftf-master/src/leveldb/include -I/c/bitcoin-nftf-master/src/leveldb/helpers -I"/c/bitcoin-nftf-master/src" -I"/usr/local/include" -o obj/alert.o alert.cpp
In file included from serialize.h:22:0,
                 from netbase.h:10,
                 from util.h:27,
                 from alert.h:13,
                 from alert.cpp:8:
allocators.h:12:53: fatal error: openssl/crypto.h: No such file or directory
compilation terminated.
make: *** [obj/alert.o] Error 1

[pera]

you should properly install boost and openssl on your mingw/msys environment.. maybe you want to try this:
http://nuwen.net/mingw.html

and then read this:
https://qt-project.org/wiki/Compiling-OpenSSL-with-MinGW

[DeathAndTaxes]

I'm not saying we should have NO TX FEE at all. But at the very fucking a least a tx fee proportionate to the input value of the transaction!

The cost in storage, bandwith, and CPU is relative to the number of inputs and outputs not the value of the tx.  A fee based as a % of value would provide no DOS protection. 

[ShadowOfHarbringer]

I'm not saying we should have NO TX FEE at all. But at the very fucking a least a tx fee proportionate to the input value of the transaction!

The cost in storage, bandwith, and CPU is relative to the number of inputs and outputs not the value of the tx.  A fee based as a % of value would provide no DOS protection. 

Ok, but couldn't we get my topic any more derailed ?

[BitHits]

dammit! Now 0.8.1 comes out and its a hard fork from 0.7.2 and lower! So this wont even work anymore.

Can you make a 0.8.x No Forced TX Fork ? Running a BitCoin Faucet/PTC site I desperately need this.

[ShadowOfHarbringer]

dammit! Now 0.8.1 comes out and its a hard fork from 0.7.2 and lower! So this wont even work anymore.

Can you make a 0.8.x No Forced TX Fork ? Running a BitCoin Faucet/PTC site I desperately need this.

I will make a fork, however be wary that now that we may be reaching block limit soon, so the transactions you make may never confirm.

This fork is kind of dangerous until the block size issue is not solved.

[BitHits]

block limit for 0.7.2 or ?

[Atruk]

block limit for 0.7.2 or ?

Block limit for prior to 0.8/0.8.1... The issue with 0.7.2 is a bit more archane.

[ShadowOfHarbringer]

block limit for 0.7.2 or ?

I was talking about the fixed 1MB block size.

Once we start getting close to it, low priority transactions (low amounts, multiple small outputs etc) without any fee may never confirm.

[BitHits]

I dont mind paying a fee. I just dont want to be paying 300% of the input of my transaction A fee absolutely proportionate to the input of my transaction is what I'm aiming for. Running a BTC Faucet like site I tend to have large transactions to many addresses for very small amounts. I've been experimenting trying to get the lowest fees. But I still cant seem to beat just sending them in bulk to about 2000 addresses at a time. Thou sending to 232-314 Addresses seems to be a bit of a sweet spot in terms of transaction size.

[ShadowOfHarbringer]

2013-03-24 Update:

NFTF - version 0.8.0, 0.8.1 released.

Fresh tags - nftf-v0.8.0, nftf-v0.8.1 are avaiable for download.
https://github.com/ShadowOfHarbringer/bitcoin-nftf/tags

MASTER branch was also updated to latest Bitcoin version:
https://github.com/ShadowOfHarbringer/bitcoin-nftf



2013-03-24 WARNING !!
PLEASE NOTE THAT UNTIL MAX BLOCK SIZE PROBLEM HAS BEEN SOLVED BY DEVELOPERS, SOME FREE (WITHOUT FEE) TRANSACTIONS CREATED BY THIS FORK MAY CONFIRM VERY SLOWLY OR NEVER.
YOU HAVE BEEN WARNED, THANK YOU FOR YOUR ATTENTION.

[BitHits]

Binaries anyone!?

[Atruk]

Binaries anyone!?

Building a binary from source isn't some magic limited to developers.

[richik]

Would be much easier to everyone, if anybody will provide compiled binaries for Windows...  

[ShadowOfHarbringer]

Would be much easier to everyone, if anybody will provide compiled binaries for Windows...  

Well that surely won't be me. I don't use "legacy technologies from twentieth century" as somebody stated on this forums.

[LvM]

Each lawyer will tell you:
All these ARBITRARY and UNFORESEEABLE enforced transaction fees are ILLEGAL.

It cannot be down to miners whim, what at all and even HOW MUCH they want to claim.
A claim of fees must at least clearly be declared before a transaction is definitely mandated by users.

Otherwise there is no agreement.
No agreement, no fee.
And no other chicanry like delays or denial of service (seems also applied - illegally).