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

Initial Gateway #4

Closed
3 tasks
barlock opened this issue Nov 28, 2018 · 0 comments
Closed
3 tasks

Initial Gateway #4

barlock opened this issue Nov 28, 2018 · 0 comments
Labels
Epic

Comments

@barlock
Copy link
Contributor

barlock commented Nov 28, 2018 •
edited
Loading

Overview

An initial HTTP gateway enabling ens routing of ipfs locations. Overall logic defined in the architecture #1.

Questions

  • Can .luxe or https://eth.show handle this?
  • Can Cloudflare's _dnslink protocol do this?

Acceptance

  • Users can access their website resolve from ens over HTTP

Nice to haves
These are things that the architecture wants but isn't necessary for the first push. If these can't be accomplished easily, note in this issue what prevents it and or any workarounds.

  • custom domains
  • time traveling across revisions

Tasks

  • Investigate possible services that will do this for us
  • Test resolver with existing gateways (cloudflare, eth.show), see if we can use them
  • reEvaluate and break this down based on answers.

Assumptions
@barlock barlock added this to the MVP milestone Nov 28, 2018
@barlock barlock added the Epic label Nov 28, 2018
@barlock barlock mentioned this issue Nov 28, 2018
Closed
3 tasks
@barlock barlock removed this from the Sprint - 11/7 milestone Nov 28, 2018
@barlock barlock closed this as completed Jan 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Epic
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@barlock