Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow to set node alias #304

Open
tnull opened this issue Jun 3, 2024 · 3 comments
Open

Allow to set node alias #304

tnull opened this issue Jun 3, 2024 · 3 comments
Labels
good first issue Good for newcomers

Comments

@tnull
Copy link
Collaborator

tnull commented Jun 3, 2024

We should add a Config field allowing to set the alias a node would use in its announcement.

For bindings, we'll need to make this a Vec<u8>. We could consider making this an Option<Vec<u8>> and refuse to a) open public channels if it's unset b) startup with public channels if it's unset or doesn't fit in the [u8; 32].

@tnull tnull added the good first issue Good for newcomers label Jun 3, 2024
@enigbe
Copy link

enigbe commented Jul 10, 2024

Hi @tnull, I'd like to pick this up if no one is currently assigned to or working on it.

@tnull
Copy link
Collaborator Author

tnull commented Jul 11, 2024

Hi @tnull, I'd like to pick this up if no one is currently assigned to or working on it.

Cool! Sure, go for it!

Note that in contrary to what I wrote above, we may want to expose this as an Option<String> and make sure we sanitize it before setting the alias. This will of course take away some degrees of freedom from our users, but also incentivize not to set some bogus/dangerous aliases that might be parsed wrongly by other network participants.

Moreover, we might want to consider only broadcasting node announcements if both the node alias and valid (public) socket addresses are set.

@enigbe
Copy link

enigbe commented Jul 25, 2024

Hi @tnull, I have a draft PR ready for a cursory look. I am still figuring out how binding generation works but didn't want that to hold up progress especially if you disagree with the direction this is taking. Please share some feedback when you can.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants