Systems, methods, and controllers to manage carbon intensity fuel production and / or tracking of carbon intensity of fuel consumption

Abstract

Embodiments of this disclosure relate to systems and methods for tracking carbon effects of a plurality of fuel transactions. A method may receive a first selected motor fuel type. A method may record a first consumption block including a first carbon intensity of the first selected motor fuel type. A method may receive a second selected motor fuel type. A method may record a second consumption block including a second carbon intensity of the second selected motor fuel type. A method may determine an overall carbon intensity of the first consumption block and the second consumption block.

Description

SYSTEMS, METHODS, AND CONTROLLERS TO MANAGE CARBON INTENSITY FUEL PRODUCTION AND / OR TRACKING OF CARBON INTENSITY OF FUEL CONSUMPTIONCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to, and the benefit of U.S. Provisional Patent Application No. 63 / 641,590, filed May 2, 2024, titled “SYSTEMS, METHODS, AND CONTROLLERS TO DETERMINE AND CONTROL AVAILABLE LOW CARBON INTENSITY FUEL,” the disclosure of which is incorporated herein by reference in its entirety.FIELD OF DISCLOSURE

[0002] Embodiments of this disclosure relate to determining and controlling availability of low carbon intensity fuel and, in particular, systems and methods to determine availability of the low carbon intensity fuel and / or increase / decrease production of the low carbon intensity fuel.BACKGROUND

[0003] Certain gases, such as carbon dioxide, carbon monoxide, nitrogen dioxide, sulfur dioxide, benzene, formaldehyde, polycyclic hydrocarbons, other particulate matter, etc., when released to the atmosphere are purported to adversely contribute to climate change and have been labeled as greenhouse gases. Consumer and industrial activity, including providing services, as well as the manufacturing, processing, and transportation of goods, contribute directly and indirectly to the atmospheric release of carbon dioxide and other greenhouse gases. To meet private, public, country, state, or global commitments / policies on climate change, much worldwide attention and focus has been placed on reducing the release of greenhouse gases to the atmosphere. To quantify the direct and indirect release of greenhouse gases attributable to consumer and / or industrial activity, the carbon intensity or emission intensity was developed as a measure of the greenhouse gases emitted per unit of activity / production. With respect to fuel and use, the carbon intensity may be defined as the lifecycle greenhouse gases emitted per unit of energy. By assessing the lifecycle greenhouse gas emissions, all greenhouse gas emissions attributable to a fuel are accounted for during the entire lifecycle of the fuel from acquisition to processing to combustion. The carbon intensity for fuels is often reported in units of grams of carbon dioxide equivalentper megajoule of energy. Because some greenhouse gases, such as methane, are considered to have a greater climatic effect than carbon dioxide, greenhouse gas emissions are reported in carbon dioxide equivalents.

[0004] To reduce and / or offset greenhouse gases produced via combustion of fuel and generated during production of the fuel itself (in other words, the carbon intensity of fuel), various processes and / or actions may occur and / or be taken. For example, utilizing solar or wind-based power during fuel production and / or blending renewable-based fuels with hydrocarbon-based fuels reduces carbon intensity of the produced fuels. However, the fuel produced may have the same or similar chemical makeup or composition as fuel produced without such carbon reductions.SUMMARY

[0005] Accordingly, Applicant has recognized a need for systems and methods to determine and / or control availability of low carbon intensity fuel. Such systems and methods may also control low carbon intensity fuel production.

[0006] The present disclosure is generally directed to systems and methods to track, manage, determine, and / or control availability of low carbon intensity fuel and / or to control low carbon intensity fuel production. Such a system may include and / or connect to a plurality of fueling sites, each fueling sites including one or more fueling stations. The system may provide indicators of availability of low carbon intensity fuel and may track consumption of such low carbon intensity fuel. The system may provide such indicators, as well as track consumption, based on data stored in a distributed ledger (for example, a blockchain or other type of distributed ledger). In embodiments, the system may prevent consumption or acquisition of low carbon intensity fuel, based on the indicators of availability. In other embodiments, rather than prevent consumption or acquisition of low carbon intensity fuel, the system may record or store an amount of over-consumption of low carbon intensity fuel or record or store each instance of fuel consumption or acquisition (for example, in the distributed ledger).

[0007] In another embodiment, the system may facilitate carbon intensity balancing across users by implementing a distributed ledger-based carbon credit tracking mechanism. For example, the system may record a first user’s fueling transaction involving a high-carbon intensity fuel at a first fueling station as a “debit” in the distributed ledger. Simultaneously or subsequently, the system may record a second user’s fueling transaction involving low- carbon intensity fuel at a second fueling station as, for example, a “credit” or a “lesserdebit” (e.g., a carbon intensity debit of lower magnitude than another higher carbon intensity debit). The distributed ledger may match these credits and / or debits based on predefined carbon intensity offset ratios or transactional equivalence. This enables a system wherein users who consume higher-carbon intensity fuels may effectively offset their emissions through the concurrent or future use of low-carbon intensity fuels by other users. Similarly, a fuel producer and / or a fuel distributor may affect their carbon emissions through concurrent or future use. At least one system described herein may optionally provide one or more of user-facing notifications, transaction histories, carbon intensity balance summaries, or other related information via user interfaces at the fueling station and / or through mobile applications, thereby enhancing user participation in carbon offset programs.

[0008] In other embodiments, the system may include and / or connect to one or more fuel production sites, such as refineries, ethanol plants, hydrogen production sites, renewable fuel refineries, bio-fuel refineries, and / or other types of fuel production sites. The system may obtain production data relating to fuel produced, including type of fuel produced, amount of fuel produced, and / or a carbon intensity rating or value, among other factors and / or data. For example, the production data may be stored in blocks of the distributed ledger. The system may store the production data in the distributed ledger. In other embodiments, each of the fuel production sites may write production data to the distributed ledger. In such embodiments, the system and / or fuel production site may record or store each instance of fuel production in the distributed ledger.

[0009] The system, utilizing the distributed ledger, may determine an amount of available fuel at one or more various carbon intensities. In other embodiments, the system may determine whether the amount of available fuel at one or more carbon intensities is at a deficit or below a selected threshold. Based on the availability, the system may cause the one or more fuel production sites to produce an amount of fuel at one or more carbon intensities. The system may generate reports based on the distributed ledger. The reports may include a total of each type of fuel amount produced and total of each type of fuel amount consumed.

[0010] In one embodiment, the systems and methods may include determining fuel availability in real-time. For example, each fueling station of a plurality of fueling stations positioned at one of a plurality of fueling sites may connect to the distributed ledger and / or a low carbon intensity fuel computing device or controller. As a user or customer selects an amount of low carbon intensity fuel at a fueling station, the fueling station (or, in someembodiments, a computing device or controller) may determine availability of the selected fuel. If the selected fuel is available, then the fueling station may initiate fueling. After the fueling operation, the fueling station may write or create a new block in the distributed ledger. If the low carbon intensity fuel is not available, then the fueling station may request production of additional low carbon intensity fuel at one or more fuel production sites. The fueling station may notify the user or customer of the lack of low carbon intensity fuel and / or prevent dispensation of the low carbon intensity fuel. The fueling station may, in an embodiment, may provide and / or indicate availability of a substitute fuel if the low carbon intensity fuel is not available. Upon production of the additional low carbon intensity fuel, the fuel production site may write or create a new block in the distributed ledger.

[0011] In one embodiment, at least one system, as described herein, may facilitate near or real-time carbon intensity balancing across multiple fueling stations using a distributed ledger system. Consider a scenario in which a first user dispenses a volume of fuel classified as having a relatively high carbon intensity at a first fueling site. The fueling station, upon completing the transaction, may generate a consumption block on the distributed ledger that records the fuel volume, carbon intensity rating, timestamp, and user identifier. Independently, a second user at a different fueling station dispenses a volume of low carbon intensity fuel. The system records this second transaction as a credit block to the ledger. The controller (or cloud-based service) periodically reconciles debit and credit entries in the ledger based on predefined carbon intensity equivalence rules — for example, 1 gallon of fuel with carbon intensity of 90 gCChe / MJ may require 1.5 gallons of fuel with CI of 50 gCChe / MJ to achieve balance. The system may also be configured to maintain carbon intensity credit balances for each user account, allowing for time-delayed or batched offsetting. These balances may be used to generate compliance reports, user incentives, or carbon intensity ratings on a per-user, per-vehicle, or per-facility basis. Optionally, the system may expose these values through user interfaces such as mobile applications, enabling participation in a voluntary or regulatory carbon trading framework. In some embodiments, the system may support pricing differentials and / or discounts at the pump, based on, for example, available carbon intensity credit balances, thus financially incentivizing the uptake of low carbon intensity fuels.

[0012] In some embodiments, fueling stations operated by independent parties may be part of one or more of an independent, a shared, or a federated distributed ledger system. This may enable carbon intensity transactions to be reconciled across one or more oforganizations, regions, or jurisdictions, facilitating market-based trading of carbon intensity credits beyond a single entity's control.

[0013] Thus, while a low carbon intensity fuel may be chemically the same as another fuel, such a system may be able to accurately determine quantities of the low carbon intensity fuel, as well as control production of low carbon intensity fuels. For example, if a specific type of fuel, defined by a selected carbon intensity, is at a deficit, the system may cause production of the fuel at one or more of the fuel production sites. Further, the system may select various options for one or more of the fuel production sites, such that fuel produced at the one or more fuel production sites meets a selected carbon intensity.

[0014] Accordingly, an embodiment of the disclosure is directed to a low carbon intensity fuel controller to determine and control available low carbon intensity fuel. The controller may comprise a plurality of first inputs / outputs connected to a plurality of fueling stations each positioned at one of a plurality of fueling sites. The controller may be configured to receive a request from a requesting fueling station of the plurality of fueling stations for a requested amount of low carbon intensity fuel. The controller may comprise a plurality of second inputs / outputs connected to a plurality of fuel production sites each of the plurality of fuel production sites configured to produce one or more of fuel or low carbon intensity fuel. The controller may be configured to determine the amount of available low carbon intensity fuel based on a distributed ledger including blocks. Each of the blocks may include data corresponding to previously produced amounts of low carbon intensity fuel and consumed amounts of low carbon intensity fuel. The controller may be configured to, in response to reception of the request from the requesting fueling station and if the requested amount of fuel is less than the amount of available low carbon intensity fuel, initiate fueling at the requesting fueling station and generate a first new block for the distributed ledger including data corresponding to the requested amount of fuel.

[0015] The controller may be further configured to, in response to reception of the request from the requesting fueling station and if the requested amount of fuel is greater than the amount of available low carbon intensity fuel, (a) initiate production of additional amounts of low carbon intensity fuel at one or more of the plurality of fuel production sites; (b) generate a second new block for the distributed ledger including data corresponding to the additional amount of low carbon intensity fuel; and (c) add the second new block to the distributed ledger. The second new block may include data corresponding to (a) an actual carbon intensity of the additional amount of low carbon intensity fuel, (b) processes utilized to reach the actual carbon intensity of the additional amount of low carbon intensity fuel,(c) a timestamp corresponding to a date of low carbon intensity fuel production, or (d) a location corresponding to production of the low carbon intensity fuel at one or more of the plurality of fuel production sites.

[0016] The first new block may include data corresponding to (a) an amount of low carbon intensity consumed, (b) a timestamp corresponding to a date of consumption of the low carbon intensity fuel, or (c) a location corresponding to location of a fueling station where consumption occurred. The fuel production sites may comprise one or more of a refinery, a blending station, or a renewable fuel production site. The controller may be configured to, prior to reception of requests from the requesting fueling station, generate the distributed ledger. Generation of the distributed ledger may comprise generation of one or more blocks corresponding to data associated with previous production of low carbon intensity fuel and, for each subsequent block of the one or more blocks, determine a hash of data contained in a preceding block and store the hash in the subsequent block. The fuel and the low carbon intensity fuel may comprise a same chemical composition.

[0017] Another embodiment of the disclosure is directed to a low carbon intensity system to determine and control low carbon intensity fuel. The system may include one or more fueling stations. Each of the one or more fueling stations may include a user interface. The user interface may allow or enable a motorist to (a) select a motor fuel type for pumping to a motorist vehicle thereby defining a selected motor fuel type and (b) obtain the selected motor fuel type. The motor fuel type may include a fuel and a low carbon intensity fuel. The system may include a computing device in communication with each of the one or more fueling stations. The computing device may be configured to receive the selected motor fuel type. The computing device may be configured to, in response to the selected motor fuel type including at least a portion of low carbon intensity fuel, (a) determine availability of low carbon intensity fuel based on data included in a distributed ledger and (b), in response to the availability of low carbon intensity fuel being greater than the selected motor fuel type, initiate pumping of the fuel from one of the one or more fueling stations to a motorist vehicle.

[0018] The user interface may be further configured to display one or more of a total local carbon reduction based on data corresponding to consumed low carbon intensity fuel in a locality from the distributed ledger, a total regional carbon reduction based on data corresponding to consumed low carbon intensity in a region from the distributed ledger, a total state carbon reduction based on data corresponding to consumed low carbon intensity in a state from the distributed ledger, or a total global regional carbon reduction based ondata corresponding to globally consumed low carbon intensity fuel from the distributed ledger. The distributed ledger may comprise a plurality of blocks. Each of the plurality of blocks may comprise a type of block. The type of block may comprise a consumption block and a production block. The consumption block may include data corresponding to low carbon intensity fuel obtained by a motorist. The production block may include data corresponding to low carbon intensity fuel produced by one or more fuel production sites. The computing device may be configured to, subsequent to initiation of pumping of the fuel from the one of the one or more fueling stations, (a) generate a new consumption block based on the selected motor fuel type and (b) add the new consumption block to the distributed ledger. The computing device may be further configured to, in response to the availability of low carbon intensity fuel being less than the selected motor fuel type, initiate low carbon intensity fuel production at one or more fuel production sites. The computing device may be configured to, in response to the availability of low carbon intensity fuel being less than the selected motor fuel type, alert the motorist of low carbon intensity fuel availability and generate a new selected motor fuel type based on availability.

[0019] Another embodiment of disclosure is directed to a method to determine and control available low carbon intensity fuel. The method may include receiving a request from one of a plurality of fueling stations for a requested amount of low carbon intensity fuel. The method may include determining an amount of available low carbon intensity fuel based on a distributed ledger including blocks. Each of the blocks may include data corresponding to previously produced amounts of low carbon intensity fuel and previously consumed amounts of low carbon intensity fuel. The method may include, in response to reception of the request from the one of the plurality of fueling stations and if the requested amount of fuel is less than the amount of available low carbon intensity fuel, initiating fuel operations at the one of the plurality of fueling stations, and generating a first new block including data corresponding to the requested amount of low carbon intensity fuel.

[0020] In another embodiment, the method may include, in response to reception of the request from the one of the plurality of fueling stations and if the requested amount of fuel is greater than the amount of available low carbon intensity fuel, initiating low carbon intensity fuel production. The method may further include generating a second new block including data corresponding to a produced amount of low carbon intensity fuel.

[0021] Another embodiment of the disclosure is directed to a method to determine and control available low carbon intensity fuel. The method may include receiving a request from one of a plurality of fueling stations for a requested amount of low carbon intensityfuel. The method may include determining an amount of available low carbon intensity fuel based on data from a low carbon intensity fuel computing device. The method may include, in response to reception of the request from the one of the plurality of fueling stations and if the requested amount of fuel is less than the amount of available low carbon intensity fuel, (a) initiating fueling at the one of the plurality of fueling stations, (b) determining an updated low carbon intensity fuel availability based on the amount of available low carbon intensity fuel, and (c) updating the amount of available low carbon intensity fuel in the low carbon intensity fuel computing device. In an embodiment, the low carbon intensity fuel computing device may track availability of low carbon intensity fuel via a distributed ledger.

[0022] In some embodiments, the techniques described herein relate to a method for tracking carbon effects of a plurality of fuel transactions, including: receiving a first selected motor fuel type, recording a first consumption block including a first carbon intensity of the first selected motor fuel type; receiving a second selected motor fuel type, recording a second consumption block including a second carbon intensity of the second selected motor fuel type; and determining an overall carbon intensity of the first consumption block and the second consumption block.

[0023] In some embodiments, the techniques described herein relate to a method, wherein one or more of the first consumption block or the second consumption block includes a volume of one or more of the first selected motor fuel type or of the second selected motor fuel type that was dispensed.

[0024] In some embodiments, the techniques described herein relate to a method, further including recording a credit in a lower carbon intensity of the first consumption block or the second consumption block.

[0025] In some embodiments, the techniques described herein relate to a method, further including: in response to receiving the first selected motor fuel type and the first selected motor fuel type, determine availability of low carbon intensity fuel based on the volume of one or more of the first selected motor fuel type or of the second selected motor fuel type that was dispensed, and one or more of: in response to the availability of low carbon intensity fuel being greater than a predetermined threshold, initiate pumping of the fuel from one or more fueling stations to a motorist vehicle, or in response to the availability of low carbon intensity fuel being less than a predetermined threshold, initiate low carbon intensity fuel production at one or more fuel production sites.

[0026] In some embodiments, the techniques described herein relate to a method, wherein one or more of the first consumption block or the second consumption block includes data corresponding to a location corresponding to production of the low carbon intensity fuel at one or more of a plurality of fuel production sites.

[0027] In some embodiments, the techniques described herein relate to a method, wherein the plurality of the fuel production sites include one or more of a refinery, a blending station, or a renewable fuel production site.

[0028] In some embodiments, the techniques described herein relate to a method, wherein recording of one or more of the first consumption block or the second consumption block is performed subsequent to initiation of pumping of the fuel from the one of the one or more fueling stations.

[0029] In some embodiments, the techniques described herein relate to a method, wherein one or more of the first consumption block or the second consumption block includes data corresponding to one or more of (a) an actual carbon intensity of an additional amount of low carbon intensity fuel, (b) processes utilized to reach the actual carbon intensity of the additional amount of low carbon intensity fuel, or (c) a timestamp corresponding to one or more of a date or a time of low carbon intensity fuel production.

[0030] In some embodiments, the techniques described herein relate to a method, wherein the first consumption block includes first account information for a first user and the second consumption block includes second account information for a second user, the method further including: based on recording a credit in a lower of (a) the first consumption block or (b) the second consumption block, associating the credit with its corresponding account in the first account information or the second account information.

[0031] In some embodiments, the techniques described herein relate to a method, wherein one or more of the first consumption block or the second consumption block includes data corresponding to one or more of (a) an amount of low carbon intensity fuel consumed, (b) a timestamp corresponding to a date of consumption of the low carbon intensity fuel, or (c) a location corresponding to location of a fueling station where consumption occurred.

[0032] In some embodiments, the techniques described herein relate to a method, wherein at least one act of recording is performed in a distributed ledger.

[0033] In some embodiments, the techniques described herein relate to a method, further including: receiving a request from one of a plurality of fueling stations for a requested amount of low carbon intensity fuel; determining an amount of available low carbon intensity fuel.

[0034] In some embodiments, the techniques described herein relate to a method, further including prior to reception of one or more requests from a plurality of fueling stations, generating the distributed ledger.

[0035] In some embodiments, the techniques described herein relate to a method, further including: in response to reception of the request from the one of the plurality of fueling stations and if the requested amount of fuel is less than the amount of available low carbon intensity fuel: initiating fuel operations at the one of the plurality of fueling stations

[0036] In some embodiments, the techniques described herein relate to a method, further including generating a first new block including data corresponding to the requested amount of low carbon intensity fuel.

[0037] In some embodiments, the techniques described herein relate to a method, wherein generating the distributed ledger includes: generation of one or more blocks corresponding to data associated with previous production of low carbon intensity fuel; and for each subsequent block of the one or more blocks: determine a hash of data contained in a preceding block, and store the hash in a subsequent block.

[0038] In some embodiments, the techniques described herein relate to a method, wherein the first selected fuel type and the second selected fuel type include a same chemical composition.

[0039] In some embodiments, the techniques described herein relate to a method to determine and control available low carbon intensity fuel, the method including: receiving a request from one of a plurality of fueling stations for a requested amount of low carbon intensity fuel; determining an amount of available low carbon intensity fuel based on a distributed ledger including blocks, each of the blocks including data corresponding to previously produced amounts of low carbon intensity fuel and previously consumed amounts of low carbon intensity fuel; and in response to reception of the request from the one of the plurality of fueling stations and if the requested amount of fuel is less than the amount of available low carbon intensity fuel: initiating fuel operations at the one of the plurality of fueling stations, and generating a first new block including data corresponding to the requested amount of low carbon intensity fuel.

[0040] In some embodiments, the techniques described herein relate to a method, further including, in response to reception of the request from the one of the plurality of fueling stations and if the requested amount of fuel is greater than the amount of available low carbon intensity fuel: initiating low carbon intensity fuel production; and generating asecond new block including data corresponding to a produced amount of low carbon intensity fuel.

[0041] In some embodiments, the techniques described herein relate to a method to determine and control available low carbon intensity fuel, the method including: receiving a request from one of a plurality of fueling stations for a requested amount of low carbon intensity fuel; determining an amount of available low carbon intensity fuel based on data from a low carbon intensity fuel computing device; and in response to reception of the request from the one of the fueling station and if the requested amount of low carbon intensity fuel is less than the amount of available low carbon intensity fuel: initiating fueling at the one of the fueling station, determining an updated low carbon intensity fuel availability based on the amount of available low carbon intensity fuel, and updating the amount of available low carbon intensity fuel in the low carbon intensity fuel computing device.

[0042] In some embodiments, the techniques described herein relate to a method, wherein the low carbon intensity fuel computing device tracks availability of low carbon intensity fuel via a distributed ledger.

[0043] In some embodiments, the techniques described herein relate to a system for managing motor fuel distribution and carbon intensity tracking, including: one or more fueling stations including a first user interface and a first controller configured to dispense the first selected motor fuel type and a second user interface and a second controller configured to dispense the second selected motor fuel type; a distributed ledger in communication with the first and second controllers; and a processor; and memory including instructions executable by the processor to perform the method.

[0044] In some embodiments, the techniques described herein relate to a system, wherein the user interface is further configured to display one or more of a total local carbon reduction based on data corresponding to consumed low carbon intensity fuel in a locality from a distributed ledger, a total regional carbon reduction based on data corresponding to consumed low carbon intensity in a region from the distributed ledger, a total state carbon reduction based on data corresponding to consumed low carbon intensity in a state from the distributed ledger, or a total global regional carbon reduction based on data corresponding to globally consumed low carbon intensity fuel from the distributed ledger.

[0045] In some embodiments, the techniques described herein relate to a low carbon intensity fuel controller to determine and control available low carbon intensity fuel, the controller including: a plurality of first inputs / outputs connected to a plurality of fuelingstations each positioned at one of a plurality of fueling sites, the controller configured to: receive a request from a requesting fueling station of the plurality of fueling stations for a requested amount of low carbon intensity fuel; and a plurality of second inputs / outputs connected to a plurality of fuel production sites each of the plurality of fuel production sites configured to produce one or more of fuel or the low carbon intensity fuel, the controller configured to: determine an amount of available low carbon intensity fuel based on a distributed ledger including blocks, each of the blocks including data corresponding to previously produced amounts of low carbon intensity fuel and consumed amounts of low carbon intensity fuel, and in response to reception of the request from the requesting fueling station and if the requested amount of fuel is less than the amount of available low carbon intensity fuel: initiate fueling at the requesting fueling station, and generate a first new block for the distributed ledger including data corresponding to the requested amount of fuel.

[0046] In some embodiments, the techniques described herein relate to a controller, wherein the controller is further configured to: in response to the reception of the request from the requesting fueling station and if the requested amount of fuel is greater than the amount of available low carbon intensity fuel: initiate production of additional amounts of low carbon intensity fuel at one or more of the plurality of the fuel production sites; generate a second new block for the distributed ledger including data corresponding to the additional amount of low carbon intensity fuel; and add the second new block to the distributed ledger.

[0047] In some embodiments, the techniques described herein relate to a controller, wherein the second new block includes data corresponding to (a) an actual carbon intensity of the additional amount of low carbon intensity fuel, (b) processes utilized to reach the actual carbon intensity of the additional amount of low carbon intensity fuel, (c) a timestamp corresponding to a date of low carbon intensity fuel production, or (d) a location corresponding to production of the low carbon intensity fuel at one or more of the plurality of fuel production sites.

[0048] In some embodiments, the techniques described herein relate to a controller, wherein the first new block includes data corresponding to (a) an amount of low carbon intensity consumed, (b) a timestamp corresponding to a date of consumption of the low carbon intensity fuel, or (c) a location corresponding to location of a fueling station where consumption occurred.

[0049] In some embodiments, the techniques described herein relate to a controller, wherein the plurality of the fuel production sites include one or more of a refinery, a blending station, or a renewable fuel production site.

[0050] In some embodiments, the techniques described herein relate to a controller, wherein the controller is configured to, prior to reception of requests from the requesting fueling station, generate the distributed ledger.

[0051] In some embodiments, the techniques described herein relate to a controller, wherein generation of the distributed ledger includes: generation of one or more blocks corresponding to data associated with previous production of low carbon intensity fuel; and for each subsequent block of the one or more blocks: determine a hash of data contained in a preceding block, and store the hash in a subsequent block.

[0052] In some embodiments, the techniques described herein relate to a controller, wherein the fuel and the low carbon intensity fuel include a same chemical composition.

[0053] Still other aspects and advantages of these embodiments and other embodiments, are discussed in detail herein. Moreover, it is to be understood that both the foregoing information and the following detailed description provide merely illustrative examples of various aspects and embodiments, and are intended to provide an overview or framework for understanding the nature and character of the claimed aspects and embodiments. Accordingly, these and other objects, along with advantages and features of the present disclosure herein disclosed, will become apparent through reference to the following description and the accompanying drawings. Furthermore, it is to be understood that the features of the various embodiments described herein are not mutually exclusive and may exist in various combinations and permutations.BRIEF DESCRIPTION OF DRAWINGS

[0054] These and other features, aspects, and advantages of the disclosure will become better understood with regard to the following descriptions, claims, and accompanying drawings. It is to be noted, however, that the drawings illustrate only several embodiments of the disclosure and, therefore, are not to be considered limiting of the scope of the disclosure.

[0055] FIG. 1A and FIG. IB are diagrams illustrating a fueling station for low carbon intensity fuel, according to one or more embodiments of the disclosure.

[0056] FIG. 2 is another diagram illustrating a fueling station for low carbon intensity fuel, according to one or more embodiments of the disclosure.

[0057] FIG. 3A, FIG. 3B, FIG. 3C, and FIG. 3D are schematic diagrams that illustrate a low carbon intensity fuel computing device configured to control low carbon intensity fuel production and add and / or update low carbon intensity fuel data in a distributed ledger, according to one or more embodiments of the disclosure.

[0058] FIG. 4 is a schematic diagram that illustrates a controller to control low carbon intensity fuel production and add and / or update low carbon intensity fuel data in a distributed ledger, according to one or more embodiments of the disclosure.

[0059] FIG. 5 is a flow diagram for controlling low carbon intensity fuel production, according to one or more embodiments of the disclosure.

[0060] FIG. 6 is another flow diagram for controlling low carbon intensity fuel production, according to one or more embodiments of the disclosure.

[0061] FIG. 7 is another flow diagram for an example method for tracking carbon effects of a plurality of fuel transactions, according to one or more embodiments of the disclosure.DETAILED DESCRIPTION

[0062] So that the manner in which the features and advantages of the embodiments of the systems and methods disclosed herein, as well as others that will become apparent, may be understood in more detail, a more particular description of embodiments of systems and methods briefly summarized above may be had by reference to the following detailed description of embodiments thereof, in which one or more are further illustrated in the appended drawings, which form a part of this specification. It is to be noted, however, that the drawings illustrate only various embodiments of the systems and methods disclosed herein and are therefore not to be considered limiting of the scope of the systems and methods disclosed herein as it may include other effective embodiments as well.

[0063] The carbon intensity parameter is typically expressed in grams of carbon dioxide equivalent per mega Joule (gCCheq / MJ); however other units of measure may be used, for example, gCCheq / bbl oil, with a standard conversion factor being used, for example, to convert between barrels of oil and the energy value thereof. Various fuels may include a carbon intensity based on the lifetime carbon dioxide emissions of the production of such fuels. In some embodiments, the combustion of such fuels may be factored in to such a carbon intensity.

[0064] Various options and / or process selections in a fuel’s lifetime (in other words, options and / or processes selected when feedstock is obtained to end-user consumption) may affect the fuel’s ultimate carbon intensity. Despite those selections and the carbonintensity of the fuel, fuels of the same type will comprise the same chemical composition. For example, gasolines having different carbon intensities comprise the same chemical composition. Thus, the present disclosure is generally directed to systems and methods for managing and / or determining availability of low carbon intensity fuel and / or to control low carbon intensity fuel production. As noted, such systems may include and / or connect to a plurality of fueling sites. Each fueling site may include one or more fueling stations. Each fueling station may offer a plurality of fuels. One of the fuels may include a low carbon intensity fuel. In other embodiments, the plurality of fuels may include fuels of varying grades of carbon intensities. The system may provide indicators of availability of low carbon intensity fuel and may track consumption of such low carbon intensity fuel, the indicators of availability determined based on data from a distributed ledger, such as a blockchain. The system may track consumption by writing new blocks to the distributed ledger. In other embodiments, the new blocks may be written to the distributed ledger by a fueling site or by a fueling station at the fueling site. In some embodiments, the system may prevent consumption or acquisition of low carbon intensity fuel, based on the indicators of availability. In other embodiments, rather than prevent consumption or acquisition of low carbon intensity fuel, the system may record or store (for example, via a new block in the distributed ledger) an amount of over-consumption of low carbon intensity fuel. In yet another embodiment, the system, fueling site, or fueling station may write a new block based on the consumption.

[0065] The system may also include and / or connect to one or more fuel production sites, such as refineries, ethanol plants, hydrogen production sites, renewable fuel refineries, biofuel refineries, and / or other types of fuel production sites. The system may obtain production data relating to fuel produced, including type of fuel produced, amount of fuel produced, and / or a carbon intensity rating or value, among other factors and / or data. For example, the production data may be stored in blocks of the distributed ledger. The system may store the production data in the distributed ledger. In other embodiments, each of the fuel production sites may write production data to the distributed ledger. In such embodiments, the system and / or fuel production site may record or store each instance of fuel production in the distributed ledger.

[0066] The system, utilizing the distributed ledger, may determine an amount of available fuel at one or more various carbon intensities. In other embodiments, the system may determine whether the amount of available fuel at one or more carbon intensities is at a deficit. Based on the availability, the system may cause the one or more fuel productionsites to produce an amount of fuel at one or more carbon intensities. The system may generate reports based on the distributed ledger. The reports may include the total amount of each type of fuel produced and the total amount of each type of fuel consumed.

[0067] As noted, the distributed ledger may be a blockchain. The blockchain may store data for each particular fuel produced and consumed. Each block may include a hash or cryptographic hash of the previous block, linking each block in the chain, as the hash value may be utilized to verify the authenticity of any of the blocks. Further, each block may be unalterable or read-only. Thus, each transaction (in other words, fuel production and consumption) may be a permanent or unalterable record.

[0068] Thus, while a low carbon intensity fuel may be chemically the same as another fuel, such a system may be able to accurately determine quantities of the low carbon intensity fuel, as well as control production of low carbon intensity fuels. For example, if a specific type of fuel, defined by a selected carbon intensity, is at a deficit, the system may cause production of the fuel at one or more of the fuel production sites. Further, the system may select various options for one or more of the fuel production sites, such that fuel produced at the one or more fuel production sites meets a selected carbon intensity. Further still, the system may determine which fuels at selected carbon intensities may be available based on combinations of fuels at different carbon intensities.

[0069] FIG. 1 A and FIG. IB are diagrams illustrating a fueling station for providing low carbon intensity fuel, according to one or more embodiments of the disclosure. Turning first to FIG. 1 A, in an embodiment, the fueling station 100 may be positioned at a fueling site. In such embodiments, the fueling site may include one or more fueling stations. The fueling site may be a comer store, gas station, terminal, marina, and / or other fueling sites. The fueling station 100 may allow or enable a user to obtain one or more fuels (for example, motor fuel). Such a fueling station 100 may include a user interface 106 or other components enabling user interaction (for example, buttons or readers, among other types of input components). The fueling station 100 may include a hose or pipe 114 connected to a fuel tank 118. The fueling station 100, in response to selection of one or more fuels by a user, may cause a pump to activate, thus causing the pump to transport fuel from the fuel tank 118 to a fuel nozzle 120 positioned at a vehicle (for example, a motorist vehicle, marine vessel, locomotive, or airplane, among other types of vehicles) or, in other embodiments, a container.

[0070] In embodiments, the user may select, via the user interface 106, a type of fuel. The fueling station 100 may include and / or dispense one or more types of fuel, such as a typicalmotor fuel, a low carbon intensity motor fuel, one or more different grades of low carbon intensity fuel, and / or one or more different octane fuels, as displayed via the user interface 106 (see 104). At 104, each of the listed fuels may include a corresponding price per gallon. Further, the user interface 106 may include buttons to increase 122 and / or decrease 124 the amount of fuel selected. Thus, the user may select one or more amounts of each type of fuel available. In another embodiment, the user may select one type of fuel. Once an amount of each of the one or more fuels or a single fuel is selected, a pump contained within the fueling station may begin to pump fuel, as indicated by fuel flow 116, from a fuel tank 118 to the fuel nozzle 120 via hose or pipe 114. During pumping of the fuel, an indicator 126 may display the amount of fuel dispensed from the fueling station. In another embodiment, the indicator 126 may illustrate the amount of a type of fuel selected and, as fuel is dispensed, the indicator 126 may count down from the amount selected to zero.

[0071] Once an amount of fuel is dispensed or prior to selection of the fuel, the user may complete the transaction digitally (for example, via a smartphone or other computing device) and / or via a dedicated card reader 112. A user may swipe a card through the card reader 112 (followed by, in an embodiment, input of a pin number or other identification number into pin pad 108), tap a card against the user interface 106 (for example, to cause a radio frequency identification chip (RFID) chip in the card to be read by a RFID scanner in the user interface), and / or insert a portion of a card including a chip into a chip reader 110.

[0072] In another embodiment, the fueling station 100 may determine availability of fuel in real-time. For example, when a selected amount of low carbon intensity fuel is requested for dispensation from the fueling station 100, the computing device or controller within the fueling station may determine whether such an amount of low carbon intensity fuel is available. Such a determination may include the computing device or controller utilizing the distributed ledger to determine a total amount of available low carbon intensity fuel and then determining whether the total amount of available low carbon intensity fuel is greater than the requested amount of low carbon intensity fuel. In another embodiment, if the total amount of available low carbon intensity fuel is not greater than the requested amount of low carbon intensity fuel, then the computing device or controller may notify the user and allow the user to select a lesser amount of low carbon intensity fuel and / or another fuel. Further, if the total amount of available low carbon intensity fuel is not greater than the requested amount of low carbon intensity fuel, the computing device or controller may directly or indirectly (for example, via a low carbon intensity fuel computing device and / ora computing device or controller positioned at the fuel production site) cause a fuel production site to produce more of a selected low carbon intensity fuel.

[0073] Turning to FIG. IB, the user interface 106, after pumping and / or during pumping of one or more fuels, may display various statistics or data regarding total carbon reduction. In another embodiment, the statistics or data may be included in a report. The report may be generated by a computing device internal or external to the fueling site or wherever the fueling station 100 may be located. The report may be in a format suitable for environmental reports to be sent to local, state, and or federal government agencies. As noted, the data may be listed or displayed via the user interface 106. The data may be displayed as a total carbon dioxide reduction for a particular user, a local carbon dioxide reduction history (for example., city, town, and / or county), a state carbon dioxide reduction history, a country-wide carbon dioxide reduction history, and / or global carbon dioxide reduction history as illustrated by screen 142 of the user interface 106.

[0074] Further, the user interface 106 may display the types of fuel selected and dispense (for example, motor fuel 1 134 and low carbon intensity (CI) fuel 138), as well as the total amount dispensed and the total cost, as illustrated in screen 136 and screen 140.

[0075] The fueling station 100 may include a computing device or controller. The computing device or controller may receive, via the user interface, the user input described above. Based on the user input, the fueling station 100 may output the specified amount of fuel. In another embodiment, the computing device or controller may record or store data indicative of the amount of fuel and type of fuel supplied or dispensed to the user. In another embodiment, the computing device or controller may connect to a supervisory controller or computing device. The computing device or controller and / or the supervisory controller or computing device may provide, write, store, or record data indicative of the amount of fuel and / or other data in a distributed ledger.

[0076] The distributed ledger may comprise machine-readable instructions configured to store blocks of records. Each block may indicate one or more of an amount of fuel dispensed, the type of fuel dispensed, a carbon intensity of fuel dispensed, a date that the fuel was dispensed, an amount of fuel produced, the type of fuel produced, a carbon intensity of fuel produced, and / or a date that the fuel was produced, among other data relating to produced or dispensed fuel. Each block in the distributed ledger may correspond to one transaction (in other words, one fuel production or one fuel dispensation). In an embodiment, each block, once written to, may retain the values written thereto. In other words, each block may be read-only or unalterable. In an embodiment, a fueling station100 (or the computing device or controller therein) or each of a plurality of fueling stations may be enabled to write to the distributed ledger. In another embodiment, each of a plurality of fueling sites, each of a plurality of fuel production sites, and / or a management or supervisory computing device or controller may write to the distributed ledger and / or may receive data from the distributed ledger.

[0077] In another embodiment, the distributed ledger may be a blockchain. In other words, each block in the chain may be connected to the preceding and subsequent blocks. Further, a subsequent block may include a hash or cryptographic hash of the previous block. The hash in a current block may be utilized to authenticate that current block. The distributed ledger may comprise another type or another algorithm.

[0078] Thus, low carbon intensity fuel may be tracked and / or availability determined via reports. Based on reports from the distributed ledger, the amount of low carbon fuel produced may be adjusted (in other words, increased or decreased). In yet another embodiment, the amount of low carbon intensity fuel available may be adjusted.

[0079] In an example, if a total amount of low carbon intensity fuel produced does not exceed the total amount of low carbon intensity fuel supplied, then the user interface 106 may not display low carbon intensity fuel for consumption. In another embodiment, if the total amount of low carbon intensity fuel produced does not exceed the total amount of low carbon intensity fuel supplied, the user interface 106 may continue to display the low carbon intensity fuel, but prompt the supervisory computing device or controller to overproduce low carbon intensity fuel. In yet another embodiment, the user interface 106 may offer one or more grades of low carbon intensity fuel. In such embodiments, each grade may correspond to different fuels that each exhibit a selected carbon intensity. As noted, such fuels may be chemically the same, but include or correspond to different carbon intensities. Thus, to distinguish between such fuels, the fueling station 100 may utilize data stored in the distributed ledger to determine how much of various types of fuel are available and, based on that availability, determine how much of each grade of fuel may be offered to a user. In yet another embodiment, the user interface 106 may display an adjustable carbon intensity fuel. In such an embodiment, a user may select a desired carbon intensity. As the user alters the carbon intensity, the user interface 106 may adjust the cost of such a fuel.

[0080] In embodiments, the user interface 106 may be a display embedded in the fueling station 100. The user interface 106 may be interactive or may be a touch screen. In other words, a user may engage (e.g., touch with a finger, tap with a stylus, dwell on visually toselect using an eye tracking mechanism) one or more of the various options displayed on the user interface 106 to select fuels, among other interactions.

[0081] As noted, the fueling station 100 may include a computing device or controller. The computing device or controller may connect to the user interface 106. The computing device or controller may be configured to continuously, substantially continuously, or periodically update fuel availability. In other words, in some embodiments, the types of fuel available may actively change over time based on user consumption and / or fuel production.

[0082] As used herein, a “computing device” refers to any one or all of programmable logic controllers (PLCs), programmable automation controllers (PACs), industrial computers, desktop computers, personal data assistants (PDAs), laptop computers, tablet computers, smart books, palm-top computers, personal computers, smartphones, wearable devices (such as headsets, smartwatches, or the like), a server, and similar electronic devices equipped with at least a processor and any other physical components necessarily to perform the various operations described herein. Devices such as smartphones, laptop computers, tablet computers, and wearable devices are generally collectively referred to as mobile devices.

[0083] As used herein, a “server” refers to any computing device capable of functioning as a server, such as a master exchange server, web server, mail server, document server, or any other type of server. A server may be a dedicated computing device or a server module (e.g., an application) hosted by a computing device that causes the computing device to operate as a server. A server module (e.g., server application) may be a full function server module, or a light or secondary server module (e.g., light or secondary server application) that is configured to provide synchronization services among the dynamic databases on computing devices.

[0084] In some embodiments, the user interface 104 displayed at a fueling station may be associated with a first user (e.g., “User A”) selecting from multiple motor fuel options (e.g., fuel 1, fuel 2), each having a different associated carbon intensity. The user interface 104 may display the carbon intensity rating and associated price per volume unit for each fuel type, as described above. In a multi-user embodiment, the system may record User A’s transaction at that fueling station 100 — particularly if a higher carbon intensity motor fuel is selected — as a consumption block on a distributed ledger. At the same or at a separate fueling station (e.g., a geographically or temporally distant fueling station), a second user (“User B”) may dispense a motor fuel with lower carbon intensity. The fueling interfaceused by User B may be similar to the user interface 104, a simplified version thereof, or a conventional fueling interface without carbon intensity data displayed.

[0085] If a lower carbon intensity fuel is selected by User B, the system may generate a credit block corresponding to that fuel usage. These blocks may be reconciled by the system using predefined carbon intensity offset ratios to offset User A’s higher carbon intensity fuel usage with User B’s lower carbon intensity fuel selection. In some embodiments, the carbon reduction contribution attributable to each user may optionally be displayed via user interface 104, recorded in an associated user profile, stored in the ledger as part of a compliance or incentive framework, or combinations thereof. In embodiments where User B is provided the carbon intensity of the fuel, User B may be provided a monetary discount for selecting a lower carbon intensity from the cost of User A’s higher carbon intensity selection. In embodiments where User B is not provided the carbon intensity at the time of sale, User B may be later credited an amount based on the lower intensity selection. In some embodiments, the value of the transaction may be provided to or split between the fueling station 100, User A, User B, other users, other fueling stations, or combinations thereof. In some embodiments, multiple users and / or multiple fueling stations (e.g., fueling stations 100) may be involved.

[0086] FIG. 2 is another diagram illustrating a fueling station for low carbon intensity fuel, according to one or more embodiments of the disclosure. In FIG. 2, rather than an interactive display, the user interface 224 may include a plurality of buttons 216 and a screen. In embodiments, the screen may display a series of prompts corresponding to one or more of the buttons. For example, the screen may display a prompt after a user swipes a credit card at card reader 112, such as “is this a debit card?” 218 to which a user may select yes 220 or no 222 via the corresponding buttons 216. Other prompts may be displayed, for example a prompt indicating a next step (such as, insert fuel nozzle 120 into vehicle and / or submit payment, among other prompts) or a prompt indicating the amount of fuel being dispensed.

[0087] In another embodiment, the fueling station 200 may include other buttons and / or displays enabling a user to select a type of fuel. For example, user interface component 202 may be a screen, static display, and / or button that indicates a type of fuel. Further, user interface component 202 may be a screen, static display, and / or button that indicates a cost of the corresponding type of fuel.

[0088] In a multi-user scenario, the user interface component 202 may be used to associate a fueling transaction with a specific user identifier, loyalty account, or anonymous token.For instance, if User A selects a motor fuel with a relatively high carbon intensity and completes the transaction using the user interface component 202, the system may log the transaction as a consumption block on the distributed ledger. A separate fueling transaction conducted by User B at a different station, possibly utilizing the same type of user interface component 202 or a simplified interface without carbon intensity information, may involve selection of a lower carbon intensity motor fuel. This transaction may be recorded as a credit block on the distributed ledger. The system may then reconcile these transactions, offsetting the carbon intensity impact of User A’s consumption with the lower carbon intensity fuel usage by User B, using stored equivalency rules and ledger logic.

[0089] FIG. 3A, FIG. 3B, FIG. 3C, and FIG. 3D are schematic diagrams that illustrate a low carbon intensity fuel computing device configured to control low carbon intensity fuel production and add and / or update low carbon intensity fuel data in a distributed ledger, according to one or more embodiments of the disclosure. Turning first to FIG. 3A, the system 300 may include one or more fueling sites 304 A, 304B, and up to 304N, one or more fuel production sites 310A, 310B, and up to 310N, a distributed ledger 320, and / or a low carbon intensity fuel computing device 302. Each of the fueling sites 304A, 304B, and up to 304N may include one or more fueling stations (for example, fueling station 100 and fueling station 200, among other types of fueling stations for other types of vehicles) which may be used by multiple users. Further, each fueling site 304A, 304B, and up to 304N may include a computing device 308 or a controller. Each of the fueling sites 304 A, 304B, and up to 304N may connect to the low carbon intensity fuel computing device 302 and the distributed ledger 320. The computing device 308 of each of the fueling sites 304A, 304B, and up to 304N may control each of the fueling stations positioned at the corresponding fueling site. The computing device 308, for example, may record to a block and / or create or generate new blocks based on fuel consumption at the corresponding fueling site. For example, if a user obtains an amount of fuel, that fueling station may send data indicative of the amount of fuel consumed, the type of fuel consumed, the carbon intensity of the fuel consumed, location of where the fuel was dispensed, and / or a timestamp for when the fuel was consumed, among other factors to the computing device 308, to the distributed ledger 320, and / or to the low carbon intensity fuel computing device 302. In such embodiments, the fueling station, computing device 308, or low carbon intensity fuel computing device 302 may record the data in the distributed ledger 320. In another embodiment, writes made to the distributed ledger 320 may include a hash or cryptographic hash of a previously entered block (for example, previously entered by any other computing device orcontroller). The hash or cryptographic hash may be based on a pre-defined algorithm specified by the distributed ledger 320 and may be utilized to authenticate blocks. As noted, blocks within the distributed ledger 320 may be read-only. In another embodiment, the computing device 308 may receive or obtain data from the distributed ledger and / or the low carbon intensity fuel computing device 302 indicative of fuel availability.

[0090] As noted, the system 300 may include one or more fuel production sites 310A, 310B, and up to 310N. The fuel production sites 310A, 310B, and up to 310N may include refineries, ethanol plants, hydrogen production sites, renewable fuel refineries, bio-fuel refineries, and / or other types of fuel production sites. Each of the fuel production sites 310A, 310B, and up to 310N may be configured to produce fuel. One or more of the fuel production sites 310A, 310B, and up to 310N may be configured to produce or may be capable of producing low carbon intensity fuel. Each of the fuel production sites 310A, 310B, and up to 310N may include a controller 312. The controller 312 may control production of fuel at the corresponding fuel production site, as well as monitor various processes within the corresponding fuel production site. The controller 312 may also be connected to the low carbon intensity fuel computing device 302 and / or the distributed ledger 320. The controller 312 may write to the distributed ledger 320 or create new blocks within the distributed ledger 320 that includes data indicative of fuel produced, type of fuel produced, carbon intensity of the fuel produced, processes and / or selections used to reduce carbon intensity, a timestamp of when the fuel was produced, and / or location of where the fuel was produced, among other factors. The controller 312 may receive data or next actions from the low carbon intensity fuel computing device 302 and / or the distributed ledger 320. The data or next actions received may include data indicating what type of fuels to produce at which fuel production site and / or which processes and / or options to select to meet a selected carbon intensity at one or more of the fuel production sites. Such processes and / or options may include a selection of one or more transportation options for feedstock and / or fuel, a selection of one or more feedstocks used to produce the fuel, various internal processes within the fuel production site (such as, waste heat recovery, carbon capture and sequestration, use of one or more renewable fuels or energy, and / or other process improvements), and / or a selection of other fuels to blend with an end-product fuel.

[0091] The low carbon intensity fuel computing device 302 may comprise a controller. The low carbon intensity fuel computing device 302 may write to or create new blocks in the distributed ledger 320. The low carbon intensity fuel computing device 302 may receive the data to write from the one or more fueling sites 304A, 304B, and up to 304N and / or theone or more fuel production sites 310A, 31 OB, and up to 3 ION. In another embodiment, the low carbon intensity fuel computing device 302 may monitor totals included in the distributed ledger 320. For example, the low carbon intensity fuel computing device 302 may determine the total amount of low carbon intensity fuel available and / or the total amount of varying grades of low carbon intensity fuel available. Further, the low carbon intensity fuel computing device 302 may determine the total amount of low carbon intensity fuel consumed and / or the total amount of varying grades of low carbon intensity fuel consumed. The low carbon intensity fuel computing device 302, using the data stored in the distributed ledger 320, may determine which grade of low carbon intensity fuel to continue to offer as available at each of the fueling sites 304 A, 304B, and up to 304N and / or which grade of low carbon intensity fuel to produce at each of the fuel production sites 310A, 310B, and up to 310N.

[0092] Turning to FIG. 3B, the distributed ledger 320 may connect to one or more sources 326 (for example, the low carbon intensity fuel computing device 302, each of the fueling sites 304A, 304B, and up to 304N, and / or each of the fuel production sites 310A, 310B, and up to 310N). Each of the one or more sources 326 may be configured to create new blocks 328 or write new blocks 328 within the distributed ledger 320. Once a block 328 is generated and written to, the blocks 328 may not be written to again. In other words, each block 328 may become an unalterable record. Further, the sources 326 may read from the distributed ledger 320. In another embodiment, the distributed ledger 320 may be configured to generate reports based on the data stored therein. The one or more sources 326 may select various options for a report. For example, the one or more sources 326 may request a report that includes fuel production over a selected timeframe and / or fuel consumption for a selected type of fuel at a selected carbon intensity or carbon intensities, among other various reports based on the data stored within the distributed ledger 320.

[0093] In an embodiment, and as illustrated in FIG. 3C, the low carbon intensity fuel computing device 302 may include the distributed ledger. In such embodiments, each of the fueling sites 304 A, 304B, and up to 304N, and / or each of the fuel production sites 310A, 310B, and up to 310N may provide data for the distributed ledger 320 to the low carbon intensity fuel computing device 302.

[0094] In another embodiment, and as illustrated in FIG. 3D, the low carbon intensity fuel computing device 302 may include a processor 314, a non-transitory machine-readable storage medium (such as memory 316) for storing instructions, and / or a communications circuitry 318 configured to enable signal communication between the low carbon intensityfuel computing device 302 and the distributed ledger 320, as well as each of the fueling sites 304A, 304B, and up to 304N, and / or each of the fuel production sites 310A, 310B, and up to 3 ION. As used herein, a “non-transitory machine-readable storage medium” may be any electronic, magnetic, optical, or other physical storage apparatus to contain or store information such as executable instructions, data, and the like. For example, any machine- readable storage medium described herein may be any of random access memory (RAM), volatile memory, non-volatile memory, flash memory, a storage drive (e.g., hard drive), a solid state drive, any type of storage disc, and the like, or a combination thereof. As noted, the memory may store or include instructions executable by the processor. As used herein, a “processor” may include, for example one processor or multiple processors included in a single device or distributed across multiple computing devices. The processor may be at least one of a central processing unit (CPU), a semiconductor-based microprocessor, a graphics processing unit (GPU), a field-programmable gate array (FPGA) to retrieve and execute instructions, a real time processor (RTP), application specific integrated circuit (ASIC), other electronic circuitry suitable for the retrieval and execution instructions stored on a machine-readable storage medium, or a combination thereof.

[0095] As used herein, “signal communication” refers to electric communication such as hard wiring two components together or wireless communication, as understood by those skilled in the art. For example, wireless communication may be Wi-Fi®, Bluetooth®, ZigBee, or forms of near field communications. In addition, signal communication may include one or more intermediate controllers or relays disposed between elements that are in signal communication with one another

[0096] The low carbon intensity fuel computing device 302 may include various instructions, such as fueling availability instructions 322, fueling production instructions 324, and / or ledger data transmission and / or retrieval instructions 330. Fueling availability instructions 322 may, when executed by the processor 314, determine whether a selected amount of fuel is available based on data stored within the distributed ledger 320. In such an embodiment, when the fueling availability instructions 322 are executed, the ledger data transmission / retrieval instructions 330 may be executed. The ledger data transmission / retrieval instructions 330 may obtain data specified by the fueling availability instructions 322. Using such data the fueling availability instructions 322 may prompt one or more of the fueling sites 304A, 304B, and up to 304N to offer one or more selected fuels for use. Such instructions may be executed frequently, as fuel may be consumed at a high frequency. For example, millions of gallons of gasoline are consumed on a day-to-day basisin just the United States for motorist vehicles. Such a statistic does not take into account the amount of fuel utilized in various other industries over the course of a day. As such, the fueling availability instructions 322 may be executed continuously, substantially continuously, and / or at a high frequency (for example, a plurality of times per day).

[0097] The fuel production instructions 324 may, when executed, determine an amount of fuel produced over a selected time. Execution of the fuel production instructions 324 may cause execution of the ledger data transmission / retrieval instructions 330. The fuel production instructions 324 may cause retrieval of data that indicates an amount of a type of fuel produced. Similar to fuel consumed, millions of barrels of fuel may be produced over a day. Thus, the fuel production instructions 324 may be executed at specified intervals.

[0098] FIG. 4 is a schematic diagram that illustrates a controller to control low carbon intensity fuel production and add and / or update low carbon intensity fuel data in a distributed ledger, according to one or more embodiments of the disclosure. The controller 402 may include one or more controllers. Further, the controller 402 may be in signal communication with various other controllers or computing devices. The controller 402 may be considered a supervisory controller. In another example, a supervisory controller may include the functionality of controller 402 and may control or manage other proximate and / or remote controllers. The controller 402 may include a non-transitory machine- readable storage medium (such as memory 406) and a processor 404. The memory 406 may include instructions.

[0099] The memory 406 may include instruction 408 to determine available low carbon intensity fuel. The instructions may be configured to determine a current total amount of low carbon intensity fuel consumed, as well as determine a total low carbon intensity fuel produced. The time frame for such determinations may include total amounts over a selected period or overall (in other words, the total amounts consumed / produced since tracking began). Once, such values have been determined, the instructions 408 may determine a currently available amount of low carbon intensity fuel based on the difference between the total low carbon intensity fuel produced and current total amount of low carbon intensity fuel consumed.

[0100] The memory 406 may include instructions 412 to initiate fueling requests. In such embodiments, the execution of instructions 412 may cause, in response to the low carbon intensity fuel being available, the selected low carbon intensity fuel to be offered at one or more fueling stations 420A, 420B, and up to 420N at one or more fueling sites. The memorymay include instructions 414 to initiate fuel production. In such embodiments, the controller 402 may cause, in response to a deficit of low carbon intensity fuel, one or more fuel production sites 422A, 422B, and up to 422N to produce the low carbon intensity fuel.

[0101] The memory 406 may include instructions 416 to update the distributed ledger. In such embodiments, the instructions 416 may cause information received to be written to a new block in a distributed ledger. Finally, the controller 402 may include or connect to a user interface 418. A user may obtain one or more reports relating to information stored therein.

[0102] In a multi-user implementation, the system may utilize additional fueling station controllers (e.g., controller 420 A), each configured to detect fuel type selection, determine associated carbon intensity values, and write corresponding transaction blocks to the distributed ledger 422A. For example, User A may dispense a higher carbon intensity motor fuel at a first fueling site, prompting controller 420A to generate a consumption block. At a different fueling station, another controller (not shown) may detect dispensing of a lower carbon intensity motor fuel by User B and generate a corresponding credit block. The system may include logic to reconcile such blocks, determine net user-level carbon intensity impacts, and update user records accordingly. These reconciliations may be stored within the ledger and optionally made available to downstream applications such as compliance monitoring, incentives, or carbon offset tokenization.

[0103] FIG. 5 is a flow diagram for controlling low carbon intensity fuel production, according to one or more embodiments of the disclosure. The method 500 is detailed with reference to the controller 402 of FIG. 4. Unless otherwise specified, the actions of method 500 may be completed within the controller 402. Specifically, method 500 may be included in one or more programs, protocols, or instructions loaded into the memory of the controller 402 and executed on the processor or one or more processors of the controller 402. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described blocks may be combined in any order and / or in parallel to implement the methods.

[0104] At block 502, a request to receive or dispense a low carbon intensity fuel may be received at a fueling station. For example, a user may attempt to obtain low carbon intensity at a fueling station. At block 504, a controller 402 included in or connected to the fueling station may determine whether low carbon intensity fuel is available in real-time. The controller 402 may determine an amount of low carbon intensity fuel available based on the amount of low carbon intensity fuel produced and consumed, as indicated in thedistributed ledger. In another embodiment, fuel dispensation may occur, a new block recorded in the distributed ledger, and then availability may be updated.

[0105] At block 506, the controller 402 may determine whether the amount available is greater than the amount requested. If the amount available is greater (based on the requested amount of fuel), then the controller, at block 508, may initiate a fuel operation (in other words, the fueling station may begin dispensing the selected fuel). At block 510, the controller 402 may generate or create a new block with the amount of fuel dispensed or requested.

[0106] At block 512, if no low carbon intensity fuel is available, the controller 402 may alert a motorist or user that such fuel is not available. At block 514, the controller 402 may prompt a fuel production site to produce more of the low carbon intensity fuel. At block 516, the controller 402 or a controller positioned at the fuel production site may cause production of the low carbon intensity fuel. Finally, at block 518, the controller may generate or create a new block with the amount of fuel produced.

[0107] In the embodiment of FIG. 5, the illustrated logic blocks may be further adapted to accommodate reconciliation of fuel transactions between two or more users. For instance, when a low carbon intensity motor fuel is dispensed and block 502 triggers generation of a new block on the distributed ledger, the system may evaluate whether that transaction can at least partially offset another previously or subsequently logged consumption block associated with a higher carbon intensity motor fuel. The logic represented by block 504 may include a matching function that assesses available credit blocks and applies them to outstanding or newly generated consumption blocks based on one or more of fuel type, volume, predefined equivalency factors, or combinations thereof. The outcome of such reconciliation may influence whether alerts are issued (e.g., block 506), or whether a fueling operation may proceed and / or trigger generation of further production requests.

[0108] FIG. 6 is a flow diagram for controlling low carbon intensity fuel production, according to one or more embodiments of the disclosure. The method 600 is detailed with reference to the controller 402 of FIG. 4. Unless otherwise specified, the actions of method 600 may be completed within the controller 402. Specifically, method 600 may be included in one or more programs, protocols, or instructions loaded into the memory of the controller 402 and executed on the processor or one or more processors of the controller 402. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described blocks may be combined in any order and / or in parallel to implement the methods

[0109] At block 602, the controller 402 may determine whether fuel has been produced. In such embodiments, the controller 402 may determine whether the fuel produced is one or more different types of fuel, such as a low carbon intensity fuel, one or more grades of low carbon intensity fuel, and / or other types of fuel. In embodiments, the controller 402 may monitor data from computing devices and / or controllers corresponding to one or more fuel production sites for produced fuel.

[0110] Upon determination that an amount of fuel has been produced, the controller 402, at block 604, may generate a new block in a distributed ledger to indicate the amount of fuel that has been produced, as well as the type of fuel, the date and time the fuel was produced, and / or other data (such as data related to processes and / or other selections that were utilized to reduce carbon intensity).[OHl] At block 606, the controller 402 may determine whether fuel has been consumed. In such embodiments, the controller 402 may determine the type of fuel consumed, such as a low carbon intensity fuel, one or more grades of low carbon intensity fuel, and / or other types of fuel. In embodiments, the controller 402 may monitor data from computing devices and / or controllers corresponding to one or more fueling sites and / or fueling stations for fuel consumed.

[0112] Upon determination that an amount of fuel has been consumed, the controller 402, at block 604, may generate a new block in the distributed ledger to indicate the amount of fuel that has been consumed, as well as the type of fuel and / or the date and time the fuel was consumed.

[0113] At block 610, the controller 402 may determine a total amount of fuel produced. The controller 402 may determine such an amount based on the each block including fuel production data in the distributed ledger. At block 612, the controller 402 may determine a total amount of fuel consumed. The controller 402 may determine such an amount based on the each block including fuel consumption data in the distributed ledger.

[0114] At block 614, the controller 402 may determine whether the total amount of fuel produced is about equal to the total amount of fuel consumed or, in other embodiments, greater than the total amount of fuel consumed. At block 616, if the total amount of fuel produced is about equal to or greater than the total amount of fuel consumed, then the controller 402 may adjust the total amount of fuel produced. In an embodiment, the controller 402 may transmit signals to one or more of the fuel production sites to indicate an amount of a selected fuel to produce. In other embodiments, if the total amount of fuel produced is about equal to or greater than the total amount of fuel consumed, then thecontroller 402 may prevent further consumption or dispensation of the fuel at each of the one or more fueling stations or fueling sites, until additional fuel is available.

[0115] FIG. 7 is a flowchart of an example method for tracking carbon effects of a plurality of fuel transactions. At block 710, a first selected motor fuel type is received. At block 720, a first consumption block is recorded. The first consumption block includes a first carbon intensity of the first selected motor fuel type. At block 730, a second selected motor fuel type is received. At block 740, a second consumption block is recorded. The second consumption block includes a second carbon intensity of the second selected motor fuel type. At block 750, an overall carbon intensity of the first consumption block and the second consumption block is determined.

[0116] In some embodiments, one or more of the first consumption block or the second consumption block includes a volume of one or more of the first selected motor fuel type or of the second selected motor fuel type that was dispensed. A credit, in some embodiments, is recorded in a lower carbon intensity of the first consumption block or the second consumption block.

[0117] In some embodiments, in response to receiving the first selected motor fuel type and the first selected motor fuel type, determine availability of low carbon intensity fuel based on the volume of one or more of the first selected motor fuel type or of the second selected motor fuel type that was dispensed, and one or more of: in response to the availability of low carbon intensity fuel being greater than a predetermined threshold, initiate pumping of the fuel from one or more fueling stations to a motorist vehicle, or in response to the availability of low carbon intensity fuel being less than a predetermined threshold, initiate low carbon intensity fuel production at one or more fuel production sites.

[0118] In some embodiments, one or more of the first consumption block or the second consumption block includes data corresponding to a location corresponding to production of the low carbon intensity fuel at one or more of a plurality of fuel production sites.

[0119] In some embodiments, the plurality of the fuel production sites include one or more of a refinery, a blending station, or a renewable fuel production site.

[0120] In some embodiments, recording of one or more of the first consumption block or the second consumption block is performed subsequent to initiation of pumping of the fuel from the one of the one or more fueling stations.

[0121] In some embodiments, one or more of the first consumption block or the second consumption block includes a volume of one or more of the first selected motor fuel type or of the second selected motor fuel type that was dispensed.

[0122] In some embodiments, the techniques described herein relate to a method, further including recording a credit in a lower carbon intensity of the first consumption block or the second consumption block.

[0123] In some embodiments, in response to receiving the first selected motor fuel type and the first selected motor fuel type, determine availability of low carbon intensity fuel based on the volume of one or more of the first selected motor fuel type or of the second selected motor fuel type that was dispensed, and one or more of: in response to the availability of low carbon intensity fuel being greater than a predetermined threshold, initiate pumping of the fuel from one or more fueling stations to a motorist vehicle, or in response to the availability of low carbon intensity fuel being less than a predetermined threshold, initiate low carbon intensity fuel production at one or more fuel production sites.

[0124] In some embodiments, one or more of the first consumption block or the second consumption block includes data corresponding to a location corresponding to production of the low carbon intensity fuel at one or more of a plurality of fuel production sites.

[0125] In some embodiments, the plurality of the fuel production sites include one or more of a refinery, a blending station, or a renewable fuel production site.

[0126] In some embodiments, recording of one or more of the first consumption block or the second consumption block is performed subsequent to initiation of pumping of the fuel from the one of the one or more fueling stations.

[0127] In some embodiments, one or more of the first consumption block or the second consumption block includes data corresponding to one or more of (a) an actual carbon intensity of an additional amount of low carbon intensity fuel, (b) processes utilized to reach the actual carbon intensity of the additional amount of low carbon intensity fuel, or (c) a timestamp corresponding to one or more of a date or a time of low carbon intensity fuel production.

[0128] In some embodiments, the first consumption block includes first account information for a first user and the second consumption block includes second account information for a second user, the method further including: based on recording a credit in a lower of (a) the first consumption block or (b) the second consumption block, associating the credit with its corresponding account in the first account information or the second account information.

[0129] In some embodiments, one or more of the first consumption block or the second consumption block includes data corresponding to one or more of (a) an amount of low carbon intensity fuel consumed, (b) a timestamp corresponding to a date of consumptionof the low carbon intensity fuel, or (c) a location corresponding to location of a fueling station where consumption occurred.

[0130] In some embodiments, at least one act of recording is performed in a distributed ledger.

[0131] In some embodiments, a request is received from one of a plurality of fueling stations for a requested amount of low carbon intensity fuel; determining an amount of available low carbon intensity fuel.

[0132] In some embodiments, prior to reception of one or more requests from a plurality of fueling stations, the distributed ledger is generated.

[0133] In some embodiments, in response to reception of the request from the one of the plurality of fueling stations and if the requested amount of fuel is less than the amount of available low carbon intensity fuel: fuel operations are initiated at the one of the plurality of fueling stations.

[0134] In some embodiments, a first new block including data corresponding to the requested amount of low carbon intensity fuel is generated.

[0135] In some embodiments, generating the distributed ledger includes: generation of one or more blocks corresponding to data associated with previous production of low carbon intensity fuel; and for each subsequent block of the one or more blocks: determine a hash of data contained in a preceding block, and store the hash in a subsequent block.

[0136] In some embodiments, the first selected fuel type and the second selected fuel type include a same chemical composition.

[0137] In the drawings and specification, several embodiments of systems and methods to provide scalable greenhouse gas capture have been disclosed, and although specific terms are employed, the terms are used in a descriptive sense only and not for purposes of limitation. Embodiments of systems and methods have been described in considerable detail with specific reference to the illustrated embodiments. However, it will be apparent that various modifications and changes may be made within the spirit and scope of the embodiments of systems and methods as described in the foregoing specification, and such modifications and changes are to be considered equivalents and part of this disclosure.

Claims

CLAIMSWHAT IS CLAIMED IS:

1. A method for tracking carbon effects of a plurality of fuel transactions, comprising: receiving a first selected motor fuel type; recording a first consumption block including a first carbon intensity of the first selected motor fuel type; receiving a second selected motor fuel type; recording a second consumption block including a second carbon intensity of the second selected motor fuel type; and determining an overall carbon intensity of the first consumption block and the second consumption block.

2. The method of claim 1, wherein one or more of the first consumption block or the second consumption block includes a volume of one or more of the first selected motor fuel type or of the second selected motor fuel type that was dispensed.

3. The method of any of claims 1 or 2, further comprising recording a credit in a lower carbon intensity of the first consumption block or the second consumption block.

4. The method of claims 2 or 3, further comprising: in response to receiving the first selected motor fuel type and the first selected motor fuel type, determine availability of low carbon intensity fuel based on the volume of one or more of the first selected motor fuel type or of the second selected motor fuel type that was dispensed, and one or more of: in response to the availability of low carbon intensity fuel being greater than a predetermined threshold, initiate pumping of the fuel from one or more fueling stations to a motorist vehicle, or in response to the availability of low carbon intensity fuel being less than a predetermined threshold, initiate low carbon intensity fuel production at one or more fuel production sites.

5. The method of claim 4, wherein one or more of the first consumption block or the second consumption block includes data corresponding to a location corresponding toproduction of the low carbon intensity fuel at one or more of a plurality of fuel production sites.

6. The method of any of claims 4 or 5, wherein the plurality of the fuel production sites comprise one or more of a refinery, a blending station, or a renewable fuel production site.

7. The method of any of claims 4-6, wherein recording of one or more of the first consumption block or the second consumption block is performed subsequent to initiation of pumping of the fuel from the one of the one or more fueling stations.

8. The method of any of claims 1-7, wherein one or more of the first consumption block or the second consumption block includes data corresponding to one or more of (a) an actual carbon intensity of an additional amount of low carbon intensity fuel, (b) processes utilized to reach the actual carbon intensity of the additional amount of low carbon intensity fuel, or (c) a timestamp corresponding to one or more of a date or a time of low carbon intensity fuel production.

9. The method of any of claims 1-8, wherein the first consumption block includes first account information for a first user and the second consumption block includes second account information for a second user, the method further comprising: based on recording a credit in a lower of (a) the first consumption block or (b) the second consumption block, associating the credit with its corresponding account in the first account information or the second account information.

10. The method of any of claims 1-7, wherein one or more of the first consumption block or the second consumption block includes data corresponding to one or more of (a) an amount of low carbon intensity fuel consumed, (b) a timestamp corresponding to a date of consumption of the low carbon intensity fuel, or (c) a location corresponding to location of a fueling station where consumption occurred.

11. The method of any of claims 1-10, wherein at least one act of recording is performed in a distributed ledger.

12. The method of any of claims 1-11, further comprising: receiving a request from one of a plurality of fueling stations for a requested amount of low carbon intensity fuel; determining an amount of available low carbon intensity fuel.

13. The method of any of claims 11 or 12, further comprising prior to reception of one or more requests from a plurality of fueling stations, generating the distributed ledger.

14. The method of any of claims 12 or 13, further comprising: in response to reception of the request from the one of the plurality of fueling stations and if the requested amount of fuel is less than the amount of available low carbon intensity fuel: initiating fuel operations at the one of the plurality of fueling stations15. The method of claim 14, further comprising generating a first new block including data corresponding to the requested amount of low carbon intensity fuel.

16. The method of any of claims 13-15, wherein generating the distributed ledger includes: generation of one or more blocks corresponding to data associated with previous production of low carbon intensity fuel; and for each subsequent block of the one or more blocks: determine a hash of data contained in a preceding block, and store the hash in a subsequent block.

17. The method of any of claims 1-16, wherein the first selected fuel type and the second selected fuel type comprise a same chemical composition.

18. A method to determine and control available low carbon intensity fuel, the method comprising: receiving a request from one of a plurality of fueling stations for a requested amount of low carbon intensity fuel; determining an amount of available low carbon intensity fuel based on a distributed ledger including blocks, each of the blocks including data corresponding to previouslyproduced amounts of low carbon intensity fuel and previously consumed amounts of low carbon intensity fuel; and in response to reception of the request from the one of the plurality of fueling stations and if the requested amount of fuel is less than the amount of available low carbon intensity fuel: initiating fuel operations at the one of the plurality of fueling stations, and generating a first new block including data corresponding to the requested amount of low carbon intensity fuel.

19. The method of claim 18, further comprising, in response to reception of the request from the one of the plurality of fueling stations and if the requested amount of fuel is greater than the amount of available low carbon intensity fuel: initiating low carbon intensity fuel production; and generating a second new block including data corresponding to a produced amount of low carbon intensity fuel.

20. A method to determine and control available low carbon intensity fuel, the method comprising: receiving a request from one of a plurality of fueling stations for a requested amount of low carbon intensity fuel; determining an amount of available low carbon intensity fuel based on data from a low carbon intensity fuel computing device; and in response to reception of the request from the one of the fueling station and if the requested amount of low carbon intensity fuel is less than the amount of available low carbon intensity fuel: initiating fueling at the one of the fueling station, determining an updated low carbon intensity fuel availability based on the amount of available low carbon intensity fuel, and updating the amount of available low carbon intensity fuel in the low carbon intensity fuel computing device.

21. The method of claim 20, wherein the low carbon intensity fuel computing device tracks availability of low carbon intensity fuel via a distributed ledger.

22. A system for managing motor fuel distribution and carbon intensity tracking, comprising: one or more fueling stations including a first user interface and a first controller configured to dispense the first selected motor fuel type and a second user interface and a second controller configured to dispense the second selected motor fuel type; a distributed ledger in communication with the first and second controllers; and a processor; and memory including instructions executable by the processor to perform the method of any of claims 1-21.

23. The system of claim 22, wherein the user interface is further configured to display one or more of a total local carbon reduction based on data corresponding to consumed low carbon intensity fuel in a locality from a distributed ledger, a total regional carbon reduction based on data corresponding to consumed low carbon intensity in a region from the distributed ledger, a total state carbon reduction based on data corresponding to consumed low carbon intensity in a state from the distributed ledger, or a total global regional carbon reduction based on data corresponding to globally consumed low carbon intensity fuel from the distributed ledger.

24. A low carbon intensity fuel controller to determine and control available low carbon intensity fuel, the controller comprising: a plurality of first inputs / outputs connected to a plurality of fueling stations each positioned at one of a plurality of fueling sites, the controller configured to: receive a request from a requesting fueling station of the plurality of fueling stations for a requested amount of low carbon intensity fuel; and a plurality of second inputs / outputs connected to a plurality of fuel production sites each of the plurality of fuel production sites configured to produce one or more of fuel or the low carbon intensity fuel, the controller configured to: determine an amount of available low carbon intensity fuel based on a distributed ledger including blocks, each of the blocks including data corresponding to previously produced amounts of low carbon intensity fuel and consumed amounts of low carbon intensity fuel, andin response to reception of the request from the requesting fueling station and if the requested amount of fuel is less than the amount of available low carbon intensity fuel: initiate fueling at the requesting fueling station, and generate a first new block for the distributed ledger including data corresponding to the requested amount of fuel.

25. The controller of claim 24, wherein the controller is further configured to: in response to the reception of the request from the requesting fueling station and if the requested amount of fuel is greater than the amount of available low carbon intensity fuel: initiate production of additional amounts of low carbon intensity fuel at one or more of the plurality of the fuel production sites; generate a second new block for the distributed ledger including data corresponding to the additional amount of low carbon intensity fuel; and add the second new block to the distributed ledger.

26. The controller of claim 25, wherein the second new block includes data corresponding to (a) an actual carbon intensity of the additional amount of low carbon intensity fuel, (b) processes utilized to reach the actual carbon intensity of the additional amount of low carbon intensity fuel, (c) a timestamp corresponding to a date of low carbon intensity fuel production, or (d) a location corresponding to production of the low carbon intensity fuel at one or more of the plurality of fuel production sites.

27. The controller of any of claims 24-26, wherein the first new block includes data corresponding to (a) an amount of low carbon intensity consumed, (b) a timestamp corresponding to a date of consumption of the low carbon intensity fuel, or (c) a location corresponding to location of a fueling station where consumption occurred.

28. The controller of any of claims 24-27, wherein the plurality of the fuel production sites comprise one or more of a refinery, a blending station, or a renewable fuel production site.

29. The controller of any of claims 24-28, wherein the controller is configured to, prior to reception of requests from the requesting fueling station, generate the distributed ledger.

30. The controller of claim 29, wherein generation of the distributed ledger comprises: generation of one or more blocks corresponding to data associated with previous production of low carbon intensity fuel; and for each subsequent block of the one or more blocks: determine a hash of data contained in a preceding block, and store the hash in a subsequent block.

31. The controller of claim 24, wherein the fuel and the low carbon intensity fuel comprise a same chemical composition.

Images