We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I believe that the version of subkey presently used supports JSON formatting which would likely be more reliable than regex and easier to upgrade.
Here's an example:
d@P51:~$ subkey --output=json inspect //Alice { "accountId": "0xd43593c715fdd31c61141abd04a99fd6822c8558854ccde39a5684e7a56da27d", "publicKey": "0xd43593c715fdd31c61141abd04a99fd6822c8558854ccde39a5684e7a56da27d", "secretKeyUri": "//Alice", "secretSeed": "0xe5be9a5092b81bca64be81d212e7f2f9eba183bb7a90954f7b76361f6edb5c0a", "ss58Address": "5GrwvaEF5zXb26Fz9rcQpDWS57CtERHpNehXCPcNoHGKutQY" }
The text was updated successfully, but these errors were encountered:
Fixed by #98
Sorry, something went wrong.
No branches or pull requests
I believe that the version of subkey presently used supports JSON formatting which would likely be more reliable than regex and easier to upgrade.
Here's an example:
The text was updated successfully, but these errors were encountered: