Sylvera × EcoWealth · an EWP receipt, expressed as a valid CDOP record (concept demo)

Read this first. Act one narrates EWP's real settlement/retirement event shape (contract 0x76c17C…A14B, Base mainnet) against the recon's own worked example (workId 14). Act two's JSON record is a concept mapping Concept, but the validation run against it is Real: we actually executed CDOP's own documented tool against CDOP's own published schema, on this record, and the output shown is unedited.

Act One: Live shape

EWP already produces the substance CDOP asks for

A work packet settles on-chain

Funded, claimed, proof-checked (photo + GPS + signature), approved, settled: a real transaction on Base mainnet, carrying a wage and a computed ecological footprint.

$ ewp:work:settle --id 14 ✓ settled workId=14 tx=0x… (Base, contract 0x76c17C…A14B)

Its footprint is retired, with a named beneficiary

A share of the settled work's carbon footprint is retired through the Klima Retirement Aggregator on Base, and by EcoWealth's own standing law, the retire beneficiary is never the signer or sender. That's already a distinct, named field in our own data, CDOP just happens to have a place for it with the same name.

retireCreditViaKlima(carbonClass, amount, beneficiary=0x9166…, detail="EWP workId 14") ✓ retired txHash=0x9c14…f02e beneficiary≠sender=true

What EWP already has, in CDOP's own vocabulary: a project reference (the credit class), a unit (quantity, status: retired), a vintage, a serial-equivalent identifier, and, the one that matters most here, a retirement_beneficiary that is provably not the sender. Nothing new has to be invented; it has to be relabeled.

Act Two: Concept mapping, real validation Validation: Real

The same packet, as a CDOP `Unit_Description` record

The JSON below is a concept mapping, EcoWealth has not submitted anything to the CDOP repo. But every value on the right is either a real EWP field or a clearly-labeled illustrative identifier, and the schema it's checked against is CDOP's actual, current, public file, fetched fresh, not cached from memory.

EWP's own settlement shape

{
  "workId": 14,
  "contract": "0x76c17C…A14B",
  "chain": "Base (8453)",
  "signer": "0x034F…c89",
  "beneficiary": "0x9166…",
  "creditClass": "Regen Network:
    City Forest Credits",
  "vintage": "2024",
  "status": "retired",
  "quantity_tCO2e": 1,
  "txHash": "0x9c14…f02e"
}

Mapped into CDOP's Unit_Description fields

{
  "project.current_registry_project_id":
    "REGEN-NETWORK:CITY-FOREST-CREDITS:0x0008f3",
  "unit.metric": "tCO2e",
  "unit.owner_account_id": "0x034F…c89",
  "unit.retirement_beneficiary":
    "EcoWealth EWP: settled workId 14",
  "unit.serial_number":
    "EWP-BASE-0x76c17C-WORK-14-RETIRE",
  "unit.status": "Retired",
  "unit.type": "Removal",
  "unit.quantity": 1,
  "vintage.vintage": "2024-01-01"
}

Running it: real terminal output, both attempts

# fetched the real, current schema straight from the CDOP repo $ curl -s -o Unit_Description.schema.json \ https://raw.githubusercontent.com/Carbon-Data-Open-Protocol/Carbon-Data-Open-Protocol/main/json_schema/Unit_Description.schema.json # installed CDOP's own documented validator $ pip install check-jsonschema # first attempt — our own draft had a real mistake $ check-jsonschema --schemafile Unit_Description.schema.json ewp-work14-as-cdop-unit.json Schema validation errors were encountered. ewp-work14-as-cdop-unit.json::$.vintage.vintage: '2024' is not a 'date' # fixed: vintage.vintage → "2024-01-01" (schema requires format:"date", not a bare year) $ check-jsonschema --schemafile Unit_Description.schema.json ewp-work14-as-cdop-unit.json ok -- validation done

The full record, both attempts, and the exact commands are in evidence.json, reproducible by anyone with curl, pip, and five minutes.

Act one is real, ours, and already running. Act two is a mapping we drafted, not a Sylvera-published artifact, but the validation step is not a mockup: CDOP's own tool, checked against CDOP's own schema, said ok. The rail exists; the receipt fits; nobody has filed the mapping doc yet.

→ See the mapping doc and export concept in the Agent Kit

← Back to the hub

EcoWealth Corporation · Prepared by Brandon Kelly · [email protected]
Unlisted concept page, noindex, nofollow. Act one narrates real EWP contract/event shapes; no live call was made from this page. Act two's JSON record is a concept mapping, clearly labeled; the schema-validation run against it is real and independently reproducible. No relationship with Sylvera / CDOP exists or is claimed; nothing has been submitted to the CDOP repository.

A settled work packet, fitted into Sylvera's own open schema, and validated for real