Amazon full node and 0.12 again

[Jet Cash]

I've been looking at the peers linking to my full node again. One of them has sparked my interest - the IP is listed as 52.17.57.25:8333 via 46.233.116.251:52951
Another on is the 0.12 version of the core - this IP is 98.250.82.63:8333 (no redirection)

The first IP is registered to Amazon in Dublin Ireland, the second IP is my current connection. My questions are -

Is Amazon now accepting Bitcoin directly, if they are running a full node?

Why is traffic being redirected to port 52951 at my IP ( I'm on McDonalds free WiFi again)? All peers do this except for the 0.12 peer

What is the change in 0.12 that avoids the re-direction? Can we expect an improvement in transfer speeds as a result of this?

[achow101]

I've been looking at the peers linking to my full node again. One of them has sparked my interest - the IP is listed as 52.17.57.25:8333 via 46.233.116.251:52951
Another on is the 0.12 version of the core - this IP is 98.250.82.63:8333 (no redirection)

The first IP is registered to Amazon in Dublin Ireland, the second IP is my current connection. My questions are -

Is Amazon now accepting Bitcoin directly, if they are running a full node?

No. It is just someone running a full node on an Amazon Web services VPS

Why is traffic being redirected to port 52951 at my IP ( I'm on McDonalds free WiFi again)? All peers do this except for the 0.12 peer

I believe it is an internal thing because that is an outbound connection. The other one is probably inbound which should be why it has no redirect.

What is the change in 0.12 that avoids the re-direction? Can we expect an improvement in transfer speeds as a result of this?

AFAIK there shouldn't be anything that in 0.12 that does that. See above.

[Jet Cash]

Thanks for that explanation. I was quite hopeful there for a moment.

[ACNW]

It is helpful. Thank you

[Jet Cash]

When I first read about 0.12, I only saw a few of the changes, and they didn't seem to be of much advantage to me. I've now read a bit more about the new release, and there are some features that weren't mentioned that will be extremely useful to me. I appreciate that my situation is non-standard, so this may not apply to other users. I intend to upgrade to 0.12 as soon as I can download the stable version. The features that I liked are -

The ability to use a wallet with a pruned blockchain. I'd like to see if I can use this to install a core wallet on a Chromebook

Increased efficiency. Again this will help with operations on a chromebook.

Transaction time locks. I'm hoping that this will be useful to me as I restart my domain name trading activities.

Some providers of free WiFi cap data transfers. O2 provides the WiFi for McDonalds ( and others) in the UK, and they have a 10Gb per month cap. Running a full node, and viewing and uploading Youtube video clips could use this up. Hopefully prudent use of a pruned node will provide a small reduction indata transfers, and reduce the demands on the computer.

RBF - I'm coming round to the idea that this is a useful optional feature. Everybody seems to focus on Bitcoin as an instant (or almost instant ) exchange mechanism, but it's an international money transfer service, and, apart from face-to-face exchanges, a delay of 10 minutes, or even an hour, may not be significant. If it is, then it's always possible to reject RBF transfers. This shouldn't be a problem for merchants as long as they make it clear that their policy is to reject these transactions.

No doubt use of 0.12 will generate some changes in my attitude, but at the moment, as a newbie who is prepared to experiment, I am fairly positive.

[achow101]

Some providers of free WiFi cap data transfers. O2 provides the WiFi for McDonalds ( and others) in the UK, and they have a 10Gb per month cap. Running a full node, and viewing and uploading Youtube video clips could use this up. Hopefully prudent use of a pruned node will provide a small reduction indata transfers, and reduce the demands on the computer.

Pruning will not really affect that since pruning is only a local thing on the disk. If still downloads the entire blockchain and AFAIK it will still relay new blocks and transactions. The pruning aspect is that it just won't save the entire blockchain on the disk but rather delete part of it.

[Jet Cash]

Thanks DK

My plan is to copy the complete blockchain onto a usb stick, and then try to run a pruned core starting with that. This will avoid downloading the blockchain onto the chromebook. I'm not sure where to store the pruned chain. It would have to be on a USB stick fitted in another port, or an SD card. Given my backup problem, the SD card may not be an option. The other difficulty will come from trying to install core under chrome OS. I believe that it's a Linux variant, but it may mean I'll have to compile the code if nobody else has done it. I'm an assembler programmer, and my C is a bit sketchy, so this may be an interesting challenge for me.

I understand that the code in 0.12 may be a bit more efficient, and that would be helpful as the chromebook is a bit underpowered. If all fails, I'll still have the HP wallet, but it would be handy to have a second wallet on the chromebook.

I've just re-read your post, and I understand the point you are making. I guess I'll have to conserve bandwidth by limiting the period that I run the core. Hopefully that would cut out much of the traffic that isn't directly involved with maintaining the new blocks added to the chain.