This would be a way to implement an air-gapped cold wallet setup. That's not the same as a hardware wallet.

A hardware wallet is meant to be secure when used with compromised device as it stores the keys securely. This can't be sad about a standard smartphone.

An air-gapped setup definitely isn't worse, but actually more secure, when used correctly, but it has other advantages and isn't a hardware wallet.

It is always better to not throw away the mnemonic code.

You might accidentally receive coins to an address derived from the old wallet seed.

The best would be to not use it anymore, while not throwing it away. Keep it in case you'll need it.

The transaction does not exist.
It either got dropped 2 years ago or you got scammed by buying a wallet file.



No, since the transaction does not exist you can't do anything.
You never were in possession of these funds. And a CPFP won't help you.

If you can't find the transaction ID on a block explorer and the receiving address of yours does not have any balance according to a blockchain explorer, then there is no balance.

It is very well possible that the transaction simply got dropped or that you are looking at a manipulated wallet file (did you buy the file?).
Just check the address on a block explorer. If if shows no balance, there is no balance.

Wenn du dir große Sorgen machst, dann leg einfach noch einen "Zwischenstop" ein.
Transferiere also deine ChipMixer Münzen zuerst auf deine Adresse, und zahle die dann auf eine Börse ein.

Damit wird es schwer dir nachzuweisen, dass du derjenige warst, der einen Mixer verwendet hat.

If the files weren't deleted, yes.
If they were deleted, only a file recovery could yield some results. But this is rather unlikely to be successful (might be still worth a try tho).

Blockstack v 0.18 only works with python 2. It is incompatible with python 3.




Somehow the onedrivesdk pip package is broken.
As mentioned in the above posted github, use:

Mycelium is following BIP32, BIP44, BIP49 and BIP84.



Yes, you can definitely do that. At least as long as we are talking about legacy addresses (starting with 1..).
For any other address type, no fixed standard to sign messages exist.. You could sign messages using a segwit address with electrum, but that message then can only be verified using electrum.

However, the correct derivation paths are:

• m/44'/0'/0' for addresses starting with 1..
• m/49'/0'/0' for addresses starting with 3..
• m/84'/0'/0' for addresses starting with bc1..

Ctrl + C sends a SIGINT signal to the process. This is not a termination signal like SIGKILL or SIGSTOP.
What the software does after receiving a SIGINT completely depends on the software. It can be ignored, or used as a "shutdown command".

Pressing ctrl + c does not terminate the process. It tells the process to stop / terminate itself. So, yes. you are fine using ctrl + c as its just asking the software to stop.

If sending the transaction with the lowest possible fee, which is  1 sat/vB, would cost more in fees than it would transact, than you can't do anything since the amount is too small and not worth using/transacting.
Did you set the lowest possible fee?

Also, did you check how many inputs your transaction is using? There might be lots of small dust UTXO's which increase the transaction size and therefore doesn't make it worth to transact the other non-dust UTXO's ?
What is the size of your transaction, how many inputs are you using?

No, definitely not.

Android makes use of the unix permissions as a security measurement.
The SD card is "free for all". Any application can read/write to it. That would be the last place the wallet file should be stored (and it isn't).

It is stored where it belongs to. In the data directory of the mycelium application owned by the mycelium application user.


@OP:
Don't you have any form of backup? Your mnemonic code?
Did you "just" uninstall myeclium or did you actively delete all mycelium data / wipe your smart phone? Uninstalling the application doesn't necessarily mean the wallet files get deleted. Might be worth to try this out on a second mobile.
Rooting your mobile without wiping the storage would be your best bet. Then you'd be able to access the wallet file and all private key.

You can send from any address type to any other one.
Network-wise that's not a problem at all.

The only problem can occur when dealing with outdated software.
Their sanity checks will deem a native segwit address as "invalid" because their software hasn't been updated for multiple years.

Don't use heavily outdated services, and you are fine. You can send to and receive from any address.

Unfortunately, since RBF is disabled and there is only one output, only the recipient can use CPFP to get it confirmed faster.
The history of the address you have posted lets me believe that it belongs to binance. In this case CPFP is not an option.

Using an accelerator doesn't work either, since the only one proven to work only accepts transactions with a fee of at least 10 sat/vB.

It seems like you'll have to wait. For the future, you might want consider to switch to a wallet where you can enable RBF and have full control over the fees.

What you are actually doing when increasing the fee is to create a second transaction spending the same funds as the first one which has the replacable flag set.
By using a higher fee, miner will prioritize the second (replacing) transaction.

If you would choose a smaller fee, there is no incentive for the miner to include your second transaction instead of the first one.

Once a (valid) transaction is broadcasted, it can be confirmed. You can't really stop it. You can only try to stop it by giving a miner the incentive to not include it (e.g. by creating a RBF transaction to yourself with a higher fee).


So the answer is: No, that's not possible.

You could start with answering all the questions..

How do you expect to get help if you don't even answer our questions? You didn't even provide any useful information to begin with.
A screenshot doesn't necessary help much.. please begin answering the questions..

That's not how the mobile operating system works.

Android makes use of the unix permissions to seperate applications from each other.
Application A is running under user X and application B is running as user Y. They can't access each others files. The unix permissions don't allow that.

Therefore an AV on android also can't scan wallet files. At least not as long your phone isn't rooted and the software has gotten the permission to do so.

Trezor is completely open source, which is good.. because the source code is open a.k.a. publicly available.
However, there is a hardware vulnerability.. Use a long and secure password and you are fine tho. It is "just" a physical attack vector which allows to extract the seed.




No.
This applies to the trezor without any password protection. That's the physical attack vector i referenced.

Bin deinem guten Beispiel mal gefolgt 


Das ist.. richtig asozial.
Die Daten sind ja sowieso schon kostenfrei im Netz erhältlich.

Dann sogar noch versuchen Geld damit zu machen und gleichzeitig zu behaupten man "hilft" den betroffenen Nutzern sodass diese überprüfen können ob deren Daten enthalten ist.. Schlimm was es für geldgierige Gestalten gibt..

Pssst.. Don't tell them!

On the underground forum c00lh4x0rz.io there was a SEO thread posted by "SE0MaztER2005" who sold this method for a very cheap price.
He has years of experience in SEO. This method works 100%. With 100% money back guarantee.

Maybe this file.pdf.exe got leaked now and therefore more people know about this super secret and super efficient method.

/sarcasm

Schrecklich.. solch eine unprofessionelle Antwort zu senden.

Stimme dir völlig zu. Das dient vermutlich auch ausschließlich zum Verteilen der Daten.
Gibt ja hier im Forum auch genügend Nutzer, die wann immer es geht gegen Ledger schießen. Denen passt es natürlich, dass so viel Schaden wie möglich angestellt wird. Ob es im Endeffekt den einzelnen Nutzer triffst.. ist denen egal.

Eine einfache Suche via Mail reicht definitiv aus.. Dazu muss nicht der gesamte Leak weiterverbreitet werden.

Dieser Satz zeigt ja auch, dass sie entweder 1) mit Absicht so handeln oder 2) absolut bescheuert sind: