Then you are wrong.

Quite a lot of exchanges combine all deposits on a cold wallet which can be linked to a specific exchange because 1) they publicly disclose their cold wallet address(es) or 2) it is quite trivial to find out to which exchange a given address belongs.
Please look at the posts on the previous page.

Since i don't know how your backend works, a general how-to would be:

• Have the xpriv backed up offline
• Use the xpub on an online server go generate addresses on-the-fly
• Assign addresses generated from the xpub to customers and save that in the database
• Use walletnotify and blocknotify with core to check for new blocks/transactions and update database entries based on that (e.g. customer has paid, transaction has X confirmations, ...)

You don't need to import private keys into core.
Either use cores HD wallet or only use core to check for transactions.

Core is also a HD wallet.
Why would you create an address outside of core, just to import it into core afterwards?

You are right, that's definitely not efficient.
What wallet are you using to generate the addresses? Electrum? If so, then why do you import them into core?

The reason for that is, that the withdrawal fee does not only cover a single (withdraw) transaction, but also the consolidating transactions and the top up transactions (hot wallet <-> cold wallet).
While the fees often sound pretty high, it isn't that overblown since they have to cover multiple transactions. And obviously they also want to earn money with that.

Yes, that's the expected output.
The warning appears because you do not trust the key yourself yet. The important part is the bold line.

When using the correct key, that's all you need to look for.

Not really.
Most (if not all) exchanges do consolidate the deposits on a hot- or cold wallet.
And most often those addresses are known (or at least can be found out by depositing multiple times to an exchange).

Tracing and/or linking a depositing transaction to an exchange isn't that hard in most cases.

Also, das Problem scheint das zu sein, was ich am Anfang vermutet habe.
Die Coins liegen auf deinem "Trading Wallet" und sind somit nicht von dem 12 Wörtern erfasst.

Die Coins gehörten dir nicht und haben dir nie gehört. Blockchain.com ist in voller Kontrolle der Coins und du hast quasi einen "Account" und das "Recht" diese (irgendwann mal) zu versenden.

Desswegen bringen dir die 12 Wörter bis jetzt auch nichts.
Um da 100%ig sicher zu sein, müssen wir natürlich wissen was du für Adressen hast. Also womit die anfangen wenn du Coins empfangen möchtest.




Bitcoin ist eine Währung.
Wenn du 1 BTC hast, dann hast du 1 BTC. Ob der Euro-Gegenwert jetzt 10.000 oder 3.50€ ist, spielt hierbei keine Rolle.

I sent you a PM.

Bump.

No, you are right in terms of that an on-chain transaction is required for both opening and closing a channel.
If you don't feel confident risking a few satoshis to play around with the LN, feel free to not do so until it is out of alpha.

A little bit more information would be useful.

How do you plan on keeping the funds? Multisig between the two parties and the escrow?
And what exactly are you looking for? someone who "can bring something new to the team" is pretty vacuous.

It may increase your perceived level of security, but doesn't help you at all.
Using a VPN makes it not more secure. Not even slightly.

With a VPN, you are simply shifting the trust from your ISP to your VPN provider. That's all. Security-wise there is no difference.




You can try any VPN you want. You are only giving away your privacy. Your wallet is not more or less secure based on which VPN provider (or if any at all) you use.



Definitely not by using a VPN since they don't help you.
Its mostly some simple things like using different passwords, not downloading tons of free software just because it's free, not downloading cracked software, using specific chosen browser addons (and only these few security-related), using 2FA (and actually on a second device!), etc..

You will be fine following these few relatively simple things.

It's quite easy. Don't do anything until you have checked your seed / mnemonic code.

Once you verified that your mnemonic code is correct, proceed further. Until then, simply don't try to repair/reset your nano.

I am offering 5$ in BTC to the first person who can verify my WeChat account (Security verification: Scanning QR code).


The requirements for international user are:

• You signed up over 1 month ago
• You haven't completed "Help Friend Register" in the past month
• You haven't been blocked in the past month

The requirements for chinese mainland user are:

• You signed up over 6 months ago
• You haven't completed "Help Friend Register" in the past month
• You haven't been blocked in the past month
• You have activated WeChat Pay

PM me if you are up for that.



Edit: Done.

Komisch.
Da du morgen zu hause bist, würde ich es dann einfach mal an einem Rechner probieren.



Du musst auf jedenfall auf deinem Ledger einen neuen Seed erstellen. Also bloß nicht den von blockchain.com importieren!
Das heißt, du musst daraufhin eine Transaktion von blockchain.com auf eine Adresse deines Ledgers durchführen.

Das Problem muss also so oder so irgendwie gelöst werden.

Ich vermute ja mal, dass sich die Coins entweder in deinem "Trading Wallet" befinden (worauf du mit deinem Mnemonic code (also den 12 Wörtern) keinen Zugriff hast) oder du hast bei Electrum einfach den falschen Adresstyp gewählt.

No one has access to it except you. At least if you believe what blockchain.com is telling you. And if you are sure what code you are running.
If you aren't sure what code exactly is being run inside your browser, you shouldn't assume that.

Additionally, the encrypted wallet file is stored on their server. So you better choose a strong password. Or (which would be way better), you stop using web wallets and start using proper wallets (mobile-, desktop- or hardware wallets).




You shouldn't disclose the xpub because of privacy reasons and security implications in some specific cases.
But you definitely can without automatically having security issues.




The xpriv is the master private key. It is used to derive private keys.
You do not want to share private keys at all. That's the reason they are called private. They allow you to spend the coins associated to your public keys (and therefore to your addresses).

To import a watch-only wallet (without the ability to spend coins), you need to import public keys (for specific addresses) or the xpub (master public key) for all addresses of your wallet.




Coins are "stored" on the blockchain, not your wallet.
They are associated to public keys. And the corresponding private key can access/send them.

So, anyone who has access to the private key, has access to the funds.

If you are going that step, you might as well install some monitoring software to check what files exactly are touched by the malware.



Some monitoring software (as mentioned) would be enough to check whether files are getting touched.
But the filesize does not need to be changed. You can easily embed malware into an image without changing the size (e.g. by deleting less relevant data). You'd need to compare the checksum (hashes) of the files.

Make sure to only change the "Bitcoin Home Dir" setting:


That's where armory will look for the blockchain files.
You don't need to change the "Armory Database Dir".

Hello,
i am looking for someone who can help me to create a wechat account (verification via QR code). I am offering you 5$ in BTC for that short task.

If you can help me, feel free to PM me. Thanks.


Edit: Done.