At the moment the endpoint of monetd is user configurable. This value is not published. So if a validator changes it, there is no way to determine its value.
We proposed adding a property to the peers.json file for the API endpoint. This would be specified as part of the join request too.
As it is in the peers json file it would be included in the /peers endpoint output, allowing it to be used from the wallet / dashboard.
I would suggest storing this value in a generic data structure of key value string pairs, to allow additional data to be attached without further code changes. This could include websites, telegram addresses, email addresses etc.
At the moment the endpoint of monetd is user configurable. This value is not published. So if a validator changes it, there is no way to determine its value.
We proposed adding a property to the peers.json file for the API endpoint. This would be specified as part of the join request too.
As it is in the peers json file it would be included in the /peers endpoint output, allowing it to be used from the wallet / dashboard.
I would suggest storing this value in a generic data structure of key value string pairs, to allow additional data to be attached without further code changes. This could include websites, telegram addresses, email addresses etc.