The retriev from cryptonetlab

Reputation score mechanism

We want to design a reputation score mechanism for the providers that we can use during testnet in order to

incentivize early adoption of the protocol;
de-risk users to lose money.

cc @lucaniz, @nicola

Work on brand, landing page, social networks

Key visuals [product design step 1]

In step 1 we are designing the key visuals.

First we’ll have a 2 propositions draft of the visual identity, moving toward one detailed brand identity
Then we’ll develop the iconographic setting and the related diagrams and use cases of it

@claudiofabbro will help us define the deliverables and the process
We’ll have a round of reviews to be scheduled

EPIC #34

Move to PL servers all the servers to make load tests

CLI for batch CIDs

Improvement of #12

soon to be discussed ti define design docs

Homepage design [product design step 2]

In step 2 we are designing together with @claudiofabbro the UX of the alpha version of the product and the landing page.

Coming after a few weeks of work from now, when we’ll have defined all the components of the ALPHA and what the landing page is about.

We’ll have to collect all the inputs coming from key references (e.g. https://drand.love )

Work on live notifications while listening on socket.io network

Create a factory contract to deploy your own contract and setup your own referee consortium

Doing the Work-Breakdown-structure to define a grid of activities and the consequent GANTT chart.

External audit to smart contract code

Write down in the readme how to run the demo

Add UI for registering as a provider

Homepage COPY

All the text that will be published on the website!

about
Team
Disclaimer for alpha
What else?

Convert Notion documentation to a Litepaper

Add admin functions to fine tune the protocol values

weekly check-ins’ record - 1st, 2nd, 3rd release

Every week you can expect 3 comments:

an AGENDA for the coming standup meeting
a short update with urgent todo’s and recap from the meeting
a log with updates on what happened during the week

release/1st (EPIC)

Within the #milestone 1, due by the end of july, we are designing 2 sprint sessions with a release at the end of each.
In this EPIC we'll track all the issues related to the 1st release!

1st release (due date: 28th June):

smart contract freeze

#10
#32
#2 [only design documentation] --> when specified issue?
#12 [we'll develop the CLI in a future release #45 ]

website is live

#4
#28

documentation

#39
#5
#38 basic documentation to run a node
#40

MVP —> dApp

#43

NFT feature

#46
check with the whole team and agree about due dates and related issues @turinglabsorg @irenegia

Automatic switch in the UI from any network to Rinkeby

Work on naming for the product and all pieces

The MVP was designed with a system of incentive and we asked to the CryptoEcon team at PL to review this system and help understanding the correct values for the parameters used there (see documentation here).

Request made here
https://github.com/protocol/CryptoEconLab-private/issues/68

Tag @alejandroterrazas

README with important links

Can we update the readme to have a bullet point list of all the important links? (kanban, demo, design docs, etc)

Website implementation Round#1

@Steve-Rog is coding the website following design from @claudiofabbro #28 and inputs from #40

We expect to have a design-to-code process, followed by a collection of feedbacks and a new iteration.

Improvements will be done to the product during next weeks, so we'll find a way to keep track of this (from brainstorms, to feedbacks, to updates)

For now I'll consider this a Round#1

When a deal is not accepted write it instead of show 0x0000000000000000000000000 address

OOO

If we want to track when we are Out-Of-Office we can use this issue and regularly update it, so that we can plan accordingly all together!

I’m aware this will be a public information, we can think about another way if you prefer.
Nonetheless, we need to coordinate so that release dates or other important milestones don’t overlap with our OOO time.

Add docker support for referees and storage providers

Documentation (EPIC)

We need to discuss together what kind of documentation we need to develop and why.
After this brainstorming phase, we’ll have to breakdown this issue into further steps.

As for the issues we were having, do we still need

video guides to explain the product or give public updates (blog posts, presentations)
~~public documentation wiki, built using gitbook or similar OSS~~
convert notion documentation to a lite paper
write down the read me how to run the demo (github /install)

In this issue me and @irenegia will define the deliverables, which will be planned accordingly (e.g. writing down the lite paper assigned to irene and design a visual guide outsourced to graphic designer)

UPDATE

Naming [product design step 0]

We’re having a serie of issues related to the design of the visual identity and UX of the alpha.

Step 0 is a brainstorming session hold by @irenegia and @nicola to come up with narrative/metaphor to communicate the product and identify each part/moment of the protocol!
This will help us set the limits and directions for the next stage of design.

@claudiofabbro will join this process to better learn about the protocol itself.

Add NFT improvement to Smart Contract

We want to add this new feature: the retrievability deals will appear as an NFT for both parties (client and provider) in their wallet.

Working on “how-to-use” documentation and tools to collect feedbacks [focus on economic side]

CLI improvements

Command Line Softwares for Providers and Referees

Client UX - ALPHA

Working on the design of UI/UX of the client side of the ALPHA

Demo day (EPIC)

We’ll have scheduled Demo days showcasing not just a collection of regular updates but a coordinated effort toward a designed release!

We are still deciding what this will consist of (videos, presentations, live walkthroughs ecc) but we need to coordinate to organise this small event

#35 expected in late June
#62 expected early august
#71 expected late september

Website with signing process for providers and referees

Create an API to support fast sync of current blockchain state, needed for a smooth UX

Client website

The client website https://pldr.dev/ misses some features. For example:

How does the client appeal? Proposal: add an appeal button
Each field needs some explanations and max/min values stated explicetely

Public documentation wiki, built using GitBook or similar OSS

Front-end improvements "MVP --> ALPHA"

We are improving the experience of using the MVP with details coherent with recent discussions and feedbacks, so that everyone can wrap their head around what’s happening via the protocol!

This constant update is carried by @Steve-Rog and in the coming weeks will follow up the design process #29 from @claudiofabbro

Round duration / Fast appeal

Each appeal is processed ("the trial") in rounds.
Each round has a fixed duration (round_duration), this is a protocol parameter.
Right now we have round_duration = 300 s (5 min).
Is this a good values?

Average block time at the time of the issue: ~12s
https://ycharts.com/indicators/ethereum_average_block_time#:~:text=Ethereum%20Average%20Block%20Time%20is,10.93%25%20from%20one%20year%20ago.

Tokens destination

The payment goes from client's account to provider's account (if no appeal, otherwise goes back to provider);
The appeal fee goes from client's account to the referees accounts (split the fee, each part in an account);
The collateral goes from provider's account to the contract account (if there is slash, otherwise back to provider);

Are we fine with this policy?
Or should we use the collateral when there is slash to repay the provider/referees?

~The protocol currently burns the collateral from the provider account when a file is not retrieved.
Should we instead give the collateral to the client (all of it, only a fraction of it)? ~

Cryptonet protocol review

@anorth
The protocol design is described in this notion for now.
https://www.notion.so/pl-strflt/Retrievability-Insurance-Protocol-638e218831904eb18e5dc4d7db505c60

Let us know here or there is you have questions/comments!

Video guides to explain the product or give public updates (blog post, presentations)

Product Design & Implementation (EPIC)

Together with @claudiofabbro https://claudio.dance , we are designing the product aspects of the data retrievability oracle protocol
@Steve-Rog will initiate and maintain the code!

DESIGN PROCESS

Each Tuesday morning there will be a kick-off meeting / brief sent via email from client (@irenegia) so that @claudiofabbro knows what we are expecting from him.
Each issue has a due date (one week after kick-off), in order to move to the next one and respect the overall deadline.

This process is made of 3 steps (+1) due for the #1st release milestone

#29 that belongs to #2nd release milestone

CODING PROCESS

Stefano will follow up with updates from the design, plus is already intervening to make key improvements on the MVP

We'll track this work in the following issues

#43 tracking the front-end improvements to the dApp
#49 which is about the implementation of the website (and the future updates we expect)

?

Change from event listeners to regular intervals to fecth slashes and deals

NFTs metadata/image_render

We need to

design an icon (expected in #27 )
program the image output coded via smartcontract (#10 )

LITEPAPER

@irenegia will covert notion documentation into a LITEPAPER

What program will you use?
What do we expect to have for #35 ?

cryptonetlab / retriev Goto Github PK

retriev's People

Contributors

Stargazers

Watchers

Forkers

retriev's Issues

1st release (due date: 28th June):

UPDATE

DESIGN PROCESS

CODING PROCESS

Recommend Projects

Recommend Topics

Recommend Org