Update mxpy cookbook for v11#1124
Conversation
|
|
||
| #### Setting the explorer url | ||
|
|
||
| mxpy already knows the explorer urls for all three networks (Mainnet, Devnet, Testnet). This is particularly useful when running the CLI on custom networks where an explorer is also available. This key is not required to be present in the env config for the config to be valid. To set the explorer url use the following command: |
There was a problem hiding this comment.
mxpy and env can be somehow emphasized (e.g. code / italic / bold).
| To delete an env config, we use the following command: | ||
|
|
||
| ```sh | ||
| mxpy env remove <config-name> |
There was a problem hiding this comment.
Oh, now I see that we have both "env delete" and "env remove" 🙈
Might be tricky for users...
There was a problem hiding this comment.
I'd say it's pretty well explained what they both do.
| mxpy address set kind pem | ||
| mxpy address set path absolute/path/to/pem/wallet.pem |
There was a problem hiding this comment.
Sorry I did not see this before - how does this work? Only for the default address?
There was a problem hiding this comment.
It's a bit tricky and ambiguous. Maybe we should let the users only adjust the properties while adding an alias, and not afterwards (that is, immutable entries).
There was a problem hiding this comment.
Sorry for only mentioning this now 🙏
There was a problem hiding this comment.
Changed as discussed.
| As of October 2023, on Windows (or WSL), you might encounter some issues when trying to use Ledger in `mxpy`. | ||
| ::: | ||
|
|
||
| ## Interacting with the Multisig Smart Contract |
| --proxy=https://devnet-gateway.multiversx.com | ||
| ``` | ||
|
|
||
| ## Interacting with the Governance Smart Contract |
|
|
||
| ```sh | ||
| mxpy env set proxy_url https://devnet-api.multiversx.com | ||
| mxpy config-env set proxy_url https://devnet-api.multiversx.com --env devnet |
There was a problem hiding this comment.
For readability, the parameter --env sould have been before ... oh, nevermind, the previous ones are positional parameters.
The base branch was changed.
Description of the pull request (what is new / what has changed)
Did you test the changes locally ?
Which category (categories) does this pull request belong to?