Sorry... re-reading that, I used the wrong word... it shouldn't have said created, it should have said "confirmed". I think it is an "impossible loop" type situation. The new transaction is spending a UTXO (We'll call it UTXO-A) that can't exist if this new transaction was added to the blockchain, as it is ALSO spending a UTXO that was used to create the transaction that actually creates UTXO-A.

It's a weird "double spend"-type scenario... and possibly just related to the order in which the server is parsing your transaction for validity.

The scenario that I can think of, would be something like this:
1. You create a transaction, that spends UTXO-X, that creates UTXO-A... but this is not confirmed.
2. You then create a 2nd transaction, that tries to spend UTXO-A, while also spending UTXO-X.
3. The server, while parsing the transaction, notes that you're spending UTXO-A and checks to see how this was created, then notes that you're spending UTXO-X... if that happened, then UTXO-A couldn't exist.

BOOM! you get the "bad-txns-spends-conflicting-tx" error... I'm not 100% sure if this is actually correct, but is one scenario I can think of that would trigger this specific error.


No, that isn't the case at all... You can actually create long chains of unconfirmed transactions. I suspect your issue is possibly caused because of the way you're creating "single" address wallets... from single keys derived from an HD wallet??!?

If you're using Electrum, and want to pick and choose exactly which address you want to send from or, more correctly, which specific UTXO(s) you want to spend, you should be using the "Coin Control" features within Electrum. If you use the menu option: "View -> Show Coins", and then select the "Coins" tab, Electrum shows each individual UTXO that your wallet currently controls. You can select as many or as few UTXOs as you want (using CTRL or SHIFT + left click etc)... then right click on the selected coin(s) and select "Spend". This will create a transaction that spends ONLY the selected UTXOs.

That would be a much much much easier way to go about doing what it is that you appear to be trying to do... Why exactly are you creating single address wallets to spend from an HD wallet?

You'll probably also want to edit your post and change your BTC Address to a SegWit address as well...

So why exactly are you not just registering with Apple for an Enterprise Account?

Is it just because you don't want to spend US$299 on a subscription? Because you've now lost close to half of that while dealing with scammers... at least use a trusted Escrow from the forums next time.

You wouldn't need multiple computers spread about... You would only need your wallet backup to be "spread about"... so, either an encrypted backup of the wallet file or an encrypted backup of your seed mnemonic.

Either/or would enable you to recover, should your house burn down.

"Missing Inputs" means that the server has rejected your transaction because you are attempting to spend a UTXO that it does not have in it's UTXO pool... ie. the input doesn't exist, or has already been spent.

"bad-txns-spends-conflicting-tx" is defined in Bitcoin Core as "A transaction that spends outputs that would be replaced by it is invalid." So, it seems it is trying to spend a UTXO that wouldn't exist if your transaction was actually created.

Definitely seems like the issue is caused by having unconfirmed transactions etc...


As long as you verified the digital signature, you'll be fine.

I was going to suggest Tether... as an alternative to TrueUSD, but I note that Tether is now also an ERC-20 token.

So, in essence, all you would need to "store" your TUSD/USDT is to create an ETH address (using MEW or MyCrypto wallet etc)... and then send your TUSD/USDT tokens to that ETH address, then export your private key.

The trick then is to figure out how to convert your BTC to TrueUSD (or Tether)... and then back again.
I'm not sure what you mean exactly by "without using any platform"? You mean you want to convert without using a centralised exchange that might require KYC? If so, the only way to achieve that would be via a DEX (like IDEX or Waves or EtherDelta etC)... or P2P trading (Escrow recommended etc).

Which wallet software were you using? Most wallets do not allow you to use "non BIP39" words... which is what a number of the words you've listed in your "brain seed" are.

When you say it is synced up... is it actually showing transaction history and just has a zero balance (all coins sent out)... or is it just showing a completely "blank" wallet with no transactions?


Also, for future reference... there is no such thing as a "public seed"... your seed is the most critical piece of data for securing your coins... it should remain 100% confidential and secret at all times!

It certainly wasn't a wallet created or released by the developers of the desktop MultiBit wallet... as I mentioned earlier, it was ONLY released for Windows, Linux and MacOSX desktops.

It's possible you were using the "Bitcoin Wallet for Android"... It was also based on BitcoinJ and used a backup file name format of: "bitcoin-wallet-backup-YYYY-MM-DD", which seems awfully close to what you have.

If you don't have another Android device to try installing that on to test... there are scripts available to decrypt and extract the contents of those wallet file backups.


Are you able to open either of these files with a plain text editor like Notepad (or better, Notepad++ etc)?

Do they look something like this:
Specifically... are the first characters "U2FsdGVkX"?

NOTE: DO NOT POST THE FULL CONTENTS OF EITHER FILE HERE! I don't want you accidentally pasting plaintext private keys etc!

Exactly... a "seed mnemonic only" wallet, basically has a single point of failure... the seed mnemonic. Once the seed mnemonic is compromised == Game Over!

Having a passphrase is essentially 2FA. Now you need two puzzle pieces to make it all work... plus, as you say, the "obvious" puzzle (the seed mnemonic) can actually be a red herring with a small amount of coin that could trick the user into believing they got it, but you had "nothing", whilst the real fortune is hidden behind 2nd puzzle piece (passphrase).

Now the issue is... how does one "store" that 2nd puzzle piece (passphrase)? There are 2 aspects to consider... "Security" and "Safety". Security being prevention of unauthorised access of the puzzle pieces... safety being prevention of accidental loss of the puzzle pieces.

The most obvious and arguably most "secure" is... in your head. If the passphrase is relatively strong (8+ chars, mix of upper/lower/numeric/symbols etc) and never, ever leaves your head... the odds of someone bruteforcing that are VERY small.

However, this maybe isn't that "safe" for inheritance purposes as it is likely to go to the grave with you, leaving your Next-of-Kin with nothing

Once you start putting things online, the game changes significantly. Whilst it might increase the "safety" aspect of storing your puzzle piece in terms of having another (hopefully reliable) location to store it to prevent loss and the ability for your Next-of-Kin to get access should the worst happen... the "security" aspect is now greatly diminished.

It is indeed a very delicate balancing act... and different people will no doubt have different requirements.

Still, I view your service as a valid option for folks who want some peace of mind that their family will be able to get ALL the puzzle pieces should the need arise... and as I said earlier, it looks like you've put a lot of thought and care into this project... I hope it all works out!

That is the OPs big problem... the "reputable" exchanges which currently offer SHIFT and BEANCASH, are essentially "off limits" as they do not provide service to users from his location.

So, OP is left with the option of using less well known exchanges like Livecoin (never used, but the reviews are mixed)... or by doing a P2P exchange with another user... however the risks are greater and the chances of finding anyone who actually cares or wants these coins is relatively low.

PyWallet has a --passphrase option that will allow you to dump encrypted wallet.dat files... provided that you know the correct passphrase of course


Also, you need to install Python 2.7.x... PyWallet will not work properly with Python 3

Have you actually checked the email headers to see if it was in fact sent by Paxful? It could be a phishing attempt... ie. Scammer spoofs email from Paxful saying you've had a successful login and to "click here" if this was NOT you... "click here" link takes you to phishing site to try and get you to enter your Paxful login details.

If you have changed your password and/or locked the account... and you're still getting "Successful Login" emails, then chances are high they are just phishing emails.

To view the original message headers, open the message, click the '...' options button in the top-right corner of the message and then select "Show Original".

I had originally "HOPED" that it was some kind of "SECRET" code... but then realised it was "JUST" incoherent ranting

While that might work for your setup... it may not work for others who store their seed offsite and would have a significant time delay between seed being compromised and them knowing that it is... and even with your setup, what happens if you go away on vacation for 2-3 weeks and your house is robbed the day after you leave?

But I digress, we could play this "but what if?" game forever Just realise that I'm not saying that your personal system is "bad" per se... simply that you could (and probably should) offer the option to users who can then decide how they want to do it

Of course, then the issue would be "how one can store an encrypted passphrase... and still allow your family to get access to it in case of death/incapacitation?" you would need some way to store the passphrase for the passphrase! and then you get into an infinite loop of how/where to store passphrases

That looks like a very useful service... you have obviously put a lot of thought and effort into this. Especially around the management of seeds, passphrases and inheritance/disaster planning.

I think you misunderstood what he said... he wasn't claiming that storing the passphrase online was bad practice, he said it was bad practice to store it unencrypted...

As you say, (as long as it is a unique passphrase designed and used only for your hardwallet) if someone finds it, they wouldn't be able to use it without your seed mnemonic. The danger of course is that if your seed mnemonic is compromised, then having the passphrase online could be very problematic... especially if you're unaware that the seed was compromised.


Also, the website is loading fine for me...

Additionally... most of these "coins" are actually just ERC-20 tokens. I would think that adding new ones is relatively trivial after initially implementing ERC-20 support.

However, I do note that Ledger actually refer to the items in their list as "assets" rather than coins and/or tokens... whereas Trezor uses "Coins & Tokens".

Yes... Ledger utilises the BIP39 wordlist... specifically, the English one.

It is a published list of 2048 English words... when the device is first initialised, it generates a very large random number known as the "seed", from which all your private keys are generated... This very large number is VERY important, and needs to be able to be backed up and restored, to prevent you from losing your funds should your device get lost/damaged/stolen etc.

Rather than have users attempt to write down this very large number as a backup (which would be incredibly easy to get wrong, one missed/incorrect numeral would invalidate it!), a system was devised to represent the very large number by a sequence of words, which are generally a lot easier for humans to write down, store and re-enter without mistakes than a very very VERY long sequence of numbers. So, the seed is broken down into smaller "chunks" (24 chunks in the case of the Ledger)... and each chunk is then represented by a word from the list.

As each "chunk" is actually 11 bits long, and 11 bits can be used to represent 2048 numbers in the range from 0-2047... hence the reason why the list has 2048 words.

When you restore your device... and enter your 24 words... each word is converted back into the 11 bit number "chunk"... all the chunks are then concatenated back together... and the device once again has your very large number (aka seed)!

That is a very over simplified explanation of BIP39 seed mnemonics... you can read more here: https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki

Very generous of your mocacinno!

I just used the Windows Subsystem for Linux, "Ubuntu" from the Microsoft Store... and then installed the "electrs" server as per the github instructions... left it whirring away processing the blocks from Bitcoin Core... and now I have my own "personal" Electrum Server that I can spool up in a few moments if the public servers aren't working properly

Slightly overkill really but always fun experimenting

Pretty much... Bitcoin Cash, Bitcoin Gold and Bitcoin SV all have forked versions of Electrum available... so you could probably use those forked versions in conjunction with your private keys to sweep the coins. There may or may not be others for other forks (like Bitcoin Diamond etc)

I'd check the relative values of each forkcoin with coinmarketcap.com and sweep in descending value order... most valuable first. That way you stand to lose the least amount of money if the one of the fork wallets turns out to be nefarious.

Currently, that would be:
Bitcoin
Bitcoin Cash
Bitcoin SV
Bitcoin Gold
Bitcoin Diamond

Ask the Electrum devs how good users are at "checking if the URL is correct"...


Do you have (or are you planning to release) Linux and MacOSX versions of the recovery tools? As far as I can see... all that is available is a couple of Windows .exe/.dll binaries?

Also, given these tools are available from "many other places", are these recovery tools digitally signed, or is there any other way to verify that they are legitimate and not malware or fake versions designed to simply steal passphrases+salts?


Except for the fact that you need some executable Windows binaries, developed I assume by Bitfi, to recover your funds should your device be unusable for whatever reason... is that correct?