@sumangs That's an exchange address and can't be staked since you will not be able to sign a message nor spend the actual input(s) in case you needed it for account recovery/verification.

Reference: Wallet [00000dd86b]
I'm 100% positive that wallet dd86b is Coins.ph or Coins.pro Exchange's deposit address - from a trusted source  

Stake another address from a wallet that you have full control over the private keys (ex. Electrum).

The only possible reason is Electrum have connected to a malicious server despite the added parameters in the shortcut.
That message will show if the server tried "something else" other than broadcasting the transaction.

Try to edit Electrum's setting into "oneserver"=true.
You can find it in %appdata%/Electrum/config (open with notepad).
[%appdata% = Win+R->type %appdata%]

After the import, did it produce the same addresses in the "address tab" (View->Show Address)?

• If yes, it just needed to sync to be able to display the transaction history and balance.
• If no, select the proper deviation path using the three options available for BIP39 SEEDs. (or the instructions above)

Next if you've successfully restored the addresses but the history didn't showed up:

• Electrum needs to be v3.3.3 or above to be able to connect to a server.
• Check if you're connected to a server by looking at the lower-right circle icon (Green=Connected / Red=Not)
• Is this the first time you've installed/opened Electrum on that PC?
  If yes, you need to at least wait for a couple of minutes (depending on your internet speed) to download the "block_headers" file before it can display the full history.

You said "Bitlum to Electrum" so it must be 0 confirmation (unconfirmed) since Electrum will instantly recognize the tx as long as the connected server received the txid on its mempool.
And a gap of 2 hours to broadcast the tx is too long since this should be instant if you have full control of the (bitlum) wallet.

So, is it an exchange-like service which implements "transaction batching" to withdrawals;
Does the txid of those two transactions involves multiple outputs or just yours alone?

If it indeed works like that, I don't see any relevance on using LN for those purposes. But it could work as a "reloadable micro-wallet" for small transactions utilizing lightning channels.

New to porn? Tell you what:
The best porn videos out there are only available for members with subscription since most of them were produced by high-budget studios/producers.
Also, most free videos are either stolen contents by uploaders or "short previews" of a full video.

Short previews commonly consists of bundled 10-20 seconds scenes of the whole video, you will not enjoy it as "porn is all about the plot"  

He's talking about PornHub's accepted cryptocurrencies as a response to jak3's comparison to PornHub.

If you're too worried about that detection, do not.

First of all, "Python/Coinminer.B" is generally a malware that remotely mine using your resources, not a tool to get sensitive information.
Secondly, Electrum doesn't have that PUA, it just a "similar" signature that your AV have detected from the executable.
AKA, false positive.

If you want to see more detection inconsistencies, go to Virustotal and upload that file and you'll see various Antivirus heuristics (Mostly non-famous AVs) detection to the file and it differs from "Malicious", "TrojanHorse" and "CoinMiner".
Famous Antivirus however, resulted with negative results.

Well, if they keep on doing that "redirect after click" leading to 2X advertisement impressions, they should close that faucet.
It's annoying and unintentionally fraudulent for both clients and advertisers (two ad views/set per claim and especially, forced ad clicks).

Users doesn't have a choice but to find a way to bypass it.

Have you confirmed that it was connected to your server?
If not, click the connection icon (Green Circle) and you'll see the actual server where you've connected.
If it's not your IP or server name, there's a problem with the instructions that you've followed.

I have read the "The Box" from your nodl link and it seems like a pre-configured hardware that can run a full node and other related software.

Right, ever since these "Veil-signatured" guys (not all of them) came here, Mining (Altcoin) board become a total mess (There's something fishy going around).
It's as problematic as YoBit's recruited bounty hunters.

I got no problem with Signature Campaigns as I am wearing one too, but the spamming to boost the post count is a different scenario.
I have asked a mod to lock this thread.

Yes, but realistically, that's what happening.
The ones in the losing sides are either the newbies or those who are "cashing-in or cashing-out" regardless of the price, mostly deposited from external sources like mining and services.
I've seen many specially in our local exchange when people usually sell their cryptos (at loss) even if there will be an expected rise or the price is currently at the bottom.

In this "What if" scenario, most traders will be the winner, the late ones may not;
as long as there are people who's at the other side of the market who aren't traders but casual buyers/sellers that fuels the supply.

Everyone's discarding the fact that this is a "What if" scenario and answering "it can't be" 

@GreatArkansas You have a baseball cap and you must be a WO veteran or at least a regular, I thought you should be well-informed.
Here's the answer: it will be a race, the slowest will lose or at least won't benefit from it as there will be NO buying order for the losing side (you said everyone is an expert).
Who will buy if it is obvious to them that it will drop even more for the next month or so.

Wait, they picked Verge as the sole payment option for crypto and they dubbed it "We're Accepting Crypto"?
Who the hell uses verge other than for day trading, <1% of the crypto community 
They should make it Bitcoins (also ETH) and it will grow beyond 50%, if not, about a quarter percentage.

Linking the free videos to the percentage wasn't correct, it never contribute to their total sales thus, will not affect the percentage of crypto earnings.

"Selecting" like click to highlight? Yes it won't be selected that way.
Aside from manually writing the server address/IP, you can also right-click and select "use as server".

You can lock this topic now if you don't have any other concerns.

Since you've received that message, you must be using a "safe" version (v3.3.3 or the latest) and connected to a malicious server.

Just like the message said, connect to a different server and try again.
I'm not experiencing the issue since I'm sticking to one server.

AFAIK, Trezor implements it differently than Electrum's method.
It signs the legacy format of the address using the same private key of the SegWit address.

I'm not sure if it's Trezor or another Hardware wallet though.

For the meantime, here's an open-source "verifyer" of messages signed to SegWit addresses using Trezor wallet (not mine).
https://jhoenicke.github.io/brainwallet.github.io/#verify <- Different than the regular brainwallet/#verify link.
I already tried it, and it worked.

So with this you've successfully followed those tutorials.
The problems are the address type and connection/synchronization issues.

For the address type:
If the SEED was created by Electrum, it will immediately recognize its "type" after you pasted it to the input box.
If it was created by an external BIP39 tool, you need to choose the right address type to match your old address.

• Select "legacy (p2pkh)" if your previous addresses starts with "1".
• Select "p2sh-segwit (p2wpkh-p2sh)" if it starts with "3".
• Or select "native segwit (p2wpkh)" if it starts with "bc1".

For Connection issues:

• At first run, Electrum requires to download the "block_headers" file to display the correct balance and transaction history.
  Even synchronized the balance will not show up if it wasn't downloaded yet (about 44mb+).
• Read the other replies above for more possible causes of connection issues.

This will only work if he's importing the BIP39 SEED, not the private key and with the latest version, this is not necessary.
After pasting the SEED, check "BIP39", and after pressing "next", there will be a checkbox of the available address type,
he can just select, "Legacy", "Native-SegWit" and "P2SH-Nested Segwit" to match the original addresses.

Then consider to lock the thread and/or edit the title and add "[SOLVED]" at the beginning 

This might come in handy if someone got the same issue.
It will show in google search anyways.

@RodeoX, Any news about this year's GeoCache?
We are way past the first quarter of the year and we haven't heard anything from you since March.

For this year's round, don't left it floating in the ocean since the chances that it will be taken by the coastguards or get mistaken as a floating package by drug syndicates is high.

If anything, do not use the idea of splitting the private key into two/three and place them in different locations, this will complicate things a lot.

-A 2/3 miltisig will do, 1 private key in the main thread for all participants, 1 prv key in the Cache and 1 for you (in case of the package being lost/destroyed).
-Or the first seven characters of the private key in the thread and the rest written in the cache.
Both will require a procedure written as a note included in the package.

This way, the winner will definitely visit this thread and may consider sharing his "treasure hunting" story.

Lets' go back to the root of this long discussion: exposing the Public key.

Okay, either of the two methods will indirectly expose the address' public key. By spending the UTXO, the user will have to provide a Signature and Public key to the scriptsig.
But as everyone mentioned, it's pretty safe as long as the user hasn't been reusing addresses.

---

The topic is getting derailed from "How to prove that an address belong to you?" to ECDSA security.

To sum it up, since either is "fine", let's categorize the main question from:

• 1. How to prove to someone that an Bitcoin address belongs to you?
• 2. How to prove to someone that an UTXO belongs to you?

[1] Sign a message.
[2] Sign a message or Spend the actual UTXO using coin control.