Skip to content

Conversation

@Jimbo4350
Copy link
Contributor

@Jimbo4350 Jimbo4350 commented Oct 23, 2025

Changelog

- description: |
    Deprecate "old" certificate api helper functions and introduce equivalent functions exposed by:
      `Cardano.Api.Compatible.Certificate`
      `Cardano.Api.Experimental.Certificate`
  type:
  - feature     
  - refactoring   
  projects:
  - cardano-api

Context

Additional context for the PR goes here. If the PR fixes a particular issue please provide a link to the issue.

How to trust this PR

Highlight important bits of the PR that will make the review faster. If there are commands the reviewer can run to observe the new behavior, describe them.

Checklist

  • Commit sequence broadly makes sense and commits have useful messages
  • New tests are added if needed and existing tests are updated. See Running tests for more details
  • Self-reviewed the diff

@Jimbo4350 Jimbo4350 force-pushed the jordan/backwarks-compatible-certificates branch from 8a5595f to 6519563 Compare October 23, 2025 20:15
@Jimbo4350 Jimbo4350 force-pushed the jordan/backwarks-compatible-certificates branch from 6519563 to 81b7a98 Compare October 23, 2025 20:20
@Jimbo4350 Jimbo4350 changed the title Backwards compatible certificates Deprecate "old" certificate api helper functions Oct 24, 2025
@Jimbo4350 Jimbo4350 force-pushed the jordan/backwarks-compatible-certificates branch 2 times, most recently from 71a4ef9 to b968b7b Compare October 24, 2025 14:34
@Jimbo4350 Jimbo4350 marked this pull request as ready for review October 24, 2025 14:35
@Jimbo4350 Jimbo4350 force-pushed the jordan/backwarks-compatible-certificates branch 2 times, most recently from d261519 to a73bd18 Compare October 24, 2025 20:05
@Jimbo4350 Jimbo4350 force-pushed the jordan/backwarks-compatible-certificates branch from a73bd18 to 2d0f85b Compare October 27, 2025 14:58
@Jimbo4350 Jimbo4350 force-pushed the jordan/backwarks-compatible-certificates branch from afaa27a to 44a52ba Compare October 27, 2025 18:33
@Jimbo4350 Jimbo4350 force-pushed the jordan/backwarks-compatible-certificates branch from 44a52ba to 44a720e Compare October 27, 2025 18:46
, L.EraTxOut (LedgerEra era)
, L.EraUTxO (LedgerEra era)
, FromCBOR (ChainDepState (ConsensusProtocol era))
, FromCBOR (L.TxCert (LedgerEra era))
Copy link
Contributor

@carbolymer carbolymer Oct 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment on lines +34 to +37
( Typeable ledgerera
, L.Era ledgerera
, FromCBOR (L.TxCert ledgerera)
, L.EraTxCert ledgerera
Copy link
Contributor

@carbolymer carbolymer Oct 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Those four constraints feel redundant here, because:

  1. they're provided by Era and EraTxCert ledger constraints https://cardano-ledger.cardano.intersectmbo.org/cardano-ledger-shelley/Cardano-Ledger-Shelley-TxCert.html#t:TxCert
  2. Certificate already provides EraTxCert
  3. They're not really necessary for the implementation of HasTextEnvelope

Comment on lines +48 to +50
( Typeable ledgerera
, L.Era ledgerera
, FromCBOR (L.TxCert ledgerera)
Copy link
Contributor

@carbolymer carbolymer Oct 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same thing, those three constraints feel redundant here, because they're provided by EraTxCert ledger constraints https://cardano-ledger.cardano.intersectmbo.org/cardano-ledger-shelley/Cardano-Ledger-Shelley-TxCert.html#t:TxCert

@Jimbo4350 Jimbo4350 force-pushed the jordan/backwarks-compatible-certificates branch from 945ec57 to f6ab5fd Compare October 28, 2025 19:02
@Jimbo4350 Jimbo4350 force-pushed the jordan/backwarks-compatible-certificates branch from f6ab5fd to 61e76fa Compare October 28, 2025 20:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants