What are you asking exactly?

I think I can rephrase your question:
What can I use money for?

Bitcoin is money, not something else that is mysterious and magical. It can do everything that money can do, as long as both parties accept it. The same applies for regular fiat money.

I suppose you would need to dig through GPG's code to figure out how it is packaged. I will take a look at that.
Edit: Openssl cannot sign and encrypt it seems. Here is a starting point for figuring out how GPG does that: http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=blob;f=g10/sign.c;h=ed8ac7328a151ee9bd57f5b6ca41cb25e6330731;hb=refs/heads/STABLE-BRANCH-1-4#l954

I verified it incorrectly, that was the problem. BTW I am not using GPGTools since I don't have a mac. Rather I am just using GPG command line on Ubuntu, which should be the same.

I'm looking at it and trying to figure it out. In the meantime, this article should help: http://www.sysmic.org/dotclear/index.php?post/2010/03/24/Convert-keys-betweens-GnuPG%2C-OpenSsh-and-OpenSSL
That is unfortunate. I don't know node.js, so I can't help with implementation. I can however help with logic and conceptual stuff.

How does GPGTools package the sig, encrypted data, and the key? An example would help.
edit: when I use your command in the OP, it does not produce a signed file, only encrypted.

You should not need two different RSA key pairs. RSA keys are RSA keys, and it doesn't matter how they are formatted in the export, they are still RSA keys. You just need to figure out how to export them in the same format that can be imported to two different software. Openssl uses PEM format while PGP does its own thing. It should be possible to export the raw hex of the key and then convert that hex to the proper format before importing it into your software.

Any particular reason to use Node.js? What about Java or Python which are also supported by Lambda?

Just ignore it and don't send people there. It is NOT THIS FORUM and it is most likely a phishing site.

No, a full node is not the same as the blockchain and it is not transaction confirmation points. A full node is a peer on the p2p network which will verify and validate every single block and transaction it receives according to the built in consensus rules. If the transaction or block validates, then it will be relayed to all of its peers. The consensus rules are built directly into the code so an upgrade is required to change them. Full nodes also store the entire blockchain locally and provide it to others when requested.

The blockchain is decentralized since there is no central authority that governs it. Not sure what you mean by bitcoin as an application being decentralized.

Then that full node is the only one that can provide the blockchain to others and it will become the central authority. Since SPV wallets rely on full nodes to supply the right data, that one full node could in theory rewrite history and make things up with the blockchain and no one would know about it.

It isn't. It is just that the US Dollar is the most prominent reserve currency in the world so Bitcoin just happens to be typically priced in dollars. However go to exchanges and you will find trades for Euros, Yen, Yuan, and many other currencies around the world.

The Bitcoin community is everyone who is involved in Bitcoin.

The block reward halves in order to control the supply of Bitcoin. If the block reward did not continue to halve and eventually go to zero, then Bitcoin would constantly be inflationary and over time the value of Bitcoin would drop. Being deflationary is one of the most important aspects of Bitcoin.

The blockchain uses cryptography to ensure that the data stored within blocks cannot be edited. Each block is referenced by its hash. The hash is a cryptographic function which converts all of the data in a message (in this case the block) into a long 256 bit number represented in hex. This number will change depending on the data in the block. If anything changes, then the hash will not match and the block is invalid. To prevent data in transactions from being changed, the transaction uses signatures, which also use hashes. If any data that was signed does not match the signature, then the transaction is invalid. Since transactions are stored in blocks, changing a transaction will result in making the block invalid as well.

It went bankrupt. Supposedly the Bitcoin was stolen, but people aren't sure.

We don't know how many bitcoins were lost.

There are many use cases for Bitcoin and the blockchain. Specifically the blockchain can be utilized to store data but this is not recommended. Many of these companies are utilizing the decentralized nature of Bitcoin and the blockchain to do stuff.

Pool mining is to pool people's resources together so that more mining can be done. It ensures that the miners in the pool will get paid something, and it also ensures that the network will continue to stay alive. If we didn't have pools, the mining would become more discouraged because your odds of getting any reward is very little. Through pools, people are incentivised to mine since there is always some payout for mining with a pool.

I believe that smart contracts are currently possible with Bitcoin through using p2sh addresses and the locktime field in transactions. The upcoming soft fork to enable OP_CHECKLOCKTIMEVERIFY will also help to facilitate this as well as the proposed OP_CHECKSEQUENCEVERIFY.

It is relatively hard to do and it takes some luck. Bitcoin Core 0.12 is supposed to have Replace-By-Fee so it should be easier to make a transaction with a higher fee that gets confirmed.

It looks like you got a ransomware virus. Do not pay the extortion amount, just restore everything from a backup. And get a antivirus to remove everything.

Well that is interesting. I just tried it too and I logged in without having to enter the code. I think there is a problem with their system. Open a support ticket with them.

Go to the settings tab and you should see a box titled "Google Auth" In there, there is a QR code which you scan with the google authenticator app on your phone. Then just enter the code for the site in the box and click verify.

According to the source code ( https://github.com/bitcoin/bitcoin/blob/b632145edeb376b4d1597f192ca00634f7d2866c/src/main.cpp#L944), an absurdly high fee is considered the minrelaytxfee * 10000. I suppose you can increase that by increasing your minrelaytxfee.

Honestly though, what is the point of having this? I thought high fees were a good thing.

How do you compare the security of two algorithms that are entirely different? ECIES is encryption while ECDSA is a signature algorithm, two different things. Bitcoin doesn't use encryption at all.

Definitely more than 10k was seized in all of the darknet market busts. Silk Road itself had 144K BTC seized from the site by the US government.

bump

The US government held (maybe still holds) bitcoin that it seized from Silk Road. It has been auctioning them off to buyers for a lot of money. The last one was for 44000 Bitcoin.

Wow, you are all bad at answering the question!

Nothing stops the buyer from initiating a chargeback. The point of using an escrow for PayPal transactions is that the escrow holds the Bitcoin for the 180 days that the Paypal transaction can be charged back. Then, after that time, they release the funds to the respective members. If a chargeback is initiated, then the escrow will send the funds back to the seller and the deal doesn't go through. In that way, no one loses anything except time.

I meant could I see if I had already reported a specific post, but you already answered that below.

Thanks. I really hope that this is something that can be implemented in the new Forum.

Is there any way to see if I have already reported a post yet? Can I see what posts I have already reported? It would be nice to know so that I don't accidentally report a post twice.

use cointape.com to find the ideal fee to set.

The default fee in electrum should be 0.0005 btc per kb. You will need to subtract that amount from the amount you want to send.

Go to wallet options and click export brainwallet. Then copy the text that pops up in the red box and go to bitaddress.org. Click on Brainwallet and enter the text you copied into the two boxes. Click View and you should see that the address it generates matches. Then copy the text under the private key heading and import that into another wallet. You should be able to send the bitcoin from there.