Systems and methods for watermarking time, place and identity of events

1. A method for proving an event comprising:

a) receiving, at a beacon node, a request for proving a time and location for an event, wherein the request comprises event data generated by a requesting entity;

b) creating a timestamp for the event using a clock of the beacon node, wherein the clock is synchronized to a trusted time source;

c) generating, by the beacon node, an estimated location of the requesting entity, wherein generating the estimated location comprises: (i) generating an estimated distance or location vector with respect to the requesting node based on a network latency and (ii) using a machine learning algorithm trained model to process the estimated distance or location vector to generate the estimated location;

d) generating a hash code for the timestamp and the event data; and

e) recording the hash code to a ledger at the beacon node.

2. The method of claim 1 , wherein the trusted time source comprises a grandmaster clock receiving a GNSS or GPS time signal.

3. The method of claim 1 , wherein the clock is synchronized using a PTP or NTP protocol.

4. The method of claim 1 , wherein the beacon node is located at a fixed and known location.

5. The method of claim 1 , wherein the event data includes hashed data of an event document.

6. The method of claim 1 , wherein the timestamp is generated at the time of receiving the request.

7. The method of claim 1 , wherein the requesting entity is configured to record a hashed value of the event data to a hash-chain managed by the requesting entity.

8. The method of claim 1 , wherein the beacon node is configured to audit another beacon node's time, location and identity.

9. The method of claim 1 , wherein the estimated distance or location vector is obtained using a route probing method or based on the Received Signal Strength Indication (RSSI).

10. The method of claim 1 , wherein the estimated distance or location vector is obtained from multiple of the beacon nodes that receive the request from the requesting entity.

11. The method of claim 1 , wherein the request further comprises a location data about the event.

12. The method of claim 11 , further comprising generating a probability that the location data is correct.

13. The method of claim 12 , wherein the probability is generated using a machine learning algorithm trained model.

14. The method of claim 1 , wherein the hash code is generating by combing previously hashed events data.

15. The method of claim 1 , further comprising sending, by the beacon node, the timestamp, the estimated location and the hashed event data to the requesting entity.

16. The method of claim 15 , further comprising creating, by the requesting entity, a watermark based on the timestamp, the estimated location and the hashed event data.

17. A system for proving an event comprising:

a network of one or more beacon nodes, wherein each beacon node is configured to:

a) receive a request over the network for proving a time and location for an event, wherein the request comprises event data generated by a requesting entity;

b) create a timestamp for the event using a clock of the beacon node, wherein the clock is synchronized to a trusted time source;

c) generate an estimated location of the requesting entity, wherein generating the estimated location comprises: (i) generating an estimated distance or location vector with respect to the requesting node based on a network latency and (ii) using a machine learning algorithm trained model to process the estimated distance or location vector to generate the estimated location;

d) generate a hash code for the timestamp and the event data; and

e) record the hash code to a ledger at the beacon node.

18. The system of claim 17 , wherein the event data includes hashed data of an event document.