Vai al contenuto principale
removal Mexico Vintage 2025, 2026 Documentazione completa General Methodology v2.0

Sea Cave True Blue Carbon, Baja California, Mexico

CT-744 ↗

4.2 / 10
Integrity
3.2
Transparency
5.0
Claim Safety
4.2
Documentation
5.4

Score Breakdown

Integrity

missing Baseline approach and reassessment timing were not found in the extracted record (PDD/validation/monitoring set), limiting confidence in quantified removals

missing Permanence and leakage are not addressed (no buffer pool stated; reversal risk not discussed; leakage justification absent)

Transparency

verified Key project metadata and monitoring period are provided, and an independent VVB is named (monitoring report 2024-05-31; validation report 2024-04-19)

missing Total verified/claimed removals were not found in the extracted record, reducing MRV transparency (monitoring report 2024-05-31)

Claim Safety

verified The project is explicitly not CORSIA-eligible, reducing certain double-claiming/eligibility marketing risks (extracted record)

missing Additionality verification is inconsistent across documents and core quantification fields (baseline, leakage, ERR) are missing, increasing greenwashing/over-crediting risk

Documentation

verified Three core document types are present (PDD, validation report, monitoring report) with 2024 dates, supporting basic traceability

missing Medium extraction confidence and an internal contradiction on additionality verification indicate documentation reliability gaps

Detailed Analysis

Integrity

The PDD describes additionality using a common-practice test, but the validation report does not confirm that additionality was verified by the VVB, weakening additionality robustness (PDD 2024-11-29; validation report 2024-04-19). The baseline approach and any baseline reassessment timing were not found in the extracted record, which is a major gap for a removal project’s quantification integrity (PDD/validation/monitoring set). Permanence is not substantiated: reversal risk is not discussed and no buffer pool contribution is stated (monitoring report 2024-05-31). Leakage is also not addressed—no deduction percentage or justification is provided (monitoring report 2024-05-31).

Transparency

The monitoring period is clearly stated as 2023-08-01 to 2024-10-01, and the VVB is identified as Earthood, which supports basic transparency (monitoring report 2024-05-31; validation report 2024-04-19). However, the extracted record does not include total claimed or total verified removals for the period, limiting the ability to reconcile issuance with monitoring results (monitoring report 2024-05-31). Key MRV parameters such as baseline method and leakage treatment are also missing from the extracted record, reducing auditability (PDD/validation/monitoring set).

Claim Safety

The project is explicitly not CORSIA-eligible, which reduces the risk of CORSIA-related eligibility misclaims (extracted record). Nonetheless, over-crediting/greenwashing risk remains elevated because the baseline method is not found in the extracted record and leakage and reversal provisions are not addressed (monitoring report 2024-05-31). The inconsistency on whether the VVB verified additionality further increases claim risk because marketing statements could overstate third-party assurance (PDD 2024-11-29; validation report 2024-04-19).

Documentation

The document set includes a PDD, a validation report, and a monitoring report, all recent (2024), which is a reasonable minimum package for review (evidence documents list; monitoring report 2024-05-31; validation report 2024-04-19; PDD 2024-11-29). Extraction confidence is medium, suggesting some readability/structure limitations that can hide key quantitative details. The presence of a direct contradiction between the PDD and validation report on VVB verification of additionality indicates documentation consistency issues that reduce confidence in the record.

Overall

This project scores weakest on integrity because baseline, leakage, and permanence provisions are not evidenced in the extracted record, and additionality assurance is unclear. The key contradiction is that the PDD states additionality was verified by the VVB, while the validation report indicates it was not; the validation report (dated 2024-04-19) is privileged as the higher-authority third-party assurance document over the project-authored PDD (dated 2024-11-29), and the inconsistency lowers confidence and scores. With documentation present but incomplete on core quantification fields, transparency and claim safety are moderate-to-low; note that if integrity were scored below 4.0, an overall cap would apply under the gate rules (not pre-applied here).

Audit Analysis

The project has some social safeguard elements documented (FPIC and a grievance mechanism), but core carbon-accounting integrity elements are not evidenced in the extracted record (baseline approach, leakage treatment, and reversal/permanence provisions). A key inconsistency between the PDD and the validation report on whether additionality was verified by the VVB raises reliability concerns and increases over-crediting risk.

Project Description

Sea Cave True Blue Carbon represents a multi-faceted approach to atmospheric CO2 reduction and Blue Carbon by passively removing CO2 through macroalgae photosynthesis, dramatically reducing carbon emitting process associated with fishing behavior and calculating carbon stored in the reef biomass. Sea Cave® True Blue Carbon® comes with a built in contractual assurance (a Blue Credit ® NFT) that for each verified true blue carbon credits sold, at least 100 kilograms of marine life is generated. If we fail to meet the promised marine life levels, we expand the project at our cost until marine life targets are met. The result is that the Sea Cave True Blue Carbon program creates a vehicle for world-wide, assured, fast -acting, measurable increases in ocean health and marine life abundance focusing on kelp and coral ecosystems.

Red Flags

  • Contradiction on whether additionality was verified by the VVB (PDD vs validation report), undermining confidence in additionality claims
  • Baseline approach not found in the extracted record, limiting ability to assess over-crediting risk
  • Leakage not addressed (no justification and no deduction stated) despite being a removal project where activity-shifting risks can be relevant
  • Reversal/permanence provisions not addressed (no buffer pool percentage stated; reversal events not discussed)

Credit Vintages

Nessuna emissione registrata sul registro.

Il marketplace dichiara i vintage: 2025, 2026 (non verificato).

Cosa migliorerebbe questo punteggio

  • Provide a clearly specified baseline method (including data sources, assumptions, and when it will be reassessed) and include it consistently across the PDD, validation, and monitoring documentation.
  • Add explicit permanence and leakage provisions: quantify any leakage deduction (or justify negligible leakage) and document reversal risk management, including any buffer pool contribution and monitoring/response procedures.

Questi suggerimenti indicano quali prove pubbliche aggiuntive potrebbero migliorare il livello di confidenza di questa valutazione. Non garantiscono un punteggio futuro più alto.

Risk Indicators

Additionality

Test described but VVB verification disputed

Permanence

Reversal risk/buffer not evidenced

Leakage

Leakage not addressed

Baseline

Baseline method not found

Safeguards

FPIC and grievance mechanism documented

Double-claim

Not CORSIA-eligible; CCP status not stated

Where to buy

Marketplaces

+ Know where to buy this?

Listing multiple projects? Send us a CSV at [email protected].

⚑ Dispute this rating
CT-744 ↗

Registry Documents

monitoring

pdd

validation

Analysis Provenance Scored 2026-04-02 General Methodology v2.0 Documentazione completa

Sei il proprietario di questo progetto?

Correzione metadati (gratuita)

Nome, paese, marketplace o link errati? Segnalacelo.

Non modifica lo score.

[email protected]

Rivalutazione con nuovi documenti

Hai documentazione aggiornata non ancora inclusa? Puoi richiedere un nuovo run della pipeline con i nuovi input.

Invia Documenti