TransferRequest

​

Fields

​

Usage Example

use taple_core::{
    EventRequest, TransferRequest,
    DigestIdentifier, KeyIdentifier
};

// Transfer ownership of a subject to a new owner
let transfer_request = EventRequest::Transfer(TransferRequest {
    subject_id: DigestIdentifier::from_str(
        "JXtZRpNgBWVg9v5YG9AaTNfCpPd-rCTTKrFW9cV8-JKs"
    ).unwrap(),
    public_key: new_owner_key,
});

// Example: Transfer an asset in a supply chain
let asset_transfer = EventRequest::Transfer(TransferRequest {
    subject_id: asset_id.clone(),
    public_key: buyer_public_key.clone(),
});

​

Notes

• TransferRequest is wrapped in the EventRequest::Transfer variant
• Authorization required: Only the current owner of the subject can initiate a transfer
• This request does not require evaluation and approval from the governance
• The transfer creates a new event in the subject’s event chain
• The subject’s state is not modified by the transfer, only the ownership changes
• After transfer, only the new owner can perform operations on the subject
• The previous owner loses all control over the subject after the transfer is completed

​

Transfer Process

1. The current owner creates and signs a transfer request
2. The request is submitted to the TAPLE network
3. The network verifies that the requester is the current owner
4. A transfer event is created and added to the subject’s event chain
5. The subject’s owner field is updated to the new public key
6. The new owner can now perform operations on the subject

​

Use Cases

• Asset transfers: Transfer ownership of physical or digital assets tracked on TAPLE
• Supply chain: Transfer custody of goods as they move through the supply chain
• Credential delegation: Transfer control of credentials or certifications
• Organizational changes: Transfer subjects between departments or organizations

​

Related Types

• EventRequest
• DigestIdentifier
• KeyIdentifier