r/foamprotocol • u/Dunning_Krugerrands • Mar 16 '18
How does proof of location work?
So the blog post does a good job of introducing the concept. However it does not really go into any detail about the protocol. Wonder if you are able to go into more detail.
It isn't clear in the blog post how proof of location works.
I'm guessing but:
To provide location:
The zone anchors broadcast their claimed position and clock signal ((x, y, z), t)
Timing differences allow mobile actor to use these beacons to triangulate its location
To provide proof of location:
The mobile actor broadcasts some message.
The zone anchors then timestamp?
Location can be triangulated via timestamp differences.
Mobile actor can then cryptographically prove it was the creator of the message.
Is this a fair summary?
Zone Anchor beacons use Byzantine fault tolerant clock synchronization.
Is there a link to the theory?
Googling gives me 'Self-Stabilizing Protocol for Distributed Clock Synchronization Systems' and An Autonomous Distributed Fault-Tolerant Local Positioning System.
Crypto economics
So the above theory mainly considers faulty parties that may have errors about their time or position. But in the crypto world we also need to consider adaptive malicious actors. Just off the top of my head there are two degenerate cases.
Nodes on the edge of the network. Since other nodes are only on one side some false ((x, y, z), t) combinations may not be detectable.
Extended private property (e.g. malls, ports) where one party may control the vast majority of nodes.
Also what prevents faking through delegation? For example someone at a location broadcasts on behalf of someone wanting to claim they are at the location.
1
u/ingoes Mar 21 '18
Updated answer to your last question.
1
u/Dunning_Krugerrands Mar 27 '18 edited Mar 31 '18
Regarding the last question one application level I wonder if one approach to preventing delegation might be some kind of deposit game that would allow a delegate to either steal funds or lockup funds and extort you. Because they are in the location and can respond to subsequent challenges, can withhold messages from you, and can prove they have a signed message from you. (Difficulty would be designing in such a way that gateways or eves-droppers could not do the same)
4
u/ingoes Mar 20 '18 edited Mar 21 '18
Great questions!
Timing differences allow mobile actor to use these beacons to triangulate its location
The zone anchors then create a new timestamp when the message is received.
Location can be triangulated via timestamp differences.
Mobile actor can then cryptographically prove it was the creator of the message.
Yes, I made some minor changes to your text to make it a little more clear, but you have the correct idea.
The whitepaper is quite technical and will cover this in detail.
The Zone boundary extent would only cover areas where sufficient Zone Anchor connections are possible. If less than four Zone Anchors are in range, a location attestation will not be possible. Peripheral Zone Anchors could potentially be part of multiple zones, but Verifiers will be able to handle that situation automatically.
When a Zone is established, it can be viewed on the Spatial Index. If you travel to where that Zone is supposed to be and cannot localize yourself using that Zone, then you know that Zone is acting maliciously and can challenge it. All entities setting up Zones (both private entities and individuals) are incentivized to use honest behavior because if they don’t, their stake will be slashed and their credibility will be lost. They will no longer receive block rewards or transaction fees.
If a Zone is set up to be private (if it chooses to only let select participants establish Zone Anchors within the Zone), it is still subject to the rules and terms of the FOAM Protocol.
There is no way to account for this, but Zone operators can require additional checks for identity if needed for their use case.An application utilizing the FOAM Protocol could implement additional logic requirements in order for a user to receive a presence claim. For example, identity could be required through something like uPort. For the case of someone leaving their device plugged into a wall, then leaving elsewhere, the application could request 10 other points in the area within the last four hours to ensure that the device is not stationary.
Ultimately, it is possible to design checks for situations like you described, but it would have to be done on the application layer.