Author of the paper summary here - my understanding is that XFaaS doesn't run functions that are run in response to user input (e.g. XFaaS does not execute code that fetches and returns data because a user clicked on a button).
Neat and funny that they have an uncited figure (the one with the six exchanges with wacky trade size distributions) from research that we did while I was working at Bitwise.
100% - although this time around there is (in my opinion) _a lot more data_ [1] that regulated markets (like CME bitcoin futures) drive price discovery.
[1] There was data back then too, it just wasn't received.
The x-axis is size of trade, and the y-axis is % of trades at a specific size. ExRates had _many_ large trades, which shows up as a significantly different distribution than other exchanges like Coinbase/Bitstamp/Kraken (which had many small trades, and a long tail of larger size trades). See slide 42-44 here: https://www.sec.gov/comments/sr-nysearca-2019-01/srnysearca2...
Author here - thank you for pointing that out! The context in the comment you linked to is also helpful.
In your opinion, would it be correct to remove "uniquely" from the first sentence? Maybe that would help clarify the issue you pointed out. As far as I understand, the CIDs are still unique when referring to _metadata_, and can be used to "unambiguously fetch content from its peers".
IMO the closest equivalent to an IPFS CID is a BitTorrent magnet URL. They both can be used to obtain an intermediate metadata value, which can in turn be used to fetch file content.
> CIDs are still unique when referring to _metadata_, and can be used to
> "unambiguously fetch content from its peers".
A CID, mathematically, cannot uniquely identify a single file. Consider the CID bafybcfbaqydfnrof5stdvkzhwx6kglb7p6owxja:
[desktop]$ ipfs get bafybcfbaqydfnrof5stdvkzhwx6kglb7p6owxja -o temp.pdf
[desktop]$ shasum -a 256 temp.pdf
2bb787a73e37352f92383abe7e2902936d1059ad9f1ba6daaa9c1e58ee6970d0 temp.pdf
[laptop]$ ipfs get bafybcfbaqydfnrof5stdvkzhwx6kglb7p6owxja -o temp.pdf
[laptop]$ shasum -a 256 temp.pdf
d4488775d29bdef7993367d541064dbdda50d383f89f0aa13a6ff2e0894ba5ff temp.pdf
If you were to try fetching that CID from the peer network, which file you'd get would depend on which peer you're fetching it from.
I try to do paper reviews (like https://news.ycombinator.com/item?id=31379383) because it is a great way for me to learn more and _hopefully_ share in a way that is useful for others . My writing abilities are still a work in progress :)
