The site counts the posts by itself, it doesn't mirror from bitcointalk. This may lead to some discrepancies if any posts of yours were in a thread that is in a section that a normal account cannot access, like the trashcan. Since the bot can't read those posts, it won't know about them, but the forum still counts those posts since they are still stored in its databases.

Seems about right. I have to wait at least one second between requests to bitcointalk otherwise the forum will give the bot a temporary ip ban. To be safe it waits 1.01 seconds, so the minimum time it could possibly take is the number of pages of posts you have in your show posts page multiplied by 1.01. Of course it will take a little longer because fetching the page takes time and so does parsing it.

It isn't misleading since there is more than just the price that is given. However if you think the prices are to high, suggest me a lower rate for the algorithm specified in the OP.

What exactly can a banned account do? What can they read, what can they change, etc.

I want to know this because I may have the account that I use for part of my account price estimator banned (as in ask a staff member to give it a permaban). I would want this because I fear I may one day accidentally publish the password for the account on giving when I publish each new code update. I don't want random people to be able to access the account and post from it. However before making such a request, I need to know whether having that account banned will work for my purposes.

Also, having that account banned wouldn't get me banned for ban evasion since I will have requested that it be banned, right?

Heh. Whoops. I forgot to add the wait time code back in when I migrated the program to use JSoup earlier today. It probably got itself IP banned. I'll fix that now.

Edit: Should be fixed now.

Blockchain.info's priority thing is not particularly accurate. In fact anything that estimates the confirmation time is probably wrong.

The problem with your transaction was the small fee. You will need a higher fee in order to get transactions to confirm faster.

Read the OP for the algorithm details.

That is a good idea. I think I can make it so that it would only get the addresses that you have posted in non quoted text, so it may grab an address that isn't yours. I would definitely make it so that it would only pull addresses from the stake your address thread and the marketplace section.

The program is a command line program. You need to do Shift + Right Click in the directory where you extracted the files. Then select "Open Command window here". If you don't see that option, make sure you don't have anything in the folder selected. When you see the command prompt window open, type the name of the exe file that you want to run and it will run. You will need to specify the options in the command in order for it to work properly.

Yeah, that is probably because I changed the HTML parser I was using. Previously it was using HTMLUnit and reading the HTML source files line by line. I am now in the process of migrating it over to use JSoup, which is probably working faster than before.

Yes, the inputs to a transaction are the outputs of a previous transaction. You can use coin control to select which outputs you want to use as inputs in the next transaction.

Yes, it is. You need to reverse the base58check encoding to get the raw private key. Then you can apply the base58check encoding for the altcoin that you want.

In networking, ideally each port corresponds to one service. Since port 8333 was not used for anything, it was chosen for bitcoin. That is why no other program used port 8333.

There may be vulnerabilities, but that would be a problem in bitcoin core. The vulnerabilities in ports only come from the program that opened them and the way that they handle the data from the port. If there is a vulnerability, it is a 0-day.

Yep that's a bug. I'll fix it tonight

Edit: fixed

It is possible to trace the origins of the Bitcoin in your addresses, but they will not go back to the same block. It would all trace to a bunch of different blocks. All you have to do is follow the chain of inputs to outputs to find the block the Bitcoin was generated.

Your Bitcoin is not from the first block ever mined, or from any of the first couple hundred, since the bitcoin generated in those blocks have never been spent.

Quantum computers only advantage against traditional computers with Bitcoin is that it can factor prime numbers much faster. This makes it faster at finding the private key to a known public key. I don't know how much faster, but I do not think it will be able to find the private key in less than 10 minutes. QC's are not significantly faster than classical computers when it comes to hashing.

Even so, there are built in mechanisms in Bitcoin which mitigate the effects of a QC. If you are using bitcoin addresses are they are supposed to be (without reuse) then you will mostly be fine. If the addresses are have 1 funding transaction and the second transaction is moving all of the funds out to another address, then it is safe because there will be nothing for the attackers to steal. This is because they will only know the public key after you send the second transaction, at which point there should be no funds left in that address. They can only get a private key if the public key is known.

The other aspect is with mining, and QCs are not known to have any significant advantage with hashing than classical computers. Even if they did, then when the difficulty adjusts, then the attacker would not be able to produce blocks faster than everyone else, they would still come out on average every 10 minutes.

Just post the bottom 100 lines then.

Well I don't see any error. Can you post the full thing. Put it in the quote brackets (button with pound (#) symbol above the reply box)

Yeah, I can't even ping you, so something must be blocking you. It might be your ISP is blocking any connection that wasn't initiated by you.

Thanks!

What is your node's ip address? You can PM me it if you don't want it publicly shared. I will try to connect to it with my node.

You only need the wallet.dat file. The wallet.dat file contains the private keys, and the private keys are what you need to spend the Bitcoin. The rest of the data that it uses from the blockchain can be downloaded later as it is all public. The roaming/Bitcoin folder contains the blockchain as well, but that is not necessary in a backup.