Vealth · Regen Network · The course · The tranche ledger
Every REGEN out of the tranche, and the accepted hour it paid for.
regen-1 height 29,019,226 · block time 2026-09-27T19:20:14.689831468Z · built 2026-09-27T19:20:25.086Z · every ledger read pinned to that height · rebuild: npx tsx scripts/regen/build-regen-tranche.ts
Proposal #77 moves 100,000 REGEN out of the community pool balance into a payout account, and binds every REGEN that leaves it to an hour a human accepted on a public board. This page is the record it promised. Nothing here is typed by hand.
The vote
It passed.
The first program tranche: 100,000 REGEN from the community pool, paid out only against accepted stewardship hours
Status
- On chain
- passed
- Voting closes
- 2026-09-14T23:24:51.692077013Z
- Return window
- 365 days
Tally, in REGEN
- Yes
- 53,644,270
- No
- 0
- Abstain
- 0
- No with veto
- 0
Execution and balance are two different checks. On this Cosmos SDK version, x/gov writes PROPOSAL_STATUS_PASSED only after every proposal message executes successfully; this page also verifies that #77 contains exactly the authorized protocolpool spend. The payout account balance answers a different question: whether the account can cover the unpaid program remainder now.
The payments
No payment has been made.
The deadline is 2027-09-14T23:24:51.692Z. executed 2026-09-14T23:24:51.692Z; whatever is unspent returns to the community pool by 2027-09-14T23:24:51.692Z
| Packet | Place | Hours claimed | Hours accepted | Paid | Settlement | Proof hash | Regen transaction |
|---|---|---|---|---|---|---|---|
| — | — | — | — | — | — | — | — |
Hours claimed and hours accepted are different numbers on purpose. The first is what the worker wrote on the proof. The second is what the accepting human stood behind, and it is the only one that ever multiplies the rate. When they are the same it is because the reviewer did not adjust the claim, not because the board treats them as one field.
Why the table is dashes today. The board has settled no packet that states accepted hours, so there is nothing this tranche can pay for yet. A dash here is a source that does not exist, never a zero dressed up as progress.
What binds a payment
The rules the payer refuses on, by name.
| Refusal | What it means |
|---|---|
| not_vsh_eligible | The packet does not carry the eligibility flag, so this tranche does not pay for it. |
| hours_not_accepted | No accepted hours on the record. The worker's own claim is never the pay figure. |
| hours_claimed_missing | The worker did not declare a positive hour count, so the receipt cannot carry both claimed and accepted hours. |
| accepted_hours_exceed_claim | The accepter attempted to authorize more hours than the worker declared. |
| program_funding_terms_not_bound | The worker's signed claim, accepted evidence, and current packet do not all bind the same #77 terms hash. |
| evidence_commitment_missing | The accepted work has no canonical evidence commitment. |
| regen_x_data_anchor_missing | The exact accepted evidence commitment is not proven anchored on Regen x/data. |
| vsh_method_unproven | The accepted work does not prove the registered VSH01 physical-proof method required by this first loop. |
| physical_evidence_unresolved | A human accepted the physical proof, but one or more declared photo hashes do not resolve to photo content the board actually holds and hashed itself. A bare hash is not payable evidence. |
| no_human_accepter | Nobody accepted, or a machine did. The proposal pays only against hours a human accepted. |
| accepter_is_the_worker | The worker accepted their own hours. |
| self_payment | The payment would land back in the payout account. The tranche is custody, not income. |
| worker_regen_address_unknown | No Regen account is known for this worker, and one is never guessed. |
| amount_does_not_match_rate | The amount is not the accepted hours times proposal #77's fixed 10,000 REGEN/hour rate, in whole uregen. |
| governance_rate_mismatch | A caller tried to assert a rate other than proposal #77's fixed governance rate. USD, spot-price, env and CLI values cannot rewrite it. |
| over_tranche_cap | The payment would push the running total past the tranche. |
| proposal_not_passed | x/gov has not recorded successful proposal execution. |
| proposal_execution_unproven | The proposal status/message shape does not prove the exact authorized #77 community-pool spend. |
| sanctioned_recipient | The worker's EVM identity matches the committed OFAC SDN digital-currency address cache. |
| sanctions_screen_unavailable / stale | The #77 rail fails closed until the local sanctions cache is usable and fresh. |
| tranche_balance_not_arrived | Execution is proven separately, but the payout account cannot currently cover the unpaid ledger remainder plus gas. |
| missing_tx_hash | A ledger row with no transaction hash is not a payment, and is not counted. |
Nobody types a Regen address here. A Cosmos account cannot be derived from a Base address: the Base address is a hash of the public key, and a hash does not run backwards. The worker's Regen account comes only from a signature they made, by recovering the key out of it. A worker who has signed nothing this rail can verify is refused, and the refusal says so.
Check it yourself
Every number, the call that returns it.
The JSON copy at /regen-tranche.json carries the same values, read at the same block height as the stamp at the top of this page.
Check any of this yourself
Add the header x-cosmos-block-height: 29019226 to any ledger call below and it answers at this page's height.
| Number | Call |
|---|---|
| the proposal, its status and tally | https://regen-api.polkachu.com/cosmos/gov/v1/proposals/77 |
| the community pool balance | https://regen-api.polkachu.com/cosmos/protocolpool/v1/community_pool |
| the payout account balance | https://regen-api.polkachu.com/cosmos/bank/v1beta1/balances/regen1jfheyvsah5wqfyawmedme43te056z8gzdnpf3j |
| the board's proof decisions and approved-unpaid work | https://vealth.net/labor/acceptance-log |
| who accepted each proof, and on which road | https://vealth.net/labor/acceptance-log |
What this page will not claim
- Only hours a human ACCEPTED are ever paid. The worker's own claim is carried on the receipt and never multiplies the rate.
- Duration here is worker-declared duration accepted by a human. Photo/GPS evidence is not represented as instrument-measured elapsed time.
- The first proposal-77 loop is outside-worker work: the packet creator, worker, and human accepter remain distinct consequence-bearing identities.
- Proposal 77 authorizes a fixed 10,000 REGEN per accepted hour and says changing that rule requires later governance.
- Dollar-denominated labor-unit and REGEN spot calculations may be published as economic analysis, but they do not change the amount this tranche is authorized to pay.
- Every worker-facing funding term must state the actual settlement asset and authorized rule before claim; an authored dollar estimate is separate price provenance.
- On Cosmos SDK v0.53, x/gov records PROPOSAL_STATUS_PASSED only after every proposal message executes successfully in one cached state transition. This page additionally requires proposal 77's sole decoded message to be the exact 100,000 REGEN protocolpool spend to the payout account.
- The payout account balance is a current solvency reading only. It is never used as evidence that governance executed the spend.
- A payment with no public receipt does not exist and is not counted here. A ledger row with no transaction hash is refused by the reader and listed as refused.
- The tranche is custody, not income. It buys nothing, pre-pays nobody, and is not a grant.
- Work completion, payment, and credit issuance do not by themselves prove ecological outcome.
Companion pages: the baseline (every number in the course at one block height), the turnout map, the revenue line, the course. Regen Network and REGEN are the marks of their owners. This page is offered openly for review and is not a solicitation.