-
Notifications
You must be signed in to change notification settings - Fork 93
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
Support custom Polkadot JS types on the parachain side #97
Comments
Workaround:
|
@JoshOrndorff May I ask you why if I run the local node of Moonbeam and point PolkadotJS to it - it works awesome, and if I run a custom network using PolkadotLaunch - it doesn't work at all. And what is more interesting - how do I make it work properly? Any ideas on when do I get these custom types Polkadot.JS needs? |
I haven't had this problem in a while. I guess it either it got fixed or was caused by a mistake I was making locally. If you are trying to launch a local moonbeam network, you could get support in our discord. |
@JoshOrndorff tried to reach you via the Element chat, but sure, let me try discord instead :) |
Just got an update from the team via discord. There is a method now that will let you export the required custom types: moonbeam-foundation/moonbeam#838 |
Currently the launch config has a key called
types
. This allows the user to insert custom types that are needed on the relay chain side. This is useful and necessary because if launch can't communicate with the relay chain, it can't submit transactions.There is currently no corresponding support for the Parachains. I recommend we move the current
types
field into therelaychain
section, and add a similartypes
field to each parachain.It's actually not clear to me when or why launch needs to communicate with the parachains, but I think it must because I'm getting an error about how Polkadot JS can't construct the
RoundIndex
type, and indeed that is a custom type on Monbeam.The text was updated successfully, but these errors were encountered: