Decentralized virtual trustless database for access control
Described are systems and techniques for leveraging a virtual distributed trustless database using access-enabling codes. The computations use private codes. Each computation includes the information from all previous computations so that a chain of computations is maintained and controlled. A central system insures that dual computations do not occur.
1. A distributed virtual trustless database access control system, comprising:
one or more processors; and
a non-transitory computer readable storage medium comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform operations including:
defining specifications for an event, wherein the event is related to a restricted access area;
allocating electronic tickets for the event based on the specifications;
linking the electronic tickets for the event to a first trustless database computation;
receiving a request for at least one electronic ticket of the electronic tickets;
assigning the at least one electronic ticket for the event to a requestor, wherein assigning the at least one electronic ticket includes linking the at least one electronic ticket for the event to a second trustless database computation, wherein linking the at least one electronic ticket to the second trustless database computation corresponds to tracking ownership of the at least one electronic ticket, wherein the second trustless database computation uses information from the first trustless database computation and a private code associated with the requestor, and wherein the private code is based on digital biometric information associated with the requestor;
generating an access-enabling code corresponding to the at least one electronic ticket, wherein the access-enabling code is generated based at least in part on the private code;
transmitting the access-enabling code to a requestor device associated with the requestor;
detecting that the requestor device is within a threshold distance from a geofence perimeter or entrance gate of the restricted access area; and
in response to detecting that the requestor device is within the threshold distance, automatically:
retrieving the access-enabling code from the requestor device;
performing a verification analysis of the access-enabling code; and
presenting an indicator identifying whether access is to be granted or limited based on a result of the verification analysis.
2. The distributed virtual trustless database access control system of claim 1 , wherein performing the verification analysis of the access-enabling code includes:
querying a data store for an entry associated with the access-enabling code;
modifying the entry to identify that the access-enabling code has been used; and
generating the result of the verification analysis indicating that the access-enabling code is verified.
3. The distributed virtual trustless database access control system of claim 2 , wherein modifying the entry includes removing the entry or associating the entry with a new status.
4. The distributed virtual trustless database access control system of claim 1 , wherein performing the verification analysis of the access-enabling code includes:
querying a data store for an entry associated with the access-enabling code; and
generating the result of the verification analysis indicating that the access-enabling code is not verified.
5. The distributed virtual trustless database access control system of claim 1 , wherein the indicator identifies the specifications for the event.
6. The distributed virtual trustless database access control system of claim 1 , wherein the operations further include:
assigning the electronic tickets for the event to a second requestor, wherein assigning the electronic tickets includes linking the electronic tickets for the event to a third trustless database computation, wherein the third trustless database computation uses information from the second trustless database computation.
7. The distributed virtual trustless database access control system of claim 6 , wherein the first trustless database computation, the second trustless database computation, and the third trustless database computation correspond to cryptocurrency transactions.
8. A method, comprising:
defining specifications for an event, wherein the event is related to a restricted access area;
allocating electronic tickets for the event based on the specification;
linking the electronic tickets for the event to a first trustless database computation;
publishing the electronic tickets for the event;
receiving a request for at least one electronic ticket of the electronic tickets;
assigning the at least one electronic ticket for the event to a requestor, wherein assigning the at least one electronic ticket includes linking the at least one electronic ticket for the event to a second trustless database computation, wherein linking the at least one electronic ticket to the second trustless database computation corresponds to tracking ownership of the at least one electronic ticket, wherein the second trustless database computation uses information from the first trustless database computation and a private code associated with the requestor, and wherein the private code is based on digital biometric information associated with the requestor;
generating an access-enabling code corresponding to the at least one electronic ticket, wherein the access-enabling code is generated based at least in part on the private code;
transmitting the access-enabling code to a requestor device associated with the requestor;
detecting that the requestor device is within a threshold distance from a geofence perimeter or entrance gate of the restricted access area; and
in response to detecting that the requestor device is within the threshold distance, automatically:
retrieving the access-enabling code from the requestor device;
performing a verification analysis of the access-enabling code; and
presenting an indicator identifying whether access is to be granted or limited based on a result of the verification analysis.
9. The method of claim 8 , wherein performing the verification analysis of the access-enabling code includes:
querying a data store for an entry associated with the access-enabling code;
modifying the entry to identify that the access-enabling code has been used; and
generating the result of the verification analysis indicating that the access-enabling code is verified.
10. The method of claim 9 , wherein modifying the entry includes removing the entry or associating the entry with a new status.
11. The method of claim 8 , wherein performing the verification analysis of the access-enabling code includes:
querying a data store for an entry associated with the access-enabling code; and
generating the result of the verification analysis indicating that the access-enabling code is not verified.
12. The method of claim 8 , wherein the indicator identifies the specifications for the event.
13. The method of claim 8 , further comprising:
assigning the at least one electronic ticket for the event to a second requestor, wherein assigning the at least one electronic ticket includes linking the at least one electronic ticket for the event to a third trustless database computation, wherein the third trustless database computation uses information from the second trustless database computation.
14. The method of claim 13 , wherein the first trustless database computation, the second trustless database computation, and the third trustless database computation correspond to cryptocurrency transactions.
15. A computer program product, comprising:
a non-transitory computer readable storage medium including instructions that, when executed by one or more processors, cause the one or more processors to perform operations including:
defining specifications for an event, wherein the event is related to a restricted access area;
allocating electronic tickets for the event based on the specification;
linking the electronic tickets for the event to a first trustless database computation;
publishing the electronic tickets for the event;
receiving a request for the at least one electronic ticket;
assigning the at least one electronic ticket for the event to a requestor, wherein assigning the at least one electronic ticket includes linking the at least one electronic ticket for the event to a second trustless database computation, wherein linking the at least one electronic ticket to the second trustless database computation corresponds to tracking ownership of the at least one electronic ticket, wherein the second trustless database computation uses information from the first trustless database computation and a private code associated with the requestor, and wherein the private code is based on digital biometric information associated with the requestor;
generating an access-enabling code corresponding to the at least one electronic ticket, wherein the access-enabling code is generated based at least in part on the private code;
transmitting the access-enabling code to a requestor device associated with the requestor;
detecting that the requestor device is within a threshold distance from a geofence perimeter or entrance gate of the restricted access area; and
in response to detecting that the requestor device is within the threshold distance, automatically:
retrieving the access-enabling code from the requestor device;
performing a verification analysis of the access-enabling code; and
presenting an indicator identifying whether access is to be granted or limited based on a result of the verification analysis.
16. The computer program product of claim 15 , wherein performing the verification analysis of the access-enabling code includes:
querying a data store for an entry associated with the access-enabling code;
modifying the entry to identify that the access-enabling code has been used; and
generating the result of the verification analysis indicating that the access-enabling code is verified.
17. The computer program product of claim 16 , wherein modifying the entry includes removing the entry or associating the entry with a new status.
18. The computer program product of claim 15 , wherein performing the verification analysis of the access-enabling code includes accessing a data store; and
querying a data store for an entry associated with the access-enabling code; and
generating the result of the verification analysis indicating that the access-enabling code is not verified.
19. The computer program product of claim 15 , wherein the indicator identifies the specifications for the event.
20. The computer program product of claim 15 , wherein the operations further include:
assigning the electronic tickets for the event to a second requestor, wherein assigning the electronic tickets includes linking the electronic tickets for the event to a third trustless database computation, wherein the third trustless database computation uses information from the second trustless database computation.