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.

Sign up for GitHub

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

Jump to bottom

Watchtowers policy configuration, setup and update #36

Open
darosior opened this issue Oct 21, 2020 · 3 comments
Open

Watchtowers policy configuration, setup and update #36

darosior opened this issue Oct 21, 2020 · 3 comments
Assignees
@edouardparis @kloaec @JSwambo @darosior
Labels
High priority RFC-settled This has been discussed on a higher level, and now likely needs spec update.

Comments

@darosior
Copy link
Member

We still have not settled on this..
@darosior darosior added RFC This needs to be discussed at a higher level and removed Meeting labels Nov 10, 2020
@darosior darosior changed the title Watchtowers policy configuration Watchtowers policy configuration, setup and update Nov 13, 2020
@darosior
Copy link
Member Author

This is tightly related to the ceremony and the setup.

@darosior
Copy link
Member Author

After discussion IRL with @JSwambo and @kloaec , the process the more aligned with a decent UX for stakeholders and futures extensions of the protocol (watchtower rental) is to:

  • Add a "change policy" tab to the GUI (cc @edouardparis )
  • Get a policy configuration file out of a nice interface (checkboxes?)
  • Sign this file using the Bitcoin HM (this assumes to be able to read the content of the file on the HM screen) and probably a custom pk (maybe m/0/0/)
  • Send it through the Noise KK channel with the watchtower
  • The WT verifies the signature (since it has the xpub) and changes its policy on-the-fly

@darosior darosior added RFC-settled This has been discussed on a higher level, and now likely needs spec update. and removed RFC This needs to be discussed at a higher level labels Nov 22, 2020
@darosior
Copy link
Member Author

Marking as settled as it seems to be the best solution but needs some re-hashing imo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@edouardparis edouardparis

@kloaec kloaec

@JSwambo JSwambo

@darosior darosior

Labels
High priority RFC-settled This has been discussed on a higher level, and now likely needs spec update.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@edouardparis @kloaec @JSwambo @darosior