Topic: [UPDATE: 2015-05-10] Bitcoin Core soft-fork "No Forced TX Fee" v0.10.1 available (Read 59301 times)

Nope. And not planned, really.

If you want to compile/build it, check this out:
Ubuntu:
http://bitzuma.com/posts/compile-bitcoin-core-from-source-on-ubuntu/

Windows:
https://bitcointalksearch.org/topic/building-headless-bitcoin-and-bitcoin-qt-on-windows-149479

My version builds exactly the same way as normal version, so these instructions should work.

EDIT:
Also, because of latest transaction spam attacks, i would advise against using this fork anymore. I am actually updating it because I do not want to forget and lose this code. So kind of for historical reasons.

Are there any binary downloads for this?

As stated in the first post, probably not.

Also, the fee calculation algorithm drastically changed in 0.10, so it may be needed much less than before. I am going to do some testing Soon™ to check what exactly are the current benefits of using it. If there is very little difference between Core and this then I may stop supporting this patch.

Would this fork still be needed if/when the block size changes?

2015-05-10 Update:

NFTF - versions 0.10.0 & 0.10.1 released.

Fresh tags - nftf-v0.10.0, nftf-v0.10.1 are avaiable for download.
https://github.com/ShadowOfHarbringer/bitcoin-nftf/tags
https://github.com/ShadowOfHarbringer/bitcoin-nftf/archive/nftf-v0.10.1.tar.gz
https://github.com/ShadowOfHarbringer/bitcoin-nftf/archive/nftf-v0.10.0.tar.gz

MASTER branch was updated to the newest tag (0.10.1).

I'm aware of that, but at the same time, I don't like sending transactions with no fee whatsoever.

With the setting I had for the 1 satoshi, it was added onto transactions that needed a fee, as well... so if a transaction needed a 0.005 fee, it ended up having a 0.00500001 fee on it.

It isn't necessarily the amount of the fee, but that the new release, enforces the setting to be at a particular value.

If I want to set the fee to X by default, then that's on me, and let the network prioritize it (or not) accordingly when processing transactions.

My choice what fee I want to add, and the consequences of that, comes with the choice I made.

It seems like the core devs, while often claiming otherwise, still want to impose their ideas of what we should do, rather than us choosing for ourselves.

In any event, I've been wanting to write something that would do raw transactions to handle my dust management in my wallet (which is getting pretty bad by now) by always including the oldest 1 or 2 pieces of dust as inputs to another send I'm doing, to make sure that the 1 piece of change I end up with is larger than the dust that was included... 0.10.0 is just going to make me actually do it instead of think about it.

=squeak=

edit: the 1-satoshi fee I was mainly using for transactions that were very low priority... when I didn't care if it took a couple/few weeks to confirm. mainly for coin I was sending to cold wallet.

1 satoshi fees don't really have much of an effect on the entire network. All the nodes will not relay that unless it satisfies some other minimum threshold requirement (like bitcoin days or time.)

I am currently reviewing if it is still necessary to maintain this fork as Bitcoin Core 0.10 has a new, improved fee selection UI.
Perhaps i will request my code being merged into the Bitcoin Core mainline, since now it could be easily done.

Stay tuned.

Yeah, but it doesn't let me set "paytxfee" to 1 satoshi anymore... ended up downgrading back to 0.9.3 official.

=squeak=

The latest official v10.0.0 makes 0 fee txs easy. I think this was the only difference on this fork?

Is work still being done on this fork?

=squeak=

2014-10-05 Update:

NFTF - version 0.9.3 released.

Fresh tag - nftf-v0.9.3 is avaiable for download.
https://github.com/ShadowOfHarbringer/bitcoin-nftf/tags

MASTER branch was updated to the newest version (0.9.3).

Yep, coming (this weekend probably).

Bump. Some people might be looking for version 0.9.3.

  thanks for this specific mention.

OMG, I am now a ★LEGENDARY★ member !!

That feels great man !

Hey Mr. Shadow, you can update your sig now. You are no longer a Hero member. (And I'm on my way there too.)

Nope, unfortunately NFTF is a very minor patch, only changing one small aspect of client's behavior.

no, no ... your product don't crash (i don't have tested).
it's the official 0.9.2.1 that it crash (0.9.1 work rock stable).

that why i ask "if" your product have found somes bug added corrected with the (added of) modification of the fee strategy.

NFTF fork causing crash ? Well, this is highly unlikely. There is no significant change in the code that could cause the crash.

Please compile the standard client (without the patch) and do a test in *EXACTLY THE SAME CONDITIONS* to find out if it is really the fork causing the crash.