How much do you want for this account?

Closing thread since Apparently I'm promoting a scam...

The tweet for those who didn't follow the link:
According to the OP, Theymos changed from his previous host NForce to another host because of suspicious activity. This would explain the IP change.

Edit: Found the quote:

That list is for the most recent list of exit nodes which updates every hour. I would suggest looking here: https://collector.torproject.org/formats.html#exit-lists for archived lists from the past few days to see if one of the ips was an exit when the attack occurred.

What was the message of the email, since I can't find any email from Bitcointalk or Theymos.

Right. I did not think of that. I will edit the post.

1 Satoshi   = 0.00000001 ฿   
10 Satoshi   = 0.00000010 ฿   
100 Satoshi   = 0.00000100 ฿
1,000 Satoshi   = 0.00001000 ฿   
10,000 Satoshi   = 0.00010000 ฿   
100,000 Satoshi   = 0.00100000 ฿   
1,000,000 Satoshi   = 0.01000000 ฿   
10,000,000 Satoshi   = 0.10000000 ฿   
100,000,000 Satoshi   = 1.00000000 ฿   

Therefore 5000 Satoshi is 0.00005 BTC.


How many pages are there to be added?

What campaign is the Sr. Member enrolled in and how will we get the Bitcoin from it?

According to Theymos in his post before the forum went back down:

...

It wouldn't hurt to update to 64 bit Java. A lot of websites use java to do things, and 64 bit is generally better than 32 bit. There are no negative effects of upgrading.

There isn't much to mess up with a wallet backup, especially on a web wallet. All that happens is you download a copy of your wallet, it won't effect your wallet's balance or anything unless someone steals it. Even then, you can still get an encrypted backup which is decrypted upon upload to their site for a restore if you wish to do so. Since it is a web wallet, a backup is not necessary, since they probably also back everything up and if their servers crash, they are liable and should reimburse you for any loss.

Why are you nervous about giving them your phone number for extra security? 2 factor authentication makes everything much more secure as a hacker who steals your password still cannot get into your account unless he also stole your phone.

I suppose that is ok. You should download encrypted backups of your wallet, and keep multiple copies of it in different places. Perhaps one on your computer, another on a flash drive, and a third on your old phone. You should also create a paper wallet, there should be an option for this in blockchain.info. You print out the paper wallet and put it in a safe deposit box at the bank. These are the normal tactics of keeping your Bitcoin secure.

Why would you need a password generator?

You should be able to download an app and transfer it to your phone to install it, depending on the phone. The app should never access the internet and be done completely offline. This is a viable air gap, but why would you need it?

PGP is an encryption system, unrelated to the functioning of Bitcoin. It is similar to Bitcoin, in that it uses public key cryptography. PGP can be used to verify that someone is who they claim they are by creating a signed message which can be verified. It is also used to encrypt and decrypt messages so that certain information can be kept private. GPG is an implementation of PGP.

Sorry, I misunderstood your problem.

I think that there may be open issues with some of the altcoins. You should check the git repos and see if there are any issues that are similar to yours. Also, it would be helpful if we knew what the coins you have on this NFS.

Regarding your corrupted wallet.dat, perhaps your backup had accidentally backed up a corrupted version of the wallet before you noticed?

At this point, I am not entirely sure. But, I believe that it has something to do with verifying each transaction e.g. checking the signature and scripts, however, as I said, I am not sure. I recommend that you take a look at the code and see if you can find the issue yourself. You can find the source at https://www.github.com/bitcoin/bitcoin and there are developer docs, which are easier to follow, at https://dev.visucore.com/bitcoin/doxygen/. The specific methods you are looking for are located in src/wallet/rpcwallet.cpp. If you do find that there is an issue with performance with no reasonable explanation, please open an issue with the developers, and perhaps write a patch and submit that to the core devs.

Since you are running multiple nodes, the nodes will write and overwrite things in the data directory. This causes corruption because the nodes don't know what the other nodes wrote and the sudden change of data along with simultaneous reading and writing done by the nodes to the data directory causes all of these issues. The data is then constantly changed and corrupted, causing you to need to constantly reindex or redownload the blockchain. Since all of the nodes are also accessing the same wallet.dat file, they cause it to be corrupted like the blockchain database files. The only weird thing is that the backups were also corrupted. You should keep the backups on a separate machine just in case.

AFAIK Bitcoin Core keeps an index (or something like that) of all of the transactions for the addresses so it may not look through the entire blockchain. However, getbalance and listunspent must still iterate through that list for each of the 16000 addresses in order to find which ones are still unspent and what the total balance is.

bitcoind is slower because there are not just 16000 things to look through. It must search through all 34 gigs of blockchain and find all of one addresses transactions, add up the inputs and outputs, and find which transactions have yet to be spent. Then it must repeat this for all 16000 of your addresses in order to return the data you asked for. This is why it takes so long.

In this case, and most cases involving services, it doesn't matter what happens to the proceeds. What matters is the user's privacy. Say Bob signs up for that porn site, but doesn't want his girlfriend Alice to know. If the site uses the same address for everyone, then Alice could look at Bob's transactions and see that he made a payment to a porn site. However, if the site gives one deposit address per user, then Alice will see that Bob is making same sized payments consistently to someone at a consistent time interval. If they generate a new address then Alice will only see that Bob is sending same sized payments to someone, possibly different people because of the different addresses, and is sending them at a consistent time interval. With cases 2 and 3, Alice will know that Bob is paying for something. With case 2, she knows it is the same thing, a subscription to something. With case 3, she is unsure if it is the same thing, if the price is a common price, and she cannot be sure that the payments go to the same person.

Most sites use case 3. They generate new addresses for each deposit. They also usually don't sweep all of the funds into the another large address, but instead will send withdrawals from an address that another user deposited in. This helps maintain anonymity.

The only good reason that people shouldn't reuse addresses is to maintain privacy. By not reusing addresses, it becomes more difficult to monitor and track someone's payments. As a service provider, it would be easier to give each customer their own address, BUT, many bitcoiners do not like to have their payments to be easily tracked, and by generating new addresses for each deposit, a service will appease the privacy minded and could gain more business.

The Bitcoin Address field is a place for you to advertise your bitcoin address.

It is still possible to maintain anonymity even with advertising an address. You could send the Bitcoin received by that address to a mixer or use any other method of mixing and anonymizing Bitcoin. It will prevent others from knowing what your other addresses are.

Primarily because people can track someone's payments to a site and reduces the anonymity.

Yes. I know that in some clients, like Bitcoin Armory, you can specify which address(es) to send from, and it will only be able to spend from the unspent inputs for that address.

It will prevent you from being able to send more than the amount for that address and it will not use other inputs unless you tell it to.

Any address means that it will create and send the transaction using as little input transactions as possible to keep the transaction as small as possible.

The "sender" could be many different addresses. However, the more input transactions you use, the higher fee you will need to pay.

Your first scenario would not be ideal, as different wallets and services may send from addresses that the customer does not actually own. It would be difficult to determine who sent what transaction and the customer may not be reusing addresses, so you would get lots of complaints, and it would be hard to manage each customer's payments.

The second scenario is very good for management, but reusing addresses is not recommended. However, it would allow you to easily track who is sending payments and easily credit them. You could also periodically sweep the funds from those addresses into your own main address. This however, breaks some of the anonymity because then others can see how much and when someone is depositing into your service.

Ideally you would use the third scenario, which gives each customer a new address each time, and your backend would need to know which address will be the one that receives the payment so that it can record the total balance in a database. Then, after the payment confirms, it generates a new address and waits for a payment to that address. This helps the payments stay anonymous to outsiders. You could then periodically sweep all of the funds into your main address.