Bamboo plantations by farmers and community in the country
Score Breakdown
Integrity
verified Additionality was confirmed by the VVB using a barrier test, which supports the project’s core crediting case.
missing Leakage is not addressed in the verification report, and the baseline is project-specific rather than clearly reassessed or standardized.
Transparency
verified The monitoring period is clearly stated, and the verification report identifies Carbon Check as the VVB with no material findings reported.
missing Key quantified fields are missing from the extracted record, including verified and claimed ERR totals, usage monitoring details, and leakage deduction.
Claim Safety
verified The project uses a recognized VCS methodology and has a 19% buffer pool, which helps reduce some crediting risk.
missing Leakage justification is weak in the final verification record, and CORSIA eligibility is not stated, leaving residual claim-risk uncertainty.
Documentation
verified The record includes a verification report date, a monitoring period, and multiple safeguard-related elements such as FPIC, grievance mechanism, and benefit sharing.
missing Extraction confidence is low and only one evidence document is clearly identified, which limits confidence in completeness and consistency.
Detailed Analysis
Integrity
The verification report confirms additionality through a barrier test and says the VVB, Carbon Check, found no material findings. The project also has a 19% buffer pool and reports no reversal events, which is supportive for permanence. That said, leakage is recorded as not addressed in the verification report, and the baseline is project-specific with no reassessment date found, which weakens the overall integrity case.
Transparency
The monitoring period and verification date are clearly stated, and the report identifies the verifier. However, the extracted record does not provide verified or claimed ERR totals, usage monitoring method, or leakage deduction, so the MRV trail is incomplete. The low extraction confidence further reduces transparency because at least one key document was poorly readable.
Claim Safety
The project is under VCS and uses AR-ACM0003, which is a recognized framework, but claim safety depends on how well emissions reductions are quantified and defended. Here, leakage is not addressed in the final verification record, and CORSIA eligibility is not stated, so the risk of overstated claims remains moderate. The 19% buffer pool helps, but it does not fully offset the uncertainty created by missing quantification fields.
Documentation
The file contains a verification report with a recent date, a long monitoring period, and several safeguard indicators such as FPIC, grievance mechanism, and benefit sharing. Even so, only one evidence document is clearly identified in the extracted record, and the extraction confidence is low. With no corrective actions reported, the documentation is usable but not robust enough for a high-confidence assessment.
Overall
I privileged the verification report’s statements over the earlier contradictory entries because it is the more recent and higher-priority document. On leakage, I used the verification report’s 'not addressed' value rather than the earlier 'deemed negligible' statement, and on reversals I used 'none reported' while noting that an earlier document had left the issue unaddressed. These contradictions reduce reliability and justify a conservative overall score; the project appears credible, but the evidence base is incomplete and somewhat inconsistent.
Audit Analysis
The project has some positive integrity signals, including VVB-confirmed additionality, a buffer pool of 19%, and no reported reversal events in the verification report. However, leakage is not addressed in the extracted record, the baseline is project-specific rather than clearly standardized, and the low extraction confidence reduces trust in the documentation. Overall, this looks like a moderate-quality file with meaningful evidence gaps rather than a high-confidence low-risk crediting case.
Project Description
Proponent: Infinite Environmental Solutions Limited Protocol categories: Agriculture Forestry and Other Land Use Protocols: AR-ACM0003 Estimated annual GHG reductions: 10077 tCO2e Region: Asia Registration date: 2025-12-11
Red Flags
- Leakage treatment is inconsistent across documents: one source said it was deemed negligible, while the verification report records it as not addressed; I privileged the later verification report because it is the higher-priority and more recent document.
- Reversal risk is not fully resolved in the record: the verification report says no reversal events were reported, but an earlier document apparently left reversals not addressed, which lowers confidence in permanence-related claims.
Credit Vintages
| Issued | Retired | Available | ||
|---|---|---|---|---|
| 2021 | 3,369 | 2,746 | 623 | |
| 2022 | 2,500 | 0 | 2,500 | |
| 2023 | 2,500 | 0 | 2,500 | |
| 2024 | 2,500 | 0 | 2,500 | |
| Total | 10,869 | 2,746 | 8,123 |
Cosa migliorerebbe questo punteggio
- Provide a clear leakage assessment in the verification or monitoring report, including any deduction or justification for why leakage is negligible.
- Publish the verified and claimed ERR totals, usage monitoring method, and a clearer document set so the emissions accounting can be independently checked.
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
VVB-confirmed barrier test
buffer pool present, no reversals reported
leakage not addressed in final report
project baseline, reassessment not stated
FPIC and grievance mechanism documented
CORSIA/CCP status not stated
Where to buy
+ Know where to buy this?
Listing multiple projects? Send us a CSV at [email protected].
⚑ Dispute this rating
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 →