If you made an intervening tx then your wallet won't be sending the same coins for your latest tx as it did the first time.  It will send the same amount, not the same coins.  Or is my understanding faulty?
For that matter, even if you make both tx's one right after the other, the typical wallet won't send out the same coin in the second tx...

In Mycelium you can increase the fee manually.  Tap the miner fee button to make it change from "normal" to "priority," which adds about .0001 to make it .0002, depending on what the normal fee was.  Mycelium calculates the normal fee by tx size.
If you want .0004 you may be out of luck.

One jerk can jam up Bitcoin for the entire world?

Sorry I haven't been paying attention to this thread.  Yes, they enabled withdrawals.
I think there are others like me, whose difficulties were resolved, but didn't think to come back on this thread and report it.

For ten or twenty million bitcoins to become worth hundreds of thousands of dollars each, trillions of dollars would have to go *poof*.  Which means the world economy would have to go *poof*.
Does this make sense to anybody here?  You don't go from a few billion to trillions like walking across the room.  It's more like having a hurricane blow the roof off and getting sucked up into the sky.  But people are talking about it as if it were a routine matter that fits into present thinking.  It's a fantasy.

You can generate new addresses, but it's a hassle, because you can't do it in the wallet.  You have to do it on your own.
Of course it would be nice to have that feature in the wallet.  Then someone with a need like dooglus expressed could accomplish that need without using multiple accounts.  It would mean adapting the wallet to show more than one receiving address.
And while we're on the subject of address lists --
Mycelium shows a list of all the HD addresses used in the past, in alphabetical order under the address signing feature.
That's nice, because you can look up an address; but you have to know the address you're looking for.
But if for example you want to see the last three addresses you used, then you won't be able to locate them in the list, because you don't know the addresses, you only know where in the HD sequence (not the alphabetical sequence) they appear.

I would like to be able to see addresses in the signing list chronologically.  And then it would be a simple matter to generate and append several future addresses, which you can copy and transmit to several people at once.  You won't have to serve one customer at a time, or use a different account for every customer.
This would not require any changes to the wallet's main send/receive page.
After receiving funds to addresses that the wallet has not actually generated yet, it might be necessary to refresh the wallet in order to bring it up to date.

Don't presume facial recognition data remain confined in a DMV database.  It's going to get spread around promiscuously.  Don't delude yourselves that there will be any enforceable segregation whatsoever of sensitive personal identifying information.  
Case in point:
The government uses facial recognition to track you through surveillance cameras.
One doesn't have an option of keeping his photo out of the government database.  You can't live in modern society without picture ID.  
There is not a word or so much as a whisper to be found in motor vehicle department published policies of the states in regard to segregating or protecting identifying information in the photographic form.  Your photograph is identifying information.  You would be alarmed if your social security number were made available, but no one here thinks releasing photographs poses any risk.
Once the government has the recognition file and tracks you through surveillance cameras, you turn into just another lemming.  

Yes, you're lemmings.  Big brother is watching you.

You don't even live here, but you take it on yourself to tell us it's hopeless.
You need something better to expend your energy on, what little there is of it.

Sign this petition against the use of facial recognition technology by States in driver license photographs.

http://petitions.moveon.org/sign/forced-into-a-facial

By rights, one shouldn't need multiple accounts to generate multiple receiving addresses.
Second and third accounts are meant to enable more than one person to use the same wallet, or for one wallet user to organize the wallet's transactions according to different uses, like a bookkeeping file system.
Forcing dooglus to create new accounts, not because the transactions have different purposes, but simply because the account he's using is limited to a single receiving address at a time, amounts to misuse of bip44's multiple accounts architecture.

If you need more than one receiving address in the same account at the same time, you can generate them yourself:
https://dcpos.github.io/bip39/
Under derivation path -- Mycelium Wallet, m/44'/0'/0'/0
you will see receiving addresses (if you want to see change addresses use bip44 and set m/44'/0'/0'/1).

If Mycelium says your account has let's say 100 private keys, scroll down the derived addresses in the mnemonic code converter until you see the current receiving address.  It will appear before you get to 100 (because change addresses are not shown).
If your current receiving address appears at 53 on the list, you may use addresses 54 and 55 to receive coins...  

Wazrning:  I haven't tried this method yet, so it should be tested with a small transaction to make sure Mycelium doesn't end up garbling transactions somehow.

Edit:  I tested it.  I sent small amounts of xbt to the two addresses (call them B and C) after the current receiving address (call it A).  Mycelium picked up the transactions and updated correctly.  Then I sent xbt to address A, and Mycelium picked up on that as well.
So you can send to addresses before or after the receiving address shown, and everything ought to work.

So you'll have the object sit on the scale, and the people lift the scale, right?  That's the only way to find out if the weight of the object changed.


Empiricism trumps all, and I do mean all.

You can generate the addresses using this
https://dcpos.github.io/bip39/
You can generate as many addresses as you like.  If you know the last address your Mycelium HD wallet generated, then you only need to generate addresses until you reach that one.
If you don't have access to your Mycelium HD wallet, just keep generating addresses and checking them against the blockchain until you reach an address that has never been used.
I tried it for my wallet, which I have been using long enough to generate more than 200 addresses.
I opened the converter, offline of course, typed in the words and clicked Mycelium.  It reached the last address of my wallet after only 84 addresses.  Probably the reason for this is that the converter only generates the receiving addresses, not the "change" addresses.  
If somebody can explain why the converter generated fewer addresses than Mycelium in actual use, please pipe up.
Naturally, you can find the change addresses to your receiving addresses by looking on the blockchain.

According to the IRS,
"A wash sale occurs when you sell or trade stock or securities at a loss and within 30 days before or after the sale you...
Buy substantially identical stock or securities..."

I did a lot of trading last year.  I had a net loss.  And as I was going back through the records of my trades, I realized that if the wash sale rule applies to my trading, most of my trades with losses will be disallowed.  The gains will remain, and be taxed.  I would go from having a pretty substantial net loss to having huge gains on the Schedule D.  So not only will I have lost money in real terms in 2014, but I will owe a lot of tax on non-existent gains.

The IRS defines bitcoin as property, not as a "stock or security."
By closely applying the letter of the IRS publications, I would say that the wash rule doesn't apply to bitcoin trading.

Opinions?  Maybe someone even has direct experience of dealing with this.

I want to know how the nuts and bolts work.  Nobody ever talks about that.  It's all pie in the sky.
EXACTLY how does one handle tethers?

Bitfinex tether announcement says:
"Tethers can also be withdrawn and held in any Bitcoin wallet where you control the private key"
But on the withdrawal page it says:
"Please confirm that you are sending tethers to a Tether-enabled wallet. Tethers sent to a non-Tether compatible address may be non-retrievable by the recipient."

Where is the step-by-step instructions?

I went to tether.to and requested an invite.
Of course, I prefer not to use a web wallet like omniwallet, which is why I want to know how to transfer tethers to an ordinary bitcoin wallet under my control.

I just have a simple question about using coinreporting.com, creating accounts and importing data.
I'm a little unclear on the correct sequence of steps to submit my trades from an exchange.
Coinreporting.com has a "Learning Center" with an faq and so on.  For entering data from a bank account or crypto exchange or whatever, you have to create an account.  Coinreporting's learning center says go to
accounts > add new account > digital exchange
type in a name, and click add account.  There is a separate importing function, and how to import trade data into the account after I create it is unclear.
I have three accounts at Bitfinex.  Say I go to the accounts tab and create three accounts named BFX1, BFX2 and BFX3.
I will have to import csv files from Bitfinex for three different accounts.  How do I assign each csv file to the correct account created in the first step?  Or do I download first, then create the accounts?  I would appreciate some gentle ELI5 from someone a little more familiar with this stuff who has used coinreporting.com.  I'm inexperienced and need to get started with baby steps.

Leverged longs are diverging from price
https://tradeblock.com/blog/bitcoin-leverage-and-price-diverge-for-the-first-time-in-2015
What is the significance of this?

Hex is suitable.
Get the arithmetic right, and you get the encoding right.
Just don't use base64.
Base64 is a big-endian file encoding scheme that takes the data to be encoded and splits it up into groups of 24 bits (3 words of 8 bits).  If there's any slop, base64 encoding pads it on the little end.  Emphatically not what you want.

Support says tx ID is supposed to always stay the same, so that explains that.
But I'm having problems making bittrex and poloniex work in mobile browsers.  Bittrex doesn't work in Chrome browser for Android, for the reason I posted.  I thought of trying a different browser, and it turns out bittrex works in Dolphin.
But poloniex is almost useless in all the browsers I've tried, Chrome, Dolphin and Opera mini.  Just putting in a couple of trades takes as much as half an hour.

I went to the deposit page and generated an address and payment ID.
I am using a tablet.
The copy function is screwed up when I try to long press on the payment ID to highlight it.
The number only stays highlighted for about half a second.
So I quickly hit copy.
But when I pasted the payment ID in the wallet I was transferring the xmr from, it pasted something else entirely, a snippet of code or something.  I kept trying.  Eventually a google page appeared that said "your search did not match any documents" and showed the payment ID, which I was then able to copy.  I entered the transfer in the originating wallet.  OK.
But now I have another problem.  The Bittrex xmr deposit page is stuck on that payment ID.  There's no way to make it generate a new one.

Maybe I did something wrong?