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.

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

DECENTRALIZED_DATA_DELIVERY_MARKETS.md Open Problem Statement #14

Merged
merged 66 commits into from
Feb 12, 2021

Conversation

daviddias
Copy link
Contributor

No description provided.

@daviddias daviddias changed the title Create DECENTRALIZED_DATA_DELIVERY_MARKETS.md Open Problem Statement DECENTRALIZED_DATA_DELIVERY_MARKETS.md Open Problem Statement Feb 10, 2021
@jsoares
Copy link
Contributor

jsoares commented Feb 10, 2021

Damn. This was on my to-do list for today and it would have been significantly easier in GDocs. I'll review...

ResNetLab organized a Research Intensive Workshop on 3DMs, out of it, the following ideas, structured as RFCs emerged:

Link to RFCs
* TO FILL
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

@jsoares jsoares left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Part I of the review: up to Data Delivery Metering & Fair Exchange heading.

Copy link
Contributor

@jsoares jsoares left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Part II: Up to the Distribution Graph Forming heading.

* Consequence: currency is spent
* Provider claims it has sent the file, but actually never did
* Type: Provider fraud
* Consequence: Client gets penalized without receiving the service
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Penalized why/how?

Copy link
Contributor

@jsoares jsoares left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Part III: Up to 369

Copy link
Contributor

@jsoares jsoares left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Part IV: the end

@jsoares
Copy link
Contributor

jsoares commented Feb 10, 2021

A few overall notes:

  • The document is really comprehensive and detailed. Kudos on all the work that went into it.
  • The document is also really long and took me a couple of hours to review. I'm afraid its length may put off readers. I'm not sure there's an action to be taken here but, in the future, I think it would be better to have a discrete and digestable document hierarchy. A good 5-page description of the overarching 3DM problem, followed by 5-page documents on each topic. Things could probably be a little more concise too; the detail is great but there is a point of diminishing returns.
  • Alternatively, something like this could one day become a technical report. While the content is (more than) sufficient, this would require a lot of work on making the different sections more uniform and coherent, i.e. bring them all to the same level of depth. I don't think this is an objective, so, again, just take this as a future suggestion.

Anyhow, great work!

@daviddias daviddias merged commit 3ff7862 into master Feb 12, 2021
@daviddias daviddias deleted the 3dm-open-problem branch February 12, 2021 11:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants