-
Notifications
You must be signed in to change notification settings - Fork 766
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
Make trusted Teleporters and Reserves queryable through Runtime APIs #97
Comments
This issue has been mentioned on Polkadot Forum. There might be relevant details there: |
Can we expose this as runtime APIs rather than adding to Metadata? The configuration is a filter not an actual list of (asset, location). Any particular benefit for one over the other? |
Yeah good point, runtime API would be fine IMO. Just as long as wallets can easily get the information. |
We'll prioritize this. It's easy and important. We'll provide runtime APIs for:
|
We could extend this to reserves and have another API for it. They have the same format |
Implemented is_trusted_reserve and is_trusted_teleporter API methods. Tested them with regular and chopstick tests. Fixes #97 --------- Co-authored-by: Francisco Aguirre <[email protected]>
The issue will be closed once these API methods are integrated in fellowship-runtimes Polkadot and Kusama |
Some applications would like to know if certain chains are Trusted Teleporters or not. This will affect how they treat DOT/KSM deposits on those chains, or on the extrinsics they construct to interact with the Relay Chain.
AFACT, one must look up the Trusted Teleporters in the source code, e.g. https://github.com/paritytech/polkadot/blob/release-v0.9.19/runtime/polkadot/src/xcm_config.rs#L114
The text was updated successfully, but these errors were encountered: