Skip to content

Commit 2f08df3

Browse files
yiannisbotjsoares
authored andcommitted
Update OPEN_PROBLEMS/DECENTRALIZED_DATA_DELIVERY_MARKETS.md
Co-authored-by: Jorge Soares <[email protected]>
1 parent d9d4301 commit 2f08df3

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

OPEN_PROBLEMS/DECENTRALIZED_DATA_DELIVERY_MARKETS.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -233,7 +233,7 @@ The area of graph forming for Decentralised Data Delivery Markets revolves aroun
233233
* **Content discovery & routing:** the system can forward requests to find content
234234
* **Content placement:** the system should have ways to proactively distribute/replicate copies of data across different Providers in different geographic regions in order to be able to serve content fast.
235235
* **Content copy selection:** the system can choose the optimal copy of the content to serve if multiple copies exist in several Providers, where potentially:
236-
* every copy has a different “asking” price (defined by the cryptoeconomic model) and latency to deliver the content item, and
236+
* every copy has a different “asking” price (defined by the cryptoeconomic model) and delivery latency, and
237237
* every miner achieves different performance and has a different reputation profile.
238238

239239
In order to achieve the above goals the system needs to have an architectural structure, that is, where do end-users connect (e.g., to a retrieval miner, or to a separate content resolution system), which entity in the architecture makes content resolution and request forwarding decisions and finally, which entity(ies) has(ve) the required knowledge to forward requests to the closest (to the requesting user) copy, _aka_ nearest replica routing.

0 commit comments

Comments
 (0)