update identities docs #801
Conversation
| :::caution | ||
| As of March 2023, keybase.pub is no longer available. As a consequence, the identity verification mechanism has been switched to GitHub, including the profile information fetched from keybase.io. | ||
| As of January 2024, the only accepted way to customize the information of a delegation contract is via MultiversX Assets. | ||
| Provisioning of information from keybase or your Github repository is no longer accepted and you should migrate to the new approach is you still use those. |
| "name": "New identity", | ||
| "website": "http://newidentity.com", | ||
| "twitter": "https://twitter.com/newidentity", | ||
| "location": "France", |
There was a problem hiding this comment.
👌
Or could have been Country_37
| "twitter": "https://twitter.com/newidentity", | ||
| "location": "France", | ||
| "owners": [ | ||
| "erd1qqqqqqqqqqqqqqqpqqqqqqqqqqqqqqqqqqqqqqqqqqqqqz8llllsh6u4jp", // staking provider address |
There was a problem hiding this comment.
this is the Arc Stake SP :D
There was a problem hiding this comment.
only on mainnet. On testnet/devnet it might not even exist. However, will put a dummy sc address
| - if you want to define the same identity for both a Staking Provider and simple nodes, set both the address of the Staking Provider and of the owner of the nodes | ||
|
|
||
| _Step 4: Open PR and validate the ownership_ | ||
| After opening the PR, you also have to validate the ownership. Refer to the --- section |
There was a problem hiding this comment.
what is --- section?
There was a problem hiding this comment.
thanks, forgot to put the link
| :::important | ||
| To also connect the validators themselves to a specific GitHub staking pool identity, two additional steps have to be completed: | ||
| :::note | ||
| Before MultiversX Assets, nodes owners needed to update the `Identity` field inside the `prefs.toml` file of each node. This is not required anymore now. |
There was a problem hiding this comment.
Should we remove this field in our next releases? cc @tanghel
There was a problem hiding this comment.
yes, it can be removed
| :::caution | ||
| As of March 2023, keybase.pub is no longer available. As a consequence, the identity verification mechanism has been switched to GitHub, including the profile information fetched from keybase.io. | ||
| As of January 2024, the only accepted way to customize the information of a delegation contract is via MultiversX Assets. | ||
| Provisioning of information from keybase or your Github repository is no longer accepted and you should migrate to the new approach is you still use those. |
There was a problem hiding this comment.
"
Provisioning of information from keybase or your Github repository is no longer accepted.
The only accepted changes are on mx-assets identities.
You can safely delete the keybase profile and also the multiversx repository inside your organization's github.
"
| :::important | ||
| To also connect the validators themselves to a specific GitHub staking pool identity, two additional steps have to be completed: | ||
| :::note | ||
| Before MultiversX Assets, nodes owners needed to update the `Identity` field inside the `prefs.toml` file of each node. This is not required anymore now. |
There was a problem hiding this comment.
Maybe you can also add " and you can safely leave the identity empty on your node configuration" to make it more clearer
Description of the pull request (what is new / what has changed)
Document new validators/staking providers mechanism for branding through MultiversX Assets
Did you test the changes locally ?
Which category (categories) does this pull request belong to?