Decentralized virtual trustless database for access control

A computer-implemented method comprising:

• defining one or more specifications for an event, wherein the event is related to a restricted access area, and wherein a valid electronic ticket enables entry into the restricted access area;
• allocating an electronic ticket for the event based on the one or more specifications;
• linking the electronic ticket for the event to a first trustless ledger transaction;
• publishing the electronic ticket for the event;
• using a second trustless ledger transaction, wherein the second trustless ledger transaction includes information from the first trustless ledger transaction:
• assigning the electronic ticket for the event to a requestor, wherein the assignment of the electronic ticket to the requestor enables the requestor to control a private access key associated with the electronic ticket, and wherein the private access key enables the requestor to transfer the electronic ticket;
• tracking a first assignment of the electronic ticket wherein the first assignment transfers the electronic ticket from the requestor to an additional requestor, wherein the first assignment of the electronic ticket includes linking the electronic ticket for the event to the second trustless ledger transaction, wherein linking the electronic ticket to the second trustless ledger transaction corresponds to tracking ownership of the electronic ticket, and wherein completing the first assignment causes the private access key to no longer enable the requestor to access the electronic ticket and the additional requestor to be enabled to transfer the electronic ticket;
• generating an access-enabling code for the electronic ticket using a private code;
• and
• granting access to the restricted access area upon presentation of the access-enabling code at an entry point of the restricted access area.

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 one or more specifications for an event, wherein the event is related to a restricted access area, and wherein a valid electronic ticket enables entry into the restricted access area;
• allocating an electronic ticket for the event based on the one or more specifications;
• linking the electronic ticket for the event to a first trustless ledger transaction;
• publishing the electronic ticket for the event;
• using a second trustless ledger transaction, wherein the second trustless ledger transaction includes information from the first trustless ledger transaction:
• assigning the electronic ticket for the event to a requestor, wherein the assignment of the electronic ticket to the requestor enables the requestor to control a private access key associated with the electronic ticket, and wherein the private access key enables the requestor to transfer the electronic ticket;
• tracking a first assignment of the electronic ticket, wherein the first assignment transfers the electronic ticket from the requestor to an additional requestor, wherein the first assignment of the electronic ticket includes linking the electronic ticket for the event to the second trustless ledger transaction, wherein linking the electronic ticket to the second trustless ledger transaction corresponds to tracking ownership of the electronic ticket, and wherein completing the first assignment causes the private access key to no longer enable the requestor to access the electronic ticket and the additional requestor to be enabled to transfer the electronic ticket;
• generating an access-enabling code for the electronic ticket using a private code;
• and
• granting access to the restricted access area upon presentation of the access- enabling code at an entry point of the restricted access area.