fix(koios): explicitly order epoch_params to get current epoch#208
Merged
solidsnakedev merged 2 commits intomainfrom Mar 16, 2026
Merged
fix(koios): explicitly order epoch_params to get current epoch#208solidsnakedev merged 2 commits intomainfrom
solidsnakedev merged 2 commits intomainfrom
Conversation
Koios preview load-balances across backend nodes with different DB row orderings. Without an explicit sort, epoch_params?limit=1 randomly returns a stale epoch (e.g. 646 with 251 PlutusV3 cost model entries) instead of the current one (297 entries), causing PPViewHashesDontMatch when submitting transactions with Plutus scripts.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes non-deterministic protocol parameter resolution when querying Koios epoch_params (notably on preview), ensuring the SDK consistently uses the latest epoch’s cost model and avoids downstream scriptDataHash mismatches.
Changes:
- Add an explicit
order=epoch_no.descto the Koiosepoch_paramsrequest while keepinglimit=1. - Add a patch changeset documenting the fix.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| packages/evolution/src/sdk/provider/internal/KoiosEffect.ts | Makes getProtocolParameters deterministic by ordering epoch params by newest epoch. |
| .changeset/fix-koios-epoch-params-ordering.md | Adds a patch-level release note for the Koios epoch ordering fix. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Koios preview load-balances across backend nodes whose PostgREST databases return rows in different physical order. Without an explicit
orderparameter,epoch_params?limit=1non-deterministically returns either the current epoch (297 PlutusV3 cost model entries) or a stale pre-Plomin epoch (251 entries). When the stale epoch is returned, the SDK computes ascriptDataHashwith the wrong cost model, causingPPViewHashesDontMatchon transaction submission.Adds
&order=epoch_no.descto the Koiosepoch_paramsquery solimit=1always returns the most recent epoch, regardless of backend node ordering.