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

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

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. 

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

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

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!

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

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

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)

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

People who occupy to protest are fine. Nothing wrong with resistance. It's the aimless granulated freedom which puts all its money on leaves in the forest vs trees debate.

The leaves want to choose!

I think he means those people who manifest themselves by occupying roads, bridges, etc., so that would be something like 80% or 90% of the population of my country, where almost everyone done it at least once in life lol

Let me get your point straight: Who should be hit by lightning specifically ?

PS.
Unfortunately that would be a fork of reality, which is not easily done unless you are the creator.

Can we have a fork where someone is hit by lightning every time they decide to sit in the middle of traffic to express their freedom?

0.8.0 is coming slowly, probably this week.

However i do not use Windows at all and have no interest in it, so you will have to build it yourself.

It builds exactly the same way as mainline version does. Instructions for building mainline version are here:
https://bitcointalksearch.org/topic/m.86700
http://bitcoin.stackexchange.com/questions/587/how-do-i-build-bitcoin-source-in-windows-7

*BUMP*

Anyone got win32 binaries for this?

Also any plans for 0.8.0 version ?

This "fork" is just a simple patch i made for historical purposes.

I want to remember and always have access to sending 0-fee transactions easily. That is all.

You are incorrect, my fork does enforce anti-spam rules. This has already been brought up before.

It does not relay invalid transaction without enough fees. The code i changed applies only to sending your own coins, not to relaying any coins.


Done, sorry for the mess.

I second that.
The only utility in NFTF fork for me is testing my 0-confirmation payment platform against double-spending attempts.
But again, I guess I always could roll my own build.

EDIT: I take it back, since we have createrawtransaction API, 0-fee transactions can be sent from a regular build. So, no, there is probably no utility in this fork for me

The min tx fees are tiny and make up a negligible portion of miners revenue (not to be confused with optional fees on high priority txs).

If a sufficient number of nodes are running code which doesn't enforce the anti-spam rules it would allow an attacker to trivially cripple the Bitcoin network in both bandwidth usage and storage requirements for a token amount of money.  So that is a "good thing" I guess.  Also this fork allows noobs to create transactions which may takes days or weeks to be included in a block leading to all kinds of confusion and frustration.  Worse when that happens the tx will seem to "Disapear" as it can't be seen by the receiver due to other nodes enforcing the rules.

I personally (as a merchant) have experienced the "fun" of this.  A noob with little understanding of Bitcoin saw the "no fees" fork and figured it must be better.  I mean those evil miners trying to force him to pay a fraction of a penny only on massive bloated spammy transactions.  Can't have that right?  He created an order with us and our site gave him a payment address.  He sent coins but of course with no fee nodes between him and us dropped the transaction so our processing node couldn't even see the tx.  Anyways long story short the customer is freaking out, thinking we are scamming him.  He can "see" he sent the coins but we can't see the coins being sent, it isn't getting include in any block.  Try explaining that concept to a noob.  Before the tx is included in a block 16 hours later, the order expires and the price drops massively so when the funds do finally clear we can't honor the price and refund the order.  Of course the uninformed noob thinks this is our fault and we are trying to scam him because the price dropped but we can't honor coins we don't have access to.

So yeah... this is a wonderful fork which will greatly help increase adoption of Bitcoin.