Ah, yeah that work out, it would just be nice to have something when to people are transferring a large sum to rule out accidentally sending to an old but active address that could accept payment. Send one payment to an address, go to send another, accidentally send second to the last. Heck I derped on an NOMP pool shortly for the BTCD mining after switching pools and making new bat files a few times. That was because for some reason my Synergy that links two of my systems was only sharing clipboard in one direction. I cut, repasted to make sure it copied correctly, switched the mouse over to the other system and pasted into the bat file. Bit later looking at pool stats, wait what? That's not the right address... I had to completely kill and restart all the synergy processes to get two way clipboard sharing working again. That was just weird, but that's exactly how freak accidents happen..
with teleport you are not sending to an address, but rather to a node, which happens to have a specific public address. They can make a new public address, but it would end up on the same destination computer.
I hope that makes sense. teleport is connecting node to node (via privacyServers) and I assign each node a public address based on what the user puts in the config file. You can send to BTCD or BTC or NXT address, all go to the same node. Also, if a person is running their privacyServer on the same computer, you could even send to the privacyServer's public address and it would also end up on that computer
So if you are sending to a pubaddr and it exists and it is responding, it is very hard for it to not be your intended destination. I prevent spoofing by requiring all packets to be signed by the linked NXT address, so some random person cant just claim a pubaddr for themselves.
Yeah, it makes sense. As I mentioned though, some people accidentally send to an address they sent to in the past instead of the one they meant to sent to, like the guy sending to the MtGox addy. People do screw up and send coin to a recently used address instead of the one they mean to, and a recently used address can very well still be alive and active. But it's all up to you, if I were ever able to send a large value teleport it would make me feel better even with checking 20 times that I have the right address in the field it won't accept if it's incorrect but a live node.
I once had a strange bug in the eBay shipping applet caused my current shipping label to print with the address the previous one should have. One person wound up getting two items, 3 the wrong item and I was very confused as I only ever box one item at a time, print the label, attach to box, close the window, box the next item open the shipping for that, print label, attach to box, close. The labels even matched the onscreen info. You would think that would leave no way to have a wrong label, but I guess not. I would really DREAD having something happen like that while if I were sending out a bunch of large payments in a row from what ever source I was getting addresses from. All good live addresses, but the system feeding me them had choked on itself.
