Ganz einfach: Bezahle gutes Geld.




Diese Nummer hat vielleicht vor 4 Jahren funktioniert.
Mittlerweile sind die Leute nicht so dumm, dass sie für Shitcoins und Shittokens umsonst arbeiten.

Nimm es mir bitte nicht übel.. aber mehr als 99% aller Coins und Tokens werden wertlos.
Und du kannst dir sicher sein, dass fast jeder eine "super geniale" und "revolutionäre" Idee hatte, die es "davor nicht gab".


Also kurz und knapp: Wenn du ein gutes Team und gute Leute möchtest: Gutes Geld bezahlen.
Bezahl entweder in guten Kryptowährungen (BTC, ETH) oder in FIAT. Sonst wird das nichts.

Wenn du das Startkapital nicht hast, dann kauft dir auch keiner ab, dass du "eInE BaNk" gründen wirst.

With addresses, you don't need to add any prefix. The address itself already contains the script type (P2SH start with 3.., P2PKH start with 1.., etc..).

If you however only have the private keys, then i'd say you should first create an offline wallet (or two, as described above).
Then you can easily check the funds on an online computer and don't need to do any additional work to actually spend from that wallet.

There is effectively no way which does exactly what you are looking for.

But, the good news is that it most likely is not necessary at all.
The majority of things you can think of implementing, someone else has already though of. And therefore the probability that a good solution exists, is relatively high.

What exactly are you looking to do? What are you trying to implement, what kind of mechanism?
I can't think of use cases for what you have described, which can't effectively done with other (available) mechanisms.

You imported the private keys 1 by 1 into electrum, right?
You pasted them one per line in the box which appears after choosing "import private keys" (or similar), didn't you?

Now, import all the private keys which belong to a P2SH address from armory into electrum.
If you don't know which of them should be P2SH and which P2PKH, just create 2 wallet files in electrum.

When creating the first wallet file, add "p2pkh:" in front of every private key.
When creating the second one, add "p2sh:" before every private key.

It should roughly look like this:

Source: btcleak.com

You will end up with 2 wallets, one P2PKH and one P2SH.
This should be the easiest approach to generate all the required addresses.

What output do you get?

Starting it via the command line should result in an log being forwarded to stdout.
Are there any error messages appearing? And Warning messages? Anything which could give a clue why it works with the --no-sandbox parameter?

Also, did you try it running as root (without the --no-sandbox) parameter? Does it work this way?

This seems somewhat odd to me.

I'd assume that you either 1) didn't understand the concept of bitcoin and wallets or 2) someone is trying to scam you.

Further, this completely seems to be a XY problem.
You'd be better off explaining what exactly you want to achieve. Do not ask about something which you believe helps you to achieve it. Start off from the very beginning.

You should stick to only 1 thread. There is no reason to create a second one, even if it it seems to be a different issue now. The main problem is still that you are not able to access your coins.

Now, to fix your issue: Import your private keys and choose the corresponding prefix.

For example, if you want to generate P2SH addresses, import your private key as:

For p2pkh, do:

It doesn't make much sense, no.

Maybe not everything has been shown or there was a bug and armory crashed or something like that?

If you restore your armory wallet with your root key, you will recover all of your private keys and therefore access to all of your coins.

Are you sure that you have checked all addresses and that 2/3 of your coins are missing? Did you maybe not include some addresses which contained funds? Like change addresses?

Yea.. you probably don't want to hear that.. but it's most likely your fault 

If you actually want some helping comments, try to rephrase your question such that people don't roll their eyes when they read your nonsense.
Further, using the search engines almost always guarantees helpful answers. You might want to try this first.

It's not just about "Don't use Coinify with Ledger", but about to not use coinify at all.
And even better would be to not use any "instant exchange" at all. All of them have ridicilous fees and a pretty high percentage of them systematically scam people for "AML reasons" and further require proof of identity etc.

If you don't want to get milked like a cow and don't want to send selfies with your ID to some shady services, don't use that nonsense. Regardless of whether it is coinify, changelly, changenow, changescam ..  or what the current "best instant exchange" is.

I'd assume he simply imported his mnemonic code / private keys.

Doesn't Eclair also search for the whole transaction history when importing a used mnemonic code?
That's at least the case for all wallets i have used/tried.

Hoffentlich ist das Gerät trotzdem durch eine PIN mit einer maximalen Anzahl an Versuchen gesichert?

Andernfalls würde ich das Gerät keinem empfehlen. Zumindest nicht wenn der Fingerabdrucksensor ein paar tausend € kostet.
Da ich mal davon ausgehe, dass das Gerät weniger als ein paar tausend kostet, kann sicher davon ausgegangen werden, dass der Fingerabdrucksensor absoluter Müll ist und mit einer nicht-vernachlässigbaren Wahrscheinlichkeit mithilfe eines Blueprints (quasi ein "Universal Fingerabdruck") umgangen werden kann.

Und auch sonst, lassen sich Fingerabdrücke mittlerweile relativ genau von einem Hochauflösenden Foto aus bestimmen. Günstige Sensoren kann man damit relativ einfach täuschen.
Eine PIN ist hier das Mittel der Wahl. 

It's not just android.
It basically is any operating system. Regardless of mobile (android, ios,..) or stationary (windows, linux, macos).

Malware exists for every operating system. It is just that malware for more common systems are more likely to be encountered.
In a targeted attack with malware, it doesn't really matter which OS you are using. You always need to be careful.

Da musst du dir keine Sorgen machen.

Vermutlich hat sie das nur gesagt, damit du hier auch schön Updates gibst 
Ob es am Ende geklappt hat oder nicht interessiert uns dann schon auch immer 

Wenn du (oder ihr) dem folg(s)t, was Lakai01 schön bebildert und ich textlich dargestellt habe, dann sollten die BTC in wenigen Minuten wieder zugänglich sein 

Bitcoin does not use any encryption at all.
And definitely no symmetric cipher (what you are referring to here).




There are no messages encrypted.
You seem to be confused with encryption and signatures.

Bitcoin is using the ECDSA. This is a Digital Signature Algorithm on Elliptic Curves.

There is no encryption envolved.




If the private key has been generated randomly, yes.
If it has been derived from something (e.g. from a seed), then it still can be recovered as long as the necessary information (e.g. seed and way of deriving) is available.

Did the refund go to the same address the funds came from? Or did you explicitly set that address as your refund address?

And where did you send the funds from?
If you have sent them from an exchange, it is to be expected that they won't be credited to your account. Your deposit address of an exchange is not automatically the address where your withdrawals come from.

It depends.. what exactly are you talking about with the term "passphrase"?

If it indeed is a alphanumerical passphrase (and not a private key, mnemonic code, etc..), then your chances are literally 0 if you don't find the corresponding file and or data which it encrypts.

How many characters does your "passphrase" have?

Wozu überhaupt ein Konto bei der Fidor?

Welche deutschen Banken sind denn anti-crypto? Hatte bisher nie Probleme mit Ein- und Auszahlungen zu/von Kraken.

As long as you have your mnemonic code (the 12 words), you are fine.

Choose a wallet (e.g. electrum) and restore your wallet there using your mnemonic code:
1) Download electrum from electrum.org
1.1) If we are talking about more money you are ready to completely lose: Verify the signature. There are lots of tutorials available on this forum and on the WWW
2) Create a new wallet using the "i already have a seed" option
3) Enter your mnemonic code (the 12 words), click on options and check "BIP 39"

Afterwards, everything should be self-explanatory. Wait a minute after creating your wallet, and you should see your funds appear.

Note that using multisig itself does not prevent any loss from natural disaster and loss of information in general.

A 3-out-of-3 scheme might be perfectly secure against thieves trying to steal 1 or 2 pieces.
However, losing one piece will inevitably lead to a loss of funds.

When choosing a multisig scheme, the concrete amount of co-signers is crucial.
Also, it is worth to mention that the transaction fees will rise.


A IMO better alternative is to use a secret sharing scheme.
You can achieve the same "backup strategy" as with a multisig wallet where the single keys are spread geographically, without the increased fees and added complexity.
A proper secret sharing scheme with a N-out-of-M scheme does not leak any information about the secret if N-1 pieces are leaked, making it perfect to securely backup private keys or mnemonic codes in different geographic locations.