-
Notifications
You must be signed in to change notification settings - Fork 19
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 runtime-api call to get OmniAccount #3148
Add runtime-api call to get OmniAccount #3148
Conversation
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.
👍🏼
…mniaccount-address
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.
Thank you, Kai! 🚀
I can see it locally from the p-js explorer:
However, I can't reach it programmatically. It should be on api.call
, shouldn't it?
I also tried forcing a client-api update off your branch to get the latest types, but i can't see it either:
I'm not sure if this is really part of the scope of this PR, but wanted to bring it up in case we are missing anything.
Co-authored-by: Francisco Silva <[email protected]> Signed-off-by: Kai <[email protected]>
…mniaccount-address
@jonalvarezz Can you try JSON-RPC with |
Yeh exactly, I was expecting it to be exposed automatically, but I can't find it. I'm not sure what I'm missing.
Sweet, this one worked: const account = await api.rpc.state.call('OmniAccountApi_omni_account', api.createType('CorePrimitivesIdentity', {
Substrate:
'0x3a2647fe0ecd1fe0d450fd8650cd8bf3536ecac77b6e8ec2df1b5f5fc9d62931',
}).toHex()); I guess we can live without this types meanwhile 🤔 |
Cool then I'll merge it |
…mniaccount-address
Context
As topic, locally tested OK