# Welcome Welcome to the Regen Network Guidebook! This guide is meant to be a Regen Network 101 text, providing foundational knowledge for all wishing to join the Regen Network community.
# Regen App (Project Developers & Land Stewards) **Are you a project developer or land steward focused on carbon sequestration, biodiversity, and environmental health?** \ The Regen App and web platform provide powerful tools to communicate your project's data-rich information directly to buyers and stakeholders. By harnessing blockchain technology, The Regen App offer enhanced transparency and auditability when sharing project data. These features are especially valuable when issuing credits through Regen Network, but they also serve as a robust platform for showcasing your project and sharing critical data with your audience. # Logging In {% hint style="info" %} *A profile allows you to introduce yourself to the network and manage your projects so others can follow your work.* {% endhint %} ### Log In from the upper right corner of the Regen page
* You will be prompted to choose between two log-in methods:
### Email or Social Log In {% hint style="info" %} [*An email or social-based login is a good introduction to the network if you want to create and promote your projects, and potentially sell carbon or ecosystem service credits in the future.* ](#user-content-fn-1)[^1] {% endhint %} * You can make an account using Google account (gmail) or an email. In either case, you do not need a password. * If you choose to use an email, a code will be sent to that account. The code will be different each time you login, and will give you access to your profile page and account. * If you choose to use Google, Google may send you a verification code, but generally you should be brought straight to your profile page. You are now logged in! {% hint style="info" %} *You can move forward and set up your profile page to best represent you and your projects.* {% endhint %} ### Keplr Login in In order to do on-chain actions such as creating organizations, registering projects, and issuing credits, you'll need to log in with a Keplr wallet. [Learn more about wallets here](/guides/wallets/wallet-setup). [^1]: # Profile Customization {% hint style="info" %} *Your profile acts as a home page for you to start telling your story. Your friends, followers, customers and other Regen users will be able to see the projects that you are managing and get a sense of who you are.* {% endhint %} ### Navigate to Your Profile
* Click on your profile in the top right corner of the app. * The page below will open.
### Edit Profile * Click the "Edit Profile" button framed in green above. The page below will open.
* Here you can update profile details (shown in the image below), including:
NameBackground ImageWebsite Link
Profile ImageDescriptionSocial Media Link
Click "save" at the bottom of the page to save your updates. # Creating Projects {% hint style="info" %} *Creating a project page and adding information about your projects allows your audience to get a sense of what exactly you do.* {% endhint %} The steps below will help you create a project page like [this](https://dev.app.regen.network/project/f7a68a04-f11e-11ee-9739-0267c2be097b):

https://dev.app.regen.network/project/f7a68a04-f11e-11ee-9739-0267c2be097b

{% hint style="info" %} *Having the following materials prepped can help streamline this process:* * A short **summary** or "elevator pitch" of your project (about 100 - 200 words). * A longer **story** about who you are and the work you do (about 300 - 500 words). * A gallery of good-quality **photos** saved as *jpeg* or *png*. * A **video** (optional) with an embeddable *url*. {% endhint %} ### 1. Create a New Project * From your [profile page](/guides/regen-app-project-developers-and-land-stewards/profile-customization), under projects, click "+ Create Project." If you aren't [logged in](/guides/regen-app-project-developers-and-land-stewards/logging-in), you'll have to do this first.
* This will bring you to the page below:
### 2. Add Project Name and Size * You'll be prompted to add the project name and size. {% hint style="info" %} *In the finished example below, the project name is "BelleVue Farm" and it sits on 25 acres.* {% endhint %}
* Proceed to the next step by clicking "save and next." ### 2. Add a Location * Add the approximate location of your project. {% hint style="info" %} *For Bellevue Farm, the location is Saint-Lazare, Quebec, Canada. The map on the top right of the finished project page auto-populates based on the location you select.* {% endhint %}
* Proceed to the next step. ### 2. Add a Short Summary * Add a brief project summary. This should say what you are doing and how it benefits the environment. {% hint style="info" %} *This is a first pitch, so you'll want it to be concise and compelling.* {% endhint %}
### 3. Add a Longer Project Story * The Project Story gives those who are already interested more information about who you are and why they should be invested in your work. Readers will have to scroll down on your project's page to read this story. * Add a catchy title for the story to encourage people to read it.
* Proceed to the next step. ### 4. Add Media * The main photo is shown at the top of the finished project page, next to the map. * The gallery photos are added in between the Summary and Story. Viewers can move through them. {% hint style="info" %} *Be sure to choose high-quality images so that they are engaging and crisp for viewers.* {% endhint %} ### 7. Review and Publish * Review your project information and media, and then save! Your project is now publicly visible in association with your Regen profile. Your profile page should now include a card for the project you added.
{% hint style="info" %} *Made a mistake or something about your project changed? Don't worry, you can go back and edit it anytime. Just click "Edit Project" on the project card under your profile.* {% endhint %} # Registering a Project Terrasos type content here Only accessible to credit class issuers, you'll have select a credit class Registered project is on chain Regen team is doing this part for now, but to understand the metadata, where each piece goes on project page # Using Regen Data Stream With Regen Data Stream, you can upload data, provide updates, and anchor your information to the blockchain for full transparency and accountability {% hint style="info" %} Creating a Data Stream allows you to post dataprojects allows your audience to get a sense of how your project is progressing over time. {% endhint %} The steps below will help you create a Data Stream like this:
{% hint style="info" %} Having the following materials prepped can help streamline this process: * The pieces of data you intend to post (photos, reports, documents, .csv) * Descriptions of these posts (optional) * Captions for photos (optional) * Locations for each post and data entry (optional) {% endhint %} ## 1. Go to 'Projects' from your profile page dashboard * Identify the project you want to create a data post on
## 2. Create a Data Post * On the project you wish to create a data post for, click 'Create Post'
* This will open a pop-up window to create the data post
## 3. Add Title and Comment * Add a title that will summarize your post (110 characters) * Add a comment of any length: this could be a blog-style project update or a description of all the data that will be included on this post ## 4. Upload Files * Drag and drop or select 'Add Files' to select files from your computer * Select one file or multiple files at once * Supported file types include pdfs, documents, csv, photos, video, json and more. See more on supported file types [here](https://buf.build/regen/regen-ledger/file/main:regen/data/v1/types.proto#L64)
## 5. Select Privacy Settings * Choose from 4 privacy options for your post * Each option includes a tooltip to explain what each entails
## 6. Save Draft or Publish * You can save the post as a draft and return to it from the Data Stream page * When the post is complete, you can publish the post. * Note that posts are anchored on the blockchain and are not editable once published. They can be deleted from the data stream and remade, but will still remain on the blockchain.
## 7. Attach a Signature (Optional) * Once you hit 'Publish,' a pop-up will appear asking if you want to attach a digital signature. * If you do not wish to sign the post, click 'Skip this step.' * To utilize the signing feature, you will click to verify that the data is accurate. * To sign the post, you will need to login with your Keplr Blockchain wallet. Digital signatures are not available with an email-based login. * Once you hit 'Sign' you will be prompted to login to Keplr or, if you're already logged in, to hit 'Approve' in the Keplr pop-up.

You must be logged in with your Keplr Blockchain wallet to see this popup and attach a signature.

## 8. Successful Data Post Creation * From the 'Congrats! You successufly created this post' pop-up, you can click 'View Post' to see the post you just made. * You can also click to view the project or click to view the Blockchain record.
## 9. View the Data Post * From the data post page, you can view the data files on the map and in a list to the right side of the map. * You can scroll to see the description and the timeline, which would include signatures if you opted to digitally sign.
## 10. View the Data Stream * From the data post, you can click 'All Posts,' to view the Data Stream. You will see your data post in the Data Stream on your project page. * Depending on the type of privacy you selected for the data post, you will see tags that say 'Files are private,' 'Post is private,' or 'Locations are private.' * Scroll down to see more data posts. Select 'See more' if you would like to see more posts. * From the Data Stream you can see the data post title, the creator, the date of creation, the first line of the comment, an image of the file, the privacy tag and the Action button to share
## 11. Actions on a Data Post * On the data post, if you select 'Actions' , you will have the following options depending on the privacy settings you selected. * If you selected for the post to be public, you will have the option to 'Share the public link' or 'Delete.' * If you selected one of the three possible privacy settings, you will have the following options: * 'Share the public link,' which will preserve the privacy you selected when someone uses the link. * 'Share the secret link,' means that if you share this link, someone can access the post without any privacy settings (ie: you could share the secret link to a verifier only so they can access all the files but no one else could access it) * 'Delete'
## 12. To Create More Data Posts * You can hit 'Create Post' from the top of the Data Stream, the footer of the project page and from the project dashboard. * You can edit drafts data posts from the Data Stream. # Issuing Credits The Regen App offers two pathways for project developers to issue credits, both securely managed on the Regen Network blockchain: 1. **Enrolling in an existing Credit Protocol registered through Regen Registry**\ If you are looking to register your project in an existing Credit Protocol, see the [Project Development Overview](https://registry.regen.network/v/regen-registry-handbook/project-development/project-development-overview) section of the Regen Registry Handbook. 2. **Deploy your own Credit Protocol on the Regen App** {% tabs %} {% tab title="Submit through Regen Registry Program" %} This pathway is ideal for those seeking a formalized crediting process. It involves a community-driven peer review of methodologies and protocols, led by the Regen Registry team. Regen Registry's in-house experts will then provide direct assistance to set up issuance processes, 3rd party verification requirements, and governance procedures within the Regen App. This approach adds trust and credibility, particularly valued by buyers seeking verified credits. {% endtab %} {% tab title="Self-Service Issuance" %} This self-service pathway allows project developers or methodology creators to manage credit issuance independently by following [Regen Network's API guidelines and standards](#user-content-fn-1)[^1]. It's best suited for those with an established buyer network and technical capacity who wish to leverage the Regen App's tools without needing formal registry oversight. {% endtab %} {% endtabs %} #### Choosing the Right Pathway If your project requires a trusted, third-party verified process to reassure buyers, the **Regen Registry Program** pathway is the optimal choice, whether you are designing your own Credit Protocol, or enrolling in an existing protocol under the Regen Registry. For project developers with their own infrastructure, software team, and buyer network, **Self-service Credit Issuance** offers the flexibility to manage the process autonomously, using the technical tools provided by the Regen App. Reach out to to enroll in an existing [Credit Protocol](https://registry.regen.network/v/regen-registry-credit-classes) [Submit a methodology for approval under the Regen Registry Program](https://registry.regen.network/v/regen-registry-handbook/methodology-development/submitting-a-methodology) [Get started with self-service credit issuance](/guides/regen-app-project-developers-and-land-stewards/self-service-credit-issuance) [^1]: Mention the app, and how we can use the app here # Self-Service Credit Issuance Regen App provides a self-service option for project developers and methodology creators who want full control over the credit issuance process. This pathway allows you to directly manage and issue credits using Regen Network’s API and data standards. It’s designed for those who already have a buyer network and technical resources, enabling you to leverage the Regen App’s technical tools without needing to engage in formally enrolling with Regen Registry. This approach offers maximum flexibility for developers who prefer an independent crediting process. Here’s a closer look at how it works: ### **Overview of Credit Protocols** Every credit issued on Regen Network starts with the creation of a Credit Protocol, referred to on-chain in our API docs as a Credit Class. Each Credit Protocol is represented by the following properties: * **Credit Type:** Defines the unit or category the credit represents (e.g., carbon, biodiversity). If a new type is needed, a network-wide governance process is required to add it. * **Metadata:** Represents a set of descriptive information related to the Credit Protocol. * **Issuer List:** A set of Regen addresses authorized to issue credits under this protocol. * **Admin Address:** The Regen address of the user that can update metadata and the issuers list. ### **Selecting a Credit Type** Current credit types available on Regen Network can be queried directly through the Regen command-line interface (see details [here](https://docs.regen.network/tutorials/user/credit-class-project-batch-management.html#allowlist-type-and-fee)). If your Credit Protocol fits under a pre-existing credit type, then you can proceed below to setting up your own Credit Class on-chain. Otherwise, you'll need to first [initiate an on-chain governance proposal for adding a new credit type.](https://docs.regen.network/tutorials/user/message-based-governance-proposals.html#add-credit-type) ### **Setting Up a Credit Protocol on-chain** To create a new Credit Protocol on Regen Network, you'll need to use the Regen command-line interface, following our [Credit Class, Project and Batch Management technical tutorial](https://docs.regen.network/tutorials/user/credit-class-project-batch-management.html). It is recommended to read the above tutorial in full, as it provides all of the technical details necessary for understanding how to technically manage a Credit Protocol through the CLI, in addition to how to setup projects and issue credit batches through Regen Network's APIs. Anyone can create a Credit Protocol on-chain by paying a creation fee of 5000 REGEN. While the above tutorial also walks through setting up projects and issuing batches through the CLI, these features can also be done directly by logging in to Regen App with a wallet associated with one of the credit class's issuer addresses. ### **Visibility on the Marketplace** Credit Protocols created through the above method will automatically appear on the [Regen Marketplace](http://app.regen.network/), assuming they adhere to the JSON-LD template outlined in the [credit class creation tutorial](https://docs.regen.network/tutorials/user/credit-class-project-batch-management.html#json-ld). Projects and credit batches created under these protocols will also be visible as soon as they are created (whether through the CLI or the web-based user interfaces on Regen App), showcasing your data-rich information to potential buyers and stakeholders. ### **Managing Projects and Batches** Issuers of a Credit Protocol can easily create projects and issue credit batches through the Regen Marketplace UI. Simply log in with the Keplr wallet tied to your issuer address, and when you create a project you will be presented with an option to create a project registered with your Credit Protocol.
{% hint style="info" %} Connecting a pre-existing (off-chain) project with your crediting protocol is currently not supported directly through the Regen App.\ \ Please reach out to and someone from our team will help migrate your project to instantiate it on-chain on Regen Network and register it with your crediting protocol. {% endhint %} # Organizations Organizations in the Regen App make it easy for teams, companies, and institutions to collaborate on ecological projects under a shared identity. An **organization** represents your group on the Regen Network — a collective account that can create and manage projects, hold and distribute ecological credits, and coordinate contributions from multiple members. Through **role-based permissions**, organizations enable transparent and secure teamwork. You can invite members, assign specific roles, and control who can view, edit, or manage each part of your organization’s work. Members can also collaborate on individual projects, where roles can be tailored further to match specific responsibilities. Behind the scenes, each organization is backed by an on-chain governance structure (a DAO powered by [DAO DAO](https://daodao.zone/)), which ensures that ownership, permissions, and transactions are managed securely and transparently. The Regen App provides a simple interface so you can handle everyday operations without needing to understand the technical details. *** #### Learn More * [**Create an Organization**](/guides/regen-app-project-developers-and-land-stewards/organizations/create-an-organization) — Set up a new organization and profile to represent your team. * [**Manage Organization Members**](/guides/regen-app-project-developers-and-land-stewards/organizations/manage-organization-members) — Add, remove, or update team members and their roles. * [**Manage Project-Specific Collaborators**](/guides/regen-app-project-developers-and-land-stewards/organizations/manage-project-collaborators) — Control who can access and contribute to individual projects. # Create an Organization ## How to create an organization You are limited to one organization per user account at this time.
#### 1. Start the Creation Process * Go to your **user dropdown** in the **top right** of the app and click **“Create New Organization.”** * Alternatively, you can start from the **user dashboard** (top left) by selecting **“Create a New Organization.”** > **Note:** You must be logged in with [**Keplr**](/guides/wallets/wallet-setup/create-a-keplr-wallet) and have at least **100 $REGEN**. This amount covers gas fees and funds your organization’s DAO so it can pay gas fees for members. ***
#### 2. Set Up Your Organization Profile Fill in your organization details: * Name * Logo * Background Image * Description * Links * (Optional) Transfer your personal profile data — name, logo, background image, description, and links — to your organization profile. ***
#### 3. (Optional) Migrate Existing Projects If you already have projects linked to your user profile: * You’ll be asked if you’d like to migrate them (including tradable credits and active sell orders managed by you). * Select which projects (and respective credits/seller orders) you want to move. ***
#### 4. (Optional) Provide Your Contact Info If you haven’t already: * Add your **name** and **email address**. * The **email** is used for notifications. * The **name** helps organization members identify who is performing actions. ***
#### 5. Invite Members & Assign Roles Invite members and assign roles. As the creator, you are automatically the **Owner**, but you can transfer ownership later. **Roles:** * **Admin:** Full control of users, projects, credits, and credit classes. (Must have a Keplr address and REGEN address) * **Editor:** Full control of projects and credit classes, but cannot manage users or credits. (Must have a Keplr address and REGEN address) * **Viewer:** Can view all data posts across all projects, including private data posts. ***
#### 6. Fund Your Organization Before completing setup, **send 100 $REGEN** to your organization account.\ This covers gas fees for your members so they can perform actions without needing their own REGEN. Learn how to acquire $REGEN [here](/guides/wallets/wallet-setup/acquire-usdregen). *** #### 7. Organization Setup Complete 🎉 Congratulations — your organization is now live! You now have: * An **organization profile** that represents your team or institution on Regen Network. * An **organization dashboard** where you can manage your members, projects, and ecological credits in one place. From here, you can begin adding new projects, inviting collaborators, and managing your organization’s activity directly from your dashboard. Welcome to the next stage of your journey in regenerating Earth’s ecosystems — together, as an organization. 🌍 # Manage Organization Members ## Overview Organizations in the Regen App make it easy for teams, companies, and institutions to work together on ecological projects. Each organization provides shared access to projects, credits, and resources through **role-based permissions**, allowing you to assign exactly who can view, edit, or manage each part of your organization’s work. Behind the scenes, every organization is backed by a **DAO (Decentralized Autonomous Organization)** using **DAO DAO** smart contracts. This structure provides secure, transparent control of on-chain assets and permissions — but you don’t need to understand the blockchain details to use it. The Regen App provides a simple interface for adding members, assigning roles, and managing access. *** ### 1. Understanding Organization Roles Each member of an organization is assigned a **role** that defines what they can do across the organization and its associated projects. All roles, except **Viewer**, require a **Keplr wallet** and a **Regen address** so they can perform on-chain actions.
RoleGeneral Description
OwnerThe creator and ultimate controller of the organization. Cannot be removed except by transferring ownership.
AdminManages team members, funds, and projects. Shares most permissions with the Owner but can be removed by the Owner or other Admins.
EditorCan edit organization content and projects but cannot manage members or funds.
ViewerHas read-only access to the organization and its projects. No wallet required unless permissions are upgraded.
*** ### 2. Role Details and Permissions #### **Owner** * Has full administrative control of the organization. * Can **add, edit, and remove members**, **manage credits**, and **edit projects**. * Controls organization-level actions such as: * Creating or updating credit classes. * Managing the organization’s credit portfolio (send, retire, sell). * Managing project creation and metadata. * **Cannot be removed** from the organization unless they transfer ownership to another member. * Automatically has access to all projects under the organization. #### **Admin** * Has nearly the same permissions as the Owner but **can be removed or modified** by the Owner or other Admins. * Can: * Manage team members and their roles. * Create and manage projects. * Manage credits, credit classes, and sell orders. * Edit organizational profile information. * By default, Admins have access to **all projects within the organization**, though this can be restricted at the project level. #### **Editor** * Focused on project and content management rather than administration. * Can: * Edit the organization’s profile (name, description, logo, etc.). * Edit project content where they have project-level edit rights. * Cannot manage members, funds, or credits. * Editors automatically gain access to all projects by default but can have that access **revoked or restricted** by Admins or the Owner. #### **Viewer** * Read-only role for people who need visibility but not control. * Can: * View all organization projects and the credit portfolio. * See project and credit details, including private information where permitted. * **Does not require a wallet address** until upgraded to a higher role. * Useful for external partners, clients, or buyers who need to review data but not participate in management. {% hint style="info" %} Please note, by default project credits are issued to the Organization's account. If you want to have Admins who are not part of the Organization manage the project credits, you will need to manually send the credits to the project account. {% endhint %} *** ### 3. Default Access and Inheritance When you add someone to your organization, their role determines their **default access** to all projects. * **Owners, Admins, and Editors** automatically have access to every project associated with the organization. * **Viewers** do **not** automatically receive project access — they must be added explicitly if needed. * Admins and Editors can have their access **revoked** from specific projects to limit their visibility or editing rights. If an Admin or Editor adds a new member, that new member inherits project permissions **only for the projects the adding Admin has rights to**. This ensures that access cannot be granted to projects an Admin doesn’t control. *** 4\. Adding Members to the Organization 1. Go to your **Organization Dashboard** in the Regen App. 2. Open the **Members** tab. 3. Click **Add Member**. 4. Enter the member’s **Regen address** (for Owner, Admin, or Editor) or **email address** (for Viewer or non-wallet roles). 5. Choose their **role**. 6. Confirm to send the invitation. If the invitation is by email, the user will receive a link to join and can later connect a wallet if their role is upgraded. All role assignments and invitations are logged within the organization’s DAO and can also be viewed or managed directly through the **DAO DAO app** at [daodao.zone](https://daodao.zone). *** ### 5. Changing or Removing Members #### **Changing Roles** * Owners and Admins can upgrade or downgrade a member’s role. * Changes automatically **cascade** to projects where that Admin has rights. * Project Owners retain their project ownership regardless of organization-level changes. #### **Removing Members** * Owners and Admins can remove members from the organization. * Removal cascades to all projects the removing Admin has rights to. * The **Owner cannot be removed**; ownership must first be transferred. * Admins can only remove members from projects they control — complete removal may require coordination between multiple Admins or the Owner. All member changes are recorded on-chain, ensuring transparent access tracking. *** ### 6. Managing Members Through DAO DAO While the Regen App provides a simplified interface, all member management is ultimately powered by **DAO DAO’s role-based authorization module (RBAM)**.\ Through [daodao.zone](https://daodao.zone), organization members with Admin or Owner roles can: * View and modify all roles and authorizations. * Create or update governance proposals. * Manage on-chain assets, treasuries, and subDAOs. * Execute or delegate on-chain actions directly. This enables more advanced and auditable operations while the Regen App remains user-friendly for everyday tasks. *** ### 7. Best Practices for Role Management * **Limit Admin access** to trusted members who need control of credits, funds, and membership. * **Use Editor roles** for team members who contribute content or manage projects but don’t need admin rights. * **Use Viewer roles** for external stakeholders, buyers, or auditors who need to see private project data. * **Review roles regularly** to maintain security and transparency. *** #### Summary Organization member management in the Regen App provides a clear, flexible structure for collaboration: * Roles define permissions and access across the organization and projects. * Owners, Admins, and Editors have broad access by default, but permissions can be refined. * All changes are transparent and secure, managed through DAO DAO’s on-chain infrastructure but controlled through a familiar, intuitive interface. # Manage Project Collaborators ## Overview Projects associated with an organization are managed using a flexible, on-chain permissions system powered by [**Dao Dao**](https://daodao.zone/). Behind the scenes, each project is organized as a **Project DAO**, which simply means that project roles, permissions, and collaboration are managed transparently and securely on-chain. You don’t need to understand the technical details — just know that this setup allows for clear role management, shared decision-making, and built-in accountability. *** #### 1. Access Your Project 1. Log in with your **Keplr wallet** (you must have a Regen address). 2. Open your **organization dashboard** and select the **project** you want to manage. 3. Go to the **Members** section of the project. *** 2\. Add Collaborators You can add collaborators in two ways, depending on their role: * **For Owners, Admins, or Editors:**\ Enter the member’s **Regen address** (Keplr wallet).\ These roles require an on-chain address because they have higher-level permissions and can perform on-chain transactions on behalf of the project. * **For Authors or Viewers:**\ You can invite them using either a **Regen address** *or* an **email address**.\ Email invitations allow non-technical users or external collaborators (like data contributors or buyers) to join easily. Once you’ve added the collaborator: 1. Assign the appropriate [**role**](#id-3.-project-roles-and-permissions) (see below). 2. Confirm the addition. 3. The member will receive an invitation and gain access based on their role. All role assignments, voting, and governance actions are recorded and can also be managed directly in the [**DAO DAO app**](https://daodao.zone/). ***
#### 3. Project Roles and Permissions **Owner** * Full control of the project and all DAO functions. * Cannot be removed by Admins. * Can manage members, funds, and project settings. **Admin** * Nearly identical to Owner, but **can be removed** by the Owner. * Can manage: * Project funds in the DAO wallet. * Membership and roles. * Project settings and data posts. **Editor** * Can create, edit, and publish project content. * Cannot manage members or funds. **Author** * Can create and edit their own **data posts**. * Can delete or modify their own posts only. * Cannot manage members or make other project changes. * Cannot see the project portfolio, much less manage funds. **Viewer** * Can view **all project data**, including **private data posts**. * Cannot see **draft posts**. * Cannot make edits or manage members. * Ideal for stakeholders (e.g., **buyers or partners**) who need access to view project information securely. {% hint style="info" %} Please note, by default project credits are issued to the Organization's account. If you want to have Admins who are not part of the Organization manage the project credits, you will need to manually send the credits to the project account. {% endhint %} *** #### 4. Best Practices * **Assign Admin or Owner roles carefully**, since these roles control membership and funds. * **Invite non-technical collaborators** (like authors or data reviewers) by **email** for simplicity. * **Use the DAO DAO app** to manage voting, membership changes, and governance proposals. * Ensure all key contributors (Owners, Admins, Editors) have a **Keplr wallet** and **Regen address**. *** #### 5. Managing Members * To **update or remove members**, open the **Members** section of the project or manage them through **DAO DAO**. * Only **Owners** and **Admins** can modify roles or remove members. * All actions are recorded **on-chain**, ensuring transparency and traceability across your project’s history. # What is a DAO? ## What Is a DAO and How Regen Uses It for Better Collaboration A **Decentralized Autonomous Organization (DAO)** is a way for people to organize and make decisions together using blockchain technology. Instead of decisions being made by a single manager or company, a DAO allows a group to **govern themselves transparently and fairly** through digital tools. But while full DAO governance can involve voting and proposals on every action, not every group wants — or needs — to work that way. Many organizations and projects just need a **simple, secure way to manage roles and permissions** on-chain, similar to what they’re used to in standard web apps. That’s where the **Roles-Based Authorization Module (RBAM)** from **DAO DAO** comes in. *** #### How RBAM Makes DAOs Work Like Real Organizations Regen uses the RBAM system to make DAOs **more practical and familiar** for everyday users. With this module, each DAO can define **roles** (like Admin, Member, Viewer) and assign specific **permissions** to those roles — just like traditional team software tools do. For example: * A **Treasurer** might have permission to manage ecocredits and funds as an Organization Admin. * A **Project Lead** might be able to add or remove collaborators as a Project Admin. * A **Buyer or Verifier** might have read-only access. These permissions are **managed on-chain**, meaning they’re transparent, secure, and verifiable by anyone — but the workflow still feels like what users expect from standard web platforms. This makes it easier for organizations and projects on Regen to transition into decentralized operations without sacrificing usability or efficiency. *** #### Why This Matters for Regen Users Regen Network supports organizations and projects that are working to **regenerate ecosystems and build trust in ecological data**. These efforts often involve **many collaborators** — scientists, land stewards, funders, and community members — each needing specific access and authority levels. Using RBAM: * Organizations can **define clear permissions** for their team members. * Projects can **manage collaborators securely** without requiring every action to go through a full DAO vote. * All actions are still **recorded on-chain**, ensuring transparency and auditability. At the same time, DAOs on Regen still have the option to use **advanced governance tools** in [DAO DAO](/guides/cosmos-ecosystem/cosmos-basics/what-is-dao-dao) — such as proposals, voting, and treasury management — whenever broader community decisions are needed. *** #### In Short The Roles-Based Authorization Module helps DAOs in the Regen ecosystem work **like modern, efficient organizations**, while keeping all permissions **transparent, secure, and on-chain**. It blends the best of both worlds — **the flexibility of traditional team tools** with the **trust and openness of Web3 governance**. # Regen Marketplace (Buyers Guides) Are you looking to buy or trade ecocredits? This section provides directions for interacting with Regen and ecocredits. We also introduce Marketplace currencies and step-by-step bridging guides. # Logging In (Buyers) {% hint style="info" %} *Logging-in allows you to manage your portfolio and buy & sell ecocredits.* {% endhint %} ### Log In from the upper right corner of the Regen page
a. You will be prompted to choose between two log-in methods:
### Wallet Log In {% hint style="info" %} *A wallet-based login is best if you plan on trading eco credits immediately, and already have a Keplr Wallet.* {% endhint %} * Click the Keplr Wallet option. This will prompt a Keplr verification popup titled "Prove Ownership". * Click "Approve". * You are now logged in! {% hint style="info" %} *You can move forward and set up your profile page to best represent you and provide details for individual credit retirement certification.* {% endhint %} ### Email or Social Log In {% hint style="info" %} *An email or social-based login is a good introduction to the network if you just want to explore for now. You can link it to a wallet later to start buying and selling credits.* {% endhint %} * You can make an account using Google account (gmail) or an email. In either case, you do not need a password. * If you choose to use an email, a code will be sent to that account. The code will be different each time you login, and will give you access to your profile page and account. * If you choose to use Google, Google may send you a verification code, but generally you should be brought straight to your profile page. * You are now logged in! {% hint style="info" %} *You can move forward and set up your profile page.* {% endhint %} # Profile Customization (Buyers) {% hint style="info" %} *Your profile acts as a home page for you. You can set up your profile page to best represent you, and provide details for individual credit retirement certification.* {% endhint %} ### Navigate to Your Profile
* Click on your profile in the top right corner of the app. * The page below will open.
### Edit Profile * Click the "Edit Profile" button framed in green above. The page below will open.
* Here you can update profile details (shown in the image below), including:
NameBackground ImageWebsite Link
Profile ImageDescriptionSocial Media Link
Click "save" at the bottom of the page to save your updates. # Ecocredits # Buy Ecocredits You can now purchase blockchain-based ecocredits on Regen Marketplace with both credit cards and crypto. {% hint style="info" %} Find step-by-step directions for buying ecocredits with credit card [here](/guides/regen-marketplace-buyers-guides/ecocredits/buy-ecocredits/buy-with-credit-card)! {% endhint %} {% hint style="info" %} Find step-by-step directions for buying ecocredits with crypto [here](/guides/regen-marketplace-buyers-guides/ecocredits/buy-ecocredits/buy-with-crypto)! {% endhint %} # Buy with Credit Card ### **Step 1 - Choose a Project** Select a project you’re interested in and click the **“Buy Ecocredits”** button. > Note: Not all projects offer credits for purchase via credit card. ### **Step 2 - Select the Amount** If purchasing with a credit card, choose either: * The number of ecocredits you’d like to buy * The USD amount you wish to spend Then, click **Next**.
### **Step 3 - Enter Your Customer and Payment Information** * Enter your **name** (this will appear on your retirement certificate and as your account name if you choose to create one). * Provide your **email address** to receive a receipt and access your order details in the future. * Account creation is optional but recommended for easy access to your purchases. * Enter your **credit card details** securely. *(All payment information is processed and stored securely by* [*Stripe*](https://stripe.com/)*, our payment provider.)* * If you already have an account, please log in!
### **Step 4 - Retirement Details** To retire your credits and ensure they are permanently removed from circulation (preventing double-counting), provide: * At minimum, the **country of retirement** * (Optional) A **retirement reason**, such as: * *“On behalf of XYZ Organization”* * *“For my 2025 travel carbon offset”*
### **Step 5 - Completion** Once your purchase is successful, you will: ✅ See your **retirement certificate** on-screen ✅ Receive a **purchase confirmation email** Thank you for contributing to ecological regeneration! 🌱
# Buy with Crypto ### **Step 1 - Choose a Project** Select a project you’d like to support and click the **“Buy Ecocredits”** button. > Note: Not all projects offer credits for purchase via crypto. #### **Requirements** Before proceeding, ensure you have: * A [**Keplr wallet**](/guides/wallets/wallet-setup) * **REGEN tokens** for gas fees * **Tokens on the Regen Chain** in your preferred denomination (e.g., USDC, REGEN, etc.), as different projects list credits for sale in various currencies. ### **Step 2 - Select the "Crypto" Tab** At this stage, you must log in with your [**Keplr wallet**](/guides/wallets/wallet-setup) to continue. ### **Step 3 - Select the Amount** Choose either: * The number of ecocredits you’d like to buy * The amount of crypto you wish to spend and your preferred denomination (i.e. USDC, REGEN, etc) #### **Retirement or Tradable Credits?** Decide whether to: * **Retire credits immediately upon purchase** * **Buy tradable credits** #### **Understanding Pricing & Availability** * The total credits available may come from multiple sell orders, each with different prices. * The UI automatically selects the lowest-priced credits. * If you increase the quantity of credits, the price per credit may adjust, as the final cost is based on an average of all selected sell orders. Once you've made your selection, click **Next**.
### **Step 4 - Enter Your Customer Info** * Enter your **name** (this will appear on your retirement certificate and as your account name). * Provide your **email address** if you’d like to receive a receipt. * You can also link this email to your **Keplr wallet account**, enabling future login to the Regen Marketplace via email.
**Step 5 - Retirement Details (if applicable)** If you are retiring your credits immediately, provide the following: * At minimum, the **country of retirement** * (Optional) A **retirement reason**, such as: * *“On behalf of XYZ Organization”* * *“For my 2025 travel carbon offset”* Otherwise, if purchasing tradable credit you will simply need to agree to the Ecocredit Sales Agreement and terms of service. Click **Purchase Now**.
### **Step 6 - Completion** Once your purchase is successful, you will: ✅ See your **retirement certificate** on-screen (if retiring upon purchase), otherwise you will be redirected to your portfolio to see your tradable credits ✅ Receive a **purchase confirmation email** Thank you for contributing to ecological regeneration! 🌱
# Transfer Ecocredits
### 1. Connect Keplr Wallet a. Select the "Connect Wallet" button in the page menu. ![](/files/3FZJGwMHaL519UCV5sE8) b. If you have not previously connected your wallet, a separate Keplr window will prompt you to approve the connection. ### 2. Navigate to Your Portfolio a. This option will appear when you hover over your Regen wallet address. Click "My Portfolio".
b. The below page will populate. ![](/files/PDZcktx1Ljf6e8i0V2Df) ### 3. Select Ecocredits to Send a. Find the ecocredits you would like to transfer in the "Ecocredits" section of the page. Click the action button to the right of the section. ![ ](https://cdn-images-1.medium.com/max/1600/0*HJyULDnKHN7P5NQd) b. From the options listed, select "Send". This will generate the below pop out window. ![](/files/ErpF5n0DcipwFJ1UPDMy) c. In "Amount tradable" you may input the number of tradable ecocredits you wish to send. The "Send additional retired credits" box will allow you to send any of the tradable credits as a retired credit. Selecting this option will populate additional fields, including an amount of retired credits to send and [standard retirement information](https://guides.regen.network/guides/regen-marketplace-buyers-guides/ecocredits/pages/07OcqVP3shLfKEpjLbDh#4.-retire-tokens).
### 4. Send Ecocredits a. Once you have selected the ecocredits to be sent and filled out the relevant fields, click "SEND" and approve the transaction in the Keplr popup. ![](https://cdn-images-1.medium.com/max/1600/0*knibVEGlLLlKLD5a) b. A waiting will window will populate. When an ecocredit has been successfully sent, the below window will populate.
#### Congratulations! You have now sent ecocredits on Regen Registry!
# Retire Ecocredits
### 1. Connect Keplr Wallet a. Select the "Connect Wallet" button in the page menu. ![](/files/3FZJGwMHaL519UCV5sE8) ### 2. Navigate to Your Portfolio a. This option will appear when you hover over the account button, next to your Regen wallet address. Click "My Portfolio".
b. Your Portfolio will populate and will look similar to the example below.
### 3. Select Ecocredits a. Find the ecocredits you wish to redeem and retire. Click the actions button on the far right hand side of the section. b. From the options provided, select "Retire". The below pop out will appear. *Note: If all credits from this batch have been retired, "Retire" will not be a listed option.*
### 4. Retire Tokens a. First input the number of tokens you would like to retire. The app will display the number of ecocredits you have available to retire. You may also click the MAX button to retire all available ecocredits. b. In the "Retirement Note" field, you can add your own retirement details. This field may be required in certain situations for [credit retirement certification](/guides/regen-marketplace-buyers-guides/ecocredits/retire-ecocredits/retirement-certification). c. Fill out "Location of Retirement" details. This information prevents double counting of ecocredits in different locations. d. Click "RETIRE" and then approve the corresponding Keplr transaction through the separate window it generates. e. A successful retirement of ecocredits will generate the below window.
#### Congrats! You have retired your ecocredits on Regen Registry! Your retired ecocredits will now be available to view from your Portfolio. # Retirement Certification ## Individual/Entity Credit Retirement Credit retirement certification will draw from your user profile information by default. You may still want to include these details in the Retirement Note field to later view in a block explorer, like Mintscan. However, a credit retirement note is not required for in-app certification.
Retired ecocredits can also be viewed from [your portfolio](https://app.regen.network/ecocredits/portfolio) in the [Regen Marketplace app](https://app.regen.network/). You can [customize your user profile on Regen Marketplace](/guides/regen-app-project-developers-and-land-stewards/logging-in) to include your name/organization, a description, and links to your website and Twitter. Images may be added to further customize profile.
## Third Party Credit Retirement In order to retire ecocredits on behalf of a third party, the Retirement Note field must be filled out with the details of that individual or organization. ### Example Third Party Credit Retirement Notes * Offsetting 7% of Regen Networks historical carbon emissions * ecoToken Carbon Neutrality * Retired by Techstars to offset conference travel for staff * Credit Retirement Recognition for the Earth Regenerators Fund (via Vivero) # Sell Ecocredits ## Create Sell Order ### 1. Connect Keplr Wallet a. Select the "Connect Wallet" button in the page menu.
b. If you have not previously connected your wallet, a separate Keplr window will prompt you to approve the connection. ### 2. Navigate to Your Portfolio a. This option will appear when you hover over your Regen wallet address. Click "My Portfolio".
b. The below page will populate. ![](/files/PDZcktx1Ljf6e8i0V2Df) ### 3. Select Ecocredits to Sell a. Click the actions button to the right of the ecocredit batch you wish to sell from. From the menu that appears, select "Sell". *Note that if all the ecocredits from the given credit batch are already retired, this action won’t be available.*
b. The below window will appear.
### 4. Create Sell Order a. Set the price you wish to charge per ecocredit and how many of the available ecocredits you wish to sell. b. By default, "Disable auto-retire" is **not** checked. This means these ecocredits with retire automatically with purchase. Buyers will not have an option to manually retire ecocredits. Check this box to allow your buyers this option. c. Click "Create Sell Order" and approve the corresponding Keplr transaction.
d. Once the transaction has successfully completed, you will see the below message. **Congratulations! You have created your first sell order.**
## Cancel Sell Order ### 1. Navigate to the Trade Page
a. Click the "Trade" tab at the top of the page. ### 2. Select Sell Order to Cancel a. All recent sell orders will appear on the trade page. You may easily find yours as it will have additional options rather than a "Buy" button on the far right of its section.
b. Click actions button to see your additional options and select "Cancel". The below window will appear.
### 3. Cancel Sell Order a. Click the "Yes, Cancel Sell Order" button to start the process. A Keplr transaction window appear. Select your fee and approve the transaction.
b. Once the transaction has successfully completed, you will receive the below message.
# Baskets # Take from Basket This page provides step-by-step directions for redeeming and retiring ecocredit basket tokens through Regen Registry.
### 1. Connect Keplr Wallet a. Select the "Connect Wallet" button in the page menu. ![](/files/3FZJGwMHaL519UCV5sE8) b. Keplr will prompt you to approve the connection with a separate window. Select "Approve". ![](/files/cZwHVO2EfIYiEVUMk1ze) ### 2. Navigate to Your Portfolio a. This option will appear when you hover over your Regen wallet address. Click "My Portfolio".
b. The below page will populate. ![](/files/zbORgQWcY5AdzPC7nBNS) ### 3. Select Basket Tokens a. Find the Basket Tokens you wish to redeem and retire. Click the three dots on the far right hand side of your selected basket. b. From the options provided, select "Take from Basket". The below pop out will appear. ![](/files/HWvX0B9Ktz5eFVNGoGal) ### 4. Take (& Retire) a. **Amount:** First input the number of tokens you would like to redeem and retire. b. **Retire:** For some baskets, the "retire credits upon transfer" will be pre-checked, in which case you will need to fill in retirement information. In the "Transaction note" section, you may add an optional memo to be attached to the transaction, such as the company that the ecocredits are being retired on behalf of, for example. Fill out "Location of Retirement" details. This information prevents double counting of ecocredits in different locations. c. Click "TAKE FROM BASKET" and then approve the corresponding Keplr transaction through the separate window it generates. #### Congrats! You have taken your first ecocredits from a basket! # Put in Basket This article walks you through putting your ecocredits into an existing basket on Regen Registry.
### 1. Connect Keplr Wallet a. Select the "Connect Wallet" button in the page menu. ![](/files/3FZJGwMHaL519UCV5sE8) b. If you have not previously connected your wallet, a separate Keplr window will prompt you to approve the connection. ### 2. Navigate to Your Portfolio a. This option will appear when you hover over your Regen wallet address. Click "My Portfolio".
b. The below page will populate. ![](/files/PDZcktx1Ljf6e8i0V2Df) ### 3. Select Credits to Add to Basket a. Find the ecocredits you would like to add to a basket and click the three dots option on the far right of the listing. ![](https://cdn-images-1.medium.com/max/1600/0*Pu89Xav1Xi2FaUzd) b. From the options listed, select "Put in basket". This will generate the below pop out window. ![](/files/VPWk6oFO6SnaPhmuumwo) ### 4. Add Credits to Basket a. The "Choose basket" section of the window will contain a drop box of baskets. Select the one you would like to add your ecocredits to. b. For "Amount" input the amount of tokens you would like to add. c. Click "PUT IN BASKET" and approve the Keplr transaction that populates. #### Congratulations! You have added ecocredits to a basket on Regen Registry! # Bridging # Polygon to Regen Ledger Step-by-step guide for bridging tokens from Polygon to Regen Ledger with the Toucan app.
### 1. Connect Wallet a. Navigate to the [Cross-Chain page of the Toucan App](https://app.toucan.earth/overview?chainId=) and connect the Metamask, WalletConnect, or Coinbase Wallet containing the tokens you wish to bridge.
### 2. Fill out Transaction Details a. The Cross-Chain bridge will default to Polygon for the originating chain, but you will need to select Regen Network from the receiving chain drop list indicated with the red box below.
b. Next select the token you wish to bridge from the drop list indicated above in yellow.
c. Tokens which can be bridged will display at the top. Tokens which cannot be bridged will be displayed as semi-transparent at the bottom. d. Next, enter the number of tokens you wish to bridge. Your available token balance will display directly below the input option.
e. Finally, add the [Regen wallet address](/guides/wallets/wallet-setup/create-a-keplr-wallet) you wish to send the tokens to in the Recipient field, indicated with the yellow box above. ### 3. Bridge Tokens a. Once your transaction details have been accurately filled out, click the "Bridge TCO2 to Regen Network" button.
b. This will initiate the transfer and display the above left pop out window. The success message on the right will display if the transaction has been started successfully. c. Next click View Transaction or navigate to the [Transactions](https://app.toucan.earth/cross-chain?chainId=#transactions) tab of the Cross-Chain Bridge page. Here you can monitor your token transfer.
d. Transactions will display most recent first. Status is displayed on the far right (Processing, Successful, Failed). *Note: Bridging from Polygon to Regen Ledger can take up to 30 minutes to complete, depending on bridge traffic.* **Congrats!! You have now bridged tokens from Polygon to Regen Ledger!** # Regen Ledger to Polygon
### 1. Connect Keplr Wallet a. Select the "Connect Wallet" button in the page menu. ![](/files/3FZJGwMHaL519UCV5sE8) b. If you have not previously connected your wallet, a separate Keplr window will prompt you to approve the connection. ### 2. Access Bridge Service a. Hover over or click your wallet address in the top right of the app. From the window that appears, select Bridge.
b. The below page will populate.
### 3. Bridge Ecocredits a. Click the "Bridge" Action button to the right of the ecocredit batch you want to bridge from. The below window will populate.
b. Fill out the necessary details and agree to the [Ecocredit Sales Agreement and terms of service](https://regennetwork.notion.site/Regen-Marketplace-Contracts-7bc2b0075ee64c1a957463bb5eddcead). *Note: For Recipient you will need a valid Polygon address. We recommend bridging a small amount to confirm ecocredits arrive as expected, before bridging your full amount.* c. Click Bridge and approve the corresponding Keplr window. ### 4. Monitor Bridge a. Once the Keplr transaction has completed, you will receive the below success window.
b. From this window you can select the View Pending Bridged Credits button located below bridge details. This will redirect you to the Bridged Credits tab from the bridge service page.
c. Recently bridged ecocredits will likely display with a Pending status, as in the image above. d. Once your bridge has been completed the status will change to Complete. A link to the Polygon transaction for the bridged ecocredits will appear in the Note/Link section of the Bridged ecocredits table. #### Congrats! You have bridged ecocredits from Regen Ledger to Polygon! # Currencies # Basics A quick guide to relevant cryptocurrency basics, including exchanges, wallets and fees ## Exchanges If you are new to cryptocurrency, finding where to start can be overwhelming. Regarding cryptocurrency exchanges, you will often hear two terms tossed about, *centralized* and *decentralized*. There is much more nuance in the differences between these exchange types than this guide will go into. However, this guide will provide a contextual introduction to the topic as well as a jumping off point for acquiring the currency you will need to purchase ecocredits from the Regen Marketplace. ### Centralized Exchanges In order to purchase a cryptocurrency, you will need to use an exchange with fiat onboarding, meaning currency can be purchased with a bank account, debit or credit card. Centralized exchanges are well suited for this purpose. A centralized exchange is owned by a single entity, including all liquidity for trading pairs/pools, which are the mechanism that allow users to swap currencies in both centralized and decentralized exchanges. Because all assets are owned by the same individual or company, they are enabled to sell new users cryptocurrency in exchange for a fiat currency. However, this also means that available currencies are limited. One might easily purchase $USDC or $ATOM (Cosmos native coin), but not $REGEN. These exchanges vary in ease of use, fees, payment options, and global availability. Some exchanges require a day or two to verify your identity before purchased currency can be moved. Some exchanges require a minimum amount of currency be purchased in a single transaction. We highly encourage you to research exchange options before selecting the one that will best meet your needs. Below are some popular and trusted exchanges with fiat onboarding options. {% embed url="" %} {% embed url="" %} {% embed url="" %} {% embed url="" %} ### Decentralized Exchanges A decentralized exchange, also known as a DEX, is an on-chain exchange where all liquidity for trading pairs/pools is provided by its users. Users are generally incentivized to provide liquidity with interest, most often paid in the chain's native coin. These kinds of exchanges enable swapping one cryptocurrency for another, but not purchasing a cryptocurrency with a fiat one. Decentralized exchanges will provide more options specific to a particular audience. Thanks to the bridges available, Gravity USDC and Axelar USDC may be purchased through Cosmos Ecosystem DEX chains. As long as currencies are bridged through the provided channels, they will work in the Regen Marketplace. Currency bridged through other means may not be accepted. Below are a couple of trusted DEX chains built with Cosmos SDK and offering a wide array of coins and tokens from within the Cosmos Ecosystem. {% embed url="" %} {% embed url="" %} {% embed url="" %} ## Wallets In order to move around purchased currency, you will need the appropriate wallet. Centralized exchanges will provide an address who's key is managed by the exchange. However, in order to move your assets through one of the bridging options provided, you will need to withdraw your assets to a more neutral location. [Keplr ](/guides/wallets/wallet-setup/create-a-keplr-wallet)is an important tool for managing Cosmos Ecosystem assets, like $REGEN or USDC purchased through Osmosis. To manage assets like USDC purchased through a centralized exchange, you will need a [MetaMask](https://metamask.io/) wallet. ## Fees Fees, or gas fees, play an important role within blockchain. In most cases, fees are a small amount of the chain's native currency and are distributed to the blockchain's validator set in order to offset server costs. Fees will always be displayed clearly during a transaction and you will most often have options to set your gas fee. When approving most transactions through your Keplr wallet, you will be prompted to select a low, average, or high fee. The difference between each is minimal, but selecting a higher fee may speed up the time a transaction takes to process. When purchasing ecocredits on the Regen Marketplace, you will need a small amount of $REGEN. Below is a Keplr window that was generated during a purchase of ecocredits. Fees for the transaction range from .002 $REGEN to .008 $REGEN, each equivalent to a fraction of $0.01.
### Bridging Fees So far, our community has elected three currencies for use in the marketplace: Gravity USDC, Axelar USDC, and $REGEN. Gravity USDC and Axelar USDC will need to be bridged to your Regen wallet and will require an additional bridging fee. Unlike the $REGEN fees covered above, these are used to pay the relayers who make the bridge possible. Each bridge approaches fees in a slightly different way. #### Gravity USDC When bridging USDC with Gravity Bridge on [Blockscape](https://bridge.blockscape.network/), you will need a small amount of ETH to pay for fees. This fee is dynamically updated based on current bridge traffic. An open transaction window will update its fees periodically until the transaction is approved. This allows Gravity Bridge to ensure their relayers' costs are covered, while offering users the lowest possible bridging fee. Find the Gravity USDC bridging guide [here](#gravity-usdc). #### Axelar USDC To bridge USDC with Axelar you will need additional USDC to pay bridge fees. This bridge fee is manually set by the Axelar team and updated as necessary to accommodate relayer costs. Find the Axelar USDC bridging guide [here](#axelar-usdc). # Axelar USDC Step-by-step directions for bridging USDC to your Regen wallet Axelar USDC offers the ability to bridge USDC from your Ethereum or Osmosis wallet to your Regen wallet. This guide provides directions for bridging USDC from your Osmosis wallet to your Regen wallet through the [satellite.money](http://satellite.money/) UI. Ecocredits purchased on the Regen Marketplace are sold in a currency specified by the seller. Before bridging USDC with Axelar, confirm the credits you wish to purchase are for sale in Axelar USDC. ### 1. Connect Wallet to Satellite Interface a. Satellite will default to an Osmosis to Ethereum bridge. First change Ethereum to Regen by selecting it from the drop box.
b. Next connect to your Keplr wallet by selecting either of the connect buttons indicated with red arrows in the image above. ### 2. Enter Transaction Details a. Input how much USDC you want to transfer. The "Max" button fill this field will all available axlUSDC. *Note: Relayer Gas Fees will come out of the amount set here. You do not need to exclude a reserve amount of USDC for gas fees.*
b. Paste the Regen wallet address you are sending the USDC to or select the Autofill option to send the USDC to the connected Regen wallet. ### 3. Transfer Currency a. Click "Generate Deposit Address" which will kick start the transaction.
b. When prompted for your Relayer Gas Fees, select "Send from Keplr" and approve the corresponding transaction.
c. Once the gas fee has been accepted, your transfer will complete. ### 4. View USDC in Regen Wallet a. It may take several minutes after the "Transaction complete" message for your transaction to fully process. Once it has, you will be able to view your USDC on the Keplr Dashboard or in the wallet extension. b. From the Keplr extension, your bridged USDC will be listed in "Tokens" at the bottom of the window.
c. From the [Keplr Dashboard](https://wallet.keplr.app/), you can see your USDC in your Token Allocation, listed as "USDC".
**Congratulations! You have now bridged USDC to your Regen wallet, where it is ready to invest in your favorite Regen Marketplace project.** Find directions for purchasing ecocredits [here](/guides/regen-marketplace-buyers-guides/ecocredits/buy-ecocredits). # Gravity USDC Step-by-step directions for bridging USDC.grv to your Regen wallet The first currency approved by the community for use in the Regen Marketplace was Gravity USDC, that is Ethereum based USDC bridged to your Regen wallet using Gravity Bridge. This guide provides directions for bridging USDC from your Ethereum wallet to your Regen wallet using the Gravity Bridge Portal. Ecocredits purchased on the Regen Marketplace are sold in a currency specified by the seller. Before bridging USDC with Gravity Bridge, confirm the credits you wish to purchase are for sale in Gravity USDC. ### 1. Connect Wallets to Gravity Bridge Portal a. Navigate to the [Gravity Bridge Portal](https://bridge.blockscape.network/).
b. Connect your MetaMask and Keplr wallets through the two "Connect" buttons. ### 2. Enter Transaction Details a. Change the destination chain from "Gravity Bridge" to "Regen".
b. Enter the amount of USDC you would like to transfer. You will not need to save any USDC for transaction gas, as this is fee is charged in ETH. *Note: Your first transaction should be a small test amount to confirm functionality before sending your full amount.* c. In the "Select Token" drop box, select USD Coin.
### 3. Transfer USDC a. Click the "Begin transfer" button. You will be prompted to approve your transfer. b. A MetaMask window will appear with the estimated gas fee, highlighted in red in the above image. This fee is updated dynamically and may change if you leave the window open. This fee is paid in ETH. c. Confirm your transaction. You will receive a waiting window, followed by a success window if your transaction completes successfully.
### 4. View USDC in Regen Wallet a. It may take several minutes after the "Transaction complete" message for your transaction to fully process. Once it has, you will be able to view your USDC on the Keplr Dashboard or in the wallet extension. b. From the Keplr extension, your bridged USDC will be listed in "Tokens" at the bottom of the window.
c. From the [Keplr Dashboard](https://wallet.keplr.app/), you can see your USDC in your Token Allocation, listed as "USDC.grv". This differentiates it from other forms of USDC in the Cosmos Ecosystem, like Axelar USDC listed as "USDC" below.
**Congratulations! You have now bridged USDC to your Regen wallet, where it is ready to invest in your favorite Regen Marketplace project.** Find directions for buying ecocredits [here](/guides/regen-marketplace-buyers-guides/ecocredits/buy-ecocredits). # Regen Network This section overviews the many facets of Regen Network, dives into the evolution of Regen Ledger, and outlines the components of community. # Network Basics # About A quick overview of Regen Network and its components [*Regen Network*](https://www.regen.network/) *is* the ecological asset origination system of the [Cosmos](https://cosmos.network/) ecosystem. {% embed url="" %} ## Network Organization **Regen Network** is the overarching whole. Although we often refer to ourselves as Regen Network, the Network is not an organization, but rather a community, a commons, a movement, a public blockchain-based protocol, and a network. **Regen Network Development, Inc. (RND)** is the primary software development company building open-source tools and applications on Regen Ledger. RND also assists in maintaining Cosmos SDK for the Cosmos Ecosystem. **Regen Foundation** is a US-based tax deductible 501(c)3 non profit organization. Regen Foundation focuses its effort on scientific research and infrastructure development that creates a transparent, open digital Monitoring, Reporting, Verification (dMRV) system. Regen Foundation also controls a portion of the original token distribution, which it in turn distributes as staked tokens to groups of farmers, indigenous nations, and other non-profit partners through a process of enDAOment. With permanently staked tokens these groups can vote in Regen Network governance and help shape the future of the Regen Network toolkit, thus providing them with a voice in the process and development. Additionally, the staked $REGEN earn inflationary rewards which can be exchanged for money to fund operation costs. **Regen Ledger** is the blockchain itself, which is governed by $REGEN token holders who are staking their tokens. Anyone may participate in governance this way. Regen Ledger is covered in further depth in the [Regen Ledger](/guides/regen-network/regen-ledger) subsection of this guide. **Cerulean Ventures** is an investment firm that believes in the potential growth of natural assets which incentivize the regeneration of Earth through new coordination technologies. Cerulean Ventures invests actively in and outside of the Cosmos Ecosystem for the advancement of interblockchain communication (IBC) and other infrastructural innovations that have the potential to rapidly scale climate impact through user-focused web3 tools. # Connect with Us Regen Network Social Media accounts ## Regen Network **Website:** **Twitter:** [ ](https://twitter.com/regen_network) **Discord:** **Instagram:** **Telegram:** **Facebook:** **Medium:** **Youtube:** **Github:** **Hylo:** ### Regen Network Development, Inc **Twitter:** **LinkedIn:** ### Regen Foundation **Website:** **Twitter:** **Instagram:** **LinkedIn:** ### Regen Ledger **Github:** ### Cerulean Ventures **Website:** **Twitter:** **LinkedIn:** # Additional Resources For a lite introduction to **what fuels Regen Network**, check out "[Regen Network: How to Change the World](https://medium.com/chorus-one/regen-network-how-to-change-the-world-b4e014da8fa0)". Don't forget to peruse **Regen Network**'s [website](https://www.regen.network/)! For a **deep dive into Regen Network**, check out the [Regen Network Whitepaper](https://regen-network.gitlab.io/whitepaper/WhitePaper.pdf) and "[Community update to original Whitepaper](https://medium.com/regen-network/regen-network-community-update-65fb4f445187)". Learn more about the **RND Inc Community Funding Program** with this blog, "[Congratulations to our Community Funding Program Awardees!](https://medium.com/regen-network/congratulations-to-our-community-funding-program-awardees-50c023a21d8)" Learn more about **Regen Foundation** by visiting their [website](https://regen.foundation/). # Regen Ledger # About An overview Regen Ledger, Regen Network's blockchain. Regen Ledger is a public [delegated Proof-of-Stake (dPoS)](/guides/cosmos-ecosystem/blockchain-basics/glossary-of-terms#delegated-proof-of-stake) blockchain application built with [Cosmos SDK](https://docs.cosmos.network/). Regen Ledger provides the blockchain infrastructure for ecological assets and the verification of claims. ## The Evolution of Regen Ledger Since its initially launch on April 15, 2021, Regen Ledger has three major upgrades, each adding features necessary to achieve the goals of Regen Network. ### v2.0 - Ecocredit Module Regen Ledger v2.0 added the **Ecocredit Module**. This enabled the creation and management of credit types, credit classes and projects, as well as the issuance, transferring and retirement of ecosystem service credits (i.e. carbon credits, biodiversity credits, soil health credits, etc.). ### v3.0 - Basket Submodule Regen Ledger v3.0 introduced the **Basket Submodule** to the existing Ecocredit Module. Ecocredits are *non-fungible*, meaning they are unique in value and cannot be traded one-to-one. However, these credits can be added to a virtual basket in exchange for *fungible* tokens. These fungible tokens can be bought, sold and pooled on a centralized or decentralized exchange. At anytime, tokens may be returned to the basket and exchanged for their value in the existing ecocredits. ### v4.0 - Marketplace Submodule & Data Module [Regen Ledger v4.0 ](https://medium.com/regen-network/bringing-the-full-eco-credit-lifecycle-on-chain-with-regen-ledger-v4-0-183ca96ea7c7)added the **Marketplace Submodule** to the existing Ecocredit Module. This submodule added the functionality for buying and selling ecocredits directly in an on-chain marketplace. The most recent upgrade to Regen Ledger also added the **Data Module**. While the Ecocredit Module enables the creation and management of credit classes, projects and credit batches, the Data Module provides the verifiable supporting data for them. v4.0 also added functionality to support a coming bridge that will be used to bridge ecocredits to/from the Polygon Blockchain. This will play a key role in funding initial token baskets. # Additional Resources Deep dive into **Regen Ledger v4.0 upgrade** with this blog, "[Bringing full eco-credit lifecycles on-chain with Regen Ledger v4.0](https://medium.com/regen-network/bringing-the-full-eco-credit-lifecycle-on-chain-with-regen-ledger-v4-0-183ca96ea7c7)". Explore **Regen Ledger** on its [GitHub](https://github.com/regen-network/regen-ledger/blob/master/README.md). Learn more about the [Nature-Carbon Tonne ](https://docs.toucan.earth/protocol/pool/pool-parties/nct-pool-party-report)the Toucan Bridge will be moving from Polygon to Regen Network's blockchain. # Token & Community # $REGEN A brief overview of the $REGEN coin [$REGEN](https://www.regen.network/token) is the coin native to Regen Network's blockchain. It is heavily influenced by the design of the Cosmos' native coin, $ATOM , but adapted for the use of ecological data and outcome markets. Through inflationary rewards, which fluctuate from 3.5-10% pending market trends, $REGEN is used to reward validators and delegators engaged with Regen Network. It is with the coin that community members submit and vote on governance proposals. Coins were originally distributed between four categories, sale allocation, Community DAOs & Foundation allocation, the Regen Network team & community, and liquidity. # Validators An overview of the role of validator and the process of becoming a validator ## Role Definition Regen Ledger is built on top of the [Tendermint ](https://docs.tendermint.com/v0.35/)[delegated Proof-of-Stake (PoS)](/guides/cosmos-ecosystem/blockchain-basics/glossary-of-terms#delegated-proof-of-stake) consensus algorithm and requires validators to secure the network. Thus, we are powered by our global validator set: a constellation of companies, individuals, and community members that run the nodes securing our public blockchain. Validators play a similar role in a [PoS](/guides/cosmos-ecosystem/blockchain-basics/glossary-of-terms#proof-of-stake) network as miners do in a [PoW](/guides/cosmos-ecosystem/blockchain-basics/glossary-of-terms#proof-of-work) network. The differences is validators are enormously energy efficient, and the validator community tends to be much more open, cooperative and actively engage to build value and utility on the networks they chose to validate for. Validators run a full node and participate in consensus by broadcasting votes that contain cryptographic signatures signed by the validator's private key. Validators commit new blocks in the blockchain and receive revenue in exchange for their work. Validators must also participate in governance by voting on proposals. Validators are weighted according to their total stake. Validators are the unsung heroes of proof of stake networks, and form the foundation of security, governance and uptime of Regen Ledger. ## Becoming a Regen Network Validator Becoming a Regen Network validator is just as an important part of our ecosystem and we value anyone who attempts to do so. In order to do so the first step is to spin up a validator server by following our [guides](https://docs.regen.network/) and becoming familiar with our g[ithub](https://github.com/regen-network/regen-ledger). Next you will want to self-delegate but you will also want to gain delegations from others. Delegators typically have their own criteria for choosing which validator to delegate to, so when starting your journey to becoming a validator on the Regen Network you should ask yourself the following questions. * **Are you running secure and reliable infrastructure and have you disclosed your architecture?** * **Are you in some way trying to apply the high level application logic to create ecological credits?** * **Are you working to engage a broader community?** * **Are you a professional validator?** * **Did you perform well during testnets (if applicable)?** * **Does RND Inc know who you are?** * **Are you active within the community on discord and in this forum?** # Delegators A brief overview of the role of delegators in Regen Network Staking/delegating is a great way to earn $REGEN tokens and an important part of maintaining and growing the value of your tokens. It’s also an important part of being a community member and supporting the network. Individuals operating a validator have to pay for infrastructure. The more secure and complex the infrastructure the more costs are associated with it. Delegating to validators by staking your $REGEN tokens helps cover the infrastructure costs validators accrue, and will earn you a solid return on your $REGEN tokens as well! You are likely to earn between 7% and 20% APR on your tokens when you stake your tokens! [Staking $REGEN](/guides/wallets) and [participating in network governance](/guides/network-governance) are covered further in later sections of this guide. ## Community Staking DAOs In addition to independent delegators, [Community Staking DAOs](https://regenfoundation.notion.site/Community-Staking-DAO-1ed707d6abf8805fbacece7341962c54) (csDAOs) serve as delegators in the Regen Network ecosystem. With the launch of mainnet, Regen Foundation received 35% of the initial token distribution, which it has been distributing to groups of farmers, indigenous nations, and other non-profit partners through a process of enDAOment. In turn, these groups can use their permanently locked tokens to vote in Regen Network governance and help shape the future of the Regen Network toolkit, hence providing them with a voice in the process and development. Like individual delegators, csDAOs earn inflationary rewards which they can use to fund operation costs for their organization. # Additional Resources ## $REGEN Learn more about the **Regen Network token and what it means to invest** in it with the blog, "[The case for a small allocation to Regen](https://gardens.substack.com/p/the-case-for-a-small-allocation-to)". ## Validators Learn a little bit more about the **basics of Cosmos validators** in these [Validator FAQs](https://hub.cosmos.network/main/validators/validator-faq.html). Deep dive into **what validators are and what it takes to become one** with these guides from [Cosmos ](https://hub.cosmos.network/main/validators/overview.html#)and [Tendermint. ](https://docs.tendermint.com/master/nodes/validators.html) Learn more about the **Regen Network Validators** on our [website](https://www.regen.network/validators/). ### Validator Resources Learn how to **install Regen Ledger** on our [docs site](https://docs.regen.network/). Deep dive into the **tech behind Cosmos Validators** with "[Sentry Node Architecture Overview](https://forum.cosmos.network/t/sentry-node-architecture-overview/454)". Explore **validator security methods** in the blog, "[Playbook For Cosmos Validators: Node Architecture Choices](https://medium.com/@kidinamoto/tech-choices-for-cosmos-validators-27c7242061ea)". Check out [Testnet Kitchen Video Guides](https://www.youtube.com/channel/UCDcAV6ECpnivEk5bH68_oYA) on YouTube for a **walkthrough of key concepts**. ## Delegators If you are interested in learning more about **becoming a delegator**, start with this thorough blog, "[Staking in the Cosmos Network — Making the Ecosystem More Secure](https://blog.cosmos.network/staking-in-the-cosmos-network-making-the-ecosystem-more-secure-31cc5c0b2cdb)". Read more about the current happenings at **Regen Foundation and its csDAOs** in the [2022 annual report](https://regen.foundation/wp-content/uploads/2022/05/REGEN-ANNUALREPORT-2021.pdf). # Wallets This section contains step-by-step directions for creating, sending, staking and securing your Regen wallet. # Overview on Blockchain Accounts and Wallets Before you use the Regen Network ecosystem, it's important to understand what a blockchain **account** and **wallet** are, how they work, and why they're essential. *** ## 🌱 **What Is a Blockchain Account?** A **blockchain account** is your digital identity on Regen Ledger, similar to a username or email address in traditional web applications. It’s how you interact with blockchain-based services, like Regen Registry application or DAODAO UI, and where you receive and manage your digital assets, such as Regen tokens ($REGEN). Your blockchain account consists of two critical parts: * **Public Address:**\ A unique, public-facing identifier (like an email address) that you can safely share with others. People or apps can send tokens or digital assets to this address, or authorize it to perform actions like updating a project or issuing credits. * **Private Key:**\ A secret piece of data (similar to your password) that gives you control over your account and assets. Whoever has access to this private key controls your account, so it must remain private and secure. *** ## 💼 **What Is a Wallet?** A **wallet** is a digital tool used to access and manage your blockchain account(s). It acts as a secure interface for handling your **private key** and **public address**, enabling you to interact with blockchain-based applications, manage digital assets, and authorize transactions. Wallets provide users with the ability to: * **Create accounts:** Generate a new blockchain account with a unique public/private keypair. * **Manage assets:** Send, receive, and view tokens like $REGEN or other digital assets. * **Sign transactions:** Approve blockchain actions — such as transferring tokens, verifying projects, or voting — using your private key. {% hint style="info" %} **Important to note:** Your wallet doesn’t physically "store" tokens; rather, it securely stores your private keys, enabling you access your blockchain account to manage assets and engage in functionality. In simple terms, your wallet is what lets you “log in” to your blockchain account. {% endhint %} *** ## 🔓 Accessing Wallets To access your blockchain wallet — and the account it controls — you need the **private key** associated with it. Most modern wallets simplify this by giving you a **seed phrase**, a set of 12 or 24 randomly generated words that acts as a secure backup to generate your private key. If you ever lose your device or uninstall your wallet, this seed phrase is the only way to recover your blockchain account. The table below summarizes the key components of a blockchain accounts and wallets: | Component | Description | Analogy | Example | Visibility | | ------------------ | ------------------------------------------------------------------------------------ | --------------- | -------------------------------------------------------------------------------- | ---------------------- | | **Public Address** | Your blockchain identity — others use it to send you tokens or verify your activity. | Email Address | `regen1p5t9lfku8s...v7r34m4` | Public (shareable) | | **Private Key** | The cryptographic key that lets you sign transactions and control your account. | Password | `5Kb8kLf9zgWQnogidDA76MzPL6TsZZY36hWXMssSzNydYXYB9KF` (hidden in wallet) | Private (never share) | | **Seed Phrase** | A 12- or 24-word phrase used to recover your private key and wallet. | Master password | `zebra shield mobile melt violin blouse base canyon reject toddler paddle chaos` | Private (store safely) | *** ## 🌿 **Blockchain Accounts and Regen** Your blockchain account is the foundation for engaging with the Regen Network ecosystem. It serves as your digital identity — enabling you to participate in ecological projects, manage digital assets, and interact with applications like the **Regen Registry** or **DAODAO UI**. In practical terms, your blockchain account allows you to: * **Sign in to Regen Registry application** to create projects, upload and verify ecological data, buy and sell credits. * **Manage assets** like $REGEN and other tokens linked to your address. * **Participate in governance**, including voting on protocol upgrades, credit classes, or on-chain proposals. To use your blockchain account, you’ll need a wallet. **Keplr** is the most common choice within Regen’s ecosystem. It integrates directly with Regen apps, provides easy access to your address, and supports secure key management through self-custody or Google login options. Learn more about account and wallet setup in the [Wallet Setup](/guides/wallets/wallet-setup)section of this guide. # Wallet Setup To interact with Regen ledger — whether you’re voting on proposals, staking tokens, or creating organizations — you’ll first need a compatible wallet. The most widely used option is **Keplr**, a browser extension and mobile wallet that supports the Regen Network blockchain. Setting up your wallet is a two-step process: 1. [**Create a Keplr Wallet**](/guides/wallets/wallet-setup/create-a-keplr-wallet)\ Learn how to install Keplr, create a new wallet, and securely back up your recovery phrase. 2. [**Acquire REGEN**](/guides/wallets/wallet-setup/acquire-usdregen)\ Once your wallet is ready, follow this guide to acquire REGEN tokens so you can participate in governance, staking, and network activities. After completing these steps, your wallet will be fully set up to connect with Regen Network dApps and tools such as the Regen Explorer and Mintscan. # Create a Keplr Wallet A quick guide for creating and accessing a Keplr wallet This guide provides detailed instructions for creating a Keplr wallet — the recommended option for accessing the Regen Network ecosystem. {% hint style="info" %} Keplr is available as a browser extension (Chrome, Firefox) and as a mobile app (iOS, Android). This guide focuses on the Chrome extension. {% endhint %} *** ## 1. Install the Keplr Extension a) Navigate to the [Keplr](https://chrome.google.com/webstore/detail/keplr/dmkamcknogkgcdfhhbddcghachkejeap?hl=en) extension in the Chrome Web Store. Click "Add to Chrome". ![](/files/OiBLoTvLO2vmIQt3kkHR) b) Confirm that you want to proceed and add the Keplr extension by selecting the **Add extension** option. ![](/files/y1oxk94R56wkD4JtkOrJ) c) Confirm the extension is included among your extensions by clicking the puzzle piece in the upper right hand corner of your browser window. Click the Pin icon to keep Keplr on the browser bar.
*** ## 2. Set Up Your Wallet a) Click on your Keplr extension and you will be redirected to the below page. ![](https://miro.medium.com/max/1110/0*hSNFlzODUBwRKPaN) b) Create a new account by selecting between one of the following two options: * **Sign in with Google (Custodial):** Keplr creates and stores your [private key](/guides/wallets/overview-on-blockchain-accounts-and-wallets#blockchain-accounts-and-regen) for you. No seed phrase or manual key management is needed. This is a **custodial** option — fast and simple, but you’re trusting Keplr to manage your keys securely. * **Create new account (Self-Custodial):** Keplr generates a 12-word **seed phrase**, and **you manage the keys yourself**. This is a **self-custody** option — you have full control, but also full responsibility. {% tabs %} {% tab title="Sign in with Google (Custodial)" %} 1. Select **“Sign in with Google.”** 2. Choose your Google account and approve access. 3. Enter a name for your account, which will also serve as the name of the new account created your wallet. 4. Next, Keplr will next prompt for you to a set a password. This is a browser specific password that Keplr will prompt you for after periods of inactivity to access your wallet and its associated accounts. {% endtab %} {% tab title="Create New Account (Self-Custody)" %} 1. Select "Create new account" from the list. 2. Select a memonic seed length (12 or 24-word). A list of 12 or 24 random words, known as a mnemonic seed or [seed phrase](/guides/wallets/overview-on-blockchain-accounts-and-wallets#blockchain-accounts-and-regen), will display. **This is the single most important information associated with your account.** At a minimum you should store a hard copy of this information in two separate and secure locations. If this information is lost, the associated wallet will also be lost and any assets on it will be irretrievable. Read more about Wallet Security [here](/guides/wallets/wallet-security). 3. Enter a name for your account, which will also serve as the name of the new account created your wallet. 4. Next, Keplr will next prompt for you to a set a password. This is different from the mnemonic seed. It is a browser specific password that Keplr will prompt you for after periods of inactivity to access your wallet and its associated accounts. As long as you maintain your mnemonic seed, this password can be easily lost and reset. 5. Next you will prompted to confirm your mnemonic seed. Select the words in your mnemonic seeds in the correct order from step (2) {% endtab %} {% endtabs %} ![](https://miro.medium.com/max/1058/0*vmfpBY-LBPzUxzcS) ### 3. Access Your Regen Wallet a) Now that your have created a wallet you can access it anytime by selecting the Keplr extension in your browser bar. b) While your new wallet will be empty, $REGEN will display among your Available Balance. Searching for Regen in the tab will display all tokens available on your Regen wallet, as well as $REGEN balances on other wallets.
c) From the Staked tab of the extension, you can view staked $REGEN, claim rewards, and copy your Regen wallet address. ### 4. Copy Regen Wallet Address a) To copy your Regen wallet address to your clipboard, click the Copy Address button and then search Regen. Click anywhere on the line containing Regen (not the Redwood Testnet). The white text reading "Copy" will turn green and change to "Copied" to signal success. b) This address, also known as a public key, is safe to share. It may be used to transfer to tokens to the wallet or view a history of wallet transactions, but it cannot be used to remove funds from your wallet.
# Acquire $REGEN A quick guide to acquiring your first $REGEN for users completely new to the web3 space who wish to participate in the Regen Network community: > ### **Looking for an overview of $REGEN and where it's active?** 👉 **Visit the official** [**$REGEN Coin page**](https://coin.regen.network/) for current prices, supply, network stats, and useful links to Osmosis, Keplr, and Mintscan. ### 1. Acquire USDC To acquire $REGEN, you’ll first need a commonly traded asset like USDC on the Osmosis decentralized exchange. * **Option 1: Use Coinbase or Kraken** * Purchase USDC via a centralized exchange (CEX) like [Coinbase](https://www.coinbase.com/) or [Kraken](https://www.kraken.com/), then withdraw it to a wallet that supports Axelar (axlUSDC) or Noble USDC to bridge into Osmosis
**Other options:** * Use [Squid Router](https://www.squidrouter.com): If you already have crypto on another network (e.g. Ethereum, Polygon), you can use Squid Router to bridge into Osmosis and receive axlUSDC directly. * Osmosis on-ramp aggregators: Explore third-party options like [Transak](https://transak.com/buy/osmo) or [Skip.money](https://skip.money/) to directly fund your Osmosis wallet with USDC. * IBC transfers: If you already have USDC on another Cosmos chain (like Noble or Axelar), you can use Osmosis IBC Transfers to move it into Osmosis. ### 2. Trade USDC for $REGEN on Osmosis a. Visit the [Osmosis App](https://osmosis.zone). b. Connect your Keplr Wallet. c. Navigate to the Swap tab.
d. Select USDC.axl or USDC.noble as the asset you’re swapping *from*. e. Select REGEN as the asset you’re swapping *to*. f. Confirm the transaction in your [Keplr wallet](/guides/wallets/wallet-setup/create-a-keplr-wallet). > Once the transaction confirms, you will see your $REGEN balance on the Regen Network chain in your Keplr Wallet. ### 3. Verify Your Wallet Balance These transactions can take a few minutes and you may need to refresh your dashboard to see the update. You can also track your transaction using a blockchain explorer like [Mintscan](https://www.mintscan.io/regen), by searching your [Regen wallet address](/guides/wallets/wallet-setup/create-a-keplr-wallet).
**Congratulations!! You have purchased your very first $REGEN!** # How to Transact # Send $REGEN A step-by-step guide for sending $REGEN from one wallet to another ### 1. Access Keplr Wallet a. Pull up your Keplr wallet by clicking the Keplr icon in the extensions section of Chome.
b. For this process, you will need the address for the wallet you are sending the $REGEN to. ([Steps for copying a Regen wallet address can be found here.](https://guides.regen.network/guides/wallets/how-to-transact/pages/ZyWYsAZR8QAAElprVqWm#4.-copy-regen-wallet-address)) ### 2. Send Tokens a. Click the "Send" button (indicated with the green box in the image above) to begin the transfer process. b. Enter the correct **wallet address** in the "Wallet Address" field and the **amount** you are moving in the "Amount" field. The "Memo" field is optional for transfers between Regen wallets, but can be used for any transaction notes. c. You can adjust your Transaction Fee by clicking to view its menu. The default fee displayed from the send screen is the "Average" fee. Increasing or decreasing your paid fees will affect how quickly your transaction is processed. A higher fee will result in a faster transaction processing time. d. Click "Next". A summary of your transaction will display. If everything looks to be correct, click "Approve".
**Congrats! You have sent some $REGEN from one wallet to another!** *Note: These transactions can take a few minutes and you may need to refresh your page to see the update. You can also track your transaction (by searching the transaction ID or either wallet address) using a blockchain explorer like* [*Mintscan.*](https://www.mintscan.io/regen) # How to Stake # Stake $REGEN A step-by-step guide for staking $REGEN There are many benefits to staking/ delegating Regen Network tokens. Staking not only plays a critical role in maintaining the network's security, but also aids in price stability, encourages community growth, and helps to cover validator costs. This guide picks up where [Create a Keplr Wallet](/guides/wallets/wallet-setup/create-a-keplr-wallet) ended. If you have not yet created a Keplr wallet, follow the steps in that guide before returning to this document. ### 1. Send $REGEN to your Keplr wallet a. If you do not already have some $REGEN in your Regen Keplr wallet, you will need to [transfer](/guides/wallets/how-to-transact/send-usdregen) some. b. Transferring $REGEN may take a few minutes to complete. You can always use a blockchain like [Mintscan](https://www.mintscan.io/regen) explorer (searching by transaction or either wallet address) to view a transactions status in real time. ### 2. Access the Keplr Dashboard a. Pull up the [Keplr Dashboard](https://wallet.keplr.app/) on your Chrome browser.
b. Regen should appear in your assets list, like in the screenshot above. Click anywhere on the Regen line, as indicated with the red box in the image above, to access the Regen Network page of the Keplr Dashboard.
### 3. Select a Validator a. Scroll down to see the list of All Regen Network validators, their voting power, commission rate, and approximate APR.
b. When you've selected a validator you would like to delegate to, click the arrow at the end of their line. ### 4. Delegate Tokens a. It will produce the below pop out. ![](/files/kugxkofjuaugPegEJ5cS) b. Click the "Delegate" button. ![](/files/YICM17W7acgbpcnITbFj) c. It will prompt you for an amount to delegate. You may enter an amount or click the "MAX" button to delegate all available $REGEN. *Note: you will need some $REGEN to pay for gas on your transaction, so be sure to leave yourself a small amount.*
d. This will trigger a Keplr pop out window. Select your fee and approve the transaction. ### Congratulations! You've now staked your $REGEN! You can view your staked $REGEN from the home screen or the Regen Chain page. # Claim Staking Rewards How to claim or claim & redelegate staking rewards from the Keplr Dashboard While you are staking $REGEN, you earn inflationary rewards. These instructions are for claiming rewards from the Keplr Dashboard. ### 1. Access the Keplr Dashboard a. Navigate to the Keplr Dashboard, which can be found [here.](https://wallet.keplr.app/)
### 2. Claim or Claim & Delegate Rewards a. In the upper right hand corner of your Dashboard will be a balance of rewards accrued from your staked tokens. Click the "Claim" button inside of this box (indicated with the red arrow in the above image). This will generate the below pop up window. ![](/files/AtzWQDOJv7fLICxBFy9A) b. Here you have two options. "Claim & Stake" will allow you to claim your token balance and delegate it to the validator you have chosen in a single transaction. Claiming and delegating your rewards regularly allows you to effectively compound your inflationary rewards. "Claim" moves your available rewards to your available $REGEN balance. Clicking either option will generate a Keplr transaction window.
c. Here I have selected "Claim & Stake" which is why there are two transactions in the Messages section. If you selected "Claim" only the "Claim Staking Reward" message will appear. Select your fee and click "Approve". *Note: It is especially important to have a cushion of $REGEN to pay for the gas if you are claiming and redelegating simultaneously. There is a buffer of $REGEN taken into account that can cause your transaction to fail, even if you appear to have more $REGEN than the fee requires.* d. You have now claimed your staked rewards! This transaction may take a couple of minutes to appear. Once the transaction has been completed, your reward balance will appear in either your Staked Balance (Claimed & Staked) or Available Balance (Claimed only).
# Redelegate Staked $REGEN How to redelegate staked tokens via the Keplr Dashboard Redelegating $REGEN will move your tokens from one validator to another. They will remain bonded and will continue collecting inflationary rewards. ### 1. Access the Regen Network Chain Page a. Navigate to the Regen Chain page of the Keplr Dashboard [here.](https://wallet.keplr.app/chains/regen)
### 2. Manage Delegations a. Click anywhere on your current validator, indicated by the red box in the screenshot above. It will generate the below pop out.
b. Click the "Redelegate" button to begin the process. ### 3. Redelegate Tokens a. Clicking "Redelegate" will generate a pop up window containing a list of active validators. Select the validator you wish to move your tokens to and click "Next". ![](/files/HSlkpiIQ9rVDc82sSc3Y) b. Enter the amount of $REGEN you would like to move to the new validator and click "Redelegate".
c. A Keplr transaction window will pop up. Select your fee and click "Approve".
d. Once the transaction has processed, your validator list will be updated to reflect the redelegation.
# Undelegate Staked $REGEN How to undelegate tokens on the Keplr Dashboard Undelegating $REGEN will place your tokens into a 21 day holding period, during which time they will not accrue inflationary rewards. After the unbonding period is over, they will appear in your available balance. ### 1. Access the Regen Network Chain Page a. Navigate to the Regen Chain page of the Keplr Dashboard [here.](https://wallet.keplr.app/chains/regen)
### 2. Manage Delegations a. Click anywhere on your current validator, indicated by the red box in the screenshot above. It will generate the below pop out. ![](/files/FxU8iGgojaut82ITgXDQ) b. Click the "Undelegate" button to initiate the undelegating process. ### 3. Undelegate Tokens a. The below pop out window will appear. Enter in the amount of tokens you wish to undelegate and then click the "Undelegate" button. ![](/files/UK1jVBPdKssHfS3LVGqB) b. A Keplr transaction window will pop up. Select your fee and click "Approve" to complete the process. c. Once the transaction has processed, you will see your tokens in a new section of the chain page, "Undelegating". Here you can view the days remaining in the undbonding period. ![](/files/Rj91AGCHczcecPRo8Oc5) # Additional Resources For **more information about staking**, check out this blog, "[Staking with Keplr](https://regen-network.medium.com/staking-with-keplr-dc8cdfda0cc7)". Keep up to date with the current [Regen Network Staking Rewards](https://www.stakingrewards.com/earn/regen/). # Wallet Security # Best Practices Some best practices for keeping your Keplr wallet safe ### Backup your Mnemonic Seed Your access to the Keplr wallet you have setup begins and ends with the mnemonic seed you received when you set up your account. If you are not currently logged into your account, there is no way to recover your mnemonic seed, which means if you lose it you lose access to the wallet and all of the assets it holds. **More crypto is lost because people lose their seed than because their seed was stolen.** With this in mind, we recommend storing your mnemonic seed in at least two separate locations (such as a safe in your house or a secure deposit box). We do not recommend storing your mnemonic seed digitally (text, photo, screenshot form), as it reduces its overall security. If you are currently logged into your wallet and do not have a good record of your mnemonic seed, you use the directions below to access it. 1. Log in to your [Keplr](https://keplr.app/) browser extension 2. Click on the profile icon 3. Find your wallet and click the three dots 4. Click view mnemonic seed 5. Enter password 6. Write down your mnemonic and store securely ### Other Security Tips * Don’t use ctrl-c or copy when copying. Instead use the built in function within wallets to copy your keys * Use a hardware wallet if possible * Use a hardware option such as crypto-steel to save your mnemonic seed * Never share your private keys, mnemonic seed or password with anyone * **DO NOT** screenshot your mnemonic seed * (**OPTIONAL**) Use a computer exclusively reserved for accessing and interacting with your crypto assets # Additional Resources Don't discount the importance of security with your new crypto assets! Check out the blog, "[Setting up Keplr Wallet and Best Practices for keeping your crypto safe!](https://regen-network.medium.com/setting-up-keplr-wallet-and-best-practices-for-keeping-your-crypto-safe-cfe5f924692d)" from Regen Network as well as the article, "[A Security Checklist For New Crypto Investors](https://www.gemini.com/cryptopedia/blockchain-security-checklist-crypto-security-in-blockchain)" from Cryptopedia. # Network Governance This section dives into network governance with Regen Network, including step-by-step directions for using Commonwealth and a dedicated section to the Community Spend Pool. # Governance Basics # About The practical function of governance in the Regen Network and a deep dive into how it is carried out Governance is one of the most important tools belonging to blockchains in the [Cosmos](https://cosmos.network/) ecosystem. Governance allows stakeholders to make decisions which directly affect the way the chain operates. Since the launch of mainnet in April of 2021, our stakeholders and validators have participated in the governance process which included proposals for software upgrades, parameter changes, and spending funds from the community pool. The basic principles of community governance are very simple. Anyone staking $REGEN is eligible to vote on and submit **proposals.** Proposals, including the process that leads up to the vote itself, are used to make changes to code & procedure, utilize Community Spend funds, elect community members to upgraded roles, and generally find consensus on questions facing the network. Proposals are the backbone of community governance. Below is the life cycle of the average proposal, though not every proposal will go through every stage. In certain circumstances, an emergency proposal may need to be submitted, such as to fix a security vulnerability or a critical bug in the software. In these cases the earlier stages of the proposal process may be omitted. ## Regen Network Proposal Guidelines While there are no official rules for submitting a proposal, Regen Network offers the below guidelines for maximum success. Proposals that do not follow these guidelines may be voted down on principle. * All proposals should first be socialized on the Regen Network [Governance Forum](https://commonwealth.im/regen) before they are submitted on chain (especially before the deposit is made, which will start the voting period). * When socializing a proposal, the forum post should include a rational for the proposal that weighs the potential pros and cons of the outcome and provides supporting documentation and examples when appropriate. * Once a forum discussion has started, a link to the discussion should be shared publicly on Telegram and Twitter (tagging [@regen\_network](https://twitter.com/regen_network)). * The time between socializing the proposal and submitting the proposal will vary depending on the proposal and community engagement but generally a proposal should be brought to discussion *at least* one-week before submitting the proposal on chain. ## Discussion Before an official proposal is submitted, it should first go through a community discussion period. This not only gets the community engaged in the topic before the one-week voting period, but also weeds out proposals likely to fail. The discussion period can also be used to gauge community sentiment regarding the finer details of the future proposal. For example, before [Proposal #3](/guides/network-governance/governance-basics/list-of-proposals#3-increase-max-validators-value) (Increase Validator Seats) was submitted as an on-chain proposal, it was discussed [here.](https://commonwealth.im/regen/discussion/3565-proposal-3-increase-validators-seats) The community member who submitted the discussion suggested increasing the number of new seats from 50 to 62, and asked if the community might be willing to increase that number even higher to 70 or 75. Ultimately, Proposal #3 increased the number of new validator seats from 50 to 75 as a direct result of this discussion. ## Submission & Voting After a proposal has been properly vetted by the community, it is ready to be submitted and sent to a vote as an on-chain proposal! ### Deposits Depending on the end goal of the proposal, either a [Text Proposal](/guides/network-governance/how-to-use-commonwealth/text-proposal) or a [Community Spend Proposal](/guides/network-governance/how-to-use-commonwealth/community-spend-proposal) should be submitted on Commonwealth. When submitting either proposal, a deposit of 2000 $REGEN is required to send it to a vote. This can be done with a single wallet at the time of submission or split between multiple wallets. When split between multiple wallets, the deposit amount must be submitted in full within 14 days of the proposals creation. Generally the deposit is returned to contributors after the vote has ended, though there are circumstances where those tokens are burned (destroyed to prevent future use). Deposits are burned if: * The deposit period expires before reaching the minimum deposit of 2000 $REGEN * The proposal fails to reach quorum meaning 40% or more of all staked $REGEN did not vote * Proposals were vetoed meaning 33.4% of voting power backed the ‘no-with-veto’ option ### Announcing the Submitted Proposal Getting the proposal out to the rest of the token holders is a very important part of getting a proposal passed. Even though there has been discussion on Discord and in the Commonwealth forum there may be some extra visibility necessary in order for validators and token holders to be made aware of the proposal. A new proposal should be posted/shared on the Discord server, social media, and respective blogs or websites. This will ensure maximum visibility and participation in voting. ### Voting Parameters On-chain proposals are open for voting for a one-week period and require a 40% quorum in order for the final vote to pass or fail. The voting power is determined by stake-weight (the amount of tokens a user has staked) at the end of the 7-day voting period and is proportional to the number of total $REGEN tokens participating in the vote. $REGEN tokens must be staked in order for them to count in the voting process as liquid tokens are not counted toward a vote or quorum. While both active (validators ranking in the top 75) and inactive validators may cast votes, inactive validators voting power will not count towards the final vote. *For this reason, it is important to determine whether or not the validator you have delegated to is in the active set, because your stake-weight may not be counted towards the vote if they aren’t.* Lastly, it’s also very important to note the ‘no-with-veto’ option. Even though a simple majority of 50% or greater is required, a minority group with just 33.4% or 1/3rd of the voting power can fail a proposal that would otherwise pass by voting ‘no-with-veto’ . It is important to pay attention to the[ voting details on Keplr](https://wallet.keplr.app/#/regen/governance) which allow you to view the percentage of vote types as a whole in order to gain a good understanding of whether a proposal will be vetoed and a deposit consequently burned. ## Implementation Assuming a proposal passes, the final step in its journey is implementation. This can include a distribution of allotted funds, a scheduled upgrade, a change in voting parameters, or a change/update in the codebase, etc. You can find a complete list of passed proposals in the next section, [List of Proposals](/guides/network-governance/governance-basics/list-of-proposals). # List of Proposals Explore all on-chain governance proposals for the Regen Network. [View all Regen proposals](https://www.mintscan.io/regen/proposals) on Mintscan, where you can view details about each proposal — including descriptions, voting periods, and results. Stay informed and participate in shaping the future of the Regen Network through decentralized governance. # Additional Resources Read more about the **Community Stake Model of governance** practiced by Regen Network in the blog, "[Community Stake Governance Model](https://medium.com/regen-network/community-stake-governance-model-b949bcb1eca3)". Learn more about **Cosmos governance** with this blog, "[Overview of Cosmos Governance](https://medium.com/stakin/overview-of-cosmos-governance-4184e930a25d)". Check out the latest happenings of **Regen Network governance** on our [Discourse Page](https://forum.regen.network/). # How to Use Commonwealth Commonwealth is an important tool for participating in community governance. This section provides step-by-step directions for the basic functions of the site. # Sign-up Step-by-step directions for signing up for Commonwealth This article provides directions for creating a Commonwealth account with your Keplr wallet, which will allow you to participate in community governance. If you do not already have a Keplr wallet set up, you can create one by following [these](/guides/wallets/wallet-setup/create-a-keplr-wallet) directions. ### 1. Access the [Regen Network Commonwealth Page](https://commonwealth.im/regen/) a. Follow the above link to view the Discussions page. ![](/files/NblUHvLA8rCd4bThyTWj) ### 2. Connect Keplr Wallet a. Click the "Log in" button indicated by the red arrow in the image above. It will generate the below pop out. ![](/files/wyfWrCLchtd2dQEr3jlb) b. Click the "Continue with wallet" option. c. A drop list of available wallets will appear. If you are only currently utilizing a Keplr wallet, Keplr will be the only option to appear. Click it. ![](/files/8xUBNRZjqpU566i25UPj) d. This will generate the below pop out. To connect your wallet, you must sign a transaction that does nothing. It will not be submitted to the chain. Click the Regen wallet address listed to start the transaction. ![](/files/3tQ8aPTNuuRRb6BnJXeB) e. A Keplr transaction window will appear. Click "Approve" to approve the transaction. ![](/files/RuQdEyMm59Fk3zRJgHna) ### 3. Add Account Details a. Once the transaction has competed you will be redirected to the following pop out. ![](/files/eCZJbmaq41Mx6Qy1ok8W) b. A name for your profile is required. A headline and bio are optional. If you do not select an image for your avatar, one will be assigned. c. Click "Save and finish" to complete the process. **Congrats! You are now a member of Regen Network community governance!** # Discussion Steps for commenting on a Commentwealth Discussion On chain proposals start life as a discussion on Commonwealth. This is a [suggested minimum one week discussion period](https://github.com/regen-network/governance) before a proposal is officially submitted, but two weeks of open discussion is more common. ## Participate in a Discussion ### 1. Access the [Regen Network Discussion Page](https://commonwealth.im/regen/) on Commonwealth a. You will need to be logged in to participate in a discussion. Confirm your account name is listed in the upper right hand corner and not a log in prompt. ![](/files/Kpuca7ZoFwvLBdCHJKcf) ### 2. Select a Discussion a. Select a discussion by clicking anywhere in its block. This will bring up the discussion's page. ![](/files/kL86XniGLgEHfs24HWEA) ### 3. Comment on the Main Thread a. To comment on the main thread, scroll down to the very bottom of the discussion's page. There you will find the below input window. ![](/files/GzwPRsBPVcjfSQCXVPUd) b. Add your comment to the text box and hit "Submit". ### 4. Comment on Other Comments a. To comment on other user's comments to the main thread or successive comments, click the comment button highlighted in red below. ![](/files/NnlnGLDWWtsMRNkht8hR) b. Add your comment to the box highlighted in green. Click "Submit" to submit your comment. ## Create a Discussion Discussions are most often used by our community to submit new governance proposals. However, this can also be used as a space for general community discussions or validator specific discussions. ### 1. Access the [Regen Network Discussion Page](https://commonwealth.im/regen/) on Commonwealth a. You will need to be logged in to participate in a discussion. Confirm your account name is listed in the upper right hand corner and not a log in prompt. ![](/files/Dh8X9jAkC8wXxrS4RPwz) ### 2. Create Discussion a. Click the "New thread" button indicated by the green arrow in the image above. It will prompt you to select a new thread or a new on-chain proposal. Click "New thread". ![](/files/tVAXabDWJM9XvvzwJSYS) b. You will be redirected to a form for your Discussion. For topic, you will most likely select "Governance". Provide your Discussion a title and thorough explanation of your proposal. Click "Save draft" to save a draft or "Create Thread" to submit your discussion. ![](/files/I5A00Q2VeoWosIaW2TBv) # Text Proposal Steps for submitting an on-chain text proposal on Commonwealth. Text proposals are the most basic form of proposal; they don't have any direct ramifications on the software. These are often called signalling propsals as they are largely used to poll for sentiment about a proposed change or course of action. *Note: On-chain proposals start life as a discussion on Comonwealth. There is a* [*suggested minimum one week discussion period*](https://github.com/regen-network/governance) *before a proposal is officially submitted, but two weeks of open discussion is more common. To submit a discussion follow the directions* [*here.*](/guides/network-governance/how-to-use-commonwealth/discussion#create-a-discussion) ### 1. Access the [Regen Network Discussion Page](https://commonwealth.im/regen/) on Commonwealth a. You will need to be logged in to create a proposal. Confirm your account name is listed in the upper right hand corner and not a log in prompt. ![](/files/Kpuca7ZoFwvLBdCHJKcf) ### 2. Create a New Thread a. Click the "New thread" button indicated by the green arrow in the image above. It will prompt you to select a new thread or a new on-chain proposal. Select "New On-Chain Proposal". ![](/files/kKc0IWXBLpBbALZhw69F) b. You will be redirected to a form for your Proposal. For "Proposal Type" select "Text Proposal". Provide your Proposal a title and a thorough description. The deposit amount is in **uregen** which is equal to one millionth of a $REGEN. 200 $REGEN is required to submit a proposal, or 200000000 uregen. ![](/files/VUMpQPTbX5O3JwqUnmxj) c. Click "Send transaction" to submit your proposal. You will be prompted to approve a transaction with your Keplr wallet and then Commonwealth will redirect you to the new proposal's page. # Community Spend Proposal Step-by-step directions for creating a Community Spend Proposal *Note: These are only the directions for creating a Community Spend Proposal on Commonwealth. The full process for requesting community funds can be found* [*here*](/guides/network-governance/community-spend-pool/how-to-request-community-pool-funds)*.* ### 1. Access the [Regen Network Discussion Page](https://commonwealth.im/regen/) on Commonwealth a. You will need to be logged in to create a proposal. Confirm your account name is listed in the upper right hand corner and not a log in prompt. ![](/files/Kpuca7ZoFwvLBdCHJKcf) ### 2. Create a New Thread a. Click the "New thread" button indicated by the green arrow in the image above. It will prompt you to select a new thread or a new on-chain proposal. Select "New On-Chain Proposal". ![](/files/kKc0IWXBLpBbALZhw69F) b. You will be redirected to a form for your Proposal. For "Proposal Type" select "Community Spend". Provide your Proposal a title and a thorough description. The deposit amount is in uregen and six zeros will need to be added to the amount of $REGEN being used. 200 $REGEN is required to submit a proposal, or 200000000 uregen. For "Recipient", provide the Regen wallet address the funds should go to and for "Amount" provide the amount to be allocated. ![](/files/7G5eiA9amHxWeuwK9AOn) c. Click "Send transaction" to submit your proposal. You will be prompted to approve a transaction with your Keplr wallet and then Commonwealth will redirect you to the new proposal's page. # Voting A step-by-step guide for voting on on-chain proposals For token holders, Commonwealth voting is a key function. You can either do this yourself or delegate to a validator. ### 1. Access the [Regen Network Proposals Page](https://commonwealth.im/regen/proposals) on Commonwealth a. You will need to be logged in to vote on a proposal. Confirm your account name is listed in the upper right hand corner and not a log in prompt. ### 2. Select a Proposal a. Proposals currently in the voting period will appear in the "Active" section of the Proposals page. Click on the proposal you would like to vote on. You will be redirected to the proposal's page where you can read the details of the proposal. ![](/files/eJAcAvdqvA4orCUQ62Yt) ### 3. Vote on the Proposal a. Once you have read through the proposal, you may cast your vote in one of four categories. 1. **Yes** - the proposal is agreeable. 2. **No** - the proposal is disagreeable. 3. **Abstain** - engaged with the proposal but no opinion for or against. 4. **Veto** - the proposal is disagreeable and the poster of the proposal loses their deposit. *Note: Voting Veto on a proposal is typically used when a proposal skips the discussion period and is put straight on the chain. There are some exceptions to this norm for urgent matters, such as security issues.* ![](/files/oWURy0ozn4QDo2ugqs6z) b. Select your vote of choice and approve the resulting Keplr transaction. ![](/files/dhfpj0pBrSVU6DDFSCrF) ### 4. Monitor Proposal for Outcome a. Check back into the proposal's page to monitor its status as it moves through the voting period. # Community Spend Pool # About A brief overview of the Regen Network Community Spend Pool At the genesis launch of [Regen Network](https://regen.network/), a community pool was established. The pool is funded by token inflation in the form of a two percent tax. This means that if the current inflation is 20%, 2% goes into the community pool and the remaining 98% is distributed to the rest of the network. The community pool currently contains over 2M $REGEN that may be used as the community sees fit. Projects wishing to use community fund pools must go through the proposal process, which culminates in a community vote. The community spend pool has most recently been used to offset Regen Network's validator set as part of the [Cosmos ZERO](https://www.notion.so/Cosmos-ZERO-Achieve-protocol-net-zero-carbon-emissions-while-building-a-carbon-market-in-Cosmos-ddd441e3ff3d4dbda83265433843ec10) initiative. Cosmos ZERO is a partnership of the Interchain Foundation and the Cosmos community devised in October of 2021, and an initiative for Cosmos protocols and validators to achieve net-zero carbon emissions for their network validator node infrastructure and operations. [Proposal 21](https://forum.regen.network/proposal/21-signal-proposal-offset-regen-validator-set) was a signaling proposal for Regen Network to offset the validator carbon footprint with community funds and established which credits would be used for the offset. Proposals [23](https://forum.regen.network/proposal/23-proceed-with-city-forest-credits-offset), [25](https://forum.regen.network/proposal/25-allocate-the-missing-regen-for-city-forest-credits-offset), and [30](https://forum.regen.network/proposal/30-required-final-offset-amount-community-spend-proposal-for-purchasing-and-retiring-nct) were community spend proposals that allocated the appropriate funds to a wallet where they were used to purchase and retire ecocredits from the Regen Marketplace. # How to Request Community Pool Funds How to request community pool funds for your own project As with most things within Regen Network, someone wanting to gain access to a portion of the pool must petition the community through our governance process. You can read a more in-depth article on Regen Network governance in the [About](/guides/network-governance/governance-basics/about) article of Governance Basics, but below you will find the steps necessary to request use of these community funds. *Note: When beginning the process, you will want to have a solid use case for the funds and a good understanding of how the funds will be used as the community will be very interested in this information. It is also important to provide a transparent team bio. The community will want to know who you are and what credentials you have. It is a good idea to have a website which includes a team bio and a clear description of the project.* ## [Discord](https://discord.gg/guw5TGzCFR) — Introduction The first place to start this process is in our [Discord](https://discord.gg/guw5TGzCFR) server where much of our community lives. Introduce yourself there, give an overview of your project, reach out to other community members and make yourself available for questions. Our community is filled with a variety of members with varying skills where you can find scientists, software developers, farmers, and a number of other humans interested in planetary regeneration. This step is one of the most important ones when petitioning for funds from the community pool. The community will want to chat with you and may even be interested in helping out. Anyone requesting funds from the community pool should engage with community members on Discord and once you feel you have rallied enough support in the server you can move to submitting a discussion on [Commonwealth](https://commonwealth.im/regen/). ## [Commonwealth Forum](https://commonwealth.im/regen) — Discussion Submitting a discussion on the Commonwealth forum is a necessary step in gaining support for your on-chain proposal. This is where you will receive the majority of questions and input from the community stakeholders and validators who will eventually vote on the proposal to either accept or reject your request for funds. [How to submit a Discussion on Commonwealth](/guides/network-governance/how-to-use-commonwealth/discussion) ➡️ Please take a look at [these proposals](https://commonwealth.im/regen/proposal/12-climate-wiki-community-pool-funding) to get a good understanding of how to format your discussion. At the very least, you will want to include the following sections in your discussion: * Project Introduction * The amount of funds being requested * Transparency commitment * Links to budgets and other accounting documentation * Link to project website * Team member bios * Any other useful information Your discussion should be open for at least one week, to allow all community members a chance to chime in. If it looks like the community is in favor of your discussion, you may move forward with submitting an official community spend proposal! ## [Commonwealth Proposal](https://commonwealth.im/regen/proposals) - Official Proposal The next step in this process is submitting the official community spend proposal! [How to submit a community spend proposal on Commonwealth](/guides/network-governance/how-to-use-commonwealth/community-spend-proposal) ➡️ This final iteration of your proposal will probably look very similar to the discussion, though you may include changes as a result of the community discussion. Once your proposal has been submitted, and the deposit met, the one-week voting period will officially begin! ## Promote Proposal As soon as your proposal has been officially posted, you will want to promote it to the best of your abilities. 40% of $REGEN stakeholders must vote on a proposal for it to pass. This means even if everyone votes yes on your proposal, it can still fail if not enough community members participate in the vote. The [Regen Network Discord](https://discord.gg/guw5TGzCFR) and [Regen Network Telegram](https://t.me/regennetwork_public) are good platforms for bringing your proposal to the eyes of our active community members. We also encourage sharing your proposal on social media and any relevant blogs or websites. # Cosmos Ecosystem This section of the guide provides a high level overview of blockchain technology and Cosmos. # Blockchain Basics # Glossary of Terms Useful terms for discussing and defining blockchain technology #### **Blockchain** At its core, a blockchain is a distributed and immutable database. Participating validators (nodes or computers) in the network store a growing list of records, also called *blocks*. Each new block contains information about the previous blocks, creating a chain of data. Changes cannot be made to one block of data without also altering every subsequent block. #### **Smart Contracts** Smart contracts are programs built on a blockchain that run automatically when its conditions are met. Other blockchain environments use smart contracts (rather than an application specific blockchain, like on Cosmos) to run the dApps associated with it. #### Application Specific Blockchain Application specific blockchains are chains designed and built to run a specific app. This is in contrast to smart contracts, which traditional blockchain protocols use to run decentralized apps. #### **Consensus mechanism** In order for a blockchain to be useful, the validators in the network must be able to agree to a single version of the collated data. The term consensus mechanism refers to the method by which the validators reach that agreement. Consensus mechanisms are a safety measure against potentially faulty data and potentially malicious validators. #### **BFT consensus algorithm** BFT stands for Byzantine Fault-Tolerance. A Byzantine Fault-Tolerant consensus algorithm guarantees safety against up to a third of Byzantine, or malicious, validators. At this threshold, a chain using BFT consensus will halt to prevent further corruption. #### **Proof-of-Work** The original consensus mechanism was introduced by Bitcoin and is known as Proof-of-Work (PoW). This consensus mechanism requires validators in its network to complete complex computational problems, "work", before it can contribute to the chain. This provides chain safety by making the cost of taking over the network (running enough malicious validators to reach consensus) more than any potential gains that could be earned. However, this "work" also makes PoW slower than other consensus mechanism. #### **Proof-of-Stake** Proof-of-Stake (PoS) is a consensus mechanism that only requires validators in its network have tokens staked on the chain. This makes it much faster than the PoW model, as no additional work is required. Staked tokens serve as collateral against malicious attacks by requiring network validators to have a financial interest in the chain. Potentially faulty or malicious validators are "slashed" and their staked tokens are lost. In a traditional PoS, network validators are chosen based on various criteria from the pool of available validators. #### **Delegated Proof-of-Stake** Delegated Proof-of-Stake (dPoS) seeks to solve some of the social issues created by PoS. Because the chain's safety relies on using validators with a financial stake in the chain, many PoS algorithms will favor wealthier validators, those with more staked tokens. dPoS removes this factor by using only a set of active validators. Validators chosen for the active set are voted on by the community in the form of staked tokens, delegated to the validator of choice. #### **IBC** IBC refers to Inter-Blockchain Communication Protocol. This is a key component of the Cosmos ecosystem as it allows the transference of data between different chains. # Additional Resources Learn more about the **benefits of blockchain** in [this guide](https://www.ibm.com/topics/benefits-of-blockchain#:~:text=Blockchain%20increases%20trust%2C%20security%2C%20transparency,cost%20savings%20with%20new%20efficiencies.\&text=Blockchain%20for%20business%20uses%20a,accessed%20by%20members%20with%20permission.) written by IBM. If you'd like to learn more about **blockchain at a technical level**, you can start on the Cosmos website with ["What is a Blockchain?"](https://v1.cosmos.network/intro#what-is-a-blockchain) If you'd like to deep dive into the **differences between dPoS and PoS**, read ["What Are Proof of Stake and Delegated Proof of Stake?"](https://www.gemini.com/cryptopedia/proof-of-stake-delegated-pos-dpos) published by Cryptopedia. Interested in learning more about **Inter-Blockchain Communication Protocol**? Check out [their website](https://ibcprotocol.org/). # Cosmos Basics # About A quick overview to the Cosmos Ecosystem [*Cosmos*](https://cosmos.network/) *is a decentralized network of independent parallel blockchains, each powered by* [*Tendermint*](https://docs.tendermint.com/v0.34/introduction/quick-start.html)*'s* [*BFT*](/guides/cosmos-ecosystem/blockchain-basics/glossary-of-terms#bft-consensus-algorithm) *consensus algorithm.* Prior to Cosmos, blockchains operated independently with decentralized Apps (dApps) written as [smart contracts](/guides/cosmos-ecosystem/blockchain-basics/glossary-of-terms#smart-contracts) on top. However, thanks to the open source tools implemented by Cosmos, Tendermint, [Cosmos SDK](https://v1.cosmos.network/sdk), and [IBC](https://ibcprotocol.org/), blockchain developers are enabled to easily build high performing and secure blockchains that can scale and interoperate with others in the Cosmos ecosystem. Cosmos marries the spirit of collaboration to the innovation of blockchain. Developers within the Cosmos community are encouraged to improve existing tools and create new ones in order to fulfill the promise of blockchain technology. # Cosmos SDK This article provides a brief overview of Cosmos SDK. *The* [*Cosmos SDK*](https://github.com/cosmos/cosmos-sdk) *is an open-source framework for building multi-asset public* [*Delegated Proof-of-Stake (dPoS)*](/guides/cosmos-ecosystem/blockchain-basics/glossary-of-terms#delegated-proof-of-stake) *blockchains, like the Cosmos Hub, as well as permissioned Proof-of-Authority (PoA) blockchains.* The goal of the Cosmos SDK is to allow developers to easily launch custom blockchains that can natively interoperate with other Cosmos blockchains. Blockchains built with the Cosmos SDK are generally referred to as [application-specific blockchains](/guides/cosmos-ecosystem/blockchain-basics/glossary-of-terms#application-specific-blockchain). In the traditional blockchain model, decentralized Apps (dApps) are built on top of an existing blockchain as a set of programs called a [smart contracts](/guides/cosmos-ecosystem/blockchain-basics/glossary-of-terms#smart-contracts). This model can be very limiting, and often falls short for building complex decentralized platforms. An application-specific blockchain is a blockchain customized to operate a single application: developers have all the freedom to make the design decisions required for the application to run optimally. Building applications this way provides more flexibility to the developers, and can increase performance, sovereignty and security. {% hint style="info" %} Fun fact: Cosmos SDK is maintained in part by a group of developers at Regen Network Development, Inc (RND)! {% endhint %} # What is Dao Dao? ## What is DAO DAO? **DAO DAO** is the underlying governance and permission system that powers organizations and collaborative projects in the Regen App. When you create an **organization**, it is represented on-chain as a **DAO** (Decentralized Autonomous Organization). Likewise, every **project created within an organization** also becomes a DAO. This enables teams to manage members, permissions, and funds collectively and transparently on-chain. However, if you create a **project under a single user account** — not linked to an organization — that project does **not** become a DAO. It remains managed solely by that user, either on or off-chain, until it’s later associated with an organization. The Regen App provides a **simple interface** for managing your organization and projects, while **DAO DAO** provides the on-chain infrastructure that ensures security, transparency, and shared ownership. *** ### Why DAO DAO? DAO DAO ensures that every collaborative action in the Regen ecosystem is **secure, transparent, and role-based**.\ It powers all organization and project DAOs behind the scenes, enabling: * Collective ownership of assets (credits, tokens, NFTs) * Role-based permission management (RBAM) * On-chain execution of standard operations without requiring votes * Optional governance tools for major organizational decisions In other words:\ ➡️ **Regen App** makes it easy for you to manage your team and projects.\ ➡️ **DAO DAO** ensures that everything happens securely and transparently on-chain. *** ### What You Can Do: Regen App vs DAO DAO app | **Action** | **Regen App** | **DAO DAO (daodao.zone)** | | ----------------------------------------------- | ------------------------------------------------ | ------------------------------------------------------------------- | | **Create and manage your organization** | ✅ Yes — with guided setup and profile management | ✅ Yes — with full DAO creation and customization options | | **Add, remove, and manage members** | ✅ Yes — via the Members tab | ✅ Yes — advanced role and authorization management through RBAM | | **Assign roles (Owner, Admin, Editor, Viewer)** | ✅ Yes — intuitive in-app role picker | ✅ Yes — create, edit, and manage any roles and permissions manually | | **Create and manage projects** | ✅ Yes — directly in the app | ✅ Yes — for projects that exist as DAOs under an organization | | **Create projects under a single user account** | ✅ Yes — but these are *not* DAOs | 🚫 No — can only create project DAOs linked to an organization | | **Edit organization or project profiles** | ✅ Yes — easy off-chain editing | 🚫 Not available — profile content is managed through the Regen App | | **Manage credits (send, retire, sell)** | ✅ Yes — streamlined credit management | ✅ Yes — advanced treasury and asset management | | **Create proposals and vote on decisions** | 🚫 Not in-app | ✅ Yes — full on-chain governance and proposal system | | **Manage treasury funds and DAO assets** | 🚫 Not in-app | ✅ Yes — control and track treasury activity directly | | **Create SubDAOs for teams or working groups** | 🚫 Not in-app | ✅ Yes — supports advanced organizational structures | | **Customize governance settings** | 🚫 Default setup only | ✅ Yes — flexible thresholds, tokens, and policies | | **Cross-chain operations** | 🚫 Not supported | ✅ Yes — available for advanced users | | **Token creation and distribution** | 🚫 Not supported | ✅ Yes — mint and distribute DAO tokens | *** ### How the Two Work Together You can think of it like this: * The **Regen App** is your main workspace — where you create organizations, manage projects, invite team members, and handle credits. * **DAO DAO** is the underlying on-chain system — it ensures that everything your organization and its projects do is transparent, verifiable, and collectively managed. If you’re part of an organization, you can always open your DAO directly in the [DAO DAO](https://daodao.zone) app to explore proposals, governance settings, and treasury management. Projects created under **your personal account** are not part of a DAO until you associate them with an organization, at which point they gain DAO capabilities automatically. *** ### Learn More * [**Create an Organization**](/guides/regen-app-project-developers-and-land-stewards/organizations/create-an-organization) — Set up a new organization and profile to represent your team. * [**Manage Organization Members**](/guides/regen-app-project-developers-and-land-stewards/organizations/manage-organization-members) — Add, remove, or update team members and their roles. * [**Manage Project Collaborators**](/guides/regen-app-project-developers-and-land-stewards/organizations/manage-project-collaborators) — Control who can access and contribute to individual projects. # Additional Resources ## For more information about Cosmos: Ease into a more thorough explanation of the **Cosmos ecosystem** with this blog, "[Cosmos 'The Internet of Blockchains' an Introduction](https://medium.com/stakin/cosmos-the-internet-of-blockchains-an-introduction-868e9a1855e3)". Deep dive into **Cosmos technology** with "[How does Cosmos fit in the broader blockchain ecosystem?](https://v1.cosmos.network/intro#how-does-cosmos-fit-in-the-broader-blockchain-ecosystem)" Finally, don't forget to peruse [Cosmos website](https://cosmos.network/)! While you're there, check out the [projects that make up the Cosmos ecosystem](https://cosmos.network/ecosystem/apps). ## For more information about the Cosmos SDK: Read the **high level overview of the Cosmos SDK** found on their[ GitHub](https://github.com/cosmos/cosmos-sdk/blob/main/docs/intro/overview.md). Deep dive into **how the Cosmos SDK works with Tendermint BFT** in "[CosmosSDK and other application layer frameworks](https://v1.cosmos.network/intro#cosmos-sdk-and-other-application-layer-frameworks)". **Use Cosmos SDK** to build your own dApp with their [documentation and tutorials](https://docs.cosmos.network/). # Introduction Welcome to the **Regen Ledger & Application Architecture Guide** — the central reference for developers, partners, and product teams building on or integrating with Regen Network’s ecological accounting infrastructure. This documentation explains how Regen’s technical stack works — from the on-chain registry and crediting logic to the linked data metadata standards (JSON-LD, RDF, IRIs) that power the Regen App and related APIs. It also serves as a starting point for developers who want to query data, build new interfaces, or contribute to our open-source standards for ecological project information. ### **Who This Guide Is For** This documentation is intended for: * **Developers** building tools that query or visualize data from Regen Ledger. * **Partners and registries** integrating Regen data into regulated systems or reporting instruments. * **Researchers and data scientists** exploring linked ecological datasets using RDF, SPARQL, or JSON-LD. * **Methodologists and standards contributors** working with the Framework Working Group (FWG) to define interoperable metadata schemas. ### **How to Use This Documentation** This guide is organized into modular sections that you can read independently or in sequence: 1. **Getting Started** — overview of tools, APIs, and network access. 2. **Architecture Overview** — where information lives (on-chain, metadata, app). 3. **Regen Ledger** — modules, data model, and API queries. 4. **Metadata** — how linked data and IRIs structure project information. 5. **Retrieving Data** — end-to-end flow: project ID → IRI → JSON-LD. 6. **Framework WG Standards** — ongoing work to formalize metadata schemas. 7. **Reference & Examples** — sample queries, JSON-LD fragments, and developer tools. Each section builds on the previous one but can stand alone for quick reference. ### **Contacting Support** If you need help connecting to a Regen node, resolving IRIs, or contributing to our metadata standards: * **Developer Support:** # Overview & Architecture Regen Network's architecture connects blockchain-based state with semantic metadata and modular application layers for displaying and sharing ecological data. Together, these components form a *registry system* which prioritizes interoperability, transparency, and long-term verifiability of climate and ecosystem claims. ## System Design Regen’s architecture is guided by several core principles that ensure integrity, inclusivity, and adaptability across the ecosystem. * **Transparency** — The system uses **public ledger** to establish integrity and provenance. Users anchor canonical registry actions—credit issuance and transfers, project registrations, governance, marketplace activity, and attestations—cryptographically on-chain to create an immutable, timestamped reference for each claim or dataset, so anyone can independently verify that off-chain content matches its on-chain commitment. * **Interoperability** — The system stores information as linked data, emphasizing relationships—how projects, methods, evidence, places, and outcomes connect—rather than isolated tables. Shared vocabularies and standardized schemas makes datasets composable across systems so independent apps can publish and query ecological data without bespoke integrations. * **Extensibility** — Applications can query, cache, and present registry information without running full nodes or duplicating backend logic. Public indexing and resolution services connect on-chain state with referenced metadata, letting multiple apps build on the same verifiable dataset—supporting bioregional registries, impact dashboards, or marketplaces with minimal overhead. * **Data Privacy & Soverignty** — The system should support public verifiability while protecting sensitive information. Contributors can keep raw data permissioned or off-chain, while exposing only cryptographic proofs and descriptive metadata. This balances integrity, privacy, and community control over data access. ## Architecture Overview The system comprises four interconnected layers, each serving a distinct role while remaining modular for flexible integration:
* **Regen Ledger** Serves as the verifiable integrity and provenance backbone. Rather than functioning as a full data store, the ledger acts as the **trust anchor**—ensuring that every claim, transaction, or governance action traces back to an immutable, timestamped, and verifiable on-chain reference.\ It records all stateful information (credit classes, projects, batches, ownership, retirements, marketplace orders, governance proposals) and stores immutable references (IRIs) to associated metadata with cryptographic proofs, allowing anyone to validate metadata against its on-chain hash. * **Indexers** Listen to events from Regen Ledger and mirror them into structured databases for fast querying. This layer handles metadata resolution and caching, fetching RDF datasets, documents, or retirement information from IPFS or HTTPS endpoints, validating their hashes, and connecting on-chain state to its off-chain context. * **Storage** manages persistent off-chain data: metadata files, supporting documentation, evidence, and media assets. This includes databases for indexed data, IPFS for distributed file storage, and RDF graph stores for semantic queries via SPARQL. * **Applications** consume indexed and resolved data to create end-user experiences. The Regen App is the primary example, providing registry search, project views, and retirement certificates. Other developers can use the same data surfaces to build bioregional registries, dashboards, or marketplaces. These layers work together but remain independent—applications don't depend on specific indexer implementations, indexers don't dictate storage formats, and everything ultimately verifies against the same ledger state. This modularity means developers can integrate at any level: query the ledger directly for maximum trust, use indexer APIs for convenience, or build entirely new interfaces on top of shared, verifiable data. # Core Concepts # Regen Ledger The Regen Ledger forms the foundation of Regen Network’s technical architecture. It provides the verifiable on-chain state that underpins all ecological accounting, ensuring each project, credit, and claim can be independently validated through a transparent and immutable record. Rather than serving as a full data repository, it acts as a trust and provenance layer, recording canonical registry data and cryptographic commitments to off-chain content. ## **Architecture & Core Modules**

Regen Ledger architecture showing Cosmos SDK core modules, Regen-developed extensions, and smart contracting layer.

Built on the Cosmos SDK, Regen Ledger leverages its modular framework to implement custom logic for ecological crediting and data anchoring while maintaining compatibility with interchain standards. Regen Ledger extends the base SDK with custom modules for ecological crediting and metadata management, alongside standard Cosmos modules for core blockchain operations. The table below describes the most commonly used modules.
ModulePurposeDeveloped By
EcocreditCore registry logic for credit classes, projects, batches, issuance, retirements, and internal marketplace operations.Regen Network
DataAnchors external metadata and evidence using IRIs, enabling verifiable off-chain storage and retrieval.Regen Network
FeegrantAllows one account to pay transaction fees for another, supporting delegated operations and more accessible participation.Cosmos SDK
AuthzProvides delegated authorization for users or agents to perform actions on behalf of another account.Cosmos SDK
BankHandles token balances, transfers, and escrow for credit transactions.Cosmos SDK
GovManages on-chain proposals, parameter changes, and protocol-level voting.Cosmos SDK
Staking / Slashing / DistributionCore SDK modules ensuring validator security, consensus, and network reward distribution.Cosmos SDK
{% hint style="info" %} For a full list of modules and technical specifications, see the [Regen Ledger Docs](https://docs.regen.network/). {% endhint %} *** ## **DAO and Governance Integration** Regen Ledger integrates with **DAODAO**, a **CosmWasm-based governance framework** that provides the tooling and functionality for groups and organizations to coordinate decision-making around credit classes, community funds, and project-level governance. Through DAODAO, DAOs can: * Create and manage multi-signature treasuries. * Propose and vote on registry or funding actions. * Execute smart contract–based decisions that interact directly with ledger state. This integration extends Regen’s native governance capabilities, allowing decentralized participation in ecological asset management and network upgrades while maintaining transparent, verifiable decision trails. *** ### **Access and Queries** These endpoints are the same surfaces used by Regen’s indexers and applications, such as the Regen App, to stay synchronized with live state updates. * **gRPC Endpoints** — Structured, performant queries for applications and indexers. * **REST API** — Human-readable HTTP endpoints for direct developer use. * **CLI Commands** — Full control for validators, agents, and power users. Typical queries include retrieving project or credit class details, verifying metadata IRIs, and confirming ownership or retirement records. {% hint style="info" %} For detailed API references and more information about Regen Ledger, visit the [Regen Ledger Documentation](https://docs.regen.network/). {% endhint %} # Metadata Metadata provides the **semantic context** that gives meaning to on-chain registry records. Where the Regen Ledger captures canonical state—credit classes, projects, batches, issuances, transfers, and retirements—metadata describes **what those records represent** and the **relationships between them**. In the Regen Network Ecosystem, metadata acts as the connective tissue between projects, credits, claims, and evidence to facilitate the creation of machine-readable knowledge graphs that support advanced queries, interoperability, and transparency across applications and initiatives. *** ### **How Metadata is Used** Metadata plays several essential roles throughout the registry system, describing core entities, connecting ecological claims to evidence, and supporting application features and governance processes. * **Credit Classes, Projects, and Credit Batches:** Metadata captures and organizes essential information about credit protocols, projects, and credit batches—defining issuance requirements and processes, documenting project characteristics and impacts, and tracking credit batch states through their lifecycle from protocol definition to credit retirement. * **Data, Claims, and Evidence:** Metadata structures the relationship between ecological claims and their supporting evidence. Metadata constructed in RDF and attached to an **anchor event** using the regen data module can creates a verifiable chain linking the claim to specific pieces of evidence, verification processes, and outcomes also anchored with RDF metadata sets. This chain remains intact and queryable even when the underlying evidence data is permissioned or private, providing transparency around the verification process while respecting data sovereignty. * **Governance Decisions:** Metadata captures the governance processes and decisions that affect protocols, projects, and credits. This includes recording proposal submissions, voting outcomes, and parameter changes. The metadata creates an auditable trail of decision-making that helps establish legitimacy and enables stakeholders to understand how and why changes were made. *** ### **IRIs, Metadata, & the Ledger** #### **International Resource Identifiers (IRIs)** The Regen Ledger does not store metadata directly. Instead, it stores **content-addressed identifiers—Internationalized Resource Identifiers (IRIs)**—that point to metadata stored off-chain. An IRI acts as a cryptographically derived fingerprint of the metadata document it represents. When metadata content changes, a new IRI is generated, creating an immutable reference to the updated content while preserving access to historical versions. Metadata documents themselves are stored off-chain in locations such as IPFS, Postgres databases, or custom storage solutions. They can be stored in various formats (though JSON-LD is commonly used in the Regen ecosystem) and may include rich structured information such as ecological classifications, SDG mappings, monitoring protocols, stakeholder profiles, and verification details. This architecture preserves data integrity through cryptographic verification while enabling privacy controls, version history, and distributed contribution—all while keeping the ledger lightweight and verifiable. #### **How Metadata Is Used in the Ecocredit Module** The *ecocredit module* includes a `metadata` field that can store an IRI. These IRIs act as stable pointers linking on-chain entities to their semantic descriptions: * **Credit Classes** typically use this field to reference metadata describing protocol details, methodology requirements, eligible activities, governance parameters, and credit type definitions. * **Projects** typically used to reference metadata containing geographic extent, ecosystem characteristics, participant information, management actions, and project-specific context. * **Credit Batches** typically used to reference verification results, monitoring periods, vintage information, ecological claims, and the specific outcomes that justified issuance. Beyond the ecocredit module, IRIs appear throughout the registry: governance proposals reference metadata, the data module anchors metadata for datasets and claims, and project updates generate new IRIs that link to previous ones. This creates a cohesive semantic layer across the system. *** ### **Resource Description Framework (RDF)** The Resource Description Framework (RDF) provides the foundation for Regen's metadata architecture. RDF is a standard model for representing and describing resources on the web using a simple, graph-based structure that expresses data in triples. Each triple consists of: * **Subject**: The resource being described (e.g., "Project A", "Evidence B") * **Predicate**: The property or relationship of the resource (e.g., "has location," "authored by") * **Object**: The value or target of the relationship (e.g., "Colombia," "Terrasos") This simple but powerful structure allows complex relationships between different pieces of information to be expressed in a consistent, machine-readable way. Its graph-based model and use of unique identifiers enable rich semantic relationships and scalability, making it ideal for building linked data applications. Rather than storing isolated attributes, RDF emphasizes how information connects—projects to locations, locations to ecosystems, claims to evidence. The result is a semantic graph that supports sophisticated queries, automated reasoning, and cross-dataset interoperability. Full details on RDF vocabularies, schemas, data types, and implementation conventions appear in the Data Standards & Framework section. *** ### **Metadata Graph API** The Metadata Graph API provides a unified interface for retrieving and generating metadata via IRIs. Applications, indexers, and external tools rely on the API to resolve, traverse, and construct metadata graphs. **Key endpoints:** `GET /data/v2/metadata-graph/{iri}` Resolves an IRI and returns the corresponding metadata graph (typically in JSON-LD). The API handles resolver backends such as IPFS and HTTPS, abstracting away storage details. `POST /data/v2/iri-gen` Accepts a metadata document and returns the deterministically generated IRI for that content. Used when creating new projects, credit classes, claims, evidence references, or project updates. These endpoints allow applications—including the Regen App—to construct, publish, and display linked metadata without managing storage or hashing logic directly. For full Swagger specifications, see the [Metadata Graph API Docs](https://api.registry.regen.network/api-docs/#/metadata%20graph). *** ### **Why Metadata is Important** Metadata forms the foundation for trust and transparency in environmental markets by creating verifiable chains of evidence that stakeholders can track and audit. The public nature of metadata, even when underlying data is private, enables verification of claims while respecting data sovereignty and privacy requirements. * **Interoperability:** The standardized structure of metadata enables interoperability between different organizations and systems. As environmental markets evolve and expand, this interoperability becomes crucial for sharing and validating information across platforms while maintaining data integrity and provenance. * **Knowledge Graphs Creation & Advanced Queries:** Well-structured metadata also enables the creation of knowledge graphs that reveal patterns and insights about ecological systems and interventions. These knowledge graphs support sophisticated queries that can track relationships between different types of data, claims, and evidence across the system. For example, users can explore connections between specific conservation practices and biodiversity outcomes or analyze the effectiveness of different verification approaches. # Data Access & APIs Regen’s data access layer exposes registry information through a combination of **metadata resolution APIs** and **indexed application APIs**. Together, these interfaces allow developers to retrieve the metadata associated with credit classes, projects, and credit batches, as well as the off-chain information about projects, and retirement certificates stored the Regen Application server and indexing backend. This section provides the essential endpoints for accessing registry data in the current version of the system. # Anchored Metadata For credit classes, projects, and credit batches, the `metadata` field in the ecocredit module holds an IRI that points to an off-chain JSON-LD document. Metadata for these entities is accessed the same way: 1. **Query the Ledger** (via gRPC, REST, or CLI) to retrieve the entity's metadata IRI 2. **Resolve the IRI** using the Metadata Graph API to retrieve the full JSON-LD document 3. **Interpret the JSON-LD** as linked data describing the entity's attributes, relationships, and supporting documents {% hint style="info" %} The Regen Network Framework Working Group's is currently finalizing a RDF standardization for credit classes, project, credit batches and more. Once complete **all metadata documents will share a standardized structure**, making them predictable, machine-readable, and interoperable across applications. {% endhint %} ### Retrieving Metadata IRIs from the Ledger Each entity stores its metadata reference in a `metadata` field within the ecocredit module. Ledger queries return a string like: ``` regen:13toVh9VgHfMJUDXSFTMQiDwRtiWQvhyeBpZe3jYpGMRnkZZB7jQyN8.rdf ``` This IRI is a deterministic, content-addressed identifier for the full metadata document. ### Resolving IRIs via the Metadata Graph API Use the Metadata Graph API to resolve any IRI: ``` GET https://api.regen.network/data/v2/metadata-graph/{iri} ``` The API automatically retrieves content from IPFS, HTTPS endpoints, or other configured resolvers and returns a JSON-LD document containing the complete semantic structure: context, types, relationships, and links to supporting evidence. For full API specifications, see the [Metadata Graph API Swagger docs](https://api.regen.network/swagger/). ### JSON-LD Response Examples #### Credit Class Metadata Credit class metadata describes the protocol itself—methodology, eligible activities, impact categories, and governance structure. **Request:** ``` GET https://api.regen.network/data/v2/metadata-graph/regen:...class-iri....rdf ``` **Response (excerpt):** json {% code overflow="wrap" expandable="true" %} ```json { "@type": "regen:USS-CreditClass", "@context": { "regen": "https://schema.regen.network#", "schema": "http://schema.org/", "schema:url": { "@type": "schema:URL" }, "regen:coBenefits": { "@container": "@list" }, "regen:creditingTerm": { "@type": "schema:Duration" } }, "schema:name": "Biodiversity Credit Protocol for Umbrella Species Stewardship", "schema:url": "https://www.registry.regen.network/crediting-protocols/era-brazil", "schema:description": "The Biodiversity Crediting Protocol for Umbrella Species Stewardship (USS) provides...", "regen:creditingTerm": "P5Y", "regen:ecosystemType": ["Terrestrial"], "regen:primaryImpact": { "@id": "regen:Improved-Biodiversity", "schema:name": "Improved Biodiversity", "regen:SDGs": [ { "@id": "regen:15LifeOnLand" }, { "@id": "regen:13ClimateAction" } ] }, "regen:eligibleActivities": [ "Umbrella Species Conservation", "Ecosystem Restoration", "Ecotourism" ] } ``` {% endcode %} **Typical fields:** protocol name and description, crediting term, ecosystem types, primary impact with SDG mappings, eligible activities, applicable regions, and links to methodology documents. *** #### Project Metadata Project metadata describes the specific implementation—location, stakeholders, ecosystem characteristics, and activities. **Request:** ``` GET https://api.regen.network/data/v2/metadata-graph/regen:...project-iri....rdf ``` **Response (excerpt):** json {% code overflow="wrap" expandable="true" %} ```json { "@id": "https://app.regen.network/project/USS01-001", "@type": "regen:USS01-Project", "@context": { "regen": "https://schema.regen.network#", "schema": "http://schema.org/", "geojson": "https://purl.org/geojson/vocab#", "schema:location": { "@context": { "@vocab": "https://purl.org/geojson/vocab#", "coordinates": { "@container": "@list" } } }, "regen:coBenefits": { "@container": "@list" } }, "schema:name": "Jaguar Stewardship in the Pantanal Conservation Network", "schema:location": { "type": "Feature", "geometry": { "type": "Point", "coordinates": [-57.489822, -18.040224] }, "place_name": "Serra do Amolar, Corumbá, Mato Grosso do Sul, Brazil" }, "schema:description": "The Instituto Homem Pantaneiro (IHP) is an NGO dedicated to preserving the Brazilian Pantanal biome...", "regen:projectSize": { "qudt:unit": "unit:HA", "qudt:numericValue": 40613 }, "regen:ecosystemType": ["Tropical Wetlands"], "regen:projectDeveloper": { "@type": "regen:Organization", "schema:name": "ERA Brazil" }, "regen:projectOperator": { "@type": "regen:Organization", "schema:name": "Instituto Homem Pantaneiro" } } ``` {% endcode %} **Typical fields:** name and description, geographic location (GeoJSON), project size, ecosystem type, project developer/operator/monitor/verifier, co-benefits, activities, media assets, and start/end dates. *** #### Credit Batch Metadata Credit batch metadata documents the issuance event—monitoring reports, verification reports, and supporting evidence. **Request:** ``` GET https://api.regen.network/data/v2/metadata-graph/regen:...batch-iri....rdf ``` **Response (excerpt):** json {% code overflow="wrap" expandable="true" %} ```json { "@type": "regen:USS01-CreditBatch", "@context": { "regen": "https://framework.regen.network", "schema": "http://schema.org/", "schema:url": { "@type": "schema:URL" }, "regen:monitoringReport": { "@container": "@list" }, "regen:verificationReport": { "@container": "@list" } }, "regen:registryAgent": { "schema:name": "Regen Network Development, PBC", "schema:url": "https://registry.regen.network" }, "regen:projectVerifier": { "schema:name": "Verifit", "schema:url": "https://verifit.com.co/" }, "regen:monitoringReport": [ { "schema:name": "ERABrazil Monitoring Report (2021-2023)", "schema:url": "https://regen-registry.s3.us-east-1.amazonaws.com/...Monitoring+Report...", "regen:dataIRI": "regen:114EfLg2Xns4F5SCWQZ1f2EK1RqWNrqvQMTgPsFcvMBdwJNKGt2A.pdf" } ], "regen:verificationReport": [ { "schema:name": "Verifit Validation & Verification Report (Jan 2025)", "schema:url": "https://regen-registry.s3.us-east-1.amazonaws.com/...Verification+Report...", "regen:dataIRI": "regen:114ZqehBLYAzaroF7nHSYwEMTzPZW6isEY4gr2myxEhbFyUNWh31.pdf" } ] } ``` {% endcode %} **Typical fields:** registry agent, project verifier, monitoring reports with anchored data IRIs, verification reports, supplemental materials, and links to PDFs and evidence documents. *** ### Upcoming Standardization The Framework Working Group is finalizing unified LinkML-backed metadata schemas for credit classes, projects, credit batches, evidence, claims, and methodologies. Once adopted: * All JSON-LD documents will share consistent structures across entity types * Developers can reliably parse metadata using shared vocabularies * New capabilities (SPARQL queries, schema validation, graph navigation) will work seamlessly across the ecosystem # Additional Project Information Beyond semantic metadata, the Regen App stores additional off-chain project information—such as project descriptions, preview images, or UI-specific attributes—in an application database. This information is not anchored on-chain; instead it can be queried via the Regen Marketplace GraphQL API. The API is CSRF-protected; clients must first obtain a token: ``` GET https://api.registry.regen.network/marketplace/v1/csrfToken ``` Then include the cookie and token when querying `/marketplace/v1/graphql` **Common query: Retrieve application-level project metadata** ```graphql query ProjectByOnChainId($onChainId: String!) { projectByOnChainId(onChainId: $onChainId) { metadata # This is off-chain descriptive metadata used in the Regen App UI } } ``` This endpoint supplements anchored metadata with additional fields used for richer descriptions, media galleries, UI-specific content, and partner-managed additions. Both anchored metadata (via IRIs) and application-level metadata (via GraphQL) are used together to render complete project views in applications like the Regen App. # Retirement Certificates Retirement information is available via the Indexer GraphQL endpoint at `https://api.regen.network/indexer/v1/graphql`. Unlike the Marketplace API, this endpoint does not require CSRF authentication. **Query by transaction hash:** graphql ```graphql query IndexerRetirementByTxHash($txHash: String!) { retirementByTxHash(txHash: $txHash) { nodeId } } ``` The returned `nodeId` can be used to construct the retirement certificate URL: ``` https://app.regen.network/certificate/{nodeID} ``` # Generating New Metadata IRIs Applications can create new metadata entries—such as project updates, claims, evidence references, or credit-class documents—using the IRI Generator API. #### **Generate an IRI (without storing it)** ``` GET /data/v2/iri-gen ``` #### **Generate + store an IRI and its metadata** ``` POST https://api.regen.network/data/v2/iri-gen ``` Request body is the metadata document (JSON-LD).\ The response includes: * `iri`: content-addressed IRI * `metadata`: the stored document (if using POST) This is the same endpoint used internally for: * Project posts / updates * Evidence sets * Claims * Methodology or credit-class metadata creation # Data Standards & Framework Working Group The Framework Working Group (FWG) is developing standardized data schemas for all metadata in the Regen ecosystem. This work establishes semantic data standards for credit classes, projects, and ecological claims that enable interoperability with the broader linked data ecosystem. ### Current Status The FWG has completed significant infrastructure work including: * **LinkML schema infrastructure** for credit class and project metadata * **Automated validation pipelines** that generate JSON Schema, SHACL constraints, and RDF formats from a single source * **Live SPARQL endpoint** enabling semantic queries across all Regen datasets * **Credit class metadata migration** to the new standardized format Project-level metadata migration is currently in progress. ### Technical Resources * **Schema Documentation:** [framework.regen.network](http://framework.regen.network) * **SPARQL Endpoint:** Contact the RND team for credentials and API access * **Source Repository:** [regen-data-standards](https://github.com/regen-network/regen-data-standards) *** > **Note:** This section is a placeholder. Comprehensive documentation of the data standards, schema definitions, and query patterns will be published as the Framework Working Group completes the ongoing migration work. For the latest updates, see the [FWG progress thread](https://forum.regen.network) or reach out to the working group directly.