Let’s say there is coin based on rarity of IP address. We can call it the IP coin.
While the BTC value will be fixed in 2100+, the IP coin supply has already fixed at start due to fixed size of public IP.
Here, I can say one public IP is equal to one IP coin.
Here I define a blockchain network protocol what kinds of IPs are preciouss. Okay, so it’s basically public IP that usually in mobile network. So, not all public IP are accepted. For example, the public IP that known as company based, is not accepted. It can be verified in Whois database from https://iana.org
When I said usually in mobile networks, yes, it refers on dependencies of ISP how individu person used. Like ISP from X for person A and ISP from Y for person B.
I know that the mobile networks public IP is temporary. I also know that the mobile networks are behind NAT so they cannot receive incoming request.
That’s the question!
I want to make hypothetic blockchain that where individu user (peer) is able to collect its coin.
Here scenerio where both peers A and B are validating each other to get their coins:
- A and B are enabling webservicethat can returns their request http header since they are behinding NAT, they used tunnel.
- A has tunnel site (https://tunnel_a.com) and claims that he has IP
27...
- B still didn’t trust, B validating it with asking A to hit B and its corresponded tunnel reference (tunnel site) as body data.
- B checked the request header
Cf-Connecting-IP
and received its corresponding tunnel site which is match with A claims. - In this case, B admitted that A is indeed owning that IP. Then this information is broadcasted to blockchain.
- And same for B when it claims he has own unregistered public IP in blockchain that verified by other peers.
Here as you see, it depends on third party tunnel provider which is Cloudflare (Cf-Connecting-IP
is Cloudflared header specific to return original visitor’s IP). It’s worked, but the blockchain seems relying on specific CDN service.
I also considered STUN server which is I think neutral third party, but most ISP block STUN because of symetric NAT.
So, how to make peers validating each other while they are behind NAT?
I think, there must be something cryptography hashing at IP headers packet level.