11331 satoshi's for a 226 byte transaction comes to 50 satoshi per byte. That's a decent fee, altough https://bitcoinfees.21.co/ teaches us you should have added 100 satoshi's per byte for a 90% chance of getting in the next couple of blocks.

This being said, you still have a 90% chance of getting your tx confirmed within the next 500-ish minutes.

Just to set the record straight guys, i never said the minimum fee was 15k satoshi's... Somebody in this thread probably looked at the link, and calculated that for their transaction 15k satoshi's was the minimum fee in order to have a decent chance of getting their transaction confirmed in the timespan they wanted.

The fee is not something you pay to an exchange. The fee is given to the miner so he has an incentive to add your transaction to a block. If you cheap out on the fee, you have a chance your transaction will never be added to a block, hence remains unconfirmed and eventually gets kicked out of the mempool (gets forgotten).

It is possible some scrupulous exchanges add an extra fee on top of the miner fee and keep this one, altough i don't know any exchange that does this, it's a possiblity.

https://bitcoinfees.21.co/ would be the best place to look at when deciding which fee to add to a transaction.

The rest is still the same:
- estimate the transaction size in bytes
- look at the website posted above
- multiply the bytes with the amount found on the website, round up and add as a fee

The fee is calculated based on the size of the transaction.
The size of the transaction depends on the amount of inputs and outputs.

If you filled your wallet with dust inputs (for example, faucet earnings), it is well possible the wallet decides to add a huge fee when using hundreds of dust inputs to create one or two outputs.

For example: you requested a payment of 0.001 at 1000 faucets... This adds up to 1BTC
You want to spend this one BTC:

The size of your transaction is estimated as:
in*180 + out*34 + 10 plus or minus 'in'
1000*180+1*34+10 = 180044 bytes.

https://bitcoinfees.21.co/ teaches us you should add 80 satoshi's per byte to have a 90% chance of getting in the next couple of blocks...
180044*80 = 14403520 satoshi's = ~0.145 BTC fee

At the other end of the spectrum: if you bought 1 BTC from an exchange at once, your address has 1 inputs. When you want to spend this input, your fee would be (1*180+44)*80 = 17920 satoshi's (0.0001792 BTC)

In both virtual cases, you're spending 1 BTC worth of inputs, but in the first case you need to pay 1000 times more in fees to get a decent chance of getting added to a block in a short period of time.


Could you verify if you funded your wallet all at once, or with loads of small inputs?

The derivation path can differ from wallet to wallet... but by searching the correct path and adapting the script, it should work

I'm running on ubuntu 16.04.1 LTS (Xenial Xerus) running python 2.7 and i have installed bitcoin-python and pybitcointools in order to write some basic scripts.

There seems to be some confusion here... Tor is not a company, i'm pretty sure the developers of the tor browser have little or nothing to do with tor wallet.
Eventough using the onion router to access the Tor network might be a good thing for extra anonimity, using an online wallet in the darkweb might not be such a good idear (IMHO)... There are a lot safer ways to get some extra anonimity (again, IMHO).

since you wanted to Do it yourself
in python, this works to create the first derived address using my electrum xpub


you'll need to put this one in a loop to browse trough all keys* , and bechmark it for speed tough... I have no idear if it's slower or faster for your implementation

* for example, the derivation of the second address would be:

EDIT: was a bit bored at work (slow day), decided to do the next part of the work for you, and i updated my post accordingly

Takes 5.157 seconds to generate 1000 addresses , since you mentioned your old script takes 0.1s/address, and you need 0.01s/address, i guess 0.0051 is well within the requested range (it's allmost 20 times faster instead of the requested 10 times)...

Second edit, since electrum uses m/0/<n> for receiving addresses, and m/1/<n> for change addresses, generating change addresses would be done by changing line
childkey1 = bip32_ckd('xpub_my_electrum_xpub', 0)
to
childkey1 = bip32_ckd('xpub_my_electrum_xpub', 1)

I suppose you're talking about the testnet faucet, right? In that case, make sure you're adding an address that was generated with a testnet wallet!
Could you post the address you're trying to make a claim for?

Why take the risk? Just run bitcoin core or electrum over tor:
https://en.bitcoin.it/wiki/Tor
https://www.reddit.com/r/Electrum/comments/3bwyzf/how_do_i_route_electrum_through_tor/

 

If you want to practice transactions, you can always create a testnet wallet, claim testnet BTC and practice creating transactions, signing, creating paper wallets,... etc riskfree and for free

You can claim here:
https://testnet.manu.backend.hamburg/faucet

Testnet wallets include:
bitcoin core, coinomi,...

https://en.bitcoin.it/wiki/Testnet

Don't forget to return the testnet coins once you're done learning

Make sure your computer is 100% clean. They accessed your account, but didn't change your password.
This could either mean they know your password, but didn't want to attract any attention to themselfs by changing it OR it could mean they don't know your password either, but they used your computer to post scam threads (since you need to know your password in order to change your password).

I would advice to boot from a clean linux distro, change your password and email from within the clean environment to a new/unique/random one, make sure you have a staked address,.
Afterwards, i'd scan, rescan, re-rescan or even re-install your pc (if unsure), then i'd start to find out who got scammed by your hacker.

If it's free power, and you have space to put 6 antminer S9's, i'd probably go in that direction.
Do be carefull tough, your electric wiring needs to be OK for this, and they'll produce a lot of heat and noice.

6 antminers:
6*$2100 = $12.600 (maybe you'll find some coupons to make it a bit cheaper, but you'll have to add shipping and custom fees)
6*1500W = 9Kw
6*14Th = 84Th

84Th makes you about $55 a day at current diff, block reward and BTC price
http://www.coinwarz.com/calculators/bitcoin-mining-calculator/?h=84000&p=2600.00&pc=0.0&pf=0.00&d=281800917193.19600000&r=12.50000000&er=738.25000000&hc=0.00

The roi will probably be between 7 and 12 months (depending on the diff increase and if you're lucky with the antminers, cause they can also break)

An other option would be to be cheap second hand ASIC's on this forum. Just make sure you calculate the ROI beforehand. A thirth option would be to invest in decent GPU's and mine altcoins.

There used to be a couple other good companies, but AFAIK, those two are the two only reliable producers that are still producing ASIC's at this moment.

About canaan: the 6 th/s miner is their new product, there was a quick review on this forum, but i can't find the link anymore. You could potentially buy an avalon 6 on this forum, it'll probably be a lot cheaper now.
From what i've read, the AvalonMiner 721 is less energy efficient as the antminer S9, and more expensive, but it's very well built and the company actually seems to care about it's customers (i'm not a miner b/c my electricity rate is waaaaay to high, so this is all info i've read on this forum myself)

Like all the others before you (in this thread)
=> basically, the fee wasn't big enough in these tx'es. In your specific case, you also used the output of an unconfirmed transaction as input for a new transaction.

The sollutions are basically the same:
- wait, rebroadcast the hex if the tx is dropped from the mempool (see this thread)
- contact kano, macbook-air or quickseller and offer a reward (see this thread)
- construct a double spend  (see this thread)
- attempt a RBF  (see this thread)
- attempt a CPFP  (see this thread)

No problem... There is no harm in rebroadcasting a tx every couple of hours, altough it's only actually necessary when the biggest part of the network dropped the tx from their mempool.

Paying a higher fee is tricky. It can be done if you marked the tx as replacable when you created it, altough i'm not sure if the multibit gui already implemented this feature. You could also doublespend the inputs and generate a tx with the same output, but i think that's a very hard thing to do using multibit (since it does not allow you to export your private key, nor allows you to pick your inputs).

What you could attempt is a CPFP: generate a new tx using the unconfirmed outputs of those tx'es as inputs (or the output to your change addy). In this new tx, make sure the fee covers both the old tx and the new tx. This is also a longshot tough, since the miner has to do the effort of calculating wether he could get more fees by adding a low fee and high fee tx to his block.

A last option would be to contact quickseller or macbook-air or kano on  this forum and offer a reward if one of them includes your tx'es in a block they're currently solving.

The easyest sollution is to get the signed transaction hex by adding ?format=hex at the end of the above urls, for example:
https://blockchain.info/tx/7b38fe51ae4716031f50f0b2b586e0c326ccaa474980818daf2ddb9ac92e9a03?format=hex

Keep those hex'es in a seperate file. If the network drops the tx, you can at least rebroadcast it.

This will, in no way, speed up the addition of your transaction to a block, it's just a precaution you can take in case your transaction gets dropped from the mempool!

If you want the tx'es to be added to a block faster (confirmed), you can contact kano, macbook-air or quickseller and offer a reward for them to add your tx'es to a block.

Other than that, you could try to double spent the inputs, do a CPFP or a RBF, but those techniques are difficult and do not guarantee a confirmation either (they just enlarge the chance of a confirmation).

is this what you're looking for?
http://btc.blockr.io/api/v1/tx/raw/66c0479bf5788ece1ee086bab04bc524c3f17a358e19f6206afa3808cff4a54f

0100000002e2acad19ecff82269cd2928946daa0ff1ffbf744115af26c16f4ff48932eca6101000 0006a47304402206429572a7b0c306cd8783e030ff8e17c104facc7830ca8236fa5758af15d6583 02203de82eddaf30504cc44a6fe8c4473af41cc830f8a9cdf265d6cc62c6362d8caa012102044fc 1bad78cfa400aecf07c6aa1cffb15637054187e2fc2c769b55a0592ef87ffffffff0ae79d6df611 32d50ffb350e1fbff861020d837e4973cda427ec5ac741169287010000006b483045022100fc83c 2a2723ab6a7430aa91ed0a7932cb26d911a0c059dfb793dc9eeee3f3dd802207e81f9e54af9df0b f3c0fed960f2ac289bb2ca90940ebc9d16291179b5efa611012102044fc1bad78cfa400aecf07c6 aa1cffb15637054187e2fc2c769b55a0592ef87ffffffff023cac1400000000001976a9145a20a4 d3e7aca3d76c71bc72534a1b1a8cfb70fb88ac31090901000000001976a914b50bb9d83cd287234 d86cfb05e9f1dce199b0d7588ac00000000

I took the liberty of pushing it trough my node, so it's in blockchain.info's mempool again

quoted and verified using electrum 2.7.12

Edit: also verified online: http://wallet-2sx53n.sakurity.com/#verify?vrAddr=16YS5Z7Fkt5zsRQwpNbm7jTybZr2FPGhYx&vrMsg=This%20is%20Walletor%20from%20bitcointalk.org%20today%20is%202016-11-24%2011%3A01%3A32%20UTC%20%2B2%0AThis%20is%20my%20signature%20for%20my%20bitcointalk%20stake%20address%2016YS5Z7Fkt5zsRQwpNbm7jTybZr2FPGhYx&vrSig=G1388HMVP8zkLCZuogTiZMdAjE1PcRP%2FlekeL9Yb3fBuYtDze%2BPOqcAPiJLv8%2BviaIn0Rc0EUL1rL2Wwu%2BMI1lk%3D

since you're using bitcoind, something like this should work in your case:
bitcoin-cli createrawtransaction "[{\"txid\":\"91c9c046afda04186be488f784e7e0619b5f9eae3974a9951411b78af421f9dd\",\"vout\":1}, {\"txid\":\"72816bed825f0f488003949901fa7275887991abe8e7983a1117cd1e62114ec1\",\"vout\":2},{\"txid\":\"b0a61e7842b556ced310357aabb7df7ed88097e09d6fd6b25efccb413e189bf4\",\"vout\":0}]" "{\"188DN1tYGQsUbGgXuKmhuo8ATd5T4npsvs\":0.11679356}"

This should create a raw, unsigned transaction using the listed inputs (the 3 tx-ids, and which output of the txid has to be used as an input) to create an output of 0.11679356 to 188DN1tYGQsUbGgXuKmhuo8ATd5T4npsvs.
The sum of inputs - the sum of the outputs = the fee... Do your calculations to select an appropriate fee this time!

(in*180 + out*34 + 10 plus or minus 'in') * recommanded fee
(3 * 180 + 1* 34 + 10) * 100 = 58400 satoshi's = 0.000584 BTC

inputs => 0.11437916 + 0.0025 + 0.0003144  = 0.11719356
inputs - fee = 0.11719356 - 0.000584 = 0.11661356
so if you'd create an output of 0.1166 just to be sure, you should be ok


results in

Afterwards, you can use bitcoin-cli to sign the raw transaction.
(bitcoin-cli signrawtransaction HEX)

Do your homework and doublecheck my inputs/output, decode the hex and make sure you agree with the unsigned hex before even attempting to sign it!!!!!!!!!!!!

I don't have a lot of experience with armory, but i think you could easily export the private key of the address whose inputs you want to double spend...
Using this private key, you could use bitcoin core or the sourcecode of coinb.in to create a transaction using the same inputs as the stuck transaction, then sign this raw transaction using the private key and broadcast the new transaction.

If you could show us the tx id of the stuck transaction, i could make a raw, unsigned transaction doublespending the inputs of the stuck, unconfirmed, transaction, so you only have to sign and broadcast it.