Is your feature request related to a problem?
Since AEIP21 the transaction inputs stored for each transaction makes no sens as they are now not received by the transaction but by the genesis address.
They are still existing for retro compatibility in graphql queries and are used by explorer to display the available inputs for a transaction.
Describe the solution you'd like
We should deprecate the transaction inputs query since application should adapt to the new AEIP21 way off getting inputs history.
And explorer may be presented differently to show related transaction details.
Additional context
This would free a lot of DB space on storage nodes and will reduce self repair / validation network traffic
For old transactions, to not lose traceability we could move the transaction inputs in the consumed inputs list even if it was not created in the validation stamp at this time
Epic
No response
Is your feature request related to a problem?
Since AEIP21 the transaction inputs stored for each transaction makes no sens as they are now not received by the transaction but by the genesis address.
They are still existing for retro compatibility in graphql queries and are used by explorer to display the available inputs for a transaction.
Describe the solution you'd like
We should deprecate the transaction inputs query since application should adapt to the new AEIP21 way off getting inputs history.
And explorer may be presented differently to show related transaction details.
Additional context
This would free a lot of DB space on storage nodes and will reduce self repair / validation network traffic
For old transactions, to not lose traceability we could move the transaction inputs in the consumed inputs list even if it was not created in the validation stamp at this time
Epic
No response