Skip to content

(feat) ReadChainConfig endpoint #151

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 23, 2025
Merged

Conversation

SebastienGllmt
Copy link
Contributor

This PR is an alternative to #147 that combines everything to a single endpoint with field masks instead

message EraBoundary {
uint64 time = 1; // ms timestamp
uint64 slot = 2; // absolute slot number of the first block of this era
uint64 epoch = 3; // first epoch for this era
Copy link
Contributor Author

@SebastienGllmt SebastienGllmt Apr 1, 2025

Choose a reason for hiding this comment

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

This is the structure you get from the Cardano node. In #147 I added an extra hash field, but I leave it out for this PR since this is the less controversial option, and we have to separately solve #148 anyway

string name = 1; // name of the era (ex: "shelley")
EraBoundary start = 2; // start of this era
EraBoundary end = 3; // end of this era (if the era has a well-defined ending)
string config = 4; // encoded structure of the configuration for this era
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This would be the JSON encoding of the genesis file for that era

@scarmuega scarmuega merged commit 356bfeb into utxorpc:main Apr 23, 2025
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.

2 participants