Private participation receipt

Used in the Nondominium and TrueCommons hApps by Sensorica.

With respect to Holochain: Private Participation Receipts are cryptographically signed, cumulative records stored as private entries in an agent's source chain. They serve as proof of reliable participation in a p2p network and form the foundation for a generative reputation system.

Core Principles

• Bi-directional Issuance: Receipts are issued between agents involved in each economic interaction
• Cryptographic Integrity: All receipts are cryptographically signed for authenticity
• Multi-role Support: Agents can accumulate receipts across multiple roles simultaneously
• Privacy Preservation: Receipt details remain private while enabling reputation derivation
• ValueFlows Compliance: Modeled as specialized Claims within the ValueFlows ontology

Fundamental Concepts

Commitments and Fulfillments

• Commitments: Actions (resource creation, transfer, maintenance) are formally committed by agents
• Validations: Fulfillments that confirm commitments have been properly executed
• Good Faith Usage: Users commit to honest usage practices (reporting damage, avoiding monopolization)

Receipt Generation Logic

• Two Receipts Per Action: Each economic interaction generates exactly 2 bi-directional receipts between participating agents
• Implicit Resource Validation: Resource validation is implicit through agent validation (except for creation events)
• Agent-Focused: Receipts track agent behavior and reliability, not resource state changes

Praxis: Nondomonium hApp

Issuance Categories

Resource Creation Events: Resource Creation & Validation (Single Transaction)

Trigger: A resource is registered on the network and validated by another agent

Generated Receipts (2 total):

• Creator Agent: Receives "successful resource contribution" receipt
• Validator Agent: Receives "network validation performed" receipt

Special Case: Resource creation is an event requiring explicit validation receipts, as it establishes the resource's entry into the network

Custody Transfer Events: Resource Custody Transfer

Trigger: Resource custody is transferred between agents

Generated Receipts (2 total):

• Outgoing Custodian: Receives "responsible custody transfer" receipt
• Incoming Custodian: Receives "custody acceptance" receipt

Note: Resource validation is implicit through the custodian agents' reliability; no separate validation receipts needed

Specialized Service Receipts: Participant Structure: Involves 2 or 3 agents (original custodian, intermediate service provider, final recipient). Thus, the Resource is transferred from original custodian (User) to intermediate service provider, back to another or the same User.

Maintenance Service

- Commitment Phase: Service provider commits to maintenance duties

Generated Receipts (2 total):

• Maintenance Agent: Receives "maintenance commitment accepted" receipt
• Custodian Agent: Receives "Good faith transfer" receipt

- Fulfillment Phase: Commitment is fulfilled through completed maintenance and resource available again

Generated Receipts (2 total):

• Maintenance Agent: Receives "maintenance fulfillment completed" receipt
• Resource Recipient: Receives "custody acceptance" receipt

Storage Service

- Commitment Phase: Service provider commits to storage duties

Generated Receipts (2 total):

• Storage Agent: Receives "storage commitment accepted" receipt
• Custodian Agent: Receives "Good faith transfer" receipt

- Fulfillment Phase: Commitment is fulfilled through resource custodian transfer

Generated Receipts (2 total):

• Storage Agent: Receives "storage fulfillment completed" receipt
• Resource Recipient: Receives "custody acceptance" receipt

Transport Service

- Commitment Phase: Service provider commits to transport duties

Generated Receipts (2 total):

• Transport Agent: Receives "transport commitment accepted" receipt
• Custodian Agent: Receives "Good faith transfer" receipt

- Fulfillment Phase: Commitment is fulfilled through completed transport and resource delivery

Generated Receipts (2 total):

• Transport Agent: Receives "transport fulfillment completed" receipt
• Resource Recipient: Receives "custody acceptance" receipt

Role Chaining Mechanics

• Multi-role Agents: Agents can hold multiple intermediate roles simultaneously, ex. they can hold credencials for transport, maintenance and storage at the same time.
• Action Chaining: Service Agents can chain multiple actions (transport → repair → transport) within a single commitment
• Self-Managed Chains: Intermediate steps don't require external validation
• Atomic Transactions: Entire chain treated as single commitment/fulfillment cycle

Example Workflow: Transport + Repair Service

1. Initial State: Lynn (custodian) → Resource needs repair
2. Service Request: Lynn requests Bob (transport + repair credentials) to service resource

Commitment Phase:

Bob commits to: receive → transport → repair → transport → deliver

Mutual signatures create bi-directional receipts:

  - Lynn → Bob: "Service commitment accepted" receipt

  - Bob → Lynn: "Good faith transfer" receipt

Execution Phase:

Bob executes action chain without intermediate validation

Internal status changes (transport → repair → transport) for the resource are self-managed, pending validation.

Completion Phase:

Resource delivered to final recipient (Lynn or another recipient agent)

Final bi-directional receipts:

  - Bob → Recipient: "custody acceptance" receipt

  - Recipient → Bob: "Transport + Repair fulfillment completed" receipt

Additional PPR Contexts

Network Governance

Dispute Resolution Participation: Receipts for constructive participation in conflict resolution

• Validation Activities: Receipts for performing validation duties beyond specific transactions
• Rule Compliance: Receipts for consistent adherence to governance protocols

Quality Assurance

Economic Event Completion: Receipts for successfully completing any EconomicEvent

• Commitment Fulfillment: Receipts when claims properly link commitments to their fulfillment
• Performance Standards: Receipts for meeting or exceeding quality thresholds

ValueFlows Integration

PPRs are implemented as specialized PrivateParticipationClaim entries that extend the standard ValueFlows Claim structure. This design maintains ValueFlows compliance while enabling the cumulative reputation system essential for nondominium governance.

Resource End-of-Life Management

Resource Decommissioning

Critical Lifecycle Completion: Resources require formal end-of-life processing to prevent abuse vectors and maintain network integrity.

Resource End-of-Life Declaration

• Trigger: Resource becomes permanently unusable, damaged beyond repair, or deliberately retired
• Security Concern: This event is a potential attack vector where agents might claim resources are "destroyed" to steal or monopolize them

Generated Receipts (2 total):

• Declaring Agent: Receives "end-of-life declaration submitted" receipt
• Validator Agent: Receives "end-of-life validation performed" receipt

Strict Validation Requirements- To prevent end-of-life abuse:

• Multiple Validators Required: Minimum 2-3 validators must confirm end-of-life status
• The number of validators required can be adjusted based on the resource's value and sensitivity
• The declarator agent can't be a validator and even less than the disposal agent
• The validators must be experts (maintainers) that can validate the resource's condition and authenticity
• Evidence Documentation: Physical evidence (photos, inspection reports) required
• Validator Accountability: Validators become liable for false end-of-life approvals
• Historical Review: Past custodians notified and can challenge the declaration
• Time-Delayed Finalization: 7-14 day challenge period before final decommissioning
• Reputation Impact: False end-of-life declarations severely impact declaring agent's reputation
• Resource final transfer: Resource can not stay with the declaring agent. Validators can transfer the resource to a storage for broken resource in waiting for reparation attempt or definitively decommission it.

Complete Resource Lifecycle

This comprehensive lifecycle ensures complete accountability from resource creation through final decommissioning, with enhanced security measures protecting against end-of-life abuse vectors.