Carrot White Paper
Back to Carrot Website ▶
  • CARROT NETWORK
  • documentation
    • Introduction
      • Recycling Systems Are Broken
      • Earth Limitations
      • From Linear to Circular
      • What is Zero Waste?
      • Extended Producer Responsibility
      • Carbon Markets: From Problem to Solution
      • Greenwash & ESG
      • Solution
    • The Product
      • Carrot Network
        • Creating Value
        • dMRV
        • Creating a Market
        • Demand-Side Market
        • Atomic Network
        • Methodology Creators
        • Ownership
        • Summary Diagram
      • Recycling Supply Chain
        • Reaching the Source of Waste Creation
        • Participants
        • Validators & SOs
        • Local vs Long Hauling
      • MassIDs: Codifying Waste
        • Participant Categories and Wallets
        • MassID Composition
        • MassID Notation
        • MassID Creation
        • MassID Splits
        • Waste Validation & Audits
        • Proof-of-Authority
        • Proof-of-Work & Provenance
      • Recycling Tokens
        • Minting TRCs
        • TCC (Carbon Credits)
          • GasID Creation
          • GasID Notation
          • Minting TCCs
          • Calculating GasIDs
          • GasIDs from Composting
          • TCCs from Composting
        • Carrot Registry (EPR/ESG)
        • $CARROT Distribution Model
          • Waste Source Not Identified
        • Carbon Credit Tokens from Composting
      • Tokenomics
        • Supply and Demand
        • AMM & LPs
        • $CARROT Stablecoins/Fiat
        • Burn-As-A-Service
        • Lending & Forwards
        • Carrot Ecosystem Fees
        • Carrot Incentive Mechanism
        • Tokenomics Conclusion
      • Value Proposition
        • Network Integrators
        • Producers (Credit Buyers)
        • Recyclers, Haulers & Processors
        • Waste Generators
        • Bin Custodians
        • State and Federal
        • Municipalities
        • Fund Managers
        • NGOs & Donors
        • Partners
        • External Service Providers (ESPs)
      • Closing the Loop
        • Proof-of-Recycled-Content
        • Product Composition
        • Local Recyclability
      • Product Roadmap
        • Product Decentralization
        • Protocol Selection
    • Governance
      • Carrot DAO
        • $CARROT Token Governance
        • Carrot Improvement Proposal Process
        • Carrot DAO Maintenance and Processes
        • Carrot Retroactive Funding
      • Progressive Decentralization
        • Incentives for Participation
        • 3 Phases of Decentralization
      • Security
        • Community Values
        • Community Guidelines
        • Holder Reputational System
    • The Carrot Foundation
      • Mission
      • Goals
      • Vision
      • $CARROT Allocation
      • $CARROT Supply
      • Treasury Reserve
      • Wallet Onboarding
      • The Genesis Team
      • Community Fund
      • Launch Strategy
      • NFT Auctions w/ Options
      • Stewards & Board
      • Advisors
      • Founders
    • Conclusion
      • Acknowledgements
    • Appendix
      • Formula comparison Between TRCs And TCCs
      • Formula for Project and Leakage Emissions From Composting
      • Formula For Baseline Emissions of CO2
      • CWIP Process (Extended)
      • Generating Reputational Metrics
      • Applying Reputational Metrics
      • Holder Reputational System Token Implementation
  • Carrot Methodologies
    • Glossary
    • Rewards Distribution Policy
    • BOLD Recycling Credit
    • BOLD Carbon (CH4)
  • More
    • Terms & Conditions
      • T&C of Use
      • T&C for Sales and Purchases of TRCs and TCCs
    • Download White Paper
  • Connect With Us
    • Website
    • Discord
    • E-mail Carrot Team
Powered by GitBook
On this page
  1. documentation
  2. The Product
  3. MassIDs: Codifying Waste

Participant Categories and Wallets

PreviousMassIDs: Codifying WasteNextMassID Composition

Last updated 1 year ago

Where... CoC is the recycling chain of custody P is a Participant Category

CoC={P0,P1,P2,P3,P4,P5}CoC={\{P_0,P_1,P_2,P_3,P_4,P_5\}}CoC={P0​,P1​,P2​,P3​,P4​,P5​}
P0=Waste GeneratorP_0=Waste\:GeneratorP0​=WasteGenerator
P1=Bin Custodian(s)P_1=Bin\:Custodian(s)P1​=BinCustodian(s)
P2=Hauler(s)P_2= Hauler(s)P2​=Hauler(s)
P3=Processor(s)P_3=Processor(s)P3​=Processor(s)

in the case when... a Participant Category has more than one wallet,the subset contains all wallet–IDs

Note that while the Waste Generator and Bin Custodian are usually the same party, offering different roles to each provides opportunities for “shared economy” solutions for public bins. For example, a Gas Station may offer space and bin supervision, serving as a Bin Custodian, for individuals (Waste Generators) to drop off glass bottles. A Bin Custodian can also work with a Bin Sponsor, such as a Consumer Packaged Goods company (CPGs,) a Producer Responsibility Organizations (PRO,) and/or a Non-Governmental Organization (NGO) to share the costs of setting up specialty recycling bin networks while also receiving a portion of $CARROT rewards from recycled MassIDs. In the example above, Coca-Cola could work with gas stations to help fund the recovery of glass bottles.

Other participant categories (Haulers, Processors and Software Providers) may also involve more than one contributor in the recycling process. Expanding further on the prior example, Hauler 1 may perform the pick-up of glass bins at local gas stations in a town, while a different transporter (Hauler 2,) may carry cullet from an accumulation center in town to a different city where a glass bottling plant is located. In this case, there would also be two Processors, the local accumulating facility (Processor 1) and the glass bottling plant (Processor 2.) Processor 2, would serve as a Processor and a Recycler obtaining a $CARROT token allocation for each role.

In the example of more than one Hauler, the set (CoC) would be defined as:

P_2\: is\: the\: 'Hauler' \:participant\: category

The set (CoC) would then be defined as:

or in the instance of multiple processors

The set (CoC) would then be defined as:

These insights on recycling chain of custody (CoC) help to explain how a MassID (CoC) is defined.

P4=Recycling FacilityP_4=Recycling\: FacilityP4​=RecyclingFacility
P5=Chain–of–Custody Logistics Software(s)P_5=Chain–of–Custody \:Logistics \:Software(s)P5​=Chain–of–CustodyLogisticsSoftware(s)
Px={i0,i1,i2,...,iN}P_x={\{i_0 ,i_1 ,i_2 ,...,i_N\}}Px​={i0​,i1​,i2​,...,iN​}
i=Wallet IDi = Wallet \:IDi=WalletID
N=Number of Walletsin a Participant CategoryN = Number \:of \:Wallets in\: a \:Participant \:Category N=NumberofWalletsinaParticipantCategory
where...where...where...
i0 is the wallet–ID of Hauler onei_0 \:is \:the \:wallet–ID \:of\: Hauler \:onei0​isthewallet–IDofHaulerone
i1 is the wallet–ID of Hauler twoi_1 \: is\: the \:wallet–ID \:of \:Hauler\: twoi1​isthewallet–IDofHaulertwo
P2={i0,i1}P_2={\{i_0,i_1\}}P2​={i0​,i1​}
CoC={P0,P1,{i0,i1},P3,P4,P5}CoC={\{P_0,P_1, {\{i_0, i_1\}} ,P_3,P_4,P_5\}}CoC={P0​,P1​,{i0​,i1​},P3​,P4​,P5​}
where...where...where...
i2 is the wallet–ID of Processor onei_2\: is \:the \:wallet–ID \:of \:Processor\: onei2​isthewallet–IDofProcessorone
i3 is the wallet–ID of Processor twoi_3\: is \:the\: wallet–ID \:of \:Processor\: twoi3​isthewallet–IDofProcessortwo
P3={i2,i3}P_3={\{i_2,i_3\}}P3​={i2​,i3​}
CoC={P0,P1,P2,i2,i3,P4,P5}CoC={\{P_0,P_1,P_2,{i_2,i_3} ,P_4,P_5\}}CoC={P0​,P1​,P2​,i2​,i3​,P4​,P5​}