Theoretically yes... but do pay attention to what outputs are being generated before you sign/broadcast the transaction... make sure that any change generated (ie. you're not spending the full amount) is being sent to an address that you have the private key for...

If that private key is the ONLY key in your Electrum wallet (ie. you created a new wallet and imported just the OpenDime private key) then I *believe* it should send the change back to the OpenDime address... but I've only tested this on TestNet addresses/transactions. Suggest you use the "Preview" button prior to sending and make sure the output address with change is the same as the input address

No... it lets you check the balance of a sealed device... and if the device is unsealed, you can also send funds:


You cannot get funds out of an OpenDime if it is sealed, as the private key is not known by anyone (even the person that first setup the device with funds) and cannot be viewed until the device is unsealed.

There are quite a lot of similar words in the 2048 word list used by the Ledger (and most hardware wallets)...

ie. kit, kite, kid, kind
act, action, actor, actress, actual
clap, claw, clay

You get the idea... So it's possible that you've simply written down a "similar" word in your list of 24 by mistake.

I have previously had success finding one or two word errors by using the seedrecover.py written by gurnec: https://github.com/gurnec/btcrecover/blob/master/docs/Seedrecover_Quick_Start_Guide.md

You'll need to be able to install python and a couple of library dependencies... but the instructions listed are fairly easy to follow.

You *could* transfer more coins to the associated address, as the coins are stored on the blockchain, not on the device itself... and the blockchain has no knowledge of whether or not the OpenDime device is sealed or unsealed or even that the public key/address that the coins are being assigned to are even on an OpenDime device

You *could* also transfer just a small portion... or all of it... or none of it...

The main reason NOT to do any of these things is security... once you pop the seal, the private key is then able to be accessed. While perhaps unlikely, it is not impossible for malware to be able to access the private key once the OpenDime unsealed and connected to an infected computer.

Also, as far as transferring less than the full amount, you run the risk of losing bitcoins into unknown "change" addresses if you are not very careful about how you go about constructing the transactions to withdraw smaller amounts. It's possible, depending on the wallet you use to "spend" the contents of the OpenDime, that the leftover change will end up going into a change address that you do not have the private key for and are therefore unable to spend the coins from! Ref: http://bitzuma.com/posts/five-ways-to-lose-money-with-bitcoin-change-addresses/

You misunderstood whatever you read... or whatever you read was wrong.

You cannot "cancel" a transaction. Once it is broadcast to the network, there is nothing you can do to remove it. It will either confirm (possibly after a LONG delay ie. days)... or the various nodes on the network will eventually drop it from their mempools and the transaction will disappear.

All you did was remove the transaction from your wallet... you didn't (and can't) remove it from the mempools of other nodes. Then when you attemped to respend, the network would likely have rejected your new transaction as a "double spend" as it still had your original pending transaction using the same inputs.

low-medium? you used 33 sats/byte... that's just plain low.

I would suspect that ViaBTC did not accept it because it either had unconfirmed parents or your transaction didn't propagate well... it simply may not have been in their mempool. Sometimes it pays to rebroadcast your transaction using their broadcast tool: https://pool.viabtc.com/tools/BTC/broadcast/ before you try to accelerate it, just to make sure they have it



Who knows, maybe they were able to accelerate it, maybe they're friends with a mining pool owner... maybe they coughed up the fees to pay for acceleration...

The first accelerator is operated by a mining pool... they reserve 100 slots every hour for "free"... as long as your transaction does not have unconfirmed inputs, and a fee of at least 10 sats/byte... you can try and nab one of those 100 slots. If successful, they'll include your transaction regardless of your fee (as long as it is 10+ sats/byte of course!)

The 2nd one supposedly has links with mining pools and can get your transaction included for free (if under 500 bytes, usually a max of like 3-4 inputs)... or $4 if above 500 bytes in size...

There... fixed that for you.

There isn't a guaranteed "15 minutes"... I've seen stretches where ViaBTC don't mine a block for up to 6 hours or more... if they don't mine a block, there is no way for them to include your transaction!

Currently, they have about 1/9th of the total hashrate... so expect them to find about 10-15 blocks a day... or around one every 1-2 hours on average.... assuming of course that their percentage of the total hashrate doesn't change (and making allowances for variance and "luck" )

Basically, it is a form of laminating... the idea being to protect the paper inside a plastic covering to protect it from wear and tear, ink/paper breakdown and the danger of water etc.

By vacuum sealing or laminating your paper wallet, you make it less likely to be damaged to the point that you can no longer read it. It is one of the major drawbacks of a "paper" wallet... while they are more "robust" in some ways that desktop or hardware wallets... they are vulnerable in others.

So you've copied a valid bitcoin address from another application... and when you click the "paste" button in Electrum it doesn't do anything?

I've just tested this by copying the example bitcoin address from this page: https://en.bitcoin.it/wiki/Address (1BvBMSEYstWetqTFn5Au4m4GFg7xJaNVN2)... Then went into Android Electrum and clicked the "paste" button, the address was put into the "recipient" field fine.

Do you get any error like "invalid bitcoin URI" or anything when you click "paste"?

Sounds like you're going to need to repair your OS rather than worry too much about Electrum at this stage... The "Library" directory tree is an OS level data store, rather than something specific to Electrum. Maybe this thread might help? https://discussions.apple.com/message/18731776#18731776

It's for "Snow Leopard" rather than the new OS versions, but I would expect you should be able to do something similar (ie. "Repair OS")


For the record, to create a new wallet in Electrum, you just need to use the "File -> New\Restore" option!

Sounds like a "Gap Limit" issue. If those payments are out past the Mycelium "gap limit", then the wallet won't find them... Gap limits exist so that wallets don't search forever looking for transactions that don't exist on unused addresses... the theory being that the large majority of users use addresses consecutively... they don't generate 100 addresses, spam them out... and get transactions sent to random ones out of order.

I think the Mycelium Gap Limit is the BIP44 default of "20"...
Basically, if it is hunting through the list of generated addresses and finds 20 unused in a row, it will stop searching. Once one (or more) of those "20" addresses becomes used, the gap limit "search window" will slide along and more addresses will be searched... finding more used addresses.

Looking at that code, you cannot alter the gap limit in Mycelium ("static final" is a fixed constant value)... to confirm that those transactions have been received, you'd need to import your key into another wallet like "Electrum" on a desktop that allows you to manually configure the Gap Limit size... or use the BIP39 tool (https://iancoleman.github.io/bip39/) and check the addresses by hand in a blockexplorer...

Or you'd have to download the source code... alter those values and compile your own APK

You mean like the way they "supported" the Bitcoin Cash fork... By not allowing anyone access to their BCH until February??!?

It's a bit hard to move your funds "asap" when the exchange doesn't actually allow you to move them

By Feb, there is a good chance that BCH will be trading at DOGE levels or not at all given it's current downward spiral... now at <0.07 BTC

Here is a (slightly) outdated list of wallets and service providers that are currently (or plan to) supporting SegWit: https://bitcoincore.org/en/segwit_adoption/

NOTE: It seems it was last updated about 4 weeks ago... so there may be some errors or omissions

You are exporting a password protected key file from MultiBit classic... This actually encrypts the contents of the file, making it useless for what you're trying to achieve. It probably looks like this:




You need to enter your wallet password at the top, and then leave the password field at the bottom empty... Select the "do not password protect export file" option:



Note: you don't want to copy the datetime stamp at the end of the private keys when trying to import them into Bitcoin ABC...

This will create a plaintext version of the export file which you will find then contains the private keys in the correct "WIF" format... Ie. You'll see keys beginning with a "K" or "L"... Like this:

No, when you send a transaction, it doesn't attempt to send to multiple "versions" of the same "address" at the same time...

think of it like before SegWit... You had "1" addresses for "normal" Bitcoin addresses And "3" addresses for "MultiSig" addresses... When you sent to a 1, there wasn't some "not used output" going to a "3" address as well that miners were trying to process.

SegWit and legacy are just slightly different formats for representing the same thing... Where to assign control of some Bitcoins...

If you say, send to legacyAddressA, then ALL miners can only see a transaction that sends to legacyAddressA. If you say send to SegWitAddressA, then ALL miners can only see a transaction that sends to SegWitAddressA.

Visit Jaxx.io website and then click on the "view source code" link at the top... It's a very frustrating way to attempt to view it, it doesn't seem to show the filenames or directory structure etc...

But technically, it's the source code...

Then this would tend to confirm my suspicions... You have created a new seed on the PC wallet... Sent a small amount to it... And then restored THIS wallet onto your Android, removing the original Android wallet.



Apologies for not being more specific. Your 12 word seed backup phrase goes into the "BIP39 mnemonic" box, you shouldn't really need to do anything else except make sure the BIP44 tab is selected under "Derivation Path". Everything else should be OK on default settings... The "BIP32 Derivation Path" should show as m/44'/0'/0'/0



Firstly, you're welcome...

Secondly, yes... As I've said, whenever you first install Jaxx on any given device... Unless you specifically choose "Pair/Restore" it will generate a unique wallet and backup phrase.

As far as I can tell from the information you have provided, you have somehow put the PC phrase onto the Android... And you don't have the Android phrase written down

I would still recommend that you try using the offline webpage with you backup phrase and see if you can see the addresses from the Coinbase transactions. It might still just be a case of Jaxx failing to find your transactions.

Also, if you haven't already, hunt through all your notes looking for another backup phrase that you might have simply misplaced.

Best of luck.

There was another user that had similar issues when trying to restore a 2FA wallet, but I can't find the thread or remember exactly what it was that fixed the issue...

Possibly it was fixed by shutting down Electrum, removing the blockchain_header file from the Electrum data directory and restarting Electrum... But I'm not 100% sure on that.

It's also possible that it is a network issue and Electrum is having trouble connecting to a server nfor whatever reason...

You could always try on another PC and see if that helps. Meanwhile I'll see if I can locate the other thread...

In 2.9.3, you want to go to "File -> New\Restore -> Standard wallet -> I already have a seed"... Enter your 2FA seed... You will then be asked if you want to "keep or disable 2FA"...

You can either "keep" and reset your Google Authenticator... Or you can select "disable" and it will create a special wallet that had 2 of the 3 private key chains required to sign the transactions. You can then send the BTC to a new wallet.