Monitor a request

Once a subscription or a redemption request is in place, its whole lifecycle can be monitored either by reading the events emitted by the shares contract, or by synchronously getting the status directly from it.

Asynchronous Events

Below are the most important events when it comes to monitoring the lifecycle of a given request.

Subscription

Event	Description
SubscriptionRequest	Subscription request created
SubscriptionApproval	Subscription request approved
SubscriptionCancellation	Subscription request cancelled by the user or receiver
SubscriptionDenial	Subscription request denied by a fund operator
SubscriptionRequestExpired	Subscription request TTL has elapsed without any explicit action being made

Redemption

Event	Description
RedemptionRequest	Redemption request created
RedemptionApproval	Redemption request approved
RedemptionCancellation	Redemption request cancelled by the user or receiver
RedemptionDenial	Redemption request denied by a fund operator
RedemptionRequestExpired	Redemption request TTL has elapsed without any explicit action being made

Synchronous Check

If the current request status must be synchronously queried, the shares contract exposes a function that allows precisely that:

• getRequest(uint256 id)

  • The id parameter corresponds to the subscription/redemption ID, returned upon request creation.

The function returns a data structure with the following fields:

• requestType

• requestStatus

• asset

• assetAmount

• sharesAmount

• investor

• receiver

• timestamp

• expiryAt