But people CAN choose.
They CAN connect to whoever they want. That's the point.

Hubs are being built if people want to build them. And also.. note that Hubs are still decentralized. There is a difference between decentralized and distributed.
While the LN probably won't be completely distributed, it WILL be and currently IS decentralized.




SegWit introduced the block weight.
With 100% segwit transactions, there is room for 4x more transactions inside a block than pre-segwit.

Currently, blocks are about 2,4 MB big (incl. witness data).

I doubt so.
They'll probably take the free money and won't release any private keys to you.

But it still would be worth a try. They might be refunding it (for a fee).




Bitcoins are ALWAYS 'on the blockchain'. They are NEVER 'inside' of a wallet or 'in' an address.
The blockchain is the public ledger. The BTC's are assigned to an address.

And in order to use these UTXO's you'll need to have the corresponding private key to create a (valid) signed transaction.

Anyone with access to a private key, has access to all UTXO's associated to the addresses derived by this private key.




Yes.
If they want to help you, they are simply going to send the funds back. But i woulnd't expect them to do that.

Did you already find out why the first transaction got forwarded to coinbase ? This still seems to be somehow inconsistent because it doesn't make sense.

Very well imaginable :/
Such sensitive information should only be stored offline without the possibility to be accessed by stranger.

At least an encryption with a password which is long enough (stored offline) should be done before keeping sensitive data on your PC.




It is unlikely that the RPC vulnerability led to your coins getting lost.

This would have required you to have:
1) Your wallet open
2) Your wallet NOT password protected (which it is according to your posts)
3) Visiting a malicious site which tries to exploit the vulnerability

.. at the SAME time. It is pretty 'safe' to assume that this was not the way your data got leaked.




Note that simply disconnecting the hard drive doesn't change anything.
If your system was/is infected, simply changing hard drives won't change much.

You need to make sure to completely fresh install a new OS. In most cases this is enough.
There are still some cases (e.g. root kits) where installing a new OS won't help, but those are rare.

You'll have to click on 'Coin Control' to get into the menu to select the UTXO when creating a transaction.

It works flawlessly for me.
Did you try to refresh the website ? And you also need to have javascript enabled in your browser.

Am i correctly understanding you that you want to import the ADDRESS (to create a watch-only wallet) ?
Or was your intention to access your forked coins ? In this case you'd need to import the private keys (or seed) instead of the addresses.

But note that after entering your seed/private keys into a non-trusted software, regard them as compromised and do NOT further use them.
First move all other funds (BTC, BCH, ..) from these private keys, then access them using a 3rd party wallet.

Yes, the ATM provider in this case has the private key to this address.

You might try to contact them, but if this address isn't actively a deposit address for your account, they probably won't do much for you.

It would be still worth contacting them.




This seems really weird. There is no practical reason for the atm provider to forward your payment to your coinbase account..

I am using KDE Connect to connect my mobile and my linux. Both devices have to be on the same network.
With KDE Connect running your mobile and PC shares the same clipping board.

This means i can simply copy the address inside mycelium with my mobile and paste it inside linux.

That's by far not the best approach. But since im using it anyway to control my computer via my mobile at home, that's the easiest way (for me).

There is only one official electrum. It can be downloaded from https://electrum.org/#home and is a BTC (only) wallet.

Anything else has been forked and modified. Without reviewing the code, you are trusting some random stranger to provide you a wallet..




Running it in compatibility mode should work fine.. But why don't you simply get the 64 bit version ?

You have to open a channel, yes. But you don't have to open the channel directly with B. You can open a channel with anyone (X) as long as there is a route from X to B.




That would be fine too. This wouldn't cause a problem at all.
Those hubs don't have any influence or 'power'. If you don't want to connect to them (e.g. because big hubs or fees), don't do it.

People can choose who they connect to.




It's not really a solution. They postpone the problem.
Increasing a variable (blocksize) can never be a scaling solution.

A lot of new problems appear with a bigger blocksize which shouldn't be ignored.

This transaction was broadcasted less than 2 minutes ago.
And the mempool is quite empty at the moment.

There hasn't been any block mined in the meantime.. you'll have to wait a bit.

Your fee is not too low. It is appropriate considering the amount of transactions in the mempool currently.
Your transaction should confirm within the next (few) block(s).

Did it work after waiting a few minutes ?

If not, it might be due to some faulty firewall configuration. Did you only swap your PC itself (hardware) or also some network related configurations ?
Which OS are you using ?

If you can verify the funds are sitting on that address (via block explorer), you are fine. It's just a network-/display- issue.

Did you have single private keys stored in the text file ? Or was it your (12-/18-/24- word) mnemonic seed ?

And what funds have been accessed ? Those whose private keys were stored in that file ? Or also from other addresses ? 

IMO it is very likely that your PC somehow got compromised. Either by downloading/executing malware or through a vulnerability.

If you had electrum running all the time (e.g. in autostart) the possibility would exist that some malicious website you have entered could exploit a vulnerability in electrum to steal your funds.
But since your wallet file was password protected, this is not the case here.


For the future.. never have a digital backup stored on the same machine. You shouldn't even have a digital backup at all stored anywhere except completely offline.
And note that a digital backup NEVER replaces a physical (analogous) backup.

Mind copy/pasting the output (the error) into [ code] and [ /code] tags here, so that everyone actually can look into it ?

This will not only help others to help you, but also other people with the same problem to find the thread (and hopefully also the solution).

And there is no possibility that you have confused the deposit address from coinbase with a 'wallet' address from coinbase ?
Did you ever use an 'online wallet' (from coinbase) ?

Can you tell us which version of the coinbase app you are using on your mobile ?

How did you lose your private keys ?
Step 4) is to crack the password of a wallet file. So, if you have a electrum wallet file and don't remember the password, yes.
But if you lost your seed and don't have a (password protected) file anymore or have used electrum to access a hardware wallet, step 4 is not for you.

There might be other options to gain access to your private keys.
How did you store them (which wallet) ? And did you have any kind of backup ?

OP has mentioned that he got that address from his coinbase mobile app (on his iphone).

I am still waiting for the answer whether he is using the official ios app from coinbase.

Either it is a malicious application or OP did use a intermediary wallet. That's all i can think of.

Is it this app: https://itunes.apple.com/us/app/coinbase-bitcoin-wallet/id886427730 ?

Please verify whether you are using the official application.




Unfortunately not. The transaction from 12ngg.. to 36ii5.. made it successfully to coinbase.

This seems to be very odd..
Besides a malicious application which displays attackers addresses (and forwards them if the amount is too low), i can't think of what happened here.

This does make sense.

From the coinbase FAQ:

So, the 12ngg.. is somehow a different address (not from coinbase).
Did you use any software wallet on your PC / mobile ?




Quoted for easy-access-link: https://i.imgur.com/QRSxfrW.jpg

Did you directly copy the deposit address from coinbase and pasted it into the withdrawal field on kraken ?

Because somehow there is an intermediary address (12ngg..) between your withdrawal of kraken and the deposit to coinbase (36ii5..).

---

Edit:

Thats weird. But i believe coinbase switched to p2sh segwit addresses (starting with 3..) ? Or am i wrong here?
Did you use the official app (https://play.google.com/store/apps/details?id=com.coinbase.android) to get the deposit address??

Alright.. so looking at the transaction and the first email this is what i can conclude:


You have deposited 0.09471172 BTC from 12ngg3CB9VDvkbFDx7JKY92i9kYgDmiEaj to 36ii5gNkZw2vAZ8TVk9dYXtVVbJxk68hiE.

Coinbase has confirmed that 36ii5gNkZw2vAZ8TVk9dYXtVVbJxk68hiE is their address (from the 1st mail).

12ngg3CB9VDvkbFDx7JKY92i9kYgDmiEaj obviously is your address. Your wallet does hold the private key for this address (what wallet are you using ??)

Afterwards you have sent 0.62574 BTC to 12ngg3CB9VDvkbFDx7JKY92i9kYgDmiEaj (which you have control of), confusing it with the address from coinbase (36ii5gNkZw2vAZ8TVk9dYXtVVbJxk68hiE).


Your coins (0.62574 BTC) are still under your control. You can access them with the same wallet (and wallet file / seed / etc..) as when depositing to coinbase the first time.
They should be visible in your wallet.