You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In chainsRelayed, there's an array of objects, each having a ticker and a relayerAddress fields.
I think it would be nice to allow specifying some kind of a label/alias identifying this wallet.
My use case: so I am running 2 relayers, one with Hermes and one with rly, using different wallets.
When I go to the UI, I see something like this:
and without using the external data it's unclear which wallet is used by which relayer.
I propose doing the following:
adding the optional alias (or something similar) field to an entity in chainsRelayed
in UI, changing the text of the "Address" link to display either alias, if it's present, or relayerAddress if not (while the link should still lead to the wallet from relayerAddress field).
Should be pretty backwards-compatible this way.
What do you think?
The text was updated successfully, but these errors were encountered:
Great idea. Agreed on adding it to the json object.
As you alluded to on the UI side, Smart stake works exactly like that. It has the concept of aliases in some of the other analytics/richlists. It shows alias in place of address where alias is present but the copy button (and perhaps hover/tooltip can still show address).
will add to todo and rollout shortly. thanks for the suggestions.
Btw, on json object: I suggest adding a JSON schema and a CI action to validate it (this goes out of scope of this issue for sure, but just a thought it'd be nice)
In
chainsRelayed
, there's an array of objects, each having aticker
and arelayerAddress
fields.I think it would be nice to allow specifying some kind of a label/alias identifying this wallet.
My use case: so I am running 2 relayers, one with Hermes and one with rly, using different wallets.
When I go to the UI, I see something like this:
and without using the external data it's unclear which wallet is used by which relayer.
I propose doing the following:
alias
(or something similar) field to an entity inchainsRelayed
alias
, if it's present, orrelayerAddress
if not (while the link should still lead to the wallet fromrelayerAddress
field).Should be pretty backwards-compatible this way.
What do you think?
The text was updated successfully, but these errors were encountered: