[ANN] Bitcoin Transaction Fee Booster

[lovejoel]

someone please write a tutorial not everyone tech here,
my 2 transactions stuck in a network but the fee was 221 satoshi/byte still its not confirming

[algernonen]

it looks a bit troublesome
 I'm working on it.

[Termin4tor]

Thanks for creating and making this open source man, Im sure this well help a ton of people 

[rico666]

Thanks for creating and making this open source man, Im sure this well help a ton of people 

I wonder: https://blockchain.info/address/1QDNS5XuUEcdjQn4TU4qvXRnVtVv4CsssC

[Termin4tor]

Thanks for creating and making this open source man, Im sure this well help a ton of people 

I wonder: https://blockchain.info/address/1QDNS5XuUEcdjQn4TU4qvXRnVtVv4CsssC

Come on guys, give the man some love. Support is what everyone needs in life 

[kbs1]

Hello,

anyone got any luck running this on Ubuntu 16.04? I've installed default-jre and default-jdk but now java -jar FeeBooster.jar reports the following:

Error: Could not find or load main class FeeBooster

Am I missing some dependencies? -verbose does not tell much more. Any help is appreciated.

[paha77]

I've found this tool and try to use it as I've send a transaction 2 days ago from Multibit HD and it's still not confirmed.

I'm stuck on the unsigned version of the boosted transaction page.  How should I sign this transaction in Multibit HD?

Thank you.

[Sr.Urbanist]

I found the hex thanks to this guy:

How do you get the raw transaction in Hex format, from a transaction that is unconfirmed, and I didn't make, but appears on http://blockchain.info in a format that allows it to be passed into http://blockchain.info/pushtx when it is dropped from all miners memory pools.

Subject line says "from nodes", is that a requirement? blockchain.info returns the raw transaction if you append '?format=hex' to the URL of a transaction, e.g.:

https://blockchain.info/tx/9021b49d445c719106c95d561b9c3fac7bcb3650db67684a9226cd7fa1e1c1a0?format=hex

I have gone into my Trezor and tried to sign the receiving transaction, but do not understand it.  This is a really cool tool and I think it's going to take a little bit of time to figure out exactly how to use it.  

I signed the the tx with my signature it spit out and tx says NULL.  I assume that means I did something wrong.  Good opportunity to learn more about bitcoin programming.  This can be an extremely useful tool as sometimes fees go up expodentially very fast.

[virasog]

Ok, this looks fun.  A couple quick questions.  Once the user is sitting there with the unsigned TX, does the software help them take that the rest of the way and broadcast it or is that the end of the line and the user has to figure the rest?  Is the fee the only configurable part, along with the amount and addresses or can a user play with this and fiddle with various smart contract scripting and such.

[Sweetbtc]

Ok, this looks fun.  A couple quick questions.  Once the user is sitting there with the unsigned TX, does the software help them take that the rest of the way and broadcast it or is that the end of the line and the user has to figure the rest?  Is the fee the only configurable part, along with the amount and addresses or can a user play with this and fiddle with various smart contract scripting and such.

Also, I have never had a problem using a wallet to set a fee, but your software sounds like it will make easy work of some of things that we do to experiment and they are normally a pain.   

[achow101]

Ok, this looks fun.  A couple quick questions.  Once the user is sitting there with the unsigned TX, does the software help them take that the rest of the way and broadcast it or is that the end of the line and the user has to figure the rest? 

It will broadcast it for the user.

Is the fee the only configurable part, along with the amount and addresses or can a user play with this and fiddle with various smart contract scripting and such.

Only the fee is configurable via the GUI, but if you know what you are doing, you can mess with the raw transaction itself before it is broadcast. The broadcaster doesn't actually check if the transaction was what it was even modifying. It will just broadcast whatever you give it.

[btc_enigma]

Got project. Will check it out

[savon2k]

Any Trojans onboard?)

[Heacygg]

Hey, any bounty campaigns yet? I would love to participate in one!
By the way, just for the record. Is it written on Java, am I right?

[achow101]

Hey, any bounty campaigns yet? I would love to participate in one!

No, and there never will be.

By the way, just for the record. Is it written on Java, am I right?

Yes.

[bemboo]

Please help me.

I followed all the processes, but after I have my signed transaction text which has to be pasted in the fee booster script, it shows: "Transaction being broadcast. TXID: null". No fee boost happened.

Is it something to do with my Electrum wallet?
I have pasted the modified unsigned transaction text into the sign/verify message window in there, with my current wallet address. It generates the signature (maybe incorrectly ) and then it doesn't work in the script after I paste it and want to send the transaction. It shows that TXID: null message.

Thanks for your help in advance.

[Flex_65]

Hello. I used Feebooster as receiver (created raw tx and signed) but it seems that it decoded Hash 160 into the wrong address, not the one I filled in (with version byte of 0x01 for P2PKH) but it sent to the wrong one (version byte of 0x05 for P2SH). No idea how and why that happened.
Funds were sent to a different address (starting with 3) than the one I filed in, and both have same Hash 160.

[achow101]

Hello. I used Feebooster as receiver (created raw tx and signed) but it seems that it decoded Hash 160 into the wrong address, not the one I filled in (with version byte of 0x01 for P2PKH) but it sent to the wrong one (version byte of 0x05 for P2SH). No idea how and why that happened.
Funds were sent to a different address (starting with 3) than the one I filed in, and bot have same Hash 160.

Post the raw transactions, screenshots of what you entered, and the txids of any and all transactions involved (including the one you are bumping and the bumping tx).

[Flex_65]

Post the raw transactions, screenshots of what you entered, and the txids of any and all transactions involved (including the one you are bumping and the bumping tx).

Thanks. I tried to PM you but you didnt notice/answer. May I ?

[Flex_65]

There is a dangerous bug in Feebooster: the "bumping" CPFP transaction it creates can be wrong, it translates the destination address using P2SH script instead of P2PKH, thus sending everything to a 3... address instead of 1... address as filled in destination field.
Hope this notification can be useful to others.