Closed felix-lipski closed 1 month ago
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days.
Not sure what we want to do with this one. The thread that started this stream of work got quite deep: https://github.com/IntersectMBO/cardano-cli/pull/534
cc @Jimbo4350
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 120 days.
The
calculate-min-fee
command should support the following scenarios:The user submits an unsigned tx body specifying the number of byron/shelley witnesses they desire.
or shelley or both) to construct a "bogus" tx and callgetMinFeeTx
. We return only the fee in this case otherwise the users will have to remove the bogus witnesses if we returned the resulting tx. Constructing the dummy witnesses will allow us to avoid implementing something likecalculateByronWitnessFees
.The user submits a signed tx or an unsigned tx body along with the signing keys they intend to validate the tx with.
The user submits a signed tx without the signing keys needed to validate the tx. We simply return the fee as we can't return a valid tx.
As referenced in this comment on PR#534
The first scenerio is currently being worked on/completed. This issue only pertains to the second and third scenerio.