carp
carp copied to clipboard
Enable Plutus context in tx history endpoint
trafficstars
Currently the transaction history endpoint gives just the transaction body (and minimal amount of information about inputs)
In order to be sufficient for use-cases that need more context for Plutus use-cases, we need the following:
- [ ] To know what the redeemers for the transaction were (see #183)
- [ ] To know the full input content instead of just the addresses (see #184)
- [ ] To include the full reference inputs (instead of just the regular tx inputs) as they may contain Plutus inline datums we need
- [ ] To include any datum in the witness