-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
Context
There is currently no way to retrieve the events (logs) generated by a transaction. This data is useful for any client that needs to display or process what happened during a transaction execution (e.g. transfers, smart contract calls). The Qubic official Explorer is one example of a consumer, but this endpoint would be useful for other dapps.
Request
Input:
- the transaction hash
- Filters: event type, source (?), destination (?)
note: source and destination is with ? because if we have a single point and already will support that for 'free' then we could also use it for this scenario, no need to add extra conditions to prevent the use of these filters - Pagination parameters (optional, with default values)
Expected response
An array of events objects. Filtering and pagination are not needed.
Related
Needed by qubic/explorer-frontend#214

Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
π Backlog