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

Multi-operator mode #32

Open
amiller opened this issue Oct 20, 2024 · 0 comments
Open

Multi-operator mode #32

amiller opened this issue Oct 20, 2024 · 0 comments

Comments

@amiller
Copy link
Contributor

amiller commented Oct 20, 2024

Here's an outline of a minimal multi operator plan for the TEE backend:

  • To manage IP addresses, we might use an on-chain DNS. This could be a simple smart contract with a centralized automation script that updates the mappings. For now an EOA can own the contract. Eventually we would use encumbered. ENS is always an option but seems like it would require browsers to change.
  • We can set up a DNS record to use CAA and a fixed accounturi. This would mean that despite the domain pointing to many IP addresses, only the admin can get a cert issued https://letsencrypt.org/docs/caa/ As with the DNS entries, this can start as an EOA. But eventually would itself could become DAO-managed via account encumbrance
  • Instead of each node having to issue its own cert like the present, the "onboard" flow would pass along the shared private key for the cert. Instead of https it would have to be an encrypted message more like the decentralized ipfs project using NaCL
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant