onchain storage - design & implementation

[0xjona]

GOAL --> DEADLINE With this effort we want design and implement

• [ ] retrieval pinning protocol updated website
• [ ] new onchain.storage homepage
• [ ] dapp updated (storage deals UX featuring retrieval pinning protocol atm)
• [x] improve retrieval pinning UX

by the end of September

about PROCESS

• desing steps We expect to

  • brainstorm and have design docs with requested features
  • have all the designs via FIGMA
  • collect feedbacks on functionalities and experience via FIGMA comments
  • eventually report in this github issue questions that needs further brainstorming

• implementation steps

  • from FIGMA designs to updated websites and dapp
  • check-ins with designers and developers about specs
  • we can collect feedbacks via slack channel or in this github issue
  • iterate

Feedbacks can be

• fix requests & bug reports to be immediately resolved
• elements that need to be redesigned (we start again from design steps)
• elements that have not been correctly translated from design to code

[0xjona]

dApp improvements:

• [ ] If someone wants to allow us to check them they add us as an appeal key (suggest this via UX)
• [ ] add multiple appeal addresses (+ other improvements already pointed out in the figma)
• [ ] loading status and notification system (related to appeals)
• [ ] onchain database vs api https://github.com/turinglabsorg/ipdb
• [ ] protocol/retrieval-pinning#72
• [ ] protocol/retrieval-pinning#73
• [ ] protocol/retrieval-pinning#78

[Steve-Rog]

Based on the call we had with @0xjona this morning I will focus on fixing the following bugs/improvements for the next steps:

DASHBOARD

• Fixing the "redundancy" for downloading/displaying the file (deal).
• Replacing the "refresh" button with "delete deal" (with confirmation prompt)
• protocol/retrieval-pinning#72

DEAL CREATION

• Ability to add more appeal address and tooltip to explain this new feature to the user.

OTHERS:

• Optimize "blocking" loading screens for the user. protocol/retrieval-pinning#73
• Implement the withdraw function for the user. protocol/retrieval-pinning#78

We will also coordinate with @claudiofabbro where needed.

[irenegia]

@0xjona will move this issue in the on-chain-storage repo

[Steve-Rog]

Improvements and bug fixing:

DASHBOARD

• Replacing the "refresh" button with "delete deal" (with confirmation prompt): 60%
• Optimize "blocking" loading screens for the user. 50%
• Fixed bug of refreshing deal information in live (no need to refresh the whole page)
• Optimized the function of the search bar

[0xjona]

@irenegia moved

[Steve-Rog]

Improvements and bug fixing:

DASHBOARD

• Replacing the "refresh" button with "delete deal" (with confirmation prompt): 80%
• Optimize "blocking" loading screens for the user. 75%
• Optimizing notifications
• Bug fixing: Improved logic enabling deal elimination button

DEAL CREATION

• Logical implementation of multiple appeal addresses when creating the Deal in expert mode 80%

[Steve-Rog]

• Major code improvements changes on deal specs and dashboard
• protocol/retrieval-pinning#72 100%
• protocol/retrieval-pinning#73 90%

[Steve-Rog]

DASHBOARD:

• Improvements loader dashboard
• Sidebar to withdraw Funds. protocol/retrieval-pinning#78 100%
• Optimizing notifications protocol/retrieval-pinning#73 100%
• protocol/retrieval-pinning#85 100%

DEAL CREATION

• implementation of multiple appeal addresses when creating the Deal in expert mode 100%

[0xjona]

@Steve-Rog so now we can cancel deals and add multiple appeal keys (maybe here missing UI) right?

[0xjona]

Here's the first proposal for onchain.storage UI @nicola figma draft

This is a brief introduction to some key concepts needed to understand the new proposition (the team discussed this last friday, collecting early feedbacks with @irenegia ).

Indexing

We are looking for a way to index the informations regarding each deal, and atm we have

• file metadata (like CID, name and extensione, size..) question: to store name and extension -what about size @turinglabsorg ?- and eventually other metadata we need some kind of IPFS database
• deal informations (whos' the provider, what's the value, how much time left..)
• oracle informations (in the case of retrieval pinning the user needs to know how many appeals are left, how much they cost, when an appeal is running what is the expect time to get a result..)

Indexing allows us to give the user a better "searching experience"! once there will be more protocols options available

Modularity

This design is made to allow the platform to scale, so that it will adjust consequently if there will be more protocols available, more referees network, more providers, without loosing sight on key information (like when signing a deal or searching through active ones)

questions to be discussed in another issue about UX research

• What is a deal?
• Can each deal "contain" more protocols?
• Is the deal like a 3D connection between one (or more) CIDs, one (or more) clients and one (or more) storage/retreival providers?

[Steve-Rog]

DASHBOARD

• Improvements to withdraw UI sidebar;
• Improvements Referee navbar (dynamic address, link)

NEW DEAL:

• Minor improvements UI

• Minor bug fixing

[0xjona]

Here's a new design proposal for the onchain.storage app @nicola @irenegia

during next check-in we'll go deeper into this proposal and collect feedbacks

[Steve-Rog]

• Improvements connection page

NEW UI

• Starting implementation new UI design
• Switch theme (dark/light) functions

[Steve-Rog]

• New Dashboard UI implementation 80%

[Steve-Rog]

• New "creation deal" UI implementation 45%

[Steve-Rog]

• New "creation deal" UI implementation 80%
• New Dashboard UI implementation 90%

[Steve-Rog]

• Several code improvements - Arrangement to make all elements of deal creation, modular (protocol selection, network, provider, file upload)

[Steve-Rog]

• New navbar integration
• scss improvements
• Filters logic
• Code improvements

[Steve-Rog]

GENERAL

• Improvements UI elements
• Improvements scss code

DEAL CREATION

• inverted next/back navigation buttons
• Disabled button "change file" when loading
• Collapse details network, provider when clicking "select network"
• Saving data when go forward/backward
• Bug fixing file upload
• Placeholder protocols added

[Steve-Rog]

• Start implementation of the new web3storage protocol 60%
• Possibility of choosing 2 protocols "retrieval pinning" and "web3storage"
• Auto change from rinkeby network to goerli when selecting web3storage protocol
• Dynamic "Deal Recap" data (depending on whether you choose one or the other protocols)