regen-1block 28,311,220 · 2026-08-12 21:27 UTCgenerated 2026-08-12 21:27 UTCpublic chain data

Real regeneration, counted straight off the chain

Every project, credit and vote below is real work on real land, read straight off Regen Network's own public ledger, not a marketing page. Nothing on it can be quietly edited after the fact: this is the plain, honest measure of how much regeneration this network has actually done, credit by credit.

Commons is the full inventory. Every credit class, every registered project, every batch ever issued, and every governance proposal sit on this one page, read straight off the chain. Explorer only ever shows one address at a time. The hub ties all five tools together, and the same verified projects listed here can be funded directly on this site's own work board. Nowhere else can you see everything this chain has actually verified, at once, including the governance repair that's mid-vote right now.

187projects
608,881hectares
159,027credits retired
13credit classes
69proposals
14validators
The work behind numbers like these is fundable and claimable on this site's own board. Browsing is free, claiming is free, your wallet is your name. Agents start at vealth.net/mcp.

What a credit is called on this chain

MBS01credit class-001project-20240601vintage from-20340531vintage to-001batch

A credit denom says everything about itself and nothing about what it means. This one holds 73,245 retired credits from Mangrove Forest: Marereni, covering work done between 1 Jun 2024 and 31 May 2034. There are 80 of these on the ledger. All of them are below.

Retire a credit right now

regen-compute MCP, verified live

Everything below this line is inventory: read it at your own pace. This part is not. 4 steps, no REGEN token to buy first and no Regen wallet to set up.

  1. Browse what's for sale

    Live sell orders across all 13 credit classes, priced and ready.

    Browse credits ↗
  2. Retire it

    $0.25 from any Base wallet, one real attributed retirement with a certificate on-chain. Or retire directly on Regen's own marketplace.

    No REGEN neededOur own retire door
    Retire a credit →
  3. Get the certificate

    Every retirement is on-chain and public, by tx hash.

    Look up a tx ↗
  4. Vote on 2 open proposals

    #71 closes 2026-08-19, #70 closes 2026-08-17. Do nothing and your validator votes for you.

    Needs staked REGENEcoWealth's own
    How to vote →

What has actually been issued

/regen/ecocredit/v1/batches + /supply/{denom} + marketplace/v1/sell-orders + tx_search

Per batch supply is the only place the real split lives. Across all 80 batches, 1,824,435 credits have been issued. Retired means permanently claimed and gone. Cancelled means taken off this ledger, usually because the credit was bridged somewhere else.

tradable 1,258,408 (69%) retired 159,027 (8.7%) cancelled 407,001 (22.3%)
130 of the 187 registered projects have never issued a single credit. Registration and issuance are separate acts, and the gap between them is the honest measure of how much of this ledger is live. 57 projects carry the 80 batches above.
classprojectsbatchestradableretired (all-time)cancelledretired, tracked window (26wk)
MBS0133980,73073,27000 · dormant
C03121981,16746,211402,3752,092.4
USS012471,3966,59200 · dormant
C06202462,1933,1844,5660 · dormant
C02121212,69920,26960119.6
BT012226,3463,88701
C081123,1431,00000 · dormant
C0131304,53900 · dormant
KSH01117117500 · dormant
C051123000 · never

Of the credit classes carrying any batches, only 3 were retired at all in the tracked 26-week window (C03, BT01, C02). Everything else above shows either its all-time total only, or has never been retired.

Is retirement demand growing?

rpc-regen.ecostake.com /tx_search, weekly, 26 weeks binary-searched from the RPC's real retention floor

Counting retirement transactions says nothing here: one automated retirer submits a MsgRetire roughly every 5 minutes, every week, which holds the raw transaction count flat around 2,000/week regardless of what anyone else does (see the tx-count comparison below). Counting credits retired tells a different story.

Credits retired per week is declining, down 95.9% from the first tracked week to the most recent complete one. The week of 2026-02-16 saw 183.2 credits retired; the most recent complete week (2026-08-03) saw 7.5. The single busiest tracked week was 2026-04-20 at 189.8 credits; the quietest complete week was 2026-07-13 at 7.4. In 22 of the 25 complete tracked weeks, every single retirement came from one wallet. That reads more like the record of one actor's activity than a broad market, and a rebuild every few weeks is the only way to tell whether that changes.

For comparison, the raw ecocredit message count (every MsgRetire, MsgBuyDirect, MsgCreateBatch, ...; see regen-activity-history.json) reads roughly flat over the same kind of window: that is exactly the blind spot, a constant transaction count from one bot looks like nothing is changing, while the credits it actually retires collapsed.

weekcredits retiredretire txsunique owners
2026-02-16183.22,0361
2026-02-23182.22,0251
2026-03-02182.62,0192
2026-03-09181.72,0191
2026-03-16181.82,0201
2026-03-23181.62,0192
2026-03-30181.32,0141
2026-04-06181.22,0131
2026-04-13181.82,0201
2026-04-20189.82,0371
2026-04-27177.21,9561
2026-05-0493.91,9641
2026-05-1110.12,0251
2026-05-18102,0062
2026-05-25102,0091
2026-06-01102,0041
2026-06-08101,9971
2026-06-15101,9931
2026-06-228.32,0061
2026-06-297.51,9971
2026-07-067.52,0011
2026-07-137.41,9741
2026-07-207.41,9821
2026-07-277.52,0071
2026-08-037.52,0051
2026-08-10 (in progress)1.33501

When credits were actually issued

/regen/ecocredit/v1/batches, grouped by issuance_date

Not from a transaction search: at least one active issuer submits its batch-creation messages wrapped inside an authz MsgExec, which hides the real action from a message-type search entirely (verified live: a direct tx_search for MsgCreateBatch returns a confident, silently wrong zero for the last six months despite real batches landing inside that window). Each batch's own issuance_date is written by the module regardless of how the transaction that produced it was built, so it is the reliable source here.

monthbatches issued
2022-054
2022-064
2022-106
2022-113
2023-037
2023-048
2023-062
2023-091
2023-116
2024-031
2024-041
2024-052
2024-081
2024-101
2025-023
2025-036
2025-053
2025-063
2025-072
2025-1010
2025-113
2026-011
2026-051
2026-061

The live sell-order book

/regen/ecocredit/marketplace/v1/sell-orders

26 sell orders are open on the marketplace right now, across 6 credit classes. Verified live 2026-08-11: /regen/ecocredit/marketplace/v1/buy-orders answers HTTP 501 Not Implemented on every LCD (light client daemon, a node's own public read API) tried. This chain's marketplace module has no standing buy-order book: a buy is an atomic MsgBuyDirect against an existing sell order.

classopen orderstotal quantityUSD-priced ordersmin $/creditmax $/creditavg $/credit
C0211379.98$0.2000$80.00$13.22
C0352175$0.0198$5.00$1.43
USS01571,259.65$0.0011$0.7200$0.1517
KSH012399.22$0.0590$45.00$22.53
BT0127,454.22$0.0034$0.3500$0.1767
C0611,199.31$0.0375$0.0375$0.0375

Prices above cover only orders asking for a USD-pegged stablecoin (USDC or a bridged form of it) at the chain's own live allowed-denom exchange rate. Orders asking for REGEN, or for a denom no longer on the chain's current allowed-sale-denom list, are counted in "open orders" and "total quantity" but excluded from the price columns rather than converted with a guessed rate.

Governance, with the messages decoded

/cosmos/gov/v1/proposals

Every explorer shows a proposal's title. The title is not the change, and on this chain it is often not even there: the gov v1 API returns an empty title for 50 of the 69 proposals. 40 of those still carry a real title, buried inside the legacy content of their own message. 10 have no title anywhere on chain and can only be read by decoding what they do. All 69 are decoded below.

proposal 1proposal 71
19 keep their title on chain 40 hide it inside legacy content 10 have no title at all

Bar height is the REGEN cast on that proposal. The dotted line marks proposal 52, where the chain moved to gov v1 and titles started being recorded in the proposal itself. Hollow bars are open votes with nothing counted yet.

2 proposals are open for voting right now, with nothing cast so far. Anyone with staked REGEN can vote directly. If a delegator does nothing, their validator's vote is counted for them, which is why the set of 14 validators below decides most outcomes.
Read the participation figures carefully. Vote shares are counted against the 85,054,259 REGEN bonded today, not against the stake that existed when an older proposal closed. Bonded stake has fallen since, so older proposals can show more than 100% and that is a fact about the denominator, not about the vote. The split between yes, no, abstain and veto is exact in every case.
71 voting PoA transition (Plan A): set max_validators to 7
What it executes
MsgUpdateParams

Caps the active validator set at 7 validators, unbonding takes 21 days, minimum validator commission 0%.

params: {"unbonding_time":"1814400s","max_validators":7,"max_entries":7,"historical_entries":10000,"bond_denom":"uregen","min_commission_rate":"0.000000000000000000"}

Title comes straight from the proposal record.

How the stake voted

No votes counted yet.

What the proposer wrote
Part of the Proof-of-Authority transition (RFC #70). A standard x/staking MsgUpdateParams — no chain upgrade, effective the moment it passes — setting max_validators from 21 to 7 (the RFC floated 7/11/17). The active set is already 15 and shrinking as validators run at a loss; a smaller curated authority set is cheaper to secure and fund. All other staking params are preserved unchanged. Pairs with the zero-emissions change (votable concurrently).
submitted 2026-08-10 voting closes 2026-08-19 deposit 2,018 / 2,000 REGEN proposer regen1jfheyvsah5wqfyawmedme43te056z8gzdnpf3j (EcoWealth, this page's operator)
70 voting Make the stated inflation rate the real one: correct blocks_per_year 4,360,000 to 5,596,247
What it executes
MsgUpdateParams

Fixes REGEN issuance at a flat 3.5% a year, with the bonded target at 60%, blocks_per_year set to 5,596,247 (implies 5.64s blocks).

params: {"mint_denom":"uregen","inflation_rate_change":"1.000000000000000000","inflation_max":"0.035000000000000000","inflation_min":"0.035000000000000000","goal_bonded":"0.600000000000000000","blocks_per_year":"5596247"}

Title comes straight from the proposal record.

How the stake voted

No votes counted yet.

What the proposer wrote
Regen has been minting about 1.284x more REGEN than its own parameters say, for as long as those parameters have been set, and nothing in any dashboard or explorer shows it. This corrects that and nothing else. THE MECHANISM: x/mint pays annual_provisions divided by blocks_per_year, every block. blocks_per_year is 4,360,000, which implies a 7.23 second block. Measured over the last 100,000 blocks the chain actually produces a block every 5.635 seconds, so it makes about 5,596,247 blocks a year. Every block pays a share sized for a year that is 1.284x too short, so the payout overshoots by the same factor. WHAT THAT HAS COST: inflation reads 3.50% and annual_provisions reads 8,371,279 REGEN/yr, but realized emission is about 10,744,895 REGEN/yr, which is 4.49% of supply. The gap is roughly 2,373,616 REGEN a year minted beyond what the parameters describe. Anyone can confirm this without trusting me: take total supply at two heights a few days apart and annualize the difference. That is how I checked it, and it is how it should be checked. WHAT THIS CHANGES: one field. blocks_per_year 4,360,000 to 5,596,247. inflation_max, inflation_min, goal_bonded, inflation_rate_change and mint_denom are read live from the chain and passed through untouched. One standard x/mint MsgUpdateParams, effective on pass, no chain upgrade, no new module. WHAT IT DOES NOT DO: it sets no policy and takes nothing from anyone. It does not decide what the inflation rate should be, it makes the rate the chain actually pays match the rate the chain already says it pays. If the network wants 3.50%, this is how it gets 3.50% instead of 4.49%. If the network wants something else, that is a separate proposal and this one does not prejudge it. HONEST NOTE ON WHO THIS AFFECTS: correcting an over-mint reduces what validators and delegators receive, because they have been receiving the overshoot. I would rather that be a decision than an accident. Block time is not fixed either, so this parameter will drift again as the validator set changes; a future proposal should re-measure rather than assume this number is permanent. DISCLOSURE: I authored proposals #64, #66 and #67 from this address, and I got the bonded-ratio arithmetic in #64 wrong, which is a matter of public record. I hold no staked REGEN; my holdings are committed as governance deposits. Weigh all of that as you see fit. REPRODUCE: /cosmos/mint/v1beta1/params, /cosmos/mint/v1beta1/inflation, /cosmos/mint/v1beta1/annual_provisions, /cosmos/bank/v1beta1/supply/by_denom?denom=uregen, and two /cosmos/base/tendermint/v1beta1/blocks/{height} timestamps.
submitted 2026-08-10 voting closes 2026-08-17 deposit 2,000 / 2,000 REGEN proposer regen1jfheyvsah5wqfyawmedme43te056z8gzdnpf3j (EcoWealth, this page's operator)
69 passed Recover IBC Client with Quicksilver-2

Opening the full record…

67 passed Finish what #64 started: clamp REGEN emissions to a flat 3.50% (inflation_max = inflation_min)

Opening the full record…

66 passed Activate the M013 Burn Pool (Phase 1): stream 15.0% of community-pool revenue to burn

Opening the full record…

65 passed Recover IBC Client with Quicksilver-2

Opening the full record…

64 passed Save the network money: right-size x/mint inflation (goal_bonded 67%→60%, inflation_max 10%→7%) so Regen can refocus on revenue

Opening the full record…

63 failed LiquidityDAO Emissions Transfer #6

Opening the full record…

62 passed Regen Network: Software Upgrade Proposal - v7

Opening the full record…

61 passed LiquidityDAO Emissions Transfer #5 – Nov 26, 2025 – Jan 14, 2026

Opening the full record…

60 passed LiquidityDAO Emissions Transfer #4 – Oct 21–Nov 26, 2025

Opening the full record…

59 passed Engage X-Influencers - Phase 1 - Pilot

Opening the full record…

58 passed LiquidityDAO Emissions Transfer #3 – Sept 13–Oct 21, 2025

Opening the full record…

57 passed Request for the funding for the Tokenomics working group in Q4

Opening the full record…

56 passed Revive REGEN<>AXELAR client

Opening the full record…

55 passed LiquidityDAO Emissions Transfer #2 - Aug 26 - Sep 13, 2025

Opening the full record…

54 passed LiquidityDAO Emissions Transfer #1 (Aug 11–26, 2025)

Opening the full record…

53 passed Signalling Vote: Interest to explore further Fixed Cap, Dynamic Supply for $REGEN

Opening the full record…

52 passed Technical change associated with proposal 49, post-upgrade

Opening the full record…

51 passed Technical change associated with proposal 49

Opening the full record…

50 passed Regen Network: Software Upgrade Proposal – v6.0

Opening the full record…

49 passed Restructuring Liquidity - 15% Emissions to Liquidity DAO

Opening the full record…

48 passed Creates the USS credit type, Umbrella Species Stewardship. One credit means: Approximately one hectare of umbrella species habitat stewarded for biodiversity conservation for one year, measured using a composite index which tracks improvements in Umbrella Species Health (USH), Habitat Quality (HQ), and implementation of species-specific conservation interventions (USpToC).

Opening the full record…

47 passed Creates the MBS credit type, Marine Biodiversity Stewardship. One credit means: generic quantification of project activities adopted to restore biodiversity in marine ecosystems, with specific units defined at the credit class or project level.

Opening the full record…

46 passed Reactivate expired IBC client for Umee

Opening the full record…

45 passed Reactivate expired IBC client for UX

Opening the full record…

44 passed Decrease MaxValidators value

Opening the full record…

43 failed Lets credits be sold for usdc on the marketplace.

Opening the full record…

42 rejected REGEN Hub v4 Software Upgrade ⭐

Opening the full record…

41 passed Adjustment of Minimum and Maximum Inflation Parameters

Opening the full record…

40 passed Creates the BT credit type, BioTerra. One credit means: weighted 10m^2 score of long-term restoration/preservation in the project area.

Opening the full record…

39 passed Lets credits be sold for usdc on the marketplace.

Opening the full record…

38 passed Param change for InflationRateChange

Opening the full record…

37 passed Signalling only. Nothing executes on chain.

Opening the full record…

36 passed Sets the fee to create a new credit class at 5,000 REGEN.

Opening the full record…

35 passed Creates the KSH credit type, kilo-sheep-hour. One credit means: number of sheep * hours grazed / 1000.

Opening the full record…

34 failed Revive Evmos IBC Client

Opening the full record…

33 passed Increase Max Gas / Max Bytes

Opening the full record…

32 passed Revive Axelar IBC Client

Opening the full record…

30 passed Required Final Offset Amount - Community Spend Proposal for purchasing and retiring NCT

Opening the full record…

29 passed Changes which credit vintages the eco.uC.NCT basket will accept.

Opening the full record…

28 passed Regen Ledger v5.1 Upgrade

Opening the full record…

27 passed Increase Minimum Proposal Deposit to Prevent Spam Attacks

Opening the full record…

26 passed Liquid Staking: Enabling ICA on Regen for Quicksilver

Opening the full record…

25 passed Allocate the missing REGEN for City Forest credits offset

Opening the full record…

24 passed Stops credits being sold for ibc/F694C7575DF3B8128746FA6576830DA27891D5A322DF5DECB066288FC4948F76.

Opening the full record…

23 passed Proceed with City Forest Credits Offset

Opening the full record…

22 passed Regen Ledger v5.0 Upgrade

Opening the full record…

21 passed Signal Proposal: Offset Regen Validator Set

Opening the full record…

20 passed Add REGEN to the Regen Marketplace currency AllowList

Opening the full record…

19 passed Regen Ledger v4.1 Upgrade

Opening the full record…

18 passed Add e-Money EEUR to marketplace allow list

Opening the full record…

17 passed Adding Axelar USDC as a marketplace currency

Opening the full record…

16 rejected Adding Axelar USDC as a marketplace currency

Opening the full record…

15 passed Add Gravity USDC to Regen Marketplace Currency Allow List

Opening the full record…

14 passed Regen Ledger v4.0 Upgrade

Opening the full record…

13 passed Adoption of Currency Allow List Criteria

Opening the full record…

12 passed Climate Wiki - Community Pool Funding

Opening the full record…

11 passed Community Assistance Regarding Lost Genesis Wallets

Opening the full record…

10 passed Decrease Voting Period

Opening the full record…

9 passed Regen Ledger v3.0 Upgrade

Opening the full record…

8 passed Credit Class Creator - Regen Registry

Opening the full record…

7 passed IBC Patch Upgrade

Opening the full record…

6 passed Set a minimum validator commission rate of 5%

Opening the full record…

5 passed Regen Ledger v2.0 Upgrade

Opening the full record…

4 passed Regen Ledger v2.0 Upgrade - Signalling Proposal

Opening the full record…

3 passed Increase MaxValidators value

Opening the full record…

2 passed Enable IBC transfers

Opening the full record…

1 passed Enable REGEN Transfers

Opening the full record…

How to vote yourself

/cosmos/staking/v1beta1/delegations/{you}

Staked REGEN carries a vote whether or not you use it. Cast nothing and your validator casts it on your behalf, which is how most of the record above was written. Voting yourself overrides them, and you can do it any time before a proposal closes.

Balance looking lower than expected? REGEN deposited on a proposal marked deposit above leaves your visible balance and sits in escrow until that proposal resolves — it is still yours. Paste any address to see visible balance, bonded stake and locked deposits together, live off the ledger.

Check whether you have a vote

This asks your browser wallet for your Regen address, then asks the public ledger what you have staked. Nothing is signed and nothing is sent. If you have no wallet extension, the commands below still work.

Cast it

Any Regen wallet with a governance screen can do this. From a terminal, one line per proposal, replacing yes with no, abstain or no_with_veto and YOUR_KEY with your key name:

Proposal 71, closes 2026-08-19
regend tx gov vote 71 yes \
  --from YOUR_KEY --chain-id regen-1 \
  --node https://rpc.regen.network:443 \
  --gas auto --gas-adjustment 1.4 --fees 5000uregen
Proposal 70, closes 2026-08-17
regend tx gov vote 70 yes \
  --from YOUR_KEY --chain-id regen-1 \
  --node https://rpc.regen.network:443 \
  --gas auto --gas-adjustment 1.4 --fees 5000uregen

Your vote counts for exactly the REGEN you have bonded. If that is a small number it still changes the record, because the record currently shows almost nobody turning up.

Who the votes actually come from

/cosmos/staking/v1beta1/validators

14 validators carry the 85,054,259 REGEN that is bonded. A delegator who does not vote is voted for by their validator, so this list is the working shape of the electorate. The largest 3 hold more than a third of the stake between them, which is the share needed to stop the chain.

ecoBridge.earth19.1%16,232,832
Regenerator10.5%8,918,819
Simply Staking10.5%8,898,756
KalpaTech9.3%7,928,211
polkachu.com9.2%7,854,371
Vitwit (Previously Witval)7.9%6,714,367
Earthist7.7%6,522,447
0base.vc6.7%5,723,954
Chainflow5.5%4,712,402
ECO Stake 🌱 | REStake.app4.8%4,065,897
RydOne2.9%2,425,153
Alex (Bambarello) Validator2.1%1,803,056
MekongLabs1.9%1,630,532
Start-Staking.cc1.9%1,623,463

The projects

/data/v2/metadata-graph/{iri}

Each project's real name, place, size and method live in a structured public record (a JSON-LD document, reached through its metadata IRI), and all 187 of them resolved. That is the part the app shell will not hand to a machine. Search, filter and sort below, or jump straight to a class or country with one click; everything runs in the page.

BT01-001BT01

El Globo Habitat Bank

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Cuchilla Jardín-Támesis Integrated Management District (DMI), Colombia

340 ha2022 to 2052Terrasos

El Globo is the first project in Colombia to issue Voluntary Biodiversity Credits. It is located in the "Cuchilla Jardín-Támesis" Integrated Management District (DMI). Known as the "water star" of southwestern Antioquia, this area is a prioritized ecosystem for conservation. Here ecosystem preservation, forest enhancement and restoration activities are implemented to generate positive and permanent impacts on biodiversity. The project has a 30-year financial, technical and legal structure for operation, securing biodiversity gains in time. The area has one of the few remnants of Native High Andean Forest still preserved in the region and it is a registered Habitat Bank at the Ministry of Environment and Sustainable Development of Colombia.

Tropical ForestEcosystem PreservationForest Enhancement
issued 10,000retired 1,881tradable 8,1191 batch
BT01-002BT01

Aguadulce Habitat Bank

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Nilo, Cundinamarca, Colombia

125 ha2022 to 2022Terrasos

Aguadulce – Río Sumapaz Habitat Bank, located in the province of Alto Magdalena, Cundinamarca, Colombia, spans over 124.76 hectares and aims to preserve and restore two key ecosystems: tropical dry forest and premontane humid forest. Through this initiative, Terrasos promotes biodiversity conservation and offers biodiversity credits to offset environmental impacts. This project offers an opportunity for buyers to contribute to the protection of endangered species while supporting ecosystem restoration.

Tropical Dry ForestPremontane Humid Forest
issued 20,233retired 2,006tradable 18,2271 batch
C01-001C01

The Mai Ndombe REDD+ Project

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Mai Ndombe, Democratic Republic of the Congo, Africa

299,640 ha2011 to 2041Wildlife Works Carbon LLC
REDD
issued 4,189retired 4,189tradable 06 batches
C01-002C01

The Kasigau Corridor REDD Project - Phase II The Community Ranches

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Taita–Taveta, Kenya

169,741 ha2010 to 2039Wildlife Works Carbon LLC
REDD
issued 300retired 300tradable 06 batches
C01-003C01

Evio Kuiñaji Ese´eja Cuana

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Puerto Maldonado, Madre de Dios, Peru

7,653 ha2011 to 2030Ese´Eja Infierno Native Community
REDD
issued 50retired 50tradable 01 batch
C02-001C02

King County Urban Forest Carbon Project

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

King County, Washington, USA, North America

6 ha2018 to 2118King County Department of Natural Resources & Parks
Tree Preservation
issued 265retired 239tradable 261 batch
C02-002C02

Sandy Cross Forest Preservation Project

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Lexington, Ohio, United States of America, North America

53 ha2021 to 2061Western Reserve Land Conservancy
Tree Preservation
issued 6,497retired 5,935tradable 5621 batch
C02-003C02

Buena Vista Heights Conservation Area

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Elizabeth Township, Pennsylvania, United States, North America

50 ha2020 to 2060Allegheny Land Trust
Tree PreservationBeZero Carbon A
issued 7,709retired 5,190tradable 2,5191 batch
C02-004C02

Harvey Manning Park Expansion

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Issaquah, Washington

6 ha2021 to 2061City of Issaquah
Tree Preservation
issued 6,409retired 3,397tradable 3,0121 batch
C02-005C02

Evergreen & East Preservation Project

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Richmond, Virginia

30 ha2019 to 2059Enrichmond Foundation
Tree Preservation
issued 1,500retired 1,451tradable 491 batch
C02-006C02

St. Elmo Preservation Project

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Chattanooga, Tennessee, United States

58 ha2021 to 2061Lookout Mountain Conservancy
Tree Preservation
issued 8,714retired 2,268tradable 6,4461 batch
C02-007C02

Reforesting Des Moines

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Des Moins, Iowa

2021 to 2047Trees Forever
Tree Planting
issued 440retired 295tradable 851 batch
C02-008C02

Treasure Valley Municipal Parks Project

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Boise, Idaho, United States

10 ha2021 to 2047Treasure Valley Canopy Network
Tree Planting
issued 57retired 57tradable 01 batch
C02-009C02

Travis County Floodplain Reforestation Program

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Travis County, Texas

31 ha2021 to 2047Tree Folks
Tree Planting
issued 100retired 100tradable 01 batch
C02-010C02

Ballinger Open Space Restoration

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Shoreline, Washington

31 ha2018 to 2044Tree Folks
Tree Planting
issued 216retired 216tradable 01 batch
C02-011C02

Lake County Forest Preserve

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Lake County, Illinois

10 ha2021 to 2047Lake County Forest Preserve District
Tree Planting
issued 615retired 615tradable 01 batch
C02-012C02

Fox River Bluffs Planting Project

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Lake County, Illinois

16 ha2020 to 2046Kendall County Forest Preserve District
Tree Planting
issued 506retired 506tradable 01 batch
C03-001C03

Rimba Raya Biodiversity Reserve Project

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Central Kalimantan, Indonesia

BeZero Carbon AAA
issued 34,251retired 2,717tradable 101 batch
C03-002C03

REDD+ Project Resguardo Indigena Unificado Selva de Mataven (RIU SM)

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Vichada, Colombia

BeZero Carbon B
issued 41,369retired 13,643tradable 27,7211 batch
C03-003C03

Reduced Emissions from Deforestation and Degradation in Keo Seima Wildlife Sanctuary

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Mondulkiri, Cambodia

BeZero Carbon AAA-
issued 24,404retired 2,050tradable 151 batch
C03-004C03

The Kasigau Corridor REDD Project - Phase II The Community Ranches

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Taita–Taveta, Kenya

BeZero Carbon BBB
issued 6,873retired 3,977tradable 2,8941 batch
C03-005C03

Florestal Santa Maria Project

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Mato Grosso, Brazil

issued 41,161retired 2tradable 28,4223 batches
C03-006C03

The Mai Ndombe REDD+ Project

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Mai-Ndombe, Democratic Republic of the Congo

BeZero Carbon AA-
issued 55,282retired 21,994tradable 5,3591 batch
C03-007C03

Pacajai REDD+ Project

Registry record held by Regen Ledger, carried verbatim. Vealth does not verify or claim these outcomes.

Pará, Brazil

BeZero Carbon C
issued 15,286retired 39tradable 3,4093 batches

Showing the first 24 of 187 projects. The rest load on their own; nothing is hidden.

Check every number yourself

nothing here rests on our word

Each figure on this page comes from one of these public endpoints. Run them and you get the same answers, whether this page exists or not.

/regen/ecocredit/v1/classes
/regen/ecocredit/v1/projects
/regen/ecocredit/v1/batches
/regen/ecocredit/v1/supply/{denom}
/regen/ecocredit/v1/params (allowed sale denoms)
/regen/ecocredit/marketplace/v1/sell-orders
/cosmos/gov/v1/proposals
/cosmos/staking/v1beta1/pool
/data/v2/metadata-graph/{iri} (registry)
rpc-regen.ecostake.com /tx_search (retirement volume trend, via collect-regen-retirement-trend.ts)

Ledger https://regen-api.polkachu.com, registry https://api.registry.regen.network. Everything on this page, as one machine readable file: regen-commons.json.

Provisioned by EcoWealth · Digital Provisioning Protocol · verify this page