Overview

With regard to ecological markets, business leaders will find themselves in these four phases:

• Creating Verified Supply

• Establishing Demand

• Buying & Selling

• Offsetting

There are many rationales that can be applied here such as Greenhouse Gas Emission Profiles, Renewable Energy Credits, and Carbon Offsets. While emission allowances are subject to government regulation, a Carbon Offset, for example, is an intangible asset that is created in a process involving a project or program whose activity can be claimed to reduce or remove carbon as a result, that is independently verified and turned into a carbon offset. These offsets are minted, or issued, by an environmental registry that created the standard methodology or protocol used to create the verified carbon offset claim. The offset then represents the original owner’s property right claim to the carbon-related benefits. The asset owner(s) can then sell their credits directly to buyers, or at wholesale. The ultimate end-user has the right to claim the benefits and can retire the offset permanently – usually as part of a netting process, where the claimed CO2 benefits are subtracted from that end-users other Greenhouse Gas (GHG) emissions.

The process to create renewable energy or carbon offset claims that can be validated and verified to be turned into a product is called measurement, reporting, and verification (MRV) data. Today, this process of collecting the supporting data for these carbon offsets is heavily manual and prone to errors. The main factors driving these error-prone are:

• Poor data quality

• Lack of assurance

• Potential double counting

• Greenwashing

• Overall lack of trust.

This is where the Guardian solution which leverages a Policy Workflow Engine (PWE), is a sensible approach to ameliorate the issue with the current processes. The dynamic PWE can mirror the standards and business requirements of regulatory bodies. In particular, the Guardian solution offers carbon markets the ability to operate in a fully auditable ecosystem by including:

• W3C Decentralized Identifiers (DIDs): Decentralized Identifiers (DIDs) are a new type of globally unique identifier that are designed to enable individuals and organizations to generate their own identifiers using systems they trust.

• W3C Verifiable Credentials (VCs): A digital document that consists of information related to identifying a subject, information related to the issuing authority, information related to the type of credential, information related to specific attributes of the subject, and evidence related to how the credential was derived.

• W3C Verifiable Presentations (VPs): A collection of one or more VCs.

• Public ledger technologies.

• Policy workflow engines through fully configurable and human-readable “logic blocks” accessible through either a user interface or an application programming interface (API).

The Global Indexer is a pivotal tool within the Guardian ecosystem on the Hedera Network, designed to optimize data search, retrieval, and management. It offers advanced search capabilities across all Guardian data, including policies and documents, while improving data storage and indexing for efficient analytical queries and duplicate checks. With access to a comprehensive dataset from all Guardian instances, the Indexer ensures thorough data retrieval. Its user-friendly interface simplifies navigation, and its integration with Hedera and IPFS enhances the handling of large datasets and complex queries, making it an essential component for efficient data management.

Before we begin, lets figure out what type of user you are:

Watch this quick 2-minute video to learn about Schemas:

Watch this quick video to learn about Dry Run:

The Managed Guardian Service (MGS) Custom GPT is a specialized AI assistant designed to facilitate users in understanding and utilizing the Managed Guardian Service platform. This tool represents an advanced version of ChatGPT, customized specifically to cater to the needs of users engaging with MGS. It has been meticulously programmed with a comprehensive range of MGS-related documentation, policies, and operational guidelines.

You can also find it in the Chat GPT Store

The primary function of the MGS Custom GPT is to act as an interactive knowledge base. It helps users navigate the complexities of the MGS platform, which is pivotal for businesses involved in emissions reporting, carbon offset, and renewable energy credit creation. This AI assistant stands out due to its ability to quickly process and provide insights from a vast array of MGS documentation, which has been integrated into its system.

Key Features of MGS Custom GPT

1. Customized Assistance: Tailored specifically for the Managed Guardian Service, it provides focused and relevant information, making it a reliable source for MGS-related queries.

2. Rich Knowledge Base: Equipped with extensive data from MGS documentation, it can answer a wide range of questions, from basic setup to complex operational procedures.

3. Efficient Query Resolution: Designed to interpret and respond to user queries by referencing the integrated MGS documentation, ensuring accurate and up-to-date information.

4. User-Friendly Interface: Simplifies the user's experience with the MGS platform, offering step-by-step guidance and clarifications on various aspects of the service.

5. Support for Various MGS Aspects: Capable of assisting with vault setups, Hedera account integration, policy understanding, token operations, and trust chain features.

How to Use MGS Custom GPT:

1. Ask Specific Questions: Users can inquire about specific aspects of MGS, such as setting up user profiles, managing tenants, or understanding policy implementations.

2. Seek Clarifications: If there are aspects of the MGS documentation or operations that are unclear, the tool can provide detailed explanations.

3. Explore Features: Users can explore different functionalities and features of the MGS platform through interactive questioning.

4. Troubleshooting and Support: The tool can offer troubleshooting advice and guide users through resolving common issues encountered on the MGS platform.

The Managed Guardian Service Custom GPT serves as an invaluable asset for users, significantly enhancing their ability to effectively utilize the MGS platform. By providing instant access to a wealth of information and guidance, it empowers users to make the most out of the MGS services and capabilities.

Watch this quick 2-minute video to learn about policies:

Use the UI or APIs to create your own digital methodologies

Can't create a policy? Use one that we have already preloaded for you!

There's nothing worse than wanting to jump into the action, but not having all of the tools! The open-source Guardian community is ever growing and so is the collection of tested policies. As more become available, we'll add them to the list of preloaded policies for you to quickly drop them in.

Multi-tenancy

Multi-tenancy is an architecture in which a single instance of a software application serves multiple customers. Each environment is called a tenant. During the beta phase, we will allow up to 3 tenants per each Tenant Admin account. Additionally, you will also be able to select which Hedera network you'd like to point your tenant to the Hedera Mainnet, Testnet, and Previewnet. Let your imagination run wild on how you will use this feature. They can serve your customers, act as sandbox/production environments, or even offer different use case designs. We look forward to hearing everyone's feedback on this!

Flexible Data Storage with IPFS Storage Providers

The Managed Guardian Service (MGS) enhances its data storage capabilities through integration with various IPFS Storage Providers, ensuring that organizations and individuals have access to a decentralized and secure method for managing their digital assets and environmental data. This approach not only bolsters data integrity and accessibility but also aligns with the decentralized ethos of blockchain technologies, offering a robust solution for the storage of sensitive information across a distributed network.

Integrate with your system

The Managed Guardian Service is a hosted environment where we provide you with resources, tools, and support. Once registered for the Managed Guardian Service, users will be given two options to get started. One option is to use a simple user interface to develop policies and run proof of concepts quickly. The other option is APIs for a fully customizable application experience.

Secure self-custody with the MGS Vault

The Managed Guardian Service Vault is designed to benefit organizations and individuals looking to securely store their user account secrets, such as private keys. The Vault solution leverages the open-source version of Hashicorp Vault and is intended to be used with the Managed Guardian Service. Keep in mind, that MGS has on it's roadmap, integrations with many other popular vaults, so requests are welcome. Once registered for the Managed Guardian Service, users will need to configure their profiles. They may choose to bring their own compatible vault or use the MGS vault solution we deployed across all major cloud provider Marketplaces. Examples of those marketplaces include the Microsoft Azure Marketplace, Google Cloud Platform Marketplace, and AWS Marketplace.

Hosted Indexer: Data Tracking and Retrieval

The Indexer in Managed Guardian Service (MGS) enables tracking and retrieval of data across carbon offsets, policies, and transactions. It offers advanced search capabilities, allowing users to quickly locate specific records, such as policy updates or carbon credit histories, by filtering attributes like project type and issuance date. Designed to improve data transparency and accessibility, the Indexer supports compliance reporting, impact analysis, and audit trails, ensuring that all indexed data is up-to-date, traceable, and easily accessible for informed decision-making.

Get access to our support desk

The monitoring and alerting system is the backbone of our service. It allows us to detect any issues before they manifest themselves to users and enables us to take timely action. MGS is widely covered by monitoring and alerts to allow us to react, prevent, and analyze any issues that can happen. However, In the event that technical support is needed, the MGS team has a help desk with SLAs to address needs.

Want to get technical?

Watch this quick video to learn about the Managed Guardian Service Vault

Watch this quick video to learn about Retirement Contracts

New

Below is a list of features that are included in the initial launch of the Managed Guardian Service Beta v1

• Open-Source Guardian Version 2.7

• Introduction to Admin Users

• Multi-tenancy

• Pre-loaded Policies

  • Carbon Offsets Policies:

    • Verra Redd+ VM0007 Developed by Envision Blockchain

    • Carbon Reduction Measurement - GHG Corporate Standard Developed by TYMLEZ

  • Renewable Energy Credits Policy:

    • International Renewable Energy Credit Standard Developed by Envision Blockchain

  • Carbon Emission Policies:

    • Remote Work GHG Policy Developed by Envision Blockchain

    • Carbon Emissions Measurements - GHG Corporate Standard Developed by TYMLEZ

• Downloadable APIs

A set of regulations or instructions that specify how carbon offset projects are created, validated, confirmed, and tracked are referred to as policies in the Guardian. These regulations aid in ensuring that carbon offsets are legitimate, quantifiable, and capable of reducing or eliminating actual emissions.

The Guardian platform offers a framework for developing and overseeing carbon offset projects in accordance with a number of widely accepted international norms, such as the Verified Carbon Standard (VCS) or the Gold Standard. For various carbon offset project types, such as renewable energy, energy efficiency, forestry, or agriculture, these standards provide specific requirements.

The Guardian platform's policies are made to be flexible and adaptable to the particular requirements and objectives of each carbon offset project. They cover a variety of options and conditions, such as project parameters, baseline emissions, additionality standards, monitoring techniques, and reporting needs.

Project developers can make sure that their carbon offset projects adhere to the highest standards of reliability and quality by establishing policies within the Guardian platform. Involved parties, investors, and buyers of carbon offsets who want to make sure that their investments contribute to actual and significant emissions reductions or removals can also receive transparency and accountability from them.

Watch the videos in this youtube playlist to learn how to breakdown methodologies and create policies for the Guardian:

New

Below is a list of improvements that are included in the Managed Guardian Service Beta v2

• Upgrade to core open-source Guardian v2.8 (Retirement process for assets, Matched Assets, 3rd Party Content Providers, Modular Benefit Projects, and LedgerWorks Eco Explorer Implementation)

• Adding 2 DOVU CRU methodologies to the preloaded policies (Agrecalc and Cool Farm)

• Extend the POST/tenants/invite endpoint with the ability to return the inviteId in response

• Updated Swagger Documentation for Beta V2

• Enable Admins to manage users

• Improved Internal Alerts

• Enhanced Autoscaling for performance loading

• Bug fixes

New

• Tenant Logs

  • Tenant Admins can now access comprehensive logs specific to their tenant activity.

• Guardian v2.12 Upgrade

  • Improved minting speed due to new batching process.

  • Enhanced error handling for smoother operation.

  • Improved memory performance for faster processing.

  • Artifact tagging for easier identification and handling.

  • Enhanced policy configurator now offers customizable "themes".

  • Overall, expect a quicker user experience.

• More Pre-loaded Policies

  • Addition of more pre-loaded policies for a more comprehensive policy creator experience.

New

• Hedera Network selection: Mainnet (new), Testnet, Previewnet

• Core open-source Guardian Upgrade v2.8 to v2.11

• Self-custody of keys via MGA Vault

• High Availability

• Improved DB CPU consumption

• More pre-loaded open-source policies

New

• Guardian Core patches

  • Fixing an issue that the TokenId created are published with UUID formatting instead of a tokenId property.

  • Improvement of how the Policy Service handles large policies.

New

• New Hedera Testnet reconfiguration after testnet reset

• Web3.storage Validation

• New IPFS Storage Provider - MGS Managed IPFS Node

New

• Revolutionized User Interface: Navigate with ease and enjoy a more intuitive experience.

• Custom Tenant Branding: Tailor every one of your tenant spaces with unique branding elements for a personalized touch.

• Enhanced Standard Registry Attributes: Dive into a more comprehensive and detailed asset management journey.

• Core Guardian Upgrade to v2.20: Experience the pinnacle of our foundational technology, ensuring efficiency and reliability.

• AI-Powered Search Capabilities: Navigate through data with unprecedented ease and intelligence.

New

• Core Guardian Upgrade to v2.21

New

1. Filebase Support Added

In our continuous effort to expand and improve the IPFS solutions available in MGS, we have now added Filebase as an additional option. This integration allows users to choose Filebase for their IPFS needs, alongside the existing options. With Filebase support, users can leverage its unique features and benefits as part of their workflow in MGS.

Understanding the importance of effective communication, especially during downtimes, we have introduced a new notification system for all users. This feature is designed to inform users about any planned or unexpected downtime promptly. Here's what makes the downtime notification system stand out:

• Location and Visibility: The notification is prominently displayed at the top of the screen when enabled, ensuring maximum visibility.

• Interactivity: Users can dismiss the notification with a simple click of the [X] button. Once closed, it will not reappear until a new message is issued.

3. Enhanced Final User Profile Setup Wizard Descriptions

To make the setup process as smooth and understandable as possible, we have added helpful descriptions to each step of the Final Setup wizard. These descriptions are designed to provide users with clear information about what is required at each step, ensuring that both Standard Registry and Default User roles can be configured with ease and confidence.

4. Update to Guardian v2.22

Beta v6 includes Guardian version 2.22, bringing all the latest improvements and fixes from the Guardian platform into MGS.

New

1. Fix for IPFS Resolution Issue When using the MGS hosted IPFS storage provider option; we've resolved the "IPFS not resolved" error, enhancing the stability and reliability of our IPFS integrations.

2. Enhancements in Policy Import Process Addressing performance issues, we've fixed a critical bug in the circuit traversal loop during policy comparisons, significantly reducing processing times and CPU utilization. Additional optimizations have also been made to improve memory usage.

3. MGS Vault Integration for BYOD Key To further secure and customize your experience, we've integrated MGS Vault to support Bring Your Own DID (BYOD) Key, allowing for enhanced security and personalization within the MGS framework.

4. User Interface Improvements This version rolls out several UI enhancements designed to improve interaction and usability across the MGS platform.

5. Update to Guardian v2.23 Continuing our commitment to staying current with the latest technological advances, MGS has been updated to Guardian core version 2.23, incorporating all the new features and improvements.

Beta v7 includes Guardian version 2.23, bringing all the latest improvements and fixes from the Guardian platform into MGS.

New Features

Seamless Email-Based Login & Tenant Selection

Logging in to MGS is now smoother than ever! We've removed the friction of manually entering Tenant IDs. Instead, users can now log in using just their email and password, with a tenant selection screen for those associated with multiple tenants. This streamlined approach eliminates confusion, improves accessibility, and enhances the overall user experience.

New

Improve the UI/UX for OpenSource Policy Import Function

We have added a cleaner and more intuitive way to search for open-sourced policies directly within MGS, making it easier to find and import the policies you need.

Expose APIs for User Setup Flow

To improve integration capabilities, we've exposed public APIs for user creation functionalities (e.g., Standard Registry and Policy Users). This allows customers to seamlessly integrate MGS into their existing systems, managing user setup processes including IPFS storage providers and vault selections through their own interfaces.

Policy Lifecycle Management

Addressing performance inefficiencies, we've optimized the policy service to handle policy states more effectively. By managing obsolete policies post-Hedera testnet reset, we've reduced unnecessary load and SaaS infrastructure costs. Users can now better manage their policy data, minimizing potential data loss and improving overall satisfaction.

Updates

Update MGS to Guardian v2.24

In our commitment to staying current with technological advances, MGS has been updated to open-source Guardian version 2.24. This update brings all the latest features and improvements from the Guardian platform into MGS.

Beta V8 includes Guardian version 2.24, incorporating the latest improvements and fixes from the Guardian platform to enhance the overall functionality and reliability of MGS.

New Features & Enhancements

Trustchain Stability Fix Resolved an issue where accessing the Trustchain triggered a 422 error if the associated policy lacked a mint block. This fix ensures Trustchain visibility remains consistent and error-free regardless of policy configurations.

Improved Multi-Account Login Experience Users with multiple accounts tied to the same email can now easily select which account to log into during authentication. This streamlined selection process enhances usability across tenants and roles.

Token Minting Performance Optimization Addressed major performance bottlenecks during token minting—especially for high-load policies like. This update significantly improves loading speed and prevents UI freezing during heavy operations.

User Invite Status Tracking A new UI panel within the Tenant dashboard now displays the real-time status of user invites. Admins can track if an invite was sent, accepted, or expired—with support for resending expired invites—making user onboarding more transparent and manageable.

Direct Guardian-to-Indexer Connection (Enhanced Integration) Guardian instances can now be directly connected to the MGS hosted Indexer, enabling access to advanced UI elements and functionality previously limited to manual local setups. This integration is authenticated, streamlined, and ensures high availability with minimal user intervention.

HashScan Integration for Hedera Links All system-generated links for Topics, Tokens, and Hedera Account IDs have been updated from LedgerWorks to HashScan. This resolves broken link issues and ensures consistent access to Hedera ledger data.

Updates

Guardian Upgrade to v3.1.1 MGS is now upgraded to align with open-source Guardian v3.1.1. This ensures continued compatibility and leverages the latest core improvements from the Guardian ecosystem.

New

Email Alert on Successful Publishing of Policies

To improve communication and ensure that users are promptly informed, we have added an email notification feature. Whenever there is a successful publishing of any methodology on Testnet/Mainnet, an email alert with detailed information will be sent to the user.

Further Evolution of Policy Comparison (Mass Diff)

We have extended our policy comparison functionality to allow for mass-comparison of policies across the entire ecosystem. Users can now search for local policies similar or different to a given policy based on a similarity threshold, without needing to import them into the Guardian instance. This feature enhances the efficiency and breadth of policy analysis.

Updates

UI Improvements

We have made several enhancements to the user interface, including updates to dialog boxes, notification bars, and login screens. These improvements aim to provide a more cohesive and user-friendly experience.

Obsolete Banner Display

The obsolete banner, which should appear at the top of the page when launching MGS, is now functioning correctly and will be displayed as intended.

Policies with Tools in Dry Run Mode: Performance Improvement

The performance of executing policies with tools referenced in dry run mode has been significantly improved. Users will now experience faster execution speeds when importing and running these policies.

New Features

Database Vault Restriction for Mainnet API Access To ensure data security on the Mainnet, API access to the Hashicorp vault is now restricted, aligning API functionality with UI standards. This measure prevents unauthorized use of the vault, providing an added layer of protection for mainnet operations.

Enhanced Tenant ID Accessibility Tenant ID visibility has been streamlined for improved user experience. Previously accessible only by email or Admin login, the Tenant ID is now displayed directly within the tenant dashboard, making it easier for users to locate this essential information.

User Role Selection on Invite To improve the invitation flow, Tenant Admins can now select user roles (Standard Registry or User) when inviting new users. This update allows for better management of permissions and access levels, streamlining the onboarding process. Invitations are tailored to reflect the specific user role, enhancing clarity and usability.

Indexer Enhancements

Login Access for Indexer Interface We've added a dedicated Login/Signup button to the Indexer UI page, allowing users to directly access the login page without redirecting through the main MGS portal. This update simplifies access to Indexer functionality, making navigation smoother and more intuitive.

Global Search Integration with Indexer The Indexer is now integrated with Global Search, enabling users to search policies across the entire Hedera Testnet and Mainnet from within MGS. This enhancement improves search capabilities, providing faster, more comprehensive access to policies across instances and standard registries.

Customizable Indexer Hosting In this release, we’ve added options for hosting and customizing the Indexer. Organizations can now configure the Indexer to suit specific search and data access needs, making MGS even more flexible and adaptable to unique use cases.

Updates

MGS Upgrade to Open-Source Guardian 3.0 In alignment with the latest open-source Guardian version 3.0, MGS Beta V10 includes all the latest features and improvements from the Guardian platform. This update ensures that MGS users have access to cutting-edge functionality, security enhancements, and performance optimizations.

To ensure seamless integration and compatibility with a wide range of data storage needs within the Managed Guardian Service (MGS) framework, we have expanded our list of supported IPFS (InterPlanetary File System) storage providers. Each provider brings unique features and benefits tailored to different requirements, offering flexibility and choice to our users. Whether you are looking for enhanced security, specific geographic data residency, cost-efficiency, or scalability, our diverse range of compatible IPFS storage providers ensures that your data storage needs are met with the highest standards. Below is a list of IPFS storage providers that are fully compatible with MGS, designed to enhance your experience and optimize your data management strategy within the MGS ecosystem.

Overview

As part of the evolving Managed Guardian Service (MGS) platform, Tenant Admins now have the flexibility and autonomy to select their own IPFS (InterPlanetary File System) storage providers. They must select and configure their preferred IPFS storage provider prior to creating a tenant.

This new feature significantly enhances the customization and control Tenant Admins have over their data storage solutions within the MGS ecosystem. This introduction aims to guide Tenant Admins through the process of selecting and integrating an IPFS storage provider with their MGS tenant.

The Role of IPFS in MGS

IPFS is a peer-to-peer network protocol that enables decentralized data storage and sharing. In the context of MGS, it serves as a backbone for storing digital environmental assets securely and efficiently. Choosing the right IPFS storage provider is crucial for optimizing data accessibility, redundancy, and overall system performance.

Importance of Selecting an IPFS Provider

1. Customized Data Storage Solutions: Tenant Admins can choose a provider that best fits their specific data storage needs and requirements.

2. Enhanced Data Sovereignty: By selecting their own provider, Tenant Admins have greater control over where and how their data is stored.

3. Scalability and Flexibility: Different providers offer varying levels of scalability and flexibility, allowing Tenant Admins to tailor their storage solutions as their needs evolve.

4. Cost Optimization: With the ability to choose from various providers, Tenant Admins can select a cost-effective solution that aligns with their budget constraints.

Steps for Tenant Admins

1. Research and Evaluate IPFS Providers: Understand the offerings, features, and pricing models of various IPFS storage providers. Key factors to consider include storage capacity, redundancy, security measures, and network performance.

2. Compatibility with MGS: Ensure that the chosen IPFS provider is compatible with the MGS platform. This compatibility is essential for seamless integration and operation within the MGS ecosystem.

3. Integration Process: Follow the specific steps provided to integrate the selected IPFS storage provider with your MGS tenant. This may involve configuring API connections, setting up access credentials, and customizing storage settings.

4. Testing and Validation: After integration, thoroughly test the setup to ensure that data storage and retrieval functionalities are working correctly and efficiently within your MGS tenant.

Conclusion

The ability to select their own IPFS storage providers empowers Tenant Admins with greater control and flexibility in managing their data storage solutions within the MGS platform. This feature aligns with the overarching goal of MGS to provide a customizable, secure, and efficient environment for managing digital environmental assets. Tenant Admins are encouraged to take advantage of this feature to optimize their MGS experience and meet their specific data storage needs.

Overview

With the recent shift in the Managed Guardian Service (MGS) infrastructure, incorporating web3.storage as a critical component for data storage and management is essential. This guide provides an introduction to web3.storage, outlining its significance, operational mechanics, and the steps required for Tenant Admins to integrate it with their MGS tenants.

What is web3.storage?

web3.storage is a platform designed to facilitate easy and efficient storage of data on the decentralized web. Utilizing IPFS (InterPlanetary File System) and Filecoin, web3.storage offers a robust and scalable solution for data storage needs, particularly suited for applications within the web3 ecosystem.

Overview

In response to evolving data management needs within the Managed Guardian Service (MGS) infrastructure, integrating filebase as a key IPFS provider has become imperative. This documentation serves as a comprehensive guide to incorporating Filebase, emphasizing its importance, functionality, and the step-by-step process required for Tenant Admins to seamlessly integrate it with their MGS setup.

What is filebase?

filebase is a pioneering platform that leverages the InterPlanetary File System (IPFS) to offer scalable and decentralized data storage solutions. By harnessing the power of IPFS and blockchain technology, Filebase provides users with a secure, efficient, and cost-effective method for storing data across a distributed network. This platform is exceptionally well-suited for applications demanding high data integrity, availability, and redundancy — characteristics that align with the core objectives of the MGS ecosystem.

The integration of filebase with MGS not only enhances the platform's data storage capabilities but also aligns with the overarching goal of leveraging decentralized technologies for improved security and efficiency. This guide will navigate through the necessary steps to integrate filebase with MGS, ensuring a smooth transition for Tenant Admins aiming to optimize their data management strategies within the MGS framework.

Overview

In response to the evolving needs of our Managed Guardian Service (MGS) infrastructure, we are thrilled to introduce the Managed IPFS node as a pivotal addition to our suite of data storage solutions. This section is dedicated to providing a comprehensive understanding of the Managed IPFS node, highlighting its importance, operational dynamics, and integration process for Tenant Admins within the MGS ecosystem.

What is a Managed IPFS Node?

The Managed IPFS node is a fully managed and hosted service provided by MGS, designed to streamline the storage and management of data on the decentralized web. Leveraging the power of the InterPlanetary File System (IPFS), our Managed IPFS node offers a seamless and scalable approach to handling vast amounts of data with enhanced security, redundancy, and ease of access.

Tenant Admins play a crucial role in integrating the Managed IPFS node with their MGS tenants. Here's a step-by-step guide to get you started:

For New Tenants

1. Click the Add New Tenant Button

2. Fill out the Tenant Name and select the appropriate Network

3. When asked for the IPFS Storage Provider click the drop down and select Managed IPFS node

For Existing Tenants

1. From the Tenant Admin screen, click the "Open" button

1. Navigate to the "Settings" tab

1. When asked for the IPFS Storage Provider click the drop down and select Managed IPFS node

1. Save Changes

Step By Step Process

Following are the steps to follow to generate Web3.Storage API values:

You can check your local versions like this:

node --version && npm --version

Install the @web3-storage/w3cli package with npm

npm install -g @web3-storage/w3cli

w3 space create

1. Execute the following to set the Space you intend on delegating access to:

w3 space use

1. Execute the following command to retrieve your Agent private key and DID:

npx ucan-key ed

1. Retrieve the IPFS_STORAGE_PROOF by executing the following:

w3 delegation create <did_from_ucan-key_command_above> | base64

The output of this command is the value to be used in the environment variable IPFS_STORAGE_PROOF.

To summarize, the process of configuring delegated access to the w3up API consists of execution of the following command sequence:

1. w3 login

2. w3 create space

3. w3 use space

4. npx ucan-key ed

5. w3 delegation

Demo Video

Tenant Configuration

Now, with a Secret Access Token generated, you can proceed with configuring a new or existing tenant in MGS. If you wish to create a new tenant, log in as Tenant Admin, select the ‘Tenants’ menu option, and click ‘+ Add New Tenant’. In the modal window, enter the Tenant Name, choose the appropriate Network from the list, and select ‘filebase’ among the IPFS Storage Provider options. In the ‘filebase token’ field, enter the Secret Access Token you copied earlier. Click the ‘Create Tenant’ button to finalize the creation of this tenant.

If you need to change the IPFS Storage Provider for an existing tenant, select the ‘Tenants’ menu item, find the tenant, and click the ‘Open’ button. Then, go to the Settings tab, select ‘filebase’ from the IPFS Storage Provider list, and paste the Secret Access Token you copied earlier into the filebase token field. Click the Save Changes button at the bottom of the page to apply your changes.

Tenant Admins play a crucial role in integrating Web3.Storage with their MGS tenants. Here's a step-by-step guide to get you started:

For New Tenants

1. Click the Add New Tenant Button

2. Fill out the Tenant Name and select the appropriate Network

3. When asked for the IPFS Storage Provider click the drop down and select Web3.Storage

For Existing Tenants

1. From the Tenant Admin screen, click the "Open" button

1. Navigate to the "Settings" tab

1. When asked for the IPFS Storage Provider click the drop down and select Web3.Storage.

2. Fill out the settings and click "Save Changes."

Logging into filebase

• Next, fill out the form fields, including an email address and password, and agree to the filebase terms to create your account.

Buckets

Buckets are like file folders; they store data and associated metadata. Buckets are containers for objects. Navigate to the Buckets dashboard by clicking on the ‘Buckets’ menu option. Here you can view your existing buckets and create new ones.

If you already have the Bucket you wish to use with MGS, skip this step. To create a new bucket, click the ‘Create Bucket’ button in the top right corner of the webpage, enter the name for the new bucket, and click the ‘Create Bucket’ button.

If successful, you will be redirected to the Bucket dashboard with your newly created bucket.

Access Keys

The Access Keys menu option leads you to the access keys dashboard. Here you can view, manage, and rotate your access keys. From this menu, you can also generate a Secret Access Token to be used with MGS. To generate this token, click the dropdown menu for 'Choose Bucket to Generate Token', then select the IPFS filebase Bucket you intend to use.

Copy the generated Secret Access Token.

Create new Tenant.

PUT /tenants/user

Create new Tenant. For Tenant Admin role only.

Request Body

Return Tenants.

POST /tenants

Return Tenants. For Admin role only.

{
content:
            application/json:
              schema:
                type: object
                properties:
                  totalCount:
                    type: number
                  tenants:
                    $ref: '#/components/schemas/Tenant'
}

{
    // Response
}

{
    // Response
}

{
content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
}

Return user Tenants only.

GET /tenants/user

Return user Tenants. For Tenant Admin role only.

Delete Tenant

POST /tenants/delete

Delete Tenant and all related data. This action can't be undo. For tenant admin role only.

Request Body

Send Invite link.

POST /tenants/invite

Send an Invite link for a new user. For Tenant Admin role only.

Request Body

Return Tenant related settings.

GET /tenants/settings

Get Tenant related settings. For Tenant Admin role only.

Delete Tenant User

DELETE /tenants/{tenantId}/users/{userId}

Delete Tenant User

Path Parameters

Return Tenant Users

POST /tenants/{tenantId}/users

Return users for Tenant. For Tenant Admin role only.

Path Parameters

Request Body

Reorder tenants. For Tenant Admin role only.

POST /tenants/reorder

Reorder tenants

content:
            application/json:
              schema:
                $ref: '#/components/schemas/CommonResultDTO'

Introduction

In the realm of digital environmental assets and carbon offset tokens, data is king. The essence of creating verifiable and trustworthy digital assets lies in the quality and structure of the underlying data. This is where the concept of "Schema Types" comes into play. Schemas serve as the backbone of data organization, ensuring that every piece of information adheres to a predefined format, thereby maintaining consistency, accuracy, and reliability.

Purpose of Schema Types

Schema Types are not just about data organization; they are about setting a standard for data integrity and trustworthiness. By defining clear structures and formats for data entry, storage, and retrieval, schemas facilitate:

1. Standardization and Uniformity: Ensuring all data across various projects and methodologies conforms to a consistent structure, enabling seamless integration and comparison.

2. Flexibility and Customization: Catering to diverse needs by allowing modifications to fit specific project requirements without compromising data integrity.

3. Efficient Data Management: Streamlining the process of data handling, from input to analysis, ensuring that data-driven decisions are based on accurate and reliable information.

Role in Digital Environmental Assets

The utilization of Schema Types is pivotal for the lifecycle of digital environmental assets. From the initial stages of data collection to the final phases of token creation and verification, schemas ensure that each step is backed by solid, verifiable data. This approach not only enhances the credibility of the digital assets but also boosts confidence among stakeholders in the carbon market ecosystem.

From an Environmental perspective, schemas contain environmentally-oriented vocabularies of terms for representing machine- and human-comprehensible structured data. In other words, they are linguistic “templates”, “frames”, or “patterns” together with rules for using them to specify a potentially infinite multitude of numbers, phrases, sentences, or arguments, which represent environmental data.

In the Guardian, various environmental data produced in the course of executing policy workflows are packaged into JSON documents such as verifiable credentials and verifiable presentations. Schemas define the structure and content of these verifiable documents, enabling their automatic processing and provenance verification. It’s critical that all data required to be presented and or collected during a policy workflow has a well-defined verifiable credential schema. The schema will be used in the structural conformance verification of a document within a policy workflow.

The Standard Registry is a user that establishes policy requirements and specifications for the quantification, monitoring, reporting, verification, registration, and issuance of project-based emissions, offsets, reductions, and credits. The sections below cover:

Accept the Beta Test Term and Conditions

Fill out the required information and press the "Request Acess" button. Please wait some time while we approve your request.

You will now enter your Admin User Interface. To create a new tenant, simply click the "+ Add New Tenant" button.

Enter a name for the tenant and press the "Create Tenant" button.

Once that is finished, you can now send the invite for users to join the tenant. Press the "Send Invite" button.

Enter the email address of the individual who should receive the tenant URL link. It may be easy to send this to yourself, so you have a copy of the URL yourself. The choice of how you send it is ultimately your decision.

That's it! Your tenant users can now begin creating policies, fulfilling policy workflows, and minting digital environment assets!

Schema Demo

There are two types of Schemas:

To display System / Policy Schemas in the GUI, we have added a toggle in the Schemas tab.

System Schemas

Whenever an account is created, System Schemas have generated automatically.

Policy Schemas

This is the second option in the Schemas tab. This option displays all the Policy Schemas related to all the created/imported Policies in the Policies tab.

The below screenshot shows the Policy Schemas of an imported Policy (i.e. iRec).

We also have a filter, where by default, all the Schemas of Policies are shown. We can also select a particular Policy to show the Schemas of the selected Policy.

Tags can have attached/linked documents. To add a document to the tag, a schema is required. Such documents can be found under the Tag Schemas section.

Policy Schema's can also be created by clicking on the New button.

Once the New button is clicked, we get a dialog box that asks for the following information: 1. Schema Name

2. Policy Dropdown: To select any of the imported Policy

3. Entity Dropdown: To select any of the Entity: VC / MRV

4. Description of Schema.

5. Add Field: To add any fields required for the Schema.

Instead of creating a new Schema from scratch, there is also an option to import it via File or via IPFS.

To import the Schema, click on the Import button.

Once the Import button is clicked, we get two options: Import from file and Import from IPFS

Import from IPFS: You can also import Schema from IPFS by entering the correct Schema timestamp. Sample iREC Schema timestamp is below:\

1644847084.945541771 (iREC 3 Policy)

Once the Schema is imported, we need to select the Policy from the Policy dropdown to connect the Schema and the Policy.

After selecting the required Policy, click on the Import button.

When the Schema is imported, it will be in draft status.

Once the Schema is imported, we will have the following options: 1. Export the Schema and save it as .zip file in the local machine

2. Editing the Schema

3. Deleting the Schema

4. Displaying JSON document

To Publish the Schema, click on Publish button.

After clicking on Publish, you will be prompted to enter the version. After entering the Version and pressing the submit button, the status will change to Published.

To create a new System Schema, click on the New button at the top right corner.

After clicking on the New button, you will be asked to enter Schema details such as Schema Name, Policy Dropdown, Entity : VC/MRV/NONE, Schema Description and any other required fields.

In addition to the basic Schema details we also have an option to add Field and Condition to each field.

We can also add Property dropdown field to each field in Schema. these properties are defined by IWA and are in standardized format.

We can select respective property for that specific field by searching by entering starting alphabet:

We can also customize the Field keys and Field Title by clicking on Advanced Tab.

There are different types of Schema Types:

• None

• Verifiable Credential

• Encrypted Verifiable Credential

There are different types of Field Types:

• Number

• Integer

• String

• Boolean

• Date

• Time

• DateTime

• Duration

• URL

• Email

• Image

• Account

• Units of Measure

  • Prefix

  • Postfix

• Enum

• URI

• GeoJSON

• Help Text

Each of the above field types can be marked as either Marked or optional by checking the Required Field checkbox.

Now, we also have an ability to configure auto calculate expression when configuring the schema field as shown below:

Once the above details are added, click on the Create button.

Once the System Schema is created, we have options for activating, deleting, editing and viewing JSON documents.

UPDATING SCHEMA BASED ON SCHEMA ID

Updates the schema

PUT /schemas/{schemaId}

Updates the schema matching the id in the request body. Only users with the Standard Registry role are allowed to make the request.

Path Parameters

Request Body

{
    content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/Schema'
}

{
    // Response
}

{
    // Response
}

{
    content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
}

SCHEMA LISTING

Returns all schemas

GET /schemas

Returns all schemas

Query Parameters

{
    // Response
}

{
    // Response
}

{
    content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
}

{
    headers:
            x-total-count:
              schema:
                type: integer
              description: Total items in the collection.
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/Schema'
}

PUBLISHING SCHEMA BASED ON SCHEMA ID

Publishes the schema

PUT /schemas/{schemaId}/publish

Publishes the schema with the provided (internal) schema ID onto IPFS, sends a message featuring IPFS CID into the corresponding Hedera topic. Only users with the Standard Registry role are allowed to make the request.

Path Parameters

Request Body

{
    content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/Schema'
}

{
    // Response
}

{
    // Response
}

{
    content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
}

DELETING SCHEMA BASED ON SCHEMA ID

Deletes the schema

DELETE /schema/{schemaID}

Deletes the schema with the provided schema ID. Only users with the Standard Registry role are allowed to make the request.

Path Parameters

{
    content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/Schema'
}

{
    // Response
}

{
    // Response
}

{
    content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
}

PREVIEWING SCHEMA FROM ZIP FILE

Schema preview from a zip file

POST /schemas/import/file/preview

Previews the schema from a zip file. Only users with the Standard Registry role are allowed to make the request.

Request Body

PREVIEWING SCHEMA FROM IPFS FILE

Schema preview from IPFS

POST /schemas/import/message/preview

Previews the schema from IPFS without loading it into the local DB. Only users with the Standard Registry role are allowed to make the request.

Request Body

Imports schemas from a file for the selected topic (policy)

POST /schemas/{topicId}/import/file

Imports new schema from a zip file into the local DB. Only users with the Standard Registry role are allowed to make the request.

Path Parameters

Request Body

{
    // Response
}

{
    // Response
}

{
    content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
}

{
    content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/Schema'
}

Creates a schema related to the topic (policy)

POST /schemas/{topicId}

Creates new schema. Only users with the Standard Registry role are allowed to make the request.

Path Parameters

Request Body

{
    // Response
}

{
    // Response
}

{
    // Response
}

{
    content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
}

EXPORTING SCHEMA FILES FOR THE SCHEMA

Return zip file with schemas

POST /schemas/{schemaId}/export/file

Returns schema files for the schemas. Only users with the Standard Registry role are allowed to make the request.

Path Parameters

{
   
}

{
    // Response
}

{
    // Response
}

{
    content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
}

EXPORTING HEDERA MESSAGED IDS OF PUBLISHED SCHEMA

Hedera message IDs of published schemas

POST /schemas/{schemaId}/export/message

Returns Hedera message IDs of the published schemas, these messages contain IPFS CIDs of these schema files. Only users with the Standard Registry role are allowed to make the request.

Path Parameters

{
    content:
            application/json:
              schema:
                $ref: "#/components/schemas/ExportSchema"
}

{
    // Response
}

{
    // Response
}

{
    content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
}

IMPORTING SCHEMA FROM .ZIP FILE

Imports new schema from a zip file

POST /schemas/import/file

Imports new schema from a zip file into the local DB. Only users with the Standard Registry role are allowed to make the request.

Request Body

Embracing GBBC Specifications for Universal Data Comparability

The Need for Standardized Data Mapping

The complexity of environmental reporting and digital asset management is compounded when dealing with varied methodologies and schema designs. To address this, the Guardian implements a standardized approach to data mapping, allowing for effective comparison and analysis of project data, regardless of its original schema format. This standardization is vital for:

1. Ensuring Consistency: Regardless of how data is formatted in individual schemas, standardizing property definitions ensures a consistent approach to interpreting and comparing data.

2. Facilitating Comparability: By using a common language for data properties, the Guardian enables users to effectively compare and analyze data from similar or different methodologies.

3. Enhancing Searchability: Standardized properties allow for more efficient data retrieval, making it easier to locate specific information across various projects and schemas.

Role of the Property Glossary

The Property Glossary in MGS is more than just a list of definitions; it is a tool for aligning data across the platform. It includes a table of Standardized Property Definitions. Drawing from the GBBC Specification, the glossary provides clear definitions for each property, ensuring a common understanding across the platform.