new tracing: more strictness storing traced DataPoints
Jan 06, 12-1 PM (10)
Jan 06, 1-2 PM (13)
Jan 06, 2-3 PM (16)
Jan 06, 3-4 PM (14)
Jan 06, 4-5 PM (26)
Jan 06, 5-6 PM (23)
Jan 06, 6-7 PM (40)
Jan 06, 7-8 PM (16)
Jan 06, 8-9 PM (21)
Jan 06, 9-10 PM (12)
Jan 06, 10-11 PM (74)
Jan 06, 11-12 AM (29)
Jan 07, 12-1 AM (17)
Jan 07, 1-2 AM (10)
Jan 07, 2-3 AM (11)
Jan 07, 3-4 AM (33)
Jan 07, 4-5 AM (6)
Jan 07, 5-6 AM (0)
Jan 07, 6-7 AM (1)
Jan 07, 7-8 AM (15)
Jan 07, 8-9 AM (26)
Jan 07, 9-10 AM (33)
Jan 07, 10-11 AM (23)
Jan 07, 11-12 PM (28)
Jan 07, 12-1 PM (52)
Jan 07, 1-2 PM (67)
Jan 07, 2-3 PM (30)
Jan 07, 3-4 PM (44)
Jan 07, 4-5 PM (45)
Jan 07, 5-6 PM (23)
Jan 07, 6-7 PM (16)
Jan 07, 7-8 PM (28)
Jan 07, 8-9 PM (11)
Jan 07, 9-10 PM (11)
Jan 07, 10-11 PM (33)
Jan 07, 11-12 AM (20)
Jan 08, 12-1 AM (3)
Jan 08, 1-2 AM (18)
Jan 08, 2-3 AM (2)
Jan 08, 3-4 AM (12)
Jan 08, 4-5 AM (7)
Jan 08, 5-6 AM (4)
Jan 08, 6-7 AM (7)
Jan 08, 7-8 AM (9)
Jan 08, 8-9 AM (23)
Jan 08, 9-10 AM (18)
Jan 08, 10-11 AM (23)
Jan 08, 11-12 PM (33)
Jan 08, 12-1 PM (22)
Jan 08, 1-2 PM (27)
Jan 08, 2-3 PM (43)
Jan 08, 3-4 PM (26)
Jan 08, 4-5 PM (49)
Jan 08, 5-6 PM (25)
Jan 08, 6-7 PM (31)
Jan 08, 7-8 PM (11)
Jan 08, 8-9 PM (27)
Jan 08, 9-10 PM (17)
Jan 08, 10-11 PM (52)
Jan 08, 11-12 AM (19)
Jan 09, 12-1 AM (7)
Jan 09, 1-2 AM (19)
Jan 09, 2-3 AM (19)
Jan 09, 3-4 AM (15)
Jan 09, 4-5 AM (18)
Jan 09, 5-6 AM (10)
Jan 09, 6-7 AM (7)
Jan 09, 7-8 AM (8)
Jan 09, 8-9 AM (34)
Jan 09, 9-10 AM (55)
Jan 09, 10-11 AM (15)
Jan 09, 11-12 PM (36)
Jan 09, 12-1 PM (33)
Jan 09, 1-2 PM (71)
Jan 09, 2-3 PM (63)
Jan 09, 3-4 PM (45)
Jan 09, 4-5 PM (24)
Jan 09, 5-6 PM (35)
Jan 09, 6-7 PM (11)
Jan 09, 7-8 PM (19)
Jan 09, 8-9 PM (32)
Jan 09, 9-10 PM (28)
Jan 09, 10-11 PM (29)
Jan 09, 11-12 AM (23)
Jan 10, 12-1 AM (1)
Jan 10, 1-2 AM (3)
Jan 10, 2-3 AM (12)
Jan 10, 3-4 AM (3)
Jan 10, 4-5 AM (0)
Jan 10, 5-6 AM (3)
Jan 10, 6-7 AM (0)
Jan 10, 7-8 AM (1)
Jan 10, 8-9 AM (1)
Jan 10, 9-10 AM (1)
Jan 10, 10-11 AM (0)
Jan 10, 11-12 PM (0)
Jan 10, 12-1 PM (1)
Jan 10, 1-2 PM (0)
Jan 10, 2-3 PM (1)
Jan 10, 3-4 PM (1)
Jan 10, 4-5 PM (2)
Jan 10, 5-6 PM (0)
Jan 10, 6-7 PM (0)
Jan 10, 7-8 PM (0)
Jan 10, 8-9 PM (0)
Jan 10, 9-10 PM (1)
Jan 10, 10-11 PM (26)
Jan 10, 11-12 AM (31)
Jan 11, 12-1 AM (0)
Jan 11, 1-2 AM (3)
Jan 11, 2-3 AM (0)
Jan 11, 3-4 AM (3)
Jan 11, 4-5 AM (5)
Jan 11, 5-6 AM (5)
Jan 11, 6-7 AM (1)
Jan 11, 7-8 AM (0)
Jan 11, 8-9 AM (1)
Jan 11, 9-10 AM (1)
Jan 11, 10-11 AM (0)
Jan 11, 11-12 PM (1)
Jan 11, 12-1 PM (0)
Jan 11, 1-2 PM (9)
Jan 11, 2-3 PM (0)
Jan 11, 3-4 PM (3)
Jan 11, 4-5 PM (3)
Jan 11, 5-6 PM (4)
Jan 11, 6-7 PM (3)
Jan 11, 7-8 PM (5)
Jan 11, 8-9 PM (6)
Jan 11, 9-10 PM (2)
Jan 11, 10-11 PM (19)
Jan 11, 11-12 AM (20)
Jan 12, 12-1 AM (2)
Jan 12, 1-2 AM (2)
Jan 12, 2-3 AM (2)
Jan 12, 3-4 AM (7)
Jan 12, 4-5 AM (1)
Jan 12, 5-6 AM (1)
Jan 12, 6-7 AM (9)
Jan 12, 7-8 AM (40)
Jan 12, 8-9 AM (30)
Jan 12, 9-10 AM (21)
Jan 12, 10-11 AM (49)
Jan 12, 11-12 PM (29)
Jan 12, 12-1 PM (31)
Jan 12, 1-2 PM (27)
Jan 12, 2-3 PM (25)
Jan 12, 3-4 PM (64)
Jan 12, 4-5 PM (26)
Jan 12, 5-6 PM (46)
Jan 12, 6-7 PM (21)
Jan 12, 7-8 PM (17)
Jan 12, 8-9 PM (17)
Jan 12, 9-10 PM (29)
Jan 12, 10-11 PM (30)
Jan 12, 11-12 AM (33)
Jan 13, 12-1 AM (4)
Jan 13, 1-2 AM (7)
Jan 13, 2-3 AM (11)
Jan 13, 3-4 AM (7)
Jan 13, 4-5 AM (8)
Jan 13, 5-6 AM (44)
Jan 13, 6-7 AM (7)
Jan 13, 7-8 AM (6)
Jan 13, 8-9 AM (17)
Jan 13, 9-10 AM (91)
Jan 13, 10-11 AM (25)
Jan 13, 11-12 PM (20)
Jan 13, 12-1 PM (0)
3,029 commits this week
Jan 06, 2026
-
Jan 13, 2026
new-tracing: sanitize some fallback values
Update from ef0162a74dbd585e2f79dfd55ccf172795288e55
Not limit ChainStateHistory by 2160
The history does not contain all ticked points anymore, but only states when observations were made an the last known point. If that is too little, we can aggregate the last x points to try to find an intersection on demand. See https://github.com/cardano-scaling/hydra/issues/2437 for more details
Further simplify Chain interface by using ChainPointType
This is deliberately a ChainPointType and not a ChainStateType because modifications to the state-to-keep-track are only expected upon observations and rollbacks.
Added kes-agent-1.0.0.0
From https://github.com/input-output-hk/kes-agent at 80b344fe967da98680944f3af8c1502610f87490
Added kes-agent-crypto-1.0.0.0
From https://github.com/input-output-hk/kes-agent at 80b344fe967da98680944f3af8c1502610f87490
Add newtype wrapper around IPv4 and IPv6
Draft a growing utxo benchmark dataset
Merge pull request #1320 from IntersectMBO/mgalazyn/chore/fix-tutorial-link-in-readme
Fix tutorial link in README
Deploying to gh-pages from @ IntersectMBO/plutus@49fa8348353375b57e9a20c0438a4daea888eafe 🚀
WIP Split BlockSupportsPeras instance and base types
This commit splits the PerasCert and PerasVote types defined as part of the degenerate global BlockSupportsPeras instance into separate modules. This is the first step of a series of changes needed to define a proper BlockSupportsPeras instance for individual block types and the HFC.
Avoid leaky abstraction of IsChainState
This does not force the Simple instance to use the Cardano type (ChainPoint) and prepares usage of the parametric type ChainPointType in the Hydra.Chain interface.
Switch to only persisting ChainPoint on TickObserved
This should keep the overhead minimal by only adding block header hashes next to slot numbers. It remains a breaking change though.
Use all of history when selecting a prefix for chain sync
This should retain the original logic where start chain from was used if it was newer than the last known persisted point.
Simplify Greetings again to only report on currentSlot
This does not break abstraction and expose cardano specifics on the websocket server. Also, we can use the NodeState to report on this and don't need to provide the chain state history (avoids coupling).
fix(athena): compilation issue
deploy: 922d69bff5eae145ba9572ab698d1ddcf921f85c
Merge pull request #2919 from input-output-hk/djo/2878/add-config-secret
feat: add `ConfigSecret` type and use it for aggregator blockfrost configuration
Master rebase
Signed-off-by: Sasha Bogicevic <[email protected]>
fix(ledger-api): update ParamName for new valueContains parameters
Update parameter names to reflect the piecewise linear cost model: - ValueContains'cpu'arguments'constant (above-diagonal constant) - ValueContains'cpu'arguments'model'arguments'intercept - ValueContains'cpu'arguments'model'arguments'slope1 (x_mem coefficient) - ValueContains'cpu'arguments'model'arguments'slope2 (y_mem coefficient) These replace the previous two parameters (intercept, slope) from the multiplicative model.
docs(website): add 'testing-preview' DMQ network configuration
docs(website): update DMQ configuration file in signer setup guide