Idea/Proposal: EV1 to use EDGE-URIDs

[alvin-reyes]

Proposal

I wanted to propose that we completely revamp EstuaryV1 frontend to use EdgeURID and the upcoming deal status oracle service.

Problem

EV1 frontend is the best frontend that the #ecosystem when uploading files to the filecoin network. It has all the features a user needs to upload files to the filecoin network in seamlessly. Unfortunately it's tightly coupled with estuary node - which can't handle the usage/demand. This is why we opted to decouple estuary in microservice which is now EV2, Delta and Edge.

The lack of scalability option of estuary node made it difficult to make deals. To this day, a chunk of upload request from Estuary frontend is not on the filecoin network, only on the estuary node which serves the content as a hot storage. This impacts the reliability of service and lower number of deals made thru the app.

Solution

I propose we decouple the Estuary frontend from the it's backend and use EdgeURID instead.

This means:

• every content upload goes to one of the edgeurids available.
• zone/staging will be represented by a edgeurid bucket.
• deal status will be available via deal status oracle service.

We will need to do this in phase with the priority of onboarding data to the filecoin network
Phase 1:

• change the upload to use edgeurid.
• display the bucket information where the content is located.
• hide the deals page for now until we have the deal status oracle available.

End result of Phase 1:

• content should be shown on the page and is included on the aggregation bucket on a specific edgeurid
• we will no longer use shuttles once we redirected all upload / gw to edgeurid
• metrics should show the totals based on edgeurid uploads.

Phase 2:
TBD