> For the complete documentation index, see [llms.txt](https://valuex.gitbook.io/valuex-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://valuex.gitbook.io/valuex-whitepaper/value-x-whitepaper/5.-mrv.md).

# 5. Data and Trust: MRV (Measurement, Reporting and Verification)

Carbon Points are issued only when cryptographically signed data passes the verification rules.

![](https://1175759799-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTQIHnd2DbDjiuBhJwbBL%2Fuploads%2F8ezboGlMCLuGE0LKKS8g%2Funknown.png?alt=media\&token=1497f466-6053-438d-82de-f123093a17b7)

### 5.1 Data Lifecycle

Data is designed to pass through seven stages on its way from an emission reduction made on site to an on-chain point. On-chain commits and point issuance are planned to go live from Phase 2 (target: 2027), when on-chain MRV opens (see Sections 4.3 and 12.2).

![Figure 5. Data lifecycle: from collection to audit lookup](https://4111024654-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fw7YoFCbsDz1NbkOTHoHH%2Fuploads%2F7a833r8qeGtTR69RE2fM%2FChatGPT%20%EC%9D%B4%EB%AF%B8%EC%A7%80%202026%EB%85%84%209%EC%9B%94%2028%EC%9D%BC%20%EC%98%A4%ED%9B%84%2004_24_49.png?alt=media\&token=2876c016-4727-4b74-9af7-f978aa526052)

* Collection: a sensor or app produces a measurement together with a timestamp, location and device identifier.
* Local signing: the data is signed immediately at the point where it is generated, using a secure chip or a device key. Data changed after signing fails verification.
* Encrypted transmission: if a failure occurs, the data is stored in a local buffer and sent once service is restored.
* On-chain commit: only a hash and a de-identified reference key are recorded, not the original data. The original data and personally identifiable information are stored separately off-chain.
* Rule verification: the signature, time limits, location, duplication and plausible range are checked.
* Point issuance: points are issued only for data that passes, and rejected data is kept on record with the reason for rejection.
* Audit lookup: each point can be traced back to its commit transaction.

### 5.2 Source Weighting and Metadata

How far data can be trusted depends on where it comes from and how it is verified. VLX makes this explicit by assigning a grade.

![](https://4111024654-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fw7YoFCbsDz1NbkOTHoHH%2Fuploads%2F99PA0ieiSM1zfTFY8X6K%2FChatGPT%20%EC%9D%B4%EB%AF%B8%EC%A7%80%202026%EB%85%84%209%EC%9B%94%2028%EC%9D%BC%20%EC%98%A4%ED%9B%84%2004_27_10.png?alt=media\&token=0c8749fa-3f3e-4fa8-b4c3-c1e2adf82b4c)

The grades draw on ISO 14064-1 and -3 and the formulas on ISO 14064-2. The source grade, methodology version, measurement period and commit hash are designed to be kept permanently as metadata of each point.

### 5.3 Preventing Duplication and Manipulation (Anti-Abuse)

The following safeguards are designed to block double counting and false reduction claims.

* Unique device identification (DID): prevents multiple accounts and duplicate claims.
* Time limits: each device and activity has a minimum interval and a daily cap.
* Location consistency: GPS tracks and speed profiles are checked.
* Physically plausible range: values outside the rated capacity of the equipment fail verification.
* Single-ledger principle: points are issued only once for each activity that passes verification.

### 5.4 Methodology Versioning

VLX is designed to accommodate changes in formulas and coefficients while registering each methodology on-chain with its ID, version and effective date. The verification rule registry used for this registration will be introduced when on-chain MRV opens (see Section 4.3). Each point references the version in force when it was issued. A revision applies only to points issued after it, and **points already issued are not recalculated retroactively.**

### 5.5 Processing and Deleting Personal Data

The immutable-ledger principle does not apply to personal data.

* Only hashes and de-identified reference keys are recorded on-chain. Identifying information is not put on-chain.
* Off-chain personal data is destroyed once its retention period has passed.
* When deletion is requested, the original data is deleted without delay. The hash that remains on-chain cannot by itself be used to reconstruct the original, but combined with a wallet address or information held elsewhere it could be linked back, so the identification risk is not assumed to be zero.
* Account authentication and wallet key management for AetherFlow Wallet are outsourced to an external wallet infrastructure provider (Dynamic Labs, Inc., currently part of Fireblocks). This provider handles email verification, login token issuance, and storage of wallet key management components.
* Separate external providers are also used for blockchain data queries, market price data, and service infrastructure and databases. The list of processors and the scope of the outsourced work are published in the Privacy Policy and the Terms of Use, and are updated in the same documents when they change.

### 5.6 Roadmap for Linking with Recognized Registries

Linking with Verra VCS and Gold Standard is a medium- to long-term objective. The plan is to record verified data on VLX's own ledger, open the methodology to external review, and then link with the recognized schemes. Progress is disclosed on official channels.

<br>

***