Skip to content
    hazBasehazBaseDocs
    USE CASES
    All use cases

    Participation in urban infrastructure projects

    Organize project participation, resident input and operating reports.

    Receivables & participationExample architecture

    The scenario

    ForInfrastructure operators, development companies and public-project teams

    Manage contract-defined participation units for charging facilities or shared mobility, linking operating reports and user input to the same project.

    What this makes visible

    Access participant holdings, facility status, reports and governance records from one project.

    Token and business-data roles

    Represented by tokens

    This composition represents participation units with FlexibleToken. Distinguish resident feedback from voting with contractual decision authority.

    Managed in business systems

    Project ID, facility register, agreements, income/expenses, operating reports and resident feedback.

    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
    FlexibleTokenTrack contract-defined participation units and holdings.
    GenericGovernorManage proposals and votes under defined participation rules.
    TimelockControllerApply execution delays to approved operations.

    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. Register the project

      Link facilities, operators, participation conditions and reporting units.

    2. Record participation

      Allocate to approved participants and map agreements to holdings.

    3. Share operations and feedback

      Aggregate operational data in business systems and share it by access level. Define the scope of any vote.

    4. Record decisions and history

      Distinguish approved decisions from execution and connect them to funding and facility reports.

    Operating considerations

    Participant roles

    Manage distinct qualifications when holders, residents and operators have different access or decision rights.

    Revenue accounting

    Calculate facility income and expenses in business systems, then reconcile contract-based allocations with holdings.

    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.