Skip to content
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

Add Pontus-X support #639

Merged
merged 5 commits into from
Feb 20, 2024
Merged

Add Pontus-X support #639

merged 5 commits into from
Feb 20, 2024

Conversation

mitjat
Copy link
Contributor

@mitjat mitjat commented Feb 13, 2024

This mostly involves just copy-paste of all the sapphire initialization code.

I did a tiny refactor in node_stats. Further decluttering should be possible in cmd/analyzer in a future PR. But in general, the whole process was fairly painless and quick.

Testing: None yet; I don't have access to a functioning node.

go.mod Outdated
@@ -6,6 +6,7 @@ toolchain go1.21.3

replace (
github.com/cometbft/cometbft => github.com/oasisprotocol/cometbft v0.37.2-oasis1
github.com/oasisprotocol/oasis-sdk/client-sdk/go => /home/mitjat/oasis/oasis-sdk/client-sdk/go
Copy link
Contributor Author

Choose a reason for hiding this comment

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

PR requires https://github.com/oasisprotocol/oasis-sdk/pull/1638/files and a new SDK release, then this override can go away. In a rush, we can hardcode this part of the SDK config into nexus temporarily.

Copy link
Member

@ptrus ptrus left a comment

Choose a reason for hiding this comment

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

Also update api spec?

@csillag
Copy link
Contributor

csillag commented Feb 14, 2024

Also update api spec?

Can we use #637 for that?

@mitjat mitjat force-pushed the mitjat/pontusx-support branch from d9fa7a9 to f549c34 Compare February 15, 2024 19:13
@mitjat
Copy link
Contributor Author

mitjat commented Feb 15, 2024

Also update api spec?

Can we use #637 for that?

Thanks, I prefer to do it here though so all the changes are in one PR. Commit added.

@csillag
Copy link
Contributor

csillag commented Feb 15, 2024

Also update api spec?

Can we use #637 for that?

Thanks, I prefer to do it here though so all the changes are in one PR. Commit added.

Yeah we don't need a separate PR.
My point with that PR was only to provide a base for code generation for explorer.

As as long as your API changes are compatible, we are good.

@mitjat mitjat force-pushed the mitjat/pontusx-support branch from 9452ae7 to 5e65dc7 Compare February 20, 2024 22:34
@mitjat mitjat merged commit d4c8314 into main Feb 20, 2024
9 checks passed
@mitjat mitjat deleted the mitjat/pontusx-support branch February 20, 2024 22:48
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.

3 participants