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
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
The text was updated successfully, but these errors were encountered:
Here's an outline of a minimal multi operator plan for the TEE backend:
The text was updated successfully, but these errors were encountered: