<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Marley Gray on Medium]]></title>
        <description><![CDATA[Stories by Marley Gray on Medium]]></description>
        <link>https://medium.com/@newgatemarleyg?source=rss-55a6d0d1a2a9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*iONnhiuwCLgp7uggfpZS8Q.png</url>
            <title>Stories by Marley Gray on Medium</title>
            <link>https://medium.com/@newgatemarleyg?source=rss-55a6d0d1a2a9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 06:54:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@newgatemarleyg/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Occidental (Oxy) Open Sourcing the Verra CCS+ Master Extension Set]]></title>
            <link>https://medium.com/@newgatemarleyg/occidental-oxy-open-sourcing-the-verra-ccs-master-extension-set-7c2cd442d412?source=rss-55a6d0d1a2a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c2cd442d412</guid>
            <category><![CDATA[carbon-credits]]></category>
            <category><![CDATA[dmrv]]></category>
            <category><![CDATA[carbon-capture]]></category>
            <category><![CDATA[carbon-capture-storage]]></category>
            <category><![CDATA[distributed-ledgers]]></category>
            <dc:creator><![CDATA[Marley Gray]]></dc:creator>
            <pubDate>Thu, 19 Nov 2026 18:46:43 GMT</pubDate>
            <atom:updated>2026-11-19T18:46:43.560Z</atom:updated>
            <content:encoded><![CDATA[<h4>A reusable digital methodology template based on the Interwork Alliance Digital Measurement Reporting and Verification Framework can help accelerate trusted carbon markets, reduce implementation cost, and improve the integrity of carbon capture and storage credits.</h4><h4>Co-authored by Mohanraj Adhikari, Manager, Technology Solutions @ Verra</h4><h4>Problem being addressed</h4><p>Carbon markets depend on trust: buyers need confidence that each credit represents a real, measurable, independently verified climate impact, while project developers need an efficient path to convert project activity into financeable environmental assets. For carbon capture and storage projects, that challenge is amplified by technical complexity. The Verra VM0049 Carbon Capture and Storage methodology and its digital counterpart available on the Verra Project Hub, applies globally to CCS activities and relies on multiple modules and tools covering capture, transport, storage, electricity emissions, non-VCS CO2 accounting, and differentiation between reductions and removals. That modular structure is valuable because it can support different project designs, but it also creates a high burden for data consistency and verification.</p><p>Historically, much of the measurement, reporting, and verification process has been document centric. Methodologies are expressed in PDFs, calculations are interpreted by implementation teams, and each project may recreate similar data structures, workflows, and evidence packages. This can slow project onboarding, introduce avoidable interpretation differences, increase verification effort, and limit interoperability between registries, verification bodies, suppliers, marketplaces, and digital platforms. Though much of these issues are addressed by the digital methodology on the Verra Project Hub, the business problem still exist on how to make that digitization, auditable by multiple project entities such as project proponents, VVBs and registries without rebuilding the same foundation each time.</p><h4>Overview of how the solution works</h4><p>The Verra CCS+ Master Extension Set addresses this gap by translating methodology-specific requirements into reusable, machine-readable templates aligned with the <a href="https://gbbc.io/initiatives/interwork-alliance">GBBC/IWA Digital Measurement, Reporting, and Verification framework</a>. In the dMRV framework, Master Extension Sets are groupings of templates that encompass entities, messages, formulae/equations, and variables/parameters specific to the quality standard or methodology that a project is using. They can be organized into modules that act as shared libraries, allowing participants to use consistent digital representations of methodology requirements while still configuring them for the needs of a specific project.</p><p>A Master Extension Set functions like a common business language for the supplier, validation and verification body, and issuing registry. The open specification defines templates for equations (formulas), parameters (variables), entity extensions, and request/response message pairs. In the original methodology documentation, equations and parameters describe how project emissions and removals are calculated. In the digital implementation, those become Formula Templates and Variable Templates with fixed identifiers, descriptions, versions, units of measure, data schemas, and data examples. This means that when a supplier reports a value such as a mass flow measurement, the verifier and registry can process the same data element with a shared understanding of what it means, where it belongs, and how it contributes to a calculation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BDqoAgNGyDnjIbuJAtXERA.png" /><figcaption>Verra VM0049 — Master Extension Set</figcaption></figure><p>The release to open source is the key business accelerator. Rather than each CCS project or platform independently interpreting the same methodology and rebuilding data contracts, the open Master Extension Set provides a reusable starting point. It can be installed into an implementation such as the Environmental Credit Service or adapted by other dMRV-aligned platforms. A project then creates its own project-specific Extension Set instance from the master templates, selects the modules it needs, and configures defaults such as units of measure, environmental variables, and project-specific reporting requirements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Me3gxFZlAe3sza2ATFo9gw.png" /><figcaption>Master Variable Templates</figcaption></figure><p>The current master extension set is integrated with the digital methodology on the Verra Project Hub via Rest APIs and creates set of documents such as Project Description, Monitoring Report, Validation Report and Verification Report as required by the VCS Standard. Once the data is received using the master extension set, the Verra Project Hub also runs its own calculation to ensure that the ERR (Emission Reductions and Removals) values match. Multiple rounds of integration and accuracy testing have been conducted using a simulated yet complete data to ensure the robustness of the entire system.</p><h4>How it leverages ledgers</h4><p>Ledger platforms are used as the trust and coordination layer for the digital MRV process. As evidence is collected, submitted, reviewed, and verified, important events and attestations can be cryptographically linked to create a transparent chain of custody. The goal is not to put every operational data point on the ledger, but to establish provenance, integrity, and accountability across the lifecycle of the claim. Evidence can be secured so that its authenticity is verifiable, checkpoints can be recorded as part of a shared workflow, and verified claims can be traced through issuance, retirement of underlying claims, and distribution of the resulting environmental credit.</p><p>For business stakeholders, this improves market confidence in three ways. First, it makes the lineage of a credit easier to inspect because the origination process is digitally traceable. Second, it reduces ambiguity by anchoring the project’s data to agreed templates and shared identifiers. Third, it supports automation because suppliers, verifiers, and registries can exchange structured messages and independently process the same formula and variable definitions. The result is a more scalable pathway for generating high-quality digital environmental assets while preserving the oversight roles that buyers and regulators expect.</p><h4>Results and learnings</h4><p>The Verra CCS+ Master Extension Set demonstrates that a complex CCS methodology can be converted into reusable digital infrastructure. The implementation described in the source material includes 105 Master Formula templates and 336 Master Variable templates across five modules and two toolsets, created through a real-world supply chain supporting carbon dioxide removal credit origination for a large direct air capture facility. That scale matters: it shows that the approach can handle the depth of methodology content needed for a production-grade use case rather than a narrow proof of concept.</p><p>The biggest learning is that standardization and flexibility must be designed together. A master extension set creates consistency, but projects still need to select modules, configure assumptions, and capture project-specific evidence. The Master Extension Set approach supports both requirements: it preserves consistent identifiers, schemas, and calculation templates while allowing each project to instantiate and configure the pieces it needs. A second learning is that collaboration across the supplier, verifier, and registry is essential. The master extension set is most valuable when it reflects the common operating model of the full supply chain, not just the interpretation of one participant.</p><p>A third learning is that open-source release can turn implementation work into market infrastructure. The effort invested in digitizing formulas, variables, workflows, and entity extensions becomes reusable by other CCS projects using the same methodology and can serve as a reference pattern for other methodologies. This creates a compounding benefit: every new implementation can start closer to production readiness, while feedback from additional projects can improve the shared resource over time.</p><h4>Future opportunities</h4><p>The open-source Verra CCS+ Master Extension Set creates several near-term business opportunities. First, it can reduce onboarding time and implementation cost for CCS projects by giving teams a tested library of digital templates. Second, it can improve the quality and consistency of verification by giving VVBs structured evidence, repeatable calculations, and clear data contracts. Third, it can support interoperability between digital MRV platforms, the Verra Project Hub, registries, and exchanges by establishing common representations for methodology requirements.</p><p>Longer term, the same pattern can be extended beyond CCS. Other quality standards and methodologies can be digitized into Master Extension Sets, creating a portfolio of reusable libraries for environmental assets across carbon removal, emissions reduction, nature-based solutions, and emerging sustainability markets. As those libraries mature, they can help establish a more interoperable market infrastructure where buyers can compare credits with more confidence, registries can scale digital submission processes, and developers can access finance faster through trusted assets.</p><p>Projects at times may need to propose methodology deviations. Some of those deviations may also impact the way credits are calculated. Users can propose such deviations on the extension sets and once they are approved, options to use approved deviations are also publicly available to use. The applicability of both the methodology and extension set broadens in future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YfrK0O-wpRkDN1Eiqp13RQ.png" /><figcaption>Full Audit History — Environmental Credit Service Impact Claim</figcaption></figure><p>The business case is therefore larger than a single release. Open sourcing the Verra CCS+ Master Extension Set converts hard-won implementation knowledge into shared infrastructure for the carbon market. It reduces duplicated effort, strengthens auditability, and gives market participants a practical way to move from document-based methodology interpretation to digital, automated, blockchain-enabled origination of high-integrity environmental credits.</p><p>You can get the Verra CCS+ Master Extension Set on <a href="https://github.com/VerraProjectHub/ccs-plus-extension-set">GitHub</a>.</p><p>The Verra Digital Gateway API Resources is also available on <a href="https://projecthub.verra.org/digital-gateway-api">GitHub</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c2cd442d412" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Overcoming obstacles in digitizing Measurement, Reporting, and Verification of Environmental Assets]]></title>
            <link>https://medium.com/@newgatemarleyg/overcoming-obstacles-in-digitizing-measurement-reporting-and-verification-of-environmental-assets-70a1b58f844d?source=rss-55a6d0d1a2a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/70a1b58f844d</guid>
            <category><![CDATA[digital-asset]]></category>
            <category><![CDATA[gbbc]]></category>
            <category><![CDATA[sustainability]]></category>
            <category><![CDATA[carbon-credits]]></category>
            <category><![CDATA[carbon-markets]]></category>
            <dc:creator><![CDATA[Marley Gray]]></dc:creator>
            <pubDate>Tue, 24 Sep 2024 15:22:31 GMT</pubDate>
            <atom:updated>2024-11-06T20:16:53.712Z</atom:updated>
            <content:encoded><![CDATA[<h4>Optimizing and automating the digital creation of credits</h4><p><em>This is a continuation of: </em><a href="https://medium.com/@newgatemarleyg/addressing-problems-in-voluntary-carbon-markets-07c2bef61f2e"><em>https://medium.com/@newgatemarleyg/addressing-problems-in-voluntary-carbon-markets-07c2bef61f2e</em></a></p><p>The Interwork Alliance, part of the <a href="https://www.gbbc.io/interwork-alliance">GBBC</a>, has been developing a technical framework to simplify the fragmented and often manual process of creating environmental assets like carbon and renewable energy credits. To see why this is fundamental, consider that currently, projects aiming for positive environmental impact face high barriers and struggle to generate profit from issuing high-quality credits for sale in markets.</p><p>There are many reasons for this. These “credits” are intangible assets, meaning a 1 tonne Carbon Credit cannot be redeemed for an actual tonne of carbon that you can put in the back of your truck and drive off with. The credit represents “trust” that the work performed by the project that was issued the credit resulted in the reduction or removal of 1 tonne of CO2 from the atmosphere AND that this tonne will not be soon rereleased into the atmosphere, i.e., a reversal event.</p><blockquote><em>As the saying goes, it takes a long time to build trust and only a moment to lose it.</em></blockquote><p>Most of these project-based credits suffer from a trust issue that necessitates rebuilding the foundation of trust. This foundation can transform these credits from intangible assets to authentic, verifiable data assets that possess intrinsic value based on evidence that the benefit is real and durable, i.e., it will not lose its value due to a reversal.</p><p>For a trusted, durable, data-backed asset, the origination process (Measurement, Reporting, and Verification) must produce evidence supporting benefit claims. These claims need independent verification based on rules set by an issuing authority followed by all parties. The credits should undergo a manufacturing process that treats evidence data, processing, validation, and verification like a supply chain.</p><p>This is what the digital MRV Framework, <a href="https://interworkalliance.github.io/TokenTaxonomyFramework/dmrv/spec/v2.5/index.html">now previewing version 2.5</a>, delivers: a standardized, extensible, multi-party process and data model capable of producing the new data-backed digital assets environmental markets need to mature and scale.</p><h3>Extensibility across the Silos of Supply</h3><p>Today, a project seeking to have such an asset issued must first find an issuing authority matching its planned activity. Issuers are typically called a “Registry” because they maintain their own database of projects and credits. These registries are generally endorsed and may be members of <a href="https://icroa.org/endorsed-organisations/">ICROA</a> (for carbon). Each provides a “crediting program” along with a set of methodology, protocol, and tool “modules” that projects combine to understand the “rules” they must follow to be issued credits by the registry.</p><p>Terms like “program”, “methodology”, “protocol”, and “tool” modules describe the documentation and rule “building blocks” that need to be assembled into a “rule book” a project must follow. The IWA dubs this composite set of “rules” a Quality Standard.</p><p>A Registry will have at least one crediting “program” and a portfolio of project-specific “modules” (e.g., methodology, protocol, or tool) selected by the project, approved by the issuing registry, and engaged with a certified Validation and Verification Body (VVB), which is the independent body evaluating evidence. These three parties — project, VVB, and issuing registry — form the supply chain for issuing these credits.</p><p>Typically, this supply chain creates a Project Design Description document, usually a large (100+ page) PDF, approved as the project’s “baseline” to start producing “evidence” of their work. This evidence is generally encapsulated in a Monitoring Report, another paper-based PDF template summarizing the evidence and serving as the basis for issuance. Credits are then issued on the Registry.</p><p>Anyone buying the credit needs to evaluate its quality by reviewing these documents and the actual Quality Standard or rulebook to determine if the price is justified. This means that to judge the asset’s quality, one needs to read 1000+ pages of documentation and possess the subject matter expertise to verify the process’s validity.</p><p>How many things do you buy that require you to read 1000+ pages to gain confidence? Especially when the asset might literally become valueless after purchase. Producing PDF documents to back up an asset does NOT facilitate creating a highly trusted, scalable asset class. We need to produce structured machine-readable data to back up these assets and establish a foundation of trust. This data must be transparent, ensuring a chain of custody and proof, which cannot be accomplished at scale if each issuing registry develops its own digital MRV standard, thus perpetuating market fragmentation.</p><p>So, how does the digital MRV Framework function in a world with many different issuers with different “programs” and “modules” work?</p><h3>Introducing the MRV Extension Set</h3><p>A Quality Standard consists of a “Crediting Program” and a set of “Modules” provided by an Issuing Registry, which are adhered to by supply chain participants and the manufacturing process. The digital counterpart of this Quality Standard, applied within the digital MRV Framework, is referred to as an MRV Extension Set.</p><p>For instance, the <a href="https://assets.ctfassets.net/so75yocayyva/4STnrZJkp2YIkQWYQ4ajrx/8882b7810a5ce94d8f60b64775690402/Digital_Measurement__Reporting___Verification__dMRV__Framework_-_IWA.pdf">MRV Framework</a> defines a “project” as an Activity Impact Module, a child of an Accountable Impact Organization, where an organization can have multiple projects of various types without duplicating the organization’s identity. The framework’s data definition or model for these “entities” is generic, with fields like ‘Name’ and ‘Address’. However, an MRV Entity Extension can include specific data properties for a project type, like the kind of carbon sequestration or technical process configuration used and applied to the Activity Impact Module. Every entity defined in the framework can have one or more extensions.</p><p>While Entity Extensions provide a method to customize the data captured for a “supply chain.” MRV Message Extensions allow customizing the manufacturing “process,” or “workflow”. By defining an extension Message Pair, a request-and-response pattern, process extensions can be specified to encode automation and additional evidence data based on customized activities. For instance, the VVB might request sensor device recalibration from the project, which would respond with confirmation and results of the calibration activity.</p><p>These extensions become part of the system of record, i.e., the data backing the issued asset. Just as the Quality Standard is composite, the MRV Extension Set is also composite, agreed upon and established in the IWA <a href="https://interworkalliance.github.io/TokenTaxonomyFramework/dmrv/spec/v2.5/index.html#dt-verification-process-agreement">Verification Process Agreement</a>. This agreement digitally represents the supply chain and manufacturing process followed by all parties. It documents the MRV Extension Set so that the underlying customized system of record using the same technical infrastructure as other project types is understandable by both machines and humans.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vpzX8jGJ8u78gHsrwBKFiA.png" /><figcaption>MRV Extension Set</figcaption></figure><p>For example, <a href="https://verra.org/">Verra</a> currently has a set of <a href="https://verra.org/methodologies/vm0049-carbon-capture-and-storage/">Carbon Capture and Storage modules </a>developed by <a href="https://ccsplus.org/">CCS+</a> for their VCS Credit Issuing Program. Depending on how the project captures and stores the carbon, different modules will be selected for the project’s supply chain. A project might capture Bioenergy (<a href="https://verra.org/wp-content/uploads/2024/02/06_-CCS-Module-2.5_BECCS_final.pdf">BECCS</a>) and store it geologically. It will also need to transport the captured carbon to its storage site, e.g., via pipeline or ship.</p><p>MRV Extensions, whether entity or message, are organized within a hierarchy where module-specific extensions reside within the module definition, while Quality Standard-wide extensions can be placed higher in the hierarchy.</p><p>Below is an example of a CCS+ MRV Extension Set with a Carbon Capture, Bioenergy, Transport and Storage modules:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bS2W9Z_vXEsjiuB9WCX6PA.png" /><figcaption>CCS+ Extension Set</figcaption></figure><p>The digital MRV Framework provides the foundational entity and process definitions for establishing a supply chain and manufacturing process. Using MRV Extension Sets allows these processes to be tailored to the specific project type and program while enabling technology infrastructure reuse across various project and program types.</p><h4>Call to Action</h4><p>If you are working in this space, the IWA is seeking feedback on MRV in general, the <a href="https://gbbcouncil.org/wp-content/uploads/2023/09/Digital-Measurement-Reporting-Verification-dMRV-Framework.pdf">digital MRV Framework</a> and the proposed updates outlined above…please provide your feedback using this <a href="https://form.typeform.com/to/Nf5kUANC?typeform-source=t.co">survey</a>.</p><h3>Summary</h3><p>Implementing the digital MRV Framework for technical infrastructure facilitates reuse across a broad range of project types and issuing program It reduces the costs of origination and decreases friction in evaluating quality across issuing silos.</p><p>Creating an MRV Extension Set for a Quality Standard involves collaboration among the project, VVB, and issuing authority. The resulting MRV Extension Set of this process should then be shared as an open standard to further facilitate reuse and foster libraries of different MRV Extension Sets. These can eventually serve as plug-and-play accelerators to significantly speed up project start-up time, establish common digital asset standards, and enable comparison and differentiation of digitally originated credits based on their backing data, thereby improving quality assessment and building a foundation of trust.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70a1b58f844d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Addressing Problems in Voluntary Carbon Markets]]></title>
            <link>https://medium.com/@newgatemarleyg/addressing-problems-in-voluntary-carbon-markets-07c2bef61f2e?source=rss-55a6d0d1a2a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/07c2bef61f2e</guid>
            <category><![CDATA[paris-agreement]]></category>
            <category><![CDATA[environment]]></category>
            <category><![CDATA[financial-services]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[carbon-credits]]></category>
            <dc:creator><![CDATA[Marley Gray]]></dc:creator>
            <pubDate>Fri, 03 Nov 2023 20:06:20 GMT</pubDate>
            <atom:updated>2024-11-06T20:17:33.194Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Fix the origination process, … see part 2: </em><a href="https://medium.com/@newgatemarleyg/overcoming-obstacles-in-digitizing-measurement-reporting-and-verification-of-environmental-assets-70a1b58f844d"><em>https://medium.com/@newgatemarleyg/overcoming-obstacles-in-digitizing-measurement-reporting-and-verification-of-environmental-assets-70a1b58f844d</em></a></p><p>Non-standardized, manual origination of voluntary carbon and other environmental credits is hampering scale as well as quality.</p><p>Voluntary carbon credits are basically intangible, non-financial, un-regulated assets that behave like commodities. Although this isn’t entirely accurate, it is close enough to help understand the problem. A voluntary carbon credit is intangible, meaning you can’t drive to a carbon bank and cash in a carbon credit and drive off with a ton of carbon in the back of your truck. It’s not just invisible, it&#39;s not there…it&#39;s locked away in a tree, building materials or in a geological structure under the sea.</p><p>You have to TRUST that the originated credit is actually backed by the amount of carbon it says it does. Confidence in the value of these type of assets is a direct reflection of this trust, or lack thereof. Recent reports and counter reports about the quality and trust in one category of carbon credits can drag down the whole lot of them. How, as a whole, can the voluntary market start to address this systemic problem?</p><p>Voluntary carbon credits, and other environmental assets like renewables, are <strong>data assets</strong>, where the asset is the PROOF that backs up the claim behind it.</p><p>There are hundreds of different ways someone might reduce, avoid, or remove carbon, carbon equivalence or CO2e, and new methods are being added every year. For each of these hundreds of different ways to reduce, avoid or remove CO2e, there must be a backing “program” and “methodology or protocol” that provides the rule book for how to PROVE the amount of CO2e reduced, avoided, or removed. These “programs and methodologies” are governed by organizations called “registries” that will issue credits for the “programs and methodologies” they maintain in their portfolio.</p><p>Anyone wanting to start a project to perform some activity to impact CO2e, needs to find a registry with a matching “program and methodology” to follow for their impact to be credited. Most of these programs and methodologies were initiated and evolved from the 1990s and early part of this century, meaning they are largely paper, and people driven processes that are difficult to scale for mass production and maintain quality. Additionally, each registry maintains its own “database” along with different and often overlapping portfolios of programs and methodologies with different paper and people processes for issuing credits.</p><p>This results in a fragmented source of supply that is difficult to navigate and compare. Additionally, it slows the approval of new methods of impacting CO2e as the data and process are not standardized, requiring the wheel to be invented each time.</p><p>An open standard origination process that is digital end-to-end should help create a more navigable source of supply that is much easier for markets to determine quality at a scale.</p><p>The <a href="https://gbbcouncil.org/interwork-alliance/">Interwork Alliance</a>, a part of the Global Blockchain Business Council, has been working on this standard for over three years, called the digital Measurement, Reporting and Verification (dMRV) Framework. It has quietly gone through iterative versions to refine the data model and process so that it can be used to originate ANY type of environmental asset from carbon to water.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hDHN4RN9kQa0ZnxPjknWow.png" /><figcaption>MRV Extension Set</figcaption></figure><p>The dMRV Framework provides a common, multi-party or role based, business process and data model for originating environmental assets of any type. It does this by providing extensions to the process and model so that ANY “program and methodology/protocol”, called a Quality Standard in the framework, can have its own set of extensions that “snap” right into the framework. These extensions then become a part of the system or record which provides the transparency for how a credit was originated and the detailed PROOF backing the claim AND that it was independently verified.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kP4aemRrJwsYiBb_wctx5Q.png" /><figcaption>Supply Lineage</figcaption></figure><p>For example, a decentralized solar program and methodology to create renewable energy credits (RECs), can create a “MRV Extension Set” that is specifically used to track data points at various stages, by different roles in the process and apply them to the open standard. They can also define their own asset type, i.e., credit, or use a standard credit type.</p><p>Following this open standard data model and business process allows the silos of supply to fade into the background and for the “supply chains” of different activity types to optimize a digital process. This provides the needed focus on the differentiation of their product, instead of what should be common infrastructure.</p><p>Once credits are originated in this way, distribution agents, e.g., exchanges, marketplaces, etc., and buyers can see the proof to establish trust in product quality and meaningfully compare products from different suppliers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4LFG7Ot0Sm36gigB1cuOpQ.png" /><figcaption>Compare Supply</figcaption></figure><p>Here are resources to learn more about the Voluntary Ecological Markets (VEM) and the dMRV Framework:</p><ul><li>VEM Overview — <a href="https://gbbcouncil.org/wp-content/uploads/2022/09/Voluntary-Ecological-Markets-Version-2-InterWork-Alliance.pdf">https://gbbcouncil.org/wp-content/uploads/2022/09/Voluntary-Ecological-Markets-Version-2-InterWork-Alliance.pdf</a></li><li>DMRV 2.0 <a href="https://gbbcouncil.org/wp-content/uploads/2023/09/Digital-Measurement-Reporting-Verification-dMRV-Framework.pdf">https://gbbcouncil.org/wp-content/uploads/2023/09/Digital-Measurement-Reporting-Verification-dMRV-Framework.pdf</a></li><li>V2.0 draft technical spec: <a href="https://interworkalliance.github.io/TokenTaxonomyFramework/dmrv/spec/index.html">https://interworkalliance.github.io/TokenTaxonomyFramework/dmrv/spec/index.html</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=07c2bef61f2e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New TTF Introduction Video]]></title>
            <link>https://medium.com/tokenhall/new-ttf-introduction-video-644846f7daf6?source=rss-55a6d0d1a2a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/644846f7daf6</guid>
            <category><![CDATA[token-taxonomy-framework]]></category>
            <category><![CDATA[videos]]></category>
            <dc:creator><![CDATA[Marley Gray]]></dc:creator>
            <pubDate>Tue, 11 Aug 2020 18:43:57 GMT</pubDate>
            <atom:updated>2020-08-11T18:45:10.691Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rWcE4wROxMXWVGs-4qYYBw.png" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F4CSsKAIBkjY%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D4CSsKAIBkjY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F4CSsKAIBkjY%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/40707cbeef419f4256e5cc103db3bdbe/href">https://medium.com/media/40707cbeef419f4256e5cc103db3bdbe/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=644846f7daf6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tokenhall/new-ttf-introduction-video-644846f7daf6">New TTF Introduction Video</a> was originally published in <a href="https://medium.com/tokenhall">Token Hall</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Standardizing Sustainability — How the IWA Will Make This Happen]]></title>
            <link>https://medium.com/tokenhall/standardizing-sustainability-how-the-iwa-will-make-this-happen-bc3e3b47ae69?source=rss-55a6d0d1a2a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc3e3b47ae69</guid>
            <category><![CDATA[tokenization]]></category>
            <category><![CDATA[carbon-emissions]]></category>
            <category><![CDATA[carbon-credits]]></category>
            <dc:creator><![CDATA[Marley Gray]]></dc:creator>
            <pubDate>Wed, 29 Jul 2020 17:25:52 GMT</pubDate>
            <atom:updated>2020-07-29T17:25:52.180Z</atom:updated>
            <content:encoded><![CDATA[<h3>Standardizing Sustainability — How the IWA Will Make This Happen</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0VGWOVc0JdkrCZ087Bo7Eg.jpeg" /></figure><p>In an earlier pair of blog posts, I described how the <a href="https://interwork.org/">InterWork Alliance</a> came to be and how we are focused on simplifying the digital interchange of tokenized value for virtually any use case (<a href="https://interwork.org/the-interwork-alliance-making-tokens-easy-for-business-part-1/">Part 1</a> and <a href="https://interwork.org/the-interwork-alliance-making-tokens-easy-for-business-part-2/">Part 2</a>). In Part 2, I mentioned that sustainability use cases are very clear candidates for standardization because there are significant and myriad differences among the many organizations and entities trying to define what sustainability means, how it should be measured and accounted for, and what information can be certified. I’d like to expand on this thought and show how the IWA is working to tackle this problem by ‘standardizing sustainability’.</p><h4>A starting view of sustainability — global carbon emissions mitigation</h4><p>Concerns over climate change are not just at the government level; many corporations and investors now recognize that climate-related risks are tantamount to business risks and have therefore ‘seen the light’. A large number of publicly-traded companies are already committing to deliver on a wide variety of large scale, enterprise-wide sustainability plans — more generally referred to as environmental, social, and governance (ESG) plans. In this post I’ll focus on one specific ESG use case: voluntary markets for reducing the world’s carbon footprint.</p><p>Since 1992, there have been dozens of national laws and multilateral agreements that seek to address the physical impacts of climate change and accelerate a transition away from reliance on carbon-intensive industries. The UN Framework Convention on Climate Change (UNFCCC) resulted in the signing of the <a href="https://unfccc.int/kyoto_protocol">Kyoto Protocol</a> in 1997, creating a market-based mechanism that allowed developed countries to offset their greenhouse gas (GHG) emissions by purchasing certified credits from approved and verified emission reduction projects in developing countries. These <em>carbon</em> <em>credits</em> were then linked by the European Union and other countries to national cap-and-trade regimes that regulated industries, thereby allowing companies a cost-effective means of achieving compliance based in part on the price of carbon.</p><p>Then, In 2015, 185 nations agreed to do more with emerging support from corporations and financial institutions. Under the UNFCCC <a href="https://unfccc.int/process-and-meetings/the-paris-agreement/the-paris-agreement">Paris Agreement</a>, every nation agreed to make a voluntary nationally-determined contribution (i.e. emissions reduction) toward a collective goal of keeping global temperatures under 2 degrees Celsius warming by 2050. Since then, an array of voluntary and compliance markets have been established where verified carbon credits are both cost-effective instruments to reduce global emissions as well as catalysts for financing investments in carbon-reducing products and activities.</p><p>In short, carbon credits provide a key driver and incentive for any organization committing to a sustainability plan. They enable a company the means to cost-effectively offset its own carbon dioxide emissions while giving a company the needed time to prioritize and allocate resources and capital into longer-term direct emissions reductions achieved by cleaner technologies, fuels, and supply chains. Purchasing credits allow companies to invest in climate action, claim the achievement of near-term goals, and to sell any surplus credits they do not consume to organizations that do not have enough credit to cover their own emissions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/0*_Mq0lOgvCXivBrcN.png" /></figure><p><strong>What exactly is a carbon credit?</strong></p><p>There are generally two types of carbon credits: emission allowances and carbon offsets. Emission allowances are creatures of government regulation. Allowances are regulatory permits to emit one ton of carbon-equivalent (identified as CO2e) greenhouse gases. Permits are either allocated or auctioned to regulated entities, subject to a permitted cap — meaning that the regulated entity has to purchase allowances if its actual emissions exceed its allocation. If the original owner’s actual emissions are below its allowance allocation, it can sell the surplus to other entities.</p><p>A carbon offset is an intangible asset that is created by project owners. An offset is minted when it becomes issued in an environmental registry, something that happens upon verification that one ton of CO2e greenhouse gases have either been avoided (e.g. clean electricity), reduced (e.g. sustainable fuels), or sequestered (e.g. avoided deforestation, sustainable farming) by an approved project or activity. That offset represents the original owner’s property right claims to those carbon-related benefits. The owners can then sell their credits directly to buyers or at wholesale. The ultimate end-user has the right to claim the benefits and an ability to retire the credit permanently — usually as part of netting the claimed CO2e benefits against that end-users other GHG emissions.</p><p><strong>What obstacles are there to carbon offsets?</strong></p><p>Some of the main problems with carbon credit markets have been scalability and credibility. In the 23 years since the Kyoto Protocol was first signed, government-led efforts to devise and implement meaningful climate action have been fraught with political delay, economic indecision, and lack of standardization and transparency in carbon accounting — and yes, some fraud in offset verification and permanence.</p><p>All these obstacles have occurred precisely as the reality of climate change been progressively better understood and digested by businesses and society. In lieu of government or multilateral action, the private sector’s focus has turned to voluntary carbon markets to make near-term progress while regulatory frameworks mature. In a voluntary market, organizations make ESG pledges and report their emission reduction progress as buyers, and carbon offset projects are verified by third-party auditors who deliver verification reports to registries that issue carbon offsets project owners as the original sellers.</p><p>While this sounds promising, the ecosystem around ESG pledges and the creation of offsets is still a balkanized, patchwork approach using an array of different standards, methodologies, and registry regimes. There is no common architecture globally that brings a rather unique intersection of organizations together around such an expansive challenge of measuring and verifying CO2e emission reductions — particularly when many ESG taxonomies are more qualitative than quantitative. Such disaggregation makes it very difficult to deliver the necessary incentives for a network of participants to act if the international financial markets are not properly integrated, and impossible to isolate the largest emitters if there no common means of verifying results and measuring progress.</p><p>Action is now underway to harmonize carbon accounting and to effectively create generally-accepted carbon accounting principles. Until that happens, though, the current and growing set of necessarily complex carbon accounting standards, coupled with multiple independent verifiers for reporting and numerous exchanges for trading, has left us with an unwieldy process, island exchanges, and siloed marketplaces.</p><p>At the IWA, we believe that <strong>driving standards</strong> for carbon emissions, offsets, and green energy production — as well as for trading and derivatives contracts — is key to aligning the exchange of value between organizations. Tokenizing the outputs of verified reporting standards, in a standard way, could unlock a much more robust ecosystem — leading to the establishment of a common representation of carbon accounting standards and an international, trusted distributed network for combatting climate change.</p><p>Tokenization creates cryptographically authentic value representations for emissions and offsets that also carries the data needed by all parties to determine value. Tokens are owned and can be exchanged, leveraged, bundled, referenced, insured, speculated, and consumed by the parties participating in the marketplace. The tokenization process would not replace existing processes and accounting standards, but simply establish a standard digital asset representation that references the data and processes that generated it.</p><p><strong>How the IWA is approaching the sustainability problem</strong></p><p>The members of the IWA are planning to address the needs of the carbon emissions market with a technology-neutral solution that standardizes tokenization of key elements, clauses for ledgering templates, and market-driven multi-party analytics. We believe that this will finally allow organizations with widely divergent views to define common implementation and accounting templates that are able to eliminate fraud, incentivize behavior change, be transparent, and engage new technologies.</p><p>Today the <a href="https://interworksdev.wpengine.com/standardizing-sustainability-how-the-iwa-will-make-this-happen/">IWA announced</a> the formation of our Sustainability <a href="https://interwork.org/participate/business-working-groups/">Business Working Group</a> (BWG), which will establish the standards for tokenization, contractual extensions, workflows, and analytics for GHG/Carbon emissions and offsets. These standards will serve as foundations for both voluntary and regulated carbon markets using distributed ledger techniques to create an auditable ecosystem. Initially, the primary focus will be voluntary carbon market architectures and will later expand to regulated markets; the main categories of focus will be emissions, offsets, and contracts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4YFsx0hm1dyfEWC3.jpg" /></figure><p>As an IWA BWG, members will work together at a business-need level to define this scenario and specific market requirements into a pre-framework draft, which the <a href="https://interwork.org/participate/technical-working-groups/">Technical Working Groups</a> (TWGs) will use to develop open, standards-based specifications, frameworks, and tooling that enable multi-party solutions to be built that satisfy the needs of the global carbon mitigation marketplace.</p><p>Establishing standards for reporting and tokenization can help bring trust in the global carbon ecosystem. Establishing this trust across borders, using voluntary corporate reporting matched with accurate offset token generation, can bring much needed private capital and investment to the table to help address global climate change.</p><p>I’d like to thank Cameron Prell from Xpansive, an IWA Principal Member, for his insights while writing this post. For more information and an example of the thought leadership represented in the group, I encourage you to read <a href="https://medium.com/@Xpansiv/digital-esg-commodities-1-0-4537b8187311">Principles for Building a Common Data Governance Framework for Market &amp; Environmental Integrity</a>, co-authored by Cameron and his colleague Jeff Cohen.</p><p>Are you ready to join us? <a href="https://interwork.org/join/">Become an IWA member</a> and let’s solve this problem together!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc3e3b47ae69" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tokenhall/standardizing-sustainability-how-the-iwa-will-make-this-happen-bc3e3b47ae69">Standardizing Sustainability — How the IWA Will Make This Happen</a> was originally published in <a href="https://medium.com/tokenhall">Token Hall</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The InterWork Alliance]]></title>
            <link>https://medium.com/tokenhall/the-interwork-alliance-7c39d3959216?source=rss-55a6d0d1a2a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/7c39d3959216</guid>
            <category><![CDATA[interworks]]></category>
            <category><![CDATA[wasi]]></category>
            <category><![CDATA[token]]></category>
            <dc:creator><![CDATA[Marley Gray]]></dc:creator>
            <pubDate>Fri, 19 Jun 2020 21:02:14 GMT</pubDate>
            <atom:updated>2020-06-19T21:02:14.876Z</atom:updated>
            <content:encoded><![CDATA[<h4>Making tokens easy for business (Part 2)</h4><p>In my last article, I described the work we are doing in the InterWork Alliance to improve interworking in the token-powered space by helping organizations come to agreement on how value is represented as tokens, and how contracts are written over those tokens. Let’s now take a look at how this sort of standardization can help improve business processes.</p><h4>Can interworking changes really improve business processes?</h4><blockquote>“When we first talked about the touch-screen, the guys came back and said, ‘There’s nothing like that in the automotive supply chain,’” Musk said. “I said, ‘I know. That’s because it’s never been put in a [expletive deleted] car before.” <br>― Ashlee Vance, Elon Musk: Inventing the Future</blockquote><p>Consider health care, retail, supply chains, media and entertainment — these are examples of long-established industry verticals with business processes that require some form of insurance to mitigate risk. Because there is no standard language for specifying these business processes and expressing the insurance need, and an incredibly wide range of technological standards within and across verticals, only the very largest players have the resources to understand the specific technological requirements of every consortium they would like to serve — and we tend to see ‘specialty boutiques’ pop up to deliver industry-tailored offerings.</p><p>It doesn’t have to be this way!</p><p>Think about it… consider that there’s some new vertical consortium spinning up and they need to have an easy way to add insurance into their business flows. The consortium should not be responsible for defining insurance contracts — that’s the role of an insurance company. If the consortium used the Token Taxonomy Framework (TTF) for defining the tokenized representation of whatever it is they want insured, they would have marked the token with the ‘insurable’ behavior — which simply sets the placeholder that an insurance company can later fill with the proper contractual clause. This sort of standardization at the business language level allows any company to fill the role of insurer in the consortium by writing the clause for the token that has been defined with the ‘insurable’ behavior, and that clause can simply be added into the overall consortium contract.</p><p>There are tremendous benefits for having standardization of the underlying tokens and contracts to ensure that they work together; standardization truly opens up new market opportunities for companies providing services that are commonly required across diverse industry groups.</p><p>This is the sort of interconnected, working network that the InterWork Alliance (IWA) is trying to get to, in steps. We tackled tokenization first because that’s the lowest level problem to solve. Right now, we’re starting to work on the contractual part — again, we are not talking about writing a contract but rather the building blocks of the contract to make them interoperable with other contracts and tokens themselves.</p><h4>Interworking standards set the stage for true data analytics</h4><blockquote>“It will be found, in fact, that the ingenious are always fanciful, and the truly imaginative never otherwise than analytic.” <br>– Edgar Allan Poe</blockquote><p>Related to the need to shift from a technology-first to business-first approach, we are also seeing a new pattern emerge around analytical workloads. As customers move from multi-party transactions towards multi-party contracts, they find they have a lot of “linked” data generated by these systems — and it would be really valuable if that data could be shared with contractual partners to perform some multi-party AI over it (subject of course to any restrictions that might preclude my data from being seen by competitors). How can I write a contract for this, and how can I find some way of agreeing on multi-party shared schema for these multi-party analytical workloads?</p><p>This is the emerging pattern that we are seeing. We are beginning to envision value-added multi-party analytics on top of the core trusted infrastructure where multiple parties can share or pool data to gain insights that would ordinarily be left undiscovered. We can clearly see a future for highly efficient cross industry, cross organization contracts that have access to lots of data that could be reasoned over to further streamline and optimize business processes across organizations. This might lead to new breakthroughs — perhaps in a medical field, finding inefficiencies in supply chain, or addressing sustainability challenges. Analytics is, in effect, the third part of the IWA framework triad — tokens, contractual clauses, and analytics.</p><h4>This can change the world!</h4><blockquote>“The future we will invent is a choice we make, not something that just happens.” <br>– Satya Nadella</blockquote><p>Sustainability use cases are very clear candidates for this form of standardization because of the polarization typically found among the participating groups. Think about how hard it has been to come to any form of universal agreement on global carbon mitigation.</p><p>Climate accounting is already a major growth industry — the carbon credits market has surpassed $50 billion, and the Green Bonds market is in the hundreds of billions. Environmental, Social, and Governance (ESG) reporting is already common practice among corporates worldwide, and eventually every nation and large sub-national government will need to follow suit.</p><p>But few standard solutions exist to date! UN efforts to administer a global agreement are fraught with delay and indecision over implementation and accounting standards. How does one get organizations with widely divergent views to define implementation and accounting templates that are able to eliminate fraud, incentivize behavior change, be transparent, and engage new technologies? A technology-neutral solution with standardized tokenization of key elements, standardized clauses for carbon ledgering templates, and market-driven multi-party analytics can resolve this impasse.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/962/1*3iOeCD8nlsVVpBqp-q1kBQ.png" /></figure><p>In fact, sustainability focused on carbon mitigation is one of the first use cases that we will put through our new processes at the IWA. We are right now organizing the working groups for the tokenization and the contractual layers, and in the backend looking at the analytical workloads as well to see how this would work for a use case in this domain.</p><p>The IWA is about solving big-picture pain points. We are not going to define the programming — or how you implement it all — but rather create the frameworks for how we need to tackle these workloads. We need passionate, business-focused leaders in our standards working groups who can come in and help clearly create frameworks that are usable not within just the same vertical but cross verticals. That’s the real value.</p><p>If you are of this mindset, there is plenty of room for you at the IWA! Check us out at <a href="https://interwork.org/">https://interwork.org/</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7c39d3959216" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tokenhall/the-interwork-alliance-7c39d3959216">The InterWork Alliance</a> was originally published in <a href="https://medium.com/tokenhall">Token Hall</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The InterWork Alliance — making tokens easy for business (Part 1)]]></title>
            <link>https://medium.com/tokenhall/the-interwork-alliance-making-tokens-easy-for-business-part-1-db6d85102815?source=rss-55a6d0d1a2a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/db6d85102815</guid>
            <category><![CDATA[tokenization]]></category>
            <category><![CDATA[token]]></category>
            <category><![CDATA[multi-party-computation]]></category>
            <category><![CDATA[token-economy]]></category>
            <dc:creator><![CDATA[Marley Gray]]></dc:creator>
            <pubDate>Fri, 12 Jun 2020 13:38:18 GMT</pubDate>
            <atom:updated>2020-06-12T13:38:18.935Z</atom:updated>
            <content:encoded><![CDATA[<h3>The InterWork Alliance — making tokens easy for business (Part 1)</h3><h4>Exactly how does one go about changing the world?</h4><blockquote>“Our greatest hopes could become reality in the future. With the technology at our disposal, the possibilities are unbounded.”<br>― Stephen Hawking</blockquote><p>I’ve been driving Microsoft’s blockchain strategy for the cloud even before blockchain became ‘a thing’, and it’s become very clear to me over the last year or so that our customers really want to step back and re-evaluate exactly what they’re trying to do in this space. Based on the number of quality organizations that immediately said ‘yes’ to our pitch to form a new industry organization targeting this shift, I know that it’s not just me hearing this desire for a change in approach. That message is resonating throughout the technology industry.</p><p>Organizations of all stripes want to do something more meaningful than just simple transactional blockchain workloads. They want to <em>really</em> transform the way they do business, and are starting to express this in the form of a new category of applications called ‘multi-party’ — a category that is not limited to individual platform options, eliminates any sort of hard dependencies, and is open to cloud deployments so that they have freedom of choice.</p><p>They are certainly fed up with modeling their business processes around a technical implementation that may or may not meet their actual needs. You often see companies get into trouble as they pick a technology platform for a business process and then have to augment that process to map it onto that technology platform. Over time this disconnect leads to tremendous inefficiencies because they compromised their core business to suit the needs of a technology.</p><p>What they really need, is to be able to describe their core business processes in a neutral way, a way that does not isolate them or make them feel like they’re on an island. It’s a business-down, rather than technology-up, approach that no-one is doing in any sort of consistent way. We started the <strong>InterWork Alliance</strong> — IWA — as a platform-neutral body in order to create the specifications needed to bring about this sea change in how business processes become digitized. Making this happen requires a broad and deep collaboration between private sector organizations (large and small, technology providers and consumers), governments, academics, and civil society at large that share this vision and are willing to work together to make this happen. This is the IWA!</p><h4>Business change starts with tokens, and tokens are so much more than a blockchain</h4><blockquote>“Begin at the beginning,” the King said, very gravely, “and go on till you come to the end: then stop.”<br>― Lewis Carroll, Alice in Wonderland</blockquote><p>Although the IWA has only recently launched, it builds on a strong body of work from the former Token Taxonomy Initiative (now absorbed into the IWA) — a standardized set of basic terminologies that allow us to have discussions across organizations and across institutions using the same language with reference points so we can make progress. Our work began at the most basic level, finding common ground for describing shared value that is represented on some sort of shared medium (whatever that may be; we don’t care) so that organizations have a way to exchange value point-to-point. With this common taxonomy in hand we were able to build a composition framework — the Token Taxonomy Framework (TTF) — from which we can create specifications.</p><p>The modern concept of tokenized value is not new — it first came from the blockchain space and is (unfortunately) very often thought of in terms of cryptocurrency due to the early Bitcoin and Ethereum blockchain networks. But it was pretty clear to us that there’s no need to tie tokens to blockchains, and that blockchain is really just the first step in what is a much larger, more ambitious approach to looking at how organizations work together.</p><p>A very important concept to understand is that value does not equate to cryptocurrencies. It does not even have to equate to something financial, like money — any item (physical or digital-native), or inventory unit, or even a ‘concept’ that moves across a supply chain to track progress is value that can be represented by the TTF.</p><p>A part of our low-level agreements on how we represent value includes a set of programmatic ‘hooks’ — think of them as placeholders — that link to the next level up in our stack: where multi-party contracts or agreements (there’s a whole host of terms for these, pick your favorite) are defined.</p><p>Before we tackle that layer keep in mind that, essentially, tokens are designed to be interchangeable within their own classes and used by most participants on a network. Sitting above the tokens, the contracts represent agreements between organizations (potentially private or perhaps with regulatory oversight in the industry), and those contracts need to be able to use a standard interface to the value underneath.</p><h4>When two or more things just work with each other</h4><blockquote>“I wish to be cremated. One tenth of my ashes shall be given to my agent, as written in our contract.”<br>– Groucho Marx</blockquote><p><em>Interworking</em> is <a href="https://www.merriam-webster.com/dictionary/interworking">defined by Merriam-Webster</a> as “the state or an instance of two or more things working with or being made to work with each other” — and our InterWork Alliance was formed to bring this definition to life in the token-powered space. Coming to agreement on how we represent value as tokens is just the first step in making this happen; we now have to agree on how we write contracts over those tokens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*COAVxVMoJPTZXiw0g7eNKQ.png" /></figure><p>Important point: <em>we are not talking about standardizing contracts!</em> That’s a pretty impossible goal, as contracts are almost universally unique instruments. Certainly, nobody really writes contracts from scratch, but they pull out a template of something that’s similar and then scratch out some clauses, edit others, and add in new ones to get to the point that results in a contract that satisfies negotiation. It’s those clauses that <em>can</em> be standardized — think of a world where there’s a collection of universally agreed-to clauses that are all designed to work with the agreed-to definition of value reflected by the underlying tokens. Clauses that match ‘insurable’, ‘transferrable’, ‘compliant’, and all of the different behaviors and property sets that we have defined in the TTF. There may be a dozen ‘insurable’ clauses to choose from, you just pick the one you want (or add a new one to the collection), and everything just works because all clauses are standardized to interact with the tokens in exactly the same way. Contract definitions are as composable as token definitions.</p><p>For example, let’s say that the owner of a tokenized asset has marked that asset with the ‘insurable’ behavior. We don’t want to or need to know anything about the terms and conditions of an insurance contract covering that asset — that’s between the owner of the asset and the company insuring it. Rather, we do want to define the process for that insurance contract to be able to properly connect to the underlying asset and make it an insured token. A token with the ‘insurable’ behavior can be queried to prove that it is insured without having to produce any details of the underlying contract, as long as the contract contains a standard ‘insurable’ clause.</p><p>Building up composition frameworks around agreed-to definitions of value and agreed-to contractual clauses that interact with those definitions — that’s the basic concept of the IWA! Our work crosses all industries and sets the stage for tremendous new business opportunities. In part two, I’ll discuss some of these ramifications, in the meantime check out <a href="https://interwork.org/">https://interwork.org</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db6d85102815" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tokenhall/the-interwork-alliance-making-tokens-easy-for-business-part-1-db6d85102815">The InterWork Alliance — making tokens easy for business (Part 1)</a> was originally published in <a href="https://medium.com/tokenhall">Token Hall</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New Token Taxonomy Framework 1.0 Overview Video]]></title>
            <link>https://medium.com/tokenhall/new-token-taxonomy-framework-1-0-overview-video-f495c1f4ca92?source=rss-55a6d0d1a2a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/f495c1f4ca92</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ttf]]></category>
            <category><![CDATA[token]]></category>
            <category><![CDATA[tokenization]]></category>
            <dc:creator><![CDATA[Marley Gray]]></dc:creator>
            <pubDate>Fri, 06 Dec 2019 16:21:19 GMT</pubDate>
            <atom:updated>2019-12-06T16:21:19.731Z</atom:updated>
            <content:encoded><![CDATA[<p>After about 1000 presentations and meetings explaining what the Token Taxonomy Framework is, and just as importantly, what it is NOT…I think the <a href="https://wiki.hyperledger.org/display/CMSIG/Capital+Markets+SIG">Hyperledger Capital Markets Special Interest Group</a> was able to capture one of my best “tokensplainer” sessions.</p><p><a href="https://youtu.be/bY6MpBqwiAA">https://youtu.be/bY6MpBqwiAA</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5V6Nqs_ZSMZ-2ven7ryvVw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f495c1f4ca92" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tokenhall/new-token-taxonomy-framework-1-0-overview-video-f495c1f4ca92">New Token Taxonomy Framework 1.0 Overview Video</a> was originally published in <a href="https://medium.com/tokenhall">Token Hall</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TTF 1.0 Released]]></title>
            <link>https://medium.com/tokenhall/ttf-1-0-released-6bcc13b18fae?source=rss-55a6d0d1a2a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/6bcc13b18fae</guid>
            <category><![CDATA[token]]></category>
            <category><![CDATA[multi-party]]></category>
            <category><![CDATA[github]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Marley Gray]]></dc:creator>
            <pubDate>Tue, 05 Nov 2019 21:28:05 GMT</pubDate>
            <atom:updated>2019-11-05T21:28:05.530Z</atom:updated>
            <content:encoded><![CDATA[<p>Ready, set, collaborate!</p><p>The TTF 1.0 has been released. Instead of rehashing the <a href="https://tokentaxonomy.org/global-leaders-unite-to-unveil-comprehensive-framework-for-tokenization/">press release</a>, and the subsequent news publications. Here is a quick list of links for finding out more information:</p><ul><li><a href="https://tokentaxonomy.org/">https://tokentaxonomy.org</a> — home of the organization</li><li><a href="https://github.com/token-taxonomy-initiative/TokenTaxonomyFramework">https://github.com/token-taxonomy-initiative/TokenTaxonomyFramework</a> — GitHub repo for documentation</li><li><a href="https://tokentaxonomy.org/resources/">https://tokentaxonomy.org/resources/</a> — links to sample token specifications, more documentation and videos</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5uxvnMoEWMhV5MMSOl6_iQ.png" /><figcaption>Sample Token Designer</figcaption></figure><p>Above is a sample design for tooling you can expect from organizations participating in the TTI. The TTF is not a static framework, it is a living, breathing collaboration where moving forward, various industry groups will begin conducting and participating in workshops to create new TTF artifacts and to be contributed for reuse.</p><p>Now is the time for organizations to define industry specific behaviors and property sets from Financial Services, Supply Chain, Retail, Media &amp; Entertainment and Healthcare so the entire ecosystem can benefit and move towards an interoperable tokenized world!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6bcc13b18fae" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tokenhall/ttf-1-0-released-6bcc13b18fae">TTF 1.0 Released</a> was originally published in <a href="https://medium.com/tokenhall">Token Hall</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introduction to the Token Taxonomy Framework]]></title>
            <link>https://medium.com/tokenhall/introduction-to-the-token-taxonomy-framework-1bc84daf5cc2?source=rss-55a6d0d1a2a9------2</link>
            <guid isPermaLink="false">https://medium.com/p/1bc84daf5cc2</guid>
            <category><![CDATA[ttf]]></category>
            <category><![CDATA[tti]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[taxonomy]]></category>
            <category><![CDATA[token]]></category>
            <dc:creator><![CDATA[Marley Gray]]></dc:creator>
            <pubDate>Fri, 19 Apr 2019 18:17:23 GMT</pubDate>
            <atom:updated>2020-02-11T22:28:46.695Z</atom:updated>
            <content:encoded><![CDATA[<p>When I was a kid, I loved to take things apart, too see how things worked. At first, I was not very good at it. I was rarely able put the thing I took apart back together. From the Stretch Armstrong I promptly ruined on Christmas day using a hammer and nails, a rather disappointing result, to my neighbors Merlin, which got me in a lot of trouble, note to self, don’t take apart things that don’t belong to you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*ILuf8e2va46u5ZhSN-SLyw.png" /></figure><p>Eventually, I got pretty good at putting things back together by learning how to take them apart. Careful investigation of a thing’s seams, indentations and the location of the screws. I obtained a specialty set of micro-screwdrivers with all those tiny shaped heads that were magnetized to assist in retrieving a screw that fell into a crevasse. I rigged a flashlight to a headband that required neck positions that I couldn’t hold for long.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FjDe90F7wK_DcWtYttbnaw.jpeg" /></figure><p>Anyway, the most important thing, once you have the right tools was when you removed a screw or a cover, you needed to remember where it went and then group the same screws, washers, pads and connectors together. I found that I needed to catalog these in a notebook. If I didn’t know what something was, I’d give it a name until I found out what it was.</p><p>As long I was patient and followed my procedures, I was able to put stuff back together again with confidence. I started doing this when I was 7 years old. By the time I was 10, my Dad had me rigging “Rabbit Ears” to get the best TV signal possible.</p><p><em>Side note for those of you who did not experience a time before there was cable. But Rabbit Ears where antenna used to pick up either VHF or UHF signals that TV stations were broadcast on.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/420/1*qTOhNwEB5ITmw7j7nQ0R3Q.png" /></figure><p>And when I was 12 and got my very first computer, a <a href="https://en.wikipedia.org/wiki/Texas_Instruments_TI-99/4A">TI-99/4A</a>. I took it apart and put it back together again. That was the last major thing that I took apart. I lost all interest in taking physical things apart after I wrote my first BASIC program on my rebuilt computer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*WXI8SyUTyJLro-_hBiK9OQ.jpeg" /></figure><p>If you have made it this far, you’re probably asking yourself, what does this have to do with Tokens?</p><p>Well, when I got started in blockchain and eventually tokens, I wanted to know how they worked, so I took one apart.</p><p>Much like my experience with Stretch Armstrong, I was initially disappointed when I figured out how a token worked, it was too simple. But as new platforms and tools made it possible to do more with tokens and they became much more interesting.</p><blockquote>Switching “take apart” to “decompose”. Not like in rotting flesh, but a more “formal” sounding approach.</blockquote><p>Decomposing something makes you really understand something in order to put it back together again. When I was a kid and I took something apart, I mean decomposed, and I couldn’t put it back together again or didn’t want to, I would keep the interesting parts for future use. Useful extra screws, a spare fuse, LEDs, neat looking circuit boards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*lJhvs787067pprf1vmtBbg.png" /></figure><p>This is a side effect of decomposing something, you understand the individual components and usually you find yourself looking at a problem or something that needed to be rigged or hacked and found that one of these extra parts did the trick.</p><p>The Token Taxonomy Framework (TTF) is a byproduct of my decomposition tendencies. Meaning the framework is just a collection of spare parts that do interesting things that you can reuse when you have a need for it. In fact, you may have all the basic parts in the TTF to assemble a complete token implementation. But, if you find you are missing a part, you can use the TTF to define exactly what you need in the same way all the other parts in the framework are defined. And when you are done defining your part, you contribute it back to the TTF, so the part is there waiting for someone else to discover it and reuse it.</p><p>This makes the TTF a Composition Framework. You can use the framework to decompose existing Tokens to identify its parts and if they don’t exist in the TTF, you add them.</p><p>You also use the TTF to define a new token by building as much of the token from the parts that are in the TTF and if you find something missing or could be improved, you add or update it. The more times this process is done makes the TTF better. The more industries and organizations use the TTF it becomes cross industry allowing tokens to be designed to work together. Like Insurance and Finance for documents tokens like a Title or Invoice.</p><h3>Parts are Artifacts</h3><p>So, to be a more “formal framework”, we need to use fancy names for these token parts or artifacts. Think of an envelope holding several different documents, each serving a different purpose, that when combined make an artifact.</p><p>Artifacts are grouped together, like those tiny screws, so your parts are organized for rapid assembly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*E3whSGs-g4HqUxIVoStfew.png" /></figure><blockquote>Legos come to mind here.</blockquote><blockquote>So, let’s go with that.</blockquote><blockquote>An artifact is like a Lego.</blockquote><p>We have big Legos for foundations, 2x4 Legos that are common for building most things and then we have all the specialty Legos, like the 1x1, 2x2, 1x1 round, angled tops, etc. Ok, back to tokens.</p><h3>Templates</h3><p>A token definition is a template for how to create a specific token. Like the instruction booklets for the Lego set you buy at the store. In the box, you get all the Legos you need to assemble the picture on the box. Just pull out the instruction set and follow the step by step instructions and you will produce a tangible Lego construction. I gotta admit, this process to me is rather unsatisfying, but that is just me.</p><p>In this analogy the Token Template is the instruction booklet and the finished tangible result is the Token Class. It is obvious when inspecting the class which template it was created from. You can find other constructed Tokens and know they were created from the same template. Which means, you know how that token works, even if you were not the one who put that specific Lego, I mean token, together.</p><blockquote>Token Template = Lego Instruction Booklet</blockquote><blockquote>Token Class = Finished Lego Construction from the Template</blockquote><p>The part that I dislike about instructions for Lego sets, is following all those step by step instructions and the short-lived sense of accomplishment once it is completed. Most of us, probably discard the instructions afterward and take it apart mixing all the Legos together in a big bucket never to be reconstituted in that prescribed form again. Or maybe that is just me.</p><p>With tokens, you can’t do that. Your Token class should always come from a template. That way, when someone else runs into your Token class all they need to know is what template it was created from to be able to know how to use it. This concept allows tokens to be shared on a blockchain and be useful.</p><p>When using the Token Taxonomy Framework, you are defining a template that will allow you and others to create classes of from the template that you interact with in a common way.</p><h3>Big Legos Base Token Artifacts</h3><p>The largest logical artifacts in the TTF are the base token types, which you typically choose first. Think of this artifact like the big, wide Lego that you use for a construction base.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PkskgGvzXqvwUECNYz9tBA.jpeg" /></figure><p>There are two basic types, fungible and non-fungible that share many common properties but principally differ on their relative value and uniqueness. There are also Hybrid tokens, which allow you to define combinations of parent/child definitions. If this seems obscure, which it is initially, check out the Token Map for background on the basics of Tokens.</p><h3>Divisible?</h3><p>Once you have selected your base token type, you need to figure out if you want your token to be able to be divisible. This can be super confusing at first. Money, as usual, comes to the rescue providing us with an analogy. A dollar $ is divisible up to 2 decimal places, so I can have $.50 or $.23 and even add them together to get $.73. A movie ticket token would make no sense too divide. I can’t have .23 of a receipt or movie ticket, unless there is some theater out there that will allow you to watch .23% of the movie. Hmmm.</p><h3>Behaviors</h3><p>Most of the TTF consists of behavior artifacts. Some of these behaviors are can apply to any token type like Transferable, Mint-able a.k.a. Issuable and Burnable a.k.a. Retire. These are the most commonly found behaviors and are defined in the base TTF, like a 2x4 Lego.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/225/1*r7MIFOk0LBL8q6EA-PbjyA.jpeg" /></figure><p>When you are using the TTF to define your template and there is no defined artifact for a behavior you have in mind, you can just create one. The TTF allows you to describe what the behavior is, provide analogies and define how one would invoke or tell the token to demonstrate the behavior. An artifact is just a collection of files that you create by filling in some standard forms. When satisfied that you have captured the essence of the behavior, you contribute it or add it to the framework. You or others can reuse it in the future in another context.</p><p>A behavior reflects some business function of the token like Financeable or Insurable and in the future, you are likely to find a diverse set of them from all industries. These business and industry specific behaviors are like specialized Lego pieces.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pDeorJaEycxOtGO9I5ayTA.png" /></figure><h3>Behavior Groups</h3><p>Sometimes you will find combinations of behaviors that are used repeatedly. The TTF, for example, has one called Supply Control that bundles Mint, Burn and Roles together. When you add this to your template your token will support the minting or issuing of new tokens in the class, allow the burning or retiring of tokens and support assigning a role or group to the mint or issue behavior. The Lego Window piece is a good example.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*K0c_bCVYYuZe-tTmsGwaFA.jpeg" /></figure><h3>Composition</h3><p>Using the base, behavior and behavior groups you can begin building your template. Behind the scenes the TTF requires each individual artifact have a unique symbol.</p><p>Weird aspect here, a symbol to represent a token artifact is like a token of a token, kind of.</p><p>So, a base token type symbol is either:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/86/1*uf1K_eSxcet1XxPi-QEvXA.png" /><figcaption>Fungible</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/96/1*e_ZljKdbY452x3QDKemV7w.png" /><figcaption>Non-fungible</figcaption></figure><p>Hybrids can be:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/252/1*J2GifUZkDatT3nyacTOqvQ.png" /><figcaption>Fungible with class of non-fungibles</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/242/1*YwloAAbyvW6LahdDjn6Gpg.png" /><figcaption>Non-fungible with class of fungibles</figcaption></figure><p>for a fungible token class with any number of non-fungible child classes or a non-fungible token class with a fungible class. Hybrids could add multiple classes and one of these could be another hybrid. Which can get complex, if needed.</p><p>Behaviors are given lower case letter or letters, usually in <em>italic</em>. The symbols must be unique to the framework. You add a behavior or behavior group to a template definition using braces with a comma between them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/378/1*ZLkrG8sSTjIxtE5xm-Jtow.png" /><figcaption>Fungible token class with mint, burn and role support.</figcaption></figure><p>Which brings us to Behavior Groups. Their symbols are UPPER case letters, like Supply Control is SC. So, the template formula above is the same as:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/242/1*6hEK3RfoUL_LsAmMp81p2g.png" /></figure><h3>Property Sets</h3><p>Properties are like data fields for a token. Properties are either behavioral or non-behavioral. A behavioral property means that it is required and controlled by a behavior, like setting its value. A non-behavioral property can stand alone allowing its value to be set directly and is applied to the token base.</p><p>For example, the Roles behavior indicates that the token class should support the notion of a role or group that can have members. The role can then be bound to another behavior to indicate that only members of the role can invoke the behavior. I.e. Supply Control defines a Minters role that is bound to the Mint-able behavior. So, the Minters role is behavioral property, meaning that you have to use the Roles Behavior to add or remove a member of the Minters group.</p><p>A non-behavioral property might be something like an item SKU or Serial Number. There is no specific behavior tied to these properties but defining them in a property set artifact and adding it to your template means that the token explicitly implements the property so a user of the token will know that it is there.</p><p>Both types of properties can be defined in a property set. A behavioral property will have a dependency on a behavior to set its value, usually via logic or calculation that is defined by the behavior. Where a non-behavioral property can have its value set directly by the token owner or another account that has permission.</p><p>A property set symbol is prefixed with a:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/70/1*d8AjozCLx-M_yD849iFObg.png" /><figcaption>phi</figcaption></figure><p>followed by case insensitive letters that are unique in the framework property set collection. For example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*PuepHfosq5r_3xfHfTwh5A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/218/1*2Prk9O6Cb6bKokhPi88NDQ.png" /></figure><p>are the same. To add a property set, you add them to the token formula by surrounding the token and behaviors with brackets [] and +. If more than one is added they can be placed in braces {}. I.e.:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/356/1*xjbZH3O7GYnii7EnYksj0w.png" /><figcaption>Non-fungible class, that is non-sub-dividable with the SKU property set.</figcaption></figure><p>This introduces some properties that can be true or false which you want to clearly indicate the value. So, the above has a behavior ~<strong><em>d</em></strong> where the <strong><em>d</em></strong> is the symbol for sub-dividable the apostrophe means the opposite. So, if applied to a behavior it means that it is not or false.</p><h3>End</h3><p>Some key points to wrap up.</p><ul><li>You don’t need to be able to read a token formula, at all. The symbols are links to the artifact’s documentation which contains full words and completely understandable sentences that are used to display the names and descriptions of the artifact or part. The symbols are used mostly by tools and developers to create extensions to the framework.</li><li>This is not a complete overview of the framework but does cover all of the main concepts.</li><li>The Token Taxonomy Initiative will be improving, enhancing and validating the framework over the next couple of months. So, some concepts may expand, or contract and new concepts will be added.</li></ul><p>I will post additional articles will be added to the series over the coming weeks to supplement the framework documentation and explain or pose other background topics.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1bc84daf5cc2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tokenhall/introduction-to-the-token-taxonomy-framework-1bc84daf5cc2">Introduction to the Token Taxonomy Framework</a> was originally published in <a href="https://medium.com/tokenhall">Token Hall</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>