Minting and transacting tokenized differentiated energy attributes using blockchain
A blockchain-based system digitizes and monetizes Differentiated Energy Attributes as tokens, addressing the inefficiencies in existing methods and promoting low-emission energy production by enabling secure and transparent transactions, thus addressing the challenges of verifying and monetizing DEA-related costs and investments.
Patent Information
- Application Number
- PCT/US2024/030276
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-24
- Filing Date
- 2024-05-20
- Publication Date
- 2024-11-28
AI Technical Summary
Current methods fail to effectively monetize and verify Differentiated Energy Attributes (DEA) related costs and investments, leading to inefficiencies in energy transactions and skepticism in the energy market due to legacy carbon offset solutions.
The implementation of a blockchain-based system that digitizes DEA verifications as tokens (DEATs) using smart contracts, allowing for secure, transparent, and efficient minting, management, and monetization of these tokens, independent of energy transactions, through a private blockchain network.
This solution enables differentiated energy producers to recuperate their DEA-related costs and investments, incentivizes the transition to low-emission energy production, and enhances the transparency and efficiency of energy transactions by creating a digital asset that represents verified environmental attributes, thereby reducing emissions and increasing market confidence.
Smart Images

Figure US2024030276_28112024_PF_FP_ABST
Abstract
Description
MINTING AND TRANSACTING TOKENIZED DIFFERENTIATED ENERGY ATTRIBUTES USING BEOCKCHAINCROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This Patent Application claims priority to U.S. Provisional Patent Application No. 63 / 468,579, filed May 24, 2023, and titled “MINTING AND TRANSACTING TOKENIZED DIFFERENTIATED ENERGY ATTRIBUTES USING BLOCKCHAIN,” the disclosure of which is incorporated by reference herein in its entirety.TECHNICAL FIELD
[0002] This disclosure relates to systems and methods for recording, tracking, and monetizing verified Differentiated Energy Attributes using blockchain as a value add to physical energy transactions.DESCRIPTION OF RELATED ART
[0003] Recent developments in environmental, social, and governance standards are focused on reducing emissions related to energy production. However, methods and systems that provide differentiated energy producers’ the ability to recuperate their Differentiated Energy Attributes (“DEA”) related costs and investments via monetization of DEA tokens (“DEATs”) are desirable.SUMMARY
[0004] This Summary is provided to introduce, in a simplified form, a selection of concepts that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter. “Differentiated Energy” includes any type of energy source, including, but not limited to, natural gas, hydrogen, and liquids that meet certain emission reduction environmental, social, and governance (“ESG”) standards. Differentiated energy may be characterized by Differentiated Energy Attributes (“DEA”) related to their production, transportation, and use. DEA includes data derived from the production of energy produced by operations or sites that have been independently verified as meeting certain ESG standards including air emission reductions. “DEA verification” means the verification issued by the agencies, thatinclude, but are not limited to, Project Canary, MiQ, Validere, and Equitable Origin, after examining energy production and transportation sites. A “buyer” and “qualified buyer” are interchangeably used in this disclosure. A “seller” and “qualified seller” are interchangeably used in this disclosure.
[0005] In some implementations, an example method for digitizing differentiated energy attributes (“DEA”) verifications as differentiated energy attribute tokens (“DEATs”) on a private blockchain network independent of energy transactions may include providing an application platform configured to communicate with one or more of a differentiated energy producer’s enterprise software system, the private blockchain network, or a third-party verification entity’s software system, wherein the third-party verification entity collects and verifies differentiated energy attributes (“DEA”) related to the producer’s differentiated energy production at a production site, setting up one or more of a differentiated energy producer corporate profile account, a producer private blockchain modified multi- signature wallet (“mMSW”), a qualified DEATs buyer corporate profile account, or a qualified DEATs buyer private blockchain modified multi-signature wallet (“mMSW”) using the application platform, collecting platform managed digital signatures (“PMDS”) of one or more authorized signatories of the producer or the third-party verification entity, wherein the respective mMSW is managed by one or more authorized signatories using their respective associated PMDS instead of blockchain based public keys or private keys, and using a predetermined formula, minting one or more DEATs to the producer’s mMSW at a first predetermined interval governed by the terms and conditions of a DEATs minting smart contract executed by one or more authorized signatories of the producer or the third-party verification entity using their respective PMDS. In some instances, the DEA includes environmental attributes and emissions data related to the producer’s differentiated energy production at a production site.
[0006] In some implementations, the example application platform may be configured to implement providing permissions to and authentication of the one or more authorized signatories according to the terms and conditions of a rules smart contract. In some instances, authenticating may require one or more of JSON Web Token (“JWT”) according to the open JSON Web Token standard or two-factor authentication (“2FA”). In some other instances, 2FA includes requiring one or more of time -based one-timepassword (“TOTP”) and sent by SMS text messages (“SMS OTPs”) to the one or more authorized signatories.
[0007] In some implementations, the example application platform may be further configured to execute one or more action smart contracts for managing one or more actions related to DEATs by one or more signatories of the producer, the third-party verification entity, or a DEATs buyer using their respective PMDS. In some instances, the one or more action smart contracts may include smart contracts related to intracompany transfer of DEATs, minting of DEATs, transaction of DEATs between the producer or a DEATs seller and a DEATs buyer, or retirement of DEATs.
[0008] In some implementations, an example method for digitizing differentiated energy attributes (“DEA”) verifications as differentiated energy attribute tokens (“DEATs”) may further include inputting at a second predetermined interval, energy production units related to the producer’s energy production at a production site, verifying using the third-party verification entity whether the production site meets predetermined emission standards set by the third-party verification entity, and if emission standards are met, classifying the energy produced from the producer’s production site as differentiated energy defined by differentiated energy attributes (DEA) associated with the emission standard, and outputting a report of differentiated energy production units and DEA verification data for the producer’s approval and the third- party verification entity’s approval by one or more of their respective authorized signatories using their respective PMDS.
[0009] In some implementations, the inputting step may be performed by one or more of the producer’s enterprise software system, the producer, or personnel related to a provider of the application platform. In some instances, the first predetermined interval may be once a day. In some other instances, the second predetermined interval may include one or more of daily, weekly, monthly, quarterly, or semi-annually.
[0010] In some implementations, an example predetermined formula for minting DEATs may correlate the number of DEATs to be minted to the units of differentiated energy produced or transported from the producer’s differentiated energy production site. In some instances, the predetermined formula may include the minting of one DEAT for one unit of differentiated energy produced or transported from the producer’ s production site. In some other instances, the one unit of differentiated energy includes one or moreof 1 mcf, 1 MMBtu, 1 dekatherm, 1 gallon, 1 pipeline mile, 1 shipping mile, 1 metric ton, or 1 megawatt hour of differentiated energy corresponding to the producer’s production site.
[0011] In some implementations, an example method for digitizing DEA verifications as DEATs may further include including outputting a DEATs retirement report related to retiring one or more DEATs by a user of differentiated energy pursuant to the terms and conditions of a DEATs retirement smart contract. In some instances, retired DEATs are burned from the blockchain to prevent associated DEA from being transferred to another entity.
[0012] In some implementations, a DEATs minting operation includes embedding data related to third-party verification in each DEAT associated with a producer’s production site. In some instances, communicating with the producer’s production enterprise software system may include communicating using one or more of the platform’s application program interface (API) or a preconfigured data upload protocol. In some other instance, an example method for digitizing DEA verifications as DEATs may further include cryptographically recording to the blockchain one or more of units of differentiated energy produced, DEA verification data, or units of differentiated energy sold associated with a producer’s production site. In some instances, an example DEATs minting smart contract may be automatically published to the blockchain.
[0013] In some implementations, an example method for transacting DEATs may include providing a transaction smart contract that governs the transaction for DEATs for execution by one or more authorized signatories of a qualified DEATs buyer and a qualified DEATs seller, publishing to the blockchain the executed transaction smart contract, and automatically providing payment instructions to the qualified DEATs buyer to transfer funds to the qualified DEATs seller. In some instances, an example application platform may be configured to collect platform managed digital signatures (PMDS) of the one or more authorized signatories of the qualified DEATs buyer and the qualified DEATs seller. In some other instances, an example application platform may be configured to implement providing permissions to and authenticating the one or more authorized signatories of the qualified DEATs buyer and the qualified DEATs seller according to the terms and conditions of a rules smart contract. In some instances, an example method for transaction DEATs may further include updating the number ofDEATS in the respective modified- multi signature wallets of the qualified DEATs buyer and the qualified DEATs seller.
[0014] In some implementations, an example qualified DEATs seller may include the producer of differentiated energy. In some instances, an example qualified DEATs buyer may include a buyer pre-approved by the seller. In some implementations, a qualified DEATs buyer and qualified DEATs seller are qualified using one or more due diligence processes established by the application platform. In some instances, an example application platform may provide for electronically completing and electronically submitting the documents required for the one or more due diligence processes. In some other instances, the one or more due diligence processes may include bidirectionally communicating with at least one third party service provider databases or platforms via an API of the application platform.
[0015] In some implementations, a system for digitizing DEA verifications as DEA tokens (DEATs) on a private blockchain network independent of energy transactions may include a cloud-based application software / platform configured to mint and manage DEATs. An example platform may be configured to communicate with one or more of the private blockchain network, a differentiated energy producer’s enterprise software system, or a third-party verification entity via an API or a preconfigured data upload. In some instances, an example system may include a cloud object storage system, and a database. The application platform may be configured to bidirectionally communicate with the cloud object storage system and the database. In some other implementations, an application platform may be configured to set-up one or more of a differentiated energy producer corporate profile account, a producer private blockchain modified multisignature wallet (mMSW), a qualified DEATs buyer corporate profile account, or a qualified DEATs buyer private blockchain modified multi-signature wallet according to terms and conditions of one or more smart contracts. In some instance the platform may be configured to collect platform managed digital signatures (PMDS) of one or more authorized signatories of the producer or the third-party verification entity. The respective mMSW is managed by one or more authorized signatories using their respective PMDS instead of blockchain based public keys or private keys, and using a predetermined formula, mint one or more DEATs to the producer’s mMSW at a first predetermined interval governed by the terms and conditions of a DEATs minting smartcontract executed by one or more authorized signatories of the producer or the third-party verification entity using their respective PMDS.
[0016] In some implementations, an example application platform may be further configured to input at a second predetermined interval, energy production units related to the producer’s energy production at a production site, verify using the third-party verification entity whether the production site meets predetermined emission standards set by the third-party verification entity, and if emission standards are met, classifying the energy produced from the producer’ s production site as differentiated energy defined by differentiated energy attributes (DEA) associated with the emission standard, and output a report of differentiated energy production units and DEA verification data for the producer’s approval and the third-party verification entity’s approval using one or more of their respective authorized signatories using their respective PMDS.
[0017] In some implementations, an example the application platform may be configured to communicate with the third-party verification entity’s system via an API. The third-party verification entity may collect the environmental attributes and the emissions data (DEA) related to the producer’s differentiated energy production at a production site.
[0018] In some implementations, an example application platform may be configured to run on one or more blockchain nodes hosted on a cloud server. In some instances, the application platform may be a microservice application deployed in a cloud service. In some other instances, the cloud object storage system may be configured to provide at least 10 9’s (>99.9999999999) durability. In some instances, the database may include a RDS database.
[0019] In some instances, the example application platform may provide access to the producer corporate profile account or the qualified DEATs buyer corporate profile account by implementing authentication protocols. Authentication may include two factor authentication (2FA) by one or more of time-based one-time password (TOTP) and sent by SMS text messages (SMS OTPs) to the producer’s or DEATs buyer’s smart device, or managed by an authenticator app.
[0020] In some implementations, the example application platform may be further configured to transact DEATs via a transaction smart contract executed by one or moreauthorized signatories of a qualified DEATs buyer and a qualified DEATs seller using their respective PMDS.
[0021] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings, and the claims. Note that the relative dimensions of the following figures may not be drawn to scale.BRIEF DESCRIPTION OF THE DRAWINGS
[0022] The foregoing aspects and many of the attendant advantages of this disclosure will become more readily appreciated as the same becomes better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:
[0023] FIG. 1A shows a schematic diagram of an example method for minting DEATs on a private blockchain managed by an example application platform, according to some implementations.
[0024] FIG. IB shows a schematic diagram of an example method for transacting DEATs via a bilateral transaction on a private blockchain managed by an example application platform, according to some implementations.
[0025] All reference numerals, designators and callouts in the figures are hereby incorporated by this reference as if fully set forth herein. The failure to number an element in a figure is not intended to waive any rights. Unnumbered references may also be identified by alpha characters in the figures and appendices.
[0026] The following detailed description includes references to the accompanying drawings, which form a part of the detailed description. The drawings show, by way of illustration, specific embodiments in which the pilot assembly and methods may be practiced. These embodiments, which are to be understood as “examples” or “options,” are described in enough detail to enable those skilled in the art to practice the present invention. The embodiments may be combined, other embodiments may be utilized, or structural or logical changes may be made without departing from the scope of the invention. The following detailed description is, therefore, not to be taken in a limitingsense and the scope of the invention is defined by the appended claims and their legal equivalents.
[0027] In this document, the terms “a” or “an” are used to include one or more than one, and the term “or” is used to refer to a nonexclusive “or” unless otherwise indicated. In addition, it is to be understood that the phraseology or terminology employed herein, and not otherwise defined, is for the purpose of description only and not of limitation.
[0028] Like reference numbers and designations in the various drawings indicate like elements.DETAILED DESCRIPTION
[0029] The following description is directed to some example implementations for the purpose of describing the innovative aspects of this disclosure. However, a person having ordinary skill in the art will readily recognize that the teachings herein can be applied and modified in a multitude of different ways. The described implementations may be tailored to compensate for various performance-related deficiencies. As such, the disclosed implementations are not to be limited by the examples provided herein, but rather encompass all implementations contemplated by the attached claims.Additionally, well-known elements of the disclosure will not be described in detail or will be omitted so as not to obscure the relevant details of the disclosure.
[0030] Various aspects of the disclosed systems and methods are described more fully herein with reference to the accompanying drawings. These aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. Although some examples and aspects are described herein, many variations and permutations of these examples fall within the scope of the disclosure. Although some benefits and advantages of the various aspects are mentioned, the scope of the disclosure is not intended to be limited to benefits, uses, or objectives. The detailed description and drawings are merely illustrative of the disclosure rather than limiting, the scope of the disclosure being defined by the appended claims and equivalents thereof.
[0031] The example decentralized system and methods utilize blockchain, allowing differentiated energy production and / or transportation verification (“DEA verification”) to be digitized and traded in a safe, secure, and transparent manner. The examplemethods and systems may be used for digitizing verifications (verification data) related to all types of differentiated energy.
[0032] Driven by environmental stewardship and regulations, differentiated energy producers, transporters, shippers, and various industry participants are focused on increasing differentiated energy production while implementing low-emission operations and exploring production from renewable sources such as landfills. DEA includes data derived from the production of energy at sites that have been independently verified as meeting ESG standards including emission reductions. Regarding transportation and storage of energy, DEA includes data derived from the storage of energy at sites, or from the transportation of energy from a production or storage site to an end-user. In each case, DEA is based on data that is independently verified as meeting ESG standards including air emission reductions. Other factors considered are the producer’s management practices regarding water management, community relations efforts, chemical management, and air quality management. Energy producers are adopting proactive and voluntary measures to meet emission regulations. Environmentally harmful greenhouse gas (“GHG”) emissions, such as methane are the major constituents in energy production and varying quantities of harmful GHG emissions are typically released as waste gas at energy production sites. These harmful GHG emissions are considered as fugitive emissions because they are an unintended aspect of the production processes at well sites and transportation pathways.
[0033] At some well sites, GHG emissions, such as methane, could be as high as 5% of the total daily production volume. This is significant, because in the case of methane, GHG emissions are over 80 times more potent than carbon dioxide. The U.S. EPA has reported that methane accounts for 10% of all U.S. greenhouse gas emissions from human activities and attributed 30% of those emissions to natural gas and petroleum production sites. Recently, the U.S. EPA launched the Global Methane Initiative to reduce methane emissions. Subsequently, some natural gas producers have implemented processes to decrease fugitive methane emissions to meet the standards established by verification agencies or entities that include, but are not limited to, Project Canary, MiQ, Validere, Equitable Origin, and others.
[0034] Verification agencies or entities have established their own scientific standards for certifying the energy produced as “differentiated.” For example, Project Canary created the “TrustWell™” certification which requires continuous monitoring offracking fluids, and wastewater disposal, by implementing specific monitoring technologies. Project Canary verifies differentiated energy with three performance ratings or tiers, namely, silver, gold, and platinum. MiQ uses the “MiQ standard,” which does not require continuous monitoring of parameters. Instead, assessment by an independent third party is required. MiQ issues certification with six grades or tiers A-F. Equitable Origin uses a “EOIOO™ for Responsible Energy Development,” which does not require continuous monitoring, but requires independent assessment by a third party. Equitable Origin issues certification with three levels or tiers of performance targets PT1, PT2, PT3. Key parameters to any of the certification / verification methods are Methane Intensity (“MI”) and Carbon Intensity (“CI”). MI may be defined as the volume of methane emissions at production sites expressed as a percentage of produced gas volumes. Most producers have stated 2025 goals for MI of less than about 0.05%. A producer’s MI is a key parameter in determining overall DEA, because, as previously noted, methane is about 80 times more harmful as a greenhouse gas than CO2. CI considers emissions from methane, carbon dioxide, and nitrous oxide presented as carbon dioxide equivalent (“CO2e”). When calculating CO2e, the most recent 20-year and 100- year global warming potentials from the Intergovernmental Panel on Climate Change (“IPCC”) are typically used. Disclosing a CI value, in addition to MI, is vital for obtaining a complete picture of a company’s (producer or energy storage entity or energy transportation entity or end user) emissions performance and compliance with the GHG Reporting Program (“GHGRP”) Corporate Standard.
[0035] In addition to the above verification options, an energy producer may also consider meeting the requirements of ISO standard ISO 14001:2015, which relates to environmental management systems. The ISO standard does not require continuous monitoring but requires independent assessment by a third party. The ISO standard does not adopt performance rating tiers. DEA verification provides a declaration that a producer has passed certain standards with the expectation that differentiated energy buyers including power plant operators and liquified natural gas (“LNG”) buyers in the U.S. and worldwide will insist on this accreditation in the future during routine energy transactions. Differentiated energy verification provides unique production data related to energy production and transportation, and DEATs created as a result of the verification may be treated as tangible assets.
[0036] Unlike carbon credits, DEA verification that qualifies energy as responsibly sourced, is issued by qualified third party agencies. As previously discussed, these third- party independent verifications are issued taking into account a multitude of factors that include, but are not limited to, MI, CI, production parameters such as drilling, fracturing, wellhead production, and processing. Other factors such as transportation and distribution practices, which may impact the environment and the supply chain network, may also be considered during verification. Most DEA verifications are updated frequently, which requires continuous data collection and monitoring and strict compliance to meet verification standards. Accordingly, unlike carbon credits or carbon offsets which are based on forecasts of GHG emissions or avoidance, differentiated energy attributes represent actual emissions of carbon dioxide or other greenhouses gases associated with energy production or storage or transportation on an end-use. DEA and DEATs may motivate energy producers, energy storage entities, energy transportation entities, and end-users of energy to reduce actual emissions, and recuperate their emission reduction / DEA related costs and investments via the sale and monetization of DEATs.
[0037] The cost of monitoring energy production for DEA verification is significant. Monitoring costs are however significantly lower than carbon abatement costs. The value of DEAs may be considered as the difference of the carbon cost of non-DEA verified energy characterized by a higher CI or MI, and DEA verified energy characterized by a lower CI or MI. The Oil and Gas Climate Initiative (“OGCI”) has set a target to reduce the collective average MI of its aggregated upstream oil and gas operations to below 0.25% by 2025, with the goal to achieve 0.20%. Therefore, DEA verified energy sales would likely be associated with a price premium attached to it and producers are concerned that energy buyers such as electric utility companies may not wish to pay a premium. DEA verified energy price may approach up to 5% above market prices of non-DEA energy, or, in the case of natural gas, up to $0.15 / mcf. It is well known that slight movements in gas pricing could impact the profitability of an energy producer.
[0038] Accordingly, methods and systems that enable gas producers to digitize their DEA verifications as tokens and to quantify, verify, manage, and monetize tokens in compliance with GHGRP quality criteria on a blockchain are needed. DEATs may be viewed as a digital asset that may be traded on a private blockchain. DEATs arerepresentative of DEA volumes or units of energy sold and provide an immutable record of production and transportation parameters on the blockchain and may be audited by an independent third-party. These methods and systems are needed to enable differentiated energy producers to monetize the DEA related costs and investments related to DEA verifications as a value-add to energy transactions, independent of energy sales. These methods and systems may also incentivize energy producers to phase out nondifferentiated energy production, with a complete transition to differentiated energy production in the future. Legacy carbon offset solutions have generated distrust with respect to creation of carbon credits, trading, and derived environmental benefits, and have fostered skepticism throughout the energy market, thereby severely limiting adoption, and value creation, from these solutions. The energy market views these carbon offset solutions as a threat since the goal of carbon offset solutions is likely to phase out fossil fuel (including natural gas) use.
[0039] Disclosed are example methods and systems that utilize blockchain based smart contracts to provide differentiated energy producers the ability to recuperate their DEA related costs and investments via the sale and monetization of DEA tokens (“DEATs”). FIG. 1A shows a schematic diagram of an example method 100A for minting DEATs on a private blockchain managed by the example enterprise platform (application platform) 110, according to some implementations. DEATs may be minted pursuant to a tokens minting smart contract. Platform 110 may provide microservices, that include, but are not limited to, authentication, defining a corporate user profile, defining signatories, and rules for multi- signature patterns pursuant to a rules smart contract, providing virtual data room services, securing platform managed digital signatures (“PMDS,” as described below) related to a transaction, and creating and managing modified multi- signature wallets (“mMSWs”, as described below), and auditing.
[0040] In example method 100A for minting DEATs, enterprise platform 110 may be configured to be in communication with a differentiated energy producer’s enterprise software system 111. Although method 100A discloses DEAT minting related to energy production site 112, method 110A may be applicable to DEAT minting related to an energy storage site, or an energy transportation journey from, for example, an energy production site or an energy storage site to an end-user’s site. The transportation route may include energy transportation from any point “A” to any point “B,” and may includetransportation by land, air, or water. An end-user may include any user of energy and may include aircrafts and sea-going vessels. Application platform 110 and producer’s enterprise software system 111 may be configured to communicate via a suitable application program interface (API) or preconfigured data upload protocol 103 to determine the units of differentiated energy produced. Application platform 110 may also be configured to communicate bidirectionally via a suitable (API) in step 107 with the software system of a third-party verification entity 114 to collect the environmental attributes and emissions data, that is, differentiated energy attributes (“DEA”) related to the producer’s differentiated energy production 112 following a production batch submission in step 103. Enterprise platform 110 may be configured to present the combined production data submitted in step 103 and its related environmental data in steps 101 and 107, respectively, to the producer 113 and verification entity 114.Enterprise platform 110 may be configured to subsequently collect the respective PMDS from the producer 113 and the software system of verification entity 114 in steps 115 and 109, respectively, before minting DEATs corresponding to differentiated energy production units, to the producer’s account; that is, to the producer’s mMSW on the blockchain.
[0041] Platform 110 may be a cryptographically authenticated data repository (“CADR”) for all data, records, activities, and reports related to differentiated energy production and associated DEA verification issued by verification entities. The verification entities may certify environmental attributes and emissions data, that is, differentiated energy attributes (“DEA”) using their established certification protocols. DEAs associated with differentiated energy production site 112 (or transmission site, in the case of pipelines) may be treated as a tangible asset which may be digitally tokenized via the blockchain.
[0042] In some implementations, one DEAT may be equivalent to one unit of differentiated energy produced. One unit of differentiated energy produced may be one or more of 1 mcf, 1 MMBtu, 1 dekatherm, 1 gallon, 1 pipeline mile, 1 shipping mile, 1 metric ton, or 1 megawatt hour of differentiated energy corresponding to a particular differentiated energy production site 112. The process of transporting energy via pipeline, over the road, or on a seafaring cargo vessel may result in emissions not only attributable to the direct emissions of the transportation process, that is, pipeline, vehicle, or cargo vessel, but also attributable to the energy leaked into the atmosphere during thetransportation journey. The exemplary systems and methods provide for a differentiated energy transporter to report the volume of energy transported and the total distance, in miles, of the transportation journey. The exemplary system permits a verification entity 114 to scientifically verify the emissions data attributable to the transporter’s journey, including both direct emissions and the energy leaked during transportation.
[0043] In step 101, personnel related to the enterprise platform provider 110 may create a corporate user profile for differentiated energy producer 113 and DEAT buyer 116. Platform 110 may be a cloud-based platform. Personnel related to the enterprise platform provider 110 may then input required account set-up information on example platform 110 and provide required permissions for platform 110 to communicate with producer’s enterprise software system 111 via a suitable API or preconfigured data upload in step 103. In step 102, producer’s enterprise software system 111 may capture the volume or units of differentiated energy produced at production site 112. In step 103, platform 110 may receive data representing physical volumes or units of differentiated energy produced for data processing from producer’s enterprise software system 111. Producer 113 may submit production data reports in step 103 via an API or a preconfigured data upload to system 110. Production reports may be provided to producer 113 for approval. In parallel to platform 110 receiving differentiated energy production data from the producer’s enterprise software system 111 in step 103, the verification entity 114 may access the producer’s production data on platform 110 to verify the environmental attributes related to differentiated energy in step 107. Producer 113 may also input other information such as API call details into platform 110.
[0044] Example method 100A and platform 110 may be configured to cryptographically record production activity, DEA data and verifications, and production volumes or units of energy to the blockchain in step 105. DEA tokens (“DEATs”) that are digitally minted may be transacted bilaterally on the platform’s private blockchain, and privately transferred bilaterally between known corporate entities, and / or committed via a spot and forward smart contract 118 in step 105.
[0045] In some implementations, blockchain nodes may be hosted on a cloud server or locally and made available to only approved and contracted corporate users of the platform. The example systems and methods disclosed herein utilize the capabilities of blockchain infrastructure to enable DEAT creation derived from differentiated energy production 112 combined with science-based verification of the related environmentalattributes and emissions data by verification entity 114. The example platform and systems decouple DEATs from the actual gas molecules sold into the market in compliance with GHGRP, and therefore provide maximum flexibility for transacting DEAT data between a producer 113 and a buyer 116. The digitization process creates an immutable record of the differentiated energy’s related environmental attributes and emissions data on the blockchain.
[0046] Platform 110 may process data collected from producer’s enterprise software system 111 and data provided by the verification entity 114 in step 103 and generate one or more smart contracts 118 in step 105 for minting and trading DEATs based on produced and verified differentiated energy volumes or units of energy. Smart contracts may meet NAESB contract standards for the sale and purchase of energy attributes published by the North American Energy Standards Board (“NAESB”). Pursuant to the terms and conditions of the smart contracts 118 created by platform 110 and submitted to the producer 113 and verification entity 114 for approval in steps 115 and 109, respectively, DEATs may be minted to the producer’s modified multi-signature wallet (account) on the blockchain. DEA tokens (“DEATs”) may be minted to the blockchain based on produced or sold differentiated energy units from differentiated energy production 112. One or more of the formulas in method 100 as previously described for minting DEATs may be used. One or more authorized signatories of producer 113 and verification entity 114 may then approve the total number of tokens created by platform 110 using their respective PMDS in steps 115 and 109, respectively. Platform 110 may automatically publish in step 105 smart contracts 118 to a permissioned blockchain, which may securely track and record DEAT minting, DEAT offerings by a buyer, and DEAT transactions. The DEAT production activities, offerings, and DEAT transactions are made visible in step 106 to permissioned users of the exemplary platform 110.
[0047] DEA verifications issued by agency or entity 114 that verify the differentiated energy attributes related to a differentiated energy production / transmission point 112 of producer 113 reside on the electronic ledger in the blockchain. Unique data related to the verified differentiated energy attributes provided by the verification entity 114 in step 107 is embedded in each DEAT related to that production / transmission point 112. The example systems and methods eliminate the need to host DEA verification and differentiated energy production activity details with an outside registry, and greatly simplify the token creation, management, and trading processes.
[0048] Example platform 110, along with the blockchain, serves as a registry and eliminates the complexity and inefficiencies of legacy environmental registry solutions. As previously noted, example platform 110 serves as a cryptographically authenticated data repository (“CADR”) for all documents, data, records, activities, and reports related to the DEAT creation and transfer via the blockchain. Example platform 110 may be configured to publish smart contracts 118 to a private blockchain provided by Quorum. Example platform 110 may be configured to be blockchain agnostic and may publish smart contracts to most blockchains. DEATs issued and transacted using the example systems and methods disclosed herein are automated, provide global exposure, and introduce enhanced transactability and liquidity to both producers 113 and buyers 116. The CADR platform may offer a robust API infrastructure allowing it to interface with third party databases or platforms enabling the CADR platform to act as a master platform. Additionally, the CADR platform may provide for audit capabilities, and transactable data, and is available to provide accountants and financial professionals the ability to prepare any related tax filings and GHGRP reports.
[0049] FIG. IB shows a schematic diagram of an example method 100B for transacting DEATs via a bilateral transaction on a private blockchain managed by an example enterprise platform, according to some implementations. In example method 100B for transacting DEATs pursuant to the terms and conditions of a transaction smart contract, producer 113 may structure a bilateral transaction 120 for the sale of its DEATs to a buyer 116, via the example enterprise platform 310. Buyer 116 may be preselected or qualified by the producer 113. To conclude a transaction smart contract 118 representing the bilateral transaction, authorized signatories of the producer / seller 113 may be required to digitally agree to, and execute (sign), the transaction with their respective PMDS in step 115. The transaction smart contract created in step 105 may recite the related transactional details and present the transactional details to the buyer 116 via the enterprise platform 110 in step 106. Buyer 116 may review the details of the transaction smart contract, and one or more authorized signatories of the buyer may approve the transaction using their respective PMDS in step 117.
[0050] In some implementations, the enterprise platform service provider may qualify buyers following a suitable due diligence process. Third party identity database providers such as Thompson Reuters Clear, and REFINITIV World may be used to verify and validate corporate user profiles on platform 110. For due diligence purposes,platform 110 may provide for electronically completing required documentation, that include, but are not limited to, AML / KYC (anti-money laundering / know your customer) documents required to meet anti-money laundering regulations worldwide, and other documents, to enable DEAT sellers and buyers to conduct due diligence and to streamline diligence.
[0051] In addition to a DEAT producer, a qualified seller 113 may include any entity holding DEATs in its rnMSW. For example, a qualified buyer 116 may re-sell the DEATs via a bilateral transaction on platform 110 to another buyer. In some implementations, non-differentiated energy producers, that is, producers who do not practice emission mitigation schemes, may use the tokens during transaction of nondifferentiated energy, because associating DEATs to a non-differentiated energy transaction may help producers to sell non-differentiated energy to buyers of differentiated energy. A buyer of non-differentiated energy may be able to treat their non-differentiated transactions as a differentiated energy-like transaction by associating the transacted volume or units of energy with an equivalent number of DEATs. Such a buyer may buy DEATs on example platform 110. DEATs traded on a bilateral transaction are characterized by verifiable provenance giving both sellers and buyers confidence in these transactions. The direct buy er-to- seller nature of the bilateral transaction provides for streamlined and transparent transactions and true price discovery for DEATs. Contractual obligations related to Know-Your-Customer (“KYC”), identity management and transfer protocols may be managed on the blockchain using example platform 110.
[0052] As previously noted, the one or more smart contracts 118 related to example method 100A or 100B may include one or more of a rules smart contract, a modified multi-signature wallet (“rnMSW”) smart contract for holding custody of DEATs as disclosed below, or an action smart contract. An example action smart contract may be related to one or more of minting of tokens (DEATs), intra-company (corporate user) transfers of DEATs, for example, between different subsidiaries of a corporate user, buysell transactions of DEATs between one or more corporate users, or retirement of DEATs. Other smart contracts may be executed to govern, for example, audit compliance and reporting.
[0053] Platform 110 may automatically publish smart contracts 118 to a permissioned blockchain which securely tracks and records all ongoing items and activities related tothe creation, management, and transfer of DEATs. Smart contracts 118 may provide for automated servicing and distribution mechanisms for each instrument or contract, while permanently recording all transactions. Smart contracts published to a permissioned blockchain by platform 110 offer all parties in the DEATs marketplace the ability to digitally interact with one another relating to a transaction. The disclosed example methods 100A or 100B allow for inherent efficiencies because significant time is typically spent on due diligence activities related to financial, environmental, and legal review, predominantly due to the use of physical documents that are often stored in siloed places and have limited flexibility to be customized to suit various needs. Example platform 110 streamlines due diligence related to token transactions as prospective sellers and buyers of DEATs have visibility to the underlying information which is authenticated by the blockchain.
[0054] The value of a DEAT may be generally determined by market conditions. Market participants (for example, users of the example systems and methods described herein) may include global corporate end-users reporting GHG emissions according to the GHGRP Corporate Standard, middle marketers, brokers, traders, governmental entities, power generators, and sovereign nations. Most of these participants may not purchase differentiated energy directly from the producer who delivers differentiated energy along with its associated DEA. As previously noted, a DEAT may be valued at market rates per energy unit and may offset the cost associated with securing DEA verification. In the case of a natural gas production or transmission point 112, each DEAT may have unique serialized data embedded in it, for example, the identity of the well that produced gas, time, date, and location of the gas production. DEATs may be minted to meet the requirements of an “Ethereum Request for Comments” (“ERC”) token technical standard to maintain functionality with wallets, exchanges, and smart contracts. For example, the standard employed may be Ethereum's ERC-1155 non- fungible token (“NFT”) standard, which allows for the creation of dynamic NFTs. The example systems and methods to mint and trade DEATs are agnostic to the verification programs a producer may employ. Additionally, the example systems and methods may mint tokens of different value and tiers based on MI, CI, emissions, and environmental attribute values.
[0055] DEATs related to a differentiated energy transaction may be retired in step 119 after the associated differentiated energy is consumed by an end user, thus fulfillingits useful life. That is, a token may mirror the useful life of the physical differentiated energy as it moves from production through consumption where it no longer exists. An owner of a DEAT is not obligated to retire the tokens with consumption of an equivalent energy unit of production, but it may be required to retire the DEAT if it intends to claim the DEA as its own. If it has been determined that too many tokens were purchased and are in an owner’s mMSW, non-retired DEATs may be resold via bilateral transaction. A buyer 116 may retire acquired DEATs in step 119 via enterprise platform 110 in accordance with GHGRP standards for quality criteria, resulting in a GHGRP compliant retirement report, which may contain a complete view of the necessary GHG data including CI, MI, DEA, environmental attributes, and data provenance related to the buyer’s specific energy consumption. When retired, the DEATs are “burned” from the blockchain preventing the related DEA from being transferred to any other entity. To motivate producers 113 to continuously improve and enhance their emission mitigation methods at production or transmission points 112, DEATs are retired for a buyer to claim the DEA represented by the DEATs as its own in accordance with GHGRP. To clarify, the GHGRP, along with most emissions and carbon reporting protocols, require that the DEA emissions data are permanently retired by the ultimate user of the corresponding volume of energy represented by the DEATs to prevent double representation and use of the underlying differentiated energy attributes.
[0056] The disclosed example methods and systems streamline the creation, management, and trading of DEATs and incentivize differentiated energy producers to adopt engineering solutions that minimize emissions during energy production and transport. DEATs may be re-sold, transferred, or retired with confidence in their provenance. In some implementations, an owner may hold DEATs in its custody and allocate them for its future energy consumption. This will allow DEAT owners to transact lookback token volumes or based on units of energy to fulfill historical ESG goals, a common practice in the energy and ESG markets. Lookback volumes represent any volume or units of differentiated energy that has been produced but not sold and may be relevant when producers have started to qualify energy as differentiated but have not tokenized and monetized their verifications. That is, DEA verified tokenization lags differentiated energy production and is therefore done at a time after the production of differentiated energy based on differentiated energy volumes or units that have not been sold.
[0057] In some implementations, enterprise platform 110 may implement example method 100A for creating DEATS and example method 100B for transacting DEATs, and provide related microservices that include, one or more of, defining user profile and roles, securing platform managed digital signatures related to a transaction, authentication, creating and managing modified multi-signature wallets, or auditing as described below:
[0058] Corporate user profile. A corporate user profile or account created by platform 110 after verification of a user’s KYC / AML credentials, may require the identification of one or more signatories who may authorize a transaction, or any other action related to the corporate user profile account pursuant to predetermined permission rules associated with a user profile. The permission rules may be disclosed in a rules smart contract executed between a corporate user and a provider of platform 110. Platform 110 may automatically enforce these rules and may be configured to collect enterprise platform managed digital signatures (“PMDS”) from authorized signatories to complete an action. One or more signatories may be assigned system-wide authorization. In some implementations, signatories may be assigned limited authorization related to certain actions defined by the rules smart contract. As such, PMDS do not represent a digital blockchain based signature, which typically requires a combination of public and private keys. Qualified personnel of a corporate user of the enterprise platform 110 may login with credentials (username and password) and are subsequently authenticated based on a JSON Web Token (JWT) according to the open JSON Web Token standard.Additionally, qualified personnel may enable two factor authentication (“2FA”) on their accounts.
[0059] In some implementations, actions related to creating and transacting DEATs may require authorization from multiple signatories as defined in the rules smart contract. Pursuant to the terms and conditions of the rules smart contract, platform 110 may be configured to prompt, for example via e-mail, each signatory to authorize the action using their respective PMDS. In some implementations, an action may require the authorization of all signatories assigned to authorize a particular action using their respective PMDS. In some implementations, an action may require the authorization of a subset of signatories assigned to authorize a particular action. In some implementations, platform 110 may be configured to execute a multi- signature pattern for a particularaction. For example, a multi- signature pattern may require “x” out of a total number of “y” signatories to authorize an action.
[0060] PMDS and authentication. Platform 110 may be configured to secure the PMDS of authorized signatories who may authorize an action. Instead of digital blockchain-based signatures, certain actions, for example, steps 109, 115, and 117 (as described below), may be authorized using the PMDS of the respective signatories. In example method 100A for creating DEATs, one or more smart contracts 118 created by platform 110 may be submitted to producer 113 and verification entity 114 for approval in steps 115 and 109, respectively. The one or more smart contracts 118 may include a rules smart contract, a modified multi-signature wallet smart contract (“mMSW”) for holding custody of DEATs as disclosed below, or an action smart contract. An example action smart contract may be executed to define the terms and conditions of one or more of minting of DEATs, intra-company (corporate user) transfers of DEATs, for example, between different subsidiaries of a corporate user, buy-sell transactions of DEATs between one or more corporate users of the application platform, or retirement of DEATs. The actions of intra-company (corporate user) transfers of DEATs, for example, between different subsidiaries of a corporate user, buy-sell transactions of DEATs between one or more corporate users of the application platform, or retirement of DEATs may termed as “managing” DEATs.
[0061] To act as an authorized signatory, a user may require specific permission defined by the terms and conditions of a rules smart contract. The permissions for an authorized signatory may be defined within a role-based access control (“RBAC”) capability provided by enterprise platform 110. An authorized signatory having RBAC permission may authorize qualified personnel of the corporate user act as an authorized signatory. In addition to requiring specific permission to act as an authorized signatory, a user may also be required to satisfy specific authentication steps to act as a signatory. An authorized signatory may require 2FA to be enabled on their account. Additionally, an authorized signatory may be required to use 2FA every single time they perform a digital signature to further strengthen security measures.
[0062] PMDS may be protected by secure authentication protocols. For example, for backend authentication, Pas sport. js library may be used. This process may enable the addition of new signatories into the system. Signatories of a particular corporate user may be provided with a mandatory username and password, and depending on theregistration method, a unique email address may also be attached. Security may be enhanced using 2FA by at least one of time-based one-time password (“TOTP”) and onetime password sent by SMS text messages (“SMS OTPs”) to a user’s digital device such as a smartphone. 2FA may also be managed by an authenticator app. An authenticator app may include the Google Authenticator app, at the User’s discretion. 2FA protocols provide enhanced security compared to simple web-based authentication using only a username and password. As previously stated, PMDS do not require blockchain related public and private keys. There is no direct interaction between a corporate user or one or more of the user’s authorized signatories and the private blockchain.
[0063] Modified Multi-signature Wallet. Users of enterprise platform 110 may execute one or more unique smart contracts 118 for creating DEATs, transacting DEATs, and holding custody of the DEATs owned by that corporate user (business entity) in a user’s modified multi- signature wallet (“mMSW”). A mMSW smart contract may require the PMDS of one or more authorized signatories of the user to authorize an action (or transaction). The mMSW smart contract (also referred to as a mMSW) both holds DEATs in custody and approves specific DEAT-related actions based on the multisignature policy defined in a rules smart contract.
[0064] In some implementations, an example multi- signature policy may require “m out of n signatories to approve action x, in order for x to be considered as approved by the business entity.” The multi- signature policy may be implemented using the enterprise platform to secure PMDS from authorized signatories pursuant to the rules smart contract. When the required number (m out of n) of PMDS is secured, platform 110 may update the modified multi- signature wallet (“mMSW”) on the private blockchain. In this case, both the multi-signature configuration and the collection of signatures are performed by platform 310. The multi- signature policy may be different for different actions. For example, the rules smart contract related to a corporate user of platform 110 may require the PMDS of two authorized signatories to mint DEATs and the PMDS of one authorized user for retiring DEATs.
[0065] Unlike common multi-sig wallet models used on public blockchains, the business logic or actions regarding DEATs is not built into the modified multi-signature wallet. Business actions related to DEATs may include one or more of minting of DEATs, transaction of DEATs (buy / sell), inter-company transfer of DEATs, or retirement of DEATs. These actions are executed pursuant to the terms and conditions oftheir respective action smart contracts 118. An action smart contract may use at least one modified multi-signature wallet to manage the movement of DEATs.
[0066] Any one of the smart contracts 118 do not require blockchain generated public or private keys to authorize a transaction using an example mMSW. PMDS of one or more signatories of a corporate user are not collected or stored in an example mMSW. For the sake of clarity, at the blockchain level, DEATS are held in a mMSW of a corporate user profile established using platform 110. Individual users do not own DEATs.
[0067] Enterprise platform 110 may be developed as a microservice application deployed on a cloud computing services provider that includes Amazon Web Services (“AWS”) EC2 and served by using AWS Elastic Load Balancer (“ELB”). For file / data storage, a cloud object storage may be used may be used. For example, Amazon S3 is cloud object storage service with good scalability, data availability, security, and performance. A cloud object storage may provide for high durability (at least 99.99999999%) or 10 9’s durability. A cloud object storage may provide for high durability (at least 99.999999999%) or 11 9’s durability. For database, Relational Database Service (“RDS”) may be used. For example, Amazon Relational Database Service (“Amazon RDS”) is a web service that makes it easier to set up, operate, and scale a relational database in the S3 cloud.
[0068] Currently, energy transactions are not conducted using blockchain. Tokenizing differentiated energy transactions may reduce complexity and bureaucracy and improve the speed and transparency of differentiated energy transactions that are quite complex. Exploiting synergies between the disclosed example methods and systems for generating and monetizing DEATs with tokenizing the sale of differentiated energy on a blockchain is within the scope of this invention.EXAMPLEExample retirement of DEATs.
[0069] Owners of DEATs may allocate tokens from their modified multi- signature wallet to users within their organization that consume energy. Owners may “match” consumption of energy that is not verified as differentiated with their DEATs and then mark the DEATs as retired. For example, Company A may plan to burn 300,000 MMBtu of natural gas that is not DEA verified in a certain month. Company A mayinput this gas consumption into its Company Profile of their dashboard on example platform 110 and select “Retire DEATs” and subsequently digitally sign a retirement request in step 119. This action would “bum” 300,000 DEATs from Company A’s modified multi-signature wallet in that month and generate a serialized GHGRP compliant retirement report in the name of Company A. The serialized GHGRP compliant retirement report will be viewable permanently on example platform 110 enabling Company A’s stakeholders, regulators, and auditors to examine the detailed provenance associated with the 300,000 retired DEATs representing the 300,000 MMBtu’s of differentiated natural gas.
[0070] In some implementations, the example methods 100A or 100B, may be coupled with an auditable digital reconciliation process to ensure that the quantity of DEATs minted or created correlates directly to the volume or units of differentiated energy produced or sold. Producer 113 may be responsible for the reconciliation process. Reconciliation may be conducted within a reasonable time, for example, within about 30 days of minting tokens. To correct the number of tokens to be minted and allocated to producer 113 for a certain volumes of gas sales, platform 110 may allocate a percentage of the tokens minted in step 105 to an escrow-purposed smart contract to ensure the integrity of the volume of tokens available for sale.
[0071] In some implementations, DEATs may be traded as a Tier II commodity in the U.S. on a decentralized exchange (“DEX”).
[0072] As used herein, a phrase referring to “at least one of’ or “one or more of’ a list of items refers to any combination of those items, including single members. For example, “at least one of: a, b, or c” is intended to cover the possibilities of: a only, b only, c only, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a and b and c. Unless otherwise specified in this disclosure, for construing the scope of the term “about” or “approximately,” the error bounds associated with the values (dimensions, operating conditions etc.) disclosed is ± 10% of the values indicated in this disclosure. The error bounds associated with the values disclosed as percentages is ± 1% of the percentages indicated. The word “substantially” used before a specific word includes the meanings “considerable in extent to that which is specified,” and “largely but not wholly that which is specified.”
[0073] Various modifications to the implementations described in this disclosure may be readily apparent to persons having ordinary skill in the art, and the generic principlesdefined herein may be applied to other implementations without departing from the spirit or scope of this disclosure. Thus, the claims are not intended to be limited to the implementations shown herein but are to be accorded the widest scope consistent with this disclosure, the principles and the novel features disclosed herein.
[0074] Additionally, various features that are described in this specification in the context of separate implementations also can be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation also can be implemented in multiple implementations separately or in any suitable subcombination. As such, although features may be described above in combination with one another, and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
[0075] Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Further, the drawings may schematically depict one more example processes in the form of a flowchart or flow diagram. However, other operations that are not depicted can be incorporated in the example processes that are schematically illustrated. For example, one or more additional operations can be performed before, after, simultaneously, or between any of the illustrated operations. In some circumstances, multitasking and parallel processing may be advantageous.Moreover, the separation of various system components in the implementations described above should not be understood as requiring such separation in all implementations, and it should be understood that the described program components and systems can generally be integrated together in a single product or packaged into multiple products.REFERENCES
[0076] “Responsibly Sourced Gas: Cleaner, greener and here to stay,” Wood Mackenzie publication, October 2021.
Claims
CLAIMSWhat is claimed is:
1. A method for digitizing differentiated energy attributes (DEA) verifications as differentiated energy attribute tokens (DEATs) on a private blockchain network independent of energy transactions, the method including: providing an application platform configured to communicate with one or more of a differentiated energy producer’s enterprise software system, the private blockchain network, or a third-party verification entity’s software system, wherein the third-party verification entity collects and verifies differentiated energy attributes (DEA) related to the producer’s differentiated energy production at a production site; setting up one or more of a differentiated energy producer corporate profile account, a producer private blockchain modified multi- signature wallet (mMSW), a qualified DEATs buyer corporate profile account, or a qualified DEATs buyer private blockchain modified multi- signature wallet (mMSW) using the application platform; collecting platform managed digital signatures (PMDS) of one or more authorized signatories of the producer or the third-party verification entity, wherein the respective mMSW is managed by the one or more authorized signatories using their respective PMDS instead of blockchain based public keys or private keys; and using a predetermined formula, minting one or more DEATs to the producer’s mMSW at a first predetermined interval governed by the terms and conditions of a DEATs minting smart contract executed by one or more authorized signatories of the producer or the third-party verification entity using their respective PMDS.
2. The method of claim 1, wherein the application platform is configured to implement providing permissions to and authentication of the one or more authorized signatories according to the terms and conditions of a rules smart contract.
3. The method of claim 2, wherein authenticating requires one or more of JSON Web Token (JWT) according to the open JSON Web Token standard or two-factor authentication (2FA).
4. The method of claim 3, wherein 2FA includes requiring one or more of time-based one-time password (TOTP) and sent by SMS text messages (SMS OTPs) to the one or more authorized signatories.
5. The method of claim 1, wherein the application platform is further configured to execute one or more action smart contracts for managing one or more actions related to DEATs by one or more signatories of the producer, the third-party verification entity, or a DEATs buyer using their respective PMDS.
6. The method of claim 5, wherein the one or more action smart contracts include smart contracts related to intra-company transfer of DEATs, minting of DEATs, transaction of DEATs between the producer or a DEATs seller and a DEATs buyer, or retirement of DEATs.
7. The method of claim 1, wherein the DEA includes environmental attributes and emissions data related to the producer’s differentiated energy production at a production site.
8. The method of claim 1, further including: inputting at a second predetermined interval, energy production units related to the producer’s energy production at a production site; verifying using the third-party verification entity whether the production site meets predetermined emission standards set by the third-party verification entity, and if emission standards are met, classifying the energy produced from the producer’s production site as differentiated energy defined by differentiated energy attributes (DEA) associated with the emission standard; and outputting a report of differentiated energy production units and DEA verification data for the producer’s approval and the third-party verification entity’s approval by one or more of their respective authorized signatories using their respective PMDS.
9. The method of claim 8, wherein the inputting step is performed by one or more of the producer’s enterprise software system, the producer, or personnel related to a provider of the application platform.
10. The method of claim 8, wherein the first predetermined interval is once a day.
11. The method of claim 8, wherein the second predetermined interval includes one or more of daily, weekly, monthly, quarterly, or semi-annually.
12. The method of claim 1, wherein the predetermined formula correlates the number of DEATs to be minted to the units of differentiated energy produced or transported from the producer’s differentiated energy production site.
13. The method of claim 1, wherein the predetermined formula includes the minting of one DEAT for one unit of differentiated energy produced or transported from the producer’s production site.
14. The method of claim 13, wherein the one unit of differentiated energy includes one or more of 1 mcf, 1 MMBtu, 1 dekatherm, 1 gallon, 1 pipeline mile, 1 shipping mile, 1 metric ton, or 1 megawatt hour of differentiated energy corresponding to the producer’s production site.
15. The method of claim 1, further including outputting a DEATs retirement report related to retiring one or more DEATs by a user of differentiated energy pursuant to the terms and conditions of a DEATs retirement smart contract.
16. The method of claim 15, wherein retired DEATs are burned from the blockchain to prevent associated DEA from being transferred to another entity.
17. The method of claim 1, wherein minting includes embedding data related to third-party verification in each DEAT associated with a producer’s production site.
18. The method of claim 1, wherein communicating with the producer’s production enterprise software system includes communicating using one or more of the platform’s application program interface (API) or a preconfigured data upload protocol.
19. The method of claim 1, further including cryptographically recording to the blockchain one or more of units of differentiated energy produced, DEA verification data, or units of differentiated energy sold associated with a producer’s production site.
20. The method of claim 1, wherein the DEATs minting smart contract is automatically published to the blockchain.
21. A method for transacting DEATs minted using the method of claim 1, the method including: providing a transaction smart contract that governs the transaction for DEATs for execution by one or more authorized signatories of a qualified DEATs buyer and a qualified DEATs seller; publishing to the blockchain the executed transaction smart contract; and automatically providing payment instructions to the qualified DEATs buyer to transfer funds to the qualified DEATs seller.
22. The method of claim 21, wherein the platform is configured to collect platform managed digital signatures (PMDS) of the one or more authorized signatories of the qualified DEATs buyer and the qualified DEATs seller.
23. The method of claim 21, wherein the application platform is configured to implement providing permissions to and authenticating the one or more authorized signatories of the qualified DEATs buyer and the qualified DEATs seller according to the terms and conditions of a rules smart contract.
24. The method of claim 21, further including updating the number of DEATS in the respective modified- multi signature wallets of the qualified DEATs buyer and the qualified DEATs seller.
25. The method of claim 21, wherein the qualified DEATs seller includes the producer of differentiated energy.
26. The method of claim 21, wherein the qualified DEATs buyer includes a buyer pre-approved by the seller.
27. The method of claim 21, wherein the qualified DEATs buyer and qualified DEATs seller are qualified using one or more due diligence processes established by the application platform.
28. The method of claim 27, wherein the application platform provides for electronically completing and electronically submitting the documents required for the one or more due diligence processes.
29. The method of claim 27, wherein the one or more due diligence processes include bidirectionally communicating with at least one third party service provider databases or platforms via an API of the application platform.
30. A system for digitizing DEA verifications as DEA tokens (DEATs) on a private blockchain network independent of energy transactions, the system including: a cloud-based application software / platform configured to mint and manage DEATs, wherein the platform is configured to communicate with one or more of the private blockchain network, a differentiated energy producer’ s enterprise software system, or a third-party verification entity via an API or a preconfigured data upload; a cloud object storage system; and, a database, wherein the platform is configured to bidirectionally communicate with the cloud object storage system and the database, and wherein the platform is configured to: set-up one or more of a differentiated energy producer corporate profile account, a producer private blockchain modified multi- signature wallet (mMSW), a qualified DEATs buyer corporate profile account, or a qualified DEATs buyer private blockchain modified multi-signature wallet according to terms and conditions of one or more smart contracts; and collect platform managed digital signatures (PMDS) of one or more authorized signatories of the producer or the third-party verification entity, wherein the respective mMSW is managed by the one or more authorized signatories using their respective associated PMDS instead of blockchain based public keys or private keys; and using a predetermined formula, mint one or more DEATs to the producer’s mMSW at a first predetermined interval governed by the terms and conditions of aDEATs minting smart contract executed by one or more authorized signatories of the producer or the third-party verification entity using their respective PMDS.
31. The system of claim 30, wherein the application platform is further configured to: input at a second predetermined interval, energy production units related to the producer’s energy production at a production site; verify using the third-party verification entity whether the production site meets predetermined emission standards set by the third-party verification entity, and if emission standards are met, classifying the energy produced from the producer’s production site as differentiated energy defined by differentiated energy attributes (DEA) associated with the emission standard; and output a report of differentiated energy production units and DEA verification data for the producer’s approval and the third-party verification entity’s approval using one or more of their respective authorized signatories using their respective PMDS.
32. The system of claim 31, wherein the application platform is configured to communicate with the third-party verification entity’s system via an API, and wherein the third-party verification entity collects the environmental attributes and the emissions data (DEA) related to the producer’ s differentiated energy production at a production site.
33. The system of claim 30, wherein the application platform is configured to run on one or more blockchain nodes hosted on a cloud server.
34. The system of claim 30, wherein the application platform is a microservice application deployed in a cloud service.
35. The system of claim 30, wherein the cloud object storage system is configured to provide at least 10 9’s (>99.9999999999) durability.
36. The system of claim 30, wherein the database includes a RDS database.
37. The system of claim 30, wherein access to the producer corporate profile account or the qualified DEATs buyer corporate profile account is authenticated using two factor authentication (2FA) by one or more of time-based one-time password (TOTP) and sent by SMS text messages (SMS OTPs) to the producer’s or DEATs buyer’s smart device, or managed by an authenticator app.
38. The system of claim 30, wherein the application platform is further configured to transact DEATs via a transaction smart contract executed by one or more authorized signatories of a qualified DEATs buyer and a qualified DEATs seller using their respective PMDS.
Citation Information
Patent Citations
Battery management reward network and system
US11615409B1
Offtake-based asset backed securities and co2 removal models
WO2021113870A1
Systems and methods for transaction validation in layer 2
WO2022271669A1
