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.

Warning: Only use this fork if you know what you are doing.
Otherwise, there is a low probability that some coins sent without a fee will be lost stuck in a limbo and difficult to recover.
Read details below.

-------------------



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.




-------------------

Okay, here we go.

So as I promised, I created the "NFTF" (short of No Forced TX Fee) section on Github.
This isn't going to be anything big & professional, just few lines of code changed comparing to the standard client.

I did it, because i was unsatisfied with standard client forcing people to pay fees, even when they are not necessary at all.
I wrote many complaints about this on multiple topics on this forum, and for unknown reasons the main developers do not want either to remove this broken algorithm, or to improve it. Mining cartel ? CIA-related conspiracy ? Who knows & Who cares. I don't know and I don't care so I am going my own way.

So here you are.

Full list of branches & tags is avaiable here:

Branches contain code of older versions (from 0.3.21 to 0.3.24).
Tags contain newer versions, 0.4.0 and up.

----------------

Warning: Use this fork with following precautions (the same as if you would use mainline client v0.3.20 version):

- Make sure you get at least 7 confirmations first when resending the money without a fee.
- Sending small amounts (< 0.01) without any fee may be risky.
- Include a fee when sending money received from a lot of inputs.


----------------

2011-09-22 Update:

Today I have merged back the commit from trunk which fixes an unfairly high fees that have to be paid to the miners sometimes due to a bug re-introduced in 0.3.24.

For details see the discussion here:
https://bitcointalk.org/index.php?topic=45259.0

The patch is/will be already present in 0.4x version of official client, but i have also merged it back into 0.3.21, 0.3.22, 0.3.23 and 0.3.24 versions - for people who like to use older and more tested apps.

https://github.com/ShadowOfHarbringer/bitcoin-nftf/commits/nftf-0.3.21
https://github.com/ShadowOfHarbringer/bitcoin-nftf/commits/nftf-0.3.22
https://github.com/ShadowOfHarbringer/bitcoin-nftf/commits/nftf-0.3.23 (that version already contained the patch)
https://github.com/ShadowOfHarbringer/bitcoin-nftf/commits/nftf-0.3.24

If you have used trunk version, it already contained the patch, merged back from official client.
https://github.com/ShadowOfHarbringer/bitcoin-nftf/

Enjoy your no-unnecessary-fee transactions !
As always, wait for at least 7 confirmations before re-sending money so you lower the risk of transaction not being accepted by the network.


----------------
2011-09-24 Update:

NFTF - version 0.4.0 released.

Also:
- Removed all the messy git tags merged previously from the mailine client
- Created new, clean tag for NFTF-0.4.0
- Minor cosmetic changes in comments

So from now on, code will be organized in tags, not versions - as it should be from the beginning.

0.4.0 code is avaiable in the tag:
https://github.com/ShadowOfHarbringer/bitcoin-nftf/tree/nftf-v0.4.0/

And trunk code is avaiable from the trunk, as always. I usually only update it on major version changes or important features/bugfixes, so don't expect me to keep up with mainstream client developers all the time.

Trunk: https://github.com/ShadowOfHarbringer/bitcoin-nftf/tree/

Also, i have performed few tests, sending back and forth small amounts of BTC (0.01) having only 2 confirmations, and it seems that my fork is stable enough for the payments to get confirmed easily (up to 2 hours) without using any fees.


----------------
2011-12-03 Update:

NFTF - version 0.5.0 released.

A fresh tag - nftf-v0.5.0 is avaiable for download.
https://github.com/ShadowOfHarbringer/bitcoin-nftf/tags

Trunk code was also updated:
https://github.com/ShadowOfHarbringer/bitcoin-nftf/tree/


----------------
2012-01-07 Update:

NFTF - version 0.5.1 released.

A fresh tag - nftf-v0.5.1 is avaiable for download.
https://github.com/ShadowOfHarbringer/bitcoin-nftf/tags

Trunk code has also been merged back:
https://github.com/ShadowOfHarbringer/bitcoin-nftf/tree/


----------------
2012-02-12 Update:

NFTF - versions 0.5.2 & 0.6.0rc1 released.

NOTE: From now on i will also include release candidate (rc) tags in my fork.

Fresh tags - nftf-v0.5.2, nftf-v0.6.0rc1 are avaiable for download.
https://github.com/ShadowOfHarbringer/bitcoin-nftf/tags

Trunk code has also been merged back:
https://github.com/ShadowOfHarbringer/bitcoin-nftf/tree/


----------------
2012-03-21 Update:

NFTF - version 0.5.3.1 [critical security vulnerability hotfix] released.

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

More updates (other tags, trunk) should follow soon.


----------------
2012-03-25 Update:

NFTF tags for mainline client versions v0.5.3rc1, v0.5.3rc2, v0.5.3rc3, v0.5.3rc4, v0.5.4rc1, v0.6.0rc2, v0.6.0rc3, v0.6.0rc4 released.

https://github.com/ShadowOfHarbringer/bitcoin-nftf/tags

Trunk/master has also been fully updated to the latest mainline version.


----------------
2012-05-08 Update:

NFTF - versions 0.6.0.7/0.6.1 & 0.6.2 released.

Fresh tags -are avaiable for download as usual.
https://github.com/ShadowOfHarbringer/bitcoin-nftf/tags

Trunk code has also been merged from mainline client:
https://github.com/ShadowOfHarbringer/bitcoin-nftf/tree/


----------------
2012-08-15 Update:

NFTF - version 0.6.3 released.

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

Also, I may be making a new repo with Gentoo ebuilds avaiable soon, since I am creating them anyway for my Gentoo.
So stay tuned.


----------------
2012-11-04 Update:

NFTF - versions 0.7.0 & 0.7.1 released.

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


----------------
2013-01-27 Update:

NFTF - version 0.7.2 released.

Fresh tag - nftf-v0.7.2 is 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 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-06-23 Update:

NFTF - version 0.8.2 released.

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


----------------
2013-08-19 Update:

NFTF - version 0.8.3 released.

Fresh tag - nftf-v0.8.3 is 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-10-07 Update:

NFTF - versions 0.8.4, 0.8.5 released.

Fresh tag - nftf-v0.8.4, nftf-v0.8.5 is 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


----------------
2014-01-26 Update:

NFTF - version 0.8.6 released.

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

MASTER branch was updated to the last tag (0.8.6).


----------------
2014-06-01 Update:

NFTF - versions 0.9.0 & 0.9.1 released.

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

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


----------------
2014-08-10 Update:

NFTF - versions 0.9.2 & 0.9.2.1 released.

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

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


----------------
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).

----------------
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).

Actually, If something can be called a mark of the beast, then it is the crappy fiat currencies with their bank-controlled, crysis-causing & credit-powered baloon economy.
Today's monetary system is completely sick. It does not support wise investments, but only mindless spending.

Bitcoin is the cure.

Actually, i had the forced feee even when sending 10 BTC having 7 confirmations....
So i guess this wasn't fixed.

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.

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.

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.

+1


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

Polite bump.

Let's ask this question differently: Was the algorithm which decides what is spam and what isn't changed at all since 0.3.21 ?

Was the spam-detection algorithm improved since 0.3.21 ?
In 0.3.21, even when i wanted to send some bitcoins having 7 confirmations, i had to pay the fee. Downgrade to 0.3.20 fixed the problem, and i could send the bitcoins (and later i got 2 confirmations after 45 minutes, so the transaction was OK contrary to what client claimed).

So is this finally fixed or not ?

You mean 1 BTC or 10 BTC ?
I don't understand how this could possibly work.

Is this a troll topic or am I misunderstanding something ?

+1

Everything that i wanted to say was already said here.

muad_dib, you have no idea what you are talking about. There isn't any 100% proof that BSD is either more secure or more reliable than Linux.

@muad_dib

At first your post seemed wise, but


I stopped reading right here.

I don't know who you are, but you know nothing about security.

Definately worth of inclusion.
+1

You are not listening.
He is only talking about the linux package, not windows/macos.

Agreed. This feature seems definately cool.

Bump for inclusion.

Actually, i meant VNCing to the VM from a laptop.
VNCing from the same comp would have no sense as the keyloggers/screen capture/mouse movements capture would kill it.

But VNCing to the bottom layer from outside should be safe enough.


Well, i didn't say this is the most secure way, i just said it is more secure than having single layer protection on a single computer.

The "separate minimal machine for Bitcoin only" is of course superior to everything.

Actually, it does.
You may fool an attacker into thinking that he hacked all the layers, while he only hacked top 2 of them.
Security by obscurity + surprise element.


Who needs mouse movements when you can connect to a (virtual) machine using  encrypted VNC connection ?
The possibilities are endless. VM is just the beginning of the things you can do.


Not all of the exploits work on all kinds of VM's.
Also, a possible attacker may not be prepared for task of this level of complexity.


This is certainly the best way, but having a hall of mirrors is also useful when you are only using single machine.
As I said, "the possibilities are endless. VM is just the beginning of things you can do".

Generally my thinking is that you can create multiple levels of complexity and every one of the makes it more difficult for the attacker to hack you.

Of course it is, because you said so.
How can we ever doubt you, you are such a SMART-ASS !


Yes, and become easy prey to hackers of all sorts.

I am saying about a following scheme:

1. Create encrypted TrueCrypt hard drive.
2. Put a VirtualBox disk with VirtualBox Linux machine on it.
3. Install TrueCrypt within the Virtual Machine
4. Create encrypted TrueCrypt hard drive within the VM.
================== (LAYER 2) ==================
5. Create a VirtualBox disk with VirtualBox Linux machine on the VM.
6. Install TrueCrypt within the Virtual Machine in Virtual Machine
7. Create encrypted TrueCrypt hard drive within the VM in VM.
================== (LAYER 3) ==================
(...)
================== (LAYER 4) ==================
(...)

And so on...