|
It has nothing to do with the "wallet"... unless you are depositing to an online service where you have an "account" (as opposed to an actual wallet with access to the private keys etc.) where they only credit your account after a certain number of confirmations or something like that.
The blockchain and bitcoin network is wallet "agnostic"... it doesn't care... it is just recording transfer of bitcoins from one address to another. It has no knowledge of what wallet these addresses are being controlled by.
It is probably just different network conditions (ie. number of unconfirmed transactions and the fees they are paying) and/or the fees being used that resulted in your transactions to particular services being delayed.
|
|
|
|
is there an wallet that can control fee after send ?
if i send with small fee so back and edit fee to be high
Any wallet that supports "Replace-By-Fee" aka RBF... you will be able to bump the fees provided the transaction was originally marked as "RBF" https://bitcoincore.org/en/faq/optin_rbf/https://en.bitcoin.it/wiki/Transaction_replacementI can confirm that Bitcoin Core and Electrum both offer "Opt-in" RBF... ie. you need to use specific settings to enable it. |
|
|
|
...Is it better?
That sounds like it should achieve your goals of being able to send directly from your paper wallet without having to import it into a wallet first. Although, I still think you are needlessly complicating things. If your concern is still about privacy and wanting to mask your IP to conduct the transaction... why not just sweep the contents of your paper wallet it to your new paper wallet using a copy of Electrum that is connected via TOR?  |
|
|
|
I want to transfer my BTC (0.4) to my Ledger Wallet.
The transaction fees are round about $80! Is there an other, cheaper way to swipe my coins from paper wallet to the ledger?
Pretty easy really... Step 1. Import Paper wallet private key into Electrum Step 2. Send BTC to Ledger using fee of 0.00010001 BTC/kB (aka 10.001 sats/byte) (you'll need to set Electrum to allow manual fees) Step 3. Use ViaBTC to accelerate transaction Step 4. Profit |
|
|
|
I'm newbie and sorry for stupid question, I exported private keys from electrum, I was wondering why there is 26 of addresses and private keys, I thought it would be one.
Electrum uses hiearchial determistic(HD) seeds to generate addresses. Using the seed, the client can generate a master private key which can generate a practically unlimited number of addresses. The default behavior of Electrum is to generate addresses till they find an ąddress with Bitcoins and generate an additional 10 addresses after that point. Judging by that, you likely had 16 transactions using your wallet.
Close, but not quite... The default gap limit in Electrum is 20 for receive addresses... and 5 for change addresses. On initial wallet creation, Electrum generates your 1st receive address, and then searches for the next 20 consecutive unused receive addresses looking for coins/transactions before stopping. It then looks for the first 5 consecutive unused "change" addresses for coins/transactions before stopping. So you have 1 + 20 + 5 = 26 addresses... with 26 private keys  |
|
|
|
when I open Electrum an error occurs and I'm forced to go to console.
What is the specific error then? Without knowing what it is actually saying, no one is likely to be able to help... |
|
|
|
Is it a BTC vs mBTC display units issue?? By default, Electrum displays mBTC units (milli BTC)... Try: Tools -> Preferences -> Appearance And set the "Base Unit" to BTC... see if that makes everything "look right" NOTE: due to a weird little bug, you might need to shut down the preferences dialog after setting changing from mBTC to BTC, before you are able to increase the number of decimal places to 8. I prefer 8 as it shows it all the way to the last satoshi |
|
|
|
|
Honestly, I don't understand why they won't pay as long as you're willing to pay the fee they require regardless of the amount involved? That seems like they're just ignoring income.
If I was running a service like this, and you had only 0.2 deposited and you were willing to pay 0.1 fee, I'd still go ahead and do it... it isn't like the amount involved changes the amount of work they have to do... and they'll still get paid the same fee regardless of how much you get back.
I like philipma1957's suggestions... especially the one about being polite... staying calm and not getting angry will likely go a long way to achieving the solution you're after!
|
|
|
|
As far as I know, you can't start from the Address and work out if it is compressed/uncompressed. The address is the result of a one way hash, so you can't tell if it was created from a compressed or uncompressed public key. You'd need to start with the private key and go from there... Have a play with https://www.bitaddress.org/ Generate a new private key and then put it into the "Wallet Details" tab... you'll see every private key generates a compressed and an uncompressed address. You might be able to tell by looking at previous transactions involving those addresses on the blockchain and inspecting the input sizes... ~148 bytes = compressed... ~180 bytes = uncompressed |
|
|
|
|
You can reuse addresses... There is no rule stopping you from using the same address over and over[1]... it just isn't recommended for various security and privacy reasons. So, your coins should be fine. Once the transaction confirms, you should get your bitcoins into your wallet.
[1] The only time this might be a problem is with "one time" deposit addresses on an exchange... they may not credit your account if you deposit to an old address.
|
|
|
|
Looks like that transaction *was* at the end of a VERY long list of unconfirmed transactions... that were then all "orphaned" when a previous output further up the chain was double spent and confirmed into another transaction... I was able to go back about 50 transactions, before chain.so decided I had too many requests and blocked my IP temporarily... so I got bored and couldn't be bother tracking how far back it REALLY goes... could be a chain of more than 100 unconfirmed transactions!!    The last one I looked at was: https://chain.so/tx/BTC/5e0dd76ad5a9c573f6fb83268f9df886b1bc8e530e135dea94219f2a62d788abSorry to be the bearer of bad news, but your transaction can no longer be broadcast and/or confirmed as the inputs no longer exist. None of the unconfirmed parent transactions are valid any more either... they're all "gone". The only way to recover your payment is if the person who was sending you the coins, resends the payment using a different transaction. |
|
|
|
That transaction does not exist on ANY block explorer that I looked for it on... You either got the TXID wrong, or your transaction has been dropped by the network and no longer exists in the mempool |
|
|
|
There is really no difference between a "sweep" and a "send"... both create transactions that transfer coins from one place to another. The "sweep" functionality is just a convenience function that enables you to send directly from a private key without first importing it into your keystore... Basically it just does this: - Locates ALL UTXO's for address associated with given private key - Creates a transaction that sends total value of all found UTXO's to new address specified - Signs transaction with given private key - Broadcasts the transaction You can do the same thing by: - Importing your private key into "Offline" Electrum - Importing your address into "Online" Electrum (This finds all the UTXO's) - Create transaction on "Online" Electrum that transfers ALL the UTXOs to the new address - Save this "unsigned" transaction - Transfer "unsigned" transaction to "Offline" Electrum - Sign the transaction with private key in "Offline" Electrum - Transfer "signed" transaction back to "Online" Electrum - Broadcast "signed" transaction Both methods effectively do the same thing... just one is slightly more time intensive  |
|
|
|
|
You appear to have 2 wallets:
wallet_try1 [2of2] - This is a "2-of-2" MultiSig wallet... it requires 2 private keys to sign every transaction. When you created this wallet, it would have asked you to enter the "xpriv", "xpub" or "seed" of the co-signer. There is NO way to create a MultiSig wallet in Electrum WITHOUT entering the co-signer details.
default_wallet [2fa] - This is effectively a "2-of-3" MultiSig wallet, using the TrustedCoin API. It requires at least 2 of 3 private keys to sign every transaction. Your wallet contains 1, TrustedCoin have 1 and your 2FA seed is able to regenerate the third if required.
When you created your "wallet_try1 [2of2]", it will have asked you to create a seed, use an existing seed or use "public or private keys"... do you remember which option you chose? And do you remember what co-signer xpub or xpriv you used?
|
|
|
|
I see that you can't enter a mycelium 12 word seed in electrum or an electrum 12 word seed in mycelium.
Presumably they both use bip39. Why are they different?
Electrum uses a non-standard seed phrase checksum calculation method that is NOT BIP39 compatible... even though they use the same word list. Ref: http://docs.electrum.org/en/latest/seedphrase.html#motivationFor these reasons, Electrum does not generate BIP39 seeds. Starting with version 2.0, Electrum uses the following Seed Version System, which addresses these issues.
At present, on desktop Electrum you can import Mycelium (and other) BIP39 seed phrases (simply click the "Options" button on Seed entry and select "BIP39 Seed", leave Derivation Path as default m/44'/0'/0' for Mycelium, other wallets may differ)... and because Electrum has a custom setup, Electrum phrases are NOT able to be used in Mycelium wallet. Also, the Android version of Electrum does not currently support importing BIP39 phrases. |
|
|
|
I just pushed it using ViaBTC and AntPool... Hopefully it'll get included in one of the next few blocks... AntPool and ViaBTC currently have about 25% of the combined hashrate... so theoretically, one of them should find a block in the next hour or so! EDIT: Hahaha... AntPool just found 4 in a row!  Included In Blocks 489577 ( 2017-10-13 00:20:01 + 498 minutes )
Relayed By AntPool
You're welcome! |
|
|
|
It's completely up to you, but keep in mind that you would be cut out of your funds for a week or so if you lose your wallet
Only if you want to restore to another hardware wallet... if you're desperate for access to your funds, you can simply restore your seed into any BIP39 compatible wallet like Electrum and get access to your coins... Granted, you lose a lot of the security doing this, and would need to move all the coins ASAP to a new hardware wallet... but the point is that you aren't necessarily without funds while waiting for a new device to arrive. |
|
|
|
I get the tough love HCP, and I could accept that if that's actually what happened. But that is not what happened. I first installed the Android and copied the seed key. When I later added the pc version all I tried to do was pair the wallets, not open a new one. So I used the seed key I had. There was only one key and I have it. What happened next is anyone's guess. Jaxx updated the app the day after I installed it. They also had a problem with their Chrome extension. Who knows? One thing is for sure since I can't "prove anything." The money I'm talking about will be sitting in limbo forever...and I'll bet you 1 BTC on that!  Firstly, sorry if I came across as a bit harsh... Cryptocurrency can be quite unforgiving when you get it wrong  Honestly, I can't argue with your version of events, I wasn't there and I don't have access to your records/notes and wallets... so all I can tell you is based on what you're currently able to see. It would appear that what Danny has theorised is most likely the case... that you somehow created TWO wallets on your Android (Jaxx issue?)... only wrote down the seed for the first one... but started using the second one... so the timeline would be something like this: - Created AndroidWalletA, wrote down SeedA - Created AndroidWalletB - Possible Jaxx error? - Sent 1.0 BTC to addresses in AndroidWalletB - Installed Jaxx on PC, entered SeedA... saw 0 BTC - Sent money to addresses showing on PC (AndroidWalletA)... saw this amount show up on PC - Reinstalled the wallet on Android using SeedA... 1.0 BTC disappears along with AndroidWalletB, small amount from AndroidWalletA shows up That is a pretty shit situation to be honest... I've seen others get into trouble with Electrum on PC as well, when they forget they've used the program before... and start it up and there is an old wallet that the app uses by default and they start receiving funds to the addresses in it, not knowing what the wallet password was (as it only asks for password when you go to send etc)... and they end up with BTC stuck in a wallet that they can't send from As for bets... I would also bet 1.0 BTC that Jaxx will deny all liability if they even respond to any of your support requests... |
|
|
|
|
Show Posts
