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
Public keys become very confusing. We often interact with the same nodes/node managers.
When we could decide optionally to prepare a list of our most used peers (pubkeys) linked to an Alias (nobody has to understand that alias, just the person using it for own reference) it could help with
building routes (make optional to use pubkey or alias) in configureHops.sh
seeing where a problem occurs when the roundTrip.sh runs into an issue
The text was updated successfully, but these errors were encountered:
Public keys become very confusing. We often interact with the same nodes/node managers.
When we could decide optionally to prepare a list of our most used peers (pubkeys) linked to an Alias (nobody has to understand that alias, just the person using it for own reference) it could help with
configureHops.sh
roundTrip.sh
runs into an issueThe text was updated successfully, but these errors were encountered: