For Bitcoin Core and its derivatives, the blockchain is stored as multiple files, around 130 Mb each. The blocks are stored on the disk in their serialized format. The extra data for each block are the 4 network magic bytes and a varint the indicates the block size in bytes. Those data files are append only. There are additional files which index the locations of each block as well as undo data for those indices because everything is append only.

That is not possible. The bitcoind will have to download the entire blockchain before it can be used. You can set it to be pruned, but it will still need to download all of the data.

You have to add -zapwallettxes to the startup command for Bitcoin Core. You can open up the terminal for linux or Mac or open up the Command Prompt for windows and type the following (assuming that Bitcoin Core is installed to default locations):
Bitcoin Core will start up and once it finishes loading, you should see that those unconfirmed transactions are no longer listed. At this point, you can shut down Bitcoin Core and start it up as you would normally.

Is that it?

Can you post the log files?

It looks like you are trying to send a transaction which spends an output that was already spent in another transaction. I think you should try rescanning and then recreating the transaction.

There is no way to earn free Bitcoin. You must do some sort of work for Bitcoin. It isn't a get rich quick scheme and it isn't "magic free internet money". Bitcoin is just like any other money. You have to earn it. You earn Bitcoin the same you earn any other money, by selling some sort of good or service.

It is actually fairly difficult to send a transaction with 0 fee now because a lot of wallets protect against it.

The only way I can think of right now is to create the transaction manually in Bitcoin Core with the createrawtransaction RPC command. However this method is complicated as it is essentially building the transaction by hand.

To do this, open up Bitcoin Core and go to Help > Debug Window > Console. In the textbox at the bottom, type the following:
<id> is the transaction id of the output you would like to spend. <n> is the output index of the output you would like to spend. <address> is the address you want to send to and <amount> is the amount you want to send to that address.

To have more inputs, put a comma (,) next to the right curly brace for the txid and vout. Then copy the {"txid":"<id>","vout":<n>} and change the <id> and <n> to match the output you want to spend from.

To add more outputs, put a comma (,) next to the <amount> and copy the entire "<address>":<amount> and set the address you want to send Bitcoin to and the amount you want to send.

To send with 0 fee, you must make sure that the total of the outputs you spend from matches the total of the amounts you spend to. If you do not, the difference becomes the transaction fee; this method does not automatically create change addresses.

Once the transaction is created, you will get an output of a hex string. Sign the transaction with
where <hex> is the hex string. This only works if you have the private keys to the address you are spending from in Bitcoin Core. You will get another hex string as output.

Broadcast the transaction by doing
where <hex> is the hex string.

Then you are done.

If you need help, you can ask me and I can give you a more detailed explanation and an example. I can help you with creating the transaction itself as well.

My Bitcoin address is in my profile.

No. The point of a public key is to be public and shared with others without revealing the private key. The address is derived from the public key so it too can be shared. If it were possible to derive the private key from the public key, then the entirety of Bitcoin would be broken and there would be a massive problem not just with Armory but with Bitcoin itself.

All that would happen if someone got your watching only wallet is that he would be able to see every single transaction you make. At worst it is just a privacy leak for you.

AFAIK cookies can't really be revoked without the admins going into the server and deleting all of the cookies, so that is an issue. If you were to be hacked, the attacker could pretend to be that person even if the user changed passwords. At the very least it would be a nuisance and at worst, the attacker could use high ranking and potentially positive trust accounts to scam others.

It would be a lot easier if Bitcointalk had something like OAuth 2.0

This is an interesting idea. It could help to curb some spam depending on how the payments work. You could make it so that users are paid at a fixed rate and the user doesn't know the terms of the payment, just that if they are chosen to be in a campaign, they will get at least X Bitcoin per week (or month or whatever). That would help to curb spam as then there isn't an incentive for people to spam to meet their post requirements.

There is, of course, the huge security issue. The problem is that many users may not feel comfortable with entrusting your service with their login credentials, especially since having the login gives full access to the account. This could potentially lead to privacy leaks and loss of the account if your service were to be hacked. The risk goes up for higher ranking members and those with green trust.

Lastly, there is also a technical issue. Bitcointalk only allows you to perform a login action once every 45 seconds per IP. If you need to change the signatures and avatars on a lot of accounts, you're going to need a lot of IPs or servers. They will also IP ban you if there are more than one request per second per IP.

It wasn't actually that big, but for the machine I was using, the database was getting a little large. The server is the second cheapest Amazon EC2 instance which only has 0.6 Gb of RAM. I think that was causing the issues.

I've been seeing about 200 page views per day. The database had 1922 entries when I removed it. It is supposed to only store each entry for one week, so that should be representative of the number of requests in a week.

I've reset the server and removed the old database, it was getting ridiculously huge.

All old tokens will no longer work. If you need to see the results of an old token, please contact me.

It is a list of bitcointalk users (people) who are considered trustworthy enough to escrow bitcoin.

These users were determined to be trustworthy by their past actions. They have demonstrated that they can hold a large sum of money without stealing it. There is a feedback system. If you look at the person's profile page, you can see their trust. Clicking on that link will take you to a page where users have left feedback for that person. There have been escrows who, for a long time, were trusted, but became scammers. These people were trusted because they escrowed for a long time, did many trades, and did not scam until a long time later.

It means Announcement. The ANN thread is where the escrow announces their service and a lot of feedback about them also ends up there.

AFAIK, no, at least, not for multiple currencies like Bitcoin and PayPal. Of course, PayPal itself is also an escrow service.

When doing escrow with Bitcoin, you should also use multisig escrow, especially with large sums of money. This means that in order to send the escrowed funds anywhere, multiple people must sign the transaction. It prevents the escrow from stealing the funds.

How long has it been stuck there? Can you provide us the debug.log file? You can get it by going to Help > Debug Window and clicking the button to open the log file. Then just post everything in there here. If it is too long, go to https://pastebin.com and paste it there and post the link to that paste here.

Please stop spreading misinformation. We know that you didn't get your question answered and are now butthurt. Your posts aren't doing you any favors as you are spreading misinformation and acting like an immature troll.

Armory is not a one-man operation. There are still multiple people who are actively contributing to armory, myself included.

And neither would I. I follow the advised security practice of verifying the source code myself and building from source. You should do this too.

Maybe you missed the first part of his statement when he addresses the security:


If you can't follow that advice where he EXPLICITLY says "Don't trust me" and you don't do anything else to verify that nothing is malicious, then that is your own fault. If he were to release a malicious Armory version, then the other people who work on armory such as myself, droark, josephbisch, fanquake, etc, would notice that he inserted malicious code into the software. If he did it in the binary and not the git source, then simply following the advice of "review the code and build it yourself ... [or] find someone you trust that did it for you" would protect you from such actions.

We are also working on a system similar to Bitcoin Core's gitian builds which will ensure that the binaries are built from the source code that it is supposed to be built from.

You should update the software. The latest software doesn't have this issue anymore.

You will have to rescan the blockchain. The software does not rescan the blockchain when it reindexs or resyncs, it simply isn't something that should normally happen. Start Bitcoin Core with the -rescan option and it should fix your problems.

You use a USB drive and download the file to it. Then verify the installer and take it to your offline computer and install. At not point is the offline computer then connected to the internet. This security isn't a meme, it is just security for the paranoid.

You can earn bitcoin in the exact same way that you earn any other money. You can sell some sort of good or service for bitcoin

You can't. As was said by Belcher in the thread you mentioned, there are two forks, the Bitcoin Core fork and Bitcoin Classic. I'm not sure if sure if any of them have faster confirmations. You should only use the Button Core fork because that is more representative of the mainnet state.