1) It might, but it doesn't matter.
2( Check shorena's list: https://bitcointalk.org/index.php?topic=929353.msg10456173#msg10456173 , but again it doesn't matter that much anymore.

It will not take forever.

From the screen shot it seems you tried non-default ports. Why don't you try 8332 for starters?


That is the IP of your VPS, right?




Can you see your node on bitnodes? For example if you put your external IP in the search box here: https://getaddr.bitnodes.io/nodes/?q=


Check if the appropriate ports are open: http://www.yougetsignal.com/tools/open-ports/

*troll mode*

+1 I had high hopes for an Asia server for a while, either HK, KR or SG. Don't matter now. There's plenty of pools in China now. Missed opportunity.

Maybe time to chuck in this again:

Tx signing via minimodem
https://bitcointalk.org/index.php?topic=735111.0

Can of course be used with any sort of data you need to send / receive from the air-gapped system.

I'm sure you checked the file hashes? Then you can report a false positive to that anti-virus )or whatever it is).

*trollmode* Sure you can. Just depends if you're willing to pay for it.

*trollmode* details, details, details

It can also be found in the source on github:

https://github.com/bitcoin/bitcoin/search?utf8=%E2%9C%93&q=wladimir

The infographic shows only FAT16 and 32 are affected?

It depends. One version we waited 2 months for it to show on the ppa. Another was on the ppa even before it was announced officially.

It's fish friendly because the speed of rotation is relatively slow. Also when they design a particular project they take the size of the biggest fish living in that river into account.

Just FYI, there have been Release Candidates in public use since about 4 - 5 weeks.

Yes. Read the paragraph "How to Upgrade" in the first post.

42 is THE answer!

Reminded me of threads like this: http://www.forexfactory.com/showthread.php?t=159499 

Here's one for NLC, almost a pony:

Looking forward to the ppa

Re pruning: I probably should have linked directly to this: https://github.com/bitcoin/bitcoin/pull/4701


I should have mentioned that I actually never have done this particular scenario   Anyway, some pointers:


Re IP: Your laptop will have an IP on your internal network. That is its private IP. Probably starts with 192.etc. If you want to connect to it from outside your internal network, I recommend you fix the laptops' private network IP in the router. (Look for a setting called "DHCP static IP" or similar). Your external (public) IP may change from time to time (depends on your Internet provider). Unless your Internet provider gives you a static IP. Ask them. If it's dynamic you will need a service like NoIP.com (there are others), to make your dynamic IP available at the same connection point at all times. You can find your external IP by browsing to websites like whatismyip.com .

Now, for communication from outside your network to a certain port, you will need to open that in your router config. Also, any firewalls you may have installed on the laptop need to open that port. You may remember it from how you did it when you opened port 8333 for your node? For RPC standard is 8332, but you can (and probably should) change it to another port. Makes it a bit harder for people trying to get "in", if they happen to learn your IPs.


Re config file: Yes, I meant the bitcoin.conf file. There are more options for security like password, ssl certs, restrict to certain IP (the one of your VPS) etc. Have a look here: https://en.bitcoin.it/wiki/Running_bitcoind#Command-line_arguments  All these commands (except -conf) can be included in the conf file.


Re TCP/UDP (from the above wiki article):


From my experience things like that may need a bit of tinkering, so you might want to try this with a dummy system first.

After seeing this, I ponder if Armory is still necessary in some cases.

http://dskl.net/bitcoin/coldspend/online.html

Edit: Hm, maybe better this: http://sx.dyne.org/offlinetx.html

Do stale blocks also skew CDF calculations? I.e. the full stats show the duration on mining since the stale block. However the stale block took 20 hours to find and we got nothing from it. So shouldn't the current CDF be calculated from: (time it took to find the stale block) + (time mining on the current block)?