{"bodies":{"1":"
\n What it executes\n
MsgExecLegacyContent

Changes 1 chain parameter: bank.SendEnabled = [{"denom":"uregen","enabled":true}].

content: {"@type":"/cosmos.params.v1beta1.ParameterChangeProposal","title":"Enable REGEN Transfers","description":"This proposal enables sending and receive REGEN assets. If this proposal passes, the Bank module\\nparameter SendEnable will be updated to true.","changes":[{"subspace":"bank","key":"SendEnabled","value":"[{\\"denom\\":\\"uregen\\",\\"enabled\\":true}]"}]}
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 48,725,447\n abstain 0\n no 48,552\n veto 0\n 48,773,999 REGEN cast, which is 57.3% of the stake bonded today\n
\n What the proposer wrote
This proposal enables sending and receive REGEN assets. If this proposal passes, the Bank module\nparameter SendEnable will be updated to true.
\n
\n submitted 2021-05-31\n voting closed 2021-06-14\n \n deposit 200 / 2,000 REGEN\n \n \n
\n
","2":"
\n What it executes\n
MsgExecLegacyContent

Changes 3 chain parameters: transfer.SendEnabled = true, transfer.ReceiveEnabled = true, bank.DefaultSendEnabled = true.

content: {"@type":"/cosmos.params.v1beta1.ParameterChangeProposal","title":"Enable IBC transfers","description":"This proposal enables transferring and receiving assets using the ICS20 standard on\\nthe Cosmos Hub. If this proposal passes, the Cosmos Transfer module SendEnabled and\\nReceiveEnabled will be set to true. This will allow IBC assets to become available in\\n the Bank module of the Hub and REGEN can be made available on Zones connected over IBC.\\nThe Bank module DefaultSendEnabled will also be set to true so that IBC assets can be\\ntransferred within accounts on the Regen ledger by default.\\nSee full proposal here, https://ipfs.io/ipfs/QmZidittT1dTY5T933gaTCviELGuBXTgfwg532tKogyjVo","changes":[{"subspace":"transfer","key":"SendEnabled","value":"true"},{"subspace":"transfer","key":"ReceiveEnabled","value":"true"},{"subspace":"bank","key":"DefaultSendEnabled","value":"true"}]}
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 49,871,303\n abstain 0\n no 48,552\n veto 0\n 49,919,855 REGEN cast, which is 58.7% of the stake bonded today\n
\n What the proposer wrote
This proposal enables transferring and receiving assets using the ICS20 standard on\nthe Cosmos Hub. If this proposal passes, the Cosmos Transfer module SendEnabled and\nReceiveEnabled will be set to true. This will allow IBC assets to become available in\n the Bank module of the Hub and REGEN can be made available on Zones connected over IBC.\nThe Bank module DefaultSendEnabled will also be set to true so that IBC assets can be\ntransferred within accounts on the Regen ledger by default.\nSee full proposal here, https://ipfs.io/ipfs/QmZidittT1dTY5T933gaTCviELGuBXTgfwg532tKogyjVo
\n
\n submitted 2021-06-02\n voting closed 2021-06-17\n \n deposit 200 / 2,000 REGEN\n \n \n
\n
","3":"
\n What it executes\n
MsgExecLegacyContent

Changes 1 chain parameter: staking.MaxValidators = 75.

content: {"@type":"/cosmos.params.v1beta1.ParameterChangeProposal","title":"Increase MaxValidators value","description":"MaxValidators=50 to MaxValidators=75 / This proposal will increase the number of active validator to 75 in the regen network. You can look at details on forum proposal discussions: https://forum.regen.network/t/proposal-3-increase-validators-seats/224","changes":[{"subspace":"staking","key":"MaxValidators","value":"75"}]}
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 54,148,711\n abstain 2,109,999\n no 562,940\n veto 5\n 56,821,655 REGEN cast, which is 66.8% of the stake bonded today\n
\n What the proposer wrote
MaxValidators=50 to MaxValidators=75 / This proposal will increase the number of active validator to 75 in the regen network. You can look at details on forum proposal discussions: https://forum.regen.network/t/proposal-3-increase-validators-seats/224
\n
\n submitted 2021-07-22\n voting closed 2021-08-06\n \n deposit 254 / 2,000 REGEN\n \n \n
\n
","4":"
\n What it executes\n
MsgExecLegacyContent

Signalling only. Nothing executes on chain if this passes.

content: {"@type":"/cosmos.gov.v1beta1.TextProposal","title":"Regen Ledger v2.0 Upgrade - Signalling Proposal","description":"This proposal is a signalling proposal for the upgrade to Regen Ledger v2.0. The results of this proposal will be interpreted as follows:\\n\\n- A Yes result on the proposal would provide a clear signal that the Regen Network community accepts and understands the upgrade to Regen Ledger v2.0, the decision made to pursue a permissioned ecocredit module design, and the criteria and process for becoming an allowed credit class creator.\\n\\n- A No result on the proposal would force reconsideration of the upgrade to Regen Ledger v2.0, the permissioned ecocredit module design, and/or the criteria and process for becoming an allowed credit class creator.\\n\\nMore details can be found in the long form proposal and the forum discussion:\\n\\n-https://github.com/regen-network/gov\n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 51,645,409\n abstain 11\n no 1,682,290\n veto 0\n 53,327,709 REGEN cast, which is 62.7% of the stake bonded today\n
\n What the proposer wrote
This proposal is a signalling proposal for the upgrade to Regen Ledger v2.0. The results of this proposal will be interpreted as follows:\n\n- A Yes result on the proposal would provide a clear signal that the Regen Network community accepts and understands the upgrade to Regen Ledger v2.0, the decision made to pursue a permissioned ecocredit module design, and the criteria and process for becoming an allowed credit class creator.\n\n- A No result on the proposal would force reconsideration of the upgrade to Regen Ledger v2.0, the permissioned ecocredit module design, and/or the criteria and process for becoming an allowed credit class creator.\n\nMore details can be found in the long form proposal and the forum discussion:\n\n-https://github.com/regen-network/governance/blob/655004214eb9f40a5c2828f7e4abfa2194141e11/proposals/2021-09-regen-ledger-v2-signalling/README.md\n-https://forum.regen.network/t/proposal-4-signalling-proposal-permissioned-credit-class-designers-and-regen-ledger-v2-0-upgrade/251
\n
\n submitted 2021-09-23\n voting closed 2021-10-11\n \n deposit 201 / 2,000 REGEN\n \n \n
\n
","5":"
\n What it executes\n
MsgExecLegacyContent

Upgrades the chain to v2.0-upgrade at block 3,003,343.

content: {"@type":"/cosmos.upgrade.v1beta1.SoftwareUpgradeProposal","title":"Regen Ledger v2.0 Upgrade","description":"This is a software upgrade proposal for the upgrade to Regen Ledger v2.0. If passed, this proposal would commit Regen Mainnet to halting the application binary for Regen Ledger v1.0 at 16:00 UTC on Nov 17th and starting the application binary for Regen Ledger v2.0. \\\\n\\\\nMore details can be found in the long form proposal: https://github.com/regen-network/governance/tree/main/proposals/2021-11-regen-ledger-v2-upgrade","plan":{"name":"v2.0-upgrade","time":"0001-01-01T00:00:00Z","height":"3003343","info":"{\\"binaries\\":{\\"linux/amd64\\": \\"https://github.com/regen-network/regen-ledger/releases/download/v2.0.0/regen-ledger_2.0.0_linux_amd64.zip?checksum=sha256:99c4fddb3a50f3385e808fed3dc2635e1cb61b51fc3c21afb5242d21f191eaf7\\",\\"darwin/amd64\\": \\"https://github.com/regen-netw\n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 53,561,660\n abstain 286\n no 0\n veto 0\n 53,561,946 REGEN cast, which is 63% of the stake bonded today\n
\n What the proposer wrote
This is a software upgrade proposal for the upgrade to Regen Ledger v2.0. If passed, this proposal would commit Regen Mainnet to halting the application binary for Regen Ledger v1.0 at 16:00 UTC on Nov 17th and starting the application binary for Regen Ledger v2.0. \n\nMore details can be found in the long form proposal: https://github.com/regen-network/governance/tree/main/proposals/2021-11-regen-ledger-v2-upgrade
\n
\n submitted 2021-11-01\n voting closed 2021-11-15\n \n deposit 200 / 2,000 REGEN\n \n \n
\n
","6":"
\n What it executes\n
MsgExecLegacyContent

Signalling only. Nothing executes on chain if this passes.

content: {"@type":"/cosmos.gov.v1beta1.TextProposal","title":"Set a minimum validator commission rate of 5%","description":"Very low commissions rates are bad for our network with validators commissions rates racing to the bottom. Validators potentially running at a loss to gain share of delegation is unhealthy and doesn’t encourage decentralization.\\nThis proposal is to set a minimum validator commission of 5%. This could either be enforced through a change in the network via a software upgrade at a later date and/or by limiting any RND/Community/Foundation delegations to those validators with 5% commission rate or greater.\\nSee here for more details and discussion: https://forum.regen.network/t/set-the-validator-minimum-commission-rate-to-5/316"}
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 40,281,750\n abstain 35\n no 5,487,214\n veto 273\n 45,769,271 REGEN cast, which is 53.8% of the stake bonded today\n
\n What the proposer wrote
Very low commissions rates are bad for our network with validators commissions rates racing to the bottom. Validators potentially running at a loss to gain share of delegation is unhealthy and doesn’t encourage decentralization.\nThis proposal is to set a minimum validator commission of 5%. This could either be enforced through a change in the network via a software upgrade at a later date and/or by limiting any RND/Community/Foundation delegations to those validators with 5% commission rate or greater.\nSee here for more details and discussion: https://forum.regen.network/t/set-the-validator-minimum-commission-rate-to-5/316
\n
\n submitted 2021-11-18\n voting closed 2021-12-02\n \n deposit 200 / 2,000 REGEN\n \n \n
\n
","7":"
\n What it executes\n
MsgExecLegacyContent

Signalling only. Nothing executes on chain if this passes.

content: {"@type":"/cosmos.gov.v1beta1.TextProposal","title":"IBC Patch Upgrade","description":"The recent upgrade to Regen Ledger v2 was a great success. However there's a bug in the integration, which created an issue for IBC transfers. IBC transfers are not going through currently due to a missing migration for the IBC module. Regen Ledger v2.1.0 fixes that and this proposal is to conduct an emergency upgrade to avoid any further potential issues with IBC client expiry. If IBC clients expire, the funds would get stuck in the expired channel, so we need to upgrade the network to fix this before IBC clients expire.\\n\\nThis proposal expects every validator to update their regen software to v2.1.0 before the block height 3126912 and then to vote on this proposal. A yes vote on this proposal conveys that the validator has updated their binaries to v2.1.0.\\n\\nEstimated update time is Friday\n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 69,155,293\n abstain 5,005\n no 0\n veto 0\n 69,160,298 REGEN cast, which is 81.3% of the stake bonded today\n
\n What the proposer wrote
The recent upgrade to Regen Ledger v2 was a great success. However there's a bug in the integration, which created an issue for IBC transfers. IBC transfers are not going through currently due to a missing migration for the IBC module. Regen Ledger v2.1.0 fixes that and this proposal is to conduct an emergency upgrade to avoid any further potential issues with IBC client expiry. If IBC clients expire, the funds would get stuck in the expired channel, so we need to upgrade the network to fix this before IBC clients expire.\n\nThis proposal expects every validator to update their regen software to v2.1.0 before the block height 3126912 and then to vote on this proposal. A yes vote on this proposal conveys that the validator has updated their binaries to v2.1.0.\n\nEstimated update time is Friday, 26th Nov, 1700UTC.\n\nMore details are available in the long-form proposal: https://github.com/regen-network/governance/tree/main/proposals/2021-11-ibc-patch-upgrade
\n
\n submitted 2021-11-24\n voting closed 2021-12-08\n \n deposit 200 / 2,000 REGEN\n \n \n
\n
","8":"
\n What it executes\n
MsgExecLegacyContent

Changes 1 chain parameter: ecocredit.AllowedClassCreators = [\n "regen123a7e9gvgm53zvswc6daq7c85xtzt8263lgasm"\n ].

content: {"@type":"/cosmos.params.v1beta1.ParameterChangeProposal","title":"Credit Class Creator - Regen Registry","description":"This is a parameter change proposal to add a multisig address for Regen Registry, currently managed by members of Regen Network Development (RND), to the list of allowed credit class creators. The RND staff are applying on behalf of Regen Registry, which we envision will become the first community governed registry program, owned and operated by experts committed to ecological regeneration.\\n\\nFor more information, see the long-form proposal: https://github.com/regen-network/governance/tree/main/proposals/2021-12-regen-registry-credit-class-creator","changes":[{"subspace":"ecocredit","key":"AllowedClassCreators","value":"[\\n                \\"regen123a7e9gvgm53zvswc6daq7c85xtzt8263lgasm\\"\\n            ]"}]}
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 57,055,072\n abstain 4,104\n no 0\n veto 0\n 57,059,177 REGEN cast, which is 67.1% of the stake bonded today\n
\n What the proposer wrote
This is a parameter change proposal to add a multisig address for Regen Registry, currently managed by members of Regen Network Development (RND), to the list of allowed credit class creators. The RND staff are applying on behalf of Regen Registry, which we envision will become the first community governed registry program, owned and operated by experts committed to ecological regeneration.\n\nFor more information, see the long-form proposal: https://github.com/regen-network/governance/tree/main/proposals/2021-12-regen-registry-credit-class-creator
\n
\n submitted 2021-12-23\n voting closed 2022-01-07\n \n deposit 200 / 2,000 REGEN\n \n \n
\n
","9":"
\n What it executes\n
MsgExecLegacyContent

Upgrades the chain to v3.0.0 at block 4,623,339.

content: {"@type":"/cosmos.upgrade.v1beta1.SoftwareUpgradeProposal","title":"Regen Ledger v3.0 Upgrade","description":"This is a software upgrade proposal for the upgrade to Regen Ledger v3.0. If passed, this proposal would commit Regen Mainnet to halting the application binary for Regen Ledger v2.1 at approximately 16:00 UTC on March 14th at block height 4623339 and starting the application binary for Regen Ledger v3.0. \\\\n\\\\nMore details can be found in the long form proposal: https://github.com/regen-network/governance/tree/main/proposals/2022-02-regen-ledger-v3.0-upgrade","plan":{"name":"v3.0.0","time":"0001-01-01T00:00:00Z","height":"4623339","info":"{\\"binaries\\":{\\"linux/amd64\\":\\"https://github.com/regen-network/regen-ledger/releases/download/v3.0.0/regen-ledger_3.0.0_linux_amd64.zip?checksum=sha256:5f297431c1e14d81319609564e392295e82c847cf78f295694961f9bded5419e\\",\\"darwin/amd64\n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 69,970,254\n abstain 80,166\n no 5,202\n veto 0\n 70,055,622 REGEN cast, which is 82.4% of the stake bonded today\n
\n What the proposer wrote
This is a software upgrade proposal for the upgrade to Regen Ledger v3.0. If passed, this proposal would commit Regen Mainnet to halting the application binary for Regen Ledger v2.1 at approximately 16:00 UTC on March 14th at block height 4623339 and starting the application binary for Regen Ledger v3.0. \n\nMore details can be found in the long form proposal: https://github.com/regen-network/governance/tree/main/proposals/2022-02-regen-ledger-v3.0-upgrade
\n
\n submitted 2022-02-26\n voting closed 2022-03-12\n \n deposit 200 / 2,000 REGEN\n \n \n
\n
","10":"
\n What it executes\n
MsgExecLegacyContent

Changes 1 chain parameter: gov.votingparams = {"voting_period": "604800000000000"}.

content: {"@type":"/cosmos.params.v1beta1.ParameterChangeProposal","title":"Decrease Voting Period","description":"This is a parameter change proposal decreasing the voting period for all governance proposals from 14 days to 7 days.\\n\\nMore information can be found in the long-form proposal: https://github.com/regen-network/governance/tree/main/proposals/2022-03-decrease-voting-period","changes":[{"subspace":"gov","key":"votingparams","value":"{\\"voting_period\\": \\"604800000000000\\"}"}]}
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 61,391,379\n abstain 4,824,557\n no 1,284,792\n veto 587\n 67,501,316 REGEN cast, which is 79.4% of the stake bonded today\n
\n What the proposer wrote
This is a parameter change proposal decreasing the voting period for all governance proposals from 14 days to 7 days.\n\nMore information can be found in the long-form proposal: https://github.com/regen-network/governance/tree/main/proposals/2022-03-decrease-voting-period
\n
\n submitted 2022-03-17\n voting closed 2022-03-31\n \n deposit 200 / 2,000 REGEN\n \n \n
\n
","11":"
\n What it executes\n
MsgExecLegacyContent

Signalling only. Nothing executes on chain if this passes.

content: {"@type":"/cosmos.gov.v1beta1.TextProposal","title":"Community Assistance Regarding Lost Genesis Wallets","description":"# Overview\\\\nThis proposal aims to assist token sale participants and Regen community members as described and discussed during soft proposal period\\\\n\\\\n# Proposal\\\\n1. Token sale participants who are unable to access their tokens since genesis and whose tokens have never been transferred or staked or touched in any way can opt-in to participate in new issuance as a one time courtesy\\\\n2. Participants can choose a new address to receive their issuance\\\\n3. Participants consent that once this change has been submitted the public key can never be changed again\\\\n4. This change would be completed by dev team and included with update to Regen Ledger v4.0\\\\n5. Regen Foundation will assist with identity verification and wallet address collection\\\\n6. Participation \n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 49,121,781\n abstain 11,583,433\n no 11,962\n veto 608\n 60,717,785 REGEN cast, which is 71.4% of the stake bonded today\n
\n What the proposer wrote
Overview\nThis proposal aims to assist token sale participants and Regen community members as described and discussed during soft proposal period\n\nProposal\n1. Token sale participants who are unable to access their tokens since genesis and whose tokens have never been transferred or staked or touched in any way can opt-in to participate in new issuance as a one time courtesy\n2. Participants can choose a new address to receive their issuance\n3. Participants consent that once this change has been submitted the public key can never be changed again\n4. This change would be completed by dev team and included with update to Regen Ledger v4.0\n5. Regen Foundation will assist with identity verification and wallet address collection\n6. Participation window will close upon announcement of Regen Ledger v4.0\n\nAppendix / Activity\n- CommonWealth\nhttps://commonwealth.im/regen/discussion/3540-in-need-of-communities-assistance-tokens-lost-in-wallet-conversion\n\n- Discord\nhxxps://discord[.]com/channels/684494798358315010/684495386915766358/955616163935703057
\n
\n submitted 2022-04-05\n voting closed 2022-04-12\n \n deposit 200 / 2,000 REGEN\n \n \n
\n
","12":"
\n What it executes\n
MsgExecLegacyContent

Pays 400,000 REGEN out of the community pool to regen1geu8vpq75kkc3yld9k9tp8jqcykeaguv7tnh8p.

content: {"@type":"/cosmos.distribution.v1beta1.CommunityPoolSpendProposal","title":"Climate Wiki - Community Pool Funding","description":"This is a community fund proposal to provide the regenerative media non-profit Branch Out with $REGEN to launch Climate Wiki, following six months of discussion between Branch Out and the Regen Network & Foundation. \\n\\n Based on the proposal discussion & poll last week, a two-thirds consensus was established for an allocation of 500k $REGEN. We have decided to ask for 400k $REGEN, with the intention of establishing an even stronger consensus for the official proposal. \\n\\n One-third of this budget will be dedicated to discretionary spending, for Branch Out to used as needed to pay a small team full-time to complete the launch (phase 1) of the Web2 MVP of Climate Wiki (e.t.a. Fall 2022). \\n\\n Two-thirds of the budget will be reserved for a staking 'mi\n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 51,924,935\n abstain 150,472\n no 499\n veto 6\n 52,075,913 REGEN cast, which is 61.2% of the stake bonded today\n
\n What the proposer wrote
This is a community fund proposal to provide the regenerative media non-profit Branch Out with $REGEN to launch Climate Wiki, following six months of discussion between Branch Out and the Regen Network & Foundation. \n\n Based on the proposal discussion & poll last week, a two-thirds consensus was established for an allocation of 500k $REGEN. We have decided to ask for 400k $REGEN, with the intention of establishing an even stronger consensus for the official proposal. \n\n One-third of this budget will be dedicated to discretionary spending, for Branch Out to used as needed to pay a small team full-time to complete the launch (phase 1) of the Web2 MVP of Climate Wiki (e.t.a. Fall 2022). \n\n Two-thirds of the budget will be reserved for a staking 'mini-endaoment', then dedicated to a planned $BRANCH/$REGEN Liquidity Pool upon the launch (phase 2) of the $BRANCH token. \n\n During the token launch, Branch Out will airdrop $BRANCH tokens to $REGEN holders to replenish the community pool (beyond what is allocated), support $REGEN, and provide a stimulus for $REGEN holders to commission Climate Wiki pages. \n\n Climate Wiki is a ‘sprouting’ knowledge commons tackling the interrelated challenges of information overload, knowledge inequity, and knowledge-action disconnect. Its priority is aligning the interests of our stakeholders: land stewards, ReFi investors, and climate writers. It will subtly offer Web3 features while working as a familiar Web2 Wiki. \n\n Full Proposal, Discussion & Poll: https://commonwealth.im/regen/discussion/5164-climate-wiki-discussion-poll-for-community-pool-funding-proposal \n\n Regenerati News Hour Discussion: hxxps://twitter[.]com/regen_network/status/1532376577098383365?s=20&t=mxGDVAr87heEqPolR9zJgg \n\n Video Tour of Sample Page (Biochar), built in support of eco-credit methodology development on Regen: hxxps://www[.]loom[.]com/share/bad997e478514b6a89a0321aefa5527b \n\n Climate Wiki's Built on Regen card: hxxps://www[.]notion[.]so/Climate-Wiki-0d2b6c34ddab46ec8cbfab5b8b6dcbcf
\n
\n submitted 2022-06-06\n voting closed 2022-06-13\n \n deposit 200 / 2,000 REGEN\n \n \n
\n
","13":"
\n What it executes\n
MsgExecLegacyContent

Signalling only. Nothing executes on chain if this passes.

content: {"@type":"/cosmos.gov.v1beta1.TextProposal","title":"Adoption of Currency Allow List Criteria","description":"# Currency Allow List Criteria \\n\\nThis is a text proposal for the community to adopt a set of criteria as guidelines when evaluating future governance proposals to enable specific currencies in Regen Network's on-chain marketplace. \\n\\n* A Yes result on the proposal would provide a clear signal that the Regen Network community accepts the following as guidelines for evaluation criteria when discussing and voting to enable currencies in the allow list for use in Regen Network's ecocredit marketplace. \\n\\n* A No result on the proposal would force reconsideration of the criteria as outlined here. \\n\\n## Background \\n\\nRegen Ledger v4.0 includes a new on-chain marketplace that enables ecocredits to be listed for sale by their owners. In other words, a user who has ecocredit\n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 70,772,323\n abstain 5,760,262\n no 259\n veto 0\n 76,532,844 REGEN cast, which is 90% of the stake bonded today\n
\n What the proposer wrote
Currency Allow List Criteria \n\nThis is a text proposal for the community to adopt a set of criteria as guidelines when evaluating future governance proposals to enable specific currencies in Regen Network's on-chain marketplace. \n\n* A Yes result on the proposal would provide a clear signal that the Regen Network community accepts the following as guidelines for evaluation criteria when discussing and voting to enable currencies in the allow list for use in Regen Network's ecocredit marketplace. \n\n* A No result on the proposal would force reconsideration of the criteria as outlined here. \n\nBackground \n\nRegen Ledger v4.0 includes a new on-chain marketplace that enables ecocredits to be listed for sale by their owners. In other words, a user who has ecocredits (unretired) in their account can list any number of their credits for sale (creating a standing 'sell order'). The credits are escrowed on-chain, and another user can purchase up to the full quantity of credits in the sell order at the specified price. \n\nIn order to prevent fragmented markets and an over-complicated end-user experience, credits cannot be listed in the marketplace in any currency at all. Rather, the listed of allowed 'currencies' that ecocredits can be listed for sale in is controlled through on-chain governance. \n\nThe desire from the team at RND, Inc is to have this list be relatively small, but leave the explicit control of which currencies to enable in the marketplace up to the Regen Network token holders. \n\nThat being said, we (at RND, Inc) would like to propose a set of criteria for the community to use when evaluating accepting newly proposed currencies for use in the ecocredit marketplace. The initial conversation was started on the commonwealth forum here: https://commonwealth.im/regen/discussion/4959-adding-tokens-to-the-regen-ledger-currency-allow-list, and are now continuing that conversation in the from of this on-chain governance proposal. \n\nAllow List Criteria \n\nWe propose there are four major criteria for the analysis of any token applying to the Regen Network community: \n\n1. Is the token in question a currency? \n\n2. Is the token in question IBC compatible? \n\n3. Is the token in question liquid, stable and safe to use? \n\n4. Does the token support a good onboarding experience for non crypto natives? \n\nIn addition to these criteria we would propose the following principles for consideration: \n\n1. Ethical alignment with Regen Network aims: Is the currency in question something that supports or enables a better world, and most specifically ecological regeneration? \n\n2. Virtuous cycle with Regen Network's Ecocredits or other ecological asset types: Examples of this include opportunities for inclusion of ecocredits into a stable coin's collateral system \n\nWhile there are no specific requirements around to what extent a currency must adhere to the above criteria, we encourage deliberation and evaluation of currencies in the allow list to be focused on these criteria as discussion points. Proposal on Github: https://github.com/regen-network/governance/tree/main/proposals/2022-07-currency-allow-list
\n
\n submitted 2022-07-15\n voting closed 2022-07-22\n \n deposit 201 / 2,000 REGEN\n \n \n
\n
","14":"
\n What it executes\n
MsgExecLegacyContent

Upgrades the chain to v4.0.0 at block 6,589,400.

content: {"@type":"/cosmos.upgrade.v1beta1.SoftwareUpgradeProposal","title":"Regen Ledger v4.0 Upgrade","description":"This is a software upgrade proposal for the upgrade to Regen Ledger v4.0. If passed, this proposal would commit Regen Mainnet to halting the application binary for Regen Ledger v3.0 at approximately 16:00 UTC on August 4th at block height 6589400 and requiring nodes to restart with the application binary for Regen Ledger v4.0.\\\\n\\\\nMore details can be found in the long form proposal: https://github.com/regen-network/governance/tree/main/proposals/2022-07-regen-ledger-v4.0-upgrade","plan":{"name":"v4.0.0","time":"0001-01-01T00:00:00Z","height":"6589400","info":"{\\"binaries\\":{\\"linux/amd64\\":\\"https://github.com/regen-network/regen-ledger/releases/download/v4.0.0/regen-ledger_4.0.0_linux_amd64.zip?checksum=sha256:ca8e6020f2024f4cdb7722f917650a6334ad1f3068a8d14b0dba226bdd5\n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 80,160,520\n abstain 2,472,281\n no 5\n veto 155\n 82,632,961 REGEN cast, which is 97.2% of the stake bonded today\n
\n What the proposer wrote
This is a software upgrade proposal for the upgrade to Regen Ledger v4.0. If passed, this proposal would commit Regen Mainnet to halting the application binary for Regen Ledger v3.0 at approximately 16:00 UTC on August 4th at block height 6589400 and requiring nodes to restart with the application binary for Regen Ledger v4.0.\n\nMore details can be found in the long form proposal: https://github.com/regen-network/governance/tree/main/proposals/2022-07-regen-ledger-v4.0-upgrade
\n
\n submitted 2022-07-27\n voting closed 2022-08-03\n \n deposit 200 / 2,000 REGEN\n \n \n
\n
","15":"
\n What it executes\n
MsgExecLegacyContent

Lets credits be sold for USDC.grv on the marketplace.

content: {"@type":"/regen.ecocredit.marketplace.v1.AllowDenomProposal","title":"Add Gravity USDC to Regen Marketplace Currency Allow List","description":"\\nThis proposal, if passed, will add USDC bridged from Gravity Bridge to the Regen Ecocredit Marketplace allow list, adding it as one of the many currency options in which buyers/sellers may transact. \\n\\nAdding Gravity USDC will add the framework needed for a seamless onboarding experience targeting ETH native and non-crypto native buyers and sellers, thus covering one of the many use-cases described in discussions by RND and Regen community members. \\n\\nAdding Gravity Bridge’s transactional capabilities will help the Regen Marketplace’s goal of coin plurality by increasing the currency options for buyers/sellers.\\n\\n* A **YES** result on proposal will add `USDC.grv` to the allow list, represented by the ibc denom: `ibc/9B1FC3F80786ACD\n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 79,961,815\n abstain 2,417,283\n no 20,097\n veto 0\n 82,399,195 REGEN cast, which is 96.9% of the stake bonded today\n
\n What the proposer wrote
This proposal, if passed, will add USDC bridged from Gravity Bridge to the Regen Ecocredit Marketplace allow list, adding it as one of the many currency options in which buyers/sellers may transact. \n\nAdding Gravity USDC will add the framework needed for a seamless onboarding experience targeting ETH native and non-crypto native buyers and sellers, thus covering one of the many use-cases described in discussions by RND and Regen community members. \n\nAdding Gravity Bridge’s transactional capabilities will help the Regen Marketplace’s goal of coin plurality by increasing the currency options for buyers/sellers.\n\n* A YES result on proposal will add `USDC.grv` to the allow list, represented by the ibc denom: `ibc/9B1FC3F80786ACDD1808854BCFD234AFB71471C3972FF3DE0E279AFD2D50FDE4`\n\n* A NO result would not add USDC.grv to the allow list\n\nAdditional Information:\n\nWhat makes the Gravity Bridge USDC such a valuable asset to the Regen Community?\n\nGravity USDC is USDC that has been bridged across Gravity Bridge: https://gravitybridge.net to make it IBC compatible. Gravity USDC can be sent to any IBC enabled chain such as Regen, and the token balance is displayed in Cosmos wallets such as Keplr and Cosmostation. \n\nGravity Bridge key advantages include:\n\n* Open access, permissionless, decentralized & neutral bridge, thus aligned with the core principles of Regen Network\n* Secured by a 150+ tendermint node validator set forming consensus and governing bridge (Gravity Bridge does not simply use multisig accounts for control/governance)\n* Uses NOT UPGRADEABLE smart contract Gravity.sol which has been extensively audited and forked, thus it has the most time in production for any Eth/Cosmos bridge\n* Over $10million USDC liquidity already bridged into the Cosmos ecosystem\n* Batched deposits ensure users receive the lowest gas fees of any bridge\n\nFor recap, the [Regen Prop 13 guidelines](​​https://www.mintscan.io/regen/proposals/13) ask:\n\n1. Is the token in question a currency? \n USDC is a fully reserved stablecoin that is externally audited. Please see more details here: https://www.circle.com/en/usdc#transparency\n USDC is USD Coin: https://www.centre.io/usdc issued by Centre, a partnership between Coinbase and Circle.\n\n2. Is the token in question IBC compatible?\n Gravity USDC is IBC compatible. ETH-based USDC is locked in the Gravity Bridge contract, validated by a decentralized Cosmos validator set, then an IBC representation is minted. \n\n3. Is the token in question liquid, stable and safe to use?\n Gravity Bridge is the most decentralized and most integrated bridge in the Cosmos ecosystem. Gravity Bridge offers highest security having been audited by Code4Rena, LeastAuthority, Informal, and Certik. \n Audit reports and more information can be found in security docs: https://github.com/Gravity-Bridge/Gravity-Docs/blob/main/docs/security.md\n Also, USDC is the largest and most credible stablecoin available at this time.\n\n4. Does the token support a good onboarding experience for non crypto natives?\n USDC currently provides one of the best onboarding experiences of any stablecoin.\n Gravity Bridge provides IBC auto-forwarding from Ethereum. Allowing tokens to be sent directly from Ethereum to Regen network with only one Metamask transaction. Such transactions can be sent using The Blockscape Gravity Bridge frontend: hxxps://bridge[.]blockscape[.]network/ or with a Regen-native front end using Gravity Bridge decentralized frontend integrators API: https://github.com/Gravity-Bridge/Gravity-Docs/blob/main/docs/frontend-creation.md\n\n5. Is the currency in question something that supports or enables a better world, and most specifically ecological regeneration?\n Since USDC is issued on Ethereum, its ecological impact is decidedly negative until the ETH2.0 merge has completed. Despite this, we believe that USDC is by far the most credible and liquid stablecoin at this time, opening up opportunities for Regen Network to sell larger volumes of credits to a wider audience.\n\nFinal Thoughts\n\nFor the Regen Marketplace to open and transactions to begin, viable currencies need to be added to the allow list. The marketplace is launching with discovery and experimentation in mind as the community finds which currencies deliver the best user experiences.\n\nRegen Marketplace’s value proposition will increase by adding Gravity USDC, which will bring a stable, trusted, and secure currency through a decentralized bridge, helping it to grow and achieve its goals in becoming the leading marketplace for tokenized ecological assets.\n\nFurther discussion can be found in the commonwealth thread on this topic: https://commonwealth.im/regen/discussion/6457-usdc-to-regen-ledger-via-gravity-bridge\n\n> .
\n
\n submitted 2022-09-02\n voting closed 2022-09-09\n \n deposit 201 / 2,000 REGEN\n \n \n
\n
","16":"
\n What it executes\n
MsgExecLegacyContent

Lets credits be sold for USDC.axl on the marketplace.

content: {"@type":"/regen.ecocredit.marketplace.v1.AllowDenomProposal","title":"Adding Axelar USDC as a marketplace currency","description":"\\nThis proposal, if passed, will add Axelar USDC bridged from Osmosis to the Regen Ecocredit Marketplace allow list, adding it as one of the many currency options in which buyers/sellers may transact. \\n\\nAdding Axelar USDC will add the framework needed for a seamless onboarding experience targeting Osmosis buyers and sellers, thus covering one of the many use-cases described in discussions by RND and Regen community members. \\n\\n A **YES** result on proposal will add `USDC.axl` to the allow list, represented by the ibc denom: `ibc/D189335C6E4A68B513C10AB227BF1C1D38C746766278BA3EEB4FB14124F1D858`\\n\\n* A **NO** result would not add USDC.axl to the allow list\\n\\n\\n","denom":{"bank_denom":"ibc/D189335C6E4A68B513C10AB227BF1C1D38C746766278BA3EEB4FB14124F\n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 22,737,136\n abstain 32,147\n no 58,205,386\n veto 30,270\n 81,004,939 REGEN cast, which is 95.2% of the stake bonded today\n
\n What the proposer wrote
This proposal, if passed, will add Axelar USDC bridged from Osmosis to the Regen Ecocredit Marketplace allow list, adding it as one of the many currency options in which buyers/sellers may transact. \n\nAdding Axelar USDC will add the framework needed for a seamless onboarding experience targeting Osmosis buyers and sellers, thus covering one of the many use-cases described in discussions by RND and Regen community members. \n\n A YES result on proposal will add `USDC.axl` to the allow list, represented by the ibc denom: `ibc/D189335C6E4A68B513C10AB227BF1C1D38C746766278BA3EEB4FB14124F1D858`\n\n* A NO result would not add USDC.axl to the allow list
\n
\n submitted 2022-09-04\n voting closed 2022-09-11\n \n deposit 200 / 2,000 REGEN\n \n \n
\n
","17":"
\n What it executes\n
MsgExecLegacyContent

Lets credits be sold for USDC.axl on the marketplace.

content: {"@type":"/regen.ecocredit.marketplace.v1.AllowDenomProposal","title":"Adding Axelar USDC as a marketplace currency","description":"\\nThis proposal, if passed, will add Axelar USDC bridged from Axelar to the Regen Ecocredit Marketplace allow list, adding it as one of the many currency options in which buyers/sellers may transact. \\n\\n Adding Axelar USDC will add the framework needed for a seamless onboarding experience targeting Osmosis buyers and sellers, thus covering one of the many use-cases described in discussions by RND and Regen community members. \\n\\n A YES result on proposal will add USDC.axl to the allow list, represented by the ibc denom: ibc/334740505537E9894A64E8561030695016481830D7B36E6A9B6D13C608B55653\\n\\n* A NO result would not add USDC.axl to the allow list\\n\\n\\n Note: Proposal 16 talked about Osmosis IBC'd axlUSDC while this does not, it is upon community to c\n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 73,912,933\n abstain 2,573,386\n no 1,799\n veto 1,506\n 76,489,625 REGEN cast, which is 89.9% of the stake bonded today\n
\n What the proposer wrote
This proposal, if passed, will add Axelar USDC bridged from Axelar to the Regen Ecocredit Marketplace allow list, adding it as one of the many currency options in which buyers/sellers may transact. \n\n Adding Axelar USDC will add the framework needed for a seamless onboarding experience targeting Osmosis buyers and sellers, thus covering one of the many use-cases described in discussions by RND and Regen community members. \n\n A YES result on proposal will add USDC.axl to the allow list, represented by the ibc denom: ibc/334740505537E9894A64E8561030695016481830D7B36E6A9B6D13C608B55653\n\n* A NO result would not add USDC.axl to the allow list\n\n Note: Proposal 16 talked about Osmosis IBC'd axlUSDC while this does not, it is upon community to choose which path they want to follow
\n
\n submitted 2022-09-12\n voting closed 2022-09-19\n \n deposit 200 / 2,000 REGEN\n \n \n
\n
","18":"
\n What it executes\n
MsgExecLegacyContent

Lets credits be sold for EEUR on the marketplace.

content: {"@type":"/regen.ecocredit.marketplace.v1.AllowDenomProposal","title":"Add e-Money EEUR to marketplace allow list","description":"If this proposal passes, e-Money EEUR will be added to the Regen Ecocredit Marketplace allow list.\\n\\nE-money (www[.]e-money[.]com) has been working on adding trustworthy, transparent and asset-backed stablecoins to the Cosmos ecosystem and beyond since 2018. We have put in a lot of effort to be compliant with EU regulation and periodically publish proof-of-funds to document that the issuance is fully backed.\\n\\nA YES result on proposal will add e-Money EEUR to the allow list, represented by the ibc denom: ibc/F694C7575DF3B8128746FA6576830DA27891D5A322DF5DECB066288FC4948F76\\n\\nMore details and a brief discussion can be found at https://commonwealth.im/regen/discussion/6594-eeur-to-regen-ledger-via-ibc","denom":{"bank_denom":"ibc/F694C7575DF3B8128746FA6576\n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 69,531,474\n abstain 2,678,293\n no 10\n veto 0\n 72,209,777 REGEN cast, which is 84.9% of the stake bonded today\n
\n What the proposer wrote
If this proposal passes, e-Money EEUR will be added to the Regen Ecocredit Marketplace allow list.\n\nE-money (www[.]e-money[.]com) has been working on adding trustworthy, transparent and asset-backed stablecoins to the Cosmos ecosystem and beyond since 2018. We have put in a lot of effort to be compliant with EU regulation and periodically publish proof-of-funds to document that the issuance is fully backed.\n\nA YES result on proposal will add e-Money EEUR to the allow list, represented by the ibc denom: ibc/F694C7575DF3B8128746FA6576830DA27891D5A322DF5DECB066288FC4948F76\n\nMore details and a brief discussion can be found at https://commonwealth.im/regen/discussion/6594-eeur-to-regen-ledger-via-ibc
\n
\n submitted 2022-09-14\n voting closed 2022-09-21\n \n deposit 200 / 2,000 REGEN\n \n \n
\n
","19":"
\n What it executes\n
MsgExecLegacyContent

Upgrades the chain to v4.1.0 at block 7,479,500.

content: {"@type":"/cosmos.upgrade.v1beta1.SoftwareUpgradeProposal","title":"Regen Ledger v4.1 Upgrade","description":"This is a software upgrade proposal for the upgrade to Regen Ledger v4.1.1. If passed, this proposal would commit Regen Mainnet to halting the application binary for Regen Ledger v4.0 at block height 7479500 (approximately 16:00 UTC on Friday, October 7th) and requiring nodes to restart with the application binary for Regen Ledger v4.1.1. \\\\n\\\\nMore details can be found in the long form proposal: https://github.com/regen-network/governance/tree/main/proposals/2022-09-regen-ledger-v4.1-upgrade","plan":{"name":"v4.1.0","time":"0001-01-01T00:00:00Z","height":"7479500","info":"{\\"binaries\\":{\\"linux/amd64\\":\\"https://github.com/regen-network/regen-ledger/releases/download/v4.1.1/regen-ledger_4.1.1_linux_amd64.zip?checksum=sha256:3e6e45575638327453d82ff4443f3c672aa7b5d74fc31c\n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 84,375,324\n abstain 2,613,491\n no 345\n veto 3\n 86,989,163 REGEN cast, which is 102.3% of the stake bonded today\n
\n What the proposer wrote
This is a software upgrade proposal for the upgrade to Regen Ledger v4.1.1. If passed, this proposal would commit Regen Mainnet to halting the application binary for Regen Ledger v4.0 at block height 7479500 (approximately 16:00 UTC on Friday, October 7th) and requiring nodes to restart with the application binary for Regen Ledger v4.1.1. \n\nMore details can be found in the long form proposal: https://github.com/regen-network/governance/tree/main/proposals/2022-09-regen-ledger-v4.1-upgrade
\n
\n submitted 2022-09-29\n voting closed 2022-10-06\n \n deposit 200 / 2,000 REGEN\n \n \n
\n
","20":"
\n What it executes\n
MsgExecLegacyContent

Lets credits be sold for regen on the marketplace.

content: {"@type":"/regen.ecocredit.marketplace.v1.AllowDenomProposal","title":"Add REGEN to the Regen Marketplace currency AllowList","description":"This proposal, if passed, will add REGEN to the Regen Ecocredit Marketplace allow list, adding it as one of the many currency options in which buyers and sellers may transact./nA YES result on proposal will add REGEN to the allow list, represented by the denom:/nbank_denom: uregen/ndisplay_denom: regen/nexponent: 6/nA NO result would not add REGEN to the allow list.","denom":{"bank_denom":"uregen","display_denom":"regen","exponent":6}}
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 74,893,609\n abstain 1,366,556\n no 21,480\n veto 0\n 76,281,644 REGEN cast, which is 89.7% of the stake bonded today\n
\n What the proposer wrote
This proposal, if passed, will add REGEN to the Regen Ecocredit Marketplace allow list, adding it as one of the many currency options in which buyers and sellers may transact./nA YES result on proposal will add REGEN to the allow list, represented by the denom:/nbank_denom: uregen/ndisplay_denom: regen/nexponent: 6/nA NO result would not add REGEN to the allow list.
\n
\n submitted 2022-10-26\n voting closed 2022-11-02\n \n deposit 200 / 2,000 REGEN\n \n \n
\n
","21":"
\n What it executes\n
MsgExecLegacyContent

Signalling only. Nothing executes on chain if this passes.

content: {"@type":"/cosmos.gov.v1beta1.TextProposal","title":"Signal Proposal: Offset Regen Validator Set","description":"Description\\n\\nVoting YES to this signalling proposal indicates approval to address Regen's historic carbon emission footprint for mainnet and testnet by purchasing 6,147 carbon credits at worst-case projections. \\n\\nVoting NO to this proposal indicates that this funding should not be allocated.\\n\\nBased on feedback from carbon footprint data reported by validators of Regen Network, Regen has emitted at most 4,637 tons of carbon since the start of mainnet and an additional 1,510 tons since the start of testnet, through the end of 2022. Some assumptions have been made for testnets where data is unavailable. The total carbon emission for all networks is an estimated 6,147 tons.\\n\\nThis proposal signals intent to use a portion of the Community Pool to purchase and retire\n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 73,891,362\n abstain 1,639\n no 79,977\n veto 0\n 73,972,978 REGEN cast, which is 87% of the stake bonded today\n
\n What the proposer wrote
Description\n\nVoting YES to this signalling proposal indicates approval to address Regen's historic carbon emission footprint for mainnet and testnet by purchasing 6,147 carbon credits at worst-case projections. \n\nVoting NO to this proposal indicates that this funding should not be allocated.\n\nBased on feedback from carbon footprint data reported by validators of Regen Network, Regen has emitted at most 4,637 tons of carbon since the start of mainnet and an additional 1,510 tons since the start of testnet, through the end of 2022. Some assumptions have been made for testnets where data is unavailable. The total carbon emission for all networks is an estimated 6,147 tons.\n\nThis proposal signals intent to use a portion of the Community Pool to purchase and retire these credits. 80% of these carbon credits will be purchased via the soon to be launched NCT token on Osmosis. 20% will be purchased using City Forest Credits in the Regen Network marketplace.\n\nDue to the NCT pool not launching until early 2023, this proposal signals intent rather than initiating the community pool spend immediately. The total cost of the 6,147 credits would cost approximately $82,623. At current $REGEN price, and factoring in a 20% buffer for price volatility, approximately 430,425 $REGEN would be required to carry out this offset. \n\nMethod\n\nThe $REGEN would be transferred to a multi-sig wallet on the Regen Network, and the agreed amount of City Forest Credits and NCT would be purchased and retired manually by the multi-sig owners.\n\nThe multi-sig wallet would be managed by:\nDanny Qwoyn (Regen Network)\nECO Stake (Validator)\nLOA Labs (Validator)\n\nAny $REGEN remaining due to price fluctuations below the intentional 20% buffer to mitigate any price volatility, and a potentially lower NCT/CFC cost, would be returned to the Regen Community Pool.\n\nDiscussion: https://forum.regen.network/discussion/7829-proposal-offset-regen-validator-set
\n
\n submitted 2022-12-15\n voting closed 2022-12-22\n \n deposit 200 / 2,000 REGEN\n \n \n
\n
","22":"
\n What it executes\n
MsgExecLegacyContent

Upgrades the chain to v5.0 at block 8,942,600.

content: {"@type":"/cosmos.upgrade.v1beta1.SoftwareUpgradeProposal","title":"Regen Ledger v5.0 Upgrade","description":"This is a software upgrade proposal for the upgrade to Regen Ledger v5.0. If passed, this proposal would commit Regen Mainnet to halting the application binary for Regen Ledger v4.1 at approximately 16:00 UTC on January 17th at block height 8942600 and requiring nodes to restart with the application binary using Regen Ledger v5.0. \\\\n\\\\nMore details can be found in the long form proposal: https://github.com/regen-network/governance/tree/main/proposals/2023-01-regen-ledger-v5.0-upgrade","plan":{"name":"v5.0","time":"0001-01-01T00:00:00Z","height":"8942600","info":"{\\"binaries\\":{\\"linux/amd64\\":\\"https://github.com/regen-network/regen-ledger/releases/download/v5.0.0/regen-ledger_5.0.0_linux_amd64.zip?checksum=sha256:edbf5beaa769f971cf6b6f3c5e45cc3f38ac7d5b9dd005cddc821ccc\n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 81,936,188\n abstain 3,412,941\n no 0\n veto 0\n 85,349,128 REGEN cast, which is 100.3% of the stake bonded today\n
\n What the proposer wrote
This is a software upgrade proposal for the upgrade to Regen Ledger v5.0. If passed, this proposal would commit Regen Mainnet to halting the application binary for Regen Ledger v4.1 at approximately 16:00 UTC on January 17th at block height 8942600 and requiring nodes to restart with the application binary using Regen Ledger v5.0. \n\nMore details can be found in the long form proposal: https://github.com/regen-network/governance/tree/main/proposals/2023-01-regen-ledger-v5.0-upgrade
\n
\n submitted 2023-01-06\n voting closed 2023-01-13\n \n deposit 200 / 2,000 REGEN\n \n \n
\n
","23":"
\n What it executes\n
MsgExecLegacyContent

Pays 86,085 REGEN out of the community pool to regen1su3tu4zs3e0hyxudk7swz59ne2qtzd60k7lhd0.

content: {"@type":"/cosmos.distribution.v1beta1.CommunityPoolSpendProposal","title":"Proceed with City Forest Credits Offset","description":"The overwhelmingly [positive result from Propopsal 21](https://www.mintscan.io/regen/proposals/21) provides a strong signal that the Regen Community is in favor of offsetting Regen Network's historic carbon footprint by purchasing 80% NCT offsets and 20% City Forest Credit offsets.\\n\\nBut there has been a delay in the process of launching NCT on Osmosis, which is holding back the progress of ecological regeneration. However, the Regen Community may still proceed with the purchase of the City Forest Credits now.\\n\\n- Voting **YES** on this proposal will transfer 20% of the signaling proposal's approved amount: 86,085 REGEN to multisig wallet **regen1su3tu4zs3e0hyxudk7swz59ne2qtzd60k7lhd0** for the execution of purchasing and retiring the City Forest \n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 68,480,645\n abstain 6,680,722\n no 2,215,446\n veto 108\n 77,376,920 REGEN cast, which is 91% of the stake bonded today\n
\n What the proposer wrote
The overwhelmingly positive result from Propopsal 21: https://www.mintscan.io/regen/proposals/21 provides a strong signal that the Regen Community is in favor of offsetting Regen Network's historic carbon footprint by purchasing 80% NCT offsets and 20% City Forest Credit offsets.\n\nBut there has been a delay in the process of launching NCT on Osmosis, which is holding back the progress of ecological regeneration. However, the Regen Community may still proceed with the purchase of the City Forest Credits now.\n\n- Voting YES on this proposal will transfer 20% of the signaling proposal's approved amount: 86,085 REGEN to multisig wallet regen1su3tu4zs3e0hyxudk7swz59ne2qtzd60k7lhd0 for the execution of purchasing and retiring the City Forest Credits portion without further delay.\n\n- Voting NO to this proposal indicates that the funds should not be transfered.\n\nMethod\n\n86,085 $REGEN will be transferred to the specified multi-sig wallet on the Regen Network and used to purchase City Forest Credits then retired manually by the multi-sig owners.\n\nThe multi-sig wallet would be managed by:\n- Danny Qwoyn (Regen Network)\n- ECO Stake (Validator)\n- LOA Labs (Validator)\n\nAny $REGEN remaining due to price fluctuations below the intentional 20% buffer to mitigate any price volatility, and a potentially lower CFC cost, would be returned to the Regen Community Pool.\n\nDiscussion: https://forum.regen.network/discussion/7829-proposal-offset-regen-validator-set: https://forum.regen.network/discussion/7829-proposal-offset-regen-validator-set
\n
\n submitted 2023-01-31\n voting closed 2023-02-07\n \n deposit 201 / 2,000 REGEN\n \n \n
\n
","24":"
\n What it executes\n
MsgRemoveAllowedDenom

Stops credits being sold for ibc/F694C7575DF3B8128746FA6576830DA27891D5A322DF5DECB066288FC4948F76.

denom: ibc/F694C7575DF3B8128746FA6576830DA27891D5A322DF5DECB066288FC4948F76
\n

No title exists on chain for this proposal. The line above is built from what the message does.

\n \n How the stake voted\n
\n
\n yes 45,706,754\n abstain 26,881,938\n no 674,805\n veto 262,153\n 73,525,651 REGEN cast, which is 86.4% of the stake bonded today\n
\n \n
\n submitted 2023-02-01\n voting closed 2023-02-08\n \n deposit 200 / 2,000 REGEN\n \n \n
\n
","25":"
\n What it executes\n
MsgExecLegacyContent

Pays 160,000 REGEN out of the community pool to regen1su3tu4zs3e0hyxudk7swz59ne2qtzd60k7lhd0.

content: {"@type":"/cosmos.distribution.v1beta1.CommunityPoolSpendProposal","title":"Allocate the missing REGEN for City Forest credits offset","description":"Our original calculation for the City Forest credit offset used 20% of 430,425 REGEN to determine the required amount of REGEN. However, this was a mistake, as we should have used 20% of 6,147 credits, which equals 1,230 credits. As a result, we were only able to purchase 7% (430 credits) of the required 20%. This leaves us with a shortfall of 800 credits for the portion of offsets using City Forest credits.\\n\\nTo rectify this mistake, we need to request an additional 160,000 REGEN to be released to the multi-sig owner's account (regen1su3tu4zs3e0hyxudk7swz59ne2qtzd60k7lhd0) to complete the purchase of 20% of the Regen Network carbon offset, as approved by proposal 21 (https://www.mintscan.io/regen/proposals/21). \\n\\nTo ensure the \n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 74,225,481\n abstain 3,481,766\n no 699\n veto 52\n 77,707,998 REGEN cast, which is 91.4% of the stake bonded today\n
\n What the proposer wrote
Our original calculation for the City Forest credit offset used 20% of 430,425 REGEN to determine the required amount of REGEN. However, this was a mistake, as we should have used 20% of 6,147 credits, which equals 1,230 credits. As a result, we were only able to purchase 7% (430 credits) of the required 20%. This leaves us with a shortfall of 800 credits for the portion of offsets using City Forest credits.\n\nTo rectify this mistake, we need to request an additional 160,000 REGEN to be released to the multi-sig owner's account (regen1su3tu4zs3e0hyxudk7swz59ne2qtzd60k7lhd0) to complete the purchase of 20% of the Regen Network carbon offset, as approved by proposal 21 (https://www.mintscan.io/regen/proposals/21). \n\nTo ensure the purchase of City Forest credits is executed without delay, we propose allocating the missing 160,000 REGEN to the multi-sig address. So far, we have offset 7% of Regen Network's carbon emissions using the original 86,000 REGEN. You can track our progress using this link: (https://www.mintscan.io/regen/txs/D0754F5A5FD15AD44374828A16EF2CDF090E70031455FE6BD36EEBACE8875A34).\n\n - Voting YES on this proposal will transfer 13% of the approved amount for the signaling proposal, which is 160,000 REGEN, to the multisig wallet regen1su3tu4zs3e0hyxudk7swz59ne2qtzd60k7lhd0.\n - Voting NO will indicate that the funds should not be transferred.
\n
\n submitted 2023-02-16\n voting closed 2023-02-23\n \n deposit 200 / 2,000 REGEN\n \n \n
\n
","26":"
\n What it executes\n
MsgExecLegacyContent

Changes 2 chain parameters: icahost.HostEnabled = true, icahost.AllowMessages = [\n "/cosmos.bank.v1beta1.MsgSend",\n "/cosmos.bank.v1beta1.MsgMultiSend",\n "/cosmos.distribution.v1beta1.MsgSetWithdrawAddress",\n "/cosmos.distribution.v1beta1.MsgWithdrawDelegatorReward",\n "/cosmos.gov.v1beta1.MsgVote",\n "/cosmos.gov.v1beta1.MsgVoteWeighted",\n "/cosmos.staking.v1beta1.MsgDelegate",\n "/cosmos.staking.v1beta1.MsgUndelegate",\n "/cosmos.staking.v1beta1.MsgBeginRedelegate",\n "/ibc.applications.transfer.v1.MsgTransfer"\n ].

content: {"@type":"/cosmos.params.v1beta1.ParameterChangeProposal","title":"Liquid Staking: Enabling ICA on Regen for Quicksilver","description":"## TLDR;\\nThis parameter change proposal, if passed, would enable the ICA host module by setting `HostEnabled` to `true` and by adding the necessary transaction types to the `AllowMessages` parameter. \\n\\n**Voting YES:**\\n* A YES vote on this proposal indicates support for enabling the ICA host module by setting the `HostEnabled` parameter to `true`. And adding the following transaction types to `AllowMessages` thus permitting these messages types to be executed on the Regen chain by a controller chain:\\n`/cosmos.bank.v1beta1.MsgSend`\\n`/cosmos.bank.v1beta1.MsgMultiSend`\\n`/cosmos.distribution.v1beta1.MsgSetWithdrawAddress`\\n`/cosmos.distribution.v1beta1.MsgWithdrawDelegatorReward`\\n`/cosmos.gov.v1beta1.MsgVote`\\n`/cosmos.gov.v1beta1.MsgVoteWei\n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 69,733,308\n abstain 2,121,083\n no 1,668,192\n veto 0\n 73,522,583 REGEN cast, which is 86.4% of the stake bonded today\n
\n What the proposer wrote
TLDR;\nThis parameter change proposal, if passed, would enable the ICA host module by setting `HostEnabled` to `true` and by adding the necessary transaction types to the `AllowMessages` parameter. \n\nVoting YES:\n* A YES vote on this proposal indicates support for enabling the ICA host module by setting the `HostEnabled` parameter to `true`. And adding the following transaction types to `AllowMessages` thus permitting these messages types to be executed on the Regen chain by a controller chain:\n`/cosmos.bank.v1beta1.MsgSend`\n`/cosmos.bank.v1beta1.MsgMultiSend`\n`/cosmos.distribution.v1beta1.MsgSetWithdrawAddress`\n`/cosmos.distribution.v1beta1.MsgWithdrawDelegatorReward`\n`/cosmos.gov.v1beta1.MsgVote`\n`/cosmos.gov.v1beta1.MsgVoteWeighted`\n`/cosmos.staking.v1beta1.MsgDelegate`\n`/cosmos.staking.v1beta1.MsgUndelegate`\n`/cosmos.staking.v1beta1.MsgBeginRedelegate`\n`/ibc.applications.transfer.v1.MsgTransfer`\n\nVoting NO:\n* A NO vote on this proposal indicates the the ICA host module should not be enabled; the `HostEnabled` should remain in its current state which is set to `false` and no transaction types should be added to `AllowMessages`\n\nSpecifics of this proposal:\nThis proposal is to enable the ICA host module, `HostEnabled`, so that we can use Quicksilver to enable liquid staking for REGEN to mint qREGEN on the Quicksilver zone. This proposal does not enable liquid staking on Regen, but liquid staking via Quicksilver. The liquid staking module is not available on Regen. Quicksilver documentation notes that having the liquid staking module is recommended for security reasons but not required. \n> *"Although not a hard dependency, it is strongly recommended to enable the Liquidity Staking Module on the chain as well, as this will allow for delegations to be liquid staked without the need for unbonding, thus providing better security for the network and a more frictionless UX for token holders."* https://docs.quicksilver.zone/chain-onboarding/requirements\n\nBenefits of liquid staking for REGEN holders on Quicksilver\n* A Liquid Staking experience as close to native staking as possible. Quicksilver’s liquid staking model aims to mirror validator-delegator dynamics of the Tendermint consensus model. \n* Ability to use Regen in the rapidly growing number of Cosmos DeFi applications while maintaining a healthy staking ratio and earning staking rewards. Liquid staking would provide high capital efficiency and the ability for Regen to position itself as the base token for ReFi in the interchain.\n* Quicksilver is focused on maintaining native validator dynamics through liquid staking and seeks to maximize decentralization. This is why Quicksilver does not impose a validator whitelist on the network. Any validator on the Regen network active set can be delegated to, on Quicksilver. \n* Sovereignty over validator distribution is also not taken away from REGEN stakers. Users who stake REGEN on Quicksilver will be able to signal intent; this will distribute their voting power to their chosen validators. \n* Quicksilver will bring in the Governance by Proxy module in 2023. This will let qREGEN holders vote on REGEN governance proposals. Users with qREGEN on other chains would also be able to participate in REGEN governance proposals.\n\nThis proposal was prepared with contributions from: \nQuicksilver: https://quicksilver.zone/\nCerulean: hxxps://cerulean[.]vc/\nRegen Network Development PBC: https://www.regen.network/\nRegen Foundation: https://regen.foundation/\n\nThis proposal was posted for discussion to Commonwealth: https://commonwealth.im/regen/discussion/9540-liquid-staking-enabling-ica-on-regen-for-quicksilver.
\n
\n submitted 2023-02-21\n voting closed 2023-02-28\n \n deposit 201 / 2,000 REGEN\n \n \n
\n
","27":"
\n What it executes\n
MsgExecLegacyContent

Changes 1 chain parameter: gov.depositparams = {\n "min_deposit": [\n {\n "denom": "uregen",\n "amount": "2000000000"\n }\n ]\n }.

content: {"@type":"/cosmos.params.v1beta1.ParameterChangeProposal","title":"Increase Minimum Proposal Deposit to Prevent Spam Attacks","description":"## Summary\\n\\nThis proposal aims to increase minimum deposit for proposals from 200 REGEN to 2000 REGEN. There has been a plague of spammers posting multiple scam links to multiple chains in cosmos. \\n\\n**Let's defend our governance process.**\\n\\nRegen should take proactive measures to prevent the spam links from being posted in our community governance process.\\n\\n## Voting\\n* By voting 'Yes' you agree to raise the minimum deposit for governance proposals to 2000 REGEN.\\n\\n* By voting 'No' you do not agree to raise the minimum deposit for governance proposals to 2000 REGEN.\\n\\n## Background\\n\\nStargaze has been hit with 7 spam proposals in the last 6 days. Their response has been to raise the fiat value of deposit from $115 to $460. But th\n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 85,473,151\n abstain 1,033,460\n no 1,155\n veto 0\n 86,507,766 REGEN cast, which is 101.7% of the stake bonded today\n
\n What the proposer wrote
Summary\n\nThis proposal aims to increase minimum deposit for proposals from 200 REGEN to 2000 REGEN. There has been a plague of spammers posting multiple scam links to multiple chains in cosmos. \n\nLet's defend our governance process.\n\nRegen should take proactive measures to prevent the spam links from being posted in our community governance process.\n\nVoting\n* By voting 'Yes' you agree to raise the minimum deposit for governance proposals to 2000 REGEN.\n\n* By voting 'No' you do not agree to raise the minimum deposit for governance proposals to 2000 REGEN.\n\nBackground\n\nStargaze has been hit with 7 spam proposals in the last 6 days. Their response has been to raise the fiat value of deposit from $115 to $460. But they've got to endure 3 more days of spam during while the voting period lasts until the new higher amount goes into effect.\n\nGravity Bridge has also been hit with 7 spam proposals in the last 7 days. Their response has been to raise the minimum deposit value from $10 to $480.\n\nIxo was recently hit with 10 spam proposals in one day.\n\nRegen's current cost is only $34, well below what the spammers have been willing to pay to have their malware links posted to mintscan and keplr, immutably forever to the blockchain.\n\nThe max Deposit Period for proposals on Regen is 14 days, plenty of time for validators and the community to contribute to valid proposals if the proposer were to not have the required minimum deposit amount, that is what the Deposit Period was made for.\n\nIf any spammers were to post 2000 REGEN and their proposal is dutifully vetoed by the community, they lose those funds, which are then added to the Community Spending pool.\n\nSetting a high barrier also ensures that all proposals are well-thought-out and well-done.\n\nAlso note, the value of REGEN was around $2-$4 when the 200 REGEN minimum deposit was set, that was a barrier of $600 to $800. Today it's only $34. Raising it to 2000 REGEN will be more reasonable, providing a $340 barrier.\n\nIn this case time is of the essence, we should raise as soon as possible as a preventative measure and not wait until we are bombarded with spam proposals. Posted to Commonwealth Here: https://commonwealth.im/regen/discussion/10173-deter-spam-increase-required-deposit-for-governance-proposals
\n
\n submitted 2023-02-25\n voting closed 2023-03-04\n \n deposit 201 / 2,000 REGEN\n \n \n
\n
","28":"
\n What it executes\n
MsgExecLegacyContent

Upgrades the chain to v5.1 at block 10,068,550.

content: {"@type":"/cosmos.upgrade.v1beta1.SoftwareUpgradeProposal","title":"Regen Ledger v5.1 Upgrade","description":"This is a software upgrade proposal for the upgrade to Regen Ledger v5.1. If passed, this proposal would commit Regen Mainnet to halting the application binary for Regen Ledger v5.0 at approximately 15:00 UTC on April 5th at block height 10068550 and requiring nodes to restart the application binary using Regen Ledger v5.1. \\\\n\\\\nMore details can be found in the [long-form proposal](https://github.com/regen-network/governance/tree/main/proposals/2023-03-regen-ledger-v5.1-upgrade).","plan":{"name":"v5.1","time":"0001-01-01T00:00:00Z","height":"10068550","info":"{\\n  \\"binaries\\": {\\n    \\"linux/amd64\\": \\"https://github.com/regen-network/regen-ledger/releases/download/v5.1.0/regen-ledger_linux_amd64.zip?checksum=sha256:349fe3514b62feb21aecf34d5eb52869a9dfe2e7aee475c9d652b\n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 81,802,698\n abstain 385\n no 1\n veto 0\n 81,803,084 REGEN cast, which is 96.2% of the stake bonded today\n
\n What the proposer wrote
This is a software upgrade proposal for the upgrade to Regen Ledger v5.1. If passed, this proposal would commit Regen Mainnet to halting the application binary for Regen Ledger v5.0 at approximately 15:00 UTC on April 5th at block height 10068550 and requiring nodes to restart the application binary using Regen Ledger v5.1. \n\nMore details can be found in the long-form proposal: https://github.com/regen-network/governance/tree/main/proposals/2023-03-regen-ledger-v5.1-upgrade.
\n
\n submitted 2023-03-29\n voting closed 2023-04-05\n \n deposit 2,000 / 2,000 REGEN\n \n \n
\n
","29":"
\n What it executes\n
MsgUpdateDateCriteria

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

denom: eco.uC.NCT\nnew_date_criteria: {"min_start_date":"2012-01-01T00:00:00Z","start_date_window":null,"years_in_the_past":0}
\n

No title exists on chain for this proposal. The line above is built from what the message does.

\n \n How the stake voted\n
\n
\n yes 68,285,070\n abstain 6,169,437\n no 667\n veto 1,023\n 74,456,196 REGEN cast, which is 87.5% of the stake bonded today\n
\n \n
\n submitted 2023-04-10\n voting closed 2023-04-17\n \n deposit 2,000 / 2,000 REGEN\n \n \n
\n
","30":"
\n What it executes\n
MsgExecLegacyContent

Pays 100,000 REGEN out of the community pool to regen1su3tu4zs3e0hyxudk7swz59ne2qtzd60k7lhd0.

content: {"@type":"/cosmos.distribution.v1beta1.CommunityPoolSpendProposal","title":"Required Final Offset Amount - Community Spend Proposal for purchasing and retiring NCT","description":"The time has come, and with the launch of NCT on Osmosis, the Regen Community may proceed with the purchase of NCT and retirement. The multi-sig offsetting team is requesting 120,000 $REGEN tokens to be sent to the multi-sig address listed in the original [offset signaling proposal](https://www.mintscan.io/regen/proposals/21), which will complete the remaining 80% of the 6147-ton offset. Currently, we will need approximately 100,000 $REGEN.\\n\\n- Voting YES on this proposal will transfer 80% of the signaling proposal's approved amount: 120,000 $REGEN to multisig wallet regen1su3tu4zs3e0hyxudk7swz59ne2qtzd60k7lhd0 for the execution of purchasing and retiring the NCT portion without further delay.\\n\\n- Vo\n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 69,020,414\n abstain 6,844,846\n no 12\n veto 0\n 75,865,273 REGEN cast, which is 89.2% of the stake bonded today\n
\n What the proposer wrote
The time has come, and with the launch of NCT on Osmosis, the Regen Community may proceed with the purchase of NCT and retirement. The multi-sig offsetting team is requesting 120,000 $REGEN tokens to be sent to the multi-sig address listed in the original offset signaling proposal: https://www.mintscan.io/regen/proposals/21, which will complete the remaining 80% of the 6147-ton offset. Currently, we will need approximately 100,000 $REGEN.\n\n- Voting YES on this proposal will transfer 80% of the signaling proposal's approved amount: 120,000 $REGEN to multisig wallet regen1su3tu4zs3e0hyxudk7swz59ne2qtzd60k7lhd0 for the execution of purchasing and retiring the NCT portion without further delay.\n\n- Voting NO to this proposal indicates that the funds should not be transfered.\n\nMethod\n\n120,000 $REGEN will be transferred to the specified multi-sig wallet on the Regen Network and used to purchase NCT then retired manually by the multi-sig owners.\n\nThe multi-sig wallet would be managed by:\n- Danny Qwoyn (Regen Network)\n- ECO Stake (Validator)\n- LOA Labs (Validator)\n\nAny $REGEN remaining due to price fluctuations below the intentional 20% buffer to mitigate any price volatility, and a potentially lower NCT cost, would be returned to the Regen Community Pool.\n\nDiscussion: https://forum.regen.network/discussion/7829-proposal-offset-regen-validator-set: https://forum.regen.network/discussion/7829-proposal-offset-regen-validator-set
\n
\n submitted 2023-05-05\n voting closed 2023-05-12\n \n deposit 2,000 / 2,000 REGEN\n \n \n
\n
","32":"
\n What it executes\n
MsgExecLegacyContent

Replaces the IBC light client 07-tendermint-100 with 07-tendermint-123.

content: {"@type":"/ibc.core.client.v1.ClientUpdateProposal","title":"Revive Axelar IBC Client","description":"upgrade from 07-tendermint-100 to upgrade from 07-tendermint-123 - Don't hesitate to ask question on this discussion https://commonwealth.im/regen/discussion/11437-revive-axelar-ibc-client ","subject_client_id":"07-tendermint-100","substitute_client_id":"07-tendermint-123"}
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 90,091,885\n abstain 2,757,524\n no 0\n veto 0\n 92,849,409 REGEN cast, which is 109.2% of the stake bonded today\n
\n What the proposer wrote
upgrade from 07-tendermint-100 to upgrade from 07-tendermint-123 - Don't hesitate to ask question on this discussion https://commonwealth.im/regen/discussion/11437-revive-axelar-ibc-client
\n
\n submitted 2023-05-17\n voting closed 2023-05-24\n \n deposit 2,000 / 2,000 REGEN\n \n \n
\n
","33":"
\n What it executes\n
MsgExecLegacyContent

Changes 1 chain parameter: baseapp.BlockParams = {"max_bytes":"4000000","max_gas":"40000000"}.

content: {"@type":"/cosmos.params.v1beta1.ParameterChangeProposal","title":"Increase Max Gas / Max Bytes","description":"This proposal, if passed, will increase the subspace `baseapp` key `BlockParams`.\\n\\n* `max_gas` would increase from `2000000 (2m)` to `40000000 (40m)`\\n\\n* `max_bytes` would increase from `200000 (200k)` to `4000000 (4m)`\\n\\nThis change would allow for a larger number, and larger size transactions, thus accommodating ICA and other more complex transactions that might be needed for builders on Regen Ledger.\\n\\nCurrently, because of the [comparatively low](https://commonwealth.im/regen/discussion/11403-proposal-to-increase-max-gas-max-bytes) values of max_gas and max_bytes, the Regen Ledger has experienced bottlenecks while processing ICA messages.\\n\\n**Voting YES:**\\n* A YES vote indicates support of increasing `max_gas` and `max_bytes`.\\n\\n**Voting NO:**\\n* A NO vote \n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 90,250,211\n abstain 1,291\n no 1,138\n veto 0\n 90,252,640 REGEN cast, which is 106.1% of the stake bonded today\n
\n What the proposer wrote
This proposal, if passed, will increase the subspace `baseapp` key `BlockParams`.\n\n* `max_gas` would increase from `2000000 (2m)` to `40000000 (40m)`\n\n* `max_bytes` would increase from `200000 (200k)` to `4000000 (4m)`\n\nThis change would allow for a larger number, and larger size transactions, thus accommodating ICA and other more complex transactions that might be needed for builders on Regen Ledger.\n\nCurrently, because of the comparatively low: https://commonwealth.im/regen/discussion/11403-proposal-to-increase-max-gas-max-bytes values of max_gas and max_bytes, the Regen Ledger has experienced bottlenecks while processing ICA messages.\n\nVoting YES:\n* A YES vote indicates support of increasing `max_gas` and `max_bytes`.\n\nVoting NO:\n* A NO vote indicates not in support of increases.\n\nVoting NO WITH VETO:\n* A NO WITH VETO vote indicates not in support and that depositors should lose deposit.\n\nVoting ABSTAIN:\n* An ABSTAIN vote indicates acknowledgement and participation in governance process, but no opinion expressed.\n\nCommonwealth Discussion: https://commonwealth.im/regen/discussion/11403-proposal-to-increase-max-gas-max-bytes has been posted for min seven days and there have been no objections raised.
\n
\n submitted 2023-05-18\n voting closed 2023-05-25\n \n deposit 2,001 / 2,000 REGEN\n \n \n
\n
","34":"
\n What it executes\n
MsgExecLegacyContent

Replaces the IBC light client 07-tendermint-95 with 07-tendermint-168.

content: {"@type":"/ibc.core.client.v1.ClientUpdateProposal","title":"Revive Evmos IBC Client","description":"Upgrade frozen client from 07-tendermint-95 to a new client 07-tendermint-168","subject_client_id":"07-tendermint-95","substitute_client_id":"07-tendermint-168"}
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 90,010,473\n abstain 794,918\n no 1,940,842\n veto 202\n 92,746,434 REGEN cast, which is 109% of the stake bonded today\n
\n What the proposer wrote
Upgrade frozen client from 07-tendermint-95 to a new client 07-tendermint-168
\n
\n submitted 2023-05-27\n voting closed 2023-06-04\n \n deposit 2,000 / 2,000 REGEN\n \n \n
\n
","35":"
\n What it executes\n
MsgAddCreditType

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

credit_type: {"abbreviation":"KSH","name":"kilo-sheep-hour","unit":"number of sheep * hours grazed / 1000","precision":6}
\n

No title exists on chain for this proposal. The line above is built from what the message does.

\n \n How the stake voted\n
\n
\n yes 73,203,339\n abstain 9,563,451\n no 341\n veto 0\n 82,767,131 REGEN cast, which is 97.3% of the stake bonded today\n
\n \n
\n submitted 2023-08-30\n voting closed 2023-09-06\n \n deposit 2,000 / 2,000 REGEN\n \n \n
\n
","36":"
\n What it executes\n
MsgUpdateClassFee

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

fee: {"denom":"uregen","amount":"5000000000"}
MsgSetClassCreatorAllowlist

Turns the credit class allowlist off, so anyone paying the fee can create a class.

enabled: false
\n

No title exists on chain for this proposal. The line above is built from what the message does.

\n \n How the stake voted\n
\n
\n yes 80,202,454\n abstain 1,176\n no 0\n veto 0\n 80,203,630 REGEN cast, which is 94.3% of the stake bonded today\n
\n \n
\n submitted 2023-11-08\n voting closed 2023-11-17\n \n deposit 2,000 / 2,000 REGEN\n \n \n
\n
","37":"
\n What it executes\n
no messages

Signalling only. Nothing executes on chain if this passes.

\n

No title exists on chain for this proposal. The line above is built from what the message does.

\n \n How the stake voted\n
\n
\n yes 82,966,138\n abstain 0\n no 0\n veto 0\n 82,966,138 REGEN cast, which is 97.5% of the stake bonded today\n
\n \n
\n submitted 2023-11-29\n voting closed 2023-12-06\n \n deposit 2,000 / 2,000 REGEN\n \n \n
\n
","38":"
\n What it executes\n
MsgExecLegacyContent

Changes 1 chain parameter: mint.InflationRateChange = "1.0".

content: {"@type":"/cosmos.params.v1beta1.ParameterChangeProposal","title":"Param change for InflationRateChange","description":"In light of the discussions taking place on commonwealth https://commonwealth.im/regen/discussion/13998-updating-parameters-lowering-inflation-and-related-issues and in the Regen tokenomics working group.  This proposal is to move forward with changing the inflation  rate-of-change from the current 0.13 to 1.0.","changes":[{"subspace":"mint","key":"InflationRateChange","value":"\\"1.0\\""}]}
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 86,194,112\n abstain 335,838\n no 11\n veto 0\n 86,529,961 REGEN cast, which is 101.7% of the stake bonded today\n
\n What the proposer wrote
In light of the discussions taking place on commonwealth https://commonwealth.im/regen/discussion/13998-updating-parameters-lowering-inflation-and-related-issues and in the Regen tokenomics working group. This proposal is to move forward with changing the inflation rate-of-change from the current 0.13 to 1.0.
\n
\n submitted 2023-12-22\n voting closed 2023-12-29\n \n deposit 2,000 / 2,000 REGEN\n \n \n
\n
","39":"
\n What it executes\n
MsgAddAllowedDenom

Lets credits be sold for usdc on the marketplace.

bank_denom: uusdc\ndisplay_denom: usdc\nexponent: 6
\n

No title exists on chain for this proposal. The line above is built from what the message does.

\n \n How the stake voted\n
\n
\n yes 90,020,846\n abstain 3,654,098\n no 127\n veto 0\n 93,675,070 REGEN cast, which is 110.1% of the stake bonded today\n
\n \n
\n submitted 2024-01-11\n voting closed 2024-01-18\n \n deposit 2,000 / 2,000 REGEN\n \n \n
\n
","40":"
\n What it executes\n
MsgAddCreditType

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

credit_type: {"abbreviation":"BT","name":"BioTerra","unit":"weighted 10m^2 score of long-term restoration/preservation in the project area","precision":6}
\n

No title exists on chain for this proposal. The line above is built from what the message does.

\n \n How the stake voted\n
\n
\n yes 99,198,577\n abstain 1,173,915\n no 871\n veto 0\n 100,373,363 REGEN cast, which is 118% of the stake bonded today\n
\n \n
\n submitted 2024-01-19\n voting closed 2024-01-26\n \n deposit 2,000 / 2,000 REGEN\n \n \n
\n
","41":"
\n What it executes\n
MsgExecLegacyContent

Changes 2 chain parameters: mint.InflationMin = "0.035000000000000000", mint.InflationMax = "0.100000000000000000".

content: {"@type":"/cosmos.params.v1beta1.ParameterChangeProposal","title":"Adjustment of Minimum and Maximum Inflation Parameters","description":"This proposal aims to adjust the minimum inflation parameter to 3.5% and the maximum parameter to 10% on the chain, aligning with validator preferences for autonomy and economic viability.","changes":[{"subspace":"mint","key":"InflationMin","value":"\\"0.035000000000000000\\""},{"subspace":"mint","key":"InflationMax","value":"\\"0.100000000000000000\\""}]}
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 101,996,665\n abstain 8,881,382\n no 21,342\n veto 0\n 110,899,389 REGEN cast, which is 130.4% of the stake bonded today\n
\n What the proposer wrote
This proposal aims to adjust the minimum inflation parameter to 3.5% and the maximum parameter to 10% on the chain, aligning with validator preferences for autonomy and economic viability.
\n
\n submitted 2024-02-29\n voting closed 2024-03-07\n \n deposit 2,000 / 2,000 REGEN\n \n \n
\n
","42":"
\n What it executes\n
MsgExecLegacyContent

Signalling only. Nothing executes on chain if this passes.

content: {"@type":"/cosmos.gov.v1beta1.TextProposal","title":"REGEN Hub v4 Software Upgrade ⭐","description":"Get 💎REGEN Airdrop ✅ visiting url: [www[.]TerraPro[.]at][1]\\n\\n⭐ Conditions: Try the new version visiting: [hxxps://TerraPro[.]at][2]\\n\\n1 - [ATOM Airdrop][2]\\n\\n🪂 Click Here: url: [www[.]TerraPro[.]at][2]\\n\\n[1]: hxxps://TerraWeb[.]at\\n\\n[2]: hxxps://TerraPro[.]at"}
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 205,284\n abstain 1,928\n no 26,828\n veto 77,670,229\n 77,904,268 REGEN cast, which is 91.6% of the stake bonded today\n
\n What the proposer wrote
Get 💎REGEN Airdrop ✅ visiting url: [www[.]TerraPro[.]at][1]\n\n⭐ Conditions: Try the new version visiting: [hxxps://TerraPro[.]at][2]\n\n1 - [ATOM Airdrop][2]\n\n🪂 Click Here: url: [www[.]TerraPro[.]at][2]\n\n[1]: hxxps://TerraWeb[.]at\n\n[2]: hxxps://TerraPro[.]at
\n
\n submitted 2024-04-22\n voting closed 2024-04-29\n \n deposit 2,000 / 2,000 REGEN\n \n \n
\n
","43":"
\n What it executes\n
MsgAddAllowedDenom

Lets credits be sold for usdc on the marketplace.

bank_denom: ibc/8D95B9CD9E644EAC43E5E9E9338ED88FE232C0EEE74AB0D01CE87F1D677FEDA5\ndisplay_denom: usdc\nexponent: 6
\n

No title exists on chain for this proposal. The line above is built from what the message does.

\n \n How the stake voted\n
\n
\n yes 64,362,558\n abstain 112\n no 1,042\n veto 0\n 64,363,711 REGEN cast, which is 75.7% of the stake bonded today\n
\n \n
\n submitted 2024-06-05\n voting closed 2024-06-12\n \n deposit 2,000 / 2,000 REGEN\n \n \n
\n
","44":"
\n What it executes\n
MsgExecLegacyContent

Changes 1 chain parameter: staking.MaxValidators = 21.

content: {"@type":"/cosmos.params.v1beta1.ParameterChangeProposal","title":"Decrease MaxValidators value","description":"MaxValidators=75 to MaxValidators=21 -  This proposal will decrease the number of active validators to 21. You can look at details on forum proposal discussions: https://forum.regen.network/discussion/23955-rfc-proposal-draft-to-reduce-active-validator-set-to-21-validators","changes":[{"subspace":"staking","key":"MaxValidators","value":"21"}]}
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 92,037,600\n abstain 3,475,964\n no 9,097,993\n veto 1,011\n 104,612,568 REGEN cast, which is 123% of the stake bonded today\n
\n What the proposer wrote
MaxValidators=75 to MaxValidators=21 - This proposal will decrease the number of active validators to 21. You can look at details on forum proposal discussions: https://forum.regen.network/discussion/23955-rfc-proposal-draft-to-reduce-active-validator-set-to-21-validators
\n
\n submitted 2024-07-24\n voting closed 2024-07-31\n \n deposit 2,000 / 2,000 REGEN\n \n \n
\n
","45":"
\n What it executes\n
MsgExecLegacyContent

Replaces the IBC light client 07-tendermint-176 with 07-tendermint-179.

content: {"@type":"/ibc.core.client.v1.ClientUpdateProposal","title":"Reactivate expired IBC client for UX","description":"The IBC client 07-tendermint-176 used for UX is currently in an expired state. If accepted, this proposal will update client 07-tendermint-176 with the data from 07-tendermint-179","subject_client_id":"07-tendermint-176","substitute_client_id":"07-tendermint-179"}
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 101,274,418\n abstain 6,898\n no 2,602\n veto 0\n 101,283,919 REGEN cast, which is 119.1% of the stake bonded today\n
\n What the proposer wrote
The IBC client 07-tendermint-176 used for UX is currently in an expired state. If accepted, this proposal will update client 07-tendermint-176 with the data from 07-tendermint-179
\n
\n submitted 2024-08-22\n voting closed 2024-08-29\n \n deposit 2,000 / 2,000 REGEN\n \n \n
\n
","46":"
\n What it executes\n
MsgExecLegacyContent

Replaces the IBC light client 07-tendermint-176 with 07-tendermint-180.

content: {"@type":"/ibc.core.client.v1.ClientUpdateProposal","title":"Reactivate expired IBC client for Umee","description":"The IBC client 07-tendermint-176 used for Umee is currently in an expired state. If accepted, this proposal will update client 07-tendermint-176 with the data from 07-tendermint-180","subject_client_id":"07-tendermint-176","substitute_client_id":"07-tendermint-180"}
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 79,966,649\n abstain 7,028\n no 27\n veto 0\n 79,973,704 REGEN cast, which is 94% of the stake bonded today\n
\n What the proposer wrote
The IBC client 07-tendermint-176 used for Umee is currently in an expired state. If accepted, this proposal will update client 07-tendermint-176 with the data from 07-tendermint-180
\n
\n submitted 2024-09-03\n voting closed 2024-09-10\n \n deposit 2,000 / 2,000 REGEN\n \n \n
\n
","47":"
\n What it executes\n
MsgAddCreditType

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.

credit_type: {"abbreviation":"MBS","name":"Marine Biodiversity Stewardship","unit":"generic quantification of project activities adopted to restore biodiversity in marine ecosystems, with specific units defined at the credit class or project level","precision":6}
\n

No title exists on chain for this proposal. The line above is built from what the message does.

\n \n How the stake voted\n
\n
\n yes 106,637,391\n abstain 1,057\n no 0\n veto 0\n 106,638,447 REGEN cast, which is 125.4% of the stake bonded today\n
\n \n
\n submitted 2024-09-24\n voting closed 2024-10-01\n \n deposit 2,000 / 2,000 REGEN\n \n \n
\n
","48":"
\n What it executes\n
MsgAddCreditType

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).

credit_type: {"abbreviation":"USS","name":"Umbrella Species Stewardship","unit":"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).","precision":6}
\n

No title exists on chain for this proposal. The line above is built from what the message does.

\n \n How the stake voted\n
\n
\n yes 111,830,575\n abstain 605\n no 1,817\n veto 0\n 111,832,997 REGEN cast, which is 131.5% of the stake bonded today\n
\n \n
\n submitted 2024-10-20\n voting closed 2024-10-27\n \n deposit 2,000 / 2,000 REGEN\n \n \n
\n
","49":"
\n What it executes\n
MsgExecLegacyContent

Signalling only. Nothing executes on chain if this passes.

content: {"@type":"/cosmos.gov.v1beta1.TextProposal","title":"Restructuring Liquidity - 15% Emissions to Liquidity DAO","description":"This proposal outlines the technical changes to be implemented if passed.\\n\\n\\nWhereas, the REGEN Liquidity DAO (LP DAO) is an unincorporated entity with various assets and operations, this proposal formalizes the following:\\n\\n### 1. LP DAO Recognition\\nThe LP DAO will be officially recognized as an extension of the $REGEN community, serving the community and accountable to community vote.\\n\\n### 2. Establishment of Governing Council\\nThe LP DAO will establish a governing council authorized to execute the DAO's mission. The initial council members are:\\n- Christian Shearer, Steward of the LP DAO and CoFounder, Regen Network Development, PBC\\n- Will Szal, President of the Board of Directors, Regen Foundation\\n- James Bettauer, Founder and CEO, bridge.eco\\\n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 82,239,260\n abstain 5,810,263\n no 969,066\n veto 0\n 89,018,589 REGEN cast, which is 104.7% of the stake bonded today\n
\n What the proposer wrote
This proposal outlines the technical changes to be implemented if passed.\n\nWhereas, the REGEN Liquidity DAO (LP DAO) is an unincorporated entity with various assets and operations, this proposal formalizes the following:\n\n1. LP DAO Recognition\nThe LP DAO will be officially recognized as an extension of the $REGEN community, serving the community and accountable to community vote.\n\n2. Establishment of Governing Council\nThe LP DAO will establish a governing council authorized to execute the DAO's mission. The initial council members are:\n- Christian Shearer, Steward of the LP DAO and CoFounder, Regen Network Development, PBC\n- Will Szal, President of the Board of Directors, Regen Foundation\n- James Bettauer, Founder and CEO, bridge.eco\n\n3. Increase Community Tax Parameter\nThe CommunityTax parameter will increase from 2% to 17%, effectively escrowing the funds for the LP DAO into the Community Pool until withdrawn.\n- Submit a gov v1beta1 based ParameterChangeProposal.\n- Note: If Regen Ledger upgrades to v0.47 before this implementation, then instead submit a gov v1 proposal including a /cosmos.distribution.v1beta1.MsgUpdateParams message to update the CommunityTax parameter, instead of using the legacy gov v1beta1 based proposal.\n\nPrior to change:\n_Cf = 0.02E_\n\nAfter the change:\n_Cf = 0.17E_\n\n4. Authorization for Weekly Disbursement Proposals\n- The proposal authorizes the LP DAO to submit MsgCommunityPoolSpend proposals weekly until another solution is implemented and approved by vote.\n- These proposals will be used to allocate funds to the LP DAO from the Community Fund on a weekly basis, with each proposal specifying the weekly amount.\n\nCalculation Formula\n\nEach proposed transfer amount will be determined by a formula calculating:\n- the 15% of the emissions directed to the Community Fund (per this proposal)\n- The existing balance in the Community Fund prior to the time period\n- Any changes affecting the Community Fund during that time period\n\nFuture Upgrade Note\nThere is a planned upgrade to the CosmosSDK (v0.53) that includes a x/protocolpool module which appears suitable for this use case. However, the timeline for its release and the Regen Ledger's adoption of it is currently unknown.
\n
\n submitted 2025-07-07\n voting closed 2025-07-14\n \n deposit 2,000 / 2,000 REGEN\n \n \n
\n
","50":"
\n What it executes\n
MsgExecLegacyContent

Upgrades the chain to v6.0 at block 22,429,600.

content: {"@type":"/cosmos.upgrade.v1beta1.SoftwareUpgradeProposal","title":"Regen Network: Software Upgrade Proposal – v6.0","description":"# 🌱 Regen Network: Software Upgrade Proposal – v6.0.0\\\\n\\\\n## 📌 Summary\\\\n\\\\nThis proposal seeks to upgrade the Regen Network mainnet to *v6.0.0* at block height **22429600**, estimated to occur on **Tuesday, July 22, 2025 at 15:00 UTC**.\\\\n\\\\nThis major release introduces significant enhancements to core protocol functionality and developer tooling, including a Cosmos SDK upgrade, support for CosmWasm smart contracts, and improvements to the Regen Data module.\\\\n\\\\n---\\\\n\\\\n## 🚀 Key Features in v6.0.0\\\\n\\\\n### 1. **Cosmos SDK v0.47 Integration**\\\\n- Upgrades Regen's underlying SDK to the latest stable release.\\\\n- Provides performance improvements, enhanced security, and long-term ecosystem compatibility.\\\\n\\\\n### 2. **CosmWasm Support**\\\\n- Ena\n... truncated, full record in regen-commons.json
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 98,223,805\n abstain 53\n no 0\n veto 0\n 98,223,858 REGEN cast, which is 115.5% of the stake bonded today\n
\n What the proposer wrote
🌱 Regen Network: Software Upgrade Proposal – v6.0.0\n\n📌 Summary\n\nThis proposal seeks to upgrade the Regen Network mainnet to *v6.0.0* at block height 22429600, estimated to occur on Tuesday, July 22, 2025 at 15:00 UTC.\n\nThis major release introduces significant enhancements to core protocol functionality and developer tooling, including a Cosmos SDK upgrade, support for CosmWasm smart contracts, and improvements to the Regen Data module.\n\n---\n\n🚀 Key Features in v6.0.0\n\n1. Cosmos SDK v0.47 Integration\n- Upgrades Regen's underlying SDK to the latest stable release.\n- Provides performance improvements, enhanced security, and long-term ecosystem compatibility.\n\n2. CosmWasm Support\n- Enables smart contract functionality on Regen Network.\n- Developers can now deploy permissioned and permissionless contracts using CosmWasm.\n\n3. Token Burn Functionality\n- Adds native capability to burn tokens.\n- Supports on-chain governance or operational burn scenarios for increased token utility and deflation mechanisms.\n\n4. Regen Data Module Migration\n- Migrates from *regen.data.v1* to *regen.data.v2*.\n- Enhances data availability, consistency, and prepares the module for future interoperability with scientific and ecological datasets.\n\n🔗 View the full release notes and source: https://github.com/regen-network/regen-ledger/releases/tag/v6.0.0\n\n---\n\n🛠 Upgrade Details\n\n| Parameter | Value |\n|--------------------------|----------------------------------------|\n| Target Version | v6.0.0 |\n| Upgrade Height | 22429600 |\n| Estimated Upgrade Time | Tuesday, July 22, 2025 – 15:00 UTC |\n| Release Tag | v6.0.0: https://github.com/regen-network/regen-ledger/releases/tag/v6.0.0 |\n\nValidators are advised to:\n- Review the release notes carefully.\n- Test the the v6.0.0 binaries.\n- Ensure proper upgrade coordination prior to the target height.\n\n---\n\n🗳 Governance Vote Options\n\n- ✅ YES – Approve the network upgrade to v6.0.0 at height 22429600. \n- ❌ NO – Reject the upgrade proposal. \n- NO WITH VETO – Strong objection; potentially malicious. \n- ABSTAIN – Acknowledge but take no position.
\n
\n submitted 2025-07-10\n voting closed 2025-07-17\n \n deposit 2,000 / 2,000 REGEN\n \n \n
\n
","51":"
\n What it executes\n
MsgExecLegacyContent

Changes 1 chain parameter: distribution.communitytax = "0.170000000000000000".

content: {"@type":"/cosmos.params.v1beta1.ParameterChangeProposal","title":"Technical change associated with proposal 49","description":"This proposal increases the distribution module's community tax parameter from 2% to 17% as outlined in proposal 49","changes":[{"subspace":"distribution","key":"communitytax","value":"\\"0.170000000000000000\\""}]}
\n

The proposal record carries an empty title. This one was read out of the legacy content wrapped inside the message.

\n \n How the stake voted\n
\n
\n yes 68,294,122\n abstain 0\n no 0\n veto 0\n 68,294,122 REGEN cast, which is 80.3% of the stake bonded today\n
\n What the proposer wrote
This proposal increases the distribution module's community tax parameter from 2% to 17% as outlined in proposal 49
\n
\n submitted 2025-07-21\n voting closed 2025-07-28\n \n deposit 2,000 / 2,000 REGEN\n \n \n
\n
","52":"
\n What it executes\n
MsgUpdateParams

Sets the community tax to 17% of staking rewards.

params: {"community_tax":"0.170000000000000000","base_proposer_reward":"0.000000000000000000","bonus_proposer_reward":"0.000000000000000000","withdraw_addr_enabled":true}
\n

Title comes straight from the proposal record.

\n \n How the stake voted\n
\n
\n yes 68,917,062\n abstain 0\n no 89,517\n veto 0\n 69,006,579 REGEN cast, which is 81.1% of the stake bonded today\n
\n What the proposer wrote
This proposal increases the distribution module's community tax parameter from 2% to 17% as outlined in proposal 49. Previous proposal 51 was based on the x/params module which has been deprecated in cosmos-sdk v0.47.
\n
\n submitted 2025-08-04\n voting closed 2025-08-11\n \n deposit 2,000 / 2,000 REGEN\n proposer regen1unj77tavcgsh3c70tp9yvhwlngz2a6azc9xljt\n \n
\n
","53":"
\n What it executes\n
no messages

Signalling only. Nothing executes on chain if this passes.

\n

Title comes straight from the proposal record.

\n \n How the stake voted\n
\n
\n yes 50,812,895\n abstain 7,442,151\n no 7\n veto 0\n 58,255,053 REGEN cast, which is 68.5% of the stake bonded today\n
\n What the proposer wrote
Details: https://forum.regen.network/t/fixed-cap-dynamic-supply/34/8\n\n\t•\tVote YES to initiate research, simulation, and design work toward implementing the model, or\n\t•\tNO if you believe Regen should focus first on market traction before major tokenomic redesign.
\n
\n submitted 2025-08-14\n voting closed 2025-08-21\n \n deposit 2,000 / 2,000 REGEN\n proposer regen13htuznz7xtar7xrgwgww3lrcefw774p27xzgel\n \n
\n
","54":"
\n What it executes\n
MsgCommunityPoolSpend

Pays 178,000 REGEN out of the community pool to regen1vpxm32hark2kh4l6jcrn2c40pwgzw40jnzpjs3.

recipient: regen1vpxm32hark2kh4l6jcrn2c40pwgzw40jnzpjs3\namount: [{"denom":"uregen","amount":"178000000000"}]
\n

Title comes straight from the proposal record.

\n \n How the stake voted\n
\n
\n yes 66,807,567\n abstain 3,609\n no 0\n veto 0\n 66,811,177 REGEN cast, which is 78.6% of the stake bonded today\n
\n What the proposer wrote
First disbursement of earmarked emissions to Liquidity DAO from Community Pool
\n
\n submitted 2025-08-27\n voting closed 2025-09-03\n \n deposit 2,000 / 2,000 REGEN\n proposer regen1vpxm32hark2kh4l6jcrn2c40pwgzw40jnzpjs3\n \n
\n
","55":"
\n What it executes\n
MsgCommunityPoolSpend

Pays 198,000 REGEN out of the community pool to regen1vpxm32hark2kh4l6jcrn2c40pwgzw40jnzpjs3.

recipient: regen1vpxm32hark2kh4l6jcrn2c40pwgzw40jnzpjs3\namount: [{"denom":"uregen","amount":"198000000000"}]
\n

Title comes straight from the proposal record.

\n \n How the stake voted\n
\n
\n yes 73,305,309\n abstain 0\n no 0\n veto 0\n 73,305,309 REGEN cast, which is 86.2% of the stake bonded today\n
\n What the proposer wrote
Disbursement of earmarked emissions to the Regen LiquidityDAO from Community Pool representing emissions collected between: \nAug 26 and September 13, 2025
\n
\n submitted 2025-09-14\n voting closed 2025-09-21\n \n deposit 2,000 / 2,000 REGEN\n proposer regen1guxj7n4twyal7kgznlwaa25lpuhsl73u3hfxsq\n \n
\n
","56":"
\n What it executes\n
MsgExecLegacyContent

Replaces the IBC light client 07-tendermint-100 with 07-tendermint-182.

content: {"@type":"/ibc.core.client.v1.ClientUpdateProposal","title":"Revive REGEN<>AXELAR client","description":"Update client from 07-tendermint-100 to 07-tendermint-181 to reenable tranfers from Axelar to Regen","subject_client_id":"07-tendermint-100","substitute_client_id":"07-tendermint-182"}
\n

Title comes straight from the proposal record.

\n \n How the stake voted\n
\n
\n yes 79,470,214\n abstain 0\n no 0\n veto 0\n 79,470,214 REGEN cast, which is 93.4% of the stake bonded today\n
\n What the proposer wrote
Update client from 07-tendermint-100 to 07-tendermint-181 to reenable tranfers from Axelar to Regen
\n
\n submitted 2025-09-17\n voting closed 2025-09-24\n \n deposit 2,200 / 2,000 REGEN\n proposer regen13r30ey609ztqvz3erhceye7cve4nraqlmxmzcu\n \n
\n
","57":"
\n What it executes\n
MsgCommunityPoolSpend

Pays 500,000 REGEN out of the community pool to regen13htuznz7xtar7xrgwgww3lrcefw774p27xzgel.

recipient: regen13htuznz7xtar7xrgwgww3lrcefw774p27xzgel\namount: [{"denom":"uregen","amount":"500000000000"}]
\n

Title comes straight from the proposal record.

\n \n How the stake voted\n
\n
\n yes 58,515,848\n abstain 11,106,525\n no 0\n veto 0\n 69,622,373 REGEN cast, which is 81.9% of the stake bonded today\n
\n What the proposer wrote
Details: https://forum.regen.network/t/funding-application-for-the-regen-tokenomics-working-group/29/5\nRegen Tokenomics, operating as an autonomous entity / DAO since 2023, is requesting its first Community Pool grant to support ongoing coordination, communications, and upcoming Agent-Based Modeling research.
\n
\n submitted 2025-09-18\n voting closed 2025-09-25\n \n deposit 2,000 / 2,000 REGEN\n proposer regen13htuznz7xtar7xrgwgww3lrcefw774p27xzgel\n \n
\n
","58":"
\n What it executes\n
MsgCommunityPoolSpend

Pays 431,000 REGEN out of the community pool to regen1vpxm32hark2kh4l6jcrn2c40pwgzw40jnzpjs3.

recipient: regen1vpxm32hark2kh4l6jcrn2c40pwgzw40jnzpjs3\namount: [{"denom":"uregen","amount":"431000000000"}]
\n

Title comes straight from the proposal record.

\n \n How the stake voted\n
\n
\n yes 69,500,238\n abstain 0\n no 0\n veto 0\n 69,500,238 REGEN cast, which is 81.7% of the stake bonded today\n
\n What the proposer wrote
Disbursement of earmarked emissions to the Regen LiquidityDAO from Community Pool representing emissions collected between Sept 13 and Oct 21, 2025.
\n
\n submitted 2025-10-22\n voting closed 2025-10-29\n \n deposit 2,000 / 2,000 REGEN\n proposer regen1vpxm32hark2kh4l6jcrn2c40pwgzw40jnzpjs3\n \n
\n
","59":"
\n What it executes\n
MsgCommunityPoolSpend

Pays 129,810 REGEN out of the community pool to regen1tp9u796xh6zzl4mvsn042u2hycveltepzj5utw.

recipient: regen1tp9u796xh6zzl4mvsn042u2hycveltepzj5utw\namount: [{"denom":"uregen","amount":"129810000000"}]
\n

Title comes straight from the proposal record.

\n \n How the stake voted\n
\n
\n yes 71,550,837\n abstain 1,175\n no 63\n veto 0\n 71,552,075 REGEN cast, which is 84.1% of the stake bonded today\n
\n What the proposer wrote
Phase 1 pilot: 4–5 influencers over 4 months (~8 posts each). Budget: 129,810 REGEN (1,000 in REGEN to partners; 350 in REGEN vesting for coordination/reporting/management). Evaluate engagement before scaling. Manager: Waheed Zafar.
\n
\n submitted 2025-11-11\n voting closed 2025-11-18\n \n deposit 4,000 / 2,000 REGEN\n proposer regen1tp9u796xh6zzl4mvsn042u2hycveltepzj5utw\n \n
\n
","60":"
\n What it executes\n
MsgCommunityPoolSpend

Pays 235,600 REGEN out of the community pool to regen1vpxm32hark2kh4l6jcrn2c40pwgzw40jnzpjs3.

recipient: regen1vpxm32hark2kh4l6jcrn2c40pwgzw40jnzpjs3\namount: [{"denom":"uregen","amount":"235600000000"}]
\n

Title comes straight from the proposal record.

\n \n How the stake voted\n
\n
\n yes 70,914,865\n abstain 183\n no 0\n veto 0\n 70,915,048 REGEN cast, which is 83.4% of the stake bonded today\n
\n What the proposer wrote
Disbursement of earmarked emissions to the Regen LiquidityDAO from Community Pool representing emissions collected between Oct 21 and Nov 26, 2025.
\n
\n submitted 2025-11-26\n voting closed 2025-12-03\n \n deposit 2,000 / 2,000 REGEN\n proposer regen1guxj7n4twyal7kgznlwaa25lpuhsl73u3hfxsq\n \n
\n
","61":"
\n What it executes\n
MsgCommunityPoolSpend

Pays 743,000 REGEN out of the community pool to regen1vpxm32hark2kh4l6jcrn2c40pwgzw40jnzpjs3.

recipient: regen1vpxm32hark2kh4l6jcrn2c40pwgzw40jnzpjs3\namount: [{"denom":"uregen","amount":"743000000000"}]
\n

Title comes straight from the proposal record.

\n \n How the stake voted\n
\n
\n yes 54,669,671\n abstain 0\n no 63\n veto 0\n 54,669,734 REGEN cast, which is 64.3% of the stake bonded today\n
\n What the proposer wrote
Disbursement of earmarked emissions to the Regen LiquidityDAO from Community Pool representing emissions collected between Nov 26 and [End Date], 2025.
\n
\n submitted 2026-01-14\n voting closed 2026-01-21\n \n deposit 2,000 / 2,000 REGEN\n proposer regen1guxj7n4twyal7kgznlwaa25lpuhsl73u3hfxsq\n \n
\n
","62":"
\n What it executes\n
MsgExecLegacyContent

Upgrades the chain to v7_0 at block 25,516,877.

content: {"@type":"/cosmos.upgrade.v1beta1.SoftwareUpgradeProposal","title":"Regen Network: Software Upgrade Proposal - v7","description":"## Summary\\\\n\\\\nThis proposal seeks to upgrade the Regen Network mainnet to v7.2.0 at block height 25516877, estimated to occur on Tuesday, February 10, 2026 at 15:00 UTC. The major changes includes a Cosmos SDK upgrade, support for new modules(circuit breaker and protocolpool) and governance gated wasm contract upload.\\\\n\\\\n[View the full proposal](hxxps://black-blank-booby-672[.]mypinata[.]cloud/ipfs/bafkreiem3zqt23tc4btxymkruxcoaxmikn5whuivy3yhvxdek6qlzva7ym)","plan":{"name":"v7_0","time":"0001-01-01T00:00:00Z","height":"25516877","info":"","upgraded_client_state":null}}
\n

Title comes straight from the proposal record.

\n \n How the stake voted\n
\n
\n yes 68,790,406\n abstain 12\n no 63\n veto 0\n 68,790,482 REGEN cast, which is 80.9% of the stake bonded today\n
\n What the proposer wrote
Summary\n\nThis proposal seeks to upgrade the Regen Network mainnet to v7.2.0 at block height 25516877, estimated to occur on Tuesday, February 10, 2026 at 15:00 UTC. The major changes includes a Cosmos SDK upgrade, support for new modules(circuit breaker and protocolpool) and governance gated wasm contract upload.\n\nView the full proposal: hxxps://black-blank-booby-672[.]mypinata[.]cloud/ipfs/bafkreiem3zqt23tc4btxymkruxcoaxmikn5whuivy3yhvxdek6qlzva7ym
\n
\n submitted 2026-01-30\n voting closed 2026-02-06\n \n deposit 6,000 / 2,000 REGEN\n proposer regen1h5z08rzvrwt3pzdjc03upvuh2x0j3yskr2e95r\n \n
\n
","63":"
\n What it executes\n
MsgCommunityPoolSpend

Pays 867,000 REGEN out of the community pool to regen1vpxm32hark2kh4l6jcrn2c40pwgzw40jnzpjs3.

recipient: regen1vpxm32hark2kh4l6jcrn2c40pwgzw40jnzpjs3\namount: [{"denom":"uregen","amount":"867000000000"}]
\n

Title comes straight from the proposal record.

\n \n How the stake voted\n
\n
\n yes 43,683,675\n abstain 180\n no 0\n veto 0\n 43,683,855 REGEN cast, which is 51.4% of the stake bonded today\n
\n What the proposer wrote
Disbursement of earmarked emissions to the Regen LiquidityDAO from Community Pool representing emissions collected between Jan 14, 2026 and Mar 29, 2026. This transfer implements the emissions allocation approved by the Regen community in Proposals #49 and #52. Tracking data and emission calculations are available upon request.
\n
\n submitted 2026-03-29\n voting closed 2026-04-05\n \n deposit 2,000 / 2,000 REGEN\n proposer regen1vpxm32hark2kh4l6jcrn2c40pwgzw40jnzpjs3\n failed: external community pool is enabled - use the DistributFromCommunityPool method exposed by the external community pool: invalid request\n
\n
","64":"
\n What it executes\n
MsgUpdateParams

Sets REGEN issuance to move between 3.5% and 7% a year, with the bonded target at 60%, blocks_per_year set to 4,360,000 (implies 7.23s blocks).

params: {"mint_denom":"uregen","inflation_rate_change":"1.000000000000000000","inflation_max":"0.070000000000000000","inflation_min":"0.035000000000000000","goal_bonded":"0.600000000000000000","blocks_per_year":"4360000"}
\n

Title comes straight from the proposal record.

\n \n How the stake voted\n
\n
\n yes 47,967,962\n abstain 0\n no 0\n veto 0\n 47,967,962 REGEN cast, which is 56.4% of the stake bonded today\n
\n What the proposer wrote
For the whole network's benefit. Regen is currently minting REGEN at the maximum rate (inflation_max, 10%) with no path down: goal_bonded (67%) chases an actual bonded ratio (~60.6%) that the stock Cosmos SDK mint formula structurally cannot let it reach, so inflation stays pinned at the ceiling and the network dilutes every holder at the maximum rate for security it is not actually getting. This is a standard x/mint MsgUpdateParams — no new code, no chain upgrade, effective the moment it passes — setting goal_bonded 0.67→0.60 (matching reality so inflation can finally ease off the ceiling) and inflation_max 0.10→0.07 (slowing dilution while the bonded pool is this thin). It saves the network real money and protects REGEN's value, so the community and Foundation can put their energy into actual revenue — ecocredit issuance and agentic ecological work (EWP) — instead of fighting structural dilution. It continues a body of contributor work (brawlaphant): community-call participation, the ERC-1155 credit-wrapping and Hybrid Ecological Bonds designs, and the Economic Reboot framework, all aimed at making Regen economically self-sustaining.
\n
\n submitted 2026-07-08\n voting closed 2026-07-15\n \n deposit 2,000 / 2,000 REGEN\n proposer regen1jfheyvsah5wqfyawmedme43te056z8gzdnpf3j (EcoWealth, this page's operator)\n \n
\n
","65":"
\n What it executes\n
MsgRecoverClient

Recovers the expired IBC light client 07-tendermint-113 using 07-tendermint-185 as the substitute.

subject_client_id: 07-tendermint-113\nsubstitute_client_id: 07-tendermint-185\nsigner: regen10d07y265gmmuvt4z0w9aw880jnsr700j9qceqh
\n

Title comes straight from the proposal record.

\n \n How the stake voted\n
\n
\n yes 57,080,140\n abstain 0\n no 5,000\n veto 0\n 57,085,140 REGEN cast, which is 67.1% of the stake bonded today\n
\n What the proposer wrote
Recover the expired Quicksilver IBC client using a freshly created substitute client, preserving existing connections and channels.
\n
\n submitted 2026-07-18\n voting closed 2026-07-25\n \n deposit 2,000 / 2,000 REGEN\n proposer regen12zqrwrgp4ntqswk8rn9dcv2ykwqa3ml2umdst4\n \n
\n
","66":"
\n What it executes\n
MsgUpdateParams

Sets the community pool to pay out every block, in stake and uregen.

params: {"enabled_distribution_denoms":["stake","uregen"],"distribution_frequency":"1"}
MsgCreateContinuousFund

Streams 15% of community pool revenue to regen1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqvptr3e, with no end date.

recipient: regen1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqvptr3e\npercentage: 0.150000000000000000\nexpiry: null
\n

Title comes straight from the proposal record.

\n \n How the stake voted\n
\n
\n yes 57,062,530\n abstain 1,226\n no 0\n veto 0\n 57,063,756 REGEN cast, which is 67.1% of the stake bonded today\n
\n What the proposer wrote
Bootstrap the Economic Reboot's M013 Burn Pool with NO chain upgrade, effective the moment it passes. This is a standard x/protocolpool action: (1) enable uregen distribution, then (2) create a continuous fund routing 15.0% of community-pool revenue (validator block rewards = inflation + fees) to the null burn address (removed from circulation, on-chain). It turns real network revenue into standing deflationary pressure on REGEN — the market-side complement to the mint-params fix (prop #64). Honest scope: Regen Ledger has no supply-burn module yet, so this REMOVES REGEN from circulation (permanently unspendable); a true total-supply burn arrives with the full M013 x/feerouter + x/supply upgrade (Phase 2). The burn share is a governance dial (15.0% here, per the WG's current M013 figure) and can be adjusted or cancelled anytime (MsgCancelContinuousFund). Continues the contributor work behind the Economic Reboot framework.
\n
\n submitted 2026-07-18\n voting closed 2026-07-25\n \n deposit 2,000 / 2,000 REGEN\n proposer regen1jfheyvsah5wqfyawmedme43te056z8gzdnpf3j (EcoWealth, this page's operator)\n \n
\n
","67":"
\n What it executes\n
MsgUpdateParams

Fixes REGEN issuance at a flat 3.5% a year, with the bonded target at 60%, blocks_per_year set to 4,360,000 (implies 7.23s 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":"4360000"}
\n

Title comes straight from the proposal record.

\n \n How the stake voted\n
\n
\n yes 50,127,105\n abstain 0\n no 0\n veto 0\n 50,127,105 REGEN cast, which is 58.9% of the stake bonded today\n
\n What the proposer wrote
I authored proposal #64 from this same address, and #64 did not finish its job. It lowered inflation_max from 10% to 7%, which saved the network real money, but it did not unpin the rate, and the reason is an error in my own analysis. This proposal corrects it. WHAT IS TRUE ON CHAIN AS THIS WAS BUILT (every figure read live, none quoted from a document; reproduce commands at the end): inflation is 0.070000, which is exactly inflation_max — the signature of a rate welded to its ceiling, not one settling toward a target. x/mint moves inflation by rate_of_change = (1 - bonded_ratio/goal_bonded) * inflation_rate_change, dividing bonded tokens by the bank keeper's TOTAL supply. Bonded is 85,396,190 REGEN against a total supply of 238,632,064 REGEN, so the real bonded ratio is 0.3579. In #64 I used roughly 0.606: I divided the then-bonded ~89.7M by ~148M, which is a CoinGecko CIRCULATING-supply figure, when x/mint divides by total supply. Against goal_bonded of 0.6 the sign stays positive at +0.4036/yr, so inflation is pushed up and held at the ceiling and cannot come down on its own. goal_bonded would have to be strictly below 0.3579 to flip it; at exactly equal, rate_of_change is 0 and the rate simply holds. WHAT THIS CHANGES: exactly one field. inflation_max goes from 0.07 to 0.035. inflation_min is ALREADY 0.035 and is left untouched. Because max and min are then equal, the mint rate is clamped to exactly the 3.50% parameter regardless of bonded ratio — the clamp is what the two together produce, not a second change. Every other mint param is read live and passed through unchanged. One standard x/mint MsgUpdateParams, effective the moment it passes, no chain upgrade. THE NOMINAL RATE IS NOT THE REALIZED RATE, AND I WANT THAT ON THE RECORD RATHER THAN DISCOVERED LATER: x/mint mints annual_provisions/blocks_per_year each block. blocks_per_year is 4360000 (implying 7.23s blocks) but measured block time over the last 100,000 blocks is 5.641s, so the chain produces about 5,590,079 blocks/yr and over-mints by 1.282x. Nominal annual_provisions reads 16,704,244 REGEN/yr, but REALIZED emission is about 21,416,983 REGEN/yr, i.e. 8.97% of supply, not 7.00%. After this passes the parameter is 3.50% and the realized rate will be about 4.49%. So the real saving is about 10,708,492 REGEN/yr (about $12,434 at $0.00116112/REGEN), roughly 4.49% of supply per year, and it accrues to every holder. Anyone can check this by measuring supply growth; I would rather state it than have it used against the proposal. Correcting blocks_per_year itself is a separate proposal and is deliberately not bundled here. DISCLOSURE — THIS HALVES MY OWN BURN PROGRAM. I also authored #66, the M013 burn pool, from this address. #66 streams 15.0% of community-pool revenue to the null sink, and that revenue is 17% of block rewards, so it scales directly with emissions. The burn currently runs about 546,133 REGEN/yr; after this it runs about 273,067 REGEN/yr. I am cutting my own burn program's throughput roughly in half. Net supply change still improves by far more than the burn loses, because the burn is a small fraction of emissions — but voters should know this before voting, not after. Everything already accumulated in the pool and the sink is untouched. EVERY OTHER COMMUNITY-POOL-FUNDED PROGRAM IS ALSO HALVED, for the same reason: LiquidityDAO emissions transfers, the Tokenomics WG funding, the X-Influencers pilot, and any future pool-funded work including my own. Pool inflow goes from about 3,640,887 REGEN/yr to about 1,820,444 REGEN/yr. ON THE SECURITY BUDGET, HONESTLY: this cuts validator income and that deserves a straight answer. Note emissions accrue to DELEGATORS, not to validators — what reaches an operator is commission on its delegators' rewards plus rewards on its own self-bond. Commission across all 14 active validators is about 1,760,384 REGEN/yr (about $2,044 at $0.00116112/REGEN) combined, self-bond excluded, so per-operator revenue is small either way and this halves it. I am not pretending that is costless. The argument for doing it anyway is that no plausible emission rate at this valuation turns that into a viable business; only revenue and a curated set do. AND THE SET IS SHRINKING WHILE I PROPOSE THIS: 14 validators are active, 1 are currently UNBONDING (7,371,269 REGEN), and many unbonded monikers read "please redelegate". Disclosing that is stronger than letting someone raise it. TWO STRUCTURAL CONSEQUENCES I DO NOT WANT TO HIDE: (1) with max == min there is no automatic inflation response to any bonded ratio, so every future adjustment needs a governance vote. (2) goal_bonded stays on the books at 0.6 and becomes decorative; a future proposal that raises inflation_max alone would silently re-arm it against a 0.3579 ratio and re-pin to the new ceiling. A later proposal should retire or realign it. THIS IS NOT THE VALIDATOR-SET QUESTION. It does not remove anyone from the set; max_validators is untouched and not proposed here. It shares a premise with the validator-economics discussion at https://forum.regen.network/t/validators-and-staking-yields/616 and with the Proof-of-Authority discussion on the forum — note those are forum threads, not on-chain proposal numbers. NOT ZERO, ON PURPOSE: zero emissions would ask validators to run for free. 3.50% is defensible today and leaves the road to zero open if the network later commits to a curated set. REVERSIBLE, WITH CAVEATS: one later MsgUpdateParams restores the parameter, no upgrade needed. But restoring inflation_max to 0.07 would not restore that rate immediately — inflation would sit at 0.035 and climb at +0.4036/yr, taking roughly 32 days to re-reach the ceiling; and reversal costs a fresh 2000 REGEN deposit, a full voting period, and quorum from a validator set whose income this cut. "Reversible" is true; "instant and free" is not. REPRODUCE EVERYTHING: /cosmos/mint/v1beta1/inflation, /cosmos/mint/v1beta1/annual_provisions, /cosmos/mint/v1beta1/params, /cosmos/staking/v1beta1/pool, /cosmos/bank/v1beta1/supply/by_denom?denom=uregen, /cosmos/distribution/v1beta1/params, /cosmos/protocolpool/v1/continuous_funds, and two /cosmos/base/tendermint/v1beta1/blocks/{h} timestamps for block time.
\n
\n submitted 2026-07-30\n voting closed 2026-08-06\n \n deposit 2,000 / 2,000 REGEN\n proposer regen1jfheyvsah5wqfyawmedme43te056z8gzdnpf3j (EcoWealth, this page's operator)\n \n
\n
","69":"
\n What it executes\n
MsgRecoverClient

Recovers the expired IBC light client 07-tendermint-113 using 07-tendermint-186 as the substitute.

subject_client_id: 07-tendermint-113\nsubstitute_client_id: 07-tendermint-186\nsigner: regen10d07y265gmmuvt4z0w9aw880jnsr700j9qceqh
\n

Title comes straight from the proposal record.

\n \n How the stake voted\n
\n
\n yes 50,231,910\n abstain 128\n no 0\n veto 0\n 50,232,038 REGEN cast, which is 59.1% of the stake bonded today\n
\n What the proposer wrote
Recover the expired Quicksilver IBC client using a freshly created substitute client, preserving existing connections and channels. The previously recovered client 07-tendermint-185 expired before we were able to update our relayers.
\n
\n submitted 2026-08-03\n voting closed 2026-08-10\n \n deposit 2,000 / 2,000 REGEN\n proposer regen12zqrwrgp4ntqswk8rn9dcv2ykwqa3ml2umdst4\n \n
\n
"},"cards":["
\n
C03-008C03
\n

Inner Mongolia Chao’er Improved Forest Management Project

\n

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

\n

Inner Mongolia, China

\n \n \n
BeZero Carbon BB
\n
issued 302,456retired 1,788tradable 11,1351 batch
\n
","
\n
C03-009C03
\n

Fujian Yong’an Improved Forest Management Project

\n

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

\n

Fujian, China

\n \n \n
BeZero Carbon BB
\n
issued 6,141retired 0tradable 2,2002 batches
\n
","
\n
C03-010C03
\n

Yunnan Kunming Liangqu Improved Forest Management Project

\n

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

\n

Yunnan, China

\n \n \n
BeZero Carbon B
\n
issued 1,805retired 0tradable 03 batches
\n
","
\n
C03-011C03
\n

Jiangxi Province Le'an County Forest Farm Carbon Sink Project

\n

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

\n

Jiangxi, China

\n \n \n
BeZero Carbon BBB
\n
issued 276retired 0tradable 01 batch
\n
","
\n
C03-012C03
\n

North Pikounda REDD+

\n

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

\n

Sangha, Republic of the Congo

\n \n \n \n
issued 450retired 2tradable 01 batch
\n
","
\n
C05-001C05
\n

San Juan Carbon Project

\n

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

\n

Turtleback Mountain Preserve, Eastsound, Washington 98245, United States

\n
2022 to 2024San Juan Conservation District
\n

The San Juan Islands Garry Oak Restoration Burns Project focuses on producing biochar from waste biomass in Washington's San Juan Islands. By converting wood waste gathered from wildfire prevention and invasive species control efforts into biochar, this project sequesters carbon, reduces GHG emissions, and restores native Garry Oak woodlands. The in-stand biochar application enhances soil health and supports long-term carbon storage.

\n
ForestImproved Forest ManagementBiochar ProductionSDG 13: Climate Action
\n
issued 23retired 0tradable 231 batch
\n
","
\n
C06-001C06
\n

Philipson Estate Blaston

\n

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

\n

Blaston, Leicestershire, England, United Kingdom

\n
267 haEcometric
\n \n \n
issued 4,084retired 3,032tradable 7843 batches
\n
","
\n
C06-002C06
\n

Pimlico Farm

\n

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

\n

Oxfordshire, United Kingdom

\n
150 ha2022 to 2032Ecometric
\n

The primary indicator in this credit class is SOCS. Levels will be increased by growing harvestable and cover crops and grass to maximise canopy and root growth while incorporating crop residues and manures. Reduced soil disturbance, maintaining soil cover and returning crop residues will maximise retained organic matter (OM) in the soil and, through improved soil microbial activity, this will be converted to resilient SOC.

\n
CroplandPasturelandRegenerative Crop ManagementManaged Grazing
\n
issued 8,406retired 5tradable 4,1032 batches
\n
","
\n
C06-003C06
\n

Bromborough Estate

\n

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

\n

Northamptonshire, United Kingdom

\n
359 ha2022 to 2032Ecometric
\n

The primary indicator in this credit class is SOCS. Levels will be increased by growing harvestable and cover crops and grass to maximise canopy and root growth while incorporating crop residues and manures. Reduced soil disturbance, maintaining soil cover and returning crop residues will maximise retained organic matter (OM) in the soil and, through improved soil microbial activity, this will be converted to resilient SOC.

\n
CroplandPasturelandRegenerative Crop ManagementManaged Grazing
\n
issued 5,384retired 146tradable 5,2382 batches
\n
","
\n
C06-004C06
\n

Marston Lodge

\n

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

\n

LE16 9TT, Market Harborough, West Northamptonshire, England, United Kingdom

\n
148 ha2022 to 2032Ecometric
\n \n
CroplandPasturelandRegenerative Crop ManagementManaged Grazing
\n
issued 7,883retired 1tradable 7,8821 batch
\n
","
\n
C06-005C06
\n

Neesham Farm Ltd.

\n

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

\n

Lincoln, Lincolnshire, England, United Kingdom

\n
209 ha2022 to 2032Ecometric
\n \n
CroplandPasturelandRegenerative Crop ManagementManaged Grazing
\n
issued 1,301retired 0tradable 1,3011 batch
\n
","
\n
C06-006C06
\n

Botany Farm Partnership

\n

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

\n

Northampton, West Northamptonshire, England, United Kingdom

\n
82 ha2022 to 2032Ecometric
\n \n
CroplandPasturelandRegenerative Crop ManagementManaged Grazing
\n
issued 596retired 0tradable 5961 batch
\n
","
\n
C06-007C06
\n

Lowick Manor Farm

\n

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

\n

NN14 3BG, Kettering, North Northamptonshire, England, United Kingdom

\n
557 ha2022 to 2032Ecometric
\n \n
CroplandPasturelandRegenerative Crop ManagementManaged Grazing
\n
issued 8,050retired 0tradable 8,0501 batch
\n
","
\n
C06-008C06
\n

Alan Woodley & Sons

\n

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

\n

Peterborough, Cambridgeshire, England, United Kingdom

\n
112 ha2022 to 2031Ecometric
\n \n
CroplandPasturelandRegenerative Crop ManagementManaged Grazing
\n
issued 2,245retired 0tradable 2,2451 batch
\n
","
\n
C06-009C06
\n

Southill Park Estate

\n

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

\n

Biggleswade, Central Bedfordshire, England, United Kingdom

\n
274 ha2022 to 2031Ecometric
\n \n
CroplandPasturelandRegenerative Crop ManagementManaged Grazing
\n
issued 2,625retired 0tradable 2,6251 batch
\n
","
\n
C06-010C06
\n

Bramall Farming Limited

\n

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

\n

Epworth, Lincolnshire, England

\n
176 ha2023 to 2032Ecometric
\n

The primary indicator in this credit class is SOCS. Levels will be increased by growing harvestable and cover crops and grass to maximise canopy and root growth while incorporating crop residues and manures. Reduced soil disturbance, maintaining soil cover and returning crop residues will maximise retained organic matter (OM) in the soil and, through improved soil microbial activity, this will be converted to resilient SOC.

\n
CroplandPasturelandRegenerative Crop ManagementManaged Grazing
\n
issued 4,041retired 0tradable 4,0411 batch
\n
","
\n
C06-011C06
\n

Burton Latimer Farms

\n

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

\n

Wellingborough, Bedford, England

\n
282 ha2023 to 2032Ecometric
\n \n
CroplandPasturelandRegenerative Crop ManagementManaged Grazing
\n
issued 923retired 0tradable 9231 batch
\n
","
\n
C06-012C06
\n

Burrough Court Estate

\n

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

\n

Melton Mowbray, Leicestershire, England

\n
145 ha2023 to 2032Ecometric
\n \n
CroplandPasturelandRegenerative Crop ManagementManaged Grazing
\n
issued 489retired 0tradable 4891 batch
\n
","
\n
C06-013C06
\n

Coppicemoor Farm

\n

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

\n

Kettering, North Northamptonshire, England

\n
180 ha2023 to 2032Ecometric
\n \n
CroplandPasturelandRegenerative Crop ManagementManaged Grazing
\n
issued 3,891retired 0tradable 3,8911 batch
\n
","
\n
C06-014C06
\n

Edward Pope Farms

\n

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

\n

King's Lynn, Norfolk, England

\n
87 ha2023 to 2032Ecometric
\n \n
CroplandPasturelandRegenerative Crop ManagementManaged Grazing
\n
registered, no credits issued yet
\n
","
\n
C06-015C06
\n

Fonthill Farms

\n

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

\n

Salisbury, Wiltshire, England

\n
487 ha2023 to 2032Ecometric
\n \n
CroplandPasturelandRegenerative Crop ManagementManaged Grazing
\n
issued 7,925retired 0tradable 7,9251 batch
\n
","
\n
C06-016C06
\n

Greens Lodge Farms

\n

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

\n

Huncote, Leicestershire, England

\n
256 ha2023 to 2032Ecometric
\n \n
CroplandPasturelandRegenerative Crop ManagementManaged Grazing
\n
issued 816retired 0tradable 8161 batch
\n
","
\n
C06-017C06
\n

HCF Farms

\n

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

\n

Staverton, West Northamptonshire, England

\n
133 ha2023 to 2032Ecometric
\n \n
CroplandPasturelandRegenerative Crop ManagementManaged Grazing
\n
issued 2,855retired 0tradable 2,8551 batch
\n
","
\n
C06-018C06
\n

John Darby Farms

\n

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

\n

Lutterworth, Leicestershire, England

\n
452 ha2023 to 2032Ecometric
\n \n
CroplandPasturelandRegenerative Crop ManagementManaged Grazing
\n
issued 3,920retired 0tradable 3,9201 batch
\n
","
\n
C06-019C06
\n

RE and EJ Kerr

\n

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

\n

Market Rasen, Lincolnshire, England

\n
186 ha2023 to 2032Ecometric
\n \n
CroplandPasturelandRegenerative Crop ManagementManaged Grazing
\n
issued 727retired 0tradable 7271 batch
\n
","
\n
C06-020C06
\n

Windmill Down Farms

\n

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

\n

Hambledon, Hampshire, England

\n
123 ha2023 to 2032Ecometric
\n \n
CroplandPasturelandRegenerative Crop ManagementManaged Grazing
\n
issued 1,134retired 0tradable 1,1341 batch
\n
","
\n
C06-021C06
\n

Rockscape Farms

\n

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

\n

Crowle, North Lincolnshire, England

\n
281 ha2023 to 2032Ecometric
\n \n
CroplandPasturelandRegenerative Crop ManagementManaged Grazing
\n
issued 2,648retired 0tradable 2,6481 batch
\n
","
\n
C06-022C06
\n

CSSCP site CZ 001

\n

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

\n

Czech Republic

\n
7 ha2021 to 2031Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-023C06
\n

CSSCP site CZ 002

\n

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

\n

Czech Republic

\n
319 ha2021 to 2031Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-024C06
\n

CSSCP site CZ 003

\n

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

\n

Czech Republic

\n
44 ha2021 to 2031Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-025C06
\n

CSSCP site CZ 004

\n

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

\n

Czech Republic

\n
16 ha2021 to 2031Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-026C06
\n

CSSCP site CZ 005

\n

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

\n

Czech Republic

\n
52 ha2021 to 2031Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-027C06
\n

CSSCP site CZ 006

\n

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

\n

Czech Republic

\n
64 ha2021 to 2031Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-028C06
\n

CSSCP site CZ 007

\n

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

\n

Czech Republic

\n
36 ha2021 to 2031Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-029C06
\n

CSSCP site CZ 008

\n

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

\n

Czech Republic

\n
53 ha2021 to 2031Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-030C06
\n

CSSCP site CZ 009

\n

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

\n

Czech Republic

\n
67 ha2021 to 2031Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-031C06
\n

CSSCP site CZ 010

\n

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

\n

Czech Republic

\n
247 ha2021 to 2031Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-032C06
\n

CSSCP site CZ 011

\n

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

\n

Czech Republic

\n
449 ha2021 to 2031Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-033C06
\n

CSSCP site CZ 012

\n

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

\n

Czech Republic

\n
37 ha2021 to 2031Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-034C06
\n

CSSCP site CZ 013

\n

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

\n

Czech Republic

\n
40 ha2021 to 2031Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-035C06
\n

CSSCP site CZ 014

\n

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

\n

Czech Republic

\n
26 ha2022 to 2032Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-036C06
\n

CSSCP site CZ 015

\n

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

\n

Czech Republic

\n
155 ha2022 to 2032Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-037C06
\n

CSSCP site CZ 016

\n

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

\n

Czech Republic

\n
13 ha2022 to 2032Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-038C06
\n

CSSCP site CZ 017

\n

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

\n

Czech Republic

\n
749 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-039C06
\n

CSSCP site CZ 018

\n

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

\n

Czech Republic

\n
395 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-040C06
\n

CSSCP site CZ 019

\n

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

\n

Czech Republic

\n
103 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-041C06
\n

CSSCP site CZ 020

\n

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

\n

Czech Republic

\n
314 ha2022 to 2032Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-042C06
\n

CSSCP site CZ 021

\n

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

\n

Czech Republic

\n
88 ha2022 to 2032Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-043C06
\n

CSSCP site CZ 022

\n

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

\n

Czech Republic

\n
43 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-044C06
\n

CSSCP site CZ 023

\n

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

\n

Czech Republic

\n
42 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-045C06
\n

CSSCP site CZ 024

\n

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

\n

Czech Republic

\n
19 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-046C06
\n

CSSCP site CZ 025

\n

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

\n

Czech Republic

\n
12 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-047C06
\n

CSSCP site CZ 026

\n

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

\n

Czech Republic

\n
87 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-048C06
\n

CSSCP site CZ 027

\n

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

\n

Czech Republic

\n
63 ha2026 to 2036Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-049C06
\n

CSSCP site CZ 028

\n

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

\n

Czech Republic

\n
159 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-050C06
\n

CSSCP site CZ 029

\n

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

\n

Czech Republic

\n
66 ha2025 to 2035Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-051C06
\n

CSSCP site CZ 030

\n

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

\n

Czech Republic

\n
138 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-052C06
\n

CSSCP site CZ 031

\n

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

\n

Czech Republic

\n
104 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-053C06
\n

CSSCP site CZ 032

\n

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

\n

Czech Republic

\n
10 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-054C06
\n

CSSCP site CZ 033

\n

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

\n

Czech Republic

\n
215 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-055C06
\n

CSSCP site CZ 034

\n

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

\n

Czech Republic

\n
12 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-056C06
\n

CSSCP site CZ 035

\n

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

\n

Czech Republic

\n
52 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-057C06
\n

CSSCP site CZ 036

\n

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

\n

Czech Republic

\n
27 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-058C06
\n

CSSCP site CZ 037

\n

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

\n

Czech Republic

\n
84 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-059C06
\n

CSSCP site CZ 038

\n

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

\n

Czech Republic

\n
103 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-060C06
\n

CSSCP site CZ 039

\n

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

\n

Czech Republic

\n
253 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-061C06
\n

CSSCP site CZ 040

\n

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

\n

Czech Republic

\n
102 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-062C06
\n

CSSCP site CZ 041

\n

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

\n

Czech Republic

\n
159 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-063C06
\n

CSSCP site CZ 042

\n

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

\n

Czech Republic

\n
192 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-064C06
\n

CSSCP site CZ 043

\n

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

\n

Czech Republic

\n
183 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-065C06
\n

CSSCP site CZ 044

\n

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

\n

Czech Republic

\n
269 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-066C06
\n

CSSCP site CZ 045

\n

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

\n

Czech Republic

\n
151 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-067C06
\n

CSSCP site CZ 046

\n

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

\n

Czech Republic

\n
185 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-068C06
\n

CSSCP site CZ 047

\n

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

\n

Czech Republic

\n
56 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-069C06
\n

CSSCP site CZ 048

\n

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

\n

Czech Republic

\n
43 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-070C06
\n

CSSCP site CZ 049

\n

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

\n

Czech Republic

\n
370 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-071C06
\n

CSSCP site CZ 050

\n

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

\n

Czech Republic

\n
225 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-072C06
\n

CSSCP site CZ 051

\n

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

\n

Czech Republic

\n
41 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-073C06
\n

CSSCP site CZ 052

\n

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

\n

Czech Republic

\n
67 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-074C06
\n

CSSCP site CZ 053

\n

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

\n

Czech Republic

\n
41 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-075C06
\n

CSSCP site CZ 054

\n

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

\n

Czech Republic

\n
177 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-076C06
\n

CSSCP site CZ 055

\n

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

\n

Czech Republic

\n
20 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-077C06
\n

CSSCP site CZ 056

\n

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

\n

Czech Republic

\n
15 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-078C06
\n

CSSCP site CZ 057

\n

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

\n

Czech Republic

\n
14 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-079C06
\n

CSSCP site CZ 058

\n

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

\n

Czech Republic

\n
96 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-080C06
\n

CSSCP site CZ 059

\n

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

\n

Czech Republic

\n
24 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-081C06
\n

CSSCP site CZ 060

\n

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

\n

Czech Republic

\n
44 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-082C06
\n

CSSCP site CZ 061

\n

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

\n

Czech Republic

\n
12 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-083C06
\n

CSSCP site CZ 062

\n

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

\n

Czech Republic

\n
14 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-084C06
\n

CSSCP site CZ 063

\n

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

\n

Czech Republic

\n
184 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-085C06
\n

CSSCP site CZ 064

\n

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

\n

Czech Republic

\n
157 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-086C06
\n

CSSCP site CZ 065

\n

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

\n

Czech Republic

\n
14 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-087C06
\n

CSSCP site CZ 066

\n

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

\n

Czech Republic

\n
21 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-088C06
\n

CSSCP site CZ 067

\n

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

\n

Czech Republic

\n
44 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-089C06
\n

CSSCP site CZ 068

\n

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

\n

Czech Republic

\n
101 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-090C06
\n

CSSCP site CZ 069

\n

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

\n

Czech Republic

\n
53 ha2026 to 2036Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-091C06
\n

CSSCP site CZ 070

\n

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

\n

Czech Republic

\n
24 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-092C06
\n

CSSCP site CZ 071

\n

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

\n

Czech Republic

\n
32 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-093C06
\n

CSSCP site CZ 072

\n

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

\n

Czech Republic

\n
35 ha2025 to 2035Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-094C06
\n

CSSCP site CZ 073

\n

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

\n

Czech Republic

\n
184 ha2025 to 2035Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-095C06
\n

CSSCP site CZ 074

\n

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

\n

Czech Republic

\n
14 ha2022 to 2032Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-096C06
\n

CSSCP site CZ 075

\n

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

\n

Czech Republic

\n
96 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-097C06
\n

CSSCP site SK 001

\n

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

\n

Slovakia

\n
26 ha2022 to 2032Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-098C06
\n

CSSCP site SK 002

\n

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

\n

Slovakia

\n
786 ha2022 to 2032Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-099C06
\n

CSSCP site SK 003

\n

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

\n

Slovakia

\n
40 ha2022 to 2032Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-100C06
\n

CSSCP site SK 004

\n

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

\n

Slovakia

\n
113 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-101C06
\n

CSSCP site SK 005

\n

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

\n

Slovakia

\n
632 ha2022 to 2032Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-102C06
\n

CSSCP site SK 006

\n

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

\n

Slovakia

\n
246 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-103C06
\n

CSSCP site 02.0006.00828

\n

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

\n

Slovakia

\n
37 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-104C06
\n

CSSCP site SK 008

\n

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

\n

Slovakia

\n
1,068 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-105C06
\n

CSSCP site SK 009

\n

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

\n

Slovakia

\n
1,328 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-106C06
\n

CSSCP site SK 010

\n

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

\n

Slovakia

\n
208 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-107C06
\n

CSSCP site SK 011

\n

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

\n

Slovakia

\n
453 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-108C06
\n

CSSCP site SK 012

\n

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

\n

Slovakia

\n
1,123 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-109C06
\n

CSSCP site SK 013

\n

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

\n

Slovakia

\n
149 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-110C06
\n

CSSCP site SK 014

\n

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

\n

Slovakia

\n
435 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-111C06
\n

CSSCP site SK 015

\n

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

\n

Slovakia

\n
488 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-112C06
\n

CSSCP site SK 016

\n

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

\n

Slovakia

\n
42 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-113C06
\n

CSSCP site SK 017

\n

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

\n

Slovakia

\n
433 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-114C06
\n

CSSCP site SK 018

\n

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

\n

Slovakia

\n
527 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-115C06
\n

CSSCP site SK 019

\n

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

\n

Slovakia

\n
373 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-116C06
\n

CSSCP site SK 020

\n

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

\n

Slovakia

\n
461 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-117C06
\n

CSSCP site SK 021

\n

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

\n

Slovakia

\n
76 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-118C06
\n

CSSCP site SK 022

\n

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

\n

Slovakia

\n
28 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-119C06
\n

CSSCP site SK 023

\n

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

\n

Slovakia

\n
441 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-120C06
\n

CSSCP site SK 024

\n

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

\n

Slovakia

\n
37 ha2023 to 2033Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-121C06
\n

CSSCP site SK 025

\n

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

\n

Slovakia

\n
215 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-122C06
\n

CSSCP site SK 026

\n

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

\n

Slovakia

\n
165 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-123C06
\n

CSSCP site SK 027

\n

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

\n

Slovakia

\n
252 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-124C06
\n

CSSCP site SK 028

\n

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

\n

Slovakia

\n
107 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-125C06
\n

CSSCP site SK 029

\n

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

\n

Slovakia

\n
289 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-126C06
\n

CSSCP site SK 030

\n

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

\n

Slovakia

\n
280 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-127C06
\n

CSSCP site SK 031

\n

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

\n

Slovakia

\n
146 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-128C06
\n

CSSCP site SK 032

\n

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

\n

Slovakia

\n
67 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-129C06
\n

CSSCP site SK 033

\n

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

\n

Slovakia

\n
37 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-130C06
\n

CSSCP site SK 034

\n

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

\n

Slovakia

\n
515 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-131C06
\n

CSSCP site SK 035

\n

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

\n

Slovakia

\n
138 ha2025 to 2035Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-132C06
\n

CSSCP site SK 036

\n

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

\n

Slovakia

\n
623 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-133C06
\n

CSSCP site SK 037

\n

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

\n

Slovakia

\n
641 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-134C06
\n

CSSCP site SK 038

\n

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

\n

Slovakia

\n
646 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-135C06
\n

CSSCP site SK 039

\n

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

\n

Slovakia

\n
655 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-136C06
\n

CSSCP site SK 040

\n

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

\n

Slovakia

\n
22 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-137C06
\n

CSSCP site SK 041

\n

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

\n

Slovakia

\n
407 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-138C06
\n

CSSCP site SK 042

\n

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

\n

Slovakia

\n
200 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-139C06
\n

CSSCP site SK 043

\n

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

\n

Slovakia

\n
58 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-140C06
\n

CSSCP site SK 044

\n

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

\n

Slovakia

\n
99 ha2025 to 2035Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-141C06
\n

CSSCP site SK 045

\n

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

\n

Slovakia

\n
201 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-142C06
\n

CSSCP site SK 046

\n

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

\n

Slovakia

\n
145 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-143C06
\n

CSSCP site SK 047

\n

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

\n

Slovakia

\n
119 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Pastureland
\n
registered, no credits issued yet
\n
","
\n
C06-144C06
\n

CSSCP site SK 048

\n

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

\n

Slovakia

\n
228 ha2024 to 2034Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-145C06
\n

CSSCP site SK 049

\n

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

\n

Slovakia

\n
94 ha2026 to 2036Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-146C06
\n

CSSCP site SK 050

\n

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

\n

Slovakia

\n
73 ha2025 to 2035Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-147C06
\n

CSSCP site SK 051

\n

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

\n

Slovakia

\n
39 ha2025 to 2035Carboneg Group s.r.o.
\n \n
Cropland
\n
registered, no credits issued yet
\n
","
\n
C06-148C06
\n

Czech-Slovak Soil Carbon Project

\n

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

\n

Czech Republic and Slovakia

\n
24,238 ha2021 to 2036Carboneg Group s.r.o.
\n

A GHG removal project implemented by Carboneg Group that enhances soil organic carbon sequestration through regenerative agricultural practices in cropland and pastures.

\n
CroplandPasturelandResidue and Tillage ManagementCover CroppingBeZero Carbon Rating: A.pre A.pre
\n
registered, no credits issued yet
\n
","
\n
C07-001C07
\n

Woodburn

\n

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

\n

960 Hillview Road, Salisbury Plains New South Wales 2358, Australia

\n
2,321 ha2017 to 2027
\n

Woodburn is a beef breeding operation situated north of Walcha on the New England tablelands of Australia. The grasslands here grow on basalt and sandy loam soils and host Woodburn's high density herds of cattle. Considerable investments have been made at Woodburn to improve fencing and water infrastructure, enabling for an increase in animal density integral to prescribed grazing. Continued improvement in the ecological state of the farm is core to how Woodburn is managed.

\n
GrasslandShrublandPasturePerscribed Grazing
\n
registered, no credits issued yet
\n
","
\n
C07-002C07
\n

Cavan Station

\n

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

\n

47 Cavan Road, Cavan New South Wales 2582, Australia

\n
9,900 ha2017 to 2027
\n

Cavan Station is on the southern tablelands of New South Wales, Australia. Divided by the Murrumbidgee River at Yass, it comprises a diverse range of landscapes including limestone rocky outcrops, undulating slopes and steep native vegetated hills. The Cavan Station angus cow herd has been developed over the past 20 years on the harsh Southern Tablelands environment and steep limestone hills. The lands are managed with time controlled rotational grazing.

\n
GrasslandShrublandPasturePrescribed Grazing
\n
registered, no credits issued yet
\n
","
\n
C08-001C08
\n

Yahara WINS Watershed Carbon Project

\n

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

\n

1610 Moorland Road, Madison, Wisconsin 53713, United States

\n
13,922 ha2017 to 2036Madison Metropolitan Sewerage District (MMSD)
\n

The Yahara WINS Watershed Carbon Project implements nature-based and green infrastructure practices that avoid emissions from construction and operation of gray wastewater infrastructure. Through an adaptive management approach, the project reduces nutrient loads via agricultural and watershed best management practices—including cover crops, conservation cover, grassed waterways, wetland restoration, and structural erosion control measures—thereby avoiding the need for a tertiary/advanced filtration upgrade at the Nine Springs Wastewater Treatment Plant. Project Proponents quantify reduction in GHG emissions associated with the avoided energy and materials from the gray infrastructure that green solutions replace, including construction materials, decades of operational energy use, and facility maintenance. Credits issue annually ex-post throughout the avoided infrastructure's lifetime.

\n
WetlandCroplandGrasslandCover CroppingConservationSDG 13: Climate ActionSDG 6: Clean Water And Sanitation
\n
issued 24,143retired 1,000tradable 23,1431 batch
\n
","
\n
KSH01-001KSH01
\n

Grgich Hills Estate Regenerative Sheep Grazing

\n

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

\n

Rutherford, California

\n
127 ha2019 to 2023
\n \n
High Density, Short Duration Sheep Grazing
\n
issued 786retired 75tradable 7111 batch
\n
","
\n
MBS01-001MBS01
\n

Mangrove Forest: Marereni

\n

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

\n

Marereni

\n
500 ha
\n

Empowering local communities to plant and protect mangrove ecosystems in Marereni, Kilifi, Kenya

\n \n
issued 300,000retired 73,245tradable 226,7551 batch
\n
","
\n
MBS01-002MBS01
\n

Seatrees+ Coral Restoration in Costa Rica

\n

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

\n

Puerto Jiménez, Puntarenas, Costa Rica

\n
0 ha
\n \n \n
issued 4,000retired 24tradable 3,9761 batch
\n
","
\n
MBS01-003MBS01
\n

RESHABAY Portocolom Project

\n

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

\n

Felanitx, Balearic Islands, Spain

\n
75 haCleanwave Foundation
\n \n \n
issued 750,000retired 1tradable 749,9991 batch
\n
","
\n
USS01-001USS01
\n

Jaguar Stewardship in the Pantanal Conservation Network

\n

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

\n

Serra do Amolar, Corumbá, Mato Grosso do Sul, Brazil

\n
40,613 ha2021 to 2028ERA Brazil
\n

The Instituto Homem Pantaneiro (IHP) is an NGO dedicated to preserving the Brazilian Pantanal biome, considered the largest continental wetland on the planet and a Natural World Heritage Site. IHP conducts a range of activities to improve ecosystem health and jaguar habitat, including: managing protected areas, firefighting, monitoring biodiversity and deforestation, conducting research, and facilitating dialogue among stakeholders. One credit represents a composite measure of biodiversity stewardship effectiveness, focused on jaguars as an umbrella species, across a 40,613-hectare private conservation reserve, based on a Theory of Change established by ERA and IHP. The project combines advanced monitoring technologies with community engagement to address key threats, particularly wildfires which affected over 90% of the Serra do Amolar region in 2020.

\n
Tropical WetlandsUmbrella Species ConservationEcosystem RestorationSDG 15: Life On LandSDG 13: Climate Action
\n
issued 71,750retired 1,158tradable 70,5923 batches
\n
","
\n
USS01-002USS01
\n

Biocultural Jaguar Credits, Ancestral Stewardship in the Sharamentsa Community

\n

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

\n

Sharamentsa, Pastaza, Ecuador

\n
10,200 ha2023 to 2024Fundación Pachamama
\n

A biocultural conservation project led by the Sharamentsa community of the Achuar Nation, protecting jaguar habitat in the Ecuadorian Amazon through land management and community-based monitoring. This pilot initiative demonstrates a new ecological-economic model aligning biodiversity conservation with cultural integrity and local well-being.

\n
Tropical ForestUmbrella Species ConservationImproved Forest ManagementSDG 15: Life On LandSDG 13: Climate Action
\n
issued 6,238retired 5,434tradable 8041 batch
\n
"]}