Regen #76 9/11/2026, 10:39:34 PM

LiquidityDAO Emissions Transfer #6 (Resubmission)

Regen proposal #76: Resubmission of Proposal #63 (LiquidityDAO Emissions Transfer #6), which passed 43.68M to 0 on March 29, 2026 but failed on execution: it...

Yes

100%

No

0%

Abstain

0%

Veto

0%

If passed

Some execution details could not be interpreted. Review the source JSON before voting.

  1. 1. Uninterpreted operation

    This message type is not supported by the interpreter. Its effects are unknown.

AI Summary

gpt-5.4-mini - generated 9/9/2026, 1:41:19 AM

LiquidityDAO Emissions Transfer #6 (Resubmission)

Regen Proposal 76 resubmits a failed community pool transfer for LiquidityDAO emissions. It keeps the same 867,000 REGEN amount and recipient as Proposal 63, but switches to the correct x/protocolpool message after the v7/SDK 0.53 upgrade. The funds cover earmarked emissions from Jan 14 to Mar 29, 2026 and implement prior community approvals.

  • Resubmission of Proposal #63 after execution failed.
  • Transfers 867,000 REGEN to Regen LiquidityDAO.
  • Uses /cosmos.protocolpool.v1.MsgCommunityPoolSpend, the correct post-upgrade message.
  • Funds are earmarked emissions collected from Jan 14, 2026 to Mar 29, 2026.
  • Implements allocations approved in Proposals #49 and #52 and re-approved in #63.

Voter Impact

A yes vote would authorize the corrected transfer and complete a previously approved emissions allocation to LiquidityDAO. A no vote would leave the earmarked REGEN undistributed despite prior approvals.

Risk Signals

  • Execution previously failed due to using the old community pool message.
  • The proposal depends on correct handling of x/protocolpool after the v7 upgrade.
  • Tracking data and emission calculations are available only upon request, so voters must rely on the description's summary.

Original Proposal Text

Resubmission of Proposal #63 (LiquidityDAO Emissions Transfer #6), which passed 43.68M to 0 on March 29, 2026 but failed on execution: it used /cosmos.distribution.v1beta1.MsgCommunityPoolSpend, and since the v7 upgrade (SDK 0.53) the community pool balance is held by x/protocolpool, so the message executed against an empty account and the 867,000 REGEN never moved. This proposal is identical in amount and recipient and uses the correct /cosmos.protocolpool.v1.MsgCommunityPoolSpend message. It disburses earmarked emissions collected between Jan 14, 2026 and Mar 29, 2026 to the Regen LiquidityDAO, implementing the allocation approved by the community in Proposals #49 and #52 and re-approved in #63. Tracking data and emission calculations are available upon request.

Community

Up 0 Down 0 Comments 0

1XP X 0base.vc

Cosmos governance portal by 1XP Validator and 0base.vc

... chains Wallet ready