Skip to content
    hazBasehazBaseDocs
    USE CASES
    All use cases

    Conservation support and outcome records

    Connect support intake, field activity and verified outcomes.

    Energy & environmentExample architecture

    The scenario

    ForConservation groups, community organizers and corporate reporting teams

    Issue participation records to supporters of coastal cleanup or planting projects, sharing dates, activities and supporting evidence by project.

    What this makes visible

    Distinguish supported activities from subsequently verified results and trace the evidence behind reports.

    Token and business-data roles

    Represented by tokens

    Use PrivilegeEdition for support/participation and MultiTrustCredential for reviewed metrics, updated by authorized issuers.

    Managed in business systems

    Activity ID, location/date, work records, photos, measurement method, reviewer and use of contributions.

    Map project, asset or order IDs to chainId, contract address and tokenId where applicable. Link the operation ID to the confirmed transaction so the application can trace the result.

    Contract composition

    ContractRole in this use case
    PrivilegeEditionRecord support and participation tiers.
    MultiTrustCredentialManage reviewed metrics and their updates.
    VerifierVerify proofs when a matching proof scheme is used.

    Follow each contract for its key operations, SDK and source. Select the components your workflow needs and connect them to business approvals and records.

    User and processing flow

    1. Define activities and metrics

      Define the activity, measurement and reviewer.

    2. Record support and participation

      Verify support or participation and issue the relevant record.

    3. Review the results

      Review field evidence and register or update approved metrics.

    4. Report with evidence

      Report the period, method and reviewer alongside outcomes, retaining correction history.

    Operating considerations

    Outcome verification

    Recording data on chain does not verify field facts. Specify verification methods and responsible reviewers.

    Certificates and records

    Link activity reports, participation records and externally certified instruments through their respective identifiers.

    Review approvals, reconciliation and recovery

    Implement this use case

    These implementation patterns provide architectures, data models, processing steps and SDK examples. Start with the capabilities this use case requires.