-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove eras older than Babbage support in transaction build
and transaction build-estimate
#878
Remove eras older than Babbage support in transaction build
and transaction build-estimate
#878
Conversation
9440560
to
c5e1eda
Compare
transaction build
transaction build
transaction build
transaction build
460f8a0
to
7ea384c
Compare
transaction build
transaction build
and transaction build-estimate
7ea384c
to
2166c72
Compare
@@ -386,7 +382,7 @@ runTransactionBuildEstimateCmd -- TODO change type | |||
txOuts <- mapM (toTxOutInAnyEra sbe) txouts | |||
|
|||
-- the same collateral input can be used for several plutus scripts | |||
let filteredTxinsc = toList @(Set _) $ fromList txInsCollateral | |||
let filteredTxinsc = nubOrd txInsCollateral |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool, I didn't knew about nubOrd
💯
would this affect the |
@gitmachtl no it's only for |
2166c72
to
d243fc8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few comments. This needs to be updated as mainnet is now in the Conway era.
[ Opt.flag' (Exp.Some Exp.BabbageEra) $ | ||
mconcat | ||
[ Opt.long "babbage-era" | ||
, Opt.help "Specify the Babbage era (default)" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will need to be updated because mainnet is now in the Conway era.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it have to be updated though? Changing this will also change the behaviour of legacy commands, like making some options mandatory, suddenly.
If we're going to ditch legacy
and latest
, I would see this as a slight inconvenience for users which would accelerate the switch to era-based commands hierarchy.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I changed my mind while working on some deprecations in the cli. We are going to keep legacy
and latest
.
@@ -168,7 +169,7 @@ runLegacyTransactionCmds = \case | |||
runLegacyTransactionBuildCmd | |||
:: () | |||
=> SocketPath | |||
-> EraInEon ShelleyBasedEra | |||
-> Exp.Some Exp.Era |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to introduce a deprecation message for the legacy commands as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added deprecation for legacy transaction.
I think you've started working on this:
so it becomes out of scope of this PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR can be merged as is. I'll rebase mine on it.
|
||
envCliAnyShelleyToBabbageEra :: EnvCli -> Maybe (EraInEon ShelleyToBabbageEra) | ||
envCliAnyShelleyToBabbageEra envCli = do | ||
envCliAnyEon :: Typeable eon => Eon eon => EnvCli -> Maybe (EraInEon eon) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is called in parsers like pShelleyBasedShelley
which are not used. We can delete them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's also used in pAnyShelleyToBabbageEra
and in pAnyShelleyBasedEra
which are still in use.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was referring to parsers like pShelleyBasedShelley
which I see have been removed already.
one question, so in the future if will not be possible to generate "shelley-era" style transactions anymore if you just wanna send lovelaces around, right? |
We will expose a transaction building command that will be parameterized on the era. Currently it will only be able to spend tx inputs and accept update proposals. This is for our QA team to test hardforks from Byron -> $currentEra. |
d243fc8
to
6b65485
Compare
6b65485
to
803485a
Compare
803485a
to
9ab866f
Compare
9ab866f
to
20fa071
Compare
Changelog
Context
Requires cardano-api with:
Checklist