Transportation Decarbonization: Registry-Grade CI for LCFS, FuelEU Maritime, and RED III

For heavy-duty fleet operators running LNG, CNG, or RNG, for marine fuel buyers facing FuelEU Maritime exposure, for road freight operators handling LCFS-eligible fuel pathways, and for pathway holders responsible for CARB submissions, the central problem is the same: low carbon fuel standard compliance demands defensible carbon-intensity scores and audit-grade chain of custody, and the RNG transportation credits generated under those regimes are only as good as the pathway documentation underwriting them. Regulators on both sides of the Atlantic are tightening pathway integrity scrutiny year over year. Voluntary attestations, spreadsheet records, and producer-direct PDFs that survived 2023 audits are not surviving 2026 audits. The Greentruth answer for transportation fuel is QET-RNG (tokenized biomethane with verified CI in kgCO₂e/MMBtu) running through the QET-LCFS extension methodology for California submissions, with the same foundation positioned for FuelEU Maritime and RED III as those regimes mature.

Transportation fuel attribute proof, in one paragraph. Greentruth's QET-RNG provides registry-grade proof of the fuel attribute from production through pipeline injection — 1 MMBtu of RNG thermal energy with verified carbon intensity in kgCO₂e/MMBtu, ISO 14064-3 reasonable-assurance verification by an accredited ISO 14065:2020 verifier, blockchain-anchored chain of custody on the EarnDLT registry running on Hedera Hashgraph, and the QET-LCFS extension methodology that produces CARB-compliant pathway documentation. For Oregon Clean Fuels Program, Washington Clean Fuel Standard, FuelEU Maritime, and RED III, the same QET-RNG foundation extends to the jurisdiction-specific submission requirements as those regulatory regimes mature.

For LCFS compliance in detail

For QET-RNG in full

Tightening pathway integrity scrutiny. CARB has steadily raised the bar on LCFS pathway verification — primary data expectations, segment-level reporting, and ISO 14064-3 reasonable-assurance verification have all become more stringent. Pathway holders submitting under older documentation conventions are increasingly being asked to re-paper, and pathway approvals contingent on weaker assurance are vulnerable to retroactive review.

Geographic expansion of LCFS-style regimes. What started in California has spread. Oregon's Clean Fuels Program and Washington's Clean Fuel Standard now operate under LCFS-analogous frameworks, with each jurisdiction maintaining its own pathway-integrity expectations. Operators with multi-state fleet operations need fuel-attribute documentation that satisfies all three regimes simultaneously rather than running parallel paperwork stacks.

EU regime maturation. FuelEU Maritime (Reg. (EU) 2023/1805) imposes greenhouse-gas intensity reduction targets on ships above 5,000 GT calling at EU ports, escalating year over year. RED III (Directive (EU) 2023/2413) tightens renewable-energy share requirements across transport and adjacent end uses. Both regimes will rely on mass-balance chain-of-custody documentation backed by independent verification — exactly the documentation discipline LCFS pathways already require.

The combined effect: a transportation fuel buyer with a 2026 procurement program needs documentation that holds up across CARB, Oregon, Washington, FuelEU Maritime, RED III, and any future analogous regime — and that survives the kind of auditor or regulator review becoming standard practice. The QET-RNG foundation is designed to be that documentation.

For the QET-RNG methodology basis

The transportation-fuel buyer population splits across four primary segments, each with distinct documentation needs:

Heavy-duty fleet operators. Long-haul trucking fleets running on LNG or CNG, increasingly substituting RNG into the fuel supply for carbon-intensity reduction. Fleet operators care about per-mile CI documentation that integrates with their TMS (transportation management system), fuel-card data, and corporate sustainability disclosure.

Marine fuel buyers. Vessel operators and bunker fuel purchasers facing FuelEU Maritime exposure, where the GHG intensity of the energy used on board must demonstrate annual reduction against a baseline. The documentation requirements for marine fuel attribute proof are still maturing, but the underlying chain-of-custody discipline — verified production, mass-balance accounting, third-party assurance — is settling into the same shape as LCFS.

Road freight buyers. Logistics companies, package-delivery operators, and contract freight providers subject to customer-side Scope 3 disclosure pressure. Even where the freight buyer is not the direct LCFS submitter, they are increasingly asked by downstream customers (retailers, e-commerce platforms, industrials) to document the carbon intensity of the fuel powering their transportation services.

Pathway holders. The CARB-registered entities — producers, distributors, refiners, blenders — who file LCFS pathway applications and submit quarterly pathway data. Pathway holders have the most direct compliance exposure: they own the pathway and bear the responsibility for the underlying data quality. Greentruth's QET-LCFS extension is built around the documentation pathway holders need to file.

For all four segments, the integrity question is the same: can the fuel-attribute documentation survive verification, audit, and regulator review at the level the relevant jurisdiction expects? Greentruth's answer for transportation fuel is yes — through registry-grade tokenization anchored to ISO 14064-3 reasonable-assurance verification.

For the broader marketplace context

QET-RNG is the foundation. Each token represents 1 MMBtu of RNG thermal energy with verified carbon intensity in kgCO₂e per MMBtu, produced by an anaerobic digester, landfill gas plant, or other biomethane facility, and injected into a common-carrier pipeline. The token is minted on the EarnDLT registry on Hedera Hashgraph under three integrity layers:

• ISO 14064-3 reasonable-assurance verification. An accredited ISO 14065:2020 verifier reviews the producer's primary MRV data, the methodology application, the uncertainty quantification, and the materiality threshold, and issues an unmodified verification opinion. The opinion is anchored to the token on-chain.
• Compliance Passport five-point verification gateway. For RNG delivery integrity, the QET-RNG Compliance Passport runs the five-point gate: injection point identified, delivery point identified, pipeline connectivity confirmed, volumetric equivalence, temporal matching. When all five are met, the QET-RNG is issued as a Fuel Attribute Documentation Certificate — full Scope 1 fossil-CO₂ reduction validity.
• Mass-balance chain of custody. Total certificates issued never exceed total physical RNG injected, the injection and delivery points must sit on the same interconnected pipeline system, and the system-wide cohort accounting reconciles continuously.

For a transportation fuel buyer, the practical effect is that every QET-RNG retirement against a fleet, marine, or freight reporting claim carries the full chain of custody back to the producer's verified primary data — survivable under CARB pathway review, FuelEU Maritime verification, RED III chain-of-custody assertion, or any analogous regime.

For the full QET-RNG product

CARB's Low Carbon Fuel Standard is the most operationally mature low-carbon fuel regime in the world. Pathway holders submitting biomethane pathways under LCFS face stringent documentation requirements: site-specific primary data, segment-level reporting, ISO 14064-3 reasonable assurance, and CARB-approved verifier accreditation. The QET-LCFS extension methodology is built around exactly those requirements.

What the QET-LCFS extension adds to QET-RNG:

• CA-GREET 3.0 reference dataset. Where QET-RNG mints typically run against R&D GREET 2025 (the federal-default reference), the QET-LCFS extension methodology runs against CA-GREET 3.0 — the California-specific lifecycle dataset CARB requires for LCFS pathway calculations. The CA-GREET 3.0 version pin is recorded immutably on the resulting token.
• CARB pathway-application documentation. The extension produces the documentation set CARB expects on pathway applications: methodology application, primary-data substantiation, third-party verifier opinion, materiality threshold documentation, and the pathway-specific lifecycle calculation backed by CA-GREET 3.0.
• Quarterly reporting integration. LCFS pathway holders submit quarterly pathway data to CARB; the QET-LCFS extension generates the structured submission package consumable by CARB's LCFS Reporting Tool and the buyer's compliance workflow.
• Verifier accreditation alignment. CARB-approved verifiers operating under ISO 14064-3 are the operative pool for LCFS pathway verification; the QET-LCFS extension aligns the verifier engagement model to CARB's accreditation expectations.

For pathway holders, the practical effect is that a single QET-RNG mint with the QET-LCFS extension produces the documentation needed for both CARB pathway approval and ongoing quarterly reporting — eliminating the parallel paperwork stack that LCFS submissions traditionally require.

For LCFS compliance in detail

For the underlying CA-GREET vs R&D GREET treatment

LCFS-style low-carbon-fuel regimes have expanded beyond California, and operators with multi-state operations need documentation that satisfies each jurisdiction's specific requirements.

Oregon Clean Fuels Program (CFP). Oregon's CFP operates on an LCFS-analogous framework with its own pathway-application process, CI-score expectations, and reporting cadence. QET-RNG with appropriate methodology extension produces the documentation package Oregon CFP submissions require — building on the same primary-data and verification discipline as the California QET-LCFS extension.

Washington Clean Fuel Standard (CFS). Washington's CFS rolled out under similar architectural choices, with the state's Department of Ecology as the regulator. The pathway-application and quarterly-reporting structure tracks closely with CARB's LCFS, and QET-RNG documentation extends to Washington CFS submissions through the same methodology infrastructure.

For fleet operators, freight buyers, or pathway holders running operations across CA / OR / WA simultaneously, the documentation efficiency matters. Rather than maintaining three parallel verification and submission stacks, a single QET-RNG mint can carry the metadata each jurisdiction requires, with the relevant submission package generated for each.

The same logic extends to other jurisdictions as they roll out analogous regimes — Minnesota, New Mexico, Vermont, and Canadian provincial frameworks are at various stages of LCFS-style adoption, and the QET-RNG foundation is positioned to extend to those regimes as the documentation requirements crystallize.

The European low-carbon transportation regimes are still maturing operationally, but the documentation discipline they will require is increasingly clear.

FuelEU Maritime (Reg. (EU) 2023/1805). FuelEU Maritime imposes annual GHG-intensity reduction targets on the energy used on board ships above 5,000 GT calling at EU ports — starting at −2% in 2025 against a 2020 baseline, escalating to −80% by 2050. The regulation contemplates that vessel operators document the GHG intensity of the energy used through verified primary data and mass-balance chain of custody. For RNG bunker fuel and analogous low-carbon marine fuels, QET-RNG produces exactly the verification and chain-of-custody documentation FuelEU Maritime contemplates.

RED III (Directive (EU) 2023/2413). RED III tightens renewable-energy share requirements across transport and adjacent end uses, with chain-of-custody and verification expectations that align closely with the QET-RNG foundation. For biomethane substituting fossil natural gas in transport applications across EU member states, RED III's verification regime expects mass-balance documentation, independent third-party assurance, and the same kind of chain-of-custody discipline LCFS pathways already require.

The forward-looking framing here is deliberate. FuelEU Maritime is operative starting in 2025 but the verifier ecosystem, sub-regulatory guidance, and the practical documentation patterns are still settling. RED III's implementing acts vary by member state and continue to evolve. The QET-RNG foundation is designed so that, as these regimes mature, the same documentation a buyer is generating today for CARB or Oregon CFP submissions will extend to the EU regimes with jurisdiction-specific extensions rather than parallel verification cycles.

For transportation fuel applications, the carbon-intensity attribute structure on each QET-RNG token is what survives regulator review. The structure covers the lifecycle from feedstock through pipeline injection, with each segment carrying its own verified data:

• Feedstock characterization. What's being digested — landfill gas, dairy manure, food waste, wastewater biogas, agricultural residue. The feedstock type drives the lifecycle CI calculation under CA-GREET 3.0 (for LCFS) or R&D GREET 2025 (for federal-default applications).
• Facility operations. The RNG facility's GPS coordinates, operational parameters, and primary monitoring data. Site-specific primary data is preferred under the four-tier data-quality hierarchy.
• Methane intensity. The producer-level methane emissions at the RNG facility, captured under the QET-RNG methodology with IPCC AR5 GWP100 factors (CH₄ = 28, N₂O = 265).
• Pipeline injection. The pipeline operator, injection point, and the volumetric equivalence verification at the system boundary (criteria 1 and 4 of the Compliance Passport's five-point gateway).
• Delivery point. The buyer's facility connection or vehicle-fueling station, with pipeline-connectivity confirmation linking injection and delivery on the same interconnected system (criterion 3 of the gateway).
• Verification metadata. The accredited ISO 14065:2020 verifier of record, the ISO 14064-3 opinion date, the materiality threshold, and the lead verifier's credentials.

The full structure travels with every QET-RNG retirement and is available as machine-readable JSON or human-readable retirement certificate. For a transportation fuel buyer, the practical implication is that a single retirement event produces the full pathway documentation an auditor or regulator opening the record in 2027 or 2028 will need.

For how the data-quality hierarchy works · For the pipeline network model

For operationally significant fleet, marine, and freight programs, the QET-RNG documentation has to flow into the buyer's existing operational systems — not sit in a separate paperwork repository. The Machine-Ready API exposes every QET-RNG operation through REST endpoints with webhook events, schema-first JSON attribute model, and DID-compliant identifiers.

Three integration patterns:

• Fleet TMS integration. The transportation management system consumes QET-RNG retirement records as a structured data source — per-trip or per-fueling-event documentation attached to the route, the vehicle, and the load. The CI score travels with the trip record into the customer-facing reporting and the operator's sustainability disclosure simultaneously.
• ERP / fuel-card integration. The buyer's fuel-card data and ERP systems consume the CI attribute structure at the fueling-event level. CARB pathway-application submissions and quarterly reporting can be generated directly from the ERP-side data without a separate compliance workflow.
• ESG software integration. Watershed, Persefoni, Sweep, Workiva, or in-house GHG accounting systems consume the retirement records for corporate Scope 1 and Scope 3 disclosure — with framework-aligned exports (GHG Protocol, SBTi, CSRD ESRS E1, IFRS S2, SB 253, TCR) generated at the retirement transaction itself.

For pathway holders, fleet operators, and freight buyers running operationally at scale, the API integration is the difference between a compliance program that scales and a paperwork program that requires manual handling at every step.

For the full Machine-Ready API surface