The invreq_metadata subject in BOLT12 is used to offer extra details about the bill request that may assist distinguish between completely different bill requests related to the identical provide or move. This subject permits nodes to connect arbitrary metadata to the bill request, which may serve to determine, classify, or present context for the request.
Examples of what the information within the invreq_metadata subject would possibly appear like embody:
Person ID or Session ID: A singular identifier for a person or session that pertains to the request, facilitating monitoring or administration of a number of requests for a similar provide by a single person.
{
“user_id”: “12345”,
“session_id”: “abcde”
}
Contextual Tags: Tags that signify the aim of the bill request, comparable to “subscription”, “one-time buy”, or “donation”.
{
“tags”: [“subscription”]
}
Timestamp or Expiration Knowledge: A timestamp indicating when the request was created, or a flag indicating if the request is time-sensitive.
{
“created_at”: “2023-10-01T10:00:00Z”,
“expires_at”: “2023-10-02T10:00:00Z”
}
Customized Fields: Any extra fields {that a} node could need to embody for customized processing wants.
{
“custom_field”: “some_value”
}
The invreq_metadata is certainly a helpful method for a node to handle and distinguish between completely different open bill requests, particularly once they may need overlapping particulars, comparable to a number of requests for a similar provide. Moreover, the individuality of bill requests may also be supported by different options comparable to distinctive identifiers within the request itself, relying on the implementation.