Skip to content

Platform under construction. Nothing on this site is a public offering or an investment recommendation.

Methodology

How the numbers we publish are produced

And, more importantly, what they do not prove. A sustainability figure without its method is an assertion, not transparency.

CO2 avoided

Computed as (self-consumed energy + exported energy) times the grid emission factor. Both parts are credited: self-consumed kWh displace grid imports and avoid emissions too.

We do not use generation minus consumption. That subtraction discards self-consumption and understates the result.

The value is not entered by an operator: the database derives it from the reading and the factor for the period year. A hand-typed number would have no provenance.

On the phrase net zero

Net zero is the design target of the project, not an achieved or verified state.

A real net zero balance needs a defined boundary, a lifecycle inventory including the embodied carbon of construction (which for a new build dwarfs a few years of solar generation) and independent verification. None of that has been done.

The figures we publish cover only operational emissions avoided by solar generation. They exclude embodied carbon and are not third-party verified.

What the blockchain hash proves, and what it does not

A sha256 recorded in the contract proves that exact byte sequence existed no later than that transaction and has not been altered since.

It does not prove the measurements are accurate, that the work was done, or that the document is truthful. False data hashes just as well as true data.

The network used is a testnet with no durability guarantee, so the record demonstrates the mechanism rather than being a permanent archive.

How to verify a hash yourself

Every attestation on the transparency page publishes its canonical payload: the exact text, byte for byte, whose sha256 was anchored in the contract. Verifying it requires trusting nothing from us: copy the payload, compute its sha256, and compare it with the hash on the page and with the one the contract emitted on Basescan.

In a terminal: printf '%s' <payload> | shasum -a 256. If the text contains a single quote, save it to a file with no trailing newline and run shasum -a 256 on that file. The result has to match character for character: any added space or line break changes the hash, which is why the copy button hands over the exact original text.

An attestation without a published payload is one whose original version the platform can no longer reproduce, usually because the data was corrected after anchoring. We would rather say that than hide it: the old hash still proves what was anchored at the time, not what the page shows today.

And as the previous section explains, a matching hash proves the integrity of the text, not the truth of the measurements: false data hashes just as well as true data.

Work certificates

A certificate is a measurement act converted into money: a joint measurement recorded in an acta, signed by the works inspection and the contractor technical representative, and approved by the works director.

They are cumulative: the period value is the excess over the previous certificate. We also publish physical progress, because financial progress can be inflated by materials stockpiling and advances without executed work, and physical progress lagging financial progress is the most important early distress signal in Argentine construction. The denominator of financial progress is the work contract value in force, with its source published, not the capital being raised: they are different magnitudes, and dividing by the second compresses the percentage and mutes the comparison. With no contract value loaded, the percentage is not published.

Telemetry

Readings are taken per period with boundaries computed explicitly in UTC-3. Argentina has had no daylight saving since 2009.

A re-read replaces the period rather than adding to it. Inverters can backfill late data for several days depending on the manufacturer, so a period may be corrected after publication.

The site's solar resource, per two independent sources

As an external plausibility reference: annual global horizontal irradiation at the site (Puerto Madryn, -42.77, -65.03) is 1725 kWh/m2 per the European Commission's PVGIS v5.3 (PVGIS-ERA5 database, the only one covering the area) and 1698 kWh/m2 per NASA POWER (ALLSKY_SFC_SW_DWN climatology, 4.6483 kWh/m2 per day). Two independent models that differ by less than 2%. Both queries were made on 2026-07-27 against the public APIs, no key required.

What this allows: judging whether the generation we publish is physically plausible for the location. What it does not allow: turning it into an exact expected production, because that requires the installed capacity, orientation and losses of the real system, engineering data this version of the platform does not record. It is multi-year average climatology, not a forecast and not a promise of generation.

Emission factors used

The factor is looked up by year and frozen into each period together with its method. Nothing is published after 2023, so a later period uses the most recent year available and says so.

YearMethodkg CO2 per kWh
2023build_margin0.086
2023CM_wOM0.75_wBM0.250.3435
2023simple_OM0.4293
2021CM_wOM0.75_wBM0.250.4261
2021simple_OM0.4589

Secretaria de Energia, Calculo del Factor de Emision de CO2 de la Red Argentina de Energia Electrica (factor_de_emision_2013_a_2023.xlsx)

Attestations are recorded on Base Sepolia, a test network.