Closed biofreeze closed 9 months ago
@biofreeze thanks for reporting. I managed to reproduce. This is a bug on how we build the json output for transaction details for pre-babbage blocks. The end result, as you noticed, is a transaction record with missing collateral info.
We're working to release a patch for v1 versions ASAP.
We've merged the fixed. This is what the json output looks like for the same tx:
{
"context": {
"block_hash": "faaeda2a014e0ad176e06837978c2f663ab0fab5f5874b079b886398099b97be",
"block_number": 6703641,
"certificate_idx": null,
"input_idx": null,
"output_address": null,
"output_idx": null,
"slot": 49503576,
"timestamp": 1641069867,
"tx_hash": "f9ed2fef27cdcf60c863ba03f27d0e38f39c5047cf73ffdf2428b48edbe83234",
"tx_idx": 3
},
"fingerprint": null,
"transaction": {
"collateral_input_count": 1,
"collateral_inputs": [
{
"index": 0,
"tx_id": "9a2dbf8fa8ca07b43f5592cd00e7fa5d12d4fdf7bc511a15f05e9657a598e5b4"
}
],
"collateral_output": null,
"fee": 373665,
"has_collateral_output": false,
"hash": "f9ed2fef27cdcf60c863ba03f27d0e38f39c5047cf73ffdf2428b48edbe83234",
"input_count": 1,
"inputs": [
{
"index": 1,
"tx_id": "944cb825a06993865dcf5d8e80354ed5afa1bcfb2f17b179c139a5bae23594cd"
}
],
"metadata": null,
"mint": null,
"mint_count": 0,
"native_witnesses": [],
"network_id": null,
"output_count": 1,
"outputs": [
{
"address": "addr1vxk5cxgnfqkgzh25ztf6zj5p3h9pnk2mxp3xwe2pzh72rtg0nf5cs",
"amount": 2726335,
"assets": [],
"datum_hash": null,
"inline_datum": null
}
],
"plutus_data": [
{
"datum_hash": "2c14cb7463238191c1786dfdcc37012c2fa8534f87f22b75d8f5dc3ecf4f4d74",
"plutus_data": {
"constructor": 0,
"fields": [
{
"constructor": 0,
"fields": [
{
"bytes": "ad4c1913482c815d5412d3a14a818dca19d95b306267654115fca1ad"
},
{
"bytes": "a0028f350aaabe0545fdcb56b039bfb08e4bb4d8c4d7c3c7d481c235"
},
{
"bytes": "484f534b59"
},
{
"int": 1000000
}
]
}
]
}
}
],
"plutus_redeemers": [
{
"ex_units_mem": 0,
"ex_units_steps": 0,
"input_idx": 0,
"plutus_data": {
"constructor": 0,
"fields": []
},
"purpose": "spend"
}
],
"plutus_witnesses": [
{
"script_hash": "15b95fdaceeb507073a1bd198803373beeafbd82560fbf8abe9073ff",
"script_hex": <redacted>
}
],
"size": 4957,
"total_output": 2726335,
"ttl": 49503712,
"validity_interval_start": null,
"vkey_witnesses": [
{
"signature_hex": "9f858a30c5a53f2aba8955e6c33126e818f6701cd21137b017f972b4dc31c42e9e229d3e02c4cfad443e3e4f034caf1681f94bc6a2b3cc83c6aa9dc3ef4e6001",
"vkey_hex": "92c5efea5bf9a8fa1f1eaf2e97e7cf425122c034f360abaf44ea9fb56622e919"
}
],
"withdrawals": null
}
}
My Oura config looks like this
I've come across a transaction as follows:
If you go to the transaction on CardanoScan page for this transaction however https://cardanoscan.io/transaction/f9ed2fef27cdcf60c863ba03f27d0e38f39c5047cf73ffdf2428b48edbe83234?tab=collateral, you'll notice that the transaction does indeed have a Collateral Input, yet the data above says:
and
Is there any specific reason for this? This is a failed transaction, which took the collateral from the user. I figured this would be reflected in the transaction data, however it's not.