-
Notifications
You must be signed in to change notification settings - Fork 14
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
AMM RPC endpoints for UI integration #220
Conversation
Co-authored-by: Marcel Ebert <[email protected]>
add farming rpc api for foucoco
Co-authored-by: Marcel Ebert <[email protected]>
… into 207-implement-lp-rewards-on-amm
@TorstenStueber in case you are wondering why we need yet another fork, I looked into this with Nikita and we tried to |
207 implement lp rewards on amm (#208) * add bifrost-farming and bifrost-farming-rpc-runtime-api dependency * introduce T::CurrencyId to bifrost farming pallet * add farming runtime rpc to foucoco * Update runtime/foucoco/src/lib.rs * fix build in foucoco runtime with FoucocoTreasuryAccount * add patch for git and crates io * update pr according to request changes in PR #208 * Add farming rpc api intou pendulum node for foucoco runtime (#216) add farming rpc api for foucoco * move PoolId type declaration to runtime common * renaming create_full_spacewalk_foucoco -> create_full_foucoco create_full_spacewalk -> create_full_amplitude create_full -> create_full_pendulum * replace "introduce-abstraction-for-currency-id" to "polkadot-v0.9.37" * Update runtime/common/src/lib.rs * renaming start_node_impl() -> start_node_impl_pendulum() start_node_impl_spacewalk_foucoco() -> start_node_impl_foucoco() start_node_impl_spacewalk_amplitude() -> start_node_impl_amplitude() --------- Co-authored-by: Marcel Ebert <[email protected]>
C::Api: ZenlinkProtocolRuntimeApi<Block, AccountId, AssetId>,
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I said in the comments I would not introduce a separate development config now. At least not as part of this PR. If this is needed then let's do that somewhere else, after discussing it
@ebma it means that it not possible anymore to use the same function as for pendulum and development runtime. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay I see. I was not fully aware what's added to the development runtime. AFAIK we don't really use it. But it's probably the right step to also add other functions for that, now that we basically split everything up per network anyways.
The rest LGTM.
I am a little confused about the issues and PRs and how they are linked. This PR here is linked with an issue (#217), which itself is linked to another PR (#218), then you mention issue #219. Is there a way to clean up the PR <-> issue structure? |
@TorstenStueber |
@@ -766,6 +771,192 @@ where | |||
Ok((task_manager, client)) | |||
} | |||
|
|||
/// Start a node with the given parachain `Configuration` and relay chain `Configuration`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@RustNinja where is all of this code coming from? Is the code duplication now even getting worse?
If it is just duplicated code, then fine. If there are any crucial changes to the duplicated code here, can you point them out?
PR related to #217
and pendulum-chain/Zenlink-DEX-Module#1
PR based on top of this PR(it is already merged)