EOLRequest

​

Fields

​

Usage Example

use taple_core::{
    EventRequest, EOLRequest,
    DigestIdentifier
};

// Mark a subject as end-of-life
let eol_request = EventRequest::EOL(EOLRequest {
    subject_id: DigestIdentifier::from_str(
        "JXtZRpNgBWVg9v5YG9AaTNfCpPd-rCTTKrFW9cV8-JKs"
    ).unwrap(),
});

// Example: Retire a decommissioned sensor
let retire_sensor = EventRequest::EOL(EOLRequest {
    subject_id: sensor_id.clone(),
});

// Example: Close a completed project
let close_project = EventRequest::EOL(EOLRequest {
    subject_id: project_id.clone(),
});

​

Notes

• EOLRequest is wrapped in the EventRequest::EOL variant
• Authorization required: Only the current owner of the subject can mark it as end-of-life
• This request does not require evaluation and approval from the governance
• Once a subject is marked as EOL, no further events can be added to it
• The EOL operation creates a final event in the subject’s event chain
• The subject’s state and event history remain accessible after EOL
• This operation is irreversible - a subject cannot be reactivated after being marked as EOL

​

EOL Process

1. The subject owner creates and signs an EOL request
2. The request is submitted to the TAPLE network
3. The network verifies that the requester is the current owner
4. A final EOL event is created and added to the subject’s event chain
5. The subject is marked as end-of-life in the database
6. Any further event requests for this subject will be rejected

​

Use Cases

• Device decommissioning: Mark IoT devices or sensors as no longer active
• Project completion: Close subjects representing completed projects or initiatives
• Asset disposal: Mark physical assets that have been disposed of or destroyed
• Credential expiration: Terminate subjects representing expired credentials or certifications
• Contract termination: Mark subjects representing contracts that have been completed or terminated
• Data lifecycle management: Formally close subjects as part of data retention policies

​

Important Considerations

• Ensure you truly want to terminate the subject before sending an EOL request
• Consider archiving or exporting important data before marking as EOL
• The subject’s complete history remains auditable even after EOL
• EOL subjects still count toward storage and may be subject to data retention policies
• Some systems may implement additional cleanup or archival processes for EOL subjects

​

Related Types

• EventRequest
• DigestIdentifier