You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Integrators are asking for a way to easily access some info about the transactions returned by these RPC calls. Some use cases include:
Calculating the actual fees paid by a TX - can be derived if the input contained the amounts
Figuring out the "source address" of utxos - can be derived if the input contained the SPK
Describe the solution you'd like
Adding a new flag that can be set for each of the RPC APIs above. If the flag is set, then also include the full transaction data with the full UTXO data in inputs (not just txid and index).
Describe alternatives you've considered
Tracking the transactions manually or using api.kaspa.org - these are infeasible and rely on external data sources when the data is well within the node anyway (before it's pruned).
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Integrators are asking for a way to easily access some info about the transactions returned by these RPC calls. Some use cases include:
Describe the solution you'd like
Adding a new flag that can be set for each of the RPC APIs above. If the flag is set, then also include the full transaction data with the full UTXO data in inputs (not just txid and index).
Describe alternatives you've considered
Tracking the transactions manually or using api.kaspa.org - these are infeasible and rely on external data sources when the data is well within the node anyway (before it's pruned).
Additional context
N/A
The text was updated successfully, but these errors were encountered: