I believe there are multiple reasons for that.

1) It is annoying as hell
2) Visitors often get compromised by malicious advertisements from such AD networks.
3) The money is not THAT needed (btctalk's donation address currently holds ~188 BTC) That's pretty much enough to cover the next 'few' years of operating costs
4) It is annoying as hell

If you connect to a random (i.e. not your own) electrum server, yes.

The electrum server you are connecting to has access to the following information:

• All addresses which you query the balance for (every used + every address in your 'receiving address' tab)
• All transactions you send
• All transactions you receive
• Your overall amount of BTC
• The time of the day when you send / receive a transaction
• Your IP

Note that every wallet (which is not a full node client) can gather these information.
The only way to circumvent this is to either (1) run your own electrum server or (2) use a different (full node) wallet, e.g. bitcoin core.




It is definitely not worse than other (desktop- / lightweight-) wallets.
It even can be regarded as better because you can choose to which server you want to connect. You don't have that option with the majority of other lightweight wallets.

This is a very generic answer.. and i feel like this isn't completely true.

If OP has absolutely no clue what the password could be and the charset is relatively big, i don't think a password with 9 chars can be cracked in a short amount of time.

A 9 char password with (1) lowercase, (2) uppercase, (3) numbers and (4) special characters has a char set of 95.
This means there are 95^9 = 630.249.409.724.609.375 combinations.

I don't think this can be brute forced in a reasonable amount of time..


1) 26 chars
2) 26 chars
3) 10 chars
4) 33 chars

Since you still have full access to the device, you can enable USB-debugging in the settings, then connect to your mobile with your PC (via adb shell) and backup any necessary data (in this case: all data from mycelium).

Afterwards you should even be able to extract the mycelium pin from the backup on your computer.
The pin can be found in:

You also should be able to extact the master key itself, which is stored in a sqlite database.


That's a bit more complex than simply rooting the phone and reading it out, but you can try this first without rooting your phone.
And you will have a backup of all necessary files in case you do something wrong when rooting your mobile.



P.s. You can find the USB-debugging setting under the 'developer options' (which will get visible if you click on 'system- / version info' (or similar) 7 times in a row).

For that reason there has been a standard created which has been implemented  by most wallets already.
BIP39 (https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki) covers the encoding of the seed into the mnemonic code.

It is highly likely that you will always be able to automatically recover your coins from a BIP39 mnemonic code. And if not, the standard can be read by anyone to recover the seed by hand.





Unplugging the hard drive doesn't do anything for the security.

Since the hard drive isn't mounted at boot, there is no direct risk.
Even if you mount the hard drive, if you are using a windows PC and boot a live linux, there is almost no harm which can be done.

Upon boot, a clean OS is being loaded into the CPU / RAM. The harddrive is just some storage.

To me it seems, that your so called 'alternative market' scammed you.

The transaction went trough successfully and the recipient already has used this coins in another transaction.

You might try to contact this 'alternative market' and see whether it was a mistake. But i think it wasn't.

Is your 'alternative market' some shady market accessible via TOR ? Most of them are scam.

There is a difference between sat/B and sat/vB (virtual Byte). And that's probably what you are looking at here.
Since the SegWit soft fork, the maximum size of a block is no longer measured in bytes, but in weight units.

4WU = 1 vByte

The witness data of a (segwit) transaction weights 1 WU per Byte.
The non-witness data weights 4 WU per Byte.

That's absolutely not a problem at all. Just some conversion stuff.


Regarding your second address, this is a change address.
This is a crucial element of bitcoin, take a look at https://en.bitcoin.it/wiki/Change.

In BTC, there are no 'coins'. Just UTXO (unspent transaction outputs). Whenever you create a transaction, you are using at least 1 Input.
And if you are not completely 'using' it, you create 2 outputs, with one of them is an address of yours (a change address).




Hell no!

Ledger has 0 control over your funds or anything else.
You always have full control.

You have multiple option to achieve that.
The most commons are:

1)
You can use bitcoin core to hold your private keys, and use walletnotify and/or blocknotify to trigger external scripts whenever a payment is received.

2)
You can use electrum to receive payments via creating invoices and being notified semi-automatically.
For more information, take a look at https://docs.electrum.org/en/latest/merchant.html.

Read my answer:



If you want a more detailed (technical) explanation, read the BIPs on Github:
1) Mnemonic code: https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki
2) Key derivation: https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki

Indeed.

That's somewhat weird. I usually just received them in my standard inbox.
Seems like some shitty algorithm started to move them into the junk folder automatically.

And in addition to that, the junk folder did not synchronize itself (accessing this mail account via mobile online).


All sorted out, thank you!

I seem to not get any email notifications when receiving a PM.

Inside of the PM settings "Notify by email every time you receive a personal message" is set to Always.

Am i the only one experiencing this misbehavior ?


P.s. Disabling and re-enabling it didn't fix the issue.

Habe einen negatives Flag erstellt: https://bitcointalk.org/index.php?action=trust;u=298715

Wenn mehr Leute dafür sind als dagegen, wird für Newbies (< 7 Tage Login Zeit) und für ausgeloggte Nutzer ein Warnung bei jedem Thread erscheinen, den der besagte Nutzer erstellt hat.


Diese Nutzer sehen jetzt folgendes bei einem vom ihm erstellten Thread:




Wenn ihr der Meinung seid, dass das Flag gerechtfertigt ist, dann zögert nicht dafür zu stimmen um zu verhindern, dass irgendwelche Alts von ihm dagegen stimmen.

You would need to inspect the hardware.

Updating the firmware would remove a malicious firmware, but would not help if it has been tampered with on a hardware basis.

You either need to know which components exactly are required, open the case and check everything.. or you buy it directly from Trezor / their official resellers.

If you don't necessarily need to share your master public key with a random server (a.k.a. to be able to view your balance everywhere without your own computer),
you might as well use a desktop wallet (e.g. electrum) to monitor your balance.

You can easily use your hardware wallet with electrum to spend your funds, and without your HW being connected, you have the ability to monitor your balances (without sharing your master public key with anyone).

If OP can root his mobile without erasing all data, it will help.

The pin is stored in plaintext in a text file on the mobile.
He could simply read it out, then start mycelium and access his wallet by entering the pin.


@OP: Does the possibility exist that you are using the wrong mnemonic code? Or that you have miss-typed a word?
You might also need to create multiple "accounts" within mycelium if you have done so in your old wallet.

It is not a vulnerability. This is the protocol design.
It aims to make it extremely hard to achieve and being extremely unprofitable.

Financial Incentives excluded.




It is not encrypted, it is signed.
And it is not put into a place called "unconfirmed transactions", it is an unconfirmed transaction in the mempool of the nodes until it is being included into a block.




If the transaction is valid, it is being included. Otherwise not.
There is no 50% mark or anything similar.

Every node which thinks this transaction is valid, will add the block including it to the chain.
The other ones don't.

If - for whatever reason - 50% of the network thinks a block is invalid, while the other half thinks its valid, a fork happens.
But since there is a consensus on which transactions are valid / invalid, this shouldn't happen.




Bitcoin already had a 51% attack.
It was in the very beginning when nearly no one was mining.

Nowadays, i agree. It is effectively not possible anymore.

You didn't download the .AppImage file.

You literally just need to do:
1) Download the AppImage
1.1) Optionally (but preferable) check the signature
2) Make it executable (chmod +x)
3) Run it

Even when extacting the AppImage, you will only get a sqashfs-root directory.
Inside of this directory there is an executable called AppRun. Running this also brings up electrum. So it is obvious that you indeed didn't download the AppImage.

You seem to be over complicating this too much.


You might really want to just use the script provided by Abdussamad.
It downloads the electrum AppImage, checks the signature, moves it into a subfolder of your home directory and makes it executable.

You don't need to 'install' the AppImage.

You just need to make it executable (chmod +x filename).
Then simply run it, and it works.

If you want to be able to open it via the console from everywhere, you can create a symlink to any directory in your home path (e.g. /usr/bin or /usr/local/bin).


Regarding the error message, you need to install python3-dev from your distributions repository.
For me at least it seems to be the reason for the error appearing (Python.H missing).

You are still wrong.

I don't care what a random site says.

You were talking about the MAXIMUM amount of transactions a block can hold.

Now, since you obvoiusly can't calculate it yourself.. let me help you:

The maximum amount is reached if the transactions are the smallest (Is very obvious to everybody, just not for you).
A smallest transaction has the properties:

• being SegWit
• having 1 input and 1 output

A SegWit transaction with 1 input and 1 output has a size of 85 bytes (non-witness part).
With 1.000.000 Bytes per block, we have 1.000.000 / 85  transactions at a maximum. That's 12.195.


Wasn't that hard, was it ?


In the future you might want to stop posting nonsense / superficial knowledge which you got from somewhere without even thinking about it.


You can, of course, now start arguing like "bla bla a block never has only 1 input 1 output segwit transactions bla bla".. But it doesn't matter..
YOU started talking about the maximum a block can hold. And your statement was wrong.

And instead of accepting it and calculating it yourself, you started justifying yourself. Which obviously just backfired, because you are simply wrong.

And this is not the only statement of you which is plain wrong. Most of the stuff you are mentioning is nonsense.
I don't know whether it is because you misunderstood things, or because you are not capable of understanding it.. and it doesn't matter. Wrong is wrong.

---

Just saw this:

How do you even dare to talk about LN if you don't understand the very basics of cryptography / cryptocurrencies / BTC 

Now, do yourself a favor and first learn the basics. Then educate yourself about the advanced stuff.
THEN start discussing LN and its pros/cons.

Legacy Adressen starten mit 1, aber nicht jede SegWit Adresse startet mit 3. Und genauso ist nicht jede Adresse welche mit 3 beginnt auch eine Segwit Adresse.

Adressen, die mit 3 beginnen können entweder nested Segwit (P2WSH eingebettet in P2SH) oder eine einfache multisig Adresse sein.
Erfahren tut man das erst, wenn Coins von dieser Adresse gesendet werden.

Native Segwit (das "originale" Segwit) hat das bech32 Adressformat (Adressen beginnen mit bc1..).

---

@OP
Am public key erkennst du gar nicht um welchen Adresstyp es sich handelt.

Der public key ist eine große (256 bit) Zahl, welche mathematisch vom private key (ebenfalls 256 bit Zahl) abhängt.

Erst an der Adresse an sich, erkennt man um welchen Adresstyp (oder um präziser zu sein: welches Transaktionsformat) es sich handelt.


1.. -> Legacy, standard alte BTC adressen
3.. -> Entweder Multisig (gibt es schon fast seit Anbeginn von BTC) oder nested SegWit
bc1.. -> "echtes" SegWit, damit schöpfst du die Vorteile von SegWit vollständig aus, aber manche Börsen / Seiten haben das noch nicht implementiert und kennen das Format noch nicht.