v3.0.0-rc1 : Full Refactor and ConwayEra Support
Pre-release
Pre-release
v3.0.0-rc1 : Full Refactor and ConwayEra Support
Changes on kuber-server
- Add new chain-query api-endpoints.
- GET /api/v3/protocol-params
- GET /api/v3/chain-point
- GET /api/v3/utxo
- GET /api/v3/system-start
- GET /api/v3/genesis-params
- Update default healthcheck url in docker image. (
/api/v3/chain-point
is used for healthcheck ) - Server starts by querying NodeEra and enables fields based on
BabbageEra
orConwayEra
- TxBuilder json now supports following new fields.
- $.proposal[s] : Conway Era Governance proposals.
- $.votes[s] : Conway Era votes.
- $.certificate[s] : Registration and dregistration certs only for Conway era. (Not available when node is running in babbage era).
Release Docker image [supports only x86_64 architecture]
Known Issues:
- If node is at Babbage era when kuber-server starts, after node reaches Conway era, restart is required to enable Conway features.
$.validtyStart
is broken and is ignored when building transaction.
Changes on Kontract-example [WIP]
- Introduced new package to showcase usage of
Kontract
Changes on lib:kuber
- Update code comments for better haddock docs generation
- Implement both
ToJson
andFromJson
for all the entities used in api - Reorganize code and introduction of
Kontact
for offchain code. - Support For ConwayEra [BREAKING change ]
TxBuilder
is now parametrized onera
suppportingBabbage
andConway
eras, withIsTxBuilderEra
constraint.- Kuber Offchain code required Local Node Socket. WIP support running kuber code by connecting to kuber server
- Remove
ChainConnectInfo
and related classes. Instead, useLocalNodeConnectInfo CardanoMode
directly.