-
Notifications
You must be signed in to change notification settings - Fork 30
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 integritee chain support #134
Conversation
Encointer is a systemchain on Kusama and shares the same native KSM token as a teleporter
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.
Encointer should not use the same address type as kusama It should be first registered here https://github.com/paritytech/ss58-registry/blob/main/ss58-registry.json and get its own number.
Integritee is ok
Hi @brenzi ok understood on the prefix, but why are you using a different cla than the generic app? are you planning to have a dedicated app? |
@ainhoa-a I'm confused. As this PR is only about integritee now, I guess you're talking about that. The README in this repo says
that's what I did and it seems to be what everyone else did. |
Hey @brenzi! Thanks for the contribution. Just to double check, this chain (Integritee) is not levering the new feature on polkadot for generic, right? Ainhoa was asking about the CLA, because in case you are going to use the new app (generic one), there is no need to define the app on this file. You can just use the GenericApp class. In case you are using the legacy app, then it is ok to take the latest value and increase it by 1. |
The generic app is fine for us, thanks for the info. Would be nice if you could make this really obvious in the docs and the readme in this repo |
The Integritee Network runtime is ready for ledger support. Adding it here
slip44 registered here: satoshilabs/slips#1785
🔗 zboto Link