Vealth · Regen Network · Written for Regen Network Development

A course for Regen Network, across all directions.

A roadmap for the ledger's infrastructure on a utility basis, written for RND at its request, with vealth as Regen Network's app for digital-to-physical regeneration: provisioning ecological wealth. Here it is: the thesis, what happens if everyone does it, where things stand, the map, the steps, what still has to be built, the money, and who is taken care of how.

Version 8, November 2026. By EcoWealth, steward of the Regen Tokenomics Working Group. Unaffiliated with Regen Network Development PBC, not reviewed or endorsed by them. The votes recorded here passed on regen-1; every step still ahead needs its own vote or its own build.

The whole course at a glance

Four lanes, every track, its state and its next move.

DoneLiveBuildingNextVoteCandidate

Each bubble links to the place that proves it. The same map as an image: roadmap-map.svg.

In one screen

The course, in five lines.

What changed since version 7

Two votes rejected, nothing paid yet, the chain a patch on.

Version 7 went to RND in September 2026, with its figures read at block height 29,019,100 on 27 September. This is what the chain, the board and the Regen forum show now. Every chain figure in this section was read at block height 29,816,486 on 18 November 2026 (06:04 UTC) from https://regen-api.polkachu.com, unless a line names another read. What has not happened is said as plainly as what has.

The thesis

Regeneration will have to fight for its place.

The next decade builds data centers, solar fields and robots faster than anything ecological has ever moved. Regeneration keeps up by using the same technology: agents that write and verify work, compute that turns a settled hour of real labor into a credit, and money that moves only on proof.

That machine already runs. It is called vealth, and this course proposes it as Regen Network's app for digital-to-physical regeneration. A public board posts real maintenance work on real places. Anyone with a wallet claims a job for free, proves it with photos and location, and a human accepts it. The worker is paid in dollars, in any token, or in provision (food, housing, the life). Agents write the work, check the proof and keep the records. Every place has a standing that rises only from settled work and lapses when the work stops.

Regen Ledger is where a settled hour becomes a credit of record. The vote that adds the verified stewardship hour to Regen's registry puts vealth's unit of work next to carbon and biodiversity. So the roles are fixed: vealth leads the program, Regen keeps the book, the community pool pays for settled work, and the REGEN coin is worth what the book carries. Put plainly, vealth is Regen Network's app for digital-to-physical regeneration: the place where a credit, a payment or a line of compute becomes an hour of real work on real ground, and the ground's improvement comes back to the ledger as a record. That is what provisioning ecological wealth means.

The product test under all of it: AI and blockchain have to be so easy and so logical to opt into that it is hard not to do both. That is what yields real productivity, alignment with nature, and more abundance.

If everyone did this

It is not complicated.

Imagine every data center, solar field, town and robot fleet posted the maintenance it owes to the ground around it, and paid on proof. Every hour of that work would land as a credit on one book. Every pool of money meant for nature would pay on receipts instead of promises. Validators would be paid by that flow. The coin would be worth the size of the book. Regen's registry would be the standard record of verified labor on the planet, and RND would be the company that keeps it, with vealth as the app people and agents use to do the work.

They should be doing this. That is the whole offer, and the rest of this page is how.

Where things stand, November 2026

Eight votes on the ledger, a board full of work, a pool on Base.

8
votes the Working Group put up have passed
A burn stream, an inflation clamp, an honest block count, eleven validators, emission to zero, the verified stewardship hour, the first program tranche, the validator floor. One no vote across all eight.
~—
REGEN in the community pool
Read 18 November 2026, block 29,816,486: 3,672,775
— · — · —
credit classes, projects, batches
Anyone may create a class for five thousand REGEN; credits sell for USDC or REGEN (read 18 November 2026)
—
packets across — data-center, solar and water places
None funded (the board's funded count reads 0 on 18 November 2026); settle in dollars, any token, or provision

The mint issues — REGEN a year. Agents author and verify work around the clock. A REGEN and ECO pool exists on Base, and its depth is on the baseline page. On Robinhood Chain the board has a twin contract; a REGEN program there is a candidate and would need its own vote, with liquidity built by incentives to others, never by the house wallet. Upstream, the Cosmos software Regen runs on has shipped the new version and the proof-of-authority module Regen's plan needs. On 18 November 2026 the newest published Cosmos SDK release is v0.55.1 and the newest CometBFT release is v0.40.0; regen-1 runs SDK v0.53.6 and CometBFT v0.38.21 (node info, 18 November 2026), so it is still two minor lines behind on each. The proof-of-authority module's own release notes, read on 5 September 2026, require SDK v0.55.0 and CometBFT v0.40.0; they were not read again for this version.

The community pool paid out three votes in September: the LiquidityDAO's 867,000 REGEN (proposal 76, passed 11 September), the program tranche's 100,000 and the validator floor's 396,000 (proposals 77 and 78, passed 14 September). Two more of the Working Group's went to a vote and ended rejected on turnout, with none against: the upgrade coordination standard (proposal 80, 1 October) and the digital stewardship authority (proposal 81, 2 October).

Built since the votes. The board records verified hours on a job, claimed by the worker and accepted by the human, and marks which jobs a credit batch may draw from. The first verified-stewardship-hour class exists: VSH01, created on the ledger on 2026-09-07, the class fee burned, EcoWealth's account as admin and issuer. The WORK basket that turns VSH01 credits into one token each followed on 2026-09-08. The bridge carried REGEN to Osmosis and to Base and back the same day. An hourly loop watches proposal 77's candidate packets. The Regen Compute retirement count reads from three independent sources that agree (the retirement tracker rebuilt on 18 November 2026 says so on its page). These numbers, read at one block height and rebuilt by script: the baseline. The chain figures above were read on 18 November 2026 at block height 29,816,486.

What is on the ledger, and how the numbers go up

Four records make a claim real. Ten numbers are the pulse.

Regen Ledger is the one public book where an ecological claim exists as four records anyone can read: a class (the rules), a project (the place), a batch (the issuance) and a retirement (the permanent certificate). Credits sell for real dollars on the ledger's own marketplace, the community pool is governed by vote, the data module anchors any record for a fraction of a cent, and since this summer the ledger holds a labor unit, so an hour of verified work can be recorded next to a ton of carbon. The numbers below are the ledger's pulse. Every step in the course is a lever on one of them.

Regen's own account of its scale, published on its forum in December 2025 (The State of Regen 2025, Gregory Landua, thread 565), carried here as Regen's figures, not re-audited:

Regen's figure, December 2025Value
Live tokenized ecological credits$9.3 million
Purchased and retired$2.4 million
Credits issued, and retired6.1 million issued, 1.4 million retired (about 23 percent)
Land under verified regenerative management420,000 hectares and more
Carbon sequestered, estimated5.2 million tonnes of CO2e
On-chain market volume in 2025about $2.7 million
Participantsover 20,000

The chain figures in the next table were read at block height 29,816,486 on 18 November 2026, except the credit units, which come from the rebuilt baseline page (block height 29,816,601, 18 November 2026, 06:15 UTC), and fee income and the price of a unit of use, which come from the rebuilt fee line (its own height and day are named in the row). For credit supply, "gross issued" means tradable + retired + cancelled; "issued net of cancellations" means tradable + retired. Cancelled credits are quoted separately. Regen's separately published issued count uses its own method and is larger; the two methods should not be conflated.

On the ledgerTodayWhat moves it upWhere in the course
Credit classesfourteen, VSH01 the newestThe first verified-stewardship-hour class, then one class per method that needs its own rulesStep 4
Projectsone hundred eighty-nineEvery place on the board with settled hours becomes a projectStep 6
Credit batcheseighty-three, none of them under VSH01Each settled batch of hours becomes a batch of verified-stewardship-hour creditsStep 6
Credit units issuedabout 1.42 million net of cancellations; about 1.83 million gross, including about 407 thousand cancelledHours settled on the board and accepted by a human, issued as creditsSteps 5 to 7
Credit units retiredabout 162 thousandBuyers and RND retiring hours for a place; Regen Compute and ecoBridge retirements countedStep 10
Marketplace sell ordersforty-twoVerified-stewardship-hour credits listed for USDCStep 6
Community pool3.67 million REGEN, after proposals 76, 77 and 78Fees flowing in after the upgrade; payouts only on receipts; unspent tranches returnedSteps 5, 9, 11
Bonded stake and validatorsabout eighty million REGEN (80.2 million), eleven validatorsThe operating floor, paid on 14 September, keeps the eleven; the upgrade pays them from feesSteps 9, 11
Fee incomeabout seventy-seven REGEN in the thirty days to 18 November 2026 (fee line, block 29,816,650); eighty-three percent to the validators, seventeen percent to the poolRegistry activity routed to validators, the pool and the program by the upgradeSteps 9, 11
Price of a unit of usethe median transaction paid five thousandths of a REGEN in the thirty days to 18 November 2026 (fee line, block 29,816,650)A posted schedule of registry fees, set by the upgradeStep 11
Anchors on the data module55 sent by the steward account, the newest on 18 November 2026 at 00:25 UTC; which of them, if any, is the weekly batch root is not readEvery program record pinned on Regen on a scheduleStep 10

The map, part one

What moves on each side.

On Regen Ledger

  • Governance. The Working Group drafts, the community votes, validators decide in practice. The first program tranche and the validator operating floor passed in September; the upgrade coordination standard and the digital stewardship authority ended rejected on turnout in October; next, one chain upgrade.
  • The community pool. Protocol money, moved only by vote. It pays for settled work through a payout account named in the proposal.
  • Credits. A settled hour on the board becomes a verified-stewardship-hour batch. Retiring it produces the certificate. Carbon and biodiversity credits stack on the same places.
  • The burn stream. A standing trickle from the pool to an address nobody holds.
  • Anchors. Content hashes written to the ledger's data module, the cheapest unit of ledger use.

On vealth

  • Post, claim, prove, accept, settle. Work is posted with a definition of done. A worker claims for free, proves with photo hashes and location, a human accepts, and settlement lands in dollars, any token (including REGEN) or provision. The board reads the chain and records what moved. It never holds, prices or issues a token.
  • Standing. Computed only from settled, accepted work, per place. Lapses when the work stops.
  • Agents. Loops author one cited piece of work at a time, verify proofs, post to the board, keep the libraries honest.
  • The swap loop. Built and switched off. When it is armed, each of the two buys that can call it, the daily NET buy and the ECO dime rail (stopped), is wired to do three jobs: a stated slice of it is offered in REGEN to one open job through the board's token door, the run posts one more job, and the swap, the job and the offer land in one receipt the baseline page reads. Two switches hold it, one to arm it on the buy rails and one to let it commit anything, and both are closed by default in the code. A person can run the same loop from their own wallet today, and profits from the trade, which is why it lasts: the swap loop.

The map, part two

Which chain holds what, and which wallet moves what.

ChainWhat lives there
Regen LedgerThe registry of record, the community pool, governance, the verified stewardship hour, the burn stream, anchors
BaseThe board's settlement, the REGEN and ECO pool, the running buys of ECO and NET, REGEN bridged from the ledger
OsmosisREGEN's oldest market, reached from the ledger by a plain IBC channel that cost nothing to cross in either direction when it was run on 8 September (the holdings figures of version 7 were not read again, so they are dropped)
Robinhood ChainThe board's twin, the SPCX and ETH markets, the candidate REGEN program
Any Ethereum chainThe migration package, an option the community holds
WalletHeld byMoves
The community poolThe protocol, by voteTo the payout account; to a validator floor and a Robinhood budget if voted
The payout accountNamed in the proposalTo workers, only on settled and accepted jobs, through the board
EcoWealth's operating wallet on BaseEcoWealthDevelopment funding into the REGEN and ECO pool, the class fee, the deposits, the running buys of ECO and NET
Workers' walletsThe people doing the workReceive dollars, tokens or provision
The address nobody holdsNo oneReceives the burn stream

Who uses it

No sign-up, no fee, no permission.

The infrastructure, piece by piece

Six pieces, who runs each, and what pays for it.

Emission is zero, so nothing on the ledger is paid by new coins any more. Each piece below is paid by use: today as the table says, and after the upgrade, when a fee router sends fees on issuance, transfer, retirement and trade to validators, the pool and the program in a split the community ratifies.

PieceWho runs itPaid by, todayPaid by, after the upgrade
Consensus: the eleven validators and their nodesIndependent operatorsGas fees, about six REGEN a month each on average in the thirty days to 18 November 2026 (5.9, fee line, block 29,816,650); they run at a loss for the missionThe operating floor as a bridge, then routed registry fees
Public endpoints: RPC, LCD, gRPC, the archive nodeValidator and community operatorsThe same operators; reads are freeRouted fees; verification reads stay free
Indexers and the knowledge graphRND (the indexer, KOI); EcoWealth (the commons mirror, the baseline)RND's budget; EcoWealth's ownRouted fees on the ledger side; the program's records stay free to read
Storage and anchors: metadata, IPFS, the data moduleRND and credit originatorsGas per anchor; a credit class costs 5,000 REGEN and a basket 1,000, both burnedThe same fees, routed instead of burned where the community votes it
Applications: the registry app, the marketplace, Regen Compute, ecoBridgeRND; ecoBridge.earthMarketplace fees (values to confirm with RND), subscriptions, retirement flowThe same, plus verified-stewardship-hour credits sold and retired
Interchain: IBC relayers, the Axelar corridor, the route to BaseRelayer operators, Axelar, SkipRelay fees, and a toll on every transfer of the token out of the ledger over the Axelar corridor (143.4 REGEN on the 8 September run; quote it again before any transfer); the plain IBC channels cost nothing on that runThe same; the program batches transfers so the toll is paid once per size

Who does what

Four parties, one course.

The steps

Now, and the next three months.

Done (September)

Done: both votes took effect.Supply flat since the vote closed, the new credit type in the table.
Done: the baseline page is live.The baseline, refreshed by script, with the numbers above plus jobs posted, claimed and settled per day, hours settled, credits issued, retirements, pool balance, pool depth. A line the sources cannot answer yet shows a dash and says why.
Done, inside proposal 77.What the program pays for, the rate per hour (10,000 REGEN per accepted hour), the receipt shape and the return of anything unspent are written into the proposal that passed on 14 September, rather than a separate charter thread.
Done: the first credit class, and the WORK basket.VSH01 was created on 7 September, its five thousand REGEN fee burned, and the WORK basket that turns its credits into one token each followed on 8 September. The first project opens at the place of the first accepted hours.

Next (October to December)

Done as a tranche: proposal 77.Passed on 14 September with no vote against: 100,000 REGEN from the pool balance into the payout account, EcoWealth's own, paying only on accepted hours at the stated rate, unspent returned. The standing stream was not put up, because after emission stopped the pool's inflow measures at about a hundred and thirty REGEN a year (two dated reads of the pool, given under "What still has to be built"). Nothing has been paid from the tranche; on 18 November 2026 the board reads 0 hours settled, and the first payment waits on the first accepted hours.
Issue the first credit batch from settled hours.Retire the first one. The WORK basket is ready to take it. The board can already take one as payment: a verified-stewardship-hour credit sent tradable to a worker on regen-1 settles their job, on their own signature, against a proof a human accepted.
Turn on the swap loop on Base.The hook is built and disarmed, and the page that shows a person how to run the same loop from their own wallet is written. What remains is the two switches.
Deepen the REGEN and ECO pool.The bridge is built and non-custodial: it quotes live in both directions, hands the caller one unsigned transaction they sign with their own wallet, and a relayer carries every hop after that. Moving the token itself out of the ledger goes over the Axelar corridor and costs a toll that read at about a hundred and fifty REGEN at every size tried on 5 September and 143.4 REGEN on the 8 September run, so batch and never dribble, and quote it again before any transfer; the same corridor carried axlREGEN back from Base with no toll on that run. The same ledger also reaches Osmosis over a plain IBC channel that cost nothing in either direction on that run, but Osmosis is a separate market rather than a route into this pool. The dust runs landed on 8 September, each read on the destination chain: 100 REGEN to Osmosis, 3,000 to Base as axlREGEN (2,856.6 arrived after the corridor's toll), and 1,000 back from Base with no toll. What remains is size.
Done: the validator operating floor, proposal 78.Passed on 14 September with no vote against: 396,000 REGEN, 36,000 to each of the eleven, paid when it passed, as a bridge until the upgrade routes fees. It is a one-off payment out of the pool balance rather than a stream, because emission has stopped and the pool's whole inflow now measures at about a hundred REGEN a year, which no percentage of can pay eleven validators anything.
Count retirements and anchor the records.Regen Compute and ecoBridge retirements on the page; the program's records anchored on Regen. The retirement count is on the page. The anchor leg is built: every week the proof batch rolls every tracked record into one root and writes it to Base and then to Ethereum, and the leg pins that same root on Regen's data module. It was armed on 13 September. The daily record anchor has run since October: on 18 November 2026 the steward account has sent 55 anchors to the data module, the newest at 00:25 UTC. What remains open is the weekly root: this read does not say which anchor, if any, is one.

Put to a vote in version 7, and rejected

Neither has been put up again: the newest proposal on the chain is 82, and it is not the Working Group's.

Gate to move on

Two months in a row where settled hours, credits issued and pool payments with receipts all grow, and the pool's depth does not shrink.

The steps, continued

Then the upgrade, and the Robinhood track.

Then (first half of 2027)

One chain upgrade.The new Cosmos version with the proof-of-authority module, fee routing so registry activity pays validators, the pool and the program automatically, and validator terms with an emergency plan. The two drafts are written, from the published mechanism specifications, with the zero-revenue floor and the delegator schedule written in rather than left open. They name five things that have to be decided before an upgrade can ship: which burn survives when the fee router arrives beside the burn stream already running, how a composition rule written for fifteen validators applies to eleven, what a former delegator holds afterward, whether the module's licence permits this use, and what the rollback is if the migration fails. What remains is a lead on the engineering side and the drafts going up for review.
Eight weeks on a test network, then the vote.The first routed payment into the program fund closes the step.

Later (2027 onward)

Dynamic supply and contribution rewards.On at least two quarters of real routed-fee data. Nothing modeled on projections.

The Robinhood track (candidate)

If the program is funded on that side, this is the shape it takes: REGEN trading on Robinhood Chain against ETH and SPCX, an incentive program around that liquidity, and a self-serve DCA loop for new users there, so the coin gains a market and new hands while the ledger work continues.

Name the bridge path for REGEN to Robinhood Chain and rehearse it on a test network.The chain's own portal, a third-party bridge, or the lockbox design in the migration package.
One proposal with the budget, the period, the pairs, the rate, the receipt shape and the end date.REGEN with ETH and REGEN with SPCX. Liquidity built by incentives to others, never by the house wallet.
A DCA program for new users there.The same three-job loop, self-serve, no outreach.
Before anything is issued, settle how issuing REGEN around liquidity nets to a burn on REGEN under the burn principle below."Issued for a period" means a budget from what exists unless the community votes a bounded window for a named purpose.

The migration package. Built, public, tested, deployable for under a dollar on any Ethereum chain. An option the community holds. The program does not wait for it.

What still has to be built

Ten things, in order.

Already built and running: the board, the proof rail, standing, settlement in dollars, any token or provision, the agent loops, the tool interface for agents, the proof anchors, the migration package, the proposal rail that landed the eight votes, the program tranche and the validator floor, VSH01 and the WORK basket, the bridge router across regen-1, Osmosis and Base, the REGEN and ECO pool, the running buys of ECO and NET.
The baseline page.Live. One page, refreshed by script, with every number in this document and the program lines: the baseline. Two companion pages read the same way: the turnout map and the fee line.
The credit rail.The class exists (VSH01, created 2026-09-07) and so does the WORK basket (2026-09-08); issue a batch from settled hours on the board (the board now records hours claimed and hours accepted on a job, and on 18 November 2026 it reads 0 hours settled); retire one. The issuer key and the batch metadata are the work.
The pool proposals.Passed on 2026-09-14, each with about 53.6 million yes and none against. Proposal 77 is the first tranche: 100,000 REGEN from the pool balance into the payout account, paid only against accepted hours at the stated rate, unspent returned. Proposal 78 is the validator operating floor: an equal share to the eleven for six months, since emission is zero and the pool's inflow is fees alone. The floor paid 36,000 REGEN to each of the eleven when it passed; the tranche has paid nothing, because no hours have been accepted under it (read 18 November 2026). The standing stream was not submitted: the pool grew by about 19 REGEN in the 51 days between 27 September (3,672,755.92 REGEN, block 29,019,226) and 18 November (3,672,774.88 REGEN, block 29,816,486), which is about a hundred and thirty REGEN a year, so a share of it is a gesture, and the balance is what pays.
The swap loop's three jobs.Built, and switched off by default. Two automatic buys, the daily NET buy and the ECO dime rail (stopped), can call a hook that offers a tenth of that buy, in REGEN, to one open job, posts one more job through the proven posting rail, and writes a receipt the baseline page reads. It is disarmed in the code, and the page anyone can run the same loop from is written. What remains is the two switches, and the fraction is a stated dial that only a person moves.
The Regen anchor leg turned on.Built, and armed on 2026-09-13. The weekly proof batch's root, the one that already covers every tracked record and lands on Base and Ethereum, pinned on Regen's data module by the same recipe the work anchors use. Drafted, decoded back and accepted by the chain in check mode. The daily record anchor has run since October, and on 18 November 2026 the steward account has sent 55 anchors, the newest at 00:25 UTC. What remains open is the weekly root: this read does not say which anchor, if any, is one.
The validator floor proposal.Passed and paid on 2026-09-14: 396,000 REGEN, 36,000 to each of the eleven. Equal share to the bonded set, capped by a stated share of the pool balance, over a stated bridge period, with the recipients read live from the chain. Drafted, decoded back and accepted by the chain in check mode. Both shapes are written, one message per validator and one message into an account that divides afterwards, and the proposal itself carries the recommendation and the case against it. Nothing on this chain expires on an event, so the floor is bounded by a fixed amount, a stated period, and the fact that nothing renews it without another vote.
The Robinhood pieces.The bridge path, the REGEN token there, the two pairs, the incentive program, the new-user loop.
The chain upgrade.RND engineering, with the Working Group's fee-routing and validator-terms drafts. Both drafts are written. The fee-routing one carries the fee schedule, the split, the invariants and a floor for what happens when fee revenue stops; the validator-terms one carries the set, the pay, the performance measure, the lifecycle, an emergency plan and a dated schedule for the people who bonded stake to a validator. Every number in them is either cited to the published specification it came from or read live from the chain, and the parts that are the Working Group's own reading are separated out and labelled. What remains is a lead on the engineering side, the drafts going up for review, and five decisions the drafts name but do not make.
The protocol's next workers.Built. Two health-care work types now sit inside the Standard, because they are properties of the place rather than of a person: a walked-route hazard audit of a ward's own corridors, handrails, floor transitions and night lighting, held to the accessible-design numbers, and a care kitchen proven able to run the diets already ordered, held to the food code's holding temperatures, the dysphagia framework's own texture tests and the nine major allergens. Each carries a full method, because neither is a clinical measurement and neither reads anything off a person's body. And a robot's hours now have a proof method: the run log read against an independent operator record, bound to the place, with idle and fault and teleoperated time subtracted, then claimed and accepted through the same two fields a person's hours already use, with a human who is not the robot's operator writing the accepted figure. Nothing has been posted to the board.
The digital stewardship authority.Built, put to a vote as proposal 81 and rejected on turnout on 2026-10-02 (read 18 November 2026); it has not been put up again. Digital work for the chain, protocol and tooling, on-chain operations, registry tooling, validator and endpoint stewardship, paid by the hour: the worker signs the authority's offer before starting, publishes the evidence, anchors its hash on the ledger, and a governance proposal names the hours and carries one pool spend for hours times the rate. AI and compute are recorded as inputs and never multiply hours. A dry rehearsal of the whole path on a real posted digital job simulated cleanly against the chain. Nothing is paid under it, because the vote did not pass.

What we measure, and what could stop it

Seven measures, six risks.

On the baseline page, each read at one block height: hours settled; credits issued and retired, the verified stewardship hour first; payments from the pool, each with its receipt; pool balance and the pair's depth on Base; retirements per day; validators and how much of their cost the floor covers; fees routed, after the upgrade.

What could stop it, and what we do about each.

Money

Development funding, and the community's money.

Any REGEN that funds the build and the running of the Regen side of the program is development funding. It is not a retirement, and it buys no credit. It is used at the steward's discretion, and the plan for it is stated upfront and receipted on the baseline page:

UseAmountWhy
Deepen the REGEN and ECO pool on BaseThe bulkGrows the ECO token and the pair, the program's trading venue
The first verified-stewardship-hour credit class5,000 REGEN, spent and burned on 2026-09-07The first use of the new credit type
Governance deposits for the next votes2,000 REGEN eachRefunded when a vote passes, recycled
The Robinhood program, if fundedUnder its own proposalThe liquidity budget on the SPCX and ETH pairs

No staking. No burning by the steward. Every movement receipted.

Community funds

The pool is the community's. The rules that let it pay honestly:

The first tranche under those rules is proposal 77. It passed on 14 September, and none of it has left the payout account under the program's receipt shape (the payout account's chain history, scanned in full on 18 November 2026, 05:47 UTC): the tranche ledger carries the proposal's status, the pool balance, the stated rate per accepted hour, every payment with its packet, place, hours and transaction, and what is left.

The steward reversed one earlier position to write this: vote 68 was closed because it spent the pool on a burn. Spending the pool on verified regeneration is the opposite of a burn.

Taking care of the pieces

The validators, the coin, the burn principle.

The innovation underneath

The work protocol in the age of AI, solar, data centers and robots.

The mechanics are live, and they are what lets regeneration fight for its place.

Each settled hour becomes a credit, a receipt, a trade, a higher standing, and the reason for the next payment. That is value at the nth degree.

Everything planned after these votes

To provision ecological wealth as regeneratively as possible.

Whatever the coin does, the ecology gets healthier. We use these chains and this technology to coordinate energy, humans, robots and agents toward it. The whole plan, grouped:

The Standard

Ten conditions a place is held to; standing that rises only from settled work and lapses; re-measured on a cadence; enforced in the build.

The board and the places

Tens of thousands of method-backed definitions mapped to standards; the data-center, solar and water programs; country waves; every job names the trade it ladders into.

Work for work

Provision as settlement; earned credit that closes by being provisioned; any group's own token as terms.

Money as a program

Programmable finance for humans where gas is cents: standing buys, swaps, pools, transfers, every move receipted. The swap loop is its first public shape.

Credentials and titles

A worker credential split honestly into verified, self-declared and paid; a titles register; a public directory.

Health as a research vehicle

The health protocol inside the board, screen and refer, never diagnose; a library across humans, animals, insects, plants and fungi; medicine intake and development priced as verified hours.

Proof that stays free

Every finding of value anchored before it leaves; verification never paywalled.

Regen

The first batch and the WORK token in use, digital hours paid by vote, upgrades done in public, the chain upgrade, the Robinhood track, the migration option.

Agents everywhere

One published door with its own tool list, a zero-compute client, and a paste block that turns a person's own AI into their companion here.

Energy and robots

Builds tiled with the regeneration they owe; robot hours verified like human hours.

None of this depends on what the coin does. Whatever it does, each settled hour leaves a receipt on one public book, and the receipt is the thing that counts.

What we ask of RND, and how to check

Four answers, and every number checkable.

  1. Name who leads the chain upgrade on RND's side, and announce the next one in public ahead of its height.
  2. Share Regen Compute retirements per day, for the baseline page.
  3. Retire the first verified-stewardship-hour credits when they are issued.
  4. Confirm the marketplace fee values and where they go.

Version 7 also asked for votes on proposals 80 and 81. Both closed on 1 and 2 October, so that ask is closed.

Any live regen-1 endpoint answers these, for example https://regen-api.polkachu.com, which is the one the figures of version 8 were read from on 18 November 2026. Add the header x-cosmos-block-height: 29816486 to a chain read and it answers at the height the figures name. Emission and supply: /cosmos/mint/v1beta1/params, /cosmos/bank/v1beta1/supply/by_denom?denom=uregen. Validators: /cosmos/staking/v1beta1/validators. The pool: /cosmos/protocolpool/v1/community_pool. Registry: /regen/ecocredit/v1/credit-types, /classes, /projects, /batches. The votes that made this state: /cosmos/gov/v1/proposals/74 and /75, then /77 and /78; closed rejected: /80 and /81; not ours, rejected: /82. The tally of any of them: the same path with /tally. The voting bar: /cosmos/gov/v1/params/tallying and /cosmos/staking/v1beta1/pool. Credits under the verified stewardship hour class: /regen/ecocredit/v1/projects-by-class/VSH01 and /batches-by-class/VSH01. The board: vealth.net/labor/stats, /labor/settled, /labor/posted-definition-ids. The migration package: a fresh clone of github.com/Eco-Wealth/regen-arbitrum-migration re-derives its numbers.

Sources this continues: the Economic Reboot Roadmap v0.1 (Regen forum thread 567), the mechanism specifications in regen-network/agentic-tokenomics, the Proof of Authority RFC, the Working Group record, Regen Compute, and EcoWealth's dated receipts. Corrections and challenges are welcome on the Regen forum or at vealth.net/regen/forum. Regen Network and REGEN are the marks of their owners. This page is offered openly for review and is not a solicitation.