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
Is your feature request related to a problem? Please describe.
The Obol dapp has 5 separate Charons. But there is no convenient way to remember which Charon is being used for which purpose. It is way to easy to get them mixed up.
If the user is running Charons for different groups, like Lido and EtherFi, it can be tricky to remember which Charon is in use by which partner.
Describe the solution you'd like
Add a field to the Dappnode interface that allows the user to give a name and/or a description to each charon.
The name field would only be visible in the Dappnode interface, and would help the owner remember which charons are in use and by whom.
By default the name would be "Unused" so the owner could tell which ones had not yet been assigned.
Describe alternatives you've considered
Currently the only way to do this is by keeping a separate record, like a document or spreadsheet, but it's less convenient.
Additional context
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The Obol dapp has 5 separate Charons. But there is no convenient way to remember which Charon is being used for which purpose. It is way to easy to get them mixed up.
If the user is running Charons for different groups, like Lido and EtherFi, it can be tricky to remember which Charon is in use by which partner.
Describe the solution you'd like
Add a field to the Dappnode interface that allows the user to give a name and/or a description to each charon.
The name field would only be visible in the Dappnode interface, and would help the owner remember which charons are in use and by whom.
By default the name would be "Unused" so the owner could tell which ones had not yet been assigned.
Describe alternatives you've considered
Currently the only way to do this is by keeping a separate record, like a document or spreadsheet, but it's less convenient.
Additional context
The text was updated successfully, but these errors were encountered: