Introduction
This proposal seeks community approval to reduce the allowed active validator set parameter on the Regen Network blockchain from 75 to 21 validators.
This proposal seeks community approval to reduce the allowed active validator set parameter on the Regen Network blockchain from 75 to 21 validators.
@alphaBiota can you share anything re: your ideas for the support group formation?
I can’t answer your question, but personally I would just like to see more engagement from validators within the community and use this “participation” as at least one of the metrics. I know that many of our validators are not providing additional services relating to other aspects of the network that engage various aspects of the community (ecocredit development, marketing, software development, etc) and that is OK. But there should still be ways for them to engage - maybe regular monthly calls to gather the validators and invite external community? Share things that validators are learning from other communities, coordinate relayers, full nodes, snapshots, etc? @KingSuper are there any ways you would engage more in the Regen community?
In January 2024, Jeancarlo Barrios, Juan Carlos Ramos, Juan Fernando Ramos, and Brian Weinberg initiated “The Road to $1,” a study to assess and enhance the Regen Network’s value and traction. This initiative aims to tackle critical challenges such as decentralization issues, leadership gaps during transitions, inadequate public metrics, and fragmented strategic directions, which have been topics of discussion in the Tokenomics Working Group forum since late 2023. To address these challenges in line with the Regen Network’s ethos, we propose the formation of a Regen Network Council. This council will play a crucial role in improving network governance, operational efficiency, and strategic growth. The first and primary focus of the council will be to develop a constitution that ensures effective management of the network and leverages public goods to support regenerative development across communities governed by token holders.
Guidelines and recommendations over initial first steps, including the creation of a Council Proposal
Hey @Jeancarlo Barrios wanted to follow up and check for your ideas on how to move forward with it. If any help needed – please let me know.
Question: is what we are talking about more of a Secretariat? “1. a. an office responsible for the secretarial, clerical, and administrative affairs of a legislative body, executive council, or international organization.”
Other synonyms are: agency bureau department ministry administrative agency administrative department administrative office government department government office
Hi Regen community,
My name is James from ecoToken. We have been in discussions with RND and the Regen Foundation regarding a proposal to enhance the utility of REGEN tokens and enable Regen ecocredits to permeate through the web3 ecosystem via ecoToken’s cross-chain communication protocol.
Hi Christian - I’m not sure I agree about token lock up. The proposed allocation of 5% was largely surfaced by RND as an alignment tool to support long term investment and building on Regen Ledger. With proper gating for milestones met, I’m personally comfortable with unlocked tokens. Sourcing the tokens for this agreement still needs to be sorted.
Hi Will - all good questions. Re: Cash budget - ideally RND and ecoToken work together to design and coordinate a fundraising campaign to bring in the fiat required for execution. We appreciate ecoToken’s early estimation of price required to execute to help bring clarity to all of us of the resources required for this ambitious partnership.
This is a post to initiate conversation on the consensus changes, based on our conversations with Aaron Craelius, Will Szal and the $regen tokenomics group
A interesting reply from conversations going on at EVMOS about a move to Cosmos ICS: https://commonwealth.im/evmos/discussion/23787-evmos-road-to-ics?comment=87197
Here is an overview of the option of a complete migration from regen ledger, and the golang module approach of building on the cosmos SDK, to EVM (should be a similar amount of time and effort to port into the solana virtual machine as well). I am not advocating this, but was curious and think that MORE INFORMATION IS BETTER to evaluate different options at this juncture.
This was generated by chatgpt, using GPT 4o
Translating Cosmos SDK modules (ecocredit, group, gov, data) from Golang to Solidity for EVM smart contracts and integrating them as an “smart contract embassy” with linkage back to Regen Ledger using a bridge service (Gravity Bridge, Axelar, etc.).
Two Engineers:
Three Engineers:
These estimates can vary based on the complexity and proficiency of the engineers. Adjustments might be necessary as the project progresses.
Greetings Regen Network community.
As Regen Network grows, so does the importance of steady, vibrant and agile governance. LOA Labs validator team started a community discussion about this topic here on Commonwealth. As promised, we have attempted to distill some of the community comments and added some of our own suggestions on how to better codify best governance processes. We want to draw special attention to the section dealing with community spends and the idea of using the Groups module to better calibrate evaluation and community fund delivery for approved community spends. All ideas and upgrades welcome. We will plan on hosting a Twitter space on this topic in July.
I was impressed by Thomas et al’s proposal for community funds to build a climate regen wiki. Discussion at https://forum.regen.network/discussion/5164-climate-wiki-discussion-poll-for-community-pool-funding-proposal
The wiki concept sounds super useful, organizing information amongst regen groups, across bioregions or applications is a big challenge per status quo. My hope was that the wiki would help solve this, bring value to Regen community & be a tool that our team could use internally & to collab. I was also proud of Thomas in leading the way, suggesting to the community that we can build and asking for funds, resources & a mandate to do so. But… how has this played out?
I am starting a thread here to document my journey creating a credit class on the testnet as a non-technical user. My aim to to provide insights that can upgrade the ReGenie Corpus , docs.regen.network , and serve to provide insights for the teams building interfaces for users, as well as show what is already possible for a non technical user for developing and originating ecocredits using the Regen Network tech stack.
The UI for the Redwood Testnet can be found at dev.app.regen.network
Overview
This signaling proposal will add the kilo-sheep-hour as a new credit type to the list of approved credit types. This credit type functions to serve the Grazing in Vineyard Systems Methodology and Credit Class, which is designed to support the use of high-density, short-duration rotational targeted sheep grazing in vineyard systems to improve ecosystem functioning through active management of the soil and herbaceous cover in the vineyard understory.
Regen Foundation is opening a Request For Proposals (“RFP) to the Regen validator community (or anyone wanting to launch a new validator on Regen) to work with the Foundation to upgrade its Community Staking DAO Allocation Delegation Program. If you’re not familiar with this program and the discussion around its upgrade, you can read more about that in this thread.
Requirements
Are you needing to express the Value of the Benefits your project provides? Or do you have a ecosystem/site/project you want to permanently protect?
Based on the work we are doing with RealValue (link to regen forum post) we have the basis for what we call Ecological Ensurance .
I am cross posting to the environmental stewardship framework which creates a short term (per annum) action and monitoring based contract and results based credit/payment agreement foundation that may or may not be able to link to quantification and assignment of downstream future value (or present value being stewarded): https://www.hylo.com/groups/regen-methodology-development/post/72269
Just noting that I am following and very interested. I am wondering if you have a demo yet of how you are building this out?
We are all excited! And of course a bit bummed you chose to build all this out on an EVM.
I had the opportunity to hold a quick workshop on Open Crediting at the REGENERATION event on March 2nd at EthDenver. Just wanted to create a quick forum post to share my slide deck. I will try and update these slides with links to relevant Regen Ledger documentation. Special thanks to @ryanchristo | Chora for a quick review and offering suggestions the morning of. Please reach out if you have any input, suggestions or feedback!
https://docs.google.com/presentation/d/1FnuXOvEvJ46v1-La1mYCps7YilJNAMpB4vouxjYvXhU/edit?usp=sharing
Tavis Digital will shift away from the validator business due to regulatory uncertainty. We will shut down operations of all our validator nodes on December 1st, 2023, and kindly ask you to redelegate by then. Tavis Digital has been a keen supporter of the Regen Network from the very beginning, and we will continue to support the project as an asset management company.
I am writing to propose an adjustment to the slashing window for validators in order to provide a more reasonable timeframe for validators to recover from periods of downtime. Currently, the minimum block signing requirement is set at 500 blocks per 10,000 blocks, resulting in a maximum downtime of approximately 50 minutes. I suggest increasing this slashing window to 5,000 blocks per 10,000 blocks, allowing validators just over 8 hours (approximately 8 hours and 19 minutes) to resume their operations without being penalized.
There are several reasons why a validator may experience downtime exceeding the current 50-minute limit. These reasons include:
maxMissed
, which is SignedBlocksWindow - (MinSignedPerWindow * SignedBlocksWindow)
" and when you increase the MinSignedPerWindow (as you suggest), the maxMissed value goes down.
GM Regen Team
Zach from Common here. As we head into Q2, I wanted to share what we’ve been working on & hopefully get your feedback on Common so we can ensure that you’re getting the most out of your experience.
Hi @ballzach I continue to have various issues trying to do simple things on the Regen forum. I’ve tried to configure email notifications for the past couple years and has never worked. Trying to add my email today I get an error “unable to update email”. For many months Common did not work in my Brave browser, I could not scroll or navigate past the top page of any forum post. I could open the forum in Chromium but I did not have my wallet configured so could not participate in the forum. I’ve submitted feedback/help requests for these things and never received a response.
I generally experience issues or unexpected behavior whenever I click on navigation items (categories, post titles, user names) and find the behavior inconsistent. Sometimes there is a partial reload, other times a full reload. If something fails to load the loading indicator/state can get stuck and leave you without anything to click on.
My general understanding/assumption is that much of the Common app navigation/etc is reliant on some kind client side JS framework for buttons and navigation rather than simple, standard HTML links that browsers are designed to use. While not a bug, another inconvenience from this is that you cannot right-click to “Copy link” for any of these navigation items. Instead, you need to navigate and copy from the URL bar or use Share -> Copy Link (which doesn’t indicate success once copied).
Hi everyone,
As briefly mentioned in Regen Ledger v5.0 Upgrade Proposal , the latest version of Regen Ledger does not support the experimental build option and therefore Hambach Testnet has continued running Regen Ledger v4.0 with the experimental build. After further consideration, the RND team has decided to shut down its validator node on February 15th , which will effectively shut down Hambach Testnet. The reasons for shutting down Hambach Testnet are as follows:
Follow the Regen Network Community Event Calendar on Google:
At about 44:44 on Green Pill - Proof of Regeneration episode, Gregory and Kevin discuss a Global Index / Proof of Regeneration Global Reserve Currency. One must assume this will be $REGEN. In thinking about this, does Regen have plans to include other assets in it’s treasury… i.e. other crypto, DAO tokens, real world assets etc? Would love to hear more on this index approach. I could personally see Community Funding and Ecosystem Fund projects in the index by default.
(sidenote would love to see a “Tokenomics or Treasury” thread category)
Please add me to the group