Localized betting system and method

1. A localized electronic betting system, the system including:

a smart contract generation module configured to:

receive a first betting statement from a first user device located within a low-latency environment;

generate a smart contract based on the first betting statement, the smart contract including a criterion to be met and configured to self-execute in response to a determination that the criterion is met, wherein, when the smart contract generation module receives the first betting statement at a first time, the smart contract generation module is configured to request a timestamp from a trusted clock of the localized electronic betting system, and to include the timestamp in the smart contract; and

transmit the generated smart contract to a local blockchain node located within the low-latency environment; and

a results engine located in the low-latency environment and configured to,

based on content received from a results source, determine information indicative of whether the criterion in the first betting statement is met;

wherein the localized electronic betting system is configured to transmit a signal to the local blockchain node for storage on a local blockchain ledger or a local copy of a blockchain ledger, the signal containing the information indicative of whether the criterion is met; and

wherein the localized electronic betting system includes a set-top box which includes the results engine and the trusted clock.

2. The system of claim 1 , wherein:

a latency of the low-latency environment is no more than 40 milliseconds (ms).

3. The system of claim 1 , wherein:

the smart contract generation module is configured to receive the first betting statement from the first user device via a high-speed network, the high-speed network including a plurality of edge computing devices connected via a high-speed connection, each of the plurality of edge computing devices defining an entry point to the high-speed network;

the smart contract generation module is configured to transmit the smart contract to the local blockchain node via a high-speed network; and

the results engine may be configured to send the signal to the local blockchain node via a high-speed network, and

the first user device, the smart contract generation module, and the results engine are all part of a same sub-network, the sub-network including a subset of devices on the high-speed network that are all configured to access the high-speed network via a same entry point.

4. The system of claim 1 , wherein:

the smart contract generation module is configured to receive a second betting statement from a second user device located within the low-latency environment;

the smart contract generation module is configured to generate a smart contract including a first criterion based on the first betting statement, and a second criterion based on the second betting statement; and

the smart contract is configured to self-execute to perform a first action in response to receipt of information that the first criterion has been met, and to perform a second action in response to receipt of information that the second criterion has been met.

5. The system of claim 1 , wherein:

the smart contract generation module is configured to store a smart contract identifier in a smart contract lookup table in association with an event identifier;

the results engine is configured to receive results as results metadata, or the results engine includes a results conversion module which is configured to convert the content received from the results source into the results metadata, the results metadata including an event identifier;

the localized electronic betting system is configured to perform a lookup in the smart contract lookup table, in order to determine whether one or more event identifiers in the results metadata corresponds to one or more smart contract identifiers in the smart contract lookup table; and

when the results metadata includes at least one event identifier that corresponds to at least one smart contract identifier in the smart contract lookup table, the results engine is configured to transmit a subset of the results metadata which corresponds to the at least one smart contract identifier in the smart contract lookup table.

6. The system of claim 1 , wherein:

the set-top box is configured to receive cable or satellite television signals, and to render the cable or satellite television signals into a format which is viewable on a television; and

the results engine is configured to receive the content from a cable or satellite television provider.

7. The system of claim 6 , wherein:

the set-top box is configured to receive a programming stream, the programming stream including metadata including an event indicator, wherein the event indicator is a unique identifier of a type of event which forms part of the programming stream;

on receipt of a bet type request from a user device, the set-top box is configured to perform a lookup in a bet type lookup table in order to determine bet types that are associated with the event indicator, and to transmit a signal to the user device, the signal including information associated with the bet types.

8. A computer-implemented method performed by a localized electronic betting system operating within a low-latency environment, the method including:

receiving a first betting statement from a user device located within the low-latency environment;

generating a smart contract based on the first betting statement, the smart contract including a criterion to be met, and configured to self-execute in response to a determination that the criterion is met;

when the first betting statement is received at a first time, requesting a timestamp from a trusted clock of the localized electronic betting system and including the timestamp in the smart contract;

transmitting the generated smart contract to a local blockchain node located within the low-latency environment;

determining, based on content received from a results source, information indicative of whether the criterion is met; and

transmitting a signal to the local blockchain node for storage on a local blockchain ledger or a local copy of a blockchain ledger, the signal containing the information indicative of whether the criterion is met,

wherein the localized electronic betting system includes a set-top box which includes a results engine and the trusted clock.

9. The method of claim 8 , wherein:

a latency of the low-latency environment is no more than 40 ms.

10. The method of claim 8 , wherein:

the first betting statement is received from the user device via a high-speed network;

the smart contract is transmitted to the local blockchain node via the high-speed network; and

the signal is transmitted to the local blockchain node via the high-speed network.

11. The method of claim 8 , further including:

receiving a second betting statement from a second user device located within the low-latency environment;

generating a smart contract including a first criterion based on the first betting statement, and a second criterion based on the second betting statement, wherein:

the smart contract is configured to self-execute to perform a first action in response to receipt of information that the first criterion has been met, and to perform a second action in response to receipt of information that the second criterion has been met.

12. The method of claim 8 , further including:

storing a smart contract identifier in a smart contract lookup table in association with an event identifier;

receiving results as results metadata from a results source, or receiving content from a results source and converting the content into the results metadata, the results metadata including an event identifier;

performing a lookup in the smart contract lookup table, and determining whether one or more event identifiers in the results metadata corresponds to one or more smart contract identifiers in the smart contract lookup table; and

when the results metadata includes at least one event identifier that corresponds to at least one smart contract identifier in the smart contract lookup table, transmitting a subset of the results metadata which corresponds to the at least one smart contract identifier in the smart contract lookup table.

13. The method of claim 8 , further including:

receiving a programming stream, the programming stream including metadata including an event indicator, wherein the event indicator is a unique identifier of a type of event which forms part of the programming stream;

on receipt of a bet type request from a user device, performing a lookup in a bet type lookup table in order to determine bet types that are associated with the event indicator; and

transmitting a signal to the user device, the signal including information associated with the bet types.

14. The method of claim 8 , further comprising:

receiving cable or satellite television signals;

rendering the cable or satellite television signals into a format which is viewable on a television; and

receiving the content from a cable or satellite television provider.