Principles & requirements

Project Developers shall demonstrate that they comply with all principles and requirements outlined in the applicable version of the Rainbow Standard Rules, and described below with a specific focus on mineralization.

Additionality

To demonstrate additionality, Project Developers shall perform regulatory surplus analysis, plus either investment or barrier analysis, using the Rainbow Additionality Template.

Regulatory surplus analysis shall demonstrate that there are no regulations that require or mandate project activities.

Project Developers must demonstrate that CO2 capture was not mandated under an Emissions Trading System (ETS). A site may be eligible if the site had already met its ETS obligations, and the captured CO2 exceeded those required reductions, and the site complies with the No double counting criteria.

At the European Union level, projects automatically pass the regulatory surplus analysis, which has been conducted by the Rainbow Climate Team. Project Developers are only required to provide a country-level regulatory surplus analysis.

Durability

Durability threshold

All projects certified under this methodology shall prove durable carbon removals for at least 1000 years. The chemically-bound removed carbon is considered permanently stored upon mineralization/material production.

The final end use of the material affects its risk of reversal. This risk is mitigated by the project design requirements regarding eligible uses of carbonated materials, which allow only materials that won't be incinerated (i.e. concrete, asphalt, and landfill).

Reversal risk assessment

The carbon reversal risks from mineralization of alkaline materials are:

  • Exposure to high temperatures via combustion, where carbonated material is incinerated or subjected to extreme heat, causing thermal decomposition of carbonate minerals and re-emission of CO2.

  • Exposure to strong acids, where carbonated material comes into contact with acidic environments (e.g. acid rain, acidic groundwater infiltration, or industrial acid exposure), causing dissolution of carbonate minerals and re-emission of CO2.

This methodology establishes the following mandatory project requirements to mitigate these risks, detailed in the following sections:

  • verification of carbonation extent and mineralogical stability

  • evaluation of carbonated material end use

Upon meeting these requirements at project validation, the risk of reversal is considered negligible for mineralization of alkaline materials. There are no further project requirements to assess reversal risks or conduct post-crediting monitoring for reversals.

All projects certified under this methodology shall contribute the default minimum 2% of their verified removal RCCs to the Rainbow Buffer Pool, as defined in the Rainbow Standard Rules.

Risk mitigation: verification of mineralogical stability

Project Developers shall describe the type of carbonate minerals produced and their specific risk of reversal under relevant heat and pH conditions. This assessment shall

  • be based on project-specific primary data (e.g. laboratory measurements such as XRD analysis) or secondary data that are highly representative of the project conditions, and

  • address the carbonate type produced (e.g. anhydrous vs hydrated), and the resulting implications for resistance to thermal decomposition and acid dissolution.

Risk mitigation: evaluation of carbonated material end use

Project Developers shall demonstrate that the intended end use of carbonated material mitigates reversal risk. Eligible end uses include but are not limited to incorporation into concrete, construction aggregates, or other non-combustible permanent materials.

Project Developers shall describe the expected end use, including building or structure type and geographic location, and, in relation to the mineralogical stability assessment above, demonstrate minimized risk of exposure to thermal decomposition and acid dissolution.

No double counting

Project Developers shall sign the Rainbow MRV & Registry Terms & Conditions, committing to follow the requirements outlined in the Rainbow Standard Rules, including not double using or double issuing carbon credits.

The following double counting risks have been identified for alkaline material mineralization projects. Project Developers shall follow the outlined requirements for each risk.

Double counting risk
Explanation
Requirement

Double issuance of carbon credits with downstream material users

Users of low-carbon concrete may seek to issue carbon credits in building methodologies in regulated or voluntary carbon markets

  • Identify all direct downstream users/buyers/actors in their supply chain.

  • Provide the company/organization name, name of an individual contact person at the company/organization, and their contact information (email address at minimum).

  • Provide signed agreements and/or sales contract clauses stating carbon credits have already been issued, and users will not claim benefits or issue carbon credits for the product.

Double claiming of removals or reductions with EPDs

If there is an EPD for the carbonated product, then carbon removals and/or avoidance may be claimed by downstream users throughout the supply chain, who may issue credits or claim other environmental labels for the carbon benefit already counted and sold elsewhere

  • Provide the product’s EPD, including:

    • actual GWP values with carbon benefits, as required by norms/standard, and

    • a clause specifying when users must exclude carbon benefits in calculations using values from the EPD.

Double issuance of carbon credits with upstream CO2 capture (e.g. DACCS projects)

Carbon capture projects are well incorporated in carbon markets (e.g. BECCS, DACCS), and Project Developers must agree on which entity is issued credits/how to repartition credits or carbon finance

  • Identify all CO2 suppliers in their supply chain.

  • Provide the company/ organization name, name of an individual contact person at the company/organization, and their contact information (email address at minimum).

  • Provide signed agreements and/or sales contract clauses stating carbon credits have been issued by the CO2 user, and CO2 suppliers will not claim/issue the same carbon benefits in the carbonated material.

Double claiming of removals or reductions with ETS

CO2 used for mineralization may be captured from heavy emitting industry sites that are covered by an ETS. When the site captures CO2 emissions, they can claim the benefit in the ETS, or participate in the carbon credit issuing project, but not both.

  • Demonstrate that the CO2 supplier is not covered by an ETS.

  • If the CO2 supplier is covered by an ETS, provide their official ETS reporting documents, showing that reductions that were issued carbon credits under the present methodology are not included in ETS reporting.

Co-benefits

Projects should support at least two quantifiable and verifiable environmental or social co-benefits, aligned with the UN Sustainable Development Goalsarrow-up-right (SDGs) framework. Any co-benefits claimed by the Project Developer shall be quantified, monitored, and audited for each verification and credit issuance.

Common co-benefits under this methodology are detailed in the table below. Project Developers may suggest and prove other co-benefits not mentioned here.

SDG 13 on Climate Action by default is not considered a co-benefit here, since it is implicitly accounted for in the issuance of carbon credits. If the project delivers climate benefits that are not accounted for in the GHG reduction quantifications, then they may be considered as co-benefits.

Table 1 Common co-benefits that projects under this methodology may provide are detailed, including types of proof that can be used to justify each co-benefit.

UN SDG
Example
Proof
Indicators

SDG 12.2 Achieve the sustainable management and efficient use of natural resources

The project’s circularity will be measured by the Material Circularity Indicator (MCI), according to the Ellen MacArthur Foundation's methodology, and compared to the circularity of the baseline product.

Types of inputs used and waste status

% circularity, % improvement from baseline

SDG 9.4 Upgrade infrastructure and retrofit industries to make them sustainable

Increase strength, durability and lifetime of concrete, extending infrastructure lifespan.

Internal testing, R&D results

% extended lifespan

SDG 8.4 Improve global resource efficiency in consumption and production

Reusing alkaline waste materials in the mineralization process diverts them from other waste treatment methods.

Invoices and operations records

tonnes of waste material used

SDG 6.3 Improve water quality by reducing pollution, eliminating dumping and minimizing release of hazardous chemicals and materials

Projects that carbonate and reuse cement wastewater contribute to improved and useful wastewater treatment and water quality

Invoices and operations records

m3 of wastewater used

Environmental and social safeguards

Project Developers shall prove that the project does not contribute to substantial environmental and social harms. Projects must follow all national, local and European (if located in Europe) environmental regulations, and prove such compliance using, for example, permits, certifications, or licenses.

In addition to completing the Rainbow Mineralization risk evaluation below, Project Developers must prove the following elements:

For fossil CO2 use, Project Developers shall prove that the CO2 was not generated or emitted for the sole purpose of carbon storage, and that it was captured from an existing CO2 emission source.

For biogenic CO2 use, Project Developers shall prove that the original biomass used to generate the biogenic CO2 meets the EU's RED IIIarrow-up-right Article 29 sustainability criteria for biomass (even if the project is not located in the EU). This includes the following, summarized here for informative purposes only:

  • If the biomass is proven to be waste, no further sustainability requirements apply (refer to the positive list in the Rainbow Biomass feedstock module).

  • If the biomass is not waste, Project Developers shall prove that it did not come from:

    • Primary or old-growth forests

    • Highly biodiverse forests or other wooded land designated as such by competent authorities.

    • Protected areas for rare or endangered ecosystems/species (unless proven that biomass production does not interfere with conservation goals).

    • Highly biodiverse grasslands

    • Heathland, wetlands, or peatlands

    • Recently deforested, converted or degraded ecosystems (within past 20 years)

  • Forestry biomass shall follow the requirements listed above, and

    • Respect international, national and regional legal requirements

    • Promote forest regeneration by avoiding large clear-cuts or extraction of stumps/roots

    • Protect biodiversity and soil quality

    • Come from sustainably managed forests

Environmental and social risk assessment

Project Developers shall fill in the Rainbow Mineralization risk evaluation, to evaluate the identified environmental and social risks of projects. The identified risks include:

  • Heavy metal leaching from stored alkaline feedstock

  • Dust and particulate generation from alkaline feedstock storage and handling

  • Water use in the mineralization process

  • Fugitive CO2 leaks during the mineralization process

  • Hazardous waste generation from the use of chemical additives

  • Leaching pollutants from carbonated products during the use phase

  • Demand for fossil CO2 as a valuable product increases fossil fuel output

  • Pressure on unsustainable or nonrenewable biomass use for biogenic CO2 generation

  • Environmental impacts from opening a new mine or quarry to obtain alkaline feedstock

Project Developers shall assign a likelihood and severity score of each risk, and provide an explanation of their choices. The VVB and Rainbow’s Certification team shall evaluate the assessment and may recommend changes to the assigned scores.

Any identified material risk (defined as issues with a risk score of moderate or higher) shall be subject to a Risk Mitigation Plan, which outlines how Project Developers will mitigate, monitor, report, and if necessary, compensate for any environmental and/or social harms.

Additional proof may be required for certain high risk environmental and social problems.

The Project Developer, the Rainbow Certification Team, or the VVB may suggest additional risks to be considered for a specific project.

circle-info

Note that the life-cycle GHG reduction calculations account for the climate change impacts of most environmental risks. Nonetheless, Project Developers shall transparently describe any substantial and sensitive GHG emission risks in the risk evaluation template.

circle-info

All risk assessments must also address the Minimum environmental and social risks defined in the Rainbow Standard Rules.

Leakage

Mineralization of materials must not contribute to activity shifting leakage. The following leakage risks are covered by other requirements in this methodology:

  • Displacement of baseline mineralization: any atmospheric carbon removal via mineralization that occurs in the baseline shall be modeled in the Baseline Scenario, and effectively deducted from the project's carbon storage.

  • Increased emissions during use: leakage emissions from use of carbonated products downstream of the project are mitigated by the Baseline setting requirements, where project materials must have the same performance as baseline/replaced products.

No further methodology requirements apply. Project Developers shall follow the Leakage requirements in the Rainbow Standard Rules to comply with this requirement.

Monitoring

Monitoring Plans for this methodology shall include, but are not limited to, tracking of the following information for each Mineralization Batch.

Eligibility criteria compliance

  • Proof of regulatory additionality, that CO2 didn't have to be captured, wasn't covered by ETS (or mention no change)

  • Proof of permanence/low reversal risk, end use of product (or mention no change)

  • Proof of no double counting: EPDs, ETS (or mention no change)

  • If using biomass feedstock, proof of adherence to Environmental and social safeguards requirements (or mention no change)

  • Any co-benefits claimed

GHG quantification

  • Amount CO2 leakage during transport

  • Repartition of CO2 types purchased, entering carbonation facility

  • Total amount of carbonated material produced per monitoring period, in tonnes of material

  • Carbon storage measurements, either:

    • Solid phase:

      • CO2 measured in solid samples of carbonated material

    • Gas inflow-outflow:

      • Volumetric flow and concentration of CO2 inflow and outflow

      • Gas void fraction of alkaline feedstock (if carbonating solid materials)

      • Bulk density of the alkaline feedstock (if carbonating solid materials)

      • Amount of carbonated material produced daily, in tonnes of material

      • Ongoing demonstration of equipment calibration and QA/QC procedures

  • Transport distance or amount of fuel, and transport mode, for CO2 delivery, alkaline feedstock delivery, and final product delivery (if >50 km)

  • Amount and type of alkaline feedstock used

  • Baseline removal calculations from alkaline feedstock carbonation

  • Baseline and project removal calculations from concrete use phase carbonation

  • Amount cement needed in baseline and project scenario, and chosen cement emission factor (only for projects issuing avoidance credits from reduced cement use)

  • Energy and/or material use from CO2 capture, CO2 purification, alkaline feedstock processing, and carbonation process

The Project Developer is the party responsible for adhering to the Monitoring Plan.

Monitoring Plans shall include the following information for each monitored parameter:

  • monitoring frequency

  • emission sources and sinks

  • data source

  • measurement methods/procedures, and their accuracy and calibration

  • quality assessment or quality control procedures

  • responsible party for collecting and archiving data

Last updated