Vealth · Regen Network · The course · The baseline · The revenue line

What Regen Ledger earns today, read from every transaction.

76.99 REGEN
every fee the whole ledger collected in the last 30 days
across 10,149 transactions
1,018 times
the proposed operating floor, over what a validator actually earns in fees
5.89 REGEN a month measured per validator, against the 6,000 REGEN the validator-floor draft proposes; that floor is a governance figure, not a measured cost

regen-1 height 29,816,650 · block time 2026-11-18T06:19:32.636078281Z · built 2026-11-18T06:21:16.427Z · every parameter read pinned to that height · rebuild: npx tsx scripts/regen/regen-ledger-revenue.ts

Since proposal #74 took effect at height 28,650,945, no new REGEN is minted, so transaction fees are what the chain itself pays the validator set, plus the community tax on those fees, which was the pool's only measured inflow in the 90-day window (no direct deposit into the pool appeared in it). Two sources of income this page does not see and does not add: the marketplace fee, whose parameters the public LCD will not serve, and Regen Compute's subscription revenue, which is off-chain and Regen Network Development's to state. Rebuild the page and the numbers change; nothing here is edited by hand.

WindowTransactionsFees paidPer month at this rate
trailing 30 days10,14976.99 REGEN78.12 REGEN
trailing 90 days33,503228.45 REGEN77.26 REGEN
since #74 took effect23,689185.79 REGEN75.08 REGEN

Twelve more months at the trailing-30-day rate would be 937.38 REGEN for the whole chain.

The units of use

What one act on the ledger cost, by message type, trailing 90 days.

The three most used messages: execute under an authorization (14,764, median fee 0.005 REGEN); retire credits (9,126, median fee 0.005 REGEN); anchor a record (8,580, median fee 0.015 REGEN). By fee rather than by count, six types carry 85.47% of everything the ledger collected in the window.

What it doesTransactions carrying itMedian fee paidShare of all fees
execute under an authorization14,7350.005 REGEN33.52%
retire credits9,1260.005 REGEN19.97%
anchor a record2040.015 REGEN16.13%
withdraw staking rewards1,1620.0037 REGEN8.28%
send REGEN or another coin2,8570.0026 REGEN4.05%
edit a validator52 REGEN3.51%
everything else, 29 more message types6,1390.0006 to 2 REGEN14.53%

The table is in REGEN: the largest median in it is 2 REGEN, and the median transaction across the whole window paid 0.005 REGEN. The gas prices and all 35 message types are at the foot of the page.

Where the fees go

83.00% to the validator set, 17.00% to the pool, and the pool burns 15.00% of its inflow.

63.9 REGEN
to the validator set, trailing 30 days
gross, before each validator's commission; split by bonded stake
13.09 REGEN
to the community pool, trailing 30 days
the 17.00% community tax; 1.96 REGEN of it is burned by the #66 fund, 11.13 REGEN stays
64.84 REGEN
the set's gross fee income per month
5.89 REGEN each if split equally among 11
0 REGEN
REGEN minted per year
zero since #74; fees are the whole income
ValidatorShare of bonded stakeMonthly fee incomeCommission
ecoBridge.earth20.96%13.59 REGEN6.00%
Regenerator12.83%8.32 REGEN5.00%
polkachu.com11.25%7.29 REGEN5.00%
Earthist9.58%6.21 REGEN9.00%
Vitwit (Previously Witval)9.10%5.9 REGEN5.00%
KalpaTech8.93%5.79 REGEN10.00%
0base.vc8.34%5.4 REGEN10.00%
Chainflow7.47%4.84 REGEN8.00%
ECO Stake 🌱 | REStake.app6.54%4.24 REGEN5.00%
Alex (Bambarello) Validator3.14%2.04 REGEN10.00%
Start-Staking.cc1.86%1.2 REGEN5.00%

The floor beside the revenue

The operating floor proposed in the validator-floor draft is 1,018 times the measured fee income per validator.

5.89 REGEN
measured fee income per validator per month
the 30-day run rate, split equally among 11
6,000 REGEN
the stated floor per validator per month
unit 6's governance figure, not a measured cost
0.10%
of the floor covered by fee income
the proposed floor is 1,018 times the revenue
396,000 REGEN
the six-month floor for 11 validators
against 389.01 REGEN the set would earn in fees over the same six months at this rate

The zero-revenue trigger, answered. The upgrade draft sets the trigger (total fee revenue under a governance-set floor for four consecutive 28-day epochs) and no draft has yet set that floor's value, so whether the trigger is met is not a question this page can answer. What it can measure: the validator set's share of fees was between 50.6 and 71.8 REGEN per 28-day epoch in all 3 whole epochs that fit in the trailing 90 days. So any trigger floor set above about 71.8 REGEN an epoch would already have tripped in every measured epoch, and a fourth consecutive epoch at this rate is the run rate, not a scenario. For scale only: the operating floor proposed in this course's validator-floor draft, restated per epoch for 11 validators, would be 60,714.58 REGEN; it is a proposed operating figure, not the trigger's floor. The epoch-by-epoch table those figures come from is at the foot of the page.

The protocol's own fees

The class fee and the basket fee are burned; the marketplace fee is not readable here.

5,000 REGEN
to create a credit class
burned by the module on success; none of it reaches a validator or the pool
1,000 REGEN
to create a basket
burned the same way
6,000 REGEN
protocol fees burned in the trailing 90 days
2 class or basket creations
not readable
marketplace fee
unreadable on the public LCD: HTTP 501 Not Implemented

Where the class fee goes, with the source. https://github.com/regen-network/regen-ledger/blob/v7.2.0/x/ecocredit/base/keeper/msg_create_class.go#L155-L160 (chargeCreditClassFee: SendCoinsFromAccountToModule at line 155, BurnCoins at line 160). The basket fee follows the same two lines in https://github.com/regen-network/regen-ledger/blob/v7.2.0/x/ecocredit/basket/keeper/msg_create.go#L71-L76 (SendCoinsFromAccountToModule to the basket submodule at line 71, BurnCoins at line 76). So a class costs 5,000 REGEN and that REGEN leaves the supply; it is not income to anyone. The marketplace module's fee parameters answer Not Implemented on the public LCD, so no marketplace fee value is asserted on this page. Denoms a sell order may be priced in: USDC.axl, USDC.grv, regen, usdc.

Check it yourself

A second node was asked the same question.

Every transaction count on this page was asked of a second independent node as well: trailing 30 days, both nodes count the same transactions; trailing 90 days, both nodes count the same transactions; since #74 took effect, both nodes count the same transactions. The JSON copy at /regen-network/regen-revenue.json carries every figure, every window edge and every message type; the drawer below carries the calls, the full tables and the method behind each one.

Check any of this yourself

The windows, with their heights and block times

WindowHeightsBlock timesTransactionsFees paidPer month at this rate
trailing 30 days29,352,092 to 29,816,6502026-10-19 to 2026-11-18 (30 days)10,14976.99 REGEN78.12 REGEN
trailing 90 days28,424,383 to 29,816,6502026-08-20 to 2026-11-18 (90 days)33,503228.45 REGEN77.26 REGEN
since #74 took effect28,650,945 to 29,816,6502026-09-03 to 2026-11-18 (75.32 days)23,689185.79 REGEN75.08 REGEN

How the fee is read. Every transaction carries its fee in auth_info.fee.amount; that is what is summed, per denom, for every transaction whose height falls inside the window. A failed transaction still paid, because the fee is taken before the messages run, so failed transactions are counted too (75 of 33,503 in the 90-day window). A node can also hand back a transaction whose body it cannot decode; that transaction is counted with no fee, and the count is stated here and in the JSON for every window so an undercount cannot hide: the 90-day window holds none. A month here is 365.25 divided by 12 days.

Fee denoms seen in the 90-day window

DenomBase units paid, 90 daysNote
uregen228,453,985REGEN's base unit, one millionth of a REGEN

Every message type in the window

What it doesMessage typeMessagesTransactionsFee attributedMedian fee per transactionMedian gas price (uregen per gas)
execute under an authorization/cosmos.authz.v1beta1.MsgExec14,76414,735 (4 failed)76.59 REGEN0.005 REGEN0.0618
retire credits/regen.ecocredit.v1.MsgRetire9,1269,12645.63 REGEN0.005 REGEN0.0658
anchor a record/regen.data.v2.MsgAnchor8,580204 (1 failed)36.84 REGEN0.015 REGEN0.075
send REGEN or another coin/cosmos.bank.v1beta1.MsgSend2,8642,857 (24 failed)9.25 REGEN0.0026 REGEN0.025
buy credits from a sell order/regen.ecocredit.marketplace.v1.MsgBuyDirect2,4052,4057.03 REGEN0.003 REGEN0.025
withdraw staking rewards/cosmos.distribution.v1beta1.MsgWithdrawDelegatorReward1,8561,162 (2 failed)18.92 REGEN0.0037 REGEN0.025
IBC client update/ibc.core.client.v1.MsgUpdateClient1,3991,3994.25 REGEN0.0008 REGEN0.001
vote (gov v1beta1)/cosmos.gov.v1beta1.MsgVote4474430.72 REGEN0.0017 REGEN0.025
delegate/cosmos.staking.v1beta1.MsgDelegate366338 (1 failed)1.71 REGEN0.0055 REGEN0.025
IBC transfer out/ibc.applications.transfer.v1.MsgTransfer303303 (16 failed)1.44 REGEN0.0035 REGEN0.025
IBC acknowledgement/ibc.core.channel.v1.MsgAcknowledgement2852710.08 REGEN0.0006 REGEN0.001
IBC packet received/ibc.core.channel.v1.MsgRecvPacket2672670.11 REGEN0.0007 REGEN0.001
undelegate/cosmos.staking.v1beta1.MsgUndelegate213212 (5 failed)1.23 REGEN0.0061 REGEN0.025
send credits/regen.ecocredit.v1.MsgSend1641640.33 REGEN0.0038 REGEN0.025
redelegate/cosmos.staking.v1beta1.MsgBeginRedelegate163163 (11 failed)1.13 REGEN0.0072 REGEN0.025
execute a contract/cosmwasm.wasm.v1.MsgExecuteContract4440 (1 failed)0.97 REGEN0.0111 REGEN0.025
vote/cosmos.gov.v1.MsgVote35354.17 REGEN0.0075 REGEN0.025
set a withdraw address/cosmos.distribution.v1beta1.MsgSetWithdrawAddress2360.05 REGEN0.0215 REGEN0.025
cancel an unbonding/cosmos.staking.v1beta1.MsgCancelUnbondingDelegation2121 (9 failed)0.09 REGEN0.0046 REGEN0.025
post a sell order/regen.ecocredit.marketplace.v1.MsgSell18180.09 REGEN0.005 REGEN0.025
grant an authorization/cosmos.authz.v1beta1.MsgGrant11110.03 REGEN0.0026 REGEN0.025
submit a proposal/cosmos.gov.v1.MsgSubmitProposal990.26 REGEN0.0207 REGEN0.03
withdraw validator commission/cosmos.distribution.v1beta1.MsgWithdrawValidatorCommission88 (1 failed)3.16 REGEN0.1 REGEN0.0333
update project admin/regen.ecocredit.v1.MsgUpdateProjectAdmin660.27 REGEN0.0021 REGEN0.025
edit a validator/cosmos.staking.v1beta1.MsgEditValidator55 (1 failed)8.03 REGEN2 REGEN10
revoke an authorization/cosmos.authz.v1beta1.MsgRevoke330.01 REGEN0.0022 REGEN0.025
issue a batch/regen.ecocredit.v1.MsgCreateBatch336 REGEN2 REGEN10
update project metadata/regen.ecocredit.v1.MsgUpdateProjectMetadata330 REGEN0.0021 REGEN0.025
IBC timeout/ibc.core.channel.v1.MsgTimeout220 REGEN0.0006 REGEN0.001
cancel a sell order/regen.ecocredit.marketplace.v1.MsgCancelSellOrder220.01 REGEN0.005 REGEN0.025
MsgBurnRegen (ecocredit)/regen.ecocredit.v1.MsgBurnRegen220 REGEN0.0021 REGEN0.025
create a project/regen.ecocredit.v1.MsgCreateProject220.02 REGEN0.0112 REGEN0.0625
MsgSubmitProposal (group)/cosmos.group.v1.MsgSubmitProposal110.02 REGEN0.015 REGEN0.05
create a basket/regen.ecocredit.basket.v1.MsgCreate110.01 REGEN0.009 REGEN0.03
create a credit class/regen.ecocredit.v1.MsgCreateClass110.01 REGEN0.0075 REGEN0.03

How a fee is attributed to a message. A transaction pays one fee for every message it carries. Here that fee is divided equally across the transaction's messages and each message's share is added to its type, so the attributed column sums to the window's total, and the share-of-fees column on the page above is that attributed figure over the window's total. A transaction carrying two types is counted once under each of them, so the transaction column does not sum to the window's total; the fee columns do. The median fee per transaction is the whole fee of the transactions carrying that type, which is what a person or an agent actually paid to get that act onto the ledger. The gas price is the fee over the gas the transaction asked for, in uregen per unit of gas; across all 33,503 transactions the median was 0.0618 uregen per unit of gas. The node's own minimum gas price is not served by the public LCD, so the observed price is the only one stated.

The validator set, in full

ValidatorShare of bonded stakeMonthly gross fee incomeCommission rateOf which commission to the operator
ecoBridge.earth20.96%13.59 REGEN6.00%0.82 REGEN
Regenerator12.83%8.32 REGEN5.00%0.42 REGEN
polkachu.com11.25%7.29 REGEN5.00%0.36 REGEN
Earthist9.58%6.21 REGEN9.00%0.56 REGEN
Vitwit (Previously Witval)9.10%5.9 REGEN5.00%0.3 REGEN
KalpaTech8.93%5.79 REGEN10.00%0.58 REGEN
0base.vc8.34%5.4 REGEN10.00%0.54 REGEN
Chainflow7.47%4.84 REGEN8.00%0.39 REGEN
ECO Stake 🌱 | REStake.app6.54%4.24 REGEN5.00%0.21 REGEN
Alex (Bambarello) Validator3.14%2.04 REGEN10.00%0.2 REGEN
Start-Staking.cc1.86%1.2 REGEN5.00%0.06 REGEN

How the split is read. The community tax is /cosmos/distribution/v1beta1/params at this height: 17.00%. Fees times the tax is what reaches x/protocolpool; fees times one minus the tax is the validator set's gross, distributed by bonded stake, of which each operator keeps its commission and the rest goes to its delegators. The continuous fund created by #66 takes 15.00% of the pool's inflow and sends it to a keyless address, which is the burn. Monthly figures are the trailing-30-day run rate.

The 28-day epochs behind the trigger answer

EpochDatesTransactionsFees paidThe validator set's share
the latest 28 days2026-10-21 to 2026-11-189,52861.04 REGEN50.66 REGEN
2 epochs back2026-09-23 to 2026-10-218,19586.5 REGEN71.8 REGEN
3 epochs back2026-08-26 to 2026-09-2310,74160.97 REGEN50.6 REGEN

Two nodes, counted against each other

WindowTransactions, this build's nodeTransactions, second nodeResult
30d10,14910,149both nodes count the same transactions
90d33,50333,503both nodes count the same transactions
since_7423,68923,689both nodes count the same transactions

The second node. https://regen-api.polkachu.com, whose block store starts at height 28,424,383. Its first page of the since-#74 window (100 transactions) carries the same transaction hashes and the same fee sum as this build's.

Reconciled with the validator floor's own measurement. The floor draft measured 0.3605 REGEN reaching the pool between heights 28,650,946 and 28,669,862 by reading the pool's balance at both heights. This build sums the fees paid in those blocks: 2.12 REGEN, times the community tax is 0.3604 REGEN, a gap of 0.0001 REGEN. The floor module measured the pool's balance change (plus what the #66 fund pushed out) between two heights. Fees paid in block b reach the pool at the start of block b+1, so the fees that fall inside a balance delta from height A to height B are those of blocks A to B-1; that is the window summed here, times the community tax. Run live at this build: the floor module read 0.4248 REGEN over blocks 29,796,650 to 29,816,650 (about 119 REGEN a year, burn share observed 14.95%); the fee sum times the tax over the same blocks is 0.4265 REGEN, a gap of 0.0017 REGEN.

Every number, the call that returns it

Add the header x-cosmos-block-height: 29816650 to any parameter call below and it answers at this page's height. The transaction calls are addressed by height range and need no header.

NumberCall
transactions in a height range (paged, 100 per page)https://regen-api.polkachu.com/cosmos/tx/v1beta1/txs?query=tx.height>=29352092 AND tx.height<=29816650&limit=100&page=1&order_by=ORDER_BY_ASC
a block's time (the window edges)https://regen-api.polkachu.com/cosmos/base/tendermint/v1beta1/blocks/29352092
community taxhttps://regen-api.polkachu.com/cosmos/distribution/v1beta1/params
emission (params)https://regen-api.polkachu.com/cosmos/mint/v1beta1/params
emission (annual provisions)https://regen-api.polkachu.com/cosmos/mint/v1beta1/annual_provisions
supplyhttps://regen-api.polkachu.com/cosmos/bank/v1beta1/supply/by_denom?denom=uregen
community poolhttps://regen-api.polkachu.com/cosmos/protocolpool/v1/community_pool
continuous funds (the #66 burn fund)https://regen-api.polkachu.com/cosmos/protocolpool/v1/continuous_funds
bonded validators and their stakehttps://regen-api.polkachu.com/cosmos/staking/v1beta1/validators?status=BOND_STATUS_BONDED
class feehttps://regen-api.polkachu.com/regen/ecocredit/v1/class-fee
ecocredit params (basket fee, allowed denoms)https://regen-api.polkachu.com/regen/ecocredit/v1/params
marketplace params (not served)https://regen-api.polkachu.com/regen/ecocredit/marketplace/v1/params
second node, same transaction queryhttps://regen-api.polkachu.com/cosmos/tx/v1beta1/txs?query=tx.height>=28650945 AND tx.height<=29816650&limit=1&page=1

Companion pages: the baseline (emission, supply, the registry, the votes), the course, the commons. Regen Network and REGEN are the marks of their owners. This page is offered openly for review and is not a solicitation.