Yes. Armory is connected to core.

You can't see your coins yet because your wallet is synced up to block 389815 (according to your screenshot).
However, your transaction was included in block 633007.

Once core has passed this block, you will see your coins.





If the address you sent the coins to is from armory, no. You did not lose your BTC.

With a transaction, you are transferring the ownerships of UTXO's (your BTC's) to a different public key.
And with the corresponding private key, you are able to spend them.

Just because you don't see them in your wallet yet, doesn't mean that you don't own them.

No. You are never "always on the safe side".
There are multiple ways to infiltrate an air-gapped system.
And there are even more ways to exfiltrate data from such systems. Using a flash drive is just the easiest one. Using the cable of the monitor to emit radio waves is one example. Those radio waves can be received by any mobile phone with an integrated FM receiver.
Malware does exist to do so. There are PoC's available for that. Studies are being done in this field.

You will never achieve to always be safe.
The goal is to increase the security as much as possible, not to have a completely secure setup. Because that is not possible.

Segwit address do start with bc1, not b2.



There is not a single reason to be "against such a tx". This doesn't make sense.
The recipient doesn't care about the type of transaction. All he cares about is that he receives his funds.



It is. Always.

If you can't write a simple script to do the actions you need to be done once a payment is coming in (or confirmed), you are - by far - not able to host a lottery site.
Running a full node is not risky at all.

Obviously you have to check your implementation. Setting up some triggers is not as hard as setting up the rest of the backend of a crypto lottery site.

The choice purely depends on what OP needs and wants.

You can always send to any address type and receive from any address type.

The reason, you sometimes can not withdraw etc. is because their software has not been updated (in 3 years).
Stop using services which do not allow to withdraw to a bech32 address. They obviously do not care being up-to-date. I wouldn't trust them.

Again, the network allows you to send/receive to/from any address type.

You can not "recover" your coins in terms of undo the transaction.
The transaction is already confirmed and the funds now belong to the address you sent them to.

You don't need to be online to receive BTC and you don't need to be online to send BTC.
You just need an internet connection to broadcast a transaction.

If you want to spend/access your coins, do this:


If not, what exactly do you want to achieve ?

You basically have 2 options:
1) Use a 3rd party to handle all the payments or
2) Set up a full node and some scripts yourself

Option 1) is easier to do, but has the effect that you are not in control of the private keys and with most providers you have to pay a fee.
Option 2) takes a bit more time to set up, but you will be completely independent and have full control over your private keys. You'd need to write some scripts (e.g. to update your DB whenever you receive a transaction / confirmation).

Which option you want to choose, fully depends on how bit you want to scale your project and whether or not you care about security / privacy.




And don't accept "help" from new accounts.

Or even the power supply using probes connected to the PC and the electric control box  

Malware exists for all of these types already (power supply, speaker, hard drive LED's, monitor to emit radio frequency waves, ... )

---

OP, if you are interested in bridging the air gap, take a look at the ANT-catalog from the NSA (leaked via wikileaks):



  

Die Generierung/Ableitung funktioniert nur in eine Richtung:

Allgemein: Private Key -> Public Key -> Adresse
Mit master keys: Seed -> Master private key -> Master public key

Und Adressen lassen sich entweder mithilfe des xpriv oder xpub generieren:
1) Master private key -> Child private key -> Child public key -> Adresse
2) Master public key -> Child public key -> Adresse

Rückwärts ist dies nicht möglich. Das heißt du kannst von einer Adresse, nicht auf den master public key schließen. Und dementsprechend kannst du auch nicht herausfinden ob unterschiedliche adressen vom selben xpub stammen.

Wichtig: Mithilfe des master public keys und eines child private keys lässt sich bei non-hardened derivation paths der master private key errechnen. Also bei einem sicheren Setup niemals einen private Key teilen.

Etherdelta - their server - does not know anything.
The local javascript applicatoin which is running inside your browser tells you that the private key does not match the public key.




?
When you sign a transaction (as i have described in my post earlier), you are using your private key.
Everyone in the network can then verify it using the public key.

Whether you or someone else (with access to your private key) signed the transaction does not matter.

Correlation is not causation.
That's not an assumption you can make based on your data.

This just means there is a connection between these two events. But one does not cause the other.

Your private key is (or better: should be) only stored in your wallet on your PC / mobile / whatever device you are using.
They are not stored on the blockchain at all.

Your private key is used to sign transactions. These signatures can be verified using the corresponding public key.
No one needs access to your private key to verify signatures.




In the case of etherdelta, they don't have your private key. The private key is generated locally in your browser.
You are not given the key from their server.




You don't ever enter your private key anywhere.
You sign a transaction using your private key. And everyone can verify it by using the public key.

For visualization:
A transaction = "I want to transact X BTC from address 1 to address 2
Then you sign the transaction using the private key of address 1.
Everyone can then verify the signature by using the public key of address 1.

Please note that this visualization is not completely technically correct. But it gives you an idea how it works.

The same vulnerability has been fixed by trezor.
This has something to do with segwit and other wallets are most likely affected too.

Trezor post: https://blog.trezor.io/latest-firmware-updates-correct-possible-segwit-transaction-vulnerability-266df0d2860

Basically any reputable desktop- or mobile wallet.
For desktop usage, electrum is a good wallet which offers some nice features.
Note that there are quite a few phishing sites who look like the original one. Download only from https://electrum.org and preferably verify the signature.

For a mobile (android): Mycelium, samourai or electrum would be recommendable.

Funktioniert aber nur für DT1 Member und nicht für alle Member des Forums 

(This does only work for DT1 members and not for every one )

I pm'd you.

Your wallet is doing this in the background.

All you have to do is set the amount you want to send and the receipent.
Your wallet will figure out which inputs to use.


In electrum, if you want to set the inputs yourself, you can go to the "Coins" tab -> Select multiple UTXO's and click on "Spend".
You'll see the chosen inputs when signing/broadcasting the transaction.

I might be able to set something up for you.

If you could answer the following questions, we can work something out:

• What are the quantities you will be ordering per month ?
• Are you going to fully dropship? No stock in your warehouse ?
• What is your expected price per tshirt ?

Feel free to answer them in a PM if you want to.

Laut meinem Tool sind es 34 trusts und 50 distrusts. Und das deckt sich auch mit dem von dir verlinkten Trust list viewer.

Auf DT1 bezogen, liefert mein tool das hier:




11 inclusions; 20 exclusions.

You can include as many inputs and outputs as you want.
Of course there is a limit. The current limit for the maximum size of a transaction is ~100 kB. That's way higher than your transaction should get.

Note that if you receive multiple transactions to the same address, these are all different UTXO's.
If you receive 10 x 0.1 BTC to address X and send your whole BTC from address X, your transaction will have 10 inputs.




You can not directly import your core wallet into electrum.
And AFAIK you can't import private keys into an HD electrum wallet (not absolutely sure about that).

But if you create a wallet with your private keys from electrum and from core, yes. The BTC will add and you can send the whole amount in a single transaction.