regen-1generated 2026-09-13 09:17 UTCpublic chain data

regen compute / burn tracker

A burn means REGEN bought on the open market and destroyed forever, so every number below is a small, honest heartbeat of real usage anyone can verify.

Regen Compute burns 5% of net subscriber revenue from its AI-footprint subscription product: swap to REGEN on Osmosis, a real purchase on the open market before anything is destroyed, bridge to Regen Ledger, call MsgBurnRegen, a real supply burn, not a send to a dead address. This page reads every one of those transactions straight off regen-1, network-wide, no sender filter assumed.

19,414.91REGEN burned, lifetime
slowingcadence
$24.31value at the 2026-09-13 price
$38.17spent, at each burn's own price
5burns executed

Do something with this

  1. See the latest burn

    The most recent MsgBurnRegen, straight off regen-1.

    Open tx →
  2. Check the price

    Price, 24h volume and where it trades, as of that page's own build stamp.

    Open volume tracker →
  3. See proposal 78, open now

    The validator operating floor: 396,000 REGEN from the community pool, an equal share to the 11 bonded validators, 6 months. Closes 2026-09-14.

    Needs staked REGENEcoWealth's own
    Read the proposal →

What we found

Queried message.action='/regen.ecocredit.v1.MsgBurnRegen' on two independently operated Regen Network LCD nodes, network-wide (no sender filter). Every result comes from exactly one address: regen13hdw80n5c9yueg4mgvap82v2dcsl8dq50j00dh, Regen Compute's own burn wallet, named in its ACCOUNTING-SPEC.md.

Cross-check: primary (https://lcd-regen.keplr.app) reports 5 burns; secondary (https://rest-regen.ecostake.com) reports 5. MATCH. Both nodes' own retention floors (primary 4,134,001, secondary 25,498,036) were independently verified to sit below the earliest burn found, so this is not a pruned-node undercount.
dateREGEN burnedreason (on-chain)tx
2026-09-01 4,931.27 Buy-back-and-burn : Regen Compute ($6.09 allocation, 4931.269889 REGEN at $0.001242) 5FD5EE9CC3…
2026-06-18 3,932 Buy-back-and-burn : Regen Compute ($5.03 allocation, 3931.996016 REGEN at $0.001283) 23A0AC9A2A…
2026-04-22 2,919.43 Buy-back-and-burn : Regen Compute ($6.90 allocation, 2919.433151 REGEN at $0.002392) D29C8FC80F…
2026-03-25 7,250.39 Buy-back-and-burn : Regenerative Compute ($19.15 allocation, 7250.386765 REGEN at $0.002580) B3F8FE54BB…
2026-03-25 381.82 Buy-back-and-burn : Regenerative Compute ($1.00 allocation, 381.822147 REGEN at $0.002579) E01E3992CA…

Trend: slowing (each gap has been longer than the last)

Gaps between successive burns, oldest pair first: 0h → 28d → 57d → 74d. It has been 12 days since the last burn (2026-09-01).

The accounting spec in Regen Compute's own repo does not state a fixed execution schedule (a "scheduled retirement processor" and "auto-burn trigger" are referenced but not detailed). That is consistent with what the on-chain cadence itself shows: real, but not running on a tight clock.

Reconciling against the DAO's own figure

$REGEN Tokenomics DAO weekly meetup notes (regentokenomics.org / MaxSemenchuk/regen-tokenomics-site) states: "$11-17 in total burns so far."

Mark-to-market (19,415 REGEN × today's price $0.00125219) = $24.31, outside the claimed range.
Cost-basis (sum of each burn's own stated allocation at execution time) = $38.17, outside the claimed range.
Neither mark-to-market ($24.31) nor cost-basis ($38.17) falls inside the claimed $11-17 range — worth investigating rather than trusting either figure blind.

Verify it yourself

Nothing on this page is asserted on our own authority. Every number is re-derivable from these two public LCD calls.

curl "https://lcd-regen.keplr.app/cosmos/tx/v1beta1/txs?query=message.action='/regen.ecocredit.v1.MsgBurnRegen'&order_by=ORDER_BY_ASC&pagination.limit=200"
curl "https://api.coingecko.com/api/v3/simple/price?ids=regen&vs_currencies=usd"
Provisioned by EcoWealth · Digital Provisioning Protocol · verify this page ↗