Skip to content

Verify Offchain SDKs without the conwayHardForkAtEpoch and shiftStartTimeBehind configurations #114

@satran004

Description

@satran004

The following properties were introduced to avoid additional cost model entries (10 extra) for PlutusV2 when the devnet starts directly from the Conway era at epoch 0, because these extra entries create issues for script transactions if the cost model is hardcoded in the application. While this is acceptable for regular transactions (both script and non-script), it causes issues with ledger-state calculations such as rewards and governance state as it changes the stability window.

Similarly, when these flags are enabled, during the slotToUnixTime conversion, zeroSlot needs to be set to the same value as epochLength instead of 0, which creates some confusion among users.

conwayHardForkAtEpoch=1
shiftStartTimeBehind=true

More details about the current work-around here.
#65

We need to verify whether to remove these settings from the default configuration and keep them as optional, so that users can revert to the current default behavior by setting these properties.

But before changing the existing default settings, we need to verify them with the following off-chain SDKs.

  • Cardano Client Lib
  • Lucid Evolution
  • MeshJs
  • PyCardano
  • Blaze Cardano
  • Apollo Tx

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions