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

feat: add zenlink rpcs to parachain service #886

Merged
merged 1 commit into from
Jan 25, 2023

Conversation

gregdhill
Copy link
Member

Signed-off-by: Gregory Hill [email protected]

Exposes all Zenlink RPCs on the parachain node.
Bumped the Zenlink dependencies to use a newer version of jsonrpsee.
Renamed Zenlink stable pallet ID from bf/stamm to stbl/amm - will need manual migration for existing pools.

@gregdhill gregdhill force-pushed the feat/zenlink-rpc branch 3 times, most recently from 89bfb20 to 00a09b1 Compare January 24, 2023 17:49
@@ -1617,4 +1617,109 @@ impl_runtime_apis! {
.and_then(|liquidity| liquidity.to_rpc_tuple())
}
}

impl zenlink_protocol_runtime_api::ZenlinkProtocolApi<Block, AccountId, CurrencyId> for Runtime {
Copy link
Member

Choose a reason for hiding this comment

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

Why add these rpcs to standalone if they don't have an actual implementation?

Copy link
Member Author

@gregdhill gregdhill Jan 25, 2023

Choose a reason for hiding this comment

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

Because the rpc crate requires those runtime APIs and since we anyway plan to deprecate standalone I didn't want to add the actual Zenlink code there.

@gregdhill gregdhill merged commit 1a1afa9 into interlay:master Jan 25, 2023
@gregdhill gregdhill deleted the feat/zenlink-rpc branch January 25, 2023 12:20
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